Dcc Flood Protection
Written by Kintar0

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... } } }

If you find any errors or have any questions/comments, please contact us via email, memo, or our script forum. Thanks for your time.

2000-2001 ClanX Scripterz Organization