@ D_J, there is no timer(s) on the snippet which would cause the delay. The delay could be from your mIRC or from the server. You may have an anti-flood protection enabled or so is the server.
@ Aucun50, there is no flood control on Jethro_'s code. He was suggesting to the to romen to add a trigger flood control.
I have a similar script to this but all you have to do is provide the word trigger & the output. It can also contain several outputs. Check out xTalker v1.01.
I fixed the script for the action part. The <act> identifier was already there, though the command was missing. I also listed the identifiers that you can use, check the intro above.
Hi Cheiron, the only thing I can think of which could be causing the problem is with the name of your server. Please PM me the name of your server. Thanks.
Sorry for the late reply. This usually happens when another nick/bot has already kicked the nick-to-be-kick-banned at the same time. Try using ".kick" instead of just "kick" for the command. Not sure if that would prevent on seeing that message though.
Since this is an update of your previous snippet, just update your old snippet as said on the rules of posting snippets.
**
DO NOT post new versions as new snippets. You must edit your previous snippet.
(If you add Snippet v1.0 and Snippet v2.0 as two snippets Snippet v2.0 will be deleted.)
**
Hey wtfdidido, thanks. Pm me a copy of the revised script you have right now and also your room/server where I can test it. I checked the link you gave me before but It requires me to register. =P
1. You could have just used $lines(file.txt) to get the number of lines for your file.
2. Use /var instead of /set, making them local variables (or just get rid of the variables, which is not really necessary ;) )
3. Optional: You can also use /play to make use of it's flood protection, then use an alias so you can manipulate the output.