on :kick:#: {
if ($me == isop) {
/cs unban #chan $me
/cs akick $chan del $me $+!@*
/cs akick $chan del $address ($me,2)
/cs invite $chan $me
/cs ban $chan $nick $address
/cs akick $chan add $nick
.msg $chan haha that was fun now was it
}
}

but becose of $nick ban protection:
[21:44] ERROR Excess flood

[21:44] * [10053] Software caused connection abort

:D maybe command lines change works beter?
on :kick:#: {
if ($me == isop) {
/cs unban #chan $me
/cs akick $chan del $me $+!@*
/cs akick $chan del $address ($me,2)
/cs akick $chan add $nick
/cs ban $chan $nick $address
/cs invite $chan $me
.msg $chan haha that was fun now was it
}
}

after the fixes it is very nice!

fire_wizard1 name calling isnt needed, he is only trying to help because YOU still have bracket mismatches

one in the menu

and one at the bottom

and "if" statements go INSIDE of "events"

your missing your "on *:kick:#: {" section of your code m8

Aucun50, you fudgetard, i did all that, so stfu ,,|, -_- ,|,,

You need to read more about scripting like events, menus, if-statements, and for ever "{" there NEEDS to be a "}".

m8 , edit your scripts in your mirc then paste them here.
bracket mismatch in your menu
bracket mismatch in your "if" statement
"if" statements go INSIDE of events
you have NO event
your "if" statement should be

if ($me isop $chan) { commands here }

ok i updated the snippet, so it should be much better

cs akick $chan del $me
cs invite $me
cs akick add $nick

and you still need another } at the bottom

you do realise chances are, if you can add to the akick list,
they wont be able to kick you in the first place?

if your a channel owner or admin most servers wont let a normal op kick you
and if your a normal op you cant usually add to the akick list

just as a fyi... rather than double post.. if you look where you original comment is you will see the edit button. if you click that, that will allow you to edit and expand on your original comment :)

grins might be helpful as a future reference to cut back on how many times you have to type and update etc.

other than that.. looking not too bad now. nice job

ok i fixed it up, and took off the ban part of the protection so it should just work on your nick and address w/o clearing the akick list

/me smacks his face
thanks PunkTuReD i will change it right now

instead of

cs clear $chan akick

it would be nice if you could remove only yourself from the list, just incase you do already have some nicks on your akick list that you want to stay on it.

its ok PunkTured. and i fixed it

sorry for the double post :-s

[23:24] -ChanServ- Syntax: AKICK channel ADD mask [reason]
[23:24] -ChanServ- AKICK channel DEL mask
[23:24] -ChanServ- AKICK channel LIST [mask | list]
[23:24] -ChanServ- AKICK channel VIEW [mask | list]
[23:24] -ChanServ- AKICK channel ENFORCE
[23:24] -ChanServ- AKICK channel COUNT
[23:24] -ChanServ-
[23:24] -ChanServ- Maintains the AutoKick list for a channel. If a user
[23:24] -ChanServ- on the AutoKick list attempts to join the channel,
[23:24] -ChanServ- ChanServ will ban that user from the channel, then kick
[23:24] -ChanServ- the user.
[23:24] -ChanServ-
[23:24] -ChanServ- The AKICK ADD command adds the given nick or usermask
[23:24] -ChanServ- to the AutoKick list. If a reason is given with
[23:24] -ChanServ- the command, that reason will be used when the user is
[23:24] -ChanServ- kicked; if not, the default reason is "You have been
[23:24] -ChanServ- banned from the channel".
[23:24] -ChanServ-
[23:24] -ChanServ- The AKICK DEL command removes the given nick or mask
[23:24] -ChanServ- from the AutoKick list. It does not, however, remove any
[23:24] -ChanServ- bans placed by an AutoKick; those must be removed
[23:24] -ChanServ- manually.
[23:24] -ChanServ-
[23:24] -ChanServ- The AKICK LIST command displays the AutoKick list, or
[23:24] -ChanServ- optionally only those AutoKick entries which match the
[23:24] -ChanServ- given mask. AKICK VIEW simply shows more details.
[23:24] -ChanServ-
[23:24] -ChanServ- The AKICK ENFORCE command causes ChanServ to enforce the
[23:24] -ChanServ- current AKICK list by removing those users who match an
[23:24] -ChanServ- AKICK mask.
[23:24] -ChanServ-
[23:24] -ChanServ- The AKICK COUNT command returns how many entries there
[23:24] -ChanServ- are on the AutoKick list.

your menu still has one too many } m8

well i fixed it and all, and thanks for the input Cheiron and PunkTured :}

hmmm mabey that can work, but Kait did work on the top half of the snippet, and when i tested it out, it still worked, but now that you talk about it, i might add a clear option on the akick, that is if there is a way to clear that nick w/o clearing the akick list hmmmmmm, oh well most likely not so i wont mess with it then. but ya the akick protection was all me :D

edit on that...

menu nicklist {
  .akick
  ..addakick: /cs akick $chan add $$1 | .notice $$1 You got pwned! | msg $chan HAHA that was fun now wasn't it
}
on *:kick:#: {
  if ($me isop $chan) {
    cs clear $chan akick
    cs invite $me
    cs ban $nick $address
    cs akick $nick
    msg $chan haha that was fun now was it
  }
}

you could i think... maybe include the cs clear etc all on the single line with the | seperator.... have a play

how can it work with 2 bracket mismatches?

and you have a "if" statement but no event for it to go in :-s

try playing with this

menu nicklist {
  .akick
  ..addakick:/cs akick $chan add $$1 | /notice $$1 You got pwned! | /msg $chan HAHA that was fun now wasn't it
}
on *:kick:#: {
  if ($me isop $chan) {
    /cs clear $chan akick
    /cs invite $me 
    /cs ban $nick $address
    /cs akick $nick 
    /msg room haha that was fun now was it
  }
}

the code can be cleaned up simply enough. lose the / prefix on the chanserv command. they are not needed.. make the /notice into .notice (silences the command as the /notice is noisy and messy)... same with the /msg $chan ... that can be a simple msg $chan

as for the last line you have /msg room <--- that is an illegal statement. you need to use a channel identifier in this case .. use $chan again

also you have brackets mismatch..