See which rooms, quests and characters your testing never touched

After a long test session you feel that you saw everything, but the log may say otherwise. This entry shows how to compare what the game contains with what was visited, list what was missed, and show a percentage that does not claim a full run when one item is missing.

Why this works

Memory of a test session is generous: it remembers the rooms it liked. A complete list of what exists, set against a record of what was actually entered, gives an honest gap, and rounding down keeps one missing item from hiding behind a full-looking number.

When not to use it

Having visited something is not the same as having tested it. A room entered once may still be broken in its fifth use, and coverage says nothing about how well anything works. Use it to find blind spots, then test those deeply by hand.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 3 common mistakes and the fix
• 32 lines of example code with 4 checks that pass
• How your AI shows you that it works

Say this to your AI

Use the Spielerando entry "See which rooms, quests and characters your testing never touched" (read_entry playtest-coverage-of-rooms-and-quests) in my game. Build it step by step, and show me how you checked that it works.

Or skip this and connect the MCP: your AI then finds all of this by itself.Connect the MCP