Protection on IRC

Many users need protection and channel management tools, here we supply everyone with the tools and knowledge you'll need to IRC safely and securely operate your channel. There are two sections, one for channel protection and the other for personal protection.

Channel Protection

  • Guest Nick Kicker
  • !list Kicker
  • Mass Clone Flood Protection
  • Mass Kick Protection
  • Repeat Flood Protection
  • Ban Protection
  • Long Text Kicker
  • Spam/Advertisement Kicker [Fixed]
  • Clone Protection
  • Revolving Door Kicker
  • Seen Script Kicker
  • Swear Kicker
  • Control Code Kicker
  • Excess Punctuation Kicker
  • Caps Kicker
  • Caps Kicker #2
  • Control Code Kicker #2
  • Repeat Kicker
  • Personal Protection

  • Ctcp Flood Protection
  • Dcc Flood Protection
  • Query Window Flood Protection
  • Notice Flood Protection
  • Internet/PC Protection

    !list Kicker
    !list Kicker
    Written by DeviL

    There's some people out there who have nothing better to do other than joining a channel, typing !list, then parting as fast as they can for no reason. Use this code to kick/ban and keep them out them as fast as you can for no reason. Code goes into mIRC Remotes. (Note: I don't recommend this script be used on a server channel, such as file serving and ftp's...etc)

    on @*:text:!list:#: {
      if ($nick !isop #) {
        ban # $nick 2
        kick # $nick This is not a file sharing channel!

    The code itself is pretty simple. You may copy/paste the code into remotes and use it as you wish. The code is explained below...

    on @*:text:!list:#: {
    ; Triggers when a user types !list on a channel you're op on
      if ($nick !isop #) {
        ; Checks if the user is an op
        ban # $nick 2
        kick # $nick This is not a file sharing channel!
        ; If the user isn't an op and typed !list, we kick!

    Now those annoying people will think twice before wasting their 10 seconds just to join a channel, type !list, and leave it. If you find any errors or have any questions, please contact us via email, memo, or on our script forum. Thank you for you time.