Navigation
Install the app
How to install the app on iOS
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.
More options
-
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
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
More d20 errors
- Thread starter Lawful_g
- Start date
Belt of Dwarvenkind should not grant darkvision/dwarf abilities unless equipped. It looks like it is trying by assigning a Suppress tag, but that isn't working.
Also, the Robe of Eyes is still incorrect. It doesn't grant the comp bon to Spot, and it doesn't give 120 ft darkvision when equipped.
Also, the Robe of Eyes is still incorrect. It doesn't grant the comp bon to Spot, and it doesn't give 120 ft darkvision when equipped.
Equipped Bucklers are giving a -1 penalty to both main and off hand attacks, they should only be giving the penalty to the off hand attack.
pg 124, in the buckler's description:
"You can also use your shield arm to wield a weapon (whether you are using an off-hand weapon or using your off hand to halp wield a two-handed weapon), but you take a -1 penalty on attack rolls while doing so..."
The penalty applies to all attack rolls, not just the off-hand's attack rolls.
Studded leather is not giving an error when druids wear it.
I've put this on my to-do list. Thanks for catching it. (It'll actually be rather annoying to fix - the same tag is used in HL to mark an armor as having enough metal to be made mithral or adamantine and to mark an armor as being forbidden to druids, but studded leather can't be made into mithral studded leather and can't be worn by druids).
The Stunning Fist feat is not showing charges in the In Play tab, even though it is calculating charges in an Eval script.... It looks like you just need to click the show in charges button.
Fixed in the next update, thanks for the report.
Spiked Shields are not showing up as an option to be picked by Weapon Focus, although Armor Spikes are.
Armor Spikes are described as having their own proficiency, but shield spikes are a modification to the shield bash. So, once the shield bashing rules are implemented in HL, weapon focus (shield bash) will be available. Unfortunately, getting shields to work as weapons is going to be a lengthy project. Sorry.
Belt of Dwarvenkind should not grant darkvision/dwarf abilities unless equipped. It looks like it is trying by assigning a Suppress tag, but that isn't working.
Fixed in the next update, thanks for the report.
Also, the Robe of Eyes is still incorrect. It doesn't grant the comp bon to Spot, and it doesn't give 120 ft darkvision when equipped.
I'm afraid this is one of many complex magic items that aren't fully implemented (some other examples are the Flying Boots, Cloak of Arachnida, and the Cloak of the Bat). This is one of the projects on my to-do list.
"You can also use your shield arm to wield a weapon (whether you are using an off-hand weapon or using your off hand to help wield a two-handed weapon), but you take a -1 penalty on attack rolls while doing so because of the extra weight on your arm."
Is the full quote. I would interpret it to mean attacks with your off hand or while wielding a two handed weapon, but not with the main hand, for 2 reasons.
First, because it names both "using an off hand weapon" or using the off hand to "help wield a two handed weapon" in the examples. Second, it says the penalty is because of "the extra weight on your arm." which would be the off hand arm that is equipping the buckler. In the examples, the common denominator between the two examples is the use of the off hand, and it doesn't make sense that a buckler on one arm would hamper a weapon wielded only by the other arm.
Is the full quote. I would interpret it to mean attacks with your off hand or while wielding a two handed weapon, but not with the main hand, for 2 reasons.
First, because it names both "using an off hand weapon" or using the off hand to "help wield a two handed weapon" in the examples. Second, it says the penalty is because of "the extra weight on your arm." which would be the off hand arm that is equipping the buckler. In the examples, the common denominator between the two examples is the use of the off hand, and it doesn't make sense that a buckler on one arm would hamper a weapon wielded only by the other arm.
For a thing similar to Robe of Eyes (i.e. that gives darkvision that doesn't stack) I made a special with the same name, had it check for racial darkvision's value, if racial darkvision was higher than it's own set value it deletes it's own ShowSpec tag. If racial darkvision was less, then it deleted the ShowSpec tag on racial darkvision and leaves itself shown...
"You can also use your shield arm to wield a weapon (whether you are using an off-hand weapon or using your off hand to help wield a two-handed weapon), but you take a -1 penalty on attack rolls while doing so because of the extra weight on your arm."
Is the full quote. I would interpret it to mean attacks with your off hand or while wielding a two handed weapon, but not with the main hand, for 2 reasons.
First, because it names both "using an off hand weapon" or using the off hand to "help wield a two handed weapon" in the examples. Second, it says the penalty is because of "the extra weight on your arm." which would be the off hand arm that is equipping the buckler. In the examples, the common denominator between the two examples is the use of the off hand, and it doesn't make sense that a buckler on one arm would hamper a weapon wielded only by the other arm.
It says "on attack rolls", not "on attack rolls with your off-hand weapon".
If you can find anything official that agrees with you, I'll be happy to change it.
For a thing similar to Robe of Eyes (i.e. that gives darkvision that doesn't stack) I made a special with the same name, had it check for racial darkvision's value, if racial darkvision was higher than it's own set value it deletes it's own ShowSpec tag. If racial darkvision was less, then it deleted the ShowSpec tag on racial darkvision and leaves itself shown...
Darkvision uses the CalcValue procedure, which means that it applies only the highest Value.? tag on it. So, the robe of Darkvision only has to be bootstrapped with Value.120, and the Value.120 tag will be used instead of the Value.60 that's present on Darkvision by default (and wouldn't have been altered if a race had added darkvision).
If you want a Darkvision value smaller than 60, you'll need to use a script to delete the Value.60 tag before Final/10000:
perform hero.childfound[rDarkVis].delete[Value.60]
And assign the lower value as you would the higher value.
But darkvision is unique, and many races just bootstrap it and let it default to 60 feet rather than setting it by script. Therefore, if my character has racial darkvision + darkvision from whatever item there will be only 1 thing on the hero, and I have the Eval on my item delete the Value.60 tag to apply the 30 feet it would not stack correctly, right?
The Value 60 tag would be gone, the script would run giving it a value of 30, and the Dwarf race which should give a better (60 ft) version would not, because there is no script to run.
The Value 60 tag would be gone, the script would run giving it a value of 30, and the Dwarf race which should give a better (60 ft) version would not, because there is no script to run.
Just ran into this problem with darkvision again while doing the Inhuman Vision feat from Lords of Madness. I now realize things aren't working right with the Umbral Shroud feat either.
I really think it would be an advantage to not have darkvision automatically apply the Value.60 tag to itself and instead be set by the race, item or feat. What do you think Mathias?
I really think it would be an advantage to not have darkvision automatically apply the Value.60 tag to itself and instead be set by the race, item or feat. What do you think Mathias?
The real fix for this will be once Hero Lab can establish linkages to all the root picks of a unique pick. Then, I can have darkvision check the number of parents that exist, and figure out whether or not a Value below 60 should be used or not.
The problem with removing the default Value.60 is that there are an unknown number of user-created things out there that apply darkvision without worrying about applying their own 60' range. Every user who's created something using Darkvision would need to go in and add the 60' if I removed the default.
I think the chance of receiving Darkvision 60' from one source and Darkvision < 60' from another is very remote, and in my opinion, this problem isn't worth the effort it would take to solve until the proper mechanism is available.
The problem with removing the default Value.60 is that there are an unknown number of user-created things out there that apply darkvision without worrying about applying their own 60' range. Every user who's created something using Darkvision would need to go in and add the 60' if I removed the default.
I think the chance of receiving Darkvision 60' from one source and Darkvision < 60' from another is very remote, and in my opinion, this problem isn't worth the effort it would take to solve until the proper mechanism is available.
Last edited: