MUD Conflict Resolution checklist for MUDs

Verify that server logs containing OOC channel traffic, @tells, and public says are exported with millisecond timestamps and stored in the incident evidence folder before any staff discussion occurs.

Confirm that a new private channel or board thread is created with access limited to current shift immortals only, excluding any staff with alt characters in involved factions.

Check that the shared timeline document includes columns for UTC timestamp, character name, account ID, and channel location, with the template locked to append-only for non-admins.

Validate that logs from 48 hours prior to the reported incident are included to identify escalation triggers and provocation sequences that may not be in the initial report.

Ensure previous sanction logs and incident reports are searched for all involved account IDs to identify recurring conflict cycles or established grievance histories.

Verify via character ownership logs that no assigned immortal has alt characters, patron relationships, or clan memberships with any involved party.

Confirm consensus classification as Routine (isolated), Major (faction-wide), or Critical (harassment/RL threat) logged in the staff wiki with justification.

If factional conflict, check that clan leaders were notified via +mail of impending mediation per policy, without revealing specific allegations or evidence details.

Validate that public channels and clan comms are actively monitored for @squelch evasion attempts or coded aggression that violates cooling-off status.

If real-life personal information is involved, ensure evidence package is encrypted and access logged separately from standard incident files.

Verify the meeting space has no faction ownership flags, no combat code, no eavesdropping objects, and has been swept for hidden player characters.

Confirm that the mediation script selected addresses the specific conflict category: interpersonal harassment, factional resource dispute, or recurring social tension.

Check that 72 hours have elapsed since the last aggressive @tell or public statement from any involved party before scheduling mediation.

Validate that a second staff member with +observe permissions only (no speaking rights) is assigned to log dialogue and verify procedural adherence.

Ensure all parties received via +mail the specific agenda, time limit, no-interruption rules, and consequences for violating mediation protocol.

Confirm each party explicitly acknowledged the specific community standards or @rules sections violated before proceeding to impact statements.

Check that each player stated the emotional or gameplay impact using @tempers or @emote references without interruption from opposing parties.

Validate that the mediating immortal paraphrased each concern and asked clarifying questions before allowing rebuttal periods to proceed.

Ensure mutually acceptable future behavior is defined in specific @command terms and logged in the resolution contract accessible to all parties.

Verify that explicit sanctions for next violation are stated, including specific @ban durations or faction privilege removals, with no ambiguous language.

Verify the shared timeline is updated with the UTC resolution timestamp, outcome classification, and links to all related account IDs.

Confirm that the sanction tracking log reflects specific account IDs, penalty types, end dates, and automatic @remind entries for review dates.

Check that a written summary including the agreement terms and appeal procedure was transmitted to all parties via +mail and receipt confirmed.

If community impact exceeded ten players, validate that a neutral +motd or board post is drafted explaining policy reinforcement without naming individuals.

Ensure 30-day and 90-day follow-up dates are scheduled in the staff calendar with @remind set to check for recurrence or agreement violations.

Verify that the +survey tool was distributed to neutral observers not involved in the conflict to measure changes in community atmosphere.

Check that involved accounts show resumed normal play patterns including login frequency and public channel participation within two weeks.

Validate that clan channels and private @tells are monitored for @ignore abuse, passive-aggressive emotes, or rule-skirting behaviors.

Ensure participating immortals submitted post-mortem notes to the +review channel within 48 hours identifying process improvements or staff errors.

If the same account IDs recur within 90 days, verify that a formal retrospective is filed analyzing why the resolution failed to prevent recurrence.