100 MUD Moderation Policy resources for MUD players

Maintain a separate, non-negotiable ruleset covering real-world threats, illegal content, and platform Terms of Service violations that applies regardless of in-character context. Publish via in-game @motd and require acknowledgment on @pcreate.

Create explicit documentation defining when roleplay actions constitute harassment, including prolonged targeting, consent violations in sensitive RP, and use of OOC information IC. Distinguish between character conflict and player hostility using @note logging.

Implement opt-in protocols for ERP (erotic roleplay), graphic torture, or permanent character injury requiring explicit @consent flags. Document withdrawal of consent mid-scene procedures and immediate @freeze triggers.

Establish clear policies on multiple account ownership, including mandatory @register linkage or prohibition of alts in opposing organizations. Define metagaming boundaries regarding shared knowledge between characters.

Provide specific scenarios distinguishing legitimate IC knowledge from OOC information abuse, including Discord/screenshot sharing, stream sniping, and alt exploitation. Reference actual (anonymized) @log excerpts in training materials.

Distinguish between client triggers (acceptable) and unattended automation (prohibited). Define maximum action rates and require presence checks via @idle monitoring or periodic verification @pemits.

Apply different standards to OOC channels, newbie help, and in-character communication. Document where flaming is permitted (e.g., combat taunts) versus prohibited (help channels).

Clarify opt-in vs. open PK (player killing) policies, including corpse looting rights, XP loss percentages, and revenge window limitations. Specify @flag mechanics for consent withdrawal.

Define strict criteria for staff resurrection of dead characters, including bug-related deaths versus IC execution. Require @approval from two immortals for any resurrection to prevent favoritism.

Implement semantic versioning for rules documents. Automatically display changelogs via @notify or connect screen messages when players log in after updates, requiring @acknowledge command for continued play.

Account for GDPR data deletion requests, COPPA age requirements (13+), and regional hate speech laws in policy drafting. Document data retention periods for @logs and @mails.

Issue first contact via @pemit with specific rule citation, simultaneously logging to @syslog with timestamp and staff ID. Require player acknowledgment via reply before continuing enforcement.

Send persistent in-game mail detailing violation, previous warnings, and consequences of further infractions. Archive in player record accessible to all immortals via @stat player=warnings.

Implement graduated cooling-off periods: 15 minutes for spam, 1 hour for minor harassment, 24 hours for sustained aggression. Use @ban/temp with automatic expiration to prevent indefinite forgetfulness.

Suspend character activity without banning account, placing player in detention room or restricting commands. Document freeze reason visible to all staff and set automatic review timestamps.

Utilize physical jail rooms with restricted exits for IC crimes, distinguishing from OOC bans. Require bail systems or timed sentences served online, logged separately from administrative sanctions.

Apply command restrictions preventing use of public channels (gossip, ooc) while maintaining access to emotes, says, and tells for roleplay. Log mute duration and lifting automatically.

Assign community service via quest systems, XP penalties to offender with transfer to victim, or item confiscation for economic crimes. Avoid real-money penalties to prevent legal issues.

Apply invisible @flag indicating heightened monitoring for 30-90 days post-sanction. Require dual-immortal approval for any punishment lifting during probation and document all interactions.

Define procedures for stripping clan/guild membership, including rank demotion via @set and clan expulsion. Distinguish between IC leadership decisions and OOC administrative removals.

Document procedures for identifying sock puppet accounts via IP matching, email verification, or behavioral analysis. Implement @ban/site for persistent evaders while avoiding collateral damage on shared connections.

Final escalation requiring head immortal approval, including specific rule violated, evidence log references, and standardized appeal URL or @request command. Never apply without written warning history except for zero-tolerance violations.

Configure ban messages to show specific policy section violated, date of incident, and appeal instructions. Avoid vague 'banned' messages that prevent understanding and increase hostility.

Implement in-game command creating staff-visible ticket with unique ID, allowing players to present evidence and context. Auto-notify player of receipt and estimated review timeframe.

Establish 6-month minimum retention for @logs, @mails, and @syslog entries related to sanctions. Document automatic purging schedules for privacy compliance while maintaining case records.

Require uninvolved staff members to review appeals from players they have not previously interacted with. Maintain rotating panel assignments to prevent clique protectionism.

Publish monthly anonymized summaries of ban counts, appeal success rates, and policy clarifications via in-game bulletin boards or external wiki. Establish precedent without violating privacy.

Define strict deadlines: 30 days for temporary bans, 90 days for permanent bans. Document late appeal acceptance criteria for new evidence or extended absence circumstances.

Log all reversed sanctions with reasoning to identify staff training needs or policy ambiguities. Share lessons in staff meetings without assigning blame to individual immortals.

Require immortals to document conflicts of interest (friendships, rivalries, shared history) and recuse from cases involving those players. Maintain private registry of recusal relationships.

Display aggregate statistics on enforcement actions, average response times, and appeal outcomes visible to player base. Include trend indicators showing community health over time.

Implement procedures for complete account deletion including @logs, @mails, and forum posts while maintaining anonymized statistics. Verify identity before purging to prevent spoofing.

Require two staff members to confirm bans lasting longer than 24 hours or involving permanent character deletion. Implement @approve command logging secondary confirmation with timestamp.

Conduct 60-minute staff meetings reviewing contested warnings, edge cases, and policy gaps. Use standardized agenda template comparing similar offenses for consistency calibration.

Review sanctions for patterns targeting specific player groups, cliques, or playstyles. Analyze metrics showing enforcement rates by immortal and by player demographic to identify unconscious bias.

Establish voice guidelines distinguishing between professional enforcement (warnings) and community building (help). Prohibit staff from displaying anger or personal attacks in @pemits regardless of provocation.

Utilize shared @note system for ongoing incidents spanning multiple time zones, including current status, player emotional state, and recommended next steps. Prevent contradictory messages from different staff.

Maintain searchable archive of past cases organized by rule type, player history, and outcome. Reference during new incidents to ensure similar offenses receive similar sanctions regardless of which immortal handles the case.

Restrict new staff to observation and logging roles for 30 days, requiring mentorship from senior immortals. Gradually unlock @ban permissions after demonstrating policy comprehension.

Document staff relationships with prominent players, including alt connections, prior friendships from other games, and vendettas. Review registry before assigning cases to prevent recusal failures.

Provide standardized @pemit templates for common scenarios (cooling down heated arguments, explaining bans, redirecting rules questions) to ensure consistent, non-inflammatory communication.

Implement mandatory breaks from moderation duties after handling severe harassment cases or sustained toxic behavior. Prevent burnout-induced harshness through duty cycling and peer support channels.