Skip to main content
This recipe takes approximately 5 minutes to complete.

​
Overview

A Discord server can be destroyed in seconds by a compromised admin account or a coordinated raid. Flare is built from the ground up to prevent this. By following this recipe, you will configure a “fortress” setup using Flare’s AntiNuke, AutoMod, and Logging systems.

​
Requirements

Critical Step: Flare MUST have its role placed at the very top of your server’s role hierarchy. Flare cannot punish or stop an attacker if the attacker has a role higher than Flare.

​
Step 1: Enable AntiNuke

AntiNuke is your primary defense against rogue admins. It detects mass-bans, channel deletions, and role tampering, instantly banning the perpetrator and attempting to recover the deleted assets.
  1. Navigate to the AntiNuke module on your dashboard.
  2. Toggle the module to Enabled.
  3. Set the default punishment to Ban.
  4. Adjust the thresholds (e.g., 3 bans within 10 seconds triggers the nuke protocol).

​
Step 2: Configure AutoMod (Raid Protection)

Raids usually involve bot accounts flooding your server with spam, links, or mass mentions. Flare’s AutoMod stops them before they even hit the chat.
1

Enable Anti-Spam

Blocks users sending messages too rapidly.
2

Enable Anti-Link & Anti-Invite

Prevents malicious phishing links and unauthorized server advertising.
3

Set AutoMod Punishment

Set a secondary punishment for repeat offenders. If someone triggers AutoMod 3 times, they should be timed out.

​
Step 3: Whitelist Trusted Bots

If you use other bots for server backups or moderation (like Dyno or Wick), AntiNuke might accidentally trigger on them during legitimate operations.
You generally do not need to whitelist human administrators. Only whitelist service bots that perform bulk actions.

​
Best Practices

Audit Roles Regularly

Never give “Administrator” to roles that don’t need it. Use granular permissions instead.

Enable 2FA

Force all server moderators to enable Two-Factor Authentication in Discord Server Settings.

​
Troubleshooting

This happens when Flare’s role is below the attacker’s role in the Discord Server Settings. Go to Server Settings > Roles, and drag Flare’s integration role to the absolute top.
When running server backups or cloning channels, Flare sees this as a nuke. You must whitelist your backup bot using /antinuke whitelist add @Bot before running the backup.

​
Next Steps

Now that your server is protected, you need a way to see what’s happening. 👉 Continue to Setup Complete Logging.