MUD Staff Handoffs checklist for MUDs

Verify new admin successfully authenticates via root SSH key from external network IP and can execute sudo commands on production server

Confirm database root password changed and new credentials stored in team password vault with verified access tested via mysql/psql client

Check domain registrar account ownership transferred with 2FA reset completed and WHOIS contact information updated

Verify hosting provider billing contact and payment method updated to prevent service suspension due to expired cards or unrecognized charges

Confirm SSL certificate auto-renewal scripts execute under new admin's cron permissions and expiry alerts route to new admin email

Document all current immortal level assignments (IMP, GOD, WIZ, BUILDER) with specific character names and access justifications in permission matrix

Verify builder port/wizard access credentials tested successfully by incoming admin including zone editing and object manipulation commands

Check version control repository admin rights transferred on GitHub/GitLab/self-hosted Git with branch protection rule modifications tested

Confirm backup storage bucket access permissions updated in AWS S3/Google Cloud/self-hosted MinIO console with restoration download tested

Verify monitoring dashboard (Grafana/Nagios/Munin) admin rights transferred and real-time alerts successfully received by new admin

Execute server restart procedure from runbook during low-traffic window without assistance from outgoing admin to verify documentation accuracy

Verify database backup restoration tested on staging environment using documented steps with checksum validation against production data

Confirm custom codebase deployment steps validated with specific file path references and compilation flags documented for dialect-specific MUD code

Check on-call escalation contacts updated in PagerDuty/Opsgenie/Discord webhook with new admin phone number and timezone specifications

Document hardware vendor contact information and support contract numbers including server serial numbers and SLA details

Verify MUD lore bible/wiki access confirmed and last edit timestamps checked for currency with export of recent changes provided to new admin

Confirm upcoming event calendar exported from outgoing admin's account and imported to new admin's scheduling system with reminder settings preserved

Check Patreon/PayPal/Ko-fi business account admin rights transferred and payout methods verified to prevent donation interruption

Verify Discord server owner or administrator role transferred to new admin account with bot command permissions tested

Confirm email hosting admin panel access transferred and MX records documented with mailing list ownership updated

Execute full shadow shift where new admin handles emergency reboot and player complaint without outgoing admin intervention or communication

Verify outgoing admin's access revoked from all critical systems except explicit documented advisory role with specific limited permissions

Confirm emergency contact list updated with new admin's phone number, timezone, and physical location for hardware failure scenarios

Check all shared passwords rotated and documented in team password manager with old credentials purged from outgoing admin's devices

Verify transition completion date logged in staff changelog with both parties' signatures and archive location of handoff documentation