Forums Bug Reports //timer strange

Hi, this is very strange...

When i type //timerkick 0 1 .kick #channel nick

and after some seconds i type //timerkick off

The nick on the channel was kicked a lot of time after
* Timer kick halted
Here is an example...

* Timer kick activated
* gh11 was kicked by [R]u[F]y ([R]u[F]y)
* gh11 has joined #example
* gh11 was kicked by [R]u[F]y ([R]u[F]y)
* gh11 has joined #example
* gh11 was kicked by [R]u[F]y ([R]u[F]y)
* gh11 has joined #example
* gh11 was kicked by [R]u[F]y ([R]u[F]y)
* Timer kick halted
* gh11 has joined #example
* gh11 was kicked by [R]u[F]y ([R]u[F]y)
* gh11 has joined #example
* gh11 was kicked by [R]u[F]y ([R]u[F]y)

I think that this is a bug...

This is purely due to lag, you cannot kick someone every 1 second without lag occuring as it takes over 1 second for the kick, rejoin and new kick to take place, so it builds up like a "backlog" in mIRC. So when the timer stops there is still a bunch of kick commands that are set to be executed.

Regards,

When you put -m 0 100 and after 2 or more seconds you stop the timer, mIRC won't stop the kick.

I have understood lag, but this is exagerate...

mIRC will stop, eventually. It may take a reasonably long time depending on how long you left the timer running but it DOES stop eventually after you stop the timer. This is simply due to lag.

You can see this is not a bug by specifying a different command inside the /timer - For example, /timer -m 0 100 echo -a example, then type /timers off and you'll see that /echo stops echoing.

Regards,