Setting "No Power Points"

[CapedCrusader]

The first one might work with a trustme...

[Gumbytie]

Wow, once again CapedCrusader has crushed me with a new term I have never heard of!

Never seen it before or how to use it. Would it look something like this?

field[powPoints].text -= 1 trustme

I don't want to really try that without feedback, I have broken HeroLab enough times randomly trying out code combinations

[CapedCrusader]

Oh, forgive me, I thought you knew that one. It goes on the line preceding... although - it's text, so you may have to pull it into a number field to do the math then put it back... and try it without the trustme first. I modify that in Setup/1100 in the Arcane Powers object for the new Limitations and it doesn't need one. Oh, one other thing - most of the time it'll need a minimum value, hence the maximum function so if it's zero or below it'll stop at one.

var newpoints as number
newpoints = field[powPoints].text
newpoints -= 1
trustme
field[powPoints].text = maximum(newpoints, 1)

[Gumbytie]

The gods of Lankhmar appear to be against me (:

I tried your code, Caped, with and without the trustme.

var newpoints as number
newpoints = field[powPoints].text
newpoints -= 1
trustme (tried it with and without)
field[powPoints].text = maximum(newpoints, 1)

Without trustme I get this error:

Error: Syntax error in 'eval' script for Thing 'edgStrongCa1' (Eval Script '#1') on line 4 -> Only derived fields can generally be modified via scripts (field 'powPoints)

With trustme I get this error:

Error: Syntax error in 'eval' script for Thing 'edgStrongCa1' (Eval Script '#1') on line 5 -> Only derived fields can generally be modified via scripts (field 'powPoints)

Thanks for all the help so far. I feel guilty when you answer, don't want to take away your time with all of the stuff you working on with Pathfinder, Companions, etc.

I will still experiment with this but players will keep tracking by hand for now.

[CapedCrusader]

OK, my mistake.
The reason it works for me is because I've changed that to a derived field in this latest version. I thought trustme would get around that for now.

[CapedCrusader]

OK, my mistake.
The reason it works for me is because I've changed that to a derived field in this latest version. I thought trustme would get around that for now.