Timer Pool Duration Limit?

[firescue17]

Does ISBoxer has a limit on the duration for Timer Pools?

I have a combat chain using Mapped Key Step States which includes a Timer Pool for 4321 seconds (72 minute cooldown plus 1 second for good measure). This particular step will not reset properly and fire again. I also tried setting it to 2160 seconds (72 minutes / 2 plus 1 second) and it still wouldn't reset properly.

For further testing I changed the Timer Pool to 120 seconds at which point the Step did work correctly.

[lax]

Does ISBoxer has a limit on the duration for Timer Pools?

The practical answer is simply "No."

Technically they will break if the timer duration is long enough that if added to the current UNIX timestamp, it wraps around and starts counting again. Currently that's 1,394,723,858 (seconds since Jan 01 1970), and the wrap will happen at 4,294,967,295 (in the year 2106). So I guess if you want your timer more than a few billion seconds, then yes.

I have a combat chain using Mapped Key Step States which includes a Timer Pool for 4321 seconds (72 minute cooldown plus 1 second for good measure). This particular step will not reset properly and fire again. I also tried setting it to 2160 seconds (72 minutes / 2 plus 1 second) and it still wouldn't reset properly.

For further testing I changed the Timer Pool to 120 seconds at which point the Step did work correctly.

Are you sure you didn't Export to Inner Space or "Reload ISBoxer Settings" or such in the times that it didn't work? I can check the code but there is NOTHING special about the length of time of a timer and there is NO check as to how long it is.

[firescue17]

Thank you for the confirmation.

Are you sure you didn't Export to Inner Space or "Reload ISBoxer Settings" or such in the times that it didn't work?

The duration definitely complicates testing. The 10 and 15 minute cooldowns are about the extent of my attention span to sit there and wait for it lol. I'll report back if I find anything more concrete.

Thanks again.