Skip to main content
Server protection is split into four systems that don’t overlap. They solve genuinely different problems, and turning on the wrong one for your threat means you’re still exposed.

Antinuke

Stops staff and compromised admins mass-deleting channels, roles or members. Reverts what it can, punishes whoever did it.

Antiraid

Stops outsiders — join floods, brand-new accounts, spam waves, mention spam.

Automod

Blocks message content — banned words, links, invites, mention counts — using Discord’s native AutoMod.

Honeypot

Catches compromised accounts with a bait channel, then fingerprints their scam images and blocks them server-wide.

​
Which do I need?

Antinuke. It’s the only layer that watches people who already have permissions. Set thresholds on ban, kick, channel, role, webhook and emoji, turn on antinuke bot so nobody can sneak an app in, and whitelist only the handful of people who genuinely do bulk work.
Antiraid, specifically massjoin and newaccount. Both pause invites for a set duration when they trigger, which is what actually stops a raid rather than cleaning up after one. Add automation if the raiders are using selfbots.
Honeypot plus automod links. The honeypot catches compromised accounts before they reach a real channel; the link filter handles everything else.Then turn on honeypot scan on. It perceptually fingerprints every scam image it sees and blocks that image across the whole server — surviving re-compression, cropping and recolouring, so a campaign that rotates its wording gets caught by the graphic it keeps reusing. !honeypot blacklist add on a reply adds anything that slips through.
Automod — the word filter, invite filter, and mention limits. Discord enforces these itself, so they apply instantly with no bot round-trip. Pair it with warn thresholds so repeat offenders escalate on their own.
Fake permissions. Grant a role the ability to use ban through mira without giving it Discord’s Ban Members permission. If they lose access to the bot, they lose the ability entirely.
Copy-pasteable. Adjust the thresholds to your server’s size.
Before turning any of this on, whitelist yourself and your most senior admin. Antinuke will happily ban the server owner’s alt if it trips a threshold, and getting locked out of your own server is a bad afternoon.

​
How they interact

They run independently and can all fire on the same event — which is fine, because each is checking something different. A raider who joins during a mass-join wave, posts a scam link and mass-mentions in one message will trip antiraid, automod and the honeypot at once. Whichever punishment lands first sticks. The one thing to watch: if antiraid’s punishment is ban and antinuke’s ban threshold is low, mass-banning raiders can look like a nuke. mira’s own actions are exempt from its antinuke, so this doesn’t actually happen — but if you have another bot doing the banning, whitelist it.

​
Checking your setup

Each shows what’s enabled, the thresholds, the punishment, and who’s exempt. !configuration gives you a shorter overview across every module at once.

​
What to do during an attack

1

Pause invites

Stops new accounts arriving while you deal with the ones already inside. Discord also disables DMs from server members for the duration.
2

Lock the server

Every channel goes read-only. !unlockdown all when it’s over — it only unlocks what it locked, so channels that were already private stay private.
3

Clean up

4

Undo the damage

If antinuke caught it, its alert message has a restore button that recreates deleted roles and channels with their original permissions and members. Otherwise:
5

Resolve the state

Lifts the automatic invite pause and channel locks that antiraid applied.