Warnings

Formal warnings with optional timeouts, plus private staff notes on a member.

What it does

/warn puts a formal, stored mark on a member with a required reason, and can attach a timeout in the same action — so a warning isn't just words when it needs teeth. /warnings shows a member's history, which is what you check before deciding whether this is a first offence or a pattern.

/note is different and worth knowing about: private staff-only notes on a member that they never see. Use it for "argumentative but not rule-breaking" context that shouldn't be a formal warning.

Warning ladder

Let warnings add up to something automatically. In Dashboard → Records → Warnings, the Warning ladder card lets you add steps like 3 warnings → 1 hour timeout, 5 → kick, 7 → ban (permanent, or for a set time). Up to 10 steps.

The step runs right after the /warn (or a report's Warn button) that reaches its number, done by Cyndrix with the reason Warning ladder: reached 3 warnings. It gets its own case and a line in the log. If Cyndrix can't do it — missing permission, or a role above its own — it says so instead of failing silently.

Good habits

• Write the reason for the next moderator, not for yourself. "Rule 3" means nothing in six months; "repeatedly derailing #support after being asked twice" does.
• Point the Warnings mod-log module at a staff channel so warnings are visible to the team rather than living only in the command output.
• Warnings are separate from Auto-Mod strikes — automod strikes escalate automatically and decay; warnings are deliberate and permanent.

Commands 3

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

Related