egghelp/eggheads community

Hmm, is that what this non-banning issue is about? sentinel can get away with banning every non-op who does a CTCP, join-part, and so on during a flood because that's relatively uncommon. Non-flooders sending text during a flood happens a lot, so banning in that case would result in a lot of "...

Not sure if this is what you mean... But anywayz... If you have a large number of bots looking after a channel, it can be kind of annoying when a dynamic ban expires and every bot on the botnet does a -b for each ban that has expired. So ideally I just wanted one or two bots to do all of the -ban re...

Maximum bans: 100 Maximum channel bans: 19 Small flood short lock: Active Flood notification: Off Unless your network actually permits a channel ban list in excess of 19 I'd suggest setting it to just 19. Possibly also: .chanset #chan -enforcebans +dynamicbans It does permit ban lists greater than ...

Of course... Please note that the 'text flood' setting is only set so low to make it easier to trigger the locking script when I was testing. The others are pretty much left at their defaults. - Bot CTCP flood: 5 in 30 secs - Bot MSG flood: 6 in 20 secs - Channel CTCP flood: 5 in 20 secs - Channel A...

Hello, I have been experiencing problems with sentinel not baning anyone after it has detected a flood and locked the channel. A few days ago I had a couple of users flooding a channel which triggered the channel locking mechanism of the sentinel script, thus preventing them from flooding. However, ...