Check that the clues really point to one culprit and never to a wrong one

A mystery fails if two suspects fit all the clues, or if a clue is true of everyone but the real culprit. This entry checks both, finds the smallest sets of clues that still solve the case, and shows which clues the player cannot miss.

Why this works

A mystery is fair when the clues rule people out one at a time and the answer never contradicts any of them. Testing every combination of clues shows how little a player must find, not just whether the full set works.

When not to use it

Not suited to mysteries solved by a hunch, a confession or a scene the player must interpret, where clues are not neat facts. It also gets slow with many clues. For those cases, rely on playtesters who tell you where they got stuck.

In the full entry

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

Say this to your AI

Use the Spielerando entry "Check that the clues really point to one culprit and never to a wrong one" (read_entry mystery-clues-single-out-the-culprit) 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