Skip to main content

​
Overview

Even trusted moderators can go rogue, get compromised, or make mistakes at scale. misery’s antinuke 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 someone can take within a short window. Cross that limit, and misery punishes them automatically, undoes what it can, and logs it to your antinuke channel.
The window is a rolling 60 seconds — every new action keeps it open, so slowing down doesn’t reset the count.

​
Setting it up

Pair antinuke with fake permissions so your moderators never hold the real permissions that make mass damage possible.

​
Giving others access to configure the antinuke

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

​
Co-owners

Co-owners get server-owner-level access across misery — antinuke, fake permissions, the bot’s profile, and more.
Syntax
Example
Server owner only. Running it again revokes co-owner access.

​
Whitelisting trusted users

Need someone to bypass antinuke entirely?
Syntax
Example
Whitelisted users skip antinuke checks completely — they won’t be punished no matter what they do. Running the command again removes them.

​
Choosing where alerts go

Syntax
Example

​
Turning on protection modules

​
Flags you can tune

Threshold

How many actions can happen before misery steps in. Someone is punished on the action that reaches it.
Keeping this between 1 and 6 is usually the safest range.
Syntax
Example

Punishment

What happens once someone crosses the threshold: ban, kick, or stripstaff.stripstaff removes their staff roles, fake-permission roles, and every role carrying a dangerous permission — useful when you’d rather investigate than ban.
Syntax
Example

Command tracking

Decide whether misery’s own moderation commands (like ,ban) also count toward the threshold.
Syntax
Example

​
Protection modules

Mass bans

Stop someone from banning large numbers of members in a short burst.
$command on is recommended so misery’s own ,ban counts too.
Syntax
Example

Mass kicks

Stop someone from kicking a large batch of members quickly.
Syntax
Example

Channel creation and deletion

Prevent mass creation or deletion of channels.
Syntax
Example

Role creation and deletion

Stop a wave of role creations and deletions from wiping out your role structure. $command on also counts ,role create.
Syntax
Example

Webhook creation

Block a flood of new webhooks, often used to spam pings.
Syntax
Example

Emojis

Stop mass emoji creation and deletion.
Syntax
Example

Stickers

Stop mass sticker creation and deletion.
Syntax
Example

Bot additions

Kick any bot added without approval, and punish whoever added it.
To let a specific bot in, allow it first with ,antinuke allow (bot id).
Syntax
Example

Vanity URL changes

Punish anyone who changes your server’s vanity invite.
misery can’t set a vanity back once it’s been changed, so this module only punishes the user.
Syntax
Example
To disable a module, run the same command with off — for example ,antinuke ban off.

​
Watching dangerous permissions

misery can punish anyone who grants (or removes) a dangerous permission on a role.
Syntax
Example
,antinuke permissions list shows everything being watched.

​
Blacklisted roles

Mark up to 5 roles that only the server owner and co-owners may hand out. Anyone else who gives one — by hand or with ,role — is banned.
Syntax
Example
Adding and removing blacklisted roles is server owner only.

​
Checking your configuration

​
Starting over

,antinuke reset wipes the whole antinuke configuration. Server owner only.