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
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.
.antinuke admin (user)Exempting users from the antinuke
You can exempt users from the antinuke with the antinuke whitelist command.
.antinuke whitelist (user)Enabling an antinuke module
You can enable an antinuke module with various flags to customize its behavior.
.antinuke (module) --threshold (number) --punishment (action)Available Flags
--threshold- Number of actions before punishment (default: 3)--punishment- Action to take (ban, kick, strip, jail)--duration- Time window for threshold (default: 60s)
Available Modules
ban- Monitor mass banskick- Monitor mass kickschannel- Monitor channel deletionsrole- Monitor role deletionswebhook- Monitor webhook creationsemoji- Monitor emoji deletionspermissions- Monitor dangerous permission grants
Disabling an antinuke module
.antinuke (module) offViewing the antinuke configuration
.antinuke settingsPermissions
The following permissions are available for antinuke configuration:
.antinuke admin grant (user)- Grant admin access.antinuke admin remove (user)- Remove admin access.antinuke whitelist add (user)- Add to whitelist.antinuke whitelist remove (user)- Remove from whitelist