Article Index

Reusable locations

False leads are an inevitable part of investigative adventures, and a false lead created by a player's misinterpretation is equivalent to one deliberately presented by the GM. The clues above can apparently lead anywhere. How can we limit that effect? Primarily by limiting the environment available for exploration. If the adventure takes place on a ship or train, in a village or on a noble's estate, and we know nobody could have left, we have already defined the accessible locations. This also means that checking any clue or false lead must not take the characters outside the established playing area. Every clue and every false lead must be checkable within it, usually by comparison with other clues—for example, checking an alibi by questioning a witness. We have many clues but considerably fewer locations and NPCs, so we necessarily build on the same location or NPC at several points. Let us use a village cut off by flooding as the adventure's available playing area.

You cannot ask witness A whether B's alibi is true until you have heard the claim to be checked. It is therefore natural for characters to go from witness A to suspect B, then verify B's alibi by questioning A again. Ideally, checking the alibi might also establish that B arrived a little before C and left after C. We now have information about C's whereabouts that several other witnesses may confirm. If we know C was in the pub, we will not believe his claim to have seen his wife D at home the entire time. C's testimony is a planned false lead. 

If nobody asked him to give false testimony and he is doing it only out of love and to protect his family, that does not in principle make it a particularly strong clue yet, especially before questioning his wife and the neighbors. The wife may have been home without witnesses, home according to the neighbors too, or perhaps in church before a hundred witnesses. Of course, she may have been at the murder scene, either as the perpetrator or as a witness terrified nobody would believe her against X. A conclusion drawn too early can be another false lead introduced by the players on top of a planned one. Half of investigation is not finding clues, but filtering out false information.

At C and D's home, one scene might involve the group secretly searching it, another questioning C there, another questioning D. Or questioning a neighbor at the fence. You can use the home's description, illustrations, and maps on any occasion. C's description also works whether he is at home or in the pub. 

Designing adventures with reusable locations

When you intend to use a location only once, you roughly know what will happen there and when and where the adventure leads next. If you use it repeatedly, however, it will host a number of events unknown even to you. For every location, you need to know who is usually there and when. Those people's personalities must include how they react to events and repeated questions: you see NPCs change, and the location may develop alongside them. Normally, a location and the characters appearing there are presented together in an adventure module. In a good investigative adventure, however, people move around and their behavior changes. That means a separate NPC chapter, separate information on locations, separate information on events, and again separate information on clues. 

At every location, indicate who and what events may appear and what clues may be present. NPC descriptions also include where they usually are and when, what events involve them, and what they know. This is therefore much less continuous prose than a database with many-to-many relationships, a “pile of case files.” Because of the many cross-references, I generally recommend the GM have at least a tablet or another electronic device. I often prepare adventure modules in OneNote with many cross-references. For the clues advancing the adventure, I also indicate where and how they can be obtained. The principal tool for this is the clue repository or clue pyramid. 

Clue repository or clue pyramid

To be honest, I use a multilevel clue repository: a clue pyramid. In more extreme cases, I place proven or provable facts at the top, with leads below them, and below the leads, direct and indirect evidence. Solving an adventure might require proving three of five important provable facts. Each fact might have three good leads and one misleading false lead. I can assign, say, three useful and one useless piece of direct evidence to every lead. Three or four pieces of indirect evidence can help locate every piece of direct evidence. And each piece of evidence may have many sources. Many people can confirm that B really was in the pub, for example, or that two NPCs are probably secretly in love. Likewise, there may be several witness statements.

The five provable facts always include the “holy trinity” of motive, opportunity, and the murder weapon or instrument—or another object clearly linking the character to the murder. A confession belongs here too. The fifth “provable fact” is a story or scenario the prosecutor can present. Yes, if there is a recording of the incident, witnesses, and so forth, this means that recording. But it still has to be proved that the character is the person on the recording, so it is not a single “trump card” and solution either. A credible narrative may be built even on a few pieces of indirect evidence; player characters can easily skip levels.

The player characters find a bloodstain. They do not know when or how it got there. This is indirect evidence. If clues found at the scene and perhaps elsewhere establish that it is probably the murderer's blood, it immediately becomes direct evidence. Blood type and much else help identify people in a database, from which some legwork can lead to the right person. This is now a lead. If the lead points in the right direction, excellent. If the very person who committed the crime is the one with no records and whom you cannot find, it is a planned false lead. Even a lead pointing in the right direction is still not enough for a conviction. Despite a strong link to the incident, the person can readily say they were framed and the evidence is false. A narrative can easily be built around the story so far, but it would collapse at trial. At least one of motive, opportunity—the lack of an alibi, and so on—and a confession is needed. 

But not all investigative adventures are created equal. One of the most highly rated crime series, The Wire, essentially follows an investigation of the same criminal group across five seasons. Programs on Investigation Discovery or ID Extra also concern investigations lasting months. If you want Columbo- or CSI-style investigations, one episode per case, you need to reduce the amount of required evidence and the number of false leads. With more than a hundred elements, and solutions played out for perhaps an hour or two per element and per source, exploring the four-level clue pyramid above works when investigation is central to an adventure played over an extended period. If direct evidence provides not merely a lead but an already usable fact, establishing motive, opportunity, or means, for example, the pyramid becomes smaller and the adventure shorter. 

Designing locations

If you describe a vase as standing at the left end of a ledge on one occasion and at the right end on another, the characters may not necessarily notice. But if you build the same location as a map in Campaign Cartographer 3 or an image in DAZ Studio, and they have examined and interacted with many things so the image is fixed in their memories, they have a very good chance of noticing the change. Metagaming may not be nice, but if you want to help the characters with a little cheating, the players can become aware that you are using a different picture. 

Perhaps the image is on different paper, you swap images printed on transparencies, or take it from another folder. They cannot directly bring that information in character, and they would look around anyway and might notice. The player who spots it will even be proud of themselves. They will think not of cheating, but of the neat hidden clue they noticed. When making images in DAZ Studio, I often change the visibility of certain objects and rerender only what changed. With Campaign Cartographer maps, putting the change on a separate layer can likewise help. Consistency matters here too, however. Do not move only the thing that is a clue; show the natural rearrangement of place settings, chairs, and many other small details as well. Let the group discuss which of the seven or eight differences they see might be clues and which are not. 

So a single location can involve many scenes, many NPCs, and even more clues.