By blitzz on Dec 12, 2009This is a simple kick..What it does is, if you got kicked from channel for 3 times or more/less (depending what number you put) it will kick back the person who kick you. Mybe seems useless but useful for nick lol|ta^ayu at DALnet. She pm'd me asking if there is a script which can stop a kicker who kick her 3 or more in burst.
For extra, i added the enable and disable so it easy to switch. And, with the introduction on how exactly every line does/working/run.
Hopely this can help you a bit.
#never off
on @*:kick:#: {
;will activated at least 5 second from the 1st kick
;you can change the number "5" below to what number you want
inc -u5 %script $knick
;this will not fight back ChanServ.
;you can change the number "3" which is calculate how many time you got kicked.
if (%script == 3 ) && ($knick == $me) && ($nick != ChanServ) {
;if the suspect set invite only, you still can join the channel
cs invite # $me
;join the channel where you got kicked with timer
.timer 1 2 .join $chan
;deop and ban suspect then kick them. Add edit the message waht ever you want
.mode # -o+b $nick $wildsite | kick # $nick %msg
}
}
#never end
;right click on channel then goto Switch to turn On or Off
;richt click on channel then goto Edit/Check kick message to check current message/edit.
menu channel {
Switch
.On:.enable #never | echo 10 -a **********Now turned On**********
.Off:.disable #never | echo 4 -a **********Now turned Off**********
Edit/check kick message
.Edit kick message:set %msg $$?"What kind of message you want to put?"
.Check kick message: echo 2 -a ....... %msg .......
}
You do realize that all commands are sent to the server by mIRC as raw commands don't you? There is no special mIRC syntax for the server.
Back when everyone was using 80286-80486 machines and perhaps even with p1-p3, this simple evaluation might have made a difference that you could somehow measure. It doesn't anymore.
I've tested it with identical p4 3.00 ghz machines with no difference found.
It is only a different evaluation made by YOUR computer. On the server end, where more evaluation could effect the efficiency of the script, there is no difference at all.
/mode # & /raw -q mode # are both evaluated by mIRC and then sent to the server as the identical command.
The only reason to ever send a raw command to the server now a days, is if there is a new command that mIRC cannot understand.
@Master-Of-Death You are assuming a whole lot with that akick statement. Default for most irc's, you need a 10 access level to set akick, but this number can be set higher. I have mine all set to 100. If you only had Ops, or a 5 level, the akick statement would just render an error.
The original line in blitzz's script is more efficient than both of these, because it handles the modes in one statement. This would be 10 times more likely to succeed against a good deop/ban protection script.
For a start
(%script == 3)
will not work secondly you do not need a timer on the
.timer 1 2 .join $chan
it would be better like this:
on @*:KICK:#:{
inc %kick. $+ $chan 1
if (%kick. $+ $chan >= 3) {
.cs invite #
raw -q JOIN #
raw -q MODE # +b $address($nick,2)
raw -q KICK # $nick No Kicking Me!
}
}
on *:JOIN:#:{
raw -q MODE # +eI $me $me
}