Antinuke

Impose restrictions on moderators to prevent destructive behavior.

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 lets your server stay safe from any harmful actions.

How does the antinuke work?

The antinuke will set 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 feature.

Allowing users to configure the antinuke

Initially, only the server owner can configure the antinuke. However, you can allow other users to configure the antinuke with the antinuke admin command.

This is a dangerous command and will allow the user to entirely alter the antinuke configuration.

Syntax

.antinuke admin (user)

Exempting users from 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.

Syntax

.antinuke whitelist (user)

Enabling an antinuke module

Available flags

The following flags can be used to define the antinuke module

Threshold

The threshold is the number of actions a moderator can perform before being punished.

It’s recommended to keep the threshold between 1 and 6 to stay safe.

Syntax

--threshold (number)

Punishment

The punishment which will be applied to the moderator.

Available punishments can be found in the punishments section.

Syntax

--do (punishment)

Threshold

Whether drown commands should be counted towards the threshold. (e.g. ,ban)

Syntax

--command (on | off)

Available Modules

Punishing members for changing the vanity URL

You can prevent members from changing the vanity URL with the following command

drown can not change the vanity URL back to the original due to discord limitations

Syntax

.antinuke set vanity (on or off) [--do (punishment)]

Preventing bots from being added

You can prevent bots from being mass added with the following command

You’ll need to use antinuke whitelist (bot ID) to invite bots.

Syntax

.antinuke set botadd (on or off)

Prevent members from being banned

You can prevent members from being mass banned with the following command

It’s recommended to include the --command on flag.

Syntax

.antinuke set ban (on or off) [--threshold (number)] [--do (punishment)] [--command (on | off)]

Preventing members from being kicked

You can prevent members from being mass kicked with the following command

It’s recommended to include the --command on flag.

Syntax

.antinuke set kick (on or off) [--threshold (number)] [--do (punishment)] [--command (on | off)]

Preventing roles from being deleted

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

It’s recommended to include the --command on flag.

Syntax

.antinuke set role (on or off) [--threshold (number)] [--do (punishment)] [--command (on | off)]

Preventing channels from being created or deleted

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

Syntax

.antinuke set channel (on or off) [--threshold (number)] [--do (punishment)]

Prevent emojis from being deleted

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

Syntax

.antinuke set emoji (on or off) [--threshold (number)] [--do (punishment)]

Preventing webhooks from being created

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

Syntax

.antinuke set webhook (on or off) [--threshold (number)] [--do (punishment)]

Preventing members from being pruned

You can prevent members from being mass pruned with the following command

Syntax

.antinuke set prune (on or off) [--do (punishment)]

Disabling an antinuke module

You can disable an antinuke module with the same command you used to enable it, but with the status set to off.

Viewing the antinuke configuration

You can use the antinuke config command to view the current antinuke configuration.

Enabling and disabling the antinuke system

You can enable or disable the antinuke system using antinuke enable or antinuke disable.

Protection Role

The protection role feature creates a role called drown protection with administrator permissions and assigns it to the bot as a backup permission layer. This ensures the bot always retains its permissions even if someone attempts to strip them.

Do not delete the drown protection role manually. The bot will automatically recreate and reassign it. The role is defended autonomously — if it is deleted, has its permissions removed, or is taken away from the bot, it will be immediately restored.

You can enable or disable the protection role using the antinuke protectionrole command (alias: protrole).

Syntax

.antinuke protectionrole (on or off)

When enabling, the bot will prompt you to confirm before creating the role. On approval, it will:

• Create the drown protection role with administrator permissions
• Assign the role to itself
• Position the role just below its highest role in the hierarchy

To disable, the bot will remove the role entirely and stop defending it.

The protection role panel is also accessible from the interactive antinuke config panel via the Protection Role button.

Viewing the modules & whitelist

You can use the antinuke list command to view the enabled modules and whitelisted users.

Viewing users with antinuke admin

You can use the antinuke admins command to view users which can configure the antinuke.

Permissions available for antinuke permissions (grant or remove)

Antinuke Permissions

• administrator
• ban_members
• mention_everyone
• kick_members
• moderate_members
• manage_guild
• manage_channels
• manage_roles
• view_audit_log
• manage_webhooks
• manage_expressions
• manage_nicknames