Anti-nuke

The bot stops members who delete, ban or create too much in a short time, and undoes what they did.

How it works

The bot reads the server's audit log as it happens and counts, for each member, what they do within a number of seconds. When a member reaches a limit, they are stopped at once.

  • Deleted channels and roles (default 3).
  • Bans and kicks together (default 5).
  • Created channels and roles (default 10) and webhooks (default 3).

With Stop dangerous permissions at once a member is stopped the first time they give a role dangerous permissions or give someone a role with them, for example Administrator, Manage Server or ban. With Stop adding bots at once the same goes for adding a bot.

💡 Setting a limit to 0 turns it off.

When a member is stopped

  • By default the bot takes all the member's roles. You can pick kick or ban instead. A bot is always kicked.
  • With Undo what was done the bot recreates deleted channels and roles with their name, category and permissions, gives the roles back to their members, lifts bans, deletes what was created and takes dangerous permissions back.
  • For the next 10 minutes, everything the member does is undone at once.
  • The bot posts an alert in the Alert channel and optionally pings a role.
⚠️ Messages in a deleted channel cannot come back. The channel is recreated empty.

If it was a mistake, the owner or a trusted member can click Give roles back in the alert. The member gets their roles back, and the bot stops undoing their actions.

Trusted roles and members

The server owner and the bot itself are never stopped. Everyone else is, admins too, unless you make them trusted.

  1. 1Go to Trusted roles and members under Anti-nuke.
  2. 2Click the suggestions to add roles and members with Administrator, or pick a role or search for a member.
  3. 3Click Save.
💡 If you use another bot to ban many at once, make it trusted too.

Set it up

  1. 1Open Security in the menu under Server management and turn Anti-nuke on.
  2. 2Check the limits and Within seconds.
  3. 3Pick the Action and whether the bot should Undo what was done.
  4. 4Add your admins as trusted.
  5. 5Pick the Alert channel and optionally Role to ping, and click Save.
⚠️ The bot must be able to view the audit log and manage webhooks. If it lacks the permissions, the dashboard shows a banner with Grant permissions. The bot's own role must also be above the roles of the members it should be able to stop.

Still stuck? Ask on our Discord server or write to support@rimfrost.dk