tcl to kill bottler and irc-ork

[Davy]

Surely it would be best to ban any CTCP version reply that ISNT "mIRC" or "Iroffer" ... for those minority who use *nix in my channel, i wont miss, and that should account for Bottler / who changes ctcp versions, and IRC-Ork..

I'm looking for a script that bans anything except mIRC / Iroffer..

[BarkerJr]

Most Blotters will use mIRC as CTCP version reply.

[foobar]

i guess the only real way to keep out non chat clients is to make the chan +R (registerd users only) ir give the chan a +k and advertize the key in the channel topic.

[dudeicles]

i used the most recent version of this script with all the fixes and one day it works fine and without even altering the script i get errors like

Tcl error [ban_scripts]: can't read "::chan": no such variable
or
Tcl error [ban_scripts]: can't read "::banscripts": no such variable

can anyone please help me?

[Sir_Fz]

you're peobably using an old TCL version.

[dudeicles]

maybe it doesn't work on a Windrop i guess... any ideas how to format it for a windrop?

[CoMMy]

99% of the stuff normally works on a windrop.
The error should be somewhere else.

[]Kami[]

Just google tcl didnt worked on windrop

[CoMMy]

Some TCL commands involve Linux cmds also thus if you run thos on *Win Machine they definatelly wont work!

[SmokeyOne]

i know this is a old, subject, but as it looks, bottlers are becoming a real problem on alot of networks. Wouldn't it be easier to check against, to set number of channels, lets say in this case..... 30 channels, and do a kick/ban on a set time limit ?


the bbottler can mask the version reply, but the channel listing doesn't lie, so doing a version with maybe a backup of a whois counting the number of channels the user is in, could work.