Document every event in your server via detailed log types.
A log is what separates an argument from certainty: who deleted the message, who pulled the role, who kicked the member, and when. The system documents every event in your server, and you decide which events are recorded, where each type lands, and in what shape.
Logs are split into categories: voice, messages, reactions, moderation, members, server, protection, jail, warnings, music, and tickets. You open a category and enable only the types that matter to you.
When you set the global channel or color, it wins over each log own settings. Clear it and every type returns to its own channel and color exactly as before, so you never lose your setup.
There are exactly two options: the main server, or a separate server. In the first, log channels are created inside the server the bot moderates. In the second, you pick another server the bot has already joined, keeping the logs completely out of members sight. Every channel list across the log pages reads from the server you choose here.
You pick one role that sees the created channels, and if you have no suitable role you type a name and press create role, which creates it in the log server and selects it automatically. Channels are created hidden from everyone by default: View Channel denied for @everyone, View Channel and Read Message History allowed for the chosen role, and writing allowed for the bot.
A log is what separates an argument from certainty. A member claims a moderator took their role unfairly, the moderator denies it, and a message was deleted with nobody knowing who did it. Without a log these stay endless disputes; with one you open the table and read who did what and when.
Logs are split into eleven categories: voice, messages, reactions, moderation, members, server, protection, jail, warnings, music, and tickets. You open a category and enable only the types that matter to you, so your log never fills with what you do not read.
Every log type has its own settings: an independent enable switch, its own channel, a message you design yourself that is refused if empty, and an ignore bot actions switch. That last one matters in practice: without it, your own bots automated activity becomes most of the log and buries what humans did.
The global override is a powerful tool: a global channel, a unified color, and footer text forced onto every type at once without erasing their individual settings. So you switch between everything in one channel and each type in its own whenever you like, and clearing the override returns every type to its own channel and color exactly as before.