> ## Documentation Index
> Fetch the complete documentation index at: https://docs.zynrax.site/llms.txt
> Use this file to discover all available pages before exploring further.
# Antinuke
> Protect your server from nuking attacks.
## Why Use an AntiNuke System ?
Having a rock-solid AntiNuke system in place is absolutely essential for any serious Discord server. Moderators with elevated permissions can pose a hidden threat — and without proper protection, a single bad actor can bring your entire server crashing down in seconds. Zynrax's AntiNuke system acts as the last line of defense, keeping your server safe from permission abuse, destructive actions, and internal betrayal — so your community stays intact no matter what.
## How Does Zynrax's AntiNuke Work ?
Zynrax's AntiNuke system works by enforcing strict action limits on every moderator within a set time frame. The moment anyone — trusted or not — exceeds those limits, Zynrax detects it instantly and jumps into action, swiftly punishing the offender before any real damage can be done. Fast, intelligent, and completely unbypassable — Zynrax makes sure no one ever gets the chance to abuse their power.
## Configuring the antinuke
Discord recently introduced a mass ban feature capable of banning 200+ members in one go. It is highly recommended to create a blank role with zero permissions, place it below Zynrax's created recovery role, and assign it to everyone on the server. Keep all admin and elevated permission roles below this role — creating a protective wall that prevents any moderator from abusing this devastating 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 `extraowner set` command.
This is a dangerous command and will allow the user to entirely alter the antinuke configuration.
```bash Syntax theme={null}
,extraowner set (user)
```
```bash Example theme={null}
,extraowner set @Montage
```
## Exempting users from the antinuke
You can exempt users from the antinuke with the `whitelist add` command.
This is a dangerous command and will allow the user to bypass the antinuke entirely.
```bash Syntax theme={null}
,whitelist add (user)
```
```bash Example theme={null}
,whitelist add @Montage
```
## Enabling an Anti-Nuke Module
### Available Flags
The following flags can be used to define the Anti-Nuke module.
Set a strict daily limit on the number of actions a moderator can perform. Once that limit is hit within the day, Zynrax instantly steps in and takes action — no second chances.
It's recommended to keep the threshold between `5` and `10` to stay safe.
```bash Syntax theme={null}
,antilimit (event) (limit)
```
```bash Example 1 theme={null}
,antilimit ban 5
```
```bash Example 2 theme={null}
,antilimit chdl 3
```
### Shortcut Variables
Use these shorthands in the `(event)` field for faster configuration.
| Shortcut | Event | Shortcut | Event |
| :------------ | :------------------------ | :------- | :------------------------ |
| `ban` | Anti Ban | `unban` | Anti Unban |
| `kick` | Anti Kick | `prune` | Anti Prune |
| `botadd` | Anti Bot Add | `chcr` | Anti Channel Create |
| `chdl` | Anti Channel Delete | `chup` | Anti Channel Update |
| `rlcr` | Anti Role Create | `rldl` | Anti Role Delete |
| `rlup` | Anti Role Update | `memup` | Anti Member Update |
| `serverup` | Anti Server Update | `meneve` | Anti Everyone/Here |
| `emocr` | Anti Emoji/Sticker Create | `emodl` | Anti Emoji/Sticker Delete |
| `emoup` | Anti Emoji/Sticker Update | `rlping` | Anti Role Ping |
| `integration` | Anti Integration | `webcr` | Anti Webhook Create |
| `webdl` | Anti Webhook Delete | `webup` | Anti Webhook Update |
Define the consequence for anyone who exceeds the threshold — from stripping roles to an instant ban. Zynrax handles it swiftly and decisively.
```bash Syntax theme={null}
,antipunish (event) (punishment)
```
```bash Example 1 theme={null}
,antipunish prune ban
```
```bash Example 2 theme={null}
,antipunish chdl kick
```
### Punishment Types
Specify how you'd like Zynrax to handle violators.
| Type | Description |
| :----- | :------------------------------------------------------------- |
| `ban` | Permanently prevents the violator from re-entering the server. |
| `kick` | Instantly removes the violator from the server. |
Zynrax's intelligent command detection ensures total security. Before any command is executed, our system performs a comprehensive check on the user's **role hierarchy** and **required permissions**, neutralizing any unauthorized activity before it can even begin.
## Available Modules
Monitors and punishes unauthorized changes to your server's custom vanity URL.
Prevents unauthorized or malicious bots from being invited to your server.
Monitors all ban and unban actions to ensure no one is masspurging your community or releasing known bad actors.
* **Anti Ban**: Detects and blocks unauthorized or excessive banning.
* **Anti Unban**: Stops unauthorized unbanning of restricted accounts.
Protects your server population from unauthorized mass-removals.
* **Anti Kick**: Blocks unauthorized or mass-kicking of members.
* **Anti Prune**: Stops unauthorized member pruning attempts.
Shields your server structure by preventing unauthorized channel wipes or layout changes.
* **Anti Channel Create**: Prevents unauthorized new channels.
* **Anti Channel Delete**: Blocks unauthorized channel deletions.
* **Anti Channel Update**: Stops unauthorized changes to names, perms, or topics.
Protects your role hierarchy and critical server permissions from tampering.
* **Anti Role Create**: Stops unauthorized creation of new roles.
* **Anti Role Delete**: Prevents critical role deletions.
* **Anti Role Update**: Blocks unauthorized changes to role permissions or colors.
Protects both individual member profiles and core server settings.
* **Anti Member Update**: Monitors and stops unauthorized nickname or role changes.
* **Anti Server Update**: Prevents unauthorized changes to server names, icons, and regions.
Protects your server's visual identity and expression tools.
* **Anti Emoji Create/Delete/Update**: Full protection for custom server emojis.
* **Anti Sticker Protection**: Shields custom stickers from unauthorized removal.
Blocks rogue webhooks that could be used for spamming or data leaks.
* **Anti Webhook Create**: Blocks unauthorized new webhooks.
* **Anti Webhook Delete**: Prevents authorized webhooks from being deleted.
* **Anti Webhook Update**: Blocks changes to existing webhook configurations.
Detects and blocks unauthorized @everyone or @here pings to prevent server disruption.
Monitors apps and external links to ensure no backdoors are created.
* **Anti Integration**: Stops unauthorized app integrations.
* **Anti Invite-Role**: Prevents role assignment via invite link metadata.
* **Anti Link-Role**: Blocks malicious linking of external roles.
## 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 `disable`.
## Viewing the antinuke configuration
You can use the `,anticonfig` command to view the current antinuke configuration.
```bash Syntax theme={null}
,anticonfig
```
```bash Example theme={null}
,anticonfig
```
## Viewing the Whitelist Users
You can use the `whitelist show` command to view the whitelisted users.
```bash Syntax theme={null}
,whitelist show
```
```bash Example theme={null}
,whitelist show
```
## Unwhitelisting users from the antinuke
You can remove users from the antinuke whitelist with the `whitelist remove` command.
```bash Syntax theme={null}
,whitelist remove (user)
```
```bash Example theme={null}
,whitelist remove @Montage
```
