Antinuke
Protect your server against destructive staff actions with module-specific thresholds.
What is Antinuke?
Antinuke watches supported administrative actions, including bans, kicks, role changes, channels, webhooks, and bot additions. Each module has its own controls. It is separate from Antiraid, which deals with suspicious joins.
Review your configuration
Start by checking the enabled modules, thresholds, and trusted users. The server owner can apply the balanced preset with antinuke default setup, but should review the resulting configuration rather than assume it suits every server.
,antinuke configManaging Antinuke admins
Only the server owner can toggle another member’s ability to configure Antinuke. Inspect the current list before making changes. Grant this access only to staff you trust with the protection configuration.
,antinuke adminsWhitelisting users
antinuke whitelist toggles a user’s exemption. Being allowed to configure Antinuke and being exempt from it are different responsibilities. Review the whitelist and remove access that is no longer required.
Setting up modules
Expand a module in the command reference below to see its supported flags. Some accept a threshold from 1–6 and a punishment; others do not use a threshold. Command tracking is available only where the command lists --command. Use the exact syntax for the chosen module.
,help <command>