Recently, I was flooded with a great deal of DCC chat and send requests, all bogus, and I noticed that they all take control of the window. Not only does the chat not allow you to kill them all, you have to continually hit enter/click "no" just to get rid of them.

With a few hundred of the bots doing this, I figured it might be a bit of a problem. I turned off all forms of DCC, but I don't think this is a viable solution. What I suggest is to not have a dialog open whenever a chat or send request occurs, but to just open a window that has a list of all DCC send/chat requests (or even the chats and sends themselves) and have an option to accept, cancel, resume, etc., sends and to accept or cancel the chats -- xchat-style.

It'd not only help when I'm flooded (though it just takes a lot of time, and the freezing of mIRC, to stop the flood (one still responds to PING requests)), but it'd be a bit easier to follow.

I agree. I thought of this exploit last night and was going to test it out.

Perhaps there could be an option added to mIRC's basic flood protection as well. (ex: If 10 DCC sends/chat requests occur within a 5 second timeframe, no DCC sends appear for 10 seconds).

This is possible with mirc script's .. But i can' catch the privmsg ..

catch the privmsg? DCC is a ctcp so you have to use a ctcp event to catch it.

I agree with BoredNL. It should be build in to mIRC's flood protection even though it is easily scripted.

Put this code in remote (alt+r) - If 5 DCC sends/chat requests in 5 secs then all dccs will be ignored for 2 minutes ..
Ctcp *:dcc*:?: hinc -mu $+ $iif($hget(DccProt, DccProt).unset = 0,5,$hget(DccProt, DccProt).unset) DccProt DccProt | if ($hget(DccProt, DccProt) >= 5) { ignore -tdu120 *!*@* | echo -s 4Some one flood you ! }