April Fools: Mandoes Players' Democracy Enforcement Policy

Effective immediately, enforcement is moving to a player-driven voting model. Our moderation workload has exceeded sustainable levels: anti-cheat telemetry is producing more edge cases than we can manually review in real time, report volume spikes in Harad outpace on-call capacity, and clip verification queues are creating multi-hour delays. Continuing to adjudicate every incident 1:1 is no longer operationally viable.

This policy is designed to keep matches playable by distributing first-line decisions to the player base. We understand it's blunt; the short sentence length is intentional.

Policy overview:

Any player may initiate a vote using: /mandoes ban <player> <reason>

• A 60-second server-wide vote opens.
• One vote per account. You may change your vote during the window; only your latest vote is counted.
• Each YES = +10 seconds ban time
• Each NO = −10 seconds ban time
• Final duration = max(0, (YES − NO) × 10s). If the result ≤ 0, no action is taken.
• Bans don't apply if a player is PvP tagged
• Players can only be banned twice in the same hour

Example:

• /mandoes ban GrapesOfLag scaffolding on skirmish bridge
• /mandoes vote GrapesOfLag yes
• /mandoes status GrapesOfLag
• If YES=12 and NO=9 at 60s → (12−9)×10 = 30 seconds ban applied

Administrative note:

Staff will prioritize uptime, incident feed health, and intervention only where systems degrade match quality (e.g., command abuse impacting stability). Please keep reasons concise when opening cases; it improves traceability. We appreciate the community's help in restoring actionable signal amid the current volume.