[General] Cooldown Timers with arrays bug?

[meatfactory]

Cooldown Timers with arrays bug? (solved)

For some time I have noticed a strange problem reoccurring when I try to make a cool-down timer with array. All started timer arrays except the 1st
[ example: RESTimer(1) ] don't seem to work. Any ideas?

 

[Hashjie]

Could you perhaps show us a trigger or script so that we can analyze the problem?

All started timer arrays except the 1st
[ example: RESTimer(1) ] don't seem to work. Any ideas?

How would we be abled to know what is wrong if you are not showing us what you are doing?

 

[Maker]

Set the initial size of the timer array to the highest index you're going to use or use CreateTimer() for the needed indexes. Timers are not automatically created, except indexes 0 and 1 in GUI.

 

[Hashjie]

Set the initial size of the timer array to the highest index you're going to use or use CreateTimer() for the needed indexes. Timers are not automatically created, except indexes 0 and 1 in GUI.

Good analyzation

It might be that he is starting a timer that doesn't exist yet instead of first creating it and then starting it. And as shown in your explenation this would only work with the first timer of the array if the array index is not set, since the default is 1.

 

[meatfactory]

Set the initial size of the timer array to the highest index you're going to use or use CreateTimer() for the needed indexes. Timers are not automatically created, except indexes 0 and 1 in GUI.

Damn! I see those orbs are well earned thank you for the valuable tip! +rep

 

[Maker]

The default initial size is 1. Initializaton block works like this:

set i = 0
loop
exitwhen i == initialSize
set array = CreateTimer()
set i = i + 1
endloop

So it creates indexes 0 and 1 if default size is 1.