Branching story structure: the five shapes behind most interactive stories

Why the shape comes first

A story where every choice opens two new paths doubles at each step. Ten choices deep, that is 1,024 endings, and nobody writes 1,024 endings. Every pattern below is a different answer to that arithmetic: stop the paths early, fold them back together, let the reader wander, or keep one path and make it remember.

The names are the ones interactive fiction writers use with each other, and they are loose. Treat them as sketches, not rules. Most finished works mix two or more.

Time cave

In a time cave, every choice opens a branch that never rejoins the others. Node 1 splits into 2 and 3, node 2 splits into 4 and 5, and nothing ever comes back together. Draw it and you get a tree with a great many leaves.

The upside is that every choice visibly changes the story, and replays feel very different from each other. The cost is depth. Because the paths multiply, each one has to stay short, and most of what you write is seen by a small slice of readers.

Use it for short comic or horror pieces where the fun is in the spread of outcomes. I would not use it for anything that needs a character to change over time, because no single path is long enough for that to happen.

Gauntlet

A gauntlet is one main road with side paths that either end quickly or rejoin almost at once. Node 4 offers three doors: two end the story within a scene, one carries on. The plot stays tightly authored and the word count stays low.

The risk is that the story starts to feel like a test with right answers. Readers stop asking what their character would do and start asking which option the author wants. The fix is to make side paths pay out something other than death: a clue, an ally, a scar that comes up later.

It suits thrillers, survival stories and anything where danger is the point.

Branch and bottleneck

Here paths spread out and then meet again at key scenes. Between those meeting points the reader can take very different routes, and what changes at the bottleneck is what they carry into it: knowledge, items, a relationship.

A worked example. Act one splits three ways, to the docks, the archive or the governor's party. All three arrive at the trial in node 12. Only the docks route finds the ledger, though, so node 12 has a paragraph that appears only if the reader holds it, and the verdict can turn on that paragraph.

This is my default shape for anything story-led. Every reader sees the big scenes, the word count stays sane, and the routes still feel distinct. The failure to watch for is a bottleneck that ignores where the reader came from: if node 12 reads the same from every route, the first act's choices were decoration. The step-by-step version of building one is in how to write a choose your own adventure.

Open map

An open map has a hub, a central place the reader keeps returning to, with spokes they can visit in any order. Picture a manor with five rooms. The study stays locked until the key turns up in the greenhouse, and the cellar only matters once the reader has heard the housekeeper's story.

It gives the strongest sense of freedom, and it suits mysteries, heists and any setting worth exploring. The weak spot is pacing. Without pressure the reader drifts, so give the hub a clock: a dinner at eight, a storm that cuts the road, or a set number of rooms before the next act begins.

State tracking

State tracking is less a shape than a layer you put on top of one. The story keeps a few named values, such as trust, items or decisions made, and changes the text according to them. You can have very few branches and still get replays that feel different.

trust_ansel = 0
has_ledger = no

node 7   show Ansel the ledger?   yes: trust_ansel + 1
node 9   cover for Ansel?         yes: trust_ansel + 1
node 12  if trust_ansel is 2, Ansel backs your story
         otherwise Ansel stays silent

Two choices, no extra branches, and the trial plays out differently. The cost is testing: every yes-or-no value doubles the situations a reader can arrive in, so keep the list short. Choice of Games writes its interactive novels in its own scripting language, ChoiceScript, and inkle's free, open-source ink language was used for games like 80 Days. Both are built around this kind of memory. How to make the values pay off is the subject of choices that matter.

Which pattern should you use?

The short version, as a grid. Writing cost means words per reader experience, not total words.

Mixing patterns

Real projects rarely use one pattern. A mix I come back to often: chapter one is a short gauntlet that teaches the reader the story bites. Chapter two is a hub, with three locations in any order. Chapter three is a bottleneck that leads to one of three endings, picked by what the tracked values say about the reader.

Sketch the mix on a single page before writing. If you cannot point to where the paths meet again, you are building a time cave by accident.

And if you want to feel how an unmapped story behaves, the branching story generator works the other way round: there is no map at all, and each scene is written from the choice you just made. It is a useful contrast when you are deciding how much structure your own project needs.

Questions