Antinuke (server protection)

Antinuke is Antidote’s automated raid / griefing guard. You set how many sensitive actions someone may perform in a rolling time window; if they exceed it, the bot applies the punishment you chose (for example jail, strip dangerous roles, kick, or ban).

What you should configure first

1. Turn Antinuke on in the dashboard (or complete the in-Discord setup flow).
2. Confirm Antidote’s role is high enough in the role list to manage roles and apply your jail role (if you use jail).
3. Set jail channel and jail role under Moderation if you want the Jail punishment to work; otherwise the bot may fall back to strip roles when jail is not configured.

Where to open settings

• Run your server prefix then setup (aliases: setups, install) and choose Antinuke, or
• Run antinuke config / antinuke setup (aliases include an), or
• Use the dashboard Antinuke section for the full editor.

Protection modules

Each row is a separate counter per staff member (executor from the audit log), with its own threshold, punishment, and optional Cmd detection toggle.

Module	What it tracks (summary)
Vanity protection	Changes to the server vanity invite URL.
Deny bot joins	Bots being added to the server.
Ban protection	Member bans.
Kick protection	Member kicks (audit-driven).
Role deletion	Roles being deleted.
Channel creation / deletion	Channels being created or deleted (Antinuke uses the shared channel protection bucket for this).
Emoji deletion	Custom emojis removed.
Webhook creation	Webhooks being created.
Sticker deletion	Stickers removed.

Threshold presets (rolling window)

Presets are expressed as N actions inside a single rolling window (not “per calendar hour”). Pick stricter values for public servers and looser ones for small staff teams.

Preset (dashboard)	Meaning
Instant (first action)	The first qualifying action in the window can trigger the consequence (use with care).
3 actions / 5m	Up to 3 actions within 5 minutes.
5 actions / 10m	Up to 5 actions within 10 minutes (common default).
7 actions / 30m	Up to 7 actions within 30 minutes.
10 actions / 60m	Up to 10 actions within 60 minutes.
15 actions / 60m	Up to 15 actions within 60 minutes.
20 actions / 60m	Up to 20 actions within 60 minutes.

[!tip] Separate counters Hitting the limit on one module does not reset counts on other modules; each module has its own rolling list of recent actions.

Punishments

Punishment	What the bot does
Jail + strip	Removes high-risk permissions (see below), saves a role buffer where configured, then applies your jail role and moves the member toward your jail channel setup. If jail is not configured, stripping may still run.
Strip roles	Strips roles that grant dangerous permissions (Administrator, Ban Members, Kick Members, Manage Server, Manage Channels, Manage Roles, Manage Webhooks, Manage Expressions, Manage Messages, View Audit Log, and similar).
Ban	Bans the executor from the server.
Kick	Kicks the executor from the server.

Cmd detection (“Cmd detection” switch)

Per module, Cmd detection controls whether actions that the backend classifies as command-sourced (for example some slash / app-command moderation flows) are included in the same counters as normal audit-driven events.

• On — command-classified paths count toward thresholds (when the bot labels them that way).
• Off — those command-classified paths are ignored for Antinuke counting for that module.

Whitelists and trusted staff

• Super admins — Discord user IDs stored in Antinuke settings who can manage Antinuke and are treated as trusted for enforcement logic.
• Member whitelist — users who should not be punished by Antinuke.
• Role whitelist — optional; members with a whitelisted role can be skipped depending on configuration.

Use whitelists for known-good bots (logging bots, ticket bots) and owner-approved staff who routinely perform bulk actions.

Bot permissions (checklist)

Antinuke and jail workflows expect Antidote to have (at minimum) the permissions used in the setup validator, including:

• View Audit Log — attribute bans, kicks, deletes, and similar.
• Ban Members / Kick Members — apply those punishments.
• Manage Roles — strip dangerous roles and assign jail.
• Manage Channels — support channel-related protections and jail routing where applicable.
• Manage Webhooks — webhook protection.
• Manage Guild Expressions — emoji and sticker protections.
• Manage Server — some guild-level updates used in protections.

If Antidote is missing permissions, consequences may fail silently or log errors while the server remains exposed.

Clearing counters and inspecting status

• antinuke clear @user (and related helpers) clear cached Antinuke action timestamps for a member so they can “cool down” without changing settings.
• antinuke view @user shows how full the rolling counters are right now (based on live cache).

Counters are in-memory on the bot shard with a bounded lifetime; treat view/clear as operational tools, not a permanent audit trail.

Related

• Dashboard — full Antinuke editor, thresholds, punishments, whitelists.
• Moderation module — jail channel / role and role-buffer behaviour used by jail.
• Server logging — pair Antinuke with log channels so staff see who did what when a limit trips.