Skip to main content
Newt counts what each person does: bans, kicks, timeouts, deletes. When someone goes over a limit, Newt stops them before the next one lands. It’s on from the start for bans, kicks and timeouts, through Newt or in Discord.

Set it up

1

Check your mod roles on the Moderation tab

Your mods can act through Newt or Discord’s own menus, and Newt counts both. Through Newt is safest: the action that would go over a limit never happens. How
2

Move Newt's role to the top

Newt can’t stop anyone whose highest role sits above its own.
3

Pick a level

On the dashboard’s Anti-nuke tab, choose Relaxed, Balanced or Strict, or change any number to make your own.
4

Watch Discord itself

Optional. Tick Also watch bots, and channels, roles, webhooks and emojis to catch bad bots and anyone deleting channels or roles. Trust your ticket bot first.
Newt’s role must be the highest role in your server. Drag it to the top in Server Settings → Roles. The Health check on the Anti-nuke tab names any role above it.

The limits

Each cell is a minute / an hour. Going over either one stops them. Balanced is the default. A person’s bans, kicks and timeouts in Discord count from the start. A bot’s, and the Discord only rows, count once you turn on watching Discord itself. Your own numbers can be 1 to 50 a minute and 1 to 500 an hour.

When someone goes over

Through Newt, the action that would go over never happens. In Discord, it has already happened when Newt sees it, so Undo puts it back where Discord allows. A kick can’t be. Then:
  1. Their moderation through Newt is paused until you let them back.
  2. The punishment. Stop them (the default) takes away their roles with dangerous permissions and leaves the rest. Restrict, Kick or Ban go further. A bot is kicked, or banned.
  3. Undo (on by default) puts back what they did in the last hour: unbans, lifted timeouts and restrictions, deleted channels, roles and webhooks they made, and rebuilt channels and roles they deleted. Newt can only put back permissions it has itself, so without Administrator it can’t take Administrator off a role.
  4. Lock the whole server down (off by default) runs /lock server.
  5. An alert goes to your mod log channel, or another you pick, and to your DMs. It can ping roles. Picking a role that can’t be mentioned needs Mention Everyone.

Stopped at once

While watching Discord itself, these stop someone the first time. Each change is put back, and each check can be switched off.
  • Giving anyone a dangerous permission: Administrator, Manage Server, Manage Roles, Manage Channels, Manage Webhooks, Manage Messages, Ban, Kick or Timeout Members.
  • Changing the vanity link.
  • Pruning members.

Trusted admins

People and bots the anti-nuke never counts. They can also change who moderates and the anti-nuke on the dashboard. Only the server owner picks them, on the Anti-nuke tab or with /antinuke trust. Up to 25.

Commands

Lets a stopped moderator moderate again. Roles that were taken aren’t given back.
The settings, a health check, the trusted admins and who is stopped.
Owner only.

Good to know

  • Acting on someone who joined in the last day doesn’t count. That’s raid cleanup, not a nuke.
  • The server owner and Newt are never counted.
  • A stopped moderator can’t use any moderation command, even with Administrator.
  • For 10 minutes after they’re stopped, anything more they do in Discord is quietly undone too. With watching Discord itself off, that’s their bans and timeouts.
  • Counts last an hour. They’re saved, so a restart doesn’t reset them, and the 10 minutes after a stop carry on too.
  • Only the owner and trusted admins can change these settings, so a rogue admin can’t switch it off first.
  • Only the owner and trusted admins can lift a restriction the anti-nuke made.
Permission: The server owner and trusted admins. /antinuke trust and /antinuke untrust are the owner’s alone.