Skip to main content

Overview

Even trusted moderators can go rogue, get compromised, or make mistakes at scale. Confine’s antinuke system watches for sudden bursts of destructive actions and steps in before real damage is done.

How it works

You set a limit on how many risky actions a moderator can take within a short window. Cross that limit, and confine automatically punishes them and pings the server owner.

Setting it up

Discord’s mass ban tool can wipe out 100+ members in seconds. Pair antinuke with fake permissions so moderators can’t touch it.

Giving others access to configure the antinuke

By default, only the owner can touch antinuke settings. To let someone else help manage it, use:
Anyone granted this can rewrite your entire antinuke setup — only give this to people you fully trust. You can run this command again to remove them from antinuke administrator.

Whitelisting trusted users

Need someone to bypass antinuke entirely (like a co-owner or bot)? Whitelist them:
Whitelisted users skip antinuke checks completely — they won’t be punished no matter what they do.
Screenshot 2026 08 01 165633

Turning on protection modules

Flags you can tune

How many actions can happen before confine steps in.
Keeping this between 1 and 6 is usually the safest range.
What happens to the moderator once they cross the threshold.
Decide if confine’s own moderation commands (like ,ban) should also count toward the threshold.

Protection modules

Catch and stop a moderator from banning large numbers of members in a short burst.
Turning on $command on is recommended so this also tracks confine’s own ban command.
Catch and stop a moderator from kicking a large batch of members quickly.
Turning on $command on is recommended so this also tracks confine’s own kick command.
Prevent mass creation or deletion of channels in a short window.
Stop a wave of role creations and deletions from wiping out your server’s role structure.
Turning on $command on is recommended for full coverage.
Block a flood of new webhooks from being set up, often used to spam ping or exploit channels.
Block a flood of new emojis from being deleted.
Block a flood of new sticker from being deleted.
Block large waves of bots from being added to your server at once.
To let a specific bot in, allow it first with antinuke allow (bot id).
Stop members from swapping out your server’s vanity invite.
Discord removed the ability for bots to change vanities therefore, confine cannot set the vanity back. However, I can punish the user.
To disable an antinuke module, run the same command you used to enable a module, just switch it to off.
Screenshot 2026 08 01 170447

Checking your configuration

Use ,antinuke config to see your current antinuke configuration at a glance.
Antinuke Config

Viewing all antinuke whitelisted users

Run ,antinuke whitelisted to view all whitelisted users.
Screenshot 2026 08 01 160932

Viewing module punishments and thresholds

Run ,antinuke view to check the punishment and threshold set for each module.
Screenshot 2026 08 01 165100

Viewing who has admin access

Run ,antinuke admins to see everyone who’s allowed to configure antinuke.
Screenshot 2026 08 01 165250