trivial: ID targeting values could only be a byte size

[Avenger]

In the example for

109 IncrementGlobal(S:Name*,S:Area*,I:Value*)

we have a ChangeSpecifics call with 4000. In fact, that value would translate to 160. I suggest changing 4000 to 160 (nothing changes in the code, but people won't think they can safely go over 255).

[Roxanne]

 

In the example for

109 IncrementGlobal(S:Name*,S:Area*,I:Value*)

we have a ChangeSpecifics call with 4000. In fact, that value would translate to 160. I suggest changing 4000 to 160 (nothing changes in the code, but people won't think they can safely go over 255).

 

Just to clarify - if I use IncrementGlobal(S:Name*,S:Area*,I:Value*)

with e.g. value 1 or 2 or 3 each time it is triggered, I may well end up with a sum of total value way above 255 -

or am I mistaken?

[Avenger]

 

 

In the example for

109 IncrementGlobal(S:Name*,S:Area*,I:Value*)

we have a ChangeSpecifics call with 4000. In fact, that value would translate to 160. I suggest changing 4000 to 160 (nothing changes in the code, but people won't think they can safely go over 255).

 

Just to clarify - if I use IncrementGlobal(S:Name*,S:Area*,I:Value*)

with e.g. value 1 or 2 or 3 each time it is triggered, I may well end up with a sum of total value way above 255 -

or am I mistaken?

 

 

Incrementglobal has nothing to do with this, it is just a reference to the example which contains an incorrect ChangeSpecific call

You cannot increment ID targeting values