Skip to main content

​
Why use an antinuke system?

An antinuke system helps protect your server from destructive actions performed by moderators/staff — whether intentionally, accidentally, or through a compromised account. It limits how many high‑impact actions someone can do within a short time window and automatically responds when that limit is exceeded.

​
How does this antinuke work?

This system is event + audit‑log + rate‑limit based.
  1. A server event happens (e.g. channel created, role deleted, member banned).
  2. The bot reads the Audit Log to determine who performed the action.
  3. The bot checks if the actor is bypassed (server owner / whitelisted).
  4. A rate limiter counts how many actions that actor performs within 10 seconds.
  5. If the actor exceeds the configured threshold, AntiNuke:
    • Logs an alert to your configured log channel (if enabled)
    • Punishes the actor (ban, kick, or stripstaff)
    • Reverts what it can (e.g. deletes newly‑created channels/roles, reverts permission escalation, removes dangerous roles, deletes mention spam)

​
What it can and cannot revert

Can revert:
  • Channel creation (deletes the created channel after trigger)
  • Role creation (deletes the created role after trigger)
  • Dangerous permission escalation on roles (reverts permissions back)
  • Dangerous roles granted to members (removes the dangerous roles)
  • Mention spam (deletes cached mention messages from the last 10 seconds)
  • Webhook abuse (deletes abusive webhooks if it has permission)
  • Bot adds (kicks unauthorized bots when triggered)
Cannot reliably revert:
  • Channel deletions (Discord does not provide a true restore)
  • Role deletions (same limitation)
AntiNuke will still punish and log the actor for deletions.

​
Requirements

​
Bot permissions (important)

AntiNuke relies heavily on audit logs and moderation permissions. Recommended permissions:
  • View Audit Log (required for most modules to function)
  • Ban Members (if you use ban punishment)
  • Kick Members (if you use kick punishment)
  • Manage Roles (required for stripstaff + reverting perms + removing dangerous roles)
  • Manage Channels (required to delete channels it created / clean up)
  • Manage Webhooks (required to remove abusive webhooks)
  • Read Message History (for mention spam deletion)
  • Manage Messages (helps with deleting mention messages)
If your bot does not have a required permission, that module may silently fail to punish/revert.

​
Quick setup

  1. Invite the bot with the permissions above.
  2. Enable Antinuke: .antinuke on
  3. Set a log channel: .antinuke logchannel #logs
  4. Add trusted Antinuke admins (optional): .antinuke admin @user
  5. Configure modules (recommended set below).
  6. Verify config: .antinuke configuration

​
Core commands

​
Enable AntiNuke (server owner only)

.antinuke on

​
Disable AntiNuke (server owner only)

This disables AntiNuke and resets the stored configuration. 
.antinuke off

​
Set the log channel (server owner only)

.antinuke logchannel (#channel)

​
Disable logging

.antinuke logchannel

​
Admins and bypassing

​
Allowing other users to configure AntiNuke (server owner only)

The server owner can toggle AntiNuke Admin on a member.
This is dangerous. AntiNuke Admins can alter protections and reduce thresholds.
.antinuke admin (user)

​
Viewing AntiNuke Admins (server owner only)

.antinuke admins

​
Whitelisting (bypass AntiNuke)

Whitelisted users do not trigger antinuke punishments.
Dangerous: this bypasses ALL modules.
.antinuke whitelist (user)

​
Unwhitelist

.antinuke unwhitelist (user)

​
View whitelisted users

.antinuke whitelisted

​
Enabling an antinuke module

Modules are configured per feature (ban/kick/channelcreation/etc). Each module is stored with:
  • status (on/off)
  • punishment (ban, kick, stripstaff)
  • threshold (1–12)
  • command (true/false) (stored; triggers are event/audit-log based)

​
Available Flags

Number of actions allowed in a 10 second window before AntiNuke triggers.
Recommended:
  • 1–2 for destructive actions (deletions, dangerous permissions)
  • 2–4 for creation spam (channels/roles)
  • 3–5 for mentions
--threshold (number)
Action taken against the actor when the module triggers.
Punishments:
  • ban
  • kick
  • stripstaff (removes staff roles the bot is allowed to remove)
--do (punishment)
Stored in configuration as command: true/false.
Triggers rely on server events + audit logs, not command parsing. Keep this enabled for consistency with your config schema.
--command (true | false)

​
Modules (exactly matching your bot)

Triggers when bans are detected and attributes the action using audit logs.
.antinuke ban (on or off) --threshold (number) --do (punishment) --command (true | false)
Triggers when kicks are detected and attributes the action using audit logs.
.antinuke kick (on or off) --threshold (number) --do (punishment) --command (true | false)
If triggered, it punishes the actor and deletes the created channel.
.antinuke channelcreation (on or off) --threshold (number) --do (punishment)
Punishes/logs on threshold.
Deleted channels cannot be automatically restored.
.antinuke channeldeletion (on or off) --threshold (number) --do (punishment)
Watches channel edits (name/permissions/settings) and punishes if abused.
.antinuke channelupdate (on or off) --threshold (number) --do (punishment)
If triggered, it punishes the actor and deletes the created role.
.antinuke rolecreation (on or off) --threshold (number) --do (punishment)
Punishes/logs on threshold.
Deleted roles cannot be automatically restored.
.antinuke roledeletion (on or off) --threshold (number) --do (punishment)
Watches role edits (name/permissions/settings) and punishes if abused. If dangerous permissions were added, it can revert the role permissions back.
.antinuke roleupdate (on or off) --threshold (number) --do (punishment)
Looks for webhook create/delete/update in audit logs. If triggered and the bot has Manage Webhooks, it deletes webhooks in that channel.
.antinuke webhooks (on or off) --threshold (number) --do (punishment)
Counts mentions per message:
  • @everyone/@here adds 5
  • user mentions add 1 each
  • role mentions add 1 each
When triggered, it deletes cached mention messages from the last 10 seconds and punishes/logs.
.antinuke mentions (on or off) --threshold (number) --do (punishment)
Covers two cases:
  1. Role permission escalation (reverts permissions back if dangerous perms were added)
  2. Dangerous roles granted to members (removes the dangerous roles)
.antinuke permissions (on or off) --threshold (number) --do (punishment)
Triggers when bots are added to the server. If triggered, it can kick the bot and punish the actor.
.antinuke botadd (on or off) --threshold (number) --do (punishment)
Triggers on emoji create/update/delete activity attributed via audit logs.
.antinuke emoji (on or off) --threshold (number) --do (punishment)
Triggers on sticker create/update/delete activity attributed via audit logs.
.antinuke sticker (on or off) --threshold (number) --do (punishment)

​
Viewing configuration

Shows AntiNuke enabled status + each module state and parameters. 
.antinuke configuration

​
Troubleshooting

​
Nothing triggers

  • Ensure the bot has View Audit Log
  • Ensure AntiNuke is enabled: .antinuke configuration
  • Ensure the specific module is enabled (shows ✅)
  • Ensure the bot’s role is high enough to punish/remove roles
  • Check your log channel is set properly

​
stripstaff doesn’t work

  • Bot must have Manage Roles
  • Bot’s highest role must be above the roles it is attempting to remove

​
mentions module doesn’t work

  • Ensure Message Content intent is enabled
  • Ensure the bot can read messages in the channels
  • Ensure the module is enabled: .antinuke mentions on ...

​
Dangerous permissions tracked in code

These permission keys are treated as “dangerous”:
Dangerous Permission Keys
administrator
manage_guild
manage_roles
manage_channels
manage_webhooks
ban_members
kick_members
mention_everyone
moderate_members
manage_nicknames