Moderation
Cases, case IDs, logs, lookup, and server-specific configuration.
Oxy Controller records moderation as cases. A case is a durable record of an action taken against a member: the action type, the target, the reason, and a unique case ID. Staff can look cases up later instead of searching chat.
/modModeration actions and case lookup./clearClear messages where you have permission./settingsModeration and log configuration.When a staff member takes a supported action — or when AutoMod is configured to create cases — Oxy opens a case. Cases are per server. A case ID is unique in that server’s case sequence; do not assume IDs are globally unique across every guild.
Use /mod to look up a case by its ID and view the stored action, target, and reason. If your version also lists recent cases, that list is still scoped to the current server. If a case is missing, it may never have been created (the action type is not configured to open a case) or you may be in a different guild.
When a log channel is configured, Oxy can send an action record there as well as storing the case. Logs should identify the responsible user. Keep the log channel limited to staff. Action logging and case storage are complementary — a log message is not a substitute for a case ID.
AutoMod can open cases when it takes action. Those cases keep a case ID and appear in the same lookup flow as manual warns. See AutoMod for triggers, bypasses, and how events relate to cases.
Moderation is configured per Discord server in /settings. That includes whether cases are created, where logs go, and which staff roles may run /mod. There is no global moderation profile that spans every guild the bot is in.