Moderation & safety

Discord anti-nuke bot that stops the attacker, not your whole server

A nuke takes seconds: a compromised admin or a rogue bot deletes channels, bans half the server and floods webhooks. BotGG’s anti-nuke counts destructive actions per account, stops the one who is doing them and undoes what it can — while everyone else keeps chatting.

  • Works on the Free plan
  • 16 slash commands
  • Set up in the web console
mod-alertsDiscord preview

BotGGBOTToday at 20:14

@Admins

☢️ Possible nuke detected
4 channels deleted within 30 s.
Done by @Rogue (rogue.admin).
Response
• They were quarantined (roles removed, Quarantine role added).
Reverted
✅ 2 webhooks deleted.
Auto-restore
Recreating the deleted channels / roles from the latest backup…
↩️Restore roles

BotGGBOTToday at 20:16

♻️ Anti-nuke auto-restore
Recreated 4 channel(s) and 0 role(s).
From the backup taken October 2, 2026 4:00 AM.
The alert BotGG posts when one account starts deleting channels

What you get

Knows who did it

With View Audit Log every deletion, ban, kick, unban and webhook change is counted for the account that made it, within a time window you set.

Instant triggers

A role gaining Administrator or Ban Members, a dangerous role handed out, an unauthorized bot added, the server name or vanity URL changed — acted on at once.

Quarantine, not chaos

Default response: every role BotGG can remove is taken away and a no-permissions Quarantine role added. The roles are stored, so a “Restore roles” button gives them back.

Reverts the damage

Webhooks they created are deleted, dangerous permissions removed, dangerous roles taken back, bots they added kicked and the old server name put back.

Restore from a backup

On every plan, deleted channels and roles are recreated from your newest backup taken before the attack, then a restore report is posted.

No loophole through the bot

Bans and kicks someone makes through BotGG commands or the console count for that person too, so a compromised mod can’t nuke via /ban.

How it works

  1. Turn on Moderation and check permissions

    Enable Moderation in the BotGG console. BotGG’s invite already asks for View Audit Log — the Protection tab warns you if it is missing and offers a re-invite link.

  2. Configure anti-nuke

    On Protection → Anti-nuke set the time window and a threshold per action (0 turns one off), pick the response — quarantine, strip roles, kick, ban or alert only — and add trusted users and roles.

  3. Prepare the safety net

    BotGG creates the Quarantine role and takes a safety snapshot when you first enable anti-nuke. Turn on auto-restore (free on every plan) and keep Backups running.

  4. Respond from Discord

    When a nuke starts, your alert channel gets the trigger, the executor and what was done. Restore roles with one click, or hit /panic to lock everything down.

What the anti-nuke watches

Each counter is per executor and per time window, so a moderator banning two spammers is fine, while one account deleting several channels in a few seconds is not. Instant triggers fire on the first occurrence by anyone who isn’t trusted. The owner and BotGG are always trusted; trusted roles only count once they have been held for ten minutes, and handing someone a trusted role is itself a trigger.

If the attacker’s top role is above BotGG’s, the bot can’t touch them — the alert says so and tells your team to act now. That is why the console suggests keeping BotGG’s role near the top. Step-by-step hardening tips are in the Discord anti-nuke guide.

  • Thresholds: channel deletes and creates, role deletes and creates, bans, kicks, unbans, webhooks, emoji and sticker deletions.
  • Responses: quarantine (default), strip roles with an optional 24-hour timeout, kick, ban, or alert only.
  • A bot that nukes is kicked instead of quarantined — its power is its managed role.
  • Every incident lands in the console’s incident log with “Restore roles” and “Undo”.

Without the audit log, and when you need a panic button

Without View Audit Log BotGG can’t see who did what, so it falls back to counting channel deletions, role deletions and bans across the whole server and only alerts. Grant the permission to get per-user protection.

/panic start locks every writable channel, pauses invites for 24 hours through Discord’s incident actions and can quarantine one member; with Verification enabled, newcomers also have to solve its captcha. /panic end puts everything back. Anti-nuke is part of Moderation and works alongside anti-raid mode.

Slash commands

Generated from the bot’s real command definitions. Full list on the commands page.

/banuserreason?delete_messages?duration?evidence?Ban a user — add a duration for a temporary ban
/caseView, edit or delete a moderation case3 subcommands
  • /case viewnumberShow a case
  • /case editnumberreasonevidence?Change a case's reason (and add evidence links)
  • /case deletenumberDelete a case
/kickmemberreason?evidence?Kick a member from the server
/lockchannel?reason?Lock a channel: members can no longer send messages
/lockdownLock the whole server down during a raid2 subcommands
  • /lockdown startreason?duration?Start a lockdown now
  • /lockdown endEnd the lockdown and restore the channels
/modlogmemberA member's moderation history
/notemembertextAdd a private moderator note to a member
/panicPanic button: lock the whole server right now2 subcommands
  • /panic startquarantine?Lock every channel, pause invites and optionally quarantine a member
  • /panic endEnd the panic: unlock channels and resume invites
/purgecountuser?contains?bots?reason?Bulk-delete recent messages in this channel
/slowmodedurationchannel?Set or turn off slowmode in a channel
/softbanmemberreason?delete_messages?Ban and immediately unban to wipe a member's recent messages
/timeoutmemberdurationreason?evidence?Time out a member for a while (e.g. 10m, 2h, 1d)
/unbanuser_idreason?Unban a user
/unlockchannel?reason?Unlock a locked channel
/untimeoutmemberreason?Remove a member's timeout
/warnmemberreason?evidence?Warn a member (counts toward automatic escalation)

Commands

Frequently asked questions

What is a Discord nuke?

A nuke is when someone with too many permissions — often a hacked admin account or a malicious bot — deletes channels and roles, bans members or spams webhooks within seconds to wreck a server. An anti-nuke bot detects that burst and stops the account behind it.

How do I protect my Discord server from being nuked?

Give admin permissions to as few people as possible, keep BotGG’s role above staff roles, grant View Audit Log, enable anti-nuke with the quarantine response and keep regular backups. The anti-nuke guide walks through every step.

Will anti-nuke punish my own admins?

Only if they cross a threshold. Add them as trusted users or give them a trusted role and they are never acted on; the server owner and BotGG are always trusted. A quarantined member gets every role back with “Restore roles”.

Can BotGG bring back deleted channels?

Yes, on every plan: auto-restore recreates deleted channels and roles, including the permission overwrites that pointed at deleted roles, from the newest backup taken before the attack. You can also restore manually from Backups.

What permissions does anti-nuke need?

View Audit Log to see who did what, Manage Roles to quarantine, Kick or Ban Members for those responses, Manage Webhooks to delete webhooks (not in the default invite — the alert tells you when it is missing) and Manage Server to put the server name back.

Does it react to bans made through BotGG itself?

Yes. Kicks, bans, softbans and unbans someone makes through BotGG commands, the console or appeal approvals are counted for that person with the same thresholds, so a compromised moderator can’t use the bot to nuke.

Ready to level up your server?

Add BotGG for free, then switch features on in the web console.