BEFORE THE STORY BRANCHES
Whether you are outlining your first three-thousand-word hypertext short story for the Interactive Fiction Competition (IFComp) or restructuring a sprawling game script, these nine questions address the practical knots every branching narrative designer encounters.
1. Which open-source tool should I start with: Twine, Ink, ChoiceScript, or Inform 7?
Match the tool to your narrative rhythm. Start with Twine (specifically the SugarCube or Harlowe story formats) if you think spatially on a visual canvas of connected nodes and want standalone HTML export. Choose Inkle's Ink if you write fast-paced, line-by-line conversational weaves where branches merge every few sentences. Pick ChoiceScript for stat-driven, novel-length chapter structures, or Inform 7 if you want to build a spatial world model where readers type natural-language commands.
2. What is the difference between playthrough length and total word count?
Total word count measures every word in your source file across all mutually exclusive paths. Playthrough length measures the words a single reader encounters from opening scene to credits. A healthy ratio for a replayable Branch-and-Bottleneck story is roughly 3:1 or 4:1—meaning a 100,000-word manuscript yields a 25,000-to-33,000-word single reading experience.
3. Should I write interactive fiction in second person ("you") or first person ("I")?
Second person present tense ("You unlock the brass gate") is the classic interactive standard because it treats the prose as a conversation between the narrator and the reader. However, first person ("I never trusted the harbor master") is highly effective when writing a defined protagonist with a distinct voice—just frame the choices as the protagonist's internal deliberations.
4. How do I stop my branching outline from growing out of control in Act II?
Schedule mandatory bottleneck events before you begin drafting. Decide in advance that regardless of how the protagonist investigates the manor in Chapter 2, the dinner bell rings at midnight and forces everyone into the dining hall for Chapter 3. Carry state variables (clues found, alliances made) across that bottleneck instead of maintaining parallel geographies.
5. Should I show or hide numerical stats and relationship percentages from the reader?
Showing explicit numbers in a stats screen helps readers play strategically, which suits RPG-flavoured stories. Hiding numerical stats—and instead communicating state through narrative clues (such as an ally standing closer to you or speaking more coldly)—keeps the reader immersed in the drama rather than min-maxing numbers.
6. How do I prevent the reader from feeling punished for picking the "wrong" personality trait?
Design opposing stats (such as Subtle vs. Direct or Idealistic vs. Pragmatic) so that both ends of the spectrum unlock viable solutions. If a high-Subtlety protagonist sneaks past the sentry, let a high-Directness protagonist intimidate or rally the sentry. Never make one trait the sole "winning" stat for the entire story.
7. How many endings does a branching story actually need?
Quality and distinctiveness beat raw quantity. Three to five deeply realized endings—or a unified climax with modular epilogue variations reflecting the state of key companions and locations—satisfy readers far more than twenty abrupt one-paragraph game-over screens.
8. Can a mystery story branch without changing who the culprit is?
Absolutely. In most acclaimed interactive mysteries, the historical truth of who committed the crime remains fixed so the clues stay fair and coherent. What branches is how the detective uncovers the truth, what moral compromises they make to secure evidence, and what they decide to do with the culprit at the end.
9. What is the fastest way to prototype a branching scene before coding it?
Write the scene on physical index cards using a thick marker—if a passage does not fit on one card, it is probably too long before the next choice. Hand the stack to a friend, read the cards aloud, and hand them the two option cards to pick from. You will spot awkward phrasing and unclear stakes in five minutes.