AntiNuke Modules
Every watcher you can turn on, what triggers it, and how to set its threshold.
AntiNuke Modules
Each module is switched on with the same shape:
,antinuke <module> on --do <punishment> --threshold <number>--do is required and must be ban, kick, stripstaff or kickstripstaff. --threshold is optional and must be between 1 and 25. Leave it out and you get 3 actions. Order of the two flags does not matter, but both values have to sit right after their flag.
To switch a module off again:
,antinuke <module> offRun ,antinuke list at any time to see what is on.
Everything here can only be changed by the server owner or an AntiNuke admin.
Example
A moderator bans four people in a row during a raid wave. That is under the ten second window, so nothing happens:
,antinuke ban on --do stripstaff --threshold 5Now five bans inside the window strip the attacker's roles, unban the four members, revert anything else they touched, and post an alert.
The countable modules
These watch how often something happens inside the detection window.
| Command word | Triggers on |
|---|---|
ban | Members being banned |
kick | Members being kicked |
role | Roles being deleted |
rolecreate | Roles being created |
channel | Channels being created or deleted |
emoji | Emoji being deleted |
webhook | Webhooks being created |
invite | Invites being deleted |
Set each one separately, because the sensible threshold differs:
,antinuke channel on --do ban --threshold 4
,antinuke role on --do ban --threshold 3
,antinuke webhook on --do stripstaff --threshold 2
,antinuke invite offThe instant modules
These punish on the first action. There is no threshold to set, because one is already the maximum you should tolerate.
| Command word | Triggers on |
|---|---|
botadd | Any new bot joining the server |
prune | A bulk member prune from the settings page |
vanity | The server's custom invite link being changed |
guild | The server being renamed. rename works too |
,antinuke botadd on --do ban
,antinuke prune on --do stripstaff
,antinuke vanity on --do ban
,antinuke guild on --do kickA channel named #bot-invites where members suggest bots will trip botadd the moment one joins, so whitelist any bot you invite on purpose with ,antinuke whitelist <bot name or id>.
What each one does when it fires
The punishment runs, every recorded action is undone where possible, and an alert goes to your log channel with the member, the module, the action count and how many things were reverted. See What bore can undo for the limits.
Afterwards, that user's further damage is silently reverted for two minutes without a second punishment, so a slow attacker does not keep firing your alerts.
Choosing thresholds
| Situation | Suggestion |
|---|---|
| Small server, few active staff | Threshold 3, stripstaff |
| Large server with a busy mod team | Threshold 5 to 8, stripstaff, so a legitimate sweep does not trip it |
| You want attackers gone | ban or kickstripstaff |
| You cannot afford false positives | Longer window, ,antinuke window 60, with a higher threshold |
Run ,antinuke settings after changing anything to confirm what is actually live.
Last updated November 4, 2026