Anyway, if $ticks is the same when a new timer fires, your older timer won't fire, possibly causing a race condition
there may be some sort of race condition involved, since this only happens with low delays, but it doesn't seem to be the only problem. $ticks is perhaps a little misleading there; letting mIRC assign a name or using $rand(1, 1000000) instead, and we can see the problem is just as easily reproducible. in fact, giving the timer a constant name is the only case where i
didn't observe the bug.
Removing "$+ $ticks" and letting mIRC generate its own timer names seems to work just fine for me.
did you remove 'test' too? :P
to reproduce: remove the complete timer name,
make sure there are no timers active, and run the test.
the second step is important, and probably why Wims wasn't able to reproduce the issue after the first trial of the alias: that one timer that failed to execute was still considered active.
