Episode 3
When the reader gets a choice
Alex and Sam explore authored interactive fiction through inkle’s 80 Days and Ink’s documented design practices, asking how choices, constraints and consequences distribute authorship between writer, system and reader.
Alex & Sam · About 4 min
Minimise the player to keep listening while you browse. Autoplay continues through this programme; switch it off in the player.
Researched through 26/09/2026, 13:33:55 UTC. AI-generated conversation, reviewed before publication. Events may have developed since this recording.
The conversation
Alex
Sam
Alex
Sam
And the story can remember. Ink, inkle’s writing language, supports variables and conditional text. In plain English: an earlier decision can change what appears later. Two paths can also join up again. They don’t have to grow apart forever.
Alex
Good, because a completely separate story after every decision would get out of hand very quickly. Writer and designer Emily Short describes other structures: scenes selected because of what’s happened or what matters now, rather than an endlessly spreading tree.
Sam
Alex
There’s also a lovely imbalance here. Accounts of 80 Days describe a substantial amount of writing that any single journey won’t reveal. You see your route. The writer had to think about possibilities you’ll never meet.
Sam
Alex
Sam
Yes—the available actions put a boundary around your freedom. Emily Short’s discussion of player freedom makes that distinction useful: what can this particular world actually let you express? If there’s no way to apologise, wanting to apologise won’t conjure up a button.
Alex
Sam
Alex
Sam
Then maybe the better question is this: would you rather a story let you do anything, or give you a handful of choices you can’t stop thinking about? I’m much more interested in the second. Especially that button you wish you hadn’t pressed.
Sources & context
- 1. 80 Days - inkle's award-winning narrative adventure ↗
www.inklestudios.com · Publication date not confirmed
- 2. GDC Vault - 80 DAYS Post-mortem: Letting the Game Tell the Story ↗
www.gdcvault.com · Publication date not confirmed
- 3. Procedural Storytelling in Game Design ↗
wileywiggins.com · Publication date not confirmed
- 4. inky/app/resources/Documentation/WritingWithInk.md at master · inkle/inky · GitHub ↗
github.com · Publication date not confirmed
- 5. Beyond Branching: Quality-Based, Salience-Based, and Waypoint Narrative Structures – Emily Short's Interactive Storytelling ↗
emshort.blog · Publication date not confirmed
- 6. On Stephen Bond on Player Freedom – Emily Short's Interactive Storytelling ↗
emshort.blog · Publication date not confirmed
- 7. 80 Days (Meg Jayanth / inkle ) – Emily Short's Interactive Storytelling ↗
emshort.blog · Published 2014-08-05
Still open
- The roughly 3% figure and the 750,000-word script statistic are reported design figures, not independently audited production data. Source: s3.
- The review-based observations about 80 Days describe play and critical analysis rather than a complete technical specification; they do not establish that every player experiences consequences identically. Source: s7.
- The supplied sources do not establish the exact implementation of every route, variable, interruption, or consequence in 80 Days. Sources: s2, s4, s7.
- The supplied evidence does not establish that any single choice produces a wholly unique ending, nor does it quantify how often branches reconverge in the finished game. Sources: s2, s4, s5, s7.