Moderation

Zagreus provides layered moderation tools that cover content filtering, trade enforcement, thread management, and audit logging. Every moderator action is permanently recorded and queryable, ensuring accountability and transparency.

Content Moderation

Per-user content blocking allows moderators to restrict specific types of content from individual users. This is more granular than channel-level permissions and does not require modifying Discord roles.

Blockable Content Types

How It Works

• A moderator runs /content-block add @user <type> to block a content type for a specific user
• When the user posts a message containing the blocked content type, the message is automatically deleted
• The user receives an ephemeral message explaining what was blocked and why
• Optionally, a timeout can be applied — the block expires automatically after the specified duration
• Multiple content types can be blocked for the same user simultaneously
• Blocks are logged in the audit trail with the moderator who set them

---

Trade Enforcement

Trade Bans

Trade bans prevent a user from posting in any monitored trade channel across the entire server.

Temporary Bans

• Set a duration (hours, days, weeks) for the ban
• The ban auto-expires when the duration elapses
• The user receives a DM notification when banned and when the ban expires
• A reason is recorded in the audit log

Permanent Bans

• No expiry date — the ban persists until manually removed by a moderator
• The user is notified via DM
• Permanent bans are visually distinguished in the audit log and dashboard

Ban Behavior

• Messages posted by banned users in monitored channels are immediately deleted
• The user receives an ephemeral message with the ban reason and expiry (if temporary)
• Ban status is visible on the user's trade profile
• Bans are enforced even if the user leaves and rejoins the server

Trade Mutes

Trade mutes are a lighter alternative to bans. A muted user's messages are not deleted, but they are flagged and the user is rate-limited.

• Always temporary: Mutes require a duration and auto-expire
• Rate limiting: Muted users can only post one trade per configurable interval
• Visual indicator: Muted users' trades may be marked with a mute indicator
• DM notification: The user is informed of the mute, its reason, and when it expires

Suspicious Activity Detection

Zagreus automatically flags potentially suspicious trading behavior:

• New account trading: Users with accounts younger than a configurable threshold posting trades
• Rapid trade posting: Posting more than a configurable number of trades within a short window
• Cross-channel duplication: Identical trade content posted in multiple monitored channels
• Edited prices: Trade posts where the price was modified after initial posting
• Deleted and reposted: Trades that are deleted and immediately reposted (potential scam pattern)

Flagged activity is sent to the configured notification channel for moderator review. No automatic action is taken.

---

Thread Management

Thread Rules

Per-thread content restrictions that function similarly to content blocks but apply to everyone within a specific thread.

• Configure which content types are restricted in a thread (images, links, files, etc.)
• Messages violating thread rules are auto-deleted with an ephemeral explanation
• Optionally apply a timeout to rule violators — users who repeatedly break thread rules receive a Discord timeout
• Thread rules persist until manually removed or the thread is archived

Thread Bans

Thread bans prevent specific users from participating in a thread.

Temporary Thread Bans

• Set a duration for the ban
• The user is removed from the thread and cannot rejoin until the ban expires
• Auto-expiry with DM notification

Permanent Thread Bans

• The user is permanently removed from the thread
• If the user attempts to rejoin (via thread member updates), they are automatically removed again
• Join attempt notifications are sent to the moderator who set the ban

Thread Ban Enforcement

• When a banned user is detected joining a thread, they are immediately removed
• The threadMembersUpdate event handler monitors for banned users rejoining
• A notification is sent to the configured log channel when enforcement occurs

---

Delete and Edit Logging

Zagreus can log deleted and edited messages to a designated channel, providing a record of removed content.

Configurable Log Channels

• Set one or more channels to receive delete/edit logs
• Different channels can be configured for different categories (trades vs. general)

Who-Deleted Detection

When a message is deleted, Zagreus attempts to determine who deleted it:

• Self-delete: The author deleted their own message
• Moderator delete: A moderator or bot deleted the message (detected via audit logs)
• Unknown: Could not determine the deleter (Discord audit log limitations)

Filtering

Fine-tune what gets logged to avoid noise:

Uncached Message Logging

When a message is deleted that was not in the bot's cache (sent before the bot started or too old):

• The log entry shows "[Uncached Message]" with the message ID and channel
• If the message was a trade, the trade database record is referenced

Attachment Metadata

When a deleted message contained attachments:

• File names, sizes, and types are logged
• Image dimensions are recorded when available
• Attachment URLs are included (may expire after Discord's CDN retention period)

---

Audit Log

Every moderation action taken through Zagreus is permanently recorded in the audit log. This provides a complete, tamper-proof history of all moderation activity.

Recorded Actions

• Trade bans and unbans (with reason, duration, moderator)
• Trade mutes and unmutes
• Content blocks added and removed
• Thread bans and unbans
• Thread rules changes
• Giveaway moderation (end, cancel, reroll)
• Configuration changes (channel monitoring, role assignments)

Querying the Audit Log

The audit log can be queried via:

• Slash command: /trade audit-log with filters for user, action type, date range, and moderator
• Web dashboard: Full-featured audit log viewer with search, filters, pagination, and export

Audit Log Fields

---

Commands

---

Moderation Cases

Moderation cases provide a structured record of every warning, timeout, ban, and other disciplinary action taken against a user. Each case is assigned a unique number and tracked permanently, giving moderators a complete enforcement history.

How It Works

• A moderator issues a warning with /case warn @user [reason]
• The target user receives a DM notification with the reason
• A numbered case is created and stored in the database
• If auto-escalation rules are configured, the bot checks whether the user has crossed a threshold (e.g., 3 warnings within 30 days triggers an automatic timeout)

Auto-Escalation

Auto-escalation rules allow the server to define automatic consequences when a user accumulates too many cases within a time window.

Auto-escalation is configured via the web dashboard at Moderation > Settings.

Case Commands

---

Native Timeouts

Discord native timeouts temporarily prevent a user from sending messages, reacting, or joining voice channels. Zagreus wraps this functionality with case tracking, DM notifications, and audit logging.

Timeout Behavior

• The target user receives a DM with the timeout reason and duration before the timeout is applied
• A moderation case is automatically created and linked to the timeout
• Timeout application and removal are both logged in the audit trail
• Timeouts are enforced by Discord itself — they persist even if the bot goes offline

---

Logging System

The logging system captures server events and posts formatted log entries to designated channels. Events are organized into five categories, each independently configurable.

Log Categories

Configuration

Logging is configured through the web dashboard at Settings > Logging. Each category can be assigned its own log channel, or multiple categories can share a single channel.

Ignore Lists

Each category supports ignore lists to reduce noise:

---

Anti-Nuke Protection

Anti-nuke protection detects and responds to destructive actions that may indicate a compromised admin account or malicious bot. When suspicious activity is detected, the bot can automatically quarantine the offending account and alert moderators.

Detection

Quarantine Actions

When a threat is detected, the bot can take one or more of the following actions against the responsible account:

Server State Snapshots

Zagreus takes a snapshot of the server's channel structure, role hierarchy, and permissions every 6 hours. These snapshots serve as a reference point for detecting unexpected changes and can aid in manual recovery if a nuke event occurs.

Configuration

Anti-nuke thresholds and quarantine actions are configured through the web dashboard at Moderation > Security. You can adjust:

• Detection thresholds (how many deletions/bans/kicks trigger the alert)
• Time windows (how quickly actions must occur to be considered suspicious)
• Quarantine response (strip roles, kick, or ban)
• Notification channel for alerts

---

Protected Roles

Protected roles prevent unauthorized role assignments. When a role is designated as protected, any assignment of that role to a user is monitored — if the assignment was not performed through an approved workflow, it is automatically reverted.

How It Works

• Server admins designate specific roles as protected via the dashboard
• When a protected role is assigned to a user, the guildMemberUpdate event checks whether the assignment was authorized
• Unauthorized assignments are automatically reverted — the role is removed from the user
• An alert is sent to the configured moderation channel with details about the unauthorized assignment, including who made the change (from the Discord audit log)

Use Cases

• Admin roles: Prevent compromised accounts from granting themselves admin access
• Moderator roles: Ensure only senior staff can promote moderators
• Verified roles: Ensure verification can only happen through the intended flow

---

User Reports

Members can report other users to the moderation team. Reports appear in the configured report channel with action buttons.

Commands

How It Works

• Reporter provides a user, reason (max 1000 characters), and optional message link
• If a message link is provided, the bot snapshots the message content (first 500 characters)
• An embed is posted to the mod report channel with: report ID, reported user, reporter, reason, and message snippet
• Moderators can Resolve, Dismiss, or Escalate to a formal case using action buttons
• Cooldown between reports (default 60 seconds, configurable per server)
• Cannot report yourself or bots

---

Modmail

A DM-based support system where members message the bot and a private channel is created for staff to respond.

Commands

Workflow

---

Temporary Roles

Assign roles that automatically expire after a specified duration.

Commands

Duration Formats

Duration range: 1 minute to 30 days. The role is immediately assigned and automatically removed when the duration expires.