• 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

Standard DC but with negative modfiier Code?

bodrin

Well-known member
Heres a quirky one, from Council of Thieves Bestiary.

HTML:
Captivating Scent (Ex) An aspidochelone exudes intoxicating
pheromones from its skin, causing nearby creatures to seek it
out. Anyone within a 1-mile radius must succeed on a DC 12
Will save or feel inexplicably drawn toward the aspidochelone
by the most direct route possible. This effect is not an
overwhelming compulsion, but more a subtle suggestion. The
save DC is Charisma-based with a –10 penalty.
The ability works, bootstrapped without the -10 modifier using the Standard DC Charisma pick, however if I add the -10 Racial DC modifier i get this error

HTML:
Hero Lab was forced to stop compilation after the following errors were 
detected:

Thing 'raCapScent' - Value for stat 'abDC' is outside bounds
 for numeric stat (0 to 1e+015)

So here's a question / request why can't a negative modifier be applied to the standard DC, and does anybody have a DC script that I can utilise please?

ATM i've got it working but it's a static DC number that won't dynamically change with any Charisma effects applied!

PS Searching the forums revelas the words Difficulty and Class but not in the correct context!
 
Try adding it as a script, rather than a modifier to the field when you bootstrap the thing. I think there's a minimum value set for abDC of 0, and by bootstrapping it with a value, you're telling HL that you want that field to start with that value - HL then complains that the value you've given it is outside the parameters that have been established for that field's allowed values. I'm guessing that the StandardDC tags are incorporated at Post-Attributes/10000, so you'll want your script to be after that.
 
Try adding it as a script, rather than a modifier to the field when you bootstrap the thing. I think there's a minimum value set for abDC of 0, and by bootstrapping it with a value, you're telling HL that you want that field to start with that value - HL then complains that the value you've given it is outside the parameters that have been established for that field's allowed values. I'm guessing that the StandardDC tags are incorporated at Post-Attributes/10000, so you'll want your script to be after that.

Any example of this type of script in the datasets. Just for a reference point i'm useless at the moment it's 02.36AM GMT and i'm struggling to maintain coherent thought!
 
A script on the ability:

Phase: Post-Attributes, priority: 15000
Code:
field[abDC].value -= 10

Also use the "Standard DC" dropdown on the ability.
 
A script on the ability:

Phase: Post-Attributes, priority: 15000
Code:
field[abDC].value -= 10
Also use the "Standard DC" dropdown on the ability.

After trying to make this work I think i'm missing something.
The above code compiles but doesn't modify the DC value

I've tried variations of the code but kept getting errors or still no DC value modification. This is the code I have that currently compiles but still doesn't work. raCap Scent is the ability id!

HTML:
hero.childfound[raCapScent].field[abDC].value -= 10
 
Final/11000 looks good.

Hello and welcome to Hero Lab for Dummies. Remember phase and priority timing is probably the most stupidest thing to forget.

Anybody else wish to join Bodrin in the idiot corner? No? Good let's continue!

Thank you for the nudge towards phase and priority Mathias works a treat.:o
 
Last edited:
yup, in the corner for you. Then right back out and get to work on the next file, lol.

Its so easy to forget the simple stuff, its alwasy the comma in the code that trips you up not the complex API integration.
 
Back
Top