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 this 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.
,antinuke admin(user)
,antinuke admin@hazard
h
hazardToday at 7:37 PM
,antinuke admin @hazardsalt
drown APPToday at 7:37 PM
✓@hazard: hazardsalt is now an antinuke admin and can edit antinuke settings
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.
,antinuke whitelist(user)
,antinuke whitelist@hazardsalt
Enabling an antinuke module
Available Flags
The following flags can be used to define the antinuke module
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.
--threshold(number)
--threshold3
The punishment which will be applied to the moderator.
Available punishments can be found in the punishments section.
--do(punishment)
--doban
Whether drown commands should be counted towards the threshold. (e.g. ,ban)
--command(on | off)
--commandon
You can prevent members from being mass banned with the following command
It's recommended to include the --command on flag.
,antinuke set ban(on or off)[--threshold(number)][--do(punishment)][--command(on|off)]
,antinuke set banon--threshold 3 --do ban --command on
h
hazardToday at 2:05 PM
.antinuke set ban on --threshold 3 --do ban --command on
drown APPToday at 2:05 PM
✓@hazard: Updated ban antinuke module. Punishment is set to ban, threshold is set to 3 and command detection is on
You can prevent members from being mass kicked with the following command
It's recommended to include the --command on flag.
.antinuke set kick(on or off)[--threshold(number)][--do(punishment)][--command(on|off)]
.antinuke set kickon--threshold 3 --do ban --command on
You can prevent roles from being mass deleted with the following command
It's recommended to include the --command on flag.
.antinuke set role(on or off)[--threshold(number)][--do(punishment)][--command(on|off)]
.antinuke set roleon--threshold 3 --do ban --command on
h
hazardToday at 2:13 PM
,antinuke set role on --threshold 3 --do ban --command on
drown APPToday at 2:13 PM
✓@hazard: Updated role antinuke module. Punishment is set to ban, threshold is set to 3 and command detection is on
You can prevent channels from being mass created or deleted with the following command
.antinuke set channel(on or off)[--threshold(number)][--do(punishment)]
.antinuke set channelon--threshold 3 --do ban
You can prevent emojis from being mass deleted with the following command
.antinuke set emoji(on or off)[--threshold(number)][--do(punishment)]
.antinuke set emojion--threshold 3 --do ban
h
hazardToday at 2:13 PM
.antinuke set emoji on --threshold 3 --do ban
drown APPToday at 2:13 PM
✓@hazard: Enabled emoji antinuke module. Punishment is set to ban and threshold is set to 3
You can prevent webhooks from being mass created with the following command
.antinuke set webhook(on or off)[--threshold(number)][--do(punishment)]
.antinuke set webhookon--threshold 1 --do ban
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.
.antinuke set vanity(on or off)[--do(punishment)]
.antinuke set vanityon--do ban
h
hazardToday at 2:14 PM
.antinuke set vanity on --do ban
drown APPToday at 2:14 PM
✓@hazard: Enabled vanity antinuke module. Punishment is set to ban.
You can prevent bots from being mass added with the following command
You'll need to use antinuke whitelist (bot ID) to invite bots.
.antinuke set botadd(on or off)
.antinuke set botaddon
h
hazardToday at 2:17 PM
.antinuke set botadd on
drown APPToday at 2:17 PM
✓@hazard: Enabled botadd antinuke module
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.
h
hazardToday at 2:21 PM
.antinuke config
drown APPToday at 2:21 PM
e
hazard
Settings
Antinuke is enabled in this server
Modules
General
Mass Member Kick: ✓
Super Admins: 3
Webhook Creation: ✓
Whitelisted Bots: 18
Emoji Deletion: ✓
Whitelisted Members: 2
Mass Member Ban: ✓
Protection Modules: 8 enabled
Channel Creation/Deletion: ✓
Watch Permission Grant: 6/11
Role Deletion: ✓
Watch Permission Remove: 0/11
Vanity Protection: ✓
Deny Bot Joins: ✓
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.
Antinuke permissions
These are the permissions available for antinuke permissions (grant or remove). You can grant or remove these from trusted users to control what they are allowed to do.