I think an ON TIMER feature would be useful in many situations. For example, if you run a script that uses one or several timers that must be kept active while your time online and for some reason it is stopped, you would have a way to start it again.

If you dont add a full stop you see when a timer goes off
/timertest 1 5 /echo -a This is a test
* Timer test activated
-
This is a test
-
* Timer test halted

if you use /timer -o the timer will only be stopped if

a] you or your script specifically tells it to
b] you close the mIRC program

..OR you can make an alias called /timer, which overrides the original command and applies these conditions you need.

If you make a /timer alias, it won't work if you specify a timer name

O-oh that's true, forgot about that, sorry.

i think thats what he means, soemthing stops it, so he would like the ability to know it stopped, like some yahoo puts TIMER* OFF in there script, ok you gotta be pretty wacked to be running a script that did that, but still... I guess they could always have turned the events off as well, so the on timer event would trip either

I just came across the same problem I think. I want to run a single timer that checks idletime on all connections, but if i start one on one server there's no way really to tell if that timer is already running. The result is that the timer starts ends and restarts when you open a new server window. But my solution would be a property called active so you can check if a timer is running already. Would look something like this:

if ($timer(name/N).active == $true) {
command
}
else {
timer[name/N] etc
}

Wouldnt that be usefull ?

Johan_NL

$timer(name/N).active would seem a little redundent as name/N must exist in the timer list for $timer(name/N).???? to come back with anything , just uses this

Never too young to learn eh ?

Johan_NL