Skip to main content

​
Why use an antinuke system?

An antinuke system limits how many destructive actions a user can perform in a short time window. If the limit is exceeded, adore punishes the offender automatically - protecting your server from rogue moderators or compromised accounts.

​
How antinuke works

When you enable a protection module, adore watches for harmful actions in real time:
  1. Detection - adore listens to Discord audit logs (and message events for @everyone pings) to identify who performed each action
  2. Tracking - each user’s actions are counted in a rolling 1-minute window per module
  3. Threshold - if a user exceeds the configured limit within that window, adore triggers a punishment
  4. Punishment - the offender is automatically punished and their action counter resets

​
Punishment types

strip is the safest default - it neutralizes a rogue moderator without removing them from the server entirely.

​
What adore monitors

​
Who can configure antinuke?

Discord’s mass ban feature can ban 100+ members at once. Use fake permissions so moderators can only ban through adore, not native Discord.

​
Who is immune to antinuke?

These users will never trigger antinuke punishments:
  • Server owner (Discord owner)
  • Fake owner - your designated co-owner
  • Security admins - automatically immune
  • Whitelisted users - added via ,antinuke whitelist
Everyone else - including administrators and moderators with full Discord perms - is subject to antinuke if they exceed limits.

​
Exempting users

Add trusted bots or staff who need to perform bulk actions:
  • Running the command again toggles the user off the whitelist
  • View all whitelisted users with ,antinuke whitelists
  • The server owner cannot be whitelisted (already immune)

​
Enabling a protection module

Each module is toggled independently with on or off.

​
Available flags

Number of actions allowed per minute before punishment triggers. Range: 1–10. Default: 3.
Recommended: keep between 1 and 6 for sensitive modules like ban and permissions.
What happens when the limit is exceeded: strip, kick, or ban. Default: strip.

​
Available modules

Triggers when a member is banned (via Discord or adore).
Triggers when a member is kicked.
Triggers on role creation or deletion (both share the same limit).
Triggers on channel creation or deletion (both share the same limit).
Triggers on webhook creation or deletion.
Triggers when a user sends a message containing @everyone or @here.
Triggers when administrator or manage_guild is granted to a member via role update.
Run any module command without on/off to see its current status, limit, and punishment.

​
Viewing configuration

Shows all enabled modules with their limits and punishments, plus security admin and whitelist counts. For a typical server, start with:
Then set up fake permissions so staff can only moderate through adore.
Bot-add protection lives under antiraid, not antinuke.