Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Thanks Kendall, but you should have seen me sweating through the Pathfinder bug thread's 60+ pages. This hardly seems long compared to that. Here are the list of bugs I have fixed for the next release (though I am not sure exactly when that would be, hopefully in the next month or so).
Familiar's Intelligence was defaulting to 10, rather than advancing and changing as the master gains levels. Now the familiar will gain the Int granted by the master, or its own Intelligence if that is higher (in the case of Improved Familiars).
If you don't see your bug reported here it was either already fixed (for example missing the Value 5 and 10 tags), I could not reproduce it, or it is something not for me to do (Power attack does not have an adjustment in d20, so I didn't address the Double Weapon not working thing, though if you have questions on your own adjustment I may be able to help), or it was noted for later fixing.
The INT of the familiar of a 1st level character is 6. Why are you trying to take it lower?
Yes - the core files don't have that. The add-on should also be changing the type that's assigned to familiars - they become magical beasts, and are therefore no longer subject to the INT 1-2 restriction that applied when it was still an animal.
Yes - the core files don't have that. The add-on should also be changing the type that's assigned to familiars - they become magical beasts, and are therefore no longer subject to the INT 1-2 restriction that applied when it was still an animal.
I believe that validation rule is in the Animal type that is part of the community files.What needs to be done is to go into the eval rule, and add that it should be valid if the hero has a tag stating they are a familiar or paladin's mount.
validif (hero.isminion <> 0)
~ We are also valid if we are a familiar or Paladin's Mount
validif (hero.tagis[CompIs.cArcFamil] <> 0)
validif (hero.tagis[CompIs.cPalMount] <> 0)
Thanks, Mathias. I had done that (quickly), but I hadn't accounted for my own stupidity. I saw "CompIs.cPalMount", but couldn't do anything with it because I read it as an "L" instead of an "I".
Anyway, here's the real fix:
Code:~ We are also valid if we are a familiar or Paladin's Mount validif (hero.tagis[CompIs.cArcFamil] <> 0) validif (hero.tagis[CompIs.cPalMount] <> 0)
I'm updating the file for the 1.7 release.
I for one, appreciate that you guys do your best to help those of us who don't have the time in our lives to dedicate to learning this scripting language....and I am sure at times, it must drive you all crazy having folks like me needing/wanting our HL to function a certain way, but don't have the skills to make it happen...
Thank you for your help. It really is appreciated.
That being said, I've done my best to incorporate the fix you have suggested, adding it in a couple different spots within the 3 eval rules for the Type-Animal in the user file and each time when compiling, getting an error indicating that "the script does not support the '@valid' special symbol so the use of validif is illegal" message.
Not sure if it is because I've added it in the wrong area of the eval script or what. There are no extra characters within the fix and I've cut/pasted it into the eval script and insured it is correct in it's format...
LordV
On behalf of paladins everywhere Sendric, I say thank you.
Now, how long until LawfulG update 1.7 hits the streets?
Nigel Fogg, aka The Wayfarer