Questing & Storylines checklist for MUDs

Verify that all quest variables (qvars) persist through a warm reboot and a full cold server restart.

Audit mobprogs and scripts for recursive triggers that could cause infinite loops or CPU spikes when multiple players interact with an NPC.

Check that all quest-specific items, mobs, and rooms use unique VNUMs within the assigned area range to prevent data overwrites.

Ensure that failed or abandoned quests trigger a cleanup script to remove temporary quest items and reset NPC states.

Monitor server memory usage while repeatedly triggering quest scripts to ensure dynamic strings are properly freed.

Test every word highlighted in mob descriptions or dialogue to ensure they trigger the correct 'ask' or 'say' response.

Review all quest text on a standard 80-character width terminal to ensure no words are clipped or awkwardly wrapped.

Map all dialogue tree branches to ensure no terminal 'dead ends' exist where a player cannot progress or restart.

Verify that NPCs provide a summary of current objectives if a player returns to them mid-quest.

Cross-reference quest dialogue against the world lore wiki to ensure NPC names, dates, and locations are historically accurate.

Attempt to turn in quest objectives multiple times to verify the script checks for item possession and state completion.

Calculate the total XP reward against the average time to complete the quest; ensure it does not exceed the MUD's standard leveling curve.

Verify that unique quest rewards are flagged as 'NO_DROP', 'NO_GIVE', or 'NO_AUCTION' to prevent unintended economy flooding.

If the quest requires a gold buy-in, verify the currency is actually removed from the player's inventory before the quest proceeds.

Compare quest equipment stats against existing endgame gear to ensure the new items do not render current content obsolete.

Verify that if a quest requires a mob kill, all members of a group receive credit toward their quest state.

Adjust quest-critical mob respawn timers to prevent 'bottlenecking' where players must wait in queues to progress.

If using instanced rooms, verify that players from different instances cannot see or interact with each other's quest objects.

Ensure quest-critical items dropped by mobs are protected so only the player/group on the quest can loot them.

Verify that 'World Quests' correctly update global variables without causing race conditions between simultaneous completions.

Check the 'quest log' or 'tasks' command at every stage to ensure the description matches the current objective.

Follow every directional hint (e.g., 'Go south to the river') to ensure the map layout matches the narrative instructions.

Verify that ANSI color codes for quest items, NPCs, and locations follow the game's global style guide for readability.

Verify that players below the intended level are warned or prevented from starting quests that will result in unavoidable death.

Test the 'hint' or 'help quest' command for the specific quest to ensure it provides actionable advice without spoiling the solution.