-
Please note: In an effort to ensure that all of our users feel welcome on our forums, we’ve updated our forum rules. You can review the updated rules here: http://forums.wolflair.com/showthread.php?t=5528.
If a fellow Community member is not following the forum rules, please report the post by clicking the Report button (the red yield sign on the left) located on every post. This will notify the moderators directly. If you have any questions about these new rules, please contact support@wolflair.com.
- The Lone Wolf Development Team
Bug Reports - Community Created 3.5 D&D data set
- Thread starter ShadowChemosh
- Start date
Somewhere in reworking the domains in this latest version it now no longer recognizes the extra domain one gets to choose as a Radiant Servant of Pelor between Glory and Purification.
The validation error states Glory: Your deity does not offer this domain.
The bonus domain is granted at 5th level for the PrC.
*****
Favored Soul now applies Deity's Weapon Specialization to all weapons and armor giving validation errors for each weapon not having Weapon Focus except for the actual Favored Weapon.
The validation error states Glory: Your deity does not offer this domain.
The bonus domain is granted at 5th level for the PrC.
*****
Favored Soul now applies Deity's Weapon Specialization to all weapons and armor giving validation errors for each weapon not having Weapon Focus except for the actual Favored Weapon.
Last edited:
Last edited:
Tarmor
Well-known member
I opened your character, and added a number of different weapons to the character. None of them got any extra attack bonus, only exactly what they should receive. No validation errors. Don't see anything happening with armor either.
If you were thinking of the "Adamantine Dagger" as having an extra +1 to attack, perhaps you are forgetting that its masterwork?
Last edited:
I'm seeing the validation reports, and will look into what's causing them. Thanks.
Update: Looks like I failed to properly update the Weapon Specialization feat with the most recent update. To fix this issue, open the Custom - Core Book Mods file in the editor, and replace the entire eval script for fWepSpec2 with the following:
Code:
~ If we're disabled, do nothing
doneif (tagis[Helper.FtDisable] <> 0)
~ Set focus from the drop down or the Target.? tag
var id as string
var name as string
call fTargetId
~ We can't do anything without a unique id
doneif (empty(id) <> 0)
~ Assign the appropriate tag to all weapons that meet the criteria
foreach pick in hero where "IsWeapon." & id
perform eachpick.assign[Broadcast.WepSpec]
nexteach
~ Set our 'short name'
field[fShortName].text = "Spec: " & name
~ Forward the weapon specialization tag for the weapon to the hero
perform hero.assignstr["WepSpec." & id]
Last edited:
I get the following error when I compile it.
Thing 'cFASDeiWeS' - Condition phase/priority (First/9999) for bootstrap thing 'fWepSpec2' occurs after earliest rule/script (First/100)
Not sure if I screwed it up but thank you for your patience and help.
Edit: Switched First to Levels and it looks like it is working now. Please let me know if it should be something else.
Thing 'cFASDeiWeS' - Condition phase/priority (First/9999) for bootstrap thing 'fWepSpec2' occurs after earliest rule/script (First/100)
Not sure if I screwed it up but thank you for your patience and help.
Edit: Switched First to Levels and it looks like it is working now. Please let me know if it should be something else.
Last edited:
I've got another error regarding Weapon Specialization:
Invalid tag expression specified for 'foreach' statement
Location: 'eval' script for Thing 'fWepSpec2' (Eval Script '#1') near line 12
It seems to apply correctly, but continues popping up pretty much whenever I do anything else.
Invalid tag expression specified for 'foreach' statement
Location: 'eval' script for Thing 'fWepSpec2' (Eval Script '#1') near line 12
It seems to apply correctly, but continues popping up pretty much whenever I do anything else.
That's fine. It shouldn't have been on "first" anyway. The community set version's script runs at Pre-Levels/5000.
I was seeing this before I replaced the current script. You need to completely erase the script currently in the community set and replace it with the above script.
That did it, thanks.
I've encountered this as well. It eliminates Scribe Scroll but doesn't replace it with a selectable bonus feat. It does grant bonus feats correctly at level 5+, but not at level 1.
Thanks for the report. Fixed.
I'm afraid I'm unable to reproduce this issue. Can you explain?
You cant give paladin levels if your character's aligment isnt Lawfull good.For example if you are trying to do a Lawfull evil Paladin of Tyranny,you select paladin of tyranny from variants sector and set your aligment to lawfull evil but then you cant find Paladin cursor from classes/template section it disappears because you are not lawfull good.For level up my PoT to 12th lvl,I had to change his aligment to LG temporary : D
ShadowChemosh
Well-known member
Make sure you have set the class selection to ALL things instead of valid things. The base paladin class requires LG but once added to a character it can be other alignments based on the archetype.
I have a player that is a cleric of Sune. He decided to multiclass to paladin. But it only gives him light or medium armor, while a paladin should have heavy armor as well.
After searching this forum, it appears that this is a known issue, but is there a chance of getting it fixed anytime soon? The posts I found about it go back almost a year.
After searching this forum, it appears that this is a known issue, but is there a chance of getting it fixed anytime soon? The posts I found about it go back almost a year.
Does this have to do with variant classes? Pretty sure it's a core bug, so I'm not sure there's much I can really do about this one.