Incrementer minimum value based on one of the hero's ability scores

[Redcap's Corner]

I'm trying to code a class special ability that has an incrementer with a maximum value of 0 and a minimum value equal to the negative Intelligence modifier of the hero. Currently I'm checking the user-selected value of this incrementer at post-attributes/1000, though I may be able to check at a later point if necessary.

I have been trying to accomplish this by setting both the minimum and maximum values of the incrementer to 0 by default, but adding the following to the beginning of the script at post-attributes/1000.

field[actUserMin].value -= #attrbonus[aINT]

Unfortunately, I'm still getting 0 as my minimum value. Is there a particular timing when I'd need to make adjustments to the value of field[actUserMin]? Am I going to have access to the hero's final Intelligence modifier at that time?

[Redcap's Corner]

As an addendum, if I open up the information window for this class ability's fields, it shows field[actUserMin] with the value I want (in this case -5 for a character with 20 Int), but it isn't actually applying that number to the incrementer, which makes me think the incrementer needs the information earlier. But I won't have access to the value of aINT much earlier, right? Is there a work-around?

[ShadowChemosh]

"Search" is your friend on this forum. THIS thread has pretty much the exact same questions/issues and it has answers and timing information.

[Redcap's Corner]

After digging around I've found that post-levels/500 is where I want to set actUserMin. Does anyone know a work-around for that priority that will get me to the hero's Intelligence bonus (which normally isn't calculated until post-attributes)?

EDIT: I did actually search pretty extensively, but didn't stumble across that thread. Thanks for pointing it out for me!

[Redcap's Corner]

Hmm... so it actually isn't possible from the looks of that thread. A tracker will be wayyy too confusing in presentation for this ability. I guess my best bet is to set an arbitrary minimum that's lower than could conceivably be possible and then just set an error message if the user ever goes lower than they're allowed to?

[Aaron]

Originally Posted by Redcap's Corner

Hmm... so it actually isn't possible from the looks of that thread. A tracker will be wayyy too confusing in presentation for this ability. I guess my best bet is to set an arbitrary minimum that's lower than could conceivably be possible and then just set an error message if the user ever goes lower than they're allowed to?

As you say, probably the eval rule route is the best here.