Anti-nuke ☢️

Automatic protection against a compromised or malicious admin tearing your server apart.

What it protects you from

A "nuke" is when someone with staff permissions — a hacked moderator account, a rogue bot, or a person you trusted too much — starts mass-banning members, deleting channels, or wiping roles. It happens fast: a script can destroy months of work in under a minute, usually while you're asleep.

Anti-nuke watches for that pattern. When one person performs too many destructive actions in too short a time, BMO steps in automatically — it can alert you, kick or ban the offender, or strip their roles so they lose their permissions instantly. You don't have to be online for any of it.

How detection works

Every time a watched event happens, BMO checks the server's audit log to find out who actually did it, then counts that action against them. Two settings control when it reacts:

• Cooldown window — how far back BMO looks, in seconds. Default: 15 seconds (allowed range 3–300).
• Overload threshold — how many watched actions by the same person inside that window trip the alarm. Default: 5 events (allowed range 2–30).

So with the defaults: five destructive actions by one person within 15 seconds triggers anti-nuke. A moderator deleting one channel or banning one troll never comes close — but a mass-ban script does instantly. After it fires, the same person won't be actioned again until a full cooldown window has passed, so you get one clear response instead of a pile of duplicates.

What counts as a watched event

These are the events anti-nuke tracks, each verified against the audit log:

One extra safeguard runs on every role edit, independent of the counters: if a role suddenly gains a dangerous permission — Administrator, Manage Server, Manage Roles, Manage Channels, Kick Members, Ban Members, Manage Webhooks, Manage Emojis & Stickers, or Mention Everyone — BMO posts a "Dangerous Role Permissions Added" alert to your log channel so you can review it, even if no threshold was crossed.

Turning it on

Dashboard (recommended): open your server on the dashboard and go to the Anti-nuke page (under the Safety group). Flip Enabled on and hit save — the defaults are sensible out of the box.

Command: /antinuke enable toggles it; /antinuke status shows the full current setup, including any missing bot permissions.

The four response actions

When the threshold is crossed, BMO performs whichever action you've picked. Whatever you choose, an alert is always posted to your log channel with who triggered it, which event tipped it over, the event count, and whether the action succeeded.

What strip does, exactly: BMO removes every role it can from the person — all their roles except @everyone, roles managed by integrations (bot roles, booster roles), and any role positioned at or above BMO's own role. It's not limited to "dangerous" roles: the offender is left with effectively no permissions, but they stay in the server and their case stays visible.

Who is never punished

Anti-nuke skips counting actions from people it should obviously trust:

• The server owner — always exempt.
• BMO itself — its own cleanup actions never count.
• Bots — if Ignore bots is on (it is by default). Turn it off if you want other bots watched too, but then whitelist the bots you trust, or your music bot's channel edits could trip the alarm.
• Whitelisted users — people you add explicitly.
• Whitelisted roles — anyone holding a role you've whitelisted.

Manage whitelists on the dashboard's Anti-nuke page (user IDs as a simple list, roles with a role picker), or by command: /antinuke wladd @user, /antinuke wlremove @user, and /antinuke wllist to review it.

DM notice

Optionally, BMO can send the offender a direct message when anti-nuke acts on them, telling them which server triggered it, what action was taken, and why (e.g. "5 actions in 15s"). It's off by default; bots are never DMed. Turn it on with DM offending user on the dashboard or /antinuke dm.

Where alerts go

Anti-nuke posts its alerts to the first channel it finds in this order:

1. The anti-nuke log channel, if you've set one (dashboard field or /antinuke logchannel #channel).
2. Otherwise, your server's audit log channel.
3. Otherwise, your server's general log channel.

Running /antinuke logchannel with no channel clears the override so BMO goes back to the fallback order.

The dashboard page

Everything above lives on one form: dashboard → your server → Anti-nuke (Safety group). The fields are:

• Enabled — the master switch.
• Cooldown window (seconds) — 3 to 300.
• Events to trigger — 2 to 30.
• Action — Notify, Kick, Ban, or Strip.
• Ignore bots — skip counting other bots' actions.
• DM offending user — send the notice described above.
• Log channel — channel picker; leave empty to use the fallback order.
• Whitelist user IDs — paste IDs separated by commas or new lines.
• Whitelist roles — pick trusted roles.

Command reference

All /antinuke commands require the Administrator permission and only work inside a server.

Recommended starter settings

Good to know

• Anti-nuke reacts to the pace of actions, not their content — a slow, careful attacker spacing actions out beyond your window won't trip it. Shorter windows with lower thresholds catch more, at a higher risk of flagging a busy admin doing a big cleanup.
• Doing a legitimate mass cleanup (deleting many channels or roles at once)? Temporarily whitelist yourself, or turn anti-nuke off and back on afterwards.
• Anti-nuke limits damage — it can't undo bans or restore deleted channels. Pair it with Member guard for protection at the door and jail for day-to-day moderation.