MUD Staff Handoffs directory
Reliable staff continuity in MUDs requires documented procedures for transferring permissions, lore knowledge, and operational responsibilities. This directory catalogs tools for creating runbooks, permission matrices, and knowledge bases that prevent single points of failure in volunteer-driven administration teams.

Showing 20 of 20 entries
MudOS Documentation
freeComplete reference for MudOS driver efuns and administrative commands essential for implementor handoffs. Documents security-critical functions and driver-level configurations required for server maintenance transitions.
Pros
- + Complete efun documentation
- + Administrative command references
- + Driver-level security notes
Cons
- − Legacy formatting
- − Assumes C programming knowledge
LPmud Resources
freeCentralized repository for LPC coding standards, library documentation, and Mudlib references. Critical for coder transitions and maintaining consistent coding patterns across volunteer developer rotations.
Pros
- + LPC coding standards
- + Library documentation
- + Active community forums
Cons
- − Scattered across multiple subdomains
- − Mixed levels of maintenance
GitHub Wiki
freemiumVersion-controlled wiki platform for documenting zone lore, quest solutions, and builder guidelines. Prevents knowledge loss during staff transitions by maintaining complete edit history and granular access permissions for different immortal levels.
Pros
- + Version controlled lore
- + Permission granularity
- + Audit trails of changes
Cons
- − Requires git knowledge from non-technical builders
- − Markdown-only editing interface
Notion
freemiumFlexible workspace for creating runbook databases, permission matrices, and transition checklists. Supports templates for standardizing onboarding procedures for new immortals and builders.
Pros
- + Database views for permission matrices
- + Template support for runbooks
- + Real-time collaboration
- + Embed code snippets for MUD commands
Cons
- − Internet dependency for access
- − Export limitations in free tier
Confluence
paidEnterprise wiki platform with structured page hierarchies suitable for complex MUD documentation trees. Advanced permissions allow separation of implementor-level docs from builder guidelines.
Pros
- + Structured page hierarchies
- + Advanced permissions
- + Integration with Jira for task tracking
Cons
- − Complex licensing costs
- − Overbuilt for small volunteer MUDs
BookStack
open-sourceSelf-hosted wiki platform using shelf/book/chapter metaphors for organizing MUD lore. WYSIWYG editing accessible to non-technical staff who need to document zones without learning markup languages.
Pros
- + Self-hosted data control
- + Intuitive organizational structure
- + WYSIWYG editing for builders
Cons
- − Requires server administration knowledge
- − PHP dependency for hosting
DokuWiki
open-sourceFile-based wiki requiring no database, suitable for MUDs with limited technical infrastructure. Simple permission system supports separating mortal-readable docs from immortal-only procedures.
Pros
- + File-based storage
- + No database required
- + Simple permission system
Cons
- − Plain text storage limitations
- − Basic search functionality
Obsidian
freemiumLocal-first knowledge graph for building interconnected documentation of MUD lore and systems. Markdown files remain portable during host transitions or server changes.
Pros
- + Local knowledge graph
- + Markdown file portability
- + Graph view of lore connections
Cons
- − Sync requires subscription
- − Steep learning curve for non-technical staff
PagerDuty
enterpriseOn-call rotation management for MUD implementors handling server reboots, bug fixes, and player emergencies. Escalation policies ensure coverage during volunteer availability gaps.
Pros
- + Escalation policies for coverage gaps
- + On-call rotation management
- + Incident tracking and postmortems
Cons
- − Expensive for volunteer projects
- − Complex setup for small teams
Opsgenie
paidCalendar-based scheduling tool for managing volunteer admin availability across time zones. Supports rotation rules for distributing weekend and holiday coverage among staff.
Pros
- + Calendar scheduling interface
- + Rotation rules
- + Mobile notifications for emergencies
Cons
- − Per-user pricing model
- − Atlassian ecosystem lock-in
Discord
freemiumCommunication platform with role-based permissions mirroring MUD immortal hierarchies. Channel history retention preserves decisions and context for incoming staff members.
Pros
- + Role-based permissions matching MUD ranks
- + Persistent channel history
- + Voice channels for staff meetings
Cons
- − No threaded documentation capabilities
- − Potential distraction from game management
Slack
freemiumTeam messaging with searchable history for preserving institutional knowledge during staff transitions. Integration with development tools supports coder handoff workflows.
Pros
- + Searchable history for knowledge retention
- + Integration with dev tools
- + Threaded discussions for organization
Cons
- − 90-day history limit on free tier
- − Notification fatigue for volunteers
Trello
freemiumVisual kanban boards for tracking transition tasks during staff handoffs. Checklist templates ensure consistent offboarding procedures when immortals depart.
Pros
- + Visual kanban boards
- + Checklist templates for procedures
- + Label filtering by role type
Cons
- − Limited automation on free tier
- − Card-based structure limitations
GitHub Issues
freemiumTask tracking system for managing handoff checklist items and assignment of responsibilities. Milestone tracking coordinates multi-stage transition processes between outgoing and incoming staff.
Pros
- + Task assignment and ownership tracking
- + Milestone tracking for transitions
- + Linked pull requests for code changes
Cons
- − Developer-centric interface
- − Public visibility concerns for private MUDs
Google Workspace
freemiumShared document platform for transition notes and temporary access documentation during staff changes. Universal accessibility reduces friction for volunteers with varying technical backgrounds.
Pros
- + Shared drive access for transition files
- + Commenting system for clarifications
- + Universal access without training
Cons
- − Google account requirement
- − Limited formatting for technical documentation
Outline
open-sourceModern wiki platform with Slack integration designed for team knowledge bases. Self-host option allows MUDs to retain control of sensitive operational documentation.
Pros
- + Modern wiki interface
- + Slack integration
- + Self-host option for data control
Cons
- − Node.js dependencies
- − Requires PostgreSQL database
MUD Connector
freeListing service and community hub for recruiting replacement staff and connecting with experienced administrators. Directory of active games provides context for new staff joining established MUDs.
Pros
- + Active listing service for recruitment
- + Access to player base metrics
- + Network of veteran admins
Cons
- − Discovery focused rather than operational
- − No built-in management tools
MudBytes
freeCodebase repository and snippet sharing platform with forums for administrative discussions. Resource for understanding legacy systems during staff transitions.
Pros
- + Codebase repository for comparisons
- + Snippet sharing for solutions
- + Forums for admin advice
Cons
- − Interface aging
- − Smaller active user base than historical peaks
Gammon Forum MUD Board
freeTechnical discussion forum focused on MUSHclient and MUD implementation details. Source of experienced advice for complex handoff scenarios and legacy system documentation.
Pros
- + Technical discussions of systems
- + MUSHclient integration knowledge
- + Experienced long-term admin advice
Cons
- − Forum format requires digging
- − Specific to certain codebase families
MediaWiki
open-sourceMature open-source wiki platform powering Wikipedia, suitable for extensive MUD lore documentation. Revision history and user rights management support complex permission schemes for different staff levels.
Pros
- + Mature stable platform
- + Comprehensive revision history
- + Extensive extensions for permissions
Cons
- − Complex initial setup
- − Heavy resource usage for small installations