Documentation / Overview / Getting Started
Getting Started & Automatic Setup
After inviting the Aegis Guard bot to your server, set up the entire log, permission, and security network with a single command within 60 seconds.
- 1. Invite & Authorize the Bot
Invite the bot with server Administrator permission and move its role to the top.
https://discord.com/oauth2/authorize?client_id=1527276218007687168&permissions=8&integration_type=0&scope=bot+applications.commands - 2. Run Auto Setup
Build the log category, audit channels, and access rules with a single command.
- 3. Monitor Protection Live
/antinuke panel ile panik modunu ve eşik değerlerini görüntüleyin.
Aegis Guard is the protection system and automation hub for modern Discord communities. It works with zero configuration difficulty; the moment you issue the setup command, it analyzes the server architecture and deploys enterprise-level protection layers.
Auto Setup (/kurulum)
If there is no log category set up on the server, Aegis creates the `aegis-logs` category and log channels that only administrators can see. It also opens public, read-only `welcome` and `announcements` channels and the `tickets` category. Main log channels:
- gelen-giden
- Members joining and leaving the server.
- mesaj-log
- Deleted and edited messages, catches by AutoMod.
- ban-kick-log
- Ban, kick and timeout punishments.
- genel-log
- General events including Anti-Nuke and Anti-Raid interventions.
- ticket-log
- Opened and closed support tickets; transcripts are sent to the ticket-transcript channel.
- role-log, channel-log, voice-log
- Role, channel, and voice room changes (nickname, mute, invite, and status logs are also enabled in the full package).
/kurulumWhen a user with Administrator permission on the server runs this command, Aegis isolates all permissions in the background and activates its protection.
Ready Server Template (/sablon)
Instant ready-to-use channel and role architecture is set up for newly opened or servers that need to be reconfigured from scratch:
/sablon tur:gaming dil:trVoice rooms, chat channels, and permission matrix are automatically generated based on the selected category.
Critical: Role Hierarchy Rule
In the Discord security model, a bot can only interfere with roles and members that are **lower** than its own role. For Anti-Nuke protection to be able to ban attacking administrators, the `Aegis Guard` role must be positioned above all other administrator roles in Discord Server Settings > Roles.
- Drag the Aegis Guard role to the very top of the list (just below the Server Owner role).
- Ensure the bot's 'Manage Roles' and 'Ban Members' permissions are enabled.