Flood

Flood protection attempts to prevent you from flooding a server with messages sent in response to requests from other users via CTCP or a script.

Flooding usually results in your being disconnected from IRC servers since they place a limit on how much information you can send at one time.

mIRC will count the number of bytes you send to a server, and will initiate a flood check if you exceed a certain maximum number of bytes.

Show status in active window

Displays the flood queue status a) when there is a new item in the queue, b) every 10 seconds, if the queue status changed, and c) when the queue becomes empty.

Trigger check after

This is the number of bytes at which mIRC should check if it might be flooding the server or not. Setting this greater than 500 bytes is not too helpful since that might be the maximum amount a server allows. The lower the number, the more sensitive mIRC will be, and the slower it will reply. Default 400.

Buffer size

The maximum number of lines mIRC will buffer.

Lines per user

The maximum number of messages a user can have in the buffer.

Ignore user for

How long to ignore a user who has exceeded their maximum number of buffered messages. If zero, no ignore is done.

Limit...

This enables flood protection for CTCP replies, whois requests, and query windows.

Queue Op commands

If this is enabled, the MODE and KICK commands are also queued in the flood queue.

Queue own messages

If this is enabled, all of your own messages, such as notice and private messages, are queued in the flood queue.

The /flood command

This command allows you to turn flood protection on or off and to change the above settings. Typing /flood with no parameters gives you the current flood status. You can type /flood on to turn flood protection on with the default settings.

/flood [+c|-c] [on|off|clear] <bytes> <maxlines> <maxmessages> <ignoretime>

/flood 200 10 2 30

Here mIRC will check for flooding if it has sent 200 or more characters to the server, will buffer a maximum of 10 lines and ignore the rest, will only allow each user 2 buffered lines, and will ignore a user for 30 seconds if that user exceeded the maximum number of buffered messages.

You can also use +c or -c to enable or disable the ctcp flood protection.

The flood protection method also performs intelligent queuing in order to satisfy the maximum number of users as quickly as possible, so that no single user can hog the queue.