Did testers solve the mystery from the clues, or by guessing the culprit?

A correct accusation looks like success, but a lucky one teaches you nothing about your clues. This entry separates solved-by-reasoning from solved-by-luck, finds the clue that people miss most, and spots the testers who had the clues and still failed.

Why this works

A right answer can come from reasoning or from a lucky guess, and a wrong one from missing clues or from clues that mislead. Tracking which clues each person actually held sorts the four cases and points at the clue that is hardest to find.

When not to use it

It adds little when the mystery has no fixed solution, or when clues are meant to be understood in a flash rather than collected, as in a short puzzle. Then ask players to explain how they decided.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 3 common mistakes and the fix
• 30 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 "Did testers solve the mystery from the clues, or by guessing the culprit?" (read_entry mystery-solved-by-clues-or-luck) 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