Mod Log

A permanent record of every moderation action, edit and deletion — plus /history for a member's full mod timeline.

What it does

A permanent record of what changed in your server and who changed it. Nine independent modules, each with its own channel: Messages (deletes, edits, purges), Channels (including threads being locked, archived or deleted), Roles, Members (joins with the invite used, leaves with the roles they had, kicks and bans, role grants, nickname edits, timeouts), Admin (staff commands), Warnings, Voice (including who moved or disconnected someone), Invites and Server (server settings, bots and integrations added, webhooks, emoji and stickers, Discord AutoMod rules, onboarding).

Kicks, bans and unbans done straight from Discord's menus are logged too, with who did it and the reason they gave — not only the ones done through Cyndrix commands. Where Discord records a reason for any change, the log shows it.

Deleted messages keep their content — Cyndrix snapshots messages as they arrive, so the log shows what was actually said rather than "message deleted". That works even for messages Discord itself no longer has cached.

Each log uses a Cyndrix colour bar so you can scan the channel: teal for creates, crimson for deletes, purple for edits, gold for renames, deep crimson for bans and mutes. Message edits highlight exactly what changed — removed words struck through, added words in bold — and GIF auto-embeds are not logged as fake edits. A deleted image that was uploaded is kept in the log post itself, so it doesn't turn into a broken link later.

/history pulls a member's full Cyndrix mod timeline — warns, bans, kicks, timeouts and mutes — in one public command. Staff notes stay private on /note.

Case numbers

Every warning, timeout, mute, kick, ban, softban and unban gets a numbered case for your server — Case #42 — shown in the log entry and in Records on the dashboard. Numbers keep counting even when logging is off.

• /case view — everything about one case, with a link to its log entry.
• /case list — a member's cases, newest first.
• /case reason — fix a reason after the fact. It updates the case, the record and the original log message, marked as edited by you.

Member reports

Members can report a message themselves: right-click it (long-press on mobile) → Apps → Report message, and add a reason if they like. The report lands in your staff channel with the message, its author, a jump link, and buttons to Delete message, Warn, Timeout 1h or Dismiss. The report updates to show which moderator did what.

Turn it on in Dashboard → Mod Log → Member Reports: pick a staff-only channel and, optionally, a role to ping. Each member can send one report a minute, and a message can only be reported once, so the channel can't be flooded.

Setup

1. Dashboard → Mod Log. Set a default log channel — any module you switch on without its own channel uses it.
2. Enable the modules you want. Give high-traffic ones (Messages, Voice) their own channel so they don't drown the rest.
3. Add ignored channels globally, or per-module for finer control — you can keep #staff-chat out of message logs while still logging channel changes there. Ignoring a channel also covers its threads.
4. Press Send test log to post a test message into every log channel. If one of them is deleted or Cyndrix can't post there, the dashboard says which.

Voice is the noisy one. It logs joins, leaves and moves, so give it a dedicated channel. It deliberately ignores self-mute and self-deafen, which would otherwise flood it; server mutes by a moderator are logged.

Cutting the noise: under Don't log messages from you can list roles or members whose deleted and edited messages aren't logged. Bots' own messages aren't logged either — unless someone else deletes one. Staff clocking on and off ticket duty stays out of the role log unless you switch Ticket on-duty roles on, and new threads are only logged if you switch Thread created on (in a forum, every post is a thread). Several quick edits to one channel or role are grouped into a single entry.

Commands 3

Generated from the bot's source — this list is always what is actually deployed.

Related