This is a nice code for when you have a bunch of people trying to connect when they have a kline, but there not smart enough to realize they are klined, so this snipplet kills them off, and saves you from seeing there nick when you do a /trace..
on *:snotice:*unauth*:{
if (%unauthkill == on) {
var %nick = $mid($7,1,$calc($pos($7,[,$count($7,[)) - 1))
var %reason = $mid($9,$calc($pos($9,:,1) + 1),$len($9))) $10-
if (%reason) .raw kill %nick You Have A Kline Here.. %reason | globops 4 %nick - 3Has Been Disconnected Because They Have A Kline!!!
if (!%reason) .raw kill %nick You Have A Kline Here. | globops 4 %nick - 3Has Been Disconnected Because They Have A Kline!!!
}
}
Sure does.But the point of this is for CS servers that hide security messages from clients there is no k-line notice on TCP/IP connection broken message.So when you place your k-line they arent shown as k-lined only TCP/IP connection broken and when they try to reconnect once baned they only get the TCP/IP connection broken message there is nothing to tell them they are baned from the server so useing this sends them a proper notice that they are baned an why so hopefully they stop tryin to connect.it useful to CS if the owner decides to hide security messages.As far as ircD i got no idea.`-.-´