Flood Protection inspects one message for excessive length, too many emoji, or repeated content. Use Spam Protection for rapid activity across several messages.
Set up flood protection
Configure from the DashboardStart near the defaults and adjust after reviewing real messages.
- Open Dashboard → Moderator → Autopilot → Anti-Flood.
- Enable the protection.
- Set the character, emoji, and duplicate sensitivity values.
- Add required exceptions.
- Choose a punishment.
- Save and test harmless examples.
[Insert screenshot here]
Flood protection limits in the Dashboard
Detection settings
Character Limit is the maximum message length before the message is treated as a text wall. Enter 250 to 4,000. The default is 1,500.
Emoji Limit is the maximum combined Unicode and custom emoji count. Enter 5 to 2,000. The default is 15.
Duplicate Sensitivity detects heavily repeated content inside one message. Enter 1 to 10. Higher values catch more repeated content and can create more false positives. The default is 3.
Exceptions
Ignored users, roles, and channels bypass Flood Protection.
What happens to a violation
The detected message is deleted, then the configured punishment policy runs. Start with Warn while checking whether normal long messages, art, code, or emoji-heavy announcements need an exception.
Troubleshooting
Normal long messages are removed
Raise the character limit or ignore the specific channel used for long posts. Avoid ignoring a broad staff role unless every member with that role is trusted.
Emoji art is removed
Raise the emoji limit or ignore the dedicated art channel. Keep the lower limit in general chat if emoji floods are still a problem there.