Metlivi Blog

How to Keep a Mystery Fair When Players Explore Scenes in Different Orders

When players visit scenes in an unexpected order, keep the mystery fair by separating its fixed facts from the route through which they learn them. Decide what happened, prepare several clues that can reveal each essential conclusion, and connect scenes with multiple leads. Then let players follow those leads in their chosen order, adapting clue delivery without changing what the evidence means.

October 09, 20268 min readReading, Arts & CultureBy Metlivi Editorial Team
Section 1

Decide what is true before deciding what happens first

Write the solution in a few plain sentences: what happened, who was involved, what they wanted, and what evidence their actions left behind. Treat those as the mystery’s fixed facts. Scenes are places or conversations where the characters may learn those facts; they do not need to form a fixed sequence. This distinction gives players room to explore while keeping the answer coherent.

For example, suppose the clockmaker’s apprentice secretly replaced the town hall’s ceremonial bell with a lighter copy so it would sound at the wrong time. The apprentice’s motive, the swap, and the bell’s altered weight are facts. The workshop, the town hall, and an interview with the bell ringer are possible scenes. Players might reach the workshop first, but that changes when they learn about the swap—not whether it happened.

This approach follows node-based scenario design: prepare locations or encounters as connected nodes, with clues pointing between them. The Alexandrian describes how redundant clues can preserve forward movement as players move between nodes in different ways. Node-Based Scenario Design Part 2: Inverting the Three Clue Rule

Section 2

Name the conclusions the players need to reach

List the essential conclusions, not every detail you hope the group will notice. A compact mystery might need players to determine that the bell was replaced, identify who had access, and discover where the original bell is hidden. These are different questions, so each needs support of its own.

For each conclusion, prepare multiple clues that point toward it through different routes. The Alexandrian’s Three Clue Rule proposes at least three clues for each conclusion the characters need to make. This is a useful redundancy guideline, not a mathematical guarantee: players can miss, misunderstand, or overlook several clues. The practical benefit is that one missed scene or misread detail is less likely to stop the investigation. Node-Based Scenario Design Part 2

Vary how clues communicate. The workshop’s repair ledger might show a sudden order for lightweight metal; the bell ringer might recall that the bell sounded unusually thin; and a delivery note might place a suspicious crate at the town hall. These clues support the replacement theory through a record, a witness, and a physical detail. Repeating the same sentence three times in different rooms creates less useful redundancy.

Section 3

Connect scenes with leads, not required steps

Draw each scene as a node and connect it to other scenes with leads: information that gives the group a reason to visit another place or speak to someone. A lead might be a name in the ledger, an address on a delivery note, or a witness’s mention of the town hall’s storage room.

A clue and a lead are related but not identical. Pelgrane Press distinguishes a lead, which points to another scene, from a core clue, which is necessary for the mystery to progress; some core clues provide important information without directing the characters to a new scene. Keeping the categories clear helps you tell whether a detail is essential, merely useful, or simply flavor. Clues vs. Leads

Check the diagram for bottlenecks. If every path to the hidden original bell runs through one interview, then that interview is a required step even if players have several ways to reach it. Add another route, or make the essential fact discoverable through a different scene. GUMSHOE’s scenario guidance recommends avoiding hard-sequenced core clues and checking scene diagrams to see whether core and alternate scenes can be approached in more than one way. Rules: Gumshoe SRD

Section 4

Make essential information robust to missed rolls

In many games, a failed roll can make a clue harder to obtain. Be careful when the clue is the only route to a necessary conclusion: failure there can stall the scenario for reasons unrelated to the players’ reasoning. Consider making essential information available through another credible action or scene, or use a failure that changes the cost, timing, or complication while still letting the investigation proceed.

This does not mean every search must reveal everything. Optional clues can add background, narrow the suspect list, or make a theory more convincing. The useful distinction is whether the information is required for progress or enriches it. GUMSHOE’s published guidance treats core clues as information needed to move through the scenario and advises that plausible alternative methods can yield the information. That is a design approach to adapt to your game, not a rule every system must use. Rules: Gumshoe SRD

Section 5

Let scene order change the experience

When players reach a scene early, give them what their actions plausibly uncover there. Avoid making a location mysteriously empty just because your notes expected it later. If the group visits the storage room before interviewing the bell ringer, they might find the lighter bell and a fresh scrape on the floor. That evidence can raise new questions, while the later interview supplies context about the unusual sound.

Keep clues consistent, but allow their meaning to develop. A scrape can indicate that a heavy object was moved; it need not identify who moved it until another clue connects the room to the apprentice. If a player makes a plausible deduction from evidence they already have, accept the deduction as a possibility in the fiction. The next scene can test or refine it rather than force the group back onto a planned route.

Track which facts the characters have learned, which leads they have followed, and what remains uncertain. A simple note with three columns—fact, evidence found, open question—can prevent repeated clues from accidentally changing meaning when scenes happen out of order. Record what the players actually know, not just what their characters could have learned in the planned version.

Section 6

Use flexible clues without changing the solution

For each scene, prepare its purpose and a few likely clues, then leave room to place an essential clue where the players’ choices make sense. GUMSHOE describes floating core clues that can appear in any of several suitable scenes, with the GM choosing when to introduce them. Used carefully, this can help maintain pace when a necessary connection has not surfaced. Rules: Gumshoe SRD

For instance, if the players investigate the delivery company before they inspect the town hall, a clerk might produce the same delivery record you had planned for the town hall office. The record’s meaning stays stable; its location in play changes. Use this flexibility when the clue could credibly be found in either place. Do not move evidence in a way that contradicts earlier details or makes player choices feel irrelevant.

A flexible clue is not a license to guarantee the players’ favorite theory. If they suspect the bell ringer, let them investigate that possibility, then use evidence to confirm, complicate, or rule it out. Fairness depends on the group being able to reason from information they receive, not on every suspicion proving correct.

Section 7

Review the mystery from several possible routes

Before play, trace a few different paths through your scene map. Start with each likely first scene and ask: What can the players learn here? What new scene could that information lead them to? If they skip the scene I expected, can they still reach every essential conclusion through other clues?

A quick audit can catch fragile points:

This review does not predict every player choice. It checks whether the scenario has enough coherent routes to respond when the group chooses differently from your outline.

Circle every essential conclusion and list the clues supporting it. Add a distinct clue if a conclusion depends on one easily missed detail.
Mark scenes that contain the only clue to a required next step. Add another route or make that clue available in a suitable alternative scene.
Check whether each clue is consistent with the underlying facts and whether its source can plausibly know it.
Identify optional details and decide what they add, so missing them does not block the central mystery.
Section 8

Keep the ending open to the investigation

Prepare what the characters must establish or do to reach a satisfying resolution, but do not require them to arrive there through one prescribed chain of scenes. If they discover the apprentice’s role early, let the remaining evidence shape what they do next: locate the original bell, confront the apprentice, or check whether another person helped. The resolution can respond to what they have learned and chosen.

A fair mystery rewards attention and lets evidence matter. Its facts remain dependable; its clues offer more than one route; and its scenes accommodate the order the players create. Prepare that sturdy structure, then follow their investigation as it unfolds.

Section 9

Sources

“Node-Based Scenario Design Part 2: Inverting the Three Clue Rule,” The Alexandrian — https://www.thealexandrian.net/creations/misc/node-design/node-design2.html
“Clues vs. Leads,” Pelgrane Press — https://pelgranepress.com/2020/02/21/clues-vs-leads/?src=PPTW
“Rules,” Gumshoe SRD — https://gumshoesrd.opengamingnetwork.com/rules/
Related reading

Keep exploring this topic