silence only blocks PRIVMSG to the bot, not channelmessages.
ignore is therefor infact better, silence also resets when you disconnect and ignore does not.
metroid wrote:silence only blocks PRIVMSG to the bot, not channelmessages.
ignore is therefor infact better, silence also resets when you disconnect and ignore does not.
When your bot msg-flooded by 100-150 floodbots ... there is no way to handle it without quits with msg "sendq exceeded" On the channel you simply place a +m or +l (to limit the mass join). I want to use it when my bots flooded by a specific number of floodbots.
AFAIK, silence is limited to 20 masks (atleast on quakenet).
And if you want a spambot protection, i would advice that you make something that checks the amount of messages recieved in the past <number> seconds, if it reaches a certain limit, set silence +*!*@*.
Automatic unsetting it after a few minutes or something.
metroid wrote:AFAIK, silence is limited to 20 masks (atleast on quakenet).
And if you want a spambot protection, i would advice that you make something that checks the amount of messages recieved in the past <number> seconds, if it reaches a certain limit, set silence +*!*@*.
Automatic unsetting it after a few minutes or something.
Adds or deletes the specified nick!user@host mask to or from your silence list. Masks on the silence list will be unable to send you PRIVMSGs or NOTICEs. If no masks are specified, a list of masks currently in your silence list is returned. The list holds a maximum of 5 masks.
Add [SOLVED] to the thread title if your issue has been. Search | FAQ | RTM
Actually i was wrong, the limit is 15 on quakenet.
And i would suggest you check some other examples on this forum that have something to do with flood protection. I'm sure you can adapt one to do what you want.
Alchera wrote:I'd seriously consider timed ignores. The use of silence would seem to be a bit limited.
With ignores it is possible to exceed sendq .... so the disconnect it is matter of time.
We dont want our bots to got disconnected ....
A good idea is to change nick when flooded
if you do silence + *!*@* it ignores everything for private messages ( private messages botnet flood). if there can be any such script which can perform Silence +|- thing for variable amount of time , it can solve the problem.