ShieldBot Initialization
Welcome to the official documentation for ShieldBot. This guide will walk you through the process of securing your Discord server using our enterprise-grade infrastructure. Zero complex configs, just pure security.
Pre-requisites
Before proceeding, ensure you have the Administrator permission in the Discord server you wish to protect.
Why ShieldBot?
Traditional bots rely on slow APIs. ShieldBot uses a private WebSocket bridge that reacts in 0ms to malicious events, making it impossible for nukers to cause damage.
Quick Integration
Adding ShieldBot to your server is handled via the secure Discord OAuth2 protocol. We only request the exact permissions needed to defend your server.
// Typical integration flow
1. Click the 'ADD ShieldBot' button.
2. Select your server from the dropdown.
3. Authorize the ShieldBot integration.
4. Move the ShieldBot role to the TOP of your role hierarchy.Hierarchy Warning
If the ShieldBot role is not placed at the very top of your server settings, it cannot ban malicious admins or delete nuked roles.
Anti-Nuke Setup
The Anti-Nuke engine monitors for massive changes in roles, channels, and member permissions. If an admin account is compromised, the Anti-Nuke will detect the rapid changes and instantly strip the compromised account of its permissions.
Owner Protection
The server owner is exempt from Anti-Nuke triggers by default and cannot be banned by the bot.
Configuration is handled automatically upon join. You can use commands to fine-tune settings.
Advanced Spam Filters
Protect your server from raid bots and malicious links. Our AI-driven engine detects patterns of spam and link-swapping in real-time.
- Anti-Link: Blocks suspicious external URLs.
- Anti-Mass-Mention: Auto-quarantines users who mention too many people.
- Anti-Scam: Detects common Discord token-logging and Nitro scam links.
Command Reference
ShieldBot uses modern Discord Slash Commands (/) for zero-latency execution. Below is the list of core administrative commands.
| Command | Description | Permission Level |
|---|---|---|
| /antinuke | Toggles the main anti-nuke engine on or off. | Owner Only |
| /whitelist add | Exempts a trusted user from anti-nuke triggers. | Admin |
| /lockdown | Instantly locks all channels during a raid attempt. | Admin |
| /logs setup | Designates a secure channel for audit logs. | Admin |
| /quarantine | Isolates a suspicious user without banning them. | Moderator |
Permissions Guide
ShieldBot operates on a tiered permission system to ensure that only the right people can access sensitive security settings.
- Owner: Full access to all commands.
- Admin: Can manage whitelists and toggle non-critical modules.
- Moderator: Can access logs and quarantine users.
Automated Recovery
In the event a malicious bot manages to delete a channel before our 0ms engine catches it, the Auto-Recovery system will instantly recreate the channel with identical permissions and placement.
All recovery actions are logged to your designated logs channel.