Classic MUDs checklist for MUDs

Ensure the server is accessible via standard ports (23, 4000, or 2323) and that firewall rules allow ingress traffic for these ports.

Deploy a TLS wrapper (such as Stunnel or Nginx) to provide secure connections for modern clients that require encryption.

Verify that the Mud Client Compression Protocol (MCCP v2) is active to reduce bandwidth usage and improve latency for users on limited connections.

Configure a web-based telnet client (e.g., Grapevine, Mudlet-web, or a custom websocket proxy) to allow access via modern browsers without external software.

If the MUD is intended for BBS integration, verify terminal emulation (ANSI/Avatar) and handshaking protocols with the host BBS software.

Verify the presence of original license files (e.g., DikuMUD, Merc, or ROM) and ensure the 'credits' command accurately reflects the original authors.

Audit the C/C++ source code for pointer-to-integer casts and other legacy code patterns that fail on modern 64-bit Linux distributions.

Initialize a Git repository for the codebase to track preservation changes, patches, and historical area modifications.

Create a Dockerfile that encapsulates the specific legacy compiler versions and libraries needed to build the binary from source.

Identify and remove hard-coded file paths in the source code, replacing them with relative paths or configuration variables.

Run a dry-load of all .are or .wld files to ensure no corruption exists in room, mobile, or object definitions.

Execute a script to identify and repair corrupt player files or remove illegal items that may cause crashes during the loading process.

Configure a cron job to sync the lib/ and src/ directories to an off-site location (e.g., S3 or a secondary server) every 24 hours.

Perform a test restoration of the MUD on a fresh server instance using only the backup archives to verify data completeness.

Set up a system to archive system logs and public channel logs for historical preservation and community reference.

Deploy a shell script or systemd service that monitors the MUD process and automatically restarts it in the event of a crash.

Run the binary through Valgrind or a similar profiler to identify and patch memory leaks that could cause long-term instability.

Verify that the 'copyover' or 'hot-reboot' command functions correctly without dropping active socket connections or losing player data.

Set appropriate ulimits for the MUD user to prevent a single process from exhausting system file descriptors or memory.

Configure the server to log critical errors, player commands, and administrative actions to separate files for easier auditing.

Create a dedicated 'history' or 'credits' help file that lists the original developers, previous hosts, and significant contributors.

Update the 'help greeting' and 'help rules' to include modern contact info and instructions for modern Telnet clients.

Establish a public-facing bug tracker (e.g., GitHub Issues) where players can report world bugs or code issues.

Optionally implement a bridge between an in-game chat channel and a Discord/Matrix server to keep the community connected offline.

If accepting donations for preservation, provide a clear breakdown of hosting costs and how surplus funds are managed.