Skip to main content

​
Overview

​
Why use an antinuke system?

It’s important to have an antinuke system in place to prevent moderators from abusing their permissions. This is a security measure which keeps your server safe from any harmful actions.

​
How does the antinuke work?

Antinuke sets a limit on the number of actions a moderator can perform in a certain time frame. If the limit is exceeded, the moderator will be punished and a message will be sent to the owner.

​
Configuring the antinuke

Discord recently implemented a new mass ban feature which can quickly ban 100+ members. It’s HIGHLY recommended to utilize fake permissions to prevent moderators from using this feature.

​
Configuring modules with the modal

Run /antinuke config to open the antinuke configuration modal. The modal shows which modules are enabled and lets you select a module to configure its settings. Use the matching commands in configuring with commands if you prefer to configure the antinuke with commands instead of the modal.
Antinuke configuration modal with the module selector open

The antinuke configuration modal shows enabled modules and lets you select a module to configure.

​
Managing antinuke admins

Initially, only the server owner can configure the antinuke. Use /antinuke admin add to allow another user to manage it.
This is a dangerous command and will allow the user to entirely alter the antinuke configuration.

To remove an antinuke admin, use /antinuke admin remove.

​
Exempting users from the antinuke

You can exempt users from the antinuke with the /antinuke whitelist command.
This is a dangerous command and will allow the user to bypass the antinuke entirely.

​
Configuring with commands

​
Watching permission changes

Use these commands to watch permission grants or removals, remove a permission from the watch list, or view the permissions currently watched. When a watched permission changes on a role, bleed reverts the change and reports who made it.
Use list to see which permissions are currently watched. Available permission values are:

​
Configuring modules

Set setting to On or Off. Thresholds define how many actions trigger the module, and punishment defines what happens when it is triggered. For modules that support command_detection, set it to True to include actions performed with bleed commands.
It’s recommended to keep thresholds between 1 and 6. Available punishments are listed in the punishments section.
You can prevent members from changing the vanity URL with the following command
bleed cannot revert the vanity URL due to Discord limitations.

You can prevent bots from being mass added with the following command
Add a bot to the whitelist with /antinuke whitelist add user:<bot>.

You can prevent members from being mass banned with the following command
Set command_detection to True to include bans performed with bleed commands.

You can prevent members from being mass kicked with the following command
Set command_detection to True to include kicks performed with bleed commands.

You can prevent roles from being mass deleted with the following command
Set command_detection to True to include role changes performed with bleed commands.

You can prevent channels from being mass created or deleted with the following command

You can prevent emojis from being mass deleted with the following command

You can prevent webhooks from being mass created with the following command