Security and automatic protection
Security modules are powerful. Configure a private staff log channel, test each rule, and keep a recovery plan before enabling destructive responses.
Auto-moderation — /automod
| Command | Purpose |
|---|---|
/automod setup [rule_type] [enabled] | Configures an automatic moderation rule. |
/automod toggle [rule_type] [enabled] | Enables or disables a rule. |
/automod list | Lists configured rules. |
/automod setup-muted-role [role] | Uses an existing muted role or creates the configured one. |
Rules can cover spam, links, words, caps, emojis, attachments, and toxicity depending on the server configuration. Keep the bot role above the muted role and verify that the log destination is accessible.
Anti-raid — /raid
| Command | Purpose |
|---|---|
/raid setup [enabled] [min_account_age] [max_joins_per_minute] | Configures account age and join-rate thresholds. |
/raid mode [enabled] | Turns emergency raid mode on or off. |
/raid verification-setup [role] [channel] | Configures the verification role and channel. |
Raid mode can kick new joins while it is active. Announce a verification path and review the thresholds after every large event so normal growth is not mistaken for an attack.
Anti-nuke — /antinuke
| Command | Purpose |
|---|---|
/antinuke backup | Creates a server backup. |
/antinuke restore | Restores from the latest available backup. |
/antinuke whitelist [user] [action] | Adds or removes a user from the whitelist. |
/antinuke status | Shows protection, rate-limit, whitelist, and backup status. |
/antinuke enable [enabled] | Enables or disables anti-nuke protection. |
Backups are a recovery aid, not a replacement for Discord ownership security. Keep trusted accounts to a minimum and review the whitelist after staff changes.
Shared global bans
The global-ban commands synchronize a server's participation in Nakine's shared ban system. Use the dashboard or /global-ban-config, /global-ban-list, and /global-ban commands to review policy, list entries, and apply an allowed action. Make the scope explicit before enabling automatic enforcement.
Start with logs or a narrow rule set. A permissive whitelist, a role-hierarchy mistake, or an aggressive join threshold can make a protection system ineffective or disruptive.