> For the complete documentation index, see [llms.txt](https://discortics.com/llms.txt). A consolidated single-file corpus is available at [llms-full.txt](https://discortics.com/llms-full.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://discortics.com/guides/anti-nuke.md).

# Anti-Nuke

Anti-Nuke watches for destructive actions, including bot additions, emoji deletions, pruning, role and channel changes, and dangerous permission grants. Other bots are monitored too.

## Before you begin

- Only the **server owner** and **AntiNuke admin roles** can manage it.
- Discortics needs **Administrator**, and its role must be above every other role.
- Set a modlog channel with `/settings moderation`.

## Set up Anti-Nuke

### Dashboard Setup

1. Open **Dashboard → Moderator → AntiNuke**.
2. Give Discortics **Administrator** and move its role to the top.
3. Set a modlog channel under **Moderator → General**.
4. Review **Protections**. Each has its own limits, punishment, and recovery options.
5. Enable **Status**, then select **Save**.

### Discord Command Setup

1. Run `/autopilot antinuke` or `;antinuke`.
2. Fix any permission or role-position checks, then set the modlog with `/settings moderation`.
3. Review **Protections** and use **Manage** to edit a rule.
4. Select **Enable**.

Customise a protection in one line:

`;antinuke ban on --at 3/min --at 10/hour --punish strip --recover on`

Turn on bot additions and emoji deletions with `;antinuke bot-add on` and `;antinuke emoji-delete on`.

## Limits and punishments

Limits apply per account. The action that reaches a limit triggers the punishment.

| Punishment          | What it does                                                                                                               |
| ------------------- | -------------------------------------------------------------------------------------------------------------------------- |
| **Strip**           | Removes roles. Can't remove integration roles, `@everyone`, or direct channel permissions. Use Kick or Ban if those remain |
| **Timeout + Strip** | Times out the account and removes roles                                                                                    |
| **Kick**            | Removes the account from the server                                                                                        |
| **Soft ban**        | Bans, deletes the last 24 hours of messages, then unbans                                                                   |
| **Ban**             | Bans the account                                                                                                           |

**Mixed Actions** counts every action together across enabled protections. The defaults are 8 actions in 10 minutes and 15 actions in 1 hour.

## Whitelist and admin roles

- **Whitelist** exempts a person or bot from one or all protections, temporarily or until removed. It doesn't give setup access.
- **Allowed bot additions** lets a bot join. Its later actions are still monitored.
- **Admin roles** let up to three roles manage AntiNuke. Each needs **Manage Server** or **Administrator**, and they're whitelisted by default.

Command permissions can't give access to AntiNuke.

## What gets recovered

Recovery is best effort. Review the results with `/cases`.

| Recovered                                              | Not recovered                                              |
| ------------------------------------------------------ | ---------------------------------------------------------- |
| Channels, categories, roles, and emojis (with new IDs) | Deleted messages and role memberships                      |
| Saved role and channel positions                       | Vanity changes, kicked or pruned members, deleted webhooks |

Accounts at or above Discortics are logged but can't be punished, because of Discord's role hierarchy.

## Panic mode

Panic mode locks the server during a coordinated attack. It's **off by default**.

- **Turn it on:** enable **Automatic panic mode** in **Overview**, or use **Panic** under Protections in Discord.
- **What triggers it:** 3 different accounts breaking configured limits within a minute or an hour. You can change the account count.
- **How long it lasts:** 1 hour by default, from 1 minute to 24 hours. Repeated events don't extend it.

During panic, Discortics removes risky permissions from editable roles and channel overrides, including those of whitelisted staff. Commands, buttons, and Dashboard actions pause for everyone except the server owner.

The owner can select **End panic and restore permissions** at any time. Permissions restore automatically when the lock ends. Recent grants and conflicting edits stay for the owner to review. Held members aren't released and their punishments aren't undone.

> [!WARNING]
> Panic can't cover everything. Discord restrictions, existing webhooks, and actions already accepted can leave gaps. Check the coverage and issues it shows.

## Limitations

- Discord reports actions after they happen, so detection can't prevent the first action.
- Anti-Nuke turns itself off if Discortics loses **Administrator** or server access. Fix the cause and turn it on again as the server owner.
- Reduce your risk by removing native Discord permissions from staff and giving them Discortics command permissions instead.