MUSH / MUX checklist for MUDs

Configure an automated cron job to run @dump every 24 hours and sync the resulting .flat or .db files to a secondary off-site storage location.

Edit the netmush.conf or pennmush.conf to bind to the specific IP address and port intended for public traffic, ensuring the debug port is restricted to localhost.

Define 'max_objects' and 'max_attributes' in the configuration file to prevent database bloat or malicious 'bombing' scripts from crashing the process.

Toggle the compression flag in the engine configuration to reduce disk I/O and save space, specifically for large-scale roleplay grids.

Ensure the compiled binary matches the expected version (e.g., PennMUSH 1.8.7, TinyMUX 2.12) to avoid softcode function mismatches.

Verify that only essential administrative accounts hold the WIZARD or ROYALTY flags and that no test objects retain these permissions.

Apply restrictive @locks to all objects in the Master Room (usually #2) to prevent non-privileged players from triggering global commands.

Set the GUEST flag on the guest character template and ensure it is barred from using @create, @dig, or @open commands.

Populate the 'restrict_access' list in the config for sensitive attributes like DESCRIBE and ADESC to prevent unauthorized overwriting.

Populate the access.conf or equivalent file with known malicious IP ranges or open proxies to mitigate automated bot attacks.

Execute a full pass through the CG system to ensure attributes are correctly assigned and the character is moved to the starting room upon completion.

Check that the Global Parent object is correctly set in the config and that all +commands respond correctly from any room in the grid.

Test the Comsys (or @channel system) to ensure Public, OOC, and Staff channels have correct join/leave permissions and visibility.

Scan all objects with AENTER, ALISTEN, or AHEAR attributes for recursive calls that could cause a stack overflow or lag spike.

Verify that the +help system points to the correct database objects and that all +news files for theme and rules are populated.

Ensure every room on the public grid is @parented to a standard Room Parent to maintain consistent look, feel, and global exits.

Run a script or manual check to ensure all exits lead to valid destinations and that no 'dead-end' exits exist in the main hub.

Configure the 'player_start' or 'default_home' attribute to a valid, built room ID rather than the default Room #0.

Run @find to ensure all objects on the public grid are owned by a dedicated 'Building' or 'System' account rather than individual staff personal accounts.

Execute the engine's built-in dbck command to identify and prune orphaned objects or invalid location references.

Create a mandatory +policy entry detailing the game's stance on RPPV (Roleplay Prerogative and Victimization) and OOC consent.

Verify the staff ticketing system is functional, allowing players to submit requests and staff to track resolution status.

Ensure the +sheet command correctly pulls data from the U-functions or attributes set during character generation.

Implement code or policy that prevents IC (In-Character) information from being leaked into OOC (Out-of-Character) channels.

Apply the 'AUDITORIUM' or 'QUIET' flags where appropriate to manage spam in high-traffic roleplay hubs.