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> off

Run ,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 5

Now 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 wordTriggers on
banMembers being banned
kickMembers being kicked
roleRoles being deleted
rolecreateRoles being created
channelChannels being created or deleted
emojiEmoji being deleted
webhookWebhooks being created
inviteInvites 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 off

The instant modules

These punish on the first action. There is no threshold to set, because one is already the maximum you should tolerate.

Command wordTriggers on
botaddAny new bot joining the server
pruneA bulk member prune from the settings page
vanityThe server's custom invite link being changed
guildThe 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 kick

A 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

SituationSuggestion
Small server, few active staffThreshold 3, stripstaff
Large server with a busy mod teamThreshold 5 to 8, stripstaff, so a legitimate sweep does not trip it
You want attackers goneban or kickstripstaff
You cannot afford false positivesLonger 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