Forums Bug Reports Timer interval

Tried to search for a similar topic about this bug, but I didn't find it, so here we go:

I noticed a little bug with timers; if timer's interval is over 19327352 seconds, it will execute the command immediately.

/timertest 1 19327352 echo works like it should
/timertest 1 19327353 echo executes the command immediately

I tried it only with newest mIRC and with Windows 7.

That's because there is a limit on how long you can make the timer.

A timer that long (31 weeks, 6 days plus) is silly and inaccurate anyway. It should be set to start at the date if used at all.

As a sorta work arround you could install the following code into the perform section of options.

That's hardly a record... I've had uptimes of over 15 weeks without problems.
But we're getting off-topic now.

The nature of the limit is unclear though for me. It's not the regular 32-bit value limit.

Yeah, not sure the reason for a limit on it, but it's been commented on in the past. Using a date is much better as you mentioned if you need it that long. That or have it check every X minutes/hours/days/etc and if $ctime - original $ctime > whatever amount, do something. It won't be exact to the second, but something THAT far into the future probably doesn't need to be that exact anyhow.

If, however, you must have a lengthy timer, for whatever insane reason that may be, why not split the timer by dividing it in half? ie: 9663676 = 19327352 / 2

That way, you could use multiple timers that execute after the first, second, etc, has stopped.

It's not that I need a timer like that, but I don't see any reason why the maximum interval must be exactly "19327352" (especially when there isn't any mention about it anywhere or anything).

Some error message would be nicer than unexpected flood.