Getting Started
Fast deployment protocol & initialization instructions for
Welcome to . Our platform is built to operate with zero-configuration overhead right out of the box. Upon authorization, the engine automatically provisions isolated SQLite schemas to store your server settings. Follow this detailed 5-step roadmap to fully initialize the bot in your community:
01Authorize the Bot Client
Click the Add To Discord button in the hero header. Choose your guild and verify that the Administrator permission bit remains checked. This is required because the bot must run high-clearance actions (like rolling back channel deletions or stripping rogue admin permissions) during emergency Anti-Nuke shutdowns.
02Verify Connection & Latency
In any text channel visible to the bot, type ;ping. The bot will respond with a real-time latency ping card measuring Discord Gateway, REST API request speed, and active Lavalink music node status. You can also run ;status to view database connection status and server resource allocation (RAM/CPU usage).
03Set Up Custom Prefix
By default, responds to the semicolon (;) prefix. If you need to change this, the guild owner can type ;prefix set [newPrefix] (e.g. ;prefix set !). This prefix will immediately save to the guild configuration database without requiring a restart.
04Activate the Anti-Nuke Shield
To lock down your server against malicious administrators, initialize the Anti-Nuke framework by running ;antinuke enable. This command automatically sets up default thresholds, creates custom logs, and begins scanning server audit records for unauthorized edits.
05Whitelist Co-Admins & Staff
Once the Anti-Nuke system is active, any admin who performs high-risk tasks (like mass-kicking, channel creation, or role deletion) will trigger automated security limits and lose their permissions. To prevent this, the primary Guild Owner should add co-owners and managers to the whitelist by running ;whitelist add @User or ;whitelist add [userID].