The problem I wrote to you... your suspicion I think is right and that was exactly what I was thinking too!
In practice, when you connect after a lot of time the script has to load a lot of things: messages from the net, chat logs, open the channels that are in autojoin etc etc, and only at the last the queries were opened!
So it probably happened that the 3 seconds had already passed before the queries were even opened, making the script already active, and when the queries were opened, after all the things mentioned above had loaded, the response message was sent ... that's w***t appeared to me.
It also explains w***t happened only a few times, that is only when I connected after a long time: because when you connect after a short time there are fewer things to load, so 3 seconds were enough.
I will do the test with 10 seconds which will surely be enough, but I really think this is it :)
As for the additions you made, great!
Under "Close query", I understand that now I no longer have to put ";" to this line of code ->
I just need to turn off query closing from the option and I'm good to go, right?
Is it possible to make the "Close query" entry more intuitive? That's fine exactly the way it is, I'd just like to add the word "Active" next to it when it's on, and "Disabled" when it's off.
