Showing antinuke · All commands · VoiceMaster guide
;antinuke admin
Grant or revoke someone's ability to edit antinuke settings. Deliberately owner-only, even existing antinuke admins can't grant this to anyone else, so a single compromised admin account can't recruit allies through the system meant to stop it.
Example
;antinuke admin <add|remove> @user;antinuke admins
List everyone currently able to edit antinuke settings.
Example
;antinuke admins;antinuke ban / kick / channel / role / webhook / emoji
Each protects against a burst of that specific destructive action from one actor within a short window, mass bans, mass kicks, channel creates/deletes, role deletes, webhook creates, or emoji deletes. Each has its own independent punishment via --do, not a shared global setting. Emoji deletion may miss some of a very fast burst since Discord's own audit log for emoji actions is known to be rate-limit-flaky.
Example
;antinuke ban on --threshold 2 --do ban;antinuke botadd
Blocks new bots from joining unless specifically whitelisted, removes them immediately on join. No configurable punishment, the action is always "remove the bot."
Example
;antinuke botadd <on|off>;antinuke config
View current antinuke settings, every module's status, its own punishment and threshold, and the permission watch-list. Bare `;antinuke` shows the same thing.
Example
;antinuke config;antinuke enable / disable
Master switch, every individual module still needs to be turned on separately even once this is enabled.
Example
;antinuke <enable|disable>;antinuke list
Shows the current antinuke admins and everyone/every bot whitelisted.
Example
;antinuke list;antinuke permissions
Watch a specific dangerous permission, with its own punishment via --do. Covers two separate things from the same watch-list: a role's own permissions gaining/losing a watched flag triggers that permission's configured punishment on whoever did it (first occurrence, no threshold, same as vanity); a member RECEIVING a role that already carries a watched permission instead just DMs the real server owner and every antinuke admin, that one's always a notification only, regardless of --do, nobody gets punished automatically for it. Omitting --do stops watching that permission entirely.
Example
;antinuke permissions grant administrator --do ban;antinuke staffrole
Bind (or unbind) the role that the stripstaff punishment actually removes. stripstaff will fail with a clear error until at least one role is bound here, it deliberately doesn't fall back to stripping everything instead.
Example
;antinuke staffrole add @Staff;antinuke vanity
Punishes anyone who changes the server's vanity URL, triggers on the first change, not a burst, since a single vanity hijack is itself the violation.
Example
;antinuke vanity on --do ban;antinuke whitelist
Exempt a member or bot from every antinuke module permanently. A whitelisted bot also bypasses the botadd block, not just the other modules.
Example
;antinuke whitelist bot add @TrustedBot