yields an out-of-bounds array error if %Index% is initialized as 0 in the game. This happens even if the game itself changes the %Index% before the score setting task is run. This can be a pain when making a lot of use of the %number% argument to set scores.
I created the following work around to stop the beeping error messages:
%Score% is a special system variable that contains special logic to prevent it being updated more than once by any given task, and to sum all of the score's to calculate the value of %MaxScore%.
Whenever you enter an equation like %Score%+%Array[%Index%]%, ADRIFT will immediately calculate Set MaxScore to %MaxScore%+%Array[%Index%]%, and as the array index is wrong then you should be getting an error.
If you add anything other than a constant to %Score% then %MaxScore% will be wrong anyway.
You should create your own variable and use that instead of %Score% if you are going to do anything different than what it was intended for.
Sat 22nd Jun 2013 14:25
Ah saabie, thanks. I'll think of a way to work around this. But I actually like the only-one-trigger-aspect of the score system.
Setting score variable to an array element reference with a variable results in errormessage
