Anti-Nuke
Automatically rate-limits destructive staff actions (mass channel/role deletion, mass bans/kicks, webhook spam) and quarantines whoever tripped it before real damage is done.
What is Anti-Nuke?
Anti-Nuke watches for bursts of destructive actions - channel/role deletions, bans, kicks, webhook creations, admin role grants, and server-setting changes - performed by anyone with the permissions to do them, including staff and compromised accounts. If someone exceeds the threshold for an action within its time window, they're quarantined: timed out and stripped of their roles.
Quarantine self-heals - if someone manages to reverse it (regain roles, get un-timed-out), Pixie re-applies it automatically and alerts staff.
Setup
$antinukeThe first time you run this, it walks you through: a sensitivity preset (Strict / Normal / Loose / Custom), whether you use a ticket bot to exclude from channel-monitoring, any trusted roles that should be fully immune, and a channel for anti-nuke alerts. Every step can be skipped and revisited later from the panel (Redo Setup Walkthrough).
Sensitivity presets
| Preset | Best for |
|---|---|
| Strict | Smaller or high-security servers - trips fastest |
| Normal | Most servers - balanced default |
| Loose | Larger servers with frequent admin activity |
| Custom | Set your own count/window per action type |
Alerts channel
Anti-Nuke has its own dedicated alerts channel (set during first-run setup, or anytime via the panel's Alerts Channel button) - separate from the general event logger, so quarantine/bypass alerts always have somewhere to go even if you haven't configured logging at all.
Who can manage it
By default, only the real server owner can change Anti-Nuke settings. The owner can add other trusted staff as managers:
$antinuke addmanager @user
$antinuke removemanager @user
$antinuke managersTrusted roles/users & exceptions
Trusted roles/users are fully immune to Anti-Nuke entirely. Exceptions are narrower - immune to just one specific action type (e.g. exclude a ticket bot from channel-create/delete monitoring only, so it can keep working normally).
Releasing a quarantine
$antinukerelease @userRestores their original roles and lifts the timeout. Use this once you've confirmed it was a false positive or the situation is resolved.