Senior Member
Join Date: Jan 2015
Posts: 160
|
What's the latest point I can add Hit Dice and still have them process that info? I'm thinking First 498 is when that is processed, but since maximum number of heads that can be added is based on size, I can't process how many heads are added (and therefor how many hit dice) until First 680.
|
#11 |
Senior Member
Volunteer Data File Contributor
Join Date: Jan 2010
Location: Chicago, IL (USA)
Posts: 10,729
|
Hit Dice are like "Levels" so it needs them set before Post-Levels. This is why class scripts run mostly at Post-Levels/10000 as all the Level calculations are done.
Hero Lab Resources: Pathfinder - d20pfsrd and Pathfinder Pack Setup 3.5 D&D (d20) - Community Server Setup 5E D&D - Community Server Setup Hero Lab Help - Hero Lab FAQ, Editor Tutorials and Videos, Editor & Scripting Resources. Created by the community for the community - Realm Works kickstarter backer (Alpha Wolf) and Beta tester.- d20 HL package volunteer editor. |
#12 |
Senior Member
Join Date: Jan 2015
Posts: 160
|
Alrighty, real life intruded, but now I'm back at this. Almost have Multi-Headed done. I had to take off the hard cap on number of heads that could be added based on size, since I have to add those heads (the 2 HD per head really) before I can even check the size in order to have the BAB and other HD derivative stats calculate. As is, I just need to know how to throw an error from an evaluation script. A la:
if ((herofield[tSize].value <= 0) & (field[abValue].value > 1)) return an error where abValue is the number of heads, since a medium or smaller creature can only have one additional head added to it. |
#13 |
Senior Member
Lone Wolf Staff
Join Date: May 2005
Posts: 13,207
|
Code:
if (herofield[tSize].value <= 0) then if (field[abValue].value > 1) then return an error |
#14 |
Senior Member
Lone Wolf Staff
Join Date: May 2005
Posts: 13,207
|
Eval Rules do the same things as eval scripts, and can also report errors.
|
#15 |
Senior Member
Join Date: Jan 2015
Posts: 160
|
What I need is the code that throws the error. "Return an error" was my placeholder, but is not what registers it as an error.
|
#16 |
Senior Member
Lone Wolf Staff
Join Date: May 2005
Posts: 13,207
|
In that case, you'll want to turn the logic around, so that you can turn it valid if both tests pass, since Eval Rules start out invalid by default.
Code:
validif (herofield[tSize].value > 0) validif (field[abValue].value <= 0) |
#17 |
Thread Tools | |
Display Modes | |
|
|