Checklists

Community Guides & Mentors checklist for MUDs

Production-ready checklist for implementing mentor programs in Telnet/SSH-based MUDs. Covers softcode configuration for channel routing, helpfile indexing, immortal escalation protocols, and retention telemetry specific to text-only environments with command parsers.

Community Guides & Mentors checklist for MUDs hero illustration
Progress0 / 30 complete (0%)

Mentor Vetting & Permissions

0/5

  • Verify 90-Day Account Age Requirement

    critical

    Check 'stat <player>' output confirms 90+ days since creation date and 50+ hours online time before granting @mentor flag.

  • Validate Command Syntax Mastery

    critical

    Administer practical exam requiring successful execution of 'get all.corpse', 'tell <player> <msg>', and '@mail <player>=<subject>/<body>' without syntax errors.

  • Review Harassment History

    critical

    Query player notes database for any '@ban', '@warn', or harassment flags within last 180 days; reject if found.

  • Assess Helpful Communication Style

    recommended

    Review last 500 lines of public channel logs for clarity, patience, and absence of leetspeak or aggressive punctuation.

  • Test Conflict De-escalation

    recommended

    Simulate angry newbie scenario via secondary account; verify applicant responds with '@page <imm>' rather than argument.

Newbie Channel Infrastructure

0/5

  • Configure Auto-Mute Threshold

    critical

    Set channel config to auto-mute characters upon reaching level 5 or 4 hours playtime; verify with '@channel/status newbie'.

  • Route @newbie Alias to Active Duty

    critical

    Ensure '@newbie <msg>' pipes to only online mentors with &mentor_active attribute set to 'yes'.

  • Implement Rate Limiting

    critical

    Configure softcode to reject messages exceeding 3 per minute per unique IP; test with rapid 'say' commands.

  • Enable Daily Log Rotation

    recommended

    Verify 'logs/newbie/' directory rotates files every 24h and retains 30 days of history for abuse review.

  • Test Client Compatibility

    recommended

    Connect via raw Telnet, Mudlet, and web client; confirm channel colors and line wrapping render identically.

Helpfile Systems

0/5

  • Index Newbie Command Tree

    critical

    Verify 'help newbie' displays hierarchical menu leading to 'help movement', 'help communication', 'help combat'.

  • Validate ANSI Contrast

    critical

    Check all helpfile headers use bright cyan (\x1B[36;1m) against black background; reject dark blue or black text.

  • Link Mentor Contact Method

    recommended

    Ensure 'help mentors' outputs current list of on-duty mentors via '&mentor_list' attribute lookup.

  • Test Search Synonyms

    recommended

    Confirm 'help start', 'help begin', and 'help new' all redirect to 'help newbie' entry.

  • Screen Reader Audit

    optional

    Verify no ASCII art barriers in 'help map'; use 'screen reader' test mode to confirm linear text flow.

Escalation Protocols

0/5

  • Document Immortal Page Priority

    critical

    Post 'help escalation' file defining '@page <imm>=URGENT: harassment' for immediate wizard intervention.

  • Test Response Time SLAs

    critical

    Simulate escalation; verify Elder Guide responds within 5 minutes, Wizard within 15 minutes during peak hours.

  • Secure Abuse Logging

    recommended

    Confirm '@report <player>' logs to private immortal channel '+abuse' invisible to mentors.

  • Grant IP Lookup Permissions

    recommended

    Verify senior mentors (level 3+) can access '@ipscan' for ban requests without immortal intervention.

  • Schedule Weekly Sync

    optional

    Calendar recurring meeting between Guide Lead and Head Immortal to review edge cases.

Retention Metrics

0/5

  • Track Tutorial Completion

    critical

    Set trigger on 'score' command to flag accounts completing 'help tutorial' sequence within first 48 hours.

  • Measure 24-Hour Return

    critical

    Query database for mentored vs unmentored newbies' second login within 24h; target >60% for mentored cohort.

  • Automate Outreach Lists

    recommended

    Configure 'who newbie' to highlight characters online >30 minutes with no mentor interaction for proactive contact.

  • Ensure Log Compliance

    recommended

    Verify mentor chat logs auto-purge after 90 days or upon player request per GDPR Article 17.

  • Export Interaction Data

    optional

    Generate monthly CSV counting '@newbie' messages per mentor for recognition and workload balancing.

Burnout Prevention Systems

0/5

  • Enforce Mandatory Leave

    critical

    Systematically remove @mentor flag after 3 months active duty; require 2-week minimum break before reinstatement.

  • Implement @offduty Toggle

    critical

    Verify '@offduty' command removes mentor from '@newbie' routing and 'who mentors' list immediately.

  • Create @commend System

    recommended

    Allow players to '@commend <mentor>' storing +1 to &karma attribute visible to immortal promotion boards.

  • Automate Wellness Checks

    recommended

    Schedule in-game mail survey every 14 days asking 1-10 burnout scale; flag scores <4 to admin.

  • Rotate Timezone Coverage

    optional

    Swap primary coverage responsibilities between mentor teams every 6 months to prevent timezone fatigue.