DikuMUD checklist for MUDs

Compile the source using GCC 10+ with -Wall flags and ensure all 'type-punned pointer' and 'format-security' warnings are resolved to prevent crashes on modern Linux distros.

Verify that SIGBUS and SIGSEGV signals are trapped to trigger a global player save (do_auto_save) before the process terminates.

Ensure the codebase uses SHA-512 or Blowfish via libcrypt instead of the deprecated DES crypt() to maintain compatibility with modern glibc versions.

Run the MUD for 24 hours and monitor file descriptor counts to ensure sockets are properly closed when players drop or lose connection.

Execute a copyover command with 10+ active connections to ensure descriptors are passed correctly and no player state is lost.

Run a script to scan all room files for exits leading to VNUMs that do not exist in the current area files.

Verify that every mob and object assigned to a reset command (M, O, G, E) exists in the VNUM database.

Ensure area.lst is sequenced so that base areas load before areas that depend on their VNUM ranges or specific object templates.

Trigger every scripted mob/object to verify that the interpreted script engine does not encounter runtime errors or infinite loops.

Check VNUM 2 (Limbo) to ensure it is not accumulating 'lost' objects that should be purged by the daily cleanup routine.

Simulate combat between level 50 players and mobs to ensure Armor Class does not 'wrap' or become useless against high hitroll values.

Verify that a dedicated healer's mana-per-second recovery cannot outpace the maximum possible DPS of an equivalent level mob or player.

Ensure that 100% spell resistance is mathematically impossible through gear stacking to prevent 'invincible' player builds.

Confirm that the 'flee' command cannot move a player into a room locked by a key or flagged as private/no-mob.

Review the skill table to ensure every class has a unique 'primary' utility that cannot be replicated by other classes via items.

Check that shop buy/sell ratios (usually 100% buy / 50% sell) prevent players from profiting by buying and immediately reselling the same item.

Verify that 'Unique' or 'Limited' flags on high-end gear correctly prevent more than the specified number of items from existing in the game world.

For CircleMUD-based games, verify that rent costs for high-level items scale with the average gold-per-hour of that level range.

Confirm that player and mob corpses decay and purge within 30 minutes to prevent object bloat in high-traffic zones.

Test that putting a container inside a container does not allow players to bypass total carry weight limits (the 'bag-in-bag' bug).

Verify that commands like 'shutdown', 'reboot', and 'set' are restricted to Level 60 (or max level) only.

Ensure all administrative actions (mset, oset, transfer) are logged to the 'wiznet' channel and the system log file.

Check that the IP-tracking code correctly flags or blocks multiple connections from the same source address if the policy forbids multi-playing.

Run a script to ensure player files (pfiles) do not contain illegal characters or over-length strings that could cause buffer overflows on load.

Configure a cron job to rsync the 'player/', 'area/', and 'lib/' directories to a remote off-site location every 6 hours.