Give evidence its minimum supported conclusion
NovelToGame separates world facts, character beliefs and player knowledge. Evidence has a visible carrier and a minimum supported conclusion. Establish consistent facts before discovery instead of changing the culprit when players guess.
Original example: an office spare key is missing, and the player finds a ticket stamped last night. It supports issuance of a ticket for a sailing, not proof that its holder boarded or took the key.
Replace an automatic accusation with stamp inspection, questions to the issuer and comparison with the night log. The player now performs the judgment rather than collecting an author-supplied answer.
Connect observation to action
| Clue | Direct support | Unresolved | New action |
|---|---|---|---|
| Ticket stamp | Issued for last night’s sailing | Who used it | Question the issuer |
| Night log | Someone delivered a bag | Contents | Ask recipient and witnesses |
| Hook wear | Key was removed | By whom and why | Compare custody records |
| Proxy arrangement | Temporary custody allowed | Whether it was returned | Ask for its current location |
Avoid hiding every clue behind arbitrary clicks. The current question should guide observation and inquiry, and each discovery should make new actions intelligible.
Keep knowledge permissions consistent
Finding the ticket does not inform everyone. Showing it publicly changes witnesses’ knowledge and may force a concealed actor to adapt. Private checking preserves different knowledge boundaries. Carry that difference into behavior.
For a lie, record what the speaker knows, what they protect and which evidence changes their strategy. Testimony is a claim, not automatically fact. A reveal can establish that a ticket changed hands, but needs a supported basis rather than a convenient new person at the ending.
At shared scenes, read selected history for dialogue and questions. Do not assume every route collected all evidence.
Review the evidence along a first-play path
Hide the author’s answer and follow only available information. Before a decisive judgment, are necessary clues accessible? Can mistaken inference receive a readable correction? Does the result trace to actual observations and questions?
If only the author knows the answer, add accessible evidence or weaken the conclusion. If one clue gives everything away, retain its minimum meaning and let another observation create comparison.
Play different orders in the prototype and check knowledge and branch isolation. Fair inference does not mean immediate universal success; clarity and enjoyment require play feedback.
FAQ
Do more clues make a better mystery?
Not necessarily. Each clue should change a judgment, question or action. Merge decorative repetitions; a smaller set with comparisons and consequences can create a clearer experience.
Do it with the skill
Ask game-world-design to separate clue carriers, minimum conclusions, uncertain explanations and available actions, then check knowledge and reveals along a first-play path.
Read the method: Evidence, knowledge boundaries and reveals