There is no way that using /timer + /msg is going to be faster than /msg itself, unless you are overriding /msg in a way that take into account if it's used from a timer, somehow, but assuming you don't have a custom /msg alias (and no custom /timer alias), what you are saying is not possible.
Note that when you send a message from mIRC, mIRC locally display the message to the window, because you won't get a PRIVMSG from the server for your own message, so in the client sending the messages, all of them will appear instantly, regardless if you are ircop or not, while a different client on the channel will have to wait for the PRIVMSG from the server, we can easily assume there will be a small delay due to the lag from the sender + the time it took for the IRC server to parse the message and send it back to all clients accordingly.
On the first video, when I pause around 1sec, you can see that the mIRC client sending the messages already displayed all the number from 0 to 20, while on the second video, if you pause around the same amount of time, mIRC only displayed 0 1 and 2, this is all correct since /msg happens instantly, while the /timer will add a small delay.
On the first video, the receiver is getting the first nine messages within the same second, the next seven messages within another same second, and the last 3 within the same second, this seems correct.
However on the second video, the receiver sees everything at the same time, which is indeed weird.
You can use /debug @win to see what mIRC is sending.
Last edited by Wims; 28/07/15 08:56 PM.
