100 MUD Staff Handoffs resources for MUD players

Compile comprehensive list of suspended accounts including original violation context, appeal history, and private notes from your personal logs that explain nuanced decisions not visible in public ban lists.

Record all active zone development including coordinate ranges, room completion percentages, mob prototypes in progress, and specific builder contact information for projects requiring handoff to new zone administration.

Export email threads from the past 12 months containing policy decisions, player complaints, and disciplinary discussions that established precedents not codified in public documentation.

Compile private notes, Discord discussions, and wiki edits regarding canon changes, timeline alterations, and retcon approvals that affect ongoing roleplay narratives and player expectations.

Document active interpersonal conflicts between players including agreed-upon behavioral contracts, mediation deadlines, and sensitive information shared in confidence that requires continued handling.

Write step-by-step procedures for recurring automated or manually triggered events including specific command sequences, failure recovery steps, and expected player notification timings.

Record any personalized command shortcuts, macros, or custom shell scripts you've created for administration tasks that differ from stock codebase documentation.

Catalog all external services including domain registrars, hosting providers, SSL certificate authorities, and analytics platforms with specific renewal dates and support contact methods.

Identify unmerged features, bug fixes, or balance changes stored in your local git branches that have not yet been pushed to the main repository or deployed to production.

Move primary ownership of team credential storage in Bitwarden, 1Password, or KeePass to incoming admin while ensuring outgoing admin retains emergency access during transition period.

Record specific commands for validating backup integrity including expected file sizes, checksum verification steps, and restore testing protocols for database and flatfile storage.

Compile lists of pending forum posts, Discord moderation alerts, and private message escalations requiring administrative attention that may be time-sensitive or contain harassment reports.

Generate new SSH key pair for incoming admin, add to server authorized_keys file, and systematically revoke outgoing admin's keys while ensuring no other access methods (IPMI, serial console) are overlooked.

Change MySQL or PostgreSQL root passwords and update connection strings in game engine configuration files, ensuring new admin can perform table repairs and user management without relying on shared credentials.

Move primary ownership of GitHub, GitLab, or Bitbucket repositories to incoming admin and update organization billing contacts to prevent service interruption when payment cards expire.

Transfer domain ownership records and WHOIS contacts at registrar (Namecheap, Cloudflare, GoDaddy) to ensure new admin can modify DNS records during outages or migrate hosting without legal delays.

Transfer server ownership through Discord settings, update moderation bot configurations (Carl-bot, Dyno, MEE6), and verify webhook integrations for server status announcements route to new admin controls.

Migrate admin access for phpBB, Discourse, or NodeBB installations including database admin panels, email alias configurations, and spam filter training data specific to your community's patterns.

Transfer primary account access for OVH, Hetzner, AWS, or Linode including 2FA device reset procedures and emergency console access credentials for kernel-level server management.

Transfer Stripe, PayPal Business, or Patreon administrative access for donation processing including recurring payment management and financial reporting capabilities.

Transfer ownership of Grafana, Datadog, UptimeRobot, or Nagios monitoring setups including alert notification endpoints and SMS configuration for server downtime warnings.

Update deployment webhook secrets in GitHub/GitLab settings and Jenkins/Travis configurations to ensure automated builds trigger correctly under new admin's repository permissions.

Document Let's Encrypt certbot renewal cron jobs or commercial SSL certificate locations and transfer account access for certificate authorities to prevent expiration-related outages.

Document IP-specific firewall rules added for your access and modify cloud security groups (AWS EC2, DigitalOcean) to reflect new admin's connection sources while removing outgoing admin's IP ranges.

Schedule overlapping period where outgoing admin observes incoming admin handling live issues via shared screen sessions or tmux attachments to catch procedural knowledge gaps before full handoff.

Document specific contact procedures for hosting provider emergency tickets, including account numbers and support PINs, for scenarios when primary admin is unreachable during critical outages.

Establish pagerduty schedules or Discord webhook alert routing for urgent player issues, server crashes, or DDoS attacks requiring immediate administrative intervention.

Migrate Google Calendar, Calendly, or shared scheduling documents containing planned reboots, maintenance windows, seasonal events, and builder deadlines to prevent scheduling conflicts.

Modify message-of-the-day and login splash screens to display new admin contact information for critical issues while removing outdated contact methods to prevent player confusion.

Create template responses and forwarding protocols for copyright takedown notices, legal threats, or law enforcement inquiries including specific contact chains and document retention requirements.

Provide incoming admin with view-only access to donation pools, server cost allocations, and budget spreadsheets to ensure continuity of community funding transparency.

Transfer Twitter, Mastodon, Reddit, or Tumblr administrative access including scheduled post pipelines and automated status update integrations with game server events.

Write explicit order-of-operations for restarting game engine, database daemon, web portal, and Discord bots including dependency checks and verification steps between each service start.

Document step-by-step rollback procedures to last known good state including flatfile recovery commands, SQL dump restoration, and player compensation protocols for rollback scenarios.

Document current thresholds for automated player detection, proxy blocking rules, and CAPTCHA integration settings that prevent bot flooding while allowing legitimate VPN users.

Compile current IP range blocks, account suspension hierarchies, and trusted player exemptions that require ongoing maintenance to prevent accidental locking of legitimate community members.

Confirm new admin can assume level 31+ status and access restricted command suites including player file editing, shutdown commands, and raw database query interfaces.

Perform controlled reboot test using incoming admin's SSH keys and sudo privileges to validate full infrastructure access without relying on outgoing admin's authentication.

Conduct test restore of latest backup to staging environment to confirm new admin can recover from corruption without guidance, verifying file permissions and database connectivity.

Trigger test alerts from monitoring systems to verify SMS and email notifications route exclusively to new admin's endpoints and outgoing admin no longer receives false-positive pages.

Verify ability to restore server state using filesystem snapshot taken immediately before handoff began, ensuring forensic preservation of pre-transfer state remains accessible.

Confirm new admin receives test transaction notifications from Stripe or PayPal within 24-hour window to ensure donation processing alerts don't route to deactivated email accounts.

Confirm new admin can access server logs including player command histories, administrative action trails, and security event logs necessary for dispute resolution.

Verify automatic server status updates, crash notifications, and player count alerts successfully post to Discord channels using new admin's webhook configurations.

Test ability to modify A records or nameserver settings through registrar interface to confirm new admin can handle domain migration or CDN changes independently.

Execute automated access audit scripts across all systems (SSH, database, forums, Discord, payment processors) to verify zero remaining access points for transferred responsibilities.