Long Nick Flood Prot......

Good day to you all.....

i'v been having a bit of a problem with "Long Nick" floods in my chat room "in MSN"....

i asked around and people are always giving me the same answer "Vincula Connection can't read nick names over a certin amount of characters, and that is the reason my protection can't kick long nicks.

i was wondering if there was something i could change in my connection "Vincula" to get it to read these long nicks to get my protection to kick them.

and there is no use in banning the long nicks...becouse i do that on owner..but the deny list gets cleared alot so i need a way to get my vincula to read long nicks to get my prot to work..................................

hope some one out there can help

add this to the room access list as a deny

??????????????????????????????????????????????????*!*@*$*

Export the access list regularly. Then if it gets cleared, you can import the saved list and won't lose that information.

as i said before....the access gets cleared alot by the other owners.....and most of the time i am not around to re-add...........i need a fix to get my vincula to kick long nicks

Try this

on @*:JOIN:#: { if ($len($nick) <= 50) { sockwrite -tn msn.server. $+ $cid access $msn.get($cid,fullroom) add deny ??????????????????????????????????????????????????*!*@*$* 0 : Auto Long Nick Ban $+ $crlf $+ kick $msn.get($cid,fullroom) $nick Long Nick Kick } }

however, if it doesn't work, try this

on @*:JOIN:#: { 
if ($len($nick) <= 50) { 
sockwrite -tn msn.server. $+ $cid access $msn.get($cid,fullroom) add deny ??????????????????????????????????????????????????*!*@*$* 0 : Auto Long Nick Ban 
sockwrite -tn msn.server. $+ $cid kick $msn.get($cid,fullroom) $nick Long Nick Kick 
} 
}

Gate keeper i tried ur codeing the 2nd one with the kick and i added it to its own filein remotes but the prob im finding is its kicking every chatter that joins the room. i havent tried the first one yet as soon as i do ill let u know how it works

k i just tried the first bit of coding to and it also seems to be doin the same thing as the second one it kicks all users as a long nick

It should be this

on @*:JOIN:#: { 
if ($len($nick) >= 50) { 
sockwrite -tn msn.server. $+ $cid access $msn.get($cid,fullroom) add deny ??????????????????????????????????????????????????*!*@*$* 0 : Auto Long Nick Ban 
sockwrite -tn msn.server. $+ $cid kick $msn.get($cid,fullroom) $nick Long Nick Kick 
} 
}

lol had the signs around the wrong way. The first code is a tad faster than the second though, which is why i suggested the first code. And the reason for this is because it is only 1 sockwrite command, not 2. But really you wouldn't notice the difference.

on @*:JOIN:#: { if ($len($nick) >= 50) { sockwrite -tn msn.server. $+ $cid access $msn.get($cid,fullroom) add deny ??????????????????????????????????????????????????*!*@*$* 0 : Auto Long Nick Ban $+ $crlf $+ kick $msn.get($cid,fullroom) $nick Long Nick Kick } }

i tried em a lil while ago... i have the oppisite problem..... it denys em fine, just doesnt kick.. tried em in a group room though.. so i dunno if that had anything to do with it

just use ozzy's code that he posted then.

well all i did was correct the coding

the kick doesnt work cause mirc doesnt see the nick if its over 50 characters

if that is the case, then it can only work if you put that code into the connection [it would need tweaking ofcourse, and you would need to know how to actually put it into the connection]

Can you just go ahead and add a deny to ??????????????????????????????????????????????????*!*@*$* without the long nickname having to join the room? That way you won't have to kick.

He says the other owners clear the denys when he's not around.

seems like the only remainning way is to code a timer to add deny ??????????????????????????????????????????????????*!*@*$* each %seconds time

i guess a good way to do it is like this

 on @*:JOIN:#: { if ($nick isowner $chan) { sockwrite -tn msn.server. $+ $cid access $msn.get($cid,fullroom) add deny ??????????????????????????????????????????????????*!*@*$* 0 : Auto Long Nick Ban } } 

but then you would be getting the error that entry is already in access list quite a bit. So find out what raw it is, i think it is 914, and block it.

if hes gonna code an auto access-add when an event is triggered, it shud be on KICK, coz access is most porbably cleared on kicks

i know that most of the clear access list bots send a reply when it is done, so you could try this.

menu menubar {
-
Long Nick Auto adder
.On/Off
..$iif(%lnaa == on,$style(2)) Turn On : set %lnaa on
..$iif(%lnaa != on,$style(2)) Turn Off : unset %lnaa
.Character Allow Limit
..View : echo -at Allow Limit: %lnaaallow
..Change : set %lnaaallow $$?="What is the maximum amount of characters allowed for long nick and please note that nicks are in irc format"
.Responce lines
.View List : notepad.exe clear.txt
.Add : /write clear.txt $$?="Enter key words that the user/script will say for this to activiate"
.Clear All
..Yes : /write -c clear.txt
}
on scriptallow:TEXT:*:#: {
var %x = $strip($1-)
if (%lnaa == on) && ($read(clear.txt, w, * $+ %x $+ *)) { sockwrite -tn msn.server. $+ $cid access $msn.get($cid,fullroom) add deny $str(?,%lnaaallow) $+ *!*@*$* 0 : Auto Long Nick Ban }
}

It's a long shot i know, but it should do what you want it to do.

You could always use this as a backup:

on *:join:#:{
 if ($len($nick) >= 20) access $chan add deny $ial($nick).addr
 kick $chan $nick Nickname too long.
 access $chan add deny $str(?,20) $+ *!*@*
}