@ a careful warchild: Unfortunately it's not my responsibility to make up scripts to fit in with other scripts. I can make it to use to my own advantage, which in fact, is /black for me.

@ Bullet_Dodger: With the coding available above, any user with the general knowledge of mIRC scripting should be able to piece together an alias for it; good luck.

@ Stapler: I'm not quite sure what the problem is there for you. I've tested it thoroughly and have not had any problems. I believe some of the other users have not had m/any problems with it. Be sure you pasted it in an empty mIRC file. If the problem persists, oh well, I guess you're out of luck.

I will not be updating this script any further. Any updates made will be mandatory updates that I find actually improve the usage of the script, and is not just another feature to get in the way.

I'm sorry if I seem a little blunt with my answers, but I've pretty much stopped mIRC scripting. I will make for-fun scripts every once-in-awhile or other "useful" scripts if I find something that I haven't already coded. I've covered just about all there is to make that can still be considered "useful."

Anyways, good luck with your personal updates to the code, and have fun!

• Akishoot

You must be an operator for it to kick. I didn't include half-ops in the coding. Feel free to add it yourself, however, it will not be added into the official code.

Bullet_Dodger: Check to make sure you do not have two 'on *:INPUT' scripts going at once.

I've noticed a few problems upon using a few of the new features. I'm in class right now trying to fix it, and I'll work on it when I get home, so I should have an updated, better working version later this evening.

Here's a couple of problems I found:
Double logging of kicks when having "Kick From All Common Channels" enabled
No logs recorded when adding a blacklist entry via the dialog

How to use: Right-click on a channel or status window, or go to your menubar and select "Backup Scripts".

Okay. I've figured out the problem I was having before. It's updated now. Read the introduction for details.

(P.S. Thanks again for showing that site to me Imrac; it helped quite a bit while making the introduction. ;)

No... The very first line of the actual coding. You're missing the on EVENT part...

if ($1- == !lockdown) {
    set %e 1 
    :fred
    set %chan $nick(#,%e,reg)
    if (%chan == $null) { 
      halt
    }
    elseif (%chan ison #) && (%chan == $me) { 
      inc %e
      goto fred
    }
    elseif (%chan isreg #) || (%chan isvoice #) || (%chan isop #) {
      kick # %chan 
      mode # +i
      mode # +s
      mode # +m
      inc %e
      goto fred
    }
  }
  if ($1- == !lockdown off) {
    /mode # -i
    /mode # -s
    /mode # -m
}

There goes another... 8D

Useful to me since later in the evenings I get pretty lazy, and its a great idea. :)

7/10

Haha. :P Looks like a fun bit of code. I'll test each of them later today. Seeing that it is 2:35 a.m. here, I'm gonna try and get some sleep first.

And yet another code has been Napa'd! ;D

Hehe, any feedback would be appreciated. Always looking to improve things. ;)

A few features have been added, including Escape-From-Hell's suggestion. Check the Introduction for details.

Thanks for the comments!

Your e-mail tells it all. Let's not talk in a snippet discussion about ourselves. I'll contact you on MSN sometime. I'm in the middle of class right now.

You could also replace the /'s in front of "/disable" and "/enable" with periods (.) to hide the notifications in the status window.

Oh my God, that's you Eternal? I had no clue.

It works great. 10/10. :)

Yes, but you only have it to check if they are an operator in the room. The operator may be a temporary operator so temporary operators could be adding themselves to the access list.

Thanks for the suggestion Escape-From-Hell! I will be adding that along with a few other small things in the next update. I'm at my school right now so I don't have the coding/program in front of me to do anything.

Yes, to be on the safe side, I'd make it "/msg ChanServ" instead of "/cs".

Also, having both methods of adding someone as an operator in the same script is not a good idea, seeing as ChanServ will yell at you.

Another thing, I'm not quite sure an operator can add another operator permanently.

The only problem I see with this is the fact that not all chatrooms use the XOp method... A majority of the rooms I'm in use the ACCESS method.

Thanks for the comments guys. Still updating it periodically.

• Not very useful but quite a neat effect.

9/10 - Nice work. :D

• Size of dialog could be greatly reduced.
• \'Nickname\'/\'Password\' edit fields could be alligned a bit neater.

Other than that, a fairly simple, but nice script.

Good work. :)

How to use: Right-click a user on the nicklist or add a user manually via the dialog. [size=10](To open the dialog, right-click on any channel or select it on your menubar.)[/size]

Eugenio: It\'s /google , not /googlesearch. ;)

It should be:

on *:TEXT:*shit*:#: { /kick # $nick you have been kicked by $me : profanity not allowed! }

Etc. etc...