Im running sentinel but one problem is realy bad and sentinely doesnt seem to pikc it up as quick
people notice flood the channel and sentinel completley ignores it unless there is a join/part flood or sumthing similar is there a way to ban after the first notice ?
The original purpose of sentinel.tcl was to stop dangerous floods that threaten the security of the bots and the channel. I believe it has acheived this and flooders have moved to mostly "annoying" floods such as the one you describe (notices are popular I gather because they make mirc beep by default, increasing the annoyance factor).
It was never sentinel.tcl's purpose originally to pick up simply annoying floods except in extreme quantities when they may become dangerous (which is catered for by the all-encompassing TEXT flood detector). But I have succumbed in recent times and added detection for standard notice and long text floods. These detection mechanisms are in the next version, the release of which depends on when I get time to complete work on it.
There are however always going to be floods with some degree of annoyance, and once the next sentinel.tcl is out you can expect flooders to simply move onto something else (most likely lots of short text messages) which will still be considered annoying.
simple way to beat notice floods is just to instantly bk anyone who does a channel notice. there's never a real good reason to do them, and they just piss ppl off.
yea usualy when im online you can modelock the chanel and then ban the flooders but yesterday they knocked the bot off with the msg xcess flood which was a bit worrying
the flood was a mixture of notices and messages to the channel it jammed my screen but there was not enuff for the bot to pick it up as a tsunami/text flood?
look forward to the next release
in the mean time does anyone know of a script which bans on channel notices?
I'd advise against the suggestion of simply kicking/banning flooders who notice the channel. This might be effective on one or two flooders, but against a floodnet it is a dangerous course of action.
sexzy, I'd be interested in knowing how the bots got knocked off by the notice/tsunami you referred to - perhaps you're running another script that is reacting to them. In order to find out you would need to change "set debug-output" in the bot's config file to 1, enable .console +v in DCC, then keep a log of that DCC session during a flood to see what the bot is trying to send to the server.
I couldn't but agree with what Slennox said about the danger in ban-kicking all ppl who send channel notices.
AW of course. Just use a variable and increment it on every channel notice. Use a timer to unset it (say after 3 secs).
When that variable is >= 3 u can start ban-kicking ppl, otherwise the code just increments and exits.