A Character Relationship Map Is Not Enough: What Each Person Knows, Conceals, and Misunderstands

A relationship map only shows who is connected to whom; it cannot explain what makes the suspense work. An interactive story also needs an information gap matrix: which facts each character knows, where they learned them, what they deliberately conceal, what they mistakenly believe, and under what conditions they are willing to speak. Often, players’ choices change the flow of information rather than the events themselves.

An information gap matrix can solve three problems at once: it helps writers avoid characters suddenly becoming omniscient, helps actors understand the layers of concealment, and tells the code which conditions each piece of dialogue requires.

Do not start directly with character secrets. First, list the events that actually occurred in the story world, and assign each fact a stable ID. For example: the accident recording came from the server; Zhou Lan deleted the public copy; Chen Mo kept a local cache; the call from the future was simulated by a model.

The facts table records only the truth behind the scenes; it does not mean the player will necessarily see it. It is the baseline for judging whether characters’ statements are true or false. If the truth changes depending on the route, specify which condition changes the world state, rather than choosing an answer at the last minute in the ending.

“Knowing” means the character has sufficient reason to confirm a fact. “Suspecting” means a judgment formed from limited signs. “Concealing” means knowing something but being unwilling to disclose it. “Misunderstanding” means an incorrect conclusion the character sincerely believes.

These four categories produce different performances. Someone concealing information may avoid details, while someone who misunderstands will speak with conviction. Players also identify the two differently: the former is exposed through pressure and evidence; the latter needs new facts to correct the misunderstanding.

In Midnight Callback, Chen Mo knows the local cache exists, suspects his supervisor altered the accident records, conceals that he once copied the data, and mistakenly believes the call from the future comes from a survivor. These four states support branching better than “Chen Mo has a secret.”

A character cannot know something simply because the plot needs them to. Add “time acquired” and “source” to the matrix: witnessed firsthand, told by someone else, system records, inference, or fabrication.

Timing is especially important. Zhou Lan learns that the investigation has been exposed only after the player reports it to the police, so she cannot take precautions in advance in an earlier shared scene. If a character acquires the same fact at different times on different routes, later dialogue should also read the corresponding state.

The matrix does not need to contain every line of dialogue. Record only information that can change judgments, relationships, routes, or endings.

The player does more than receive secrets. They can choose which clue to tell which person, whether to disclose its source, and whether to test a character with false information. Information sharing itself should be recorded in the state.

For example, giving the recording to Chen Mo gains technical help, but also tells him how much the player knows; giving it to Zhou Lan may secure access permissions, but also gives her an opportunity to destroy evidence. The same clue creates different risks depending on where it goes.

This makes it possible to create meaningful branches with a small amount of material: the event’s location stays the same, but changes in the knowledge and attitudes of the characters present alter the dialogue and available actions.

Shared scenes are especially prone to characters ignoring earlier information. For each convergence point, list the “minimum shared knowledge” and “conditional inserts.” Shared dialogue can refer only to content known on every path; supplement route-specific facts with brief dialogue, interface records, or reaction shots.

If conditional inserts keep multiplying, the scene is not suited to complete convergence. At that point, split it into two state-dependent versions instead of using dozens of conditions to piece together dialogue that cannot be performed.

Ask testers to write down what each character knows, whom they are deceiving, and what they might misunderstand. Mistakes do not necessarily indicate a problem, but if players interpret a sincere misunderstanding as lying for no reason, or cannot explain how someone learned a crucial fact, you need to add sources and performance cues.

Then read the script from each character’s perspective, covering up information they should not know. Rewrite any lines that still fail to make sense. Only after the information gaps are stable can the next article discuss how to plant clues without relying on unfair concealment.

The matrix can also reveal “secret overload.” If every character conceals three things unrelated to the main storyline, players will lose sight of what matters when making judgments. Prioritize secrets that can change actions, relationships, or themes; background information used only to create an atmosphere of suspense can be downgraded to optional material.

Before filming, convert information states into acting notes, but do not simply write “you are lying.” A more specific note would be: the character knows the access credential was copied and fears the player will ask about its source, so they answer about the timing while avoiding who used it. This lets actors convey information gaps through pauses, eye movements, and wording, and tells the editor which reactions must be retained.

If world facts change during revisions, update the facts table first, then check every character cell, disclosure point, and ending. Do not change only the scene that reveals the truth, or the earlier scenes will still retain the old version’s logic.