Reports and alerts
Player reports, Discord tickets, server warnings, anti-cheat alerts, and admin observations should enter a reviewable queue.
Moderation Systems
Moderation should be a workflow, not a mood.
Good moderation requires intake, evidence, context, escalation paths, appeals, and auditability. TIRust documents these systems so enforcement is consistent and defensible.
Context packets
Every serious case should gather IDs, timestamps, server name, logs, reports, risk signals, prior history, and staff notes.
Human judgment
Automation can prioritize and summarize, but staff should own high-impact decisions like bans, long restrictions, and appeal outcomes.
Clear path back
Appeals should be factual and linked to the original evidence trail. Staff should distinguish bad calls from players simply wanting another chance.
Admin accountability
Privileged access exists to protect the community. Staff should avoid conflicts, retaliation, secret favors, and personal advantage.
Supporter neutrality
Payment status should never override rules. See Governance for supporter neutrality and enforcement standards.
Moderation stack
The practical stack includes Discord tickets, BattleMetrics notes and flags, server logs, RCON records, anti-cheat alerts, admin review channels, and documented appeal outcomes.
Related pages
See Anti-Cheat Intelligence, Operating Standards, and AI Moderation.