Anti-Nuke Protection

Squint's anti-nuke protection safeguards your server against malicious attacks that aim to destroy or disrupt your server. It detects and responds to rapid, destructive actions like mass channel/role deletions, mass bans, and malicious bot additions.

Quick Start (5 Minutes)

1. Run ;antinuke enable

2. Set punishment: ;antinuke punishment ban

3. Add trusted admins/bots to whitelist: ;antinuke whitelist add @TrustedUser

4. Check bot permissions: ;antinuke status

You're done! Read full setup below for advanced options.

Setup

1. Enable anti-nuke protection: ;antinuke enable

2. (Optional) Set co-owners who can manage settings: ;antinuke coowner add @Moderator

3. (Optional) Configure punishment type: ;antinuke punishment kick

4. (Optional) Toggle specific protection modules: ;antinuke toggle channels false

5. View current status: ;antinuke status

Configuration

• enabled: Toggles the entire anti-nuke system on or off.

• ownerId: The ID of the server owner (automatically set).

• coOwners: A list of user IDs who can also manage anti-nuke settings.

• whitelist: A list of user IDs who are exempt from anti-nuke checks.

• punishment: The action taken against detected nukers: ban, kick, or strip (removes all roles).

• permissionAlerts: Toggles alerts for when the bot lacks necessary permissions.

• protectionModules: A sub-object configuring individual protection types:

  • channels: Protects against mass channel deletion/creation.

  • roles: Protects against mass role deletion/creation.

  • kicks: Protects against mass member kicks.

  • bans: Protects against mass member bans.

  • webhooks: Protects against webhook abuse.

  • botAdd: Protects against malicious bot additions.

  • botPerms: Protects against bot permission escalation.

  • guildUpdate: Protects against server settings modification.

  • unverifiedBots: Kicks unverified bots upon joining. Each module has enabled (true/false), alertThreshold, and banThreshold.

• thresholds: A sub-object for general thresholds:

  • strikeLimit: The number of strikes a user can accumulate before a punishment is applied.

• whitelistBackupBots: Toggles automatic whitelisting of known backup bots.

Common Issues:

• Protection is not active → Ensure the bot's highest role is in the top 8 server roles and it has all required permissions (Manage Channels, Manage Roles, Ban Members, Kick Members, View Audit Log).

• Trusted admins are being punished → Add the trusted user's ID to the whitelist using ;antinuke whitelist add @user.

• Bot cannot revert changes → The bot must have a role higher than the user who performed the destructive action.

• Bot keeps leaving → Check the BlockNukeBotJoin.js handler for hardcoded banned IDs if the bot is leaving immediately after joining.

Usage

Once enabled, Anti-Nuke Protection actively monitors server events. If a user performs actions that exceed configured thresholds, Squint will intervene by applying the specified punishment and logging the incident. It also automatically bans known nuke bots and removes unverified bots.

Related Commands

• ;antinuke - Main command for managing anti-nuke settings.

• ;antiraid - Specific protection against profile picture raids.