egghelp/eggheads community

antilamer - control code, caps, etc. control

2007-06-20T12:33:30-04:00

I haven't integrated such a function natively, but setting 'antilamer(maxcaps)' above 1.0 should effitively disable the feature, because there cannot by logic be more than 100% CAPS ^-^.

PS: sorry for late answer, I read the email at work and forgot to check it at home ^-^.

Statistics: Posted by De Kus — Wed Jun 20, 2007 12:33 pm

antilamer - control code, caps, etc. control

2007-06-12T06:16:05-04:00

Great script but How do i remove CAPS/SCREAMING KICKS From the script?.. i dont need those for my channel.

Statistics: Posted by silverboy — Tue Jun 12, 2007 6:16 am

antilamer - control code, caps, etc. control

2006-04-25T12:16:04-04:00

Seems to be working nicely

Statistics: Posted by Zeniitti — Tue Apr 25, 2006 12:16 pm

antilamer - control code, caps, etc. control

2006-04-25T11:37:24-04:00

Ok, I fully restrartted eggdrop and try antilamer script. I'll post results here.

Statistics: Posted by Zeniitti — Tue Apr 25, 2006 11:37 am

antilamer - control code, caps, etc. control

2006-04-24T17:46:46-04:00

but this a mysterious coincidence, because I came back here tonight to release a fix for a "no such var" error message... but the error which occured here was:

Code:

can't read "new": no such variable    while executing"if {$antilamer(warn) && $total == [expr $antilamer(kick) - 1] || ($total > $antilamer(kick) && $new) && [botisop $chan]} {   puthelp "NOTICE $nick :$..."    (procedure "anti:lamer" line 90)

which has been fixed with the new 0.1.9 release of course .

Statistics: Posted by De Kus — Mon Apr 24, 2006 5:46 pm

antilamer - control code, caps, etc. control

2006-04-24T16:28:56-04:00

That's not an error from De Kus' antilamer. It's from allprotection4.5, you need to .restart your bot or .ap:reset . This issue will be fixed in 4.6 (hopefully will be released soon).

Statistics: Posted by Sir_Fz — Mon Apr 24, 2006 4:28 pm

antilamer - control code, caps, etc. control

2006-04-24T13:24:58-04:00

0.1.8 and this bumb to this:

Channel:

Code:

[20:34] [XS4-3622] :DDDDDDDDDDDDDDDDDDDDDDDDDDDD

Bot:

Code:

[20:35]  [20:36] Tcl error [btext:line]: can't read "o": no such variable[20:35]  [20:36] Tcl error [repeat:kick]: can't read "o": no such variable[20:35]  [20:36] Tcl error [caps:kick]: can't read "p": no such variable[20:35]  [20:36] Tcl error [text:char]: can't read "o": no such variable[20:35]  [20:36] Tcl error [text:line]: can't read "o": no such variable

Channel:

Code:

[20:37] [XS4-3622] dÃ mDÃ¥Â¥â€¼Ã‹iâ•¦Â§1Ã¥â•¦â• â™‚Â·~â•¬Ã¥â•¦Â¶â•”vâ•šâ•”â”¼u

Bot:

Code:

[20:37]  [20:38] Tcl error [btext:chars]: can't read "o": no such variable[20:37]  [20:38] Tcl error [btext:line]: can't read "o": no such variable[20:37]  [20:38] Tcl error [repeat:kick]: can't read "o": no such variable[20:37]  [20:38] Tcl error [caps:kick]: can't read "p": no such variable[20:37]  [20:38] Tcl error [text:char]: can't read "o": no such variable[20:37]  [20:38] Tcl error [text:line]: can't read "o": no such variable

Statistics: Posted by Zeniitti — Mon Apr 24, 2006 1:24 pm

antilamer - control code, caps, etc. control

2006-02-25T08:56:24-04:00

Seems I did it again. I updated a script and was too lazy/unconfident to release it . So here we go:

New version is 0.1.8 and that are the changes:
- always warn on first abuse now
- removed missplaced join, added more comments for config
- fixed a copy&paste error which caused a var abuse not found error

Statistics: Posted by De Kus — Sat Feb 25, 2006 8:56 am

antilamer - control code, caps, etc. control

2005-06-16T08:45:41-04:00

v0.1.5 released

Changes:

the way "multiple flooding" in one line was counted has been. I added now a divisor (which should never be set to 0 ) to lower everything above the 1 times
ex.: so if you set maxcolors to 10 and someone wrote 40 chars in color, he got a counter of 4 and got kicked immediatly (with default values). now 4 times will be recuded to 2.5 times (and rounded real)

best shown with the actuall code:
expr round(1 + ($rounded - 1) / $::antilamer(multidivisor))
CAPs counting has been changed a bit, so beware. Too low settings might kick users pretty fast. now the caps count is not divided by the string length, but by the count of (ASCII) letters. so screaming like "WTF !?!?!" will be 100% caps and probably trigger marks as well and he will gain 2 flood counts ^-^. the detecting is saved in $re(al6), feel free to change it, but setting something wrong could cause the bot to count every line as 1 char and kick everyone using single caps .
some default settings have been changed, also note to not delete the new setting (at the very bottom of the settings) while importing your old ones

I tried to test the time consumsion of the script, however on the shell I was testing it, it was simply to fast, each iteration took less than 1ms . So im pretty confident the regular expression caching is working. I will test it on a slower shell as soon as this was one gets identd back .

Statistics: Posted by De Kus — Thu Jun 16, 2005 8:45 am

antilamer - control code, caps, etc. control

2005-04-19T19:10:26-04:00

i see. k

Statistics: Posted by dotslasher — Tue Apr 19, 2005 7:10 pm

antilamer - control code, caps, etc. control

2005-04-19T01:13:34-04:00

li have a small question: how would you translate "Hervorhebungen"?

haha, sorry, I forgot that the shortcut "hl" might not neccesarrily lead to "highlight" .

[01:38:11] [Beholder]: Tcl: can't read "bnick": no such variable
[01:38:11] [Beholder]: Tcl: while executing
[01:38:12] [Beholder]: Tcl: "getchanhost $bnick $chan"
[01:38:12] [Beholder]: Tcl: (procedure "anti:lamer" line 85)
[01:38:12] [Beholder]: Tcl: invoked from within
[01:38:12] [Beholder]: Tcl: "anti:lamer $_pubm1 $_pubm2 $_pubm3 $_pubm4 $_pubm5"

--> i changed $bnick to $nick and it bans now, so no more bnick error

what a stupid mistake, while writing a piece a code for another here I must have copied that thing with "bnick" instead of "nick" as varname accidently, lol, what a stupid mistak .

I will update the download later, meanwhile perhaps its easier so search and replace all "bnick" to "nick" like Darth_Unslut did ^^.

this happened when doing !! ?? .. or __ abuse

i want to point out that it doesnt give the correct banmsg:
[02:19:48] [Hola]: psdojfspoj fsdfpjo sdsqdsqd qsd
[02:19:49] ::: Kick: (Hola) was kicked by (Beholder) (Excessive use of Colors is not allowed here (Warning -> Kick))
[02:19:49] ::: Join: (Hola) (God@StaticBox-A48595E7.access.telenet.be)
[02:20:10] [Hola]: ________________________
[02:20:11] ::: Mode: (Beholder) sets (+b *!*God@StaticBox-A48595E7.access.telenet.be)
[02:20:11] ::: This (*!*God@StaticBox-A48595E7.access.telenet.be) ban affects (Hola)
[02:20:11] ::: Kick: (Hola) was kicked by (Beholder) (Banned: 10min - Excessive use of Colors is not allowed here)
his 1st msg was in colors, his second was ___ abuse. why does it say: colors in the banmsg?

Maybe you set a small value for kick. If you are using 0.1.3 and not 0.1.2 which had a stupid bug in the lsort expression it might be that the color abuse was quite more high. if you set color very low the points count very fast. I was thinking about changing it, but I am not sure. Actually, when you say 5 colors are bad, than 20 colors are already 4th that bad, because the increase is currently round(amount / maxvalue) ^-^.
I removed it in the others, because you would have to use at least 41% to prevent the to count a 3 on 100% .
So simply said, the color dominated -> color is the main reason for kicking ^^. dominating is considered if highest ranking abuse has a counter of -1 of kick or more

set liste [lsort -integer -decreasing -index 0 $liste]
if { $total == [lindex [lindex $liste 0] 0] || [lindex [lindex $liste 0] 0] > [expr $antilamer(kick) - 1] }

the list should look like this now:

{3 color} {1 marks}

here it is decited if it takes a specific reason or if it takes the default one.
Probably this way isnt very accurate for a kick value below 4 ^-^.

Statistics: Posted by De Kus — Tue Apr 19, 2005 1:13 am

antilamer - control code, caps, etc. control

2005-04-18T19:35:17-04:00

this happened when doing !! ?? .. or __ abuse

[01:38:11] [Beholder]: Tcl: can't read "bnick": no such variable
[01:38:11] [Beholder]: Tcl: while executing
[01:38:12] [Beholder]: Tcl: "getchanhost $bnick $chan"
[01:38:12] [Beholder]: Tcl: (procedure "anti:lamer" line 85)
[01:38:12] [Beholder]: Tcl: invoked from within
[01:38:12] [Beholder]: Tcl: "anti:lamer $_pubm1 $_pubm2 $_pubm3 $_pubm4 $_pubm5"

--> i changed $bnick to $nick and it bans now, so no more bnick error

i want to point out that it doesnt give the correct banmsg:

[02:19:48] [Hola]: psdojfspoj fsdfpjo sdsqdsqd qsd
[02:19:49] ::: Kick: (Hola) was kicked by (Beholder) (Excessive use of Colors is not allowed here (Warning -> Kick))
[02:19:49] ::: Join: (Hola) (God@StaticBox-A48595E7.access.telenet.be)
[02:20:10] [Hola]: ________________________
[02:20:11] ::: Mode: (Beholder) sets (+b *!*God@StaticBox-A48595E7.access.telenet.be)
[02:20:11] ::: This (*!*God@StaticBox-A48595E7.access.telenet.be) ban affects (Hola)
[02:20:11] ::: Kick: (Hola) was kicked by (Beholder) (Banned: 10min - Excessive use of Colors is not allowed here)

his 1st msg was in colors, his second was ___ abuse. why does it say: colors in the banmsg?

Statistics: Posted by dotslasher — Mon Apr 18, 2005 7:35 pm

antilamer - control code, caps, etc. control

2005-04-18T18:56:34-04:00

looks interesting De Kus, i'll start using/testing it right away.

i have a small question: how would you translate "Hervorhebungen"?

Statistics: Posted by dotslasher — Mon Apr 18, 2005 6:56 pm

antilamer - control code, caps, etc. control

2007-06-20T12:37:37-04:00

This script does has various feature, some are well know, some are probably unique:

toggleable warning before kick
bans repeated offense (after kick)
Kicks abusive use of CAPS, ASCII Codes and Screams
Kicks use of control codes, if their affected characters exceed a limit
so writing a whole in color might be already worth a kick, while writing a few chars in color will never, nethertheless how many control codes are used, unless they exceed the total limit (set to reduce CPU usuage in tsunami floods)
customable kick/ban reasons. the script tries to determine what the user was actually kicked for

I am greatfull for any bug reports and tips of execution time optimizing without changing capitlities.

General idea from lamer.tcl by cmouse, but this is a complete new script (I completely wrote it vom scratch. Just giving credit for the idea of regexp counting).

Download v0.1.9:
http://home.arcor.de/dekus/antilamer.zip
http://home.arcor.de/dekus/antilamer.tar.bz2

Statistics: Posted by De Kus — Mon Apr 18, 2005 2:11 pm