Advertisement

 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
    		•   

    Dcc Flood Protection
    Written by DeviL

    Currently, mIRC categorizes Dcc's together with ctcp's for ignore so basically a ctcp flood protection could also do the same thing as this. If users decide to dcc chat or dcc send flood you, mIRC will kick in and block those dcc's which can get annoying. The code goes into mIRC Remotes. 

    ctcp *:dcc *:*: {
  if ($2 == send || $2 == chat) {
    if (%dccs. [ $+ [ $wildsite ] ] == $null) {
      set -u8 %dccs. [ $+ [ $wildsite ] ] 1
      return
    }
    else { inc %dccs. [ $+ [ $wildsite ] ] }
    if (%dccs. [ $+ [ $wildsite ] ] > 3) {
      .ignore -tu45 $wildsite
      echo -a Dcc Flood from $wildsite - Ignoring ctcp from $wildsite for 45 seconds...
    }
  }
}

    The code above simple checks for dcc sends and chats. If mIRC detects more than 3 dcc's from the same address within 8 seconds, mIRC auto ignore's that host for 45 seconds. Basically, it could be ctcp flood protction as well. Below each line is explained... 

    ctcp *:dcc *:*: {
; Listens to ctcp's beginning with 'dcc'
  if ($2 == send || $2 == chat) {
  ; Checks if the 2nd parameter of the ctcp matches send/chat...
    if (%dccs. [ $+ [ $wildsite ] ] == $null) {
    ; Checks host's variable for dcc records...
      set -u8 %dccs. [ $+ [ $wildsite ] ] 1
      return
      ; If the host has no record, mIRC creates it
    }
    else { inc %dccs. [ $+ [ $wildsite ] ] }
    ; If the user's record exists, mIRC increases the amount by one
    if (%dccs. [ $+ [ $wildsite ] ] > 3) {
      ; When/If stats go beyond 3, mIRC kicks in
      .ignore -tu45 $wildsite
      echo -a Dcc Flood from $wildsite - Ignoring ctcp from $wildsite for 45 seconds...
      ; Ignore ctcps from host and let's you know...      
    }
  }
}