Ban protect script. When a op trys to ban you it will remove then ban set by them and kick and ban them from the room with the message trying to ban me just resulted in your removal
on @!*:BAN:#: {
if ($banmask iswm $address($me,5)) {
mode $chan -b $banmask
mode # -qaohv+b $nick $banmask
mode # +b $address($nick,2)
kick # $nick 4Ban Protect Enforced, Trying to ban me just resulted in your removal!!12 $nick $+ .
}
}
@Master-Of-Death: Unfortunately so could yours and you really have to think hard on the script. There is no perfect auto unban that will ever work unless its scripted in an incredible length.
You have to consider massive amounts of nicknames also banning you at the same time and need to know how to filter out the massive bans.
Mine is almost completed and it works for almost all types of spam bans so one day I'll post it here - maybe.
that script is all wrong and when i say all i really mean it.
on *:BAN:#:{ if ($me isop #) && ($banmask iswm $address($me,5){
.mode # -b+b $banmask $address($nick,2)
raw -q kick # $nick Do Not Ban OPS!!!
}
}
That's what it should look like yours could flood you off a server for increased use of commands.
This would work, and it also doesn't.
If someone bans more than just 1 ban that affects you, you're only going to unban it once (or it might just be spammed in a single line where you unban several times.)
mode # -qaohv+b $nick $banmask
You're banning yourself in that again.
You're also putting just ONE $nick and you'll need 5 of those.
Instead use the 2nd line after but edit that.
mode # -qoahv+b $nick $nick $nick $nick $nick $address($nick,2)
And for ChanServ, you might want to use more of those commands even if other services use Anope. ChanServ is a bit more popular from what I've seen so use that commands because they guaranteed to work (unless the nick has exception.)