Antinuke rule options
Choose what each anti-nuke rule watches, its threshold, window and punishment, and the extra options such as revert.
Every rule is armed with the same flags. Start with Antinuke to set a log channel and whitelist your staff, then tune rules here. All of this is Server Owner only.
Choose what a rule watches
channel, role,
emote, botadd,
grantadmin and
removeadmin have their own subcommand. Every
other action goes through ,antinuke rule, with the same flags.
Syntax
,antinuke rule <action> <on|off> [++punish <p>] [++threshold <n>] [++window <s>]
Example
,antinuke rule webhook on ++punish ban ++threshold 3
| Action | Trips on | Threshold |
|---|---|---|
channel, channelcreate | a channel deleted, created | counted |
role, rolecreate | a role deleted, created | counted |
emote, sticker | an emote, a sticker deleted | counted |
ban, unban, kick | a member banned, unbanned, kicked | counted |
webhook, integration | created, changed, added, removed | counted |
guild | server settings changed | counted |
botadd | a bot added | first occurrence |
grantadmin, removeadmin | admin-shaped permissions granted, removed | first occurrence |
vanity | the vanity invite code changed | first occurrence |
First-occurrence actions take no threshold or window: there is no acceptable number of times to hand Administrator to a stranger.
Set the threshold, window and punishment
| Flag | Accepts | Default |
|---|---|---|
++punish | warn, timeout, stripstaff, kick, ban | ban (emote: stripstaff) |
++threshold | 1 to 50 | 3 |
++window | 5 to 300 seconds | 60 |
Each punishment needs a permission the bot actually holds.
| Punishment | Bot needs | Notes |
|---|---|---|
ban | Ban Members | |
kick | Kick Members | |
timeout | Moderate Members | One hour, reversible |
stripstaff | Manage Roles | Removes the roles on your ,staff list, so it must not be empty |
warn | nothing | Posts the incident, takes no action |
One punishment per person per 10 minutes
Someone who trips a rule is punished once, across every rule at once. A thirty-channel nuke gives one punishment and one incident. A second trip three minutes later is silent on purpose, so a quiet log is not a broken rule.
Turn on the extra options
Refused with a message on actions that do not support them.
| Flag | Applies to | Does |
|---|---|---|
++wide <on|off> | grantadmin, removeadmin | Also watches the permissions that usually come before Administrator (Ban, Kick, Moderate, Manage Server, Channels, Roles, Webhooks and a few more). Each rule has its own flag |
++countbot <on|off> | ban, kick, unban, grantadmin, removeadmin, role, rolecreate, channel, channelcreate | Counts an action a person ordered through the bot against them. Actions the bot performs are normally excused |
++revert <on|off> | channelcreate, rolecreate, ban, unban, grantadmin, removeadmin, guild, webhook, integration, botadd | Puts back what the triggering action changed, after the person is punished |
Syntax
,antinuke rule <action> <on|off> [++wide <on|off>] [++countbot <on|off>] [++revert <on|off>]
Example
,antinuke rule ban on ++punish ban ++countbot on
Two gaps countbot cannot cover
Discord's own bulk ban tool never touches this bot, so no rule sees it. Do not grant Ban Members, real
or fake, to anyone who should not have it. A mass prune is one audit entry however many members it
removes, so it adds one toward the kick threshold: at the default of 3 it will not trip alone.
Revert cannot undo a deletion
Deleted channels, roles, emotes and stickers are never recreated, and channel, role, emote and
sticker do not accept the flag. A kick cannot be undone either. A stolen vanity URL cannot be written
back by a bot: the incident prints your old code, so reclaim it in Server Settings → Vanity URL
before someone else takes it.
Revert never runs on a warn rule, or when the punishment itself was skipped. On botadd it is on by
default and removes the invited bot (++revert off keeps it). Re-arming ban always needs
++revert on stated again; every other action carries it forward.