Text flood kick or ban (Solved)

[gemeau50]

Our eggdrop only kick offenders for text flood. I cannot retrieve the parameter in the config file to make it ban.

Anyone knows how this parameter is called?

Tx in advance

[Sir_Fz]

Is it a script that causing this behavior or Eggdrop's built-in flood-chan protection?

[gemeau50]

It is the eggdrop's built-in flood-chan protection. We are not using the Sentinel TCL because it uses modes +mi to lock the channel. Being on Undernet, we are using mode +r. Flooders are never registered.

[Alchera]

Recheck your settings against the defaults in eggdrop.conf. Also check that your net-type is set to 2 (Undernet).

You may also need to look at max-bans, max-exempts, max-invites, max-modes & opchars.

[gemeau50]

net-type is 2
max-bans 45
Undernet doesn't recognized +E +I
max-modes 45
Banlist never full, we have a script on another machine which takes care of that.
opchars "@"

set global-flood-chan 4:10

I compare both config files as recommended but I couldn't find no parameters giving me a choice to either kick or ban. This is what I'm looking for.

[Alchera]

Undernet uses either of the following for channel status?

@ & ~ !

... if so, add to the opchars variable.

A properly configured eggdrop will function 100% on any of the selected networks in the configuration file. It's internal channel protection settings will work (read kick/ban) if the various channel flood control settings are set sanely.

To alter existing channel settings the ".chanset #chan <option>" trigger is required.

[DragnLord]

eggdrop normally only kicks for floods, you need a script to change that behavior

Code: Select all

bind flud - pub flud:ban
bind flud - join flud:ban
proc flud:ban ( n u h t c } {
  putserv "mode $c +b *!$u"
  putkick "$c $n temp flood ban"
}

should work nicely for banning channel message and channel join flooders

[gemeau50]

Tx for your snippet but TCL is not my script language.

Before binding a process, shouldn't I unbind something?

Also I would appreciate if you could tell me the meaning of the following:
n u h t c and $c

As for the format of the ban address, which format will *!$u trigger?
I am looking for the following format
*!*@everything_which_comes_after

[Sir_Fz]

Read Tcl-commands.doc about the FLUD bind.

[gemeau50]

We removed " bind flud - join flud:ban " since we don't want the bot to ban for join/part yet.

Here is what I am getting when trying to load that tcl:

[15:36:14] Tcl error in file 'egg.config':
[15:36:14] wrong # args: should be "proc name args body"
while executing
"proc flud:ban ( n u h t c } {
putserv "mode $c +b *!$u"
putkick "$c $n flood texte"
}"
(file "scripts/banfloodtext.tcl" line 4)
invoked from within
"source scripts/banfloodtext.tcl"
(file "egg.config" line 1368)
[15:36:14] * FICHIER DE CONFIGURATION NON CHARGE (INTROUVABLE OU ERREUR) ( config file not loaded )

Any ideas?

[Zircon]

I think DragnLord means { instead of (. So replace

Code: Select all

proc flud:ban ( n u h t c } { 

by

Code: Select all

proc flud:ban { n u h t c } { 

[gemeau50]

Tx! Now it does what I wanted it to do; kick et ban the offender.
But here is what I noticed.

1 - The eggdrop kicks the user using a default comment.

2 - Then ban the user

[20:17:18] <eggdrop> [20:17:23] Tcl error [flud:ban]: wrong # args: should be "putkick channel nick?s? ?comment?"

[20:17:19] * |nick was kicked by eggdrop (flood)
[20:17:20] * eggdrop sets mode: +b *!userid@complete.address


Actual TCL reads as follows:

Code: Select all

bind flud - pub flud:ban

proc flud:ban { n u h t c } { 
  putserv "mode $c +b *!$u" 
  putkick "$c $n flood_texte" 
}

[Zircon]

I think you should replace

Code: Select all

putkick "$c $n flood_texte"

by

Code: Select all

putkick $c $n "flood_texte"

[gemeau50]

Thank you all! It works fine.

[arvent]

Thank You! Works great and do really nice job.