Metlivi Blog

How to Avoid Fake Choices in Interactive Fiction

If you are writing a role-playing scene and want its choices to matter, trace each option to an observable consequence: a changed scene, a different response, or an action that becomes available or unavailable later. A choice can still use the same main plot route as the others, but if the options only rephrase the same action and nothing remembers the difference, it is cosmetic. Use the choice-to-consequence trace below to decide what to revise.

September 30, 20267 min readLeisure, Travel & City ExperiencesBy Metlivi Editorial Team
Section 1

What makes a choice cosmetic?

A choice is cosmetic when selecting between its options changes the wording but leaves the story situation and the player’s next actions effectively unchanged. The character might say “I agree” in one branch and “That sounds fine” in another, while the other character responds identically and the scene proceeds in the same way. The prose varies; the decision does not.

Cosmetic choices can serve a purpose when they let readers tune a character’s voice or role-play a small preference. The problem comes when the story presents one as a consequential decision—by highlighting a dilemma, asking for a commitment, or implying risk—and then behaves as though no distinction was made. Research on interactive narrative found that participants reported greater agency when choices led to different situational content than when they differed in non-situational ways. That supports a useful design test: look for a difference in what is happening, not merely a different sentence. Cardona-Rivera et al., “Foreseeing Meaningful Choices”

Section 2

Trace the choice through three moments

For every choice you want to feel consequential, write a compact trace with three entries: what the player does, what changes immediately, and where the story remembers it later. This makes a hidden or delayed effect visible to you as the writer, even if the reader does not see the entire outcome in advance.

For example, at a community garden, a character asks the player to help prepare the weekend seed table. The options are to sort the seed packets together or make a clear planting chart first. The immediate actions differ. Later, when a visitor asks what to plant in a shady corner, the character can point to the chart in one version, while in the other the player can offer a packet they sorted. These outcomes are modest, but each choice changes what the scene can refer to and which response feels natural.

Use a small ledger as you draft:

Option: Sort packets together; Immediate action: The player groups seeds by label; Later callback or available action: Offer a matching packet to the visitor

Option: Make a planting chart; Immediate action: The player records where seeds grow best; Later callback or available action: Check the chart to answer a question about shade

The table is an illustrative design aid, not a research finding. Its value is that it forces each option to connect to a later piece of content. If you cannot fill the last column with a specific scene, response, or action, either add a callback or present the choice as a low-stakes variation in voice rather than a major fork.

Section 3

Make the options legible before the click

Readers need enough context to understand what kind of decision they are making. That does not mean revealing every later plot detail. It means showing the immediate goal, the likely cost or limitation, and the distinction between the approaches. Choice of Games’ guidance on intentional choices recommends signaling likely story results and differences in difficulty, especially when an option could have a negative result. “How to Write Intentional Choices”

Compare “Take the chart” and “Take the seeds.” Those labels name objects but give little reason to choose. More legible options might be “Bring the chart so you can answer planting questions” and “Bring seed packets so visitors can choose what to take.” Each signals a purpose. Neither needs to promise a precise later outcome; the following scene can still surprise the reader.

Keep the options parallel in the information they offer. If one explains its purpose and the other is vague, the reader may be unable to judge whether the difference is intentional. Where outcomes are uncertain, signal the uncertainty through the scene: perhaps the character says the chart is incomplete, or that the seeds have not yet been sorted. The aim is for readers to choose with an intention, not guess what the writer had in mind.

Section 4

Carry consequences forward without multiplying branches

A meaningful consequence does not require every option to launch a separate storyline that never rejoins. Branches can meet again after a distinct exchange or action, while a later scene preserves a detail from the earlier choice. The ink documentation describes branching and rejoining as part of its basic story structure, and Choice of Games discusses delayed branching as a way to let earlier decisions affect later outcomes without immediately splitting the plot into ever-larger routes. ink, “Writing With ink” and “By the Numbers: How to Write a Long Interactive Novel That Doesn’t Suck”

For a small project, track a few clear facts rather than every line of dialogue. The seed-table choice might set a simple flag such as made_chart. When the visitor arrives, the story checks that fact: if true, the player can consult the chart; otherwise, they can offer a seed packet. This is a fictional illustration, not a requirement to use variables or any particular tool. A remembered object, a changed relationship, or a callback in the prose can serve the same narrative purpose.

A useful constraint is to promise only consequences you can actually write and test. If a choice affects a later scene, make sure the later scene has a distinct line, response, or available action for that state. If several old choices all feed into one broad trait, define what that trait means in the story and show it changing something the reader can notice. Choice of Games notes that delayed-branch systems create authoring complexity; keeping the tracked facts few and relevant makes their advice workable at a scene level.

Section 5

Distinguish a small consequence from no consequence

Not every decision needs to alter the main plot or lock away content. A brief acknowledgment can establish that the story remembers: a character thanks the player for making the chart, or asks whether they still have it. That is a small consequence, but it is observable. By contrast, silently changing a variable that never affects dialogue, events, or options does not give the reader evidence that the choice mattered.

When reviewing a choice, ask: “Could I tell which option the reader chose by looking at the next scene?” If the answer is no, find a natural place for the distinction to surface. The answer might be a changed prop, a character’s response, an extra question the player can ask, or a different way to complete an ordinary task. Avoid adding a callback just to tick a box; it should fit what characters know and what they are doing.

Then ask whether the difference fits the promise made by the choice. A small preference can lead to a small response. A choice framed as deciding how to prepare for an important event should have a proportionate effect on that preparation. This calibration helps readers understand both the scale of the decision and the scale of its payoff.

Section 6

Run a choice-to-consequence pass

Before polishing the dialogue, review the scene in this order:

Name the decision. In one plain sentence, say what the player is choosing between: two goals, methods, commitments, or priorities.

State the immediate difference. Write down what the character does in each option. If the actions are identical, revise the options or label them as a deliberate voice choice.

Mark what the reader can foresee. Add enough context to make the alternatives understandable, including relevant effort, limits, or uncertainty.

Choose a later payoff. Identify a specific callback, reaction, scene detail, or available action that depends on the decision. It can be small, but it should be readable in the story.

Check both routes. Read the next scene on each path. Confirm the remembered detail appears in the right branch, that both versions make sense, and that no option promises an action the story does not provide.

This pass turns “make choices meaningful” into a concrete editing task: connect what the player selects to what the story does, then make that connection visible at a scale appropriate to the decision. The plot may converge again, but the reader should be able to recognize the trace of their choice in a later scene or action.

Related reading

Keep exploring this topic