Immortals checklist for MUDs

Cross-reference the command table in the source code with the staff rank table to ensure 'force', 'set', and 'shutdown' commands are restricted to the Implementor level.

Confirm that when an Immortal logs in, their 'wizinvis' or 'incognito' level defaults to a value high enough to remain hidden from players of lower rank.

Verify that Implementor and high-level Administrator accounts are restricted to specific IP ranges or require multi-factor authentication if supported by the telnet wrapper.

Ensure staff-only rooms (Immortal Lounges) have hard-coded VNUM checks or flags that prevent players from being summoned or 'transferred' into them by lower-level staff.

Test that staff characters cannot use 'set' or 'advance' commands on their own character objects or mortal-alt characters.

Confirm that every command executed by an Immortal above level 50 is piped to a permanent 'wizlog' file that cannot be deleted via in-game commands.

Ensure that when a staff member uses 'snoop' on a player, an automated log entry is generated in the administration channel to prevent unauthorized surveillance.

Test the 'load' or 'mload' commands to ensure every item or mob created by an Immortal is logged with the VNUM and the creator's name.

Verify that the 'ban' command requires a mandatory 'reason' string and that this string is correctly written to the persistent ban-list file.

Confirm that 'tell' or 'page' commands sent to staff are logged in a separate buffer to document player reports and staff responses.

Assign and hard-lock VNUM ranges to specific Builder accounts to prevent accidental overwriting of existing world data.

Confirm that the 'asave' command is restricted so Builders can only save area files within their assigned VNUM range.

Ensure all new areas under construction are flagged as 'PROTOTYPE' or 'OFFLINE' to prevent player entry via random teleport or 'where' commands.

Run the area-check script to verify that any new mobs created by Builders do not exceed the server's gold-per-kill or experience-per-kill caps.

Confirm that the automated server backup script includes the /area or /lib/world directories every 6 hours.

Verify that the 'gecho' or 'gmsg' command correctly parses color codes and does not cause client-side crashes for players using legacy terminal emulators.

Test the 'switch' command to ensure that if a staff member loses connection while possessing an NPC, the NPC does not remain 'frozen' or 'invincible'.

Audit the 'at' and 'transfer' commands to ensure staff cannot move unique quest items into player inventories without a logged event-ID.

Confirm that 'no-recall' and 'no-summon' flags are active in event zones to prevent players from bypassing event mechanics.

Verify that the 'purge' command used in an event room only affects the current room and cannot accidentally clear the entire world buffer.

Ensure the 'help staff' and 'help rules' commands provide the current version of the Immortal Code of Conduct.

Verify that all Immortal accounts have their 'mortal-alt' names registered in the internal staff database for conflict-of-interest tracking.

Verify that every new 'Helper' or 'Guide' has completed the 'Basic Commands' tutorial on the test server before receiving production bits.

Confirm that a 'complaint' command exists for players to send encrypted logs directly to the Implementor, bypassing mid-level staff.

Ensure the 'immtalk' or 'wiznet' channel is completely invisible to players using 'snoop' or 'social' commands.