/antinuke settings
Overview
/antinuke settings opens an interactive dashboard that protects your server from compromised staff accounts or malicious bots performing mass destructive actions, such as bans, channel deletions, or role changes.
Required Permissions
- Administrator
Subcommands
settings
No options. Running the command opens a dashboard with five pages: Overview, Limits, Punishment, Allowlist, and Other.
Dashboard settings
The dashboard is split into five pages: Overview, Limits, Punishment, Allowlist, and Other.
Overview page
A master toggle turns anti-nuke on or off. Below it, toggles control which action types BetterAntiSpam tracks at all, grouped into three categories: server actions (profile changes, prunes, AutoMod, community settings, unverified bot additions, webhook edits), content actions (invite creation and deletion, emoji, sticker, and soundboard changes, message deletes and bulk deletes, message pins, stage and thread creation), and member actions (onboarding, scheduled events, application command permissions, mutes, deafens, voice moves, member updates).
Limits page
Every tracked action type has its own threshold: how many times that action can happen (by the same person, in a short window) before BetterAntiSpam treats it as a nuke attempt. Select an action from the list to set its limit (1–999). Notable defaults:
| Action | Default limit |
|---|---|
| Bans | 5 |
| Kicks | 5 |
| Bot additions | 1 |
| Channel create or delete | 3 |
| Role create or delete | 3 |
| Webhook create | 3 |
| Vanity URL change | 1 |
| Role permission escalation | 1 |
| Admin permission grant | 1 |
| AutoMod rule change | 1 |
| Voice mute, deafen, or drag | 3 |
Other tracked actions (invite create/delete, emoji, sticker, soundboard, message delete/bulk-delete/pin, stage, thread, onboarding, scheduled events, application command permissions, unban, community mode, member update, server profile, prune, invite pause, DM pause, server tag, integration changes) default to a limit of 1.
Punishment page
Choose what happens to an account that crosses a threshold: quarantine (default, strips roles and applies a quarantine role), kick, or ban. A separate set of toggles controls which action categories actually trigger punishment versus only being logged.
If quarantine is selected, choose the role to apply. BetterAntiSpam creates the role automatically if it doesn't already exist.
Allowlist page
Add trusted users or roles that bypass all anti-nuke checks. Use this for staff and trusted bots that legitimately perform bulk actions.
Other page
- Toggle whether the server owner is DMed when anti-nuke triggers (default on).
- Add extra users or roles to alert alongside the owner.
- Edit the list of "raid phrases" BetterAntiSpam watches for in nicknames and statuses after a nuke (default:
nuked by,pwned,raid by,beamed,wizzed), and the hit count and time window that trigger a response (default 5 within 60 seconds). - Toggle owner-only lock: when on, only the server owner can change any anti-nuke setting.
Behavior
- On first use, BetterAntiSpam enables anti-nuke automatically and defaults punishment to quarantine.
- Per-page Reset buttons restore that page's settings to default. A full Reset all is also available, with a confirmation step.
- Alert users and roles are shared with
/antiraid settings. The quarantine role is shared with/antispam settingsand/antiraid settings. Changing these in one dashboard changes them everywhere. - Only the admin who opened the dashboard can interact with it, unless owner-only lock is on, which restricts changes to the server owner.