Moderation

AutoMod

Triggers, actions, bypasses, logging, and moderation case creation.

AutoMod is Oxy’s automatic enforcement layer. It is configured per Discord server. When a trigger matches, Oxy performs the configured action, can write to AutoMod logs, and can open a moderation case with a case ID.

Per-server configuration

Open /settings and find AutoMod. Exact trigger names and action labels depend on the installed version — this page does not invent parameter names. Configure AutoMod in the server where it should run; copies are not applied to other guilds.

Triggers

A trigger is the condition AutoMod watches for. Available triggers are those exposed in your settings panel. If a trigger you expect is missing, it is not available in the current installation rather than implied by this site.

Actions

When a trigger matches, AutoMod performs the action you configured. That may include deleting a message, applying a moderation action, notifying staff, or opening a case. Only actions offered in settings are supported.

Bypass configuration

Bypasses let specific roles or channels skip AutoMod. Use this for staff channels and verified bots you trust. A bypass that is too wide silently disables enforcement. Review bypasses when you change staff roles.

AutoMod logging

AutoMod can post to a dedicated log or to the shared moderation log, depending on settings. Log lines should be enough to reconstruct what matched and what action ran, including the case ID when a case was opened.

Relationship to moderation cases

If case creation is enabled, an AutoMod action opens a case in the same system as /mod. Staff can then look up Case #1042 (for example) and see that the source was AutoMod rather than a human moderator. If case creation is off, AutoMod may still log, but there will be no case ID to look up.

Case #1042 (AutoMod)
Action
Warn
User
@ExampleUser
Reason
Spam
Source
AutoMod