Social masterclasses on branching design

Two game-writing threads on X converged on the same point this week: branching stories work best when choices change people, not just plot order. (x.com) Alexander “Lex” Williams argued that writers should build branches from a character’s wants, obstacles, and actions, rather than from a flowchart of endings. Williams posted the thread on X under the handle squidlord. (x.com) MaxibonHR_YT made a parallel case in a separate X thread, saying overlapping multi-narrative plots should stay self-contained so one route does not break another route’s logic. That advice targets a common failure in choice-heavy games: players notice when one branch quietly assumes information from a different branch. (x.com) Branching narrative is the design of scenes, dialogue, or missions that split based on player input, then reconnect or continue toward different outcomes. H5P, an authoring platform for interactive scenarios, describes the format as a tree with multiple branches and endings determined by user choices. (h5p.org) Game writers have wrestled with that structure for decades because games can present choices, but every extra branch multiplies writing, testing, and continuity work. Game Developer called branching conversation systems “clumsy” and “difficult to write” in a 2014 series that remains widely cited in narrative design circles. (gamedeveloper.com) Academic work on role-playing dialogue systems frames the same problem in player terms: agency only works if choices are legible and the game reflects them. A 2020 Springer chapter on player-centered branching dialogues lists agency, ambiguity, context, and lack of judgement among the core design properties. (link.springer.com) That is why both threads push writers away from “fake choice,” where branches differ in wording but collapse into the same unchanged relationship or knowledge state. In practice, stronger branches tend to alter what a character knows, whom they trust, what role they occupy, or which future scenes remain possible. (x.com) The advice also reflects production reality. Self-contained branches are easier to test, easier to revise, and less likely to create continuity bugs when teams add new scenes late in development. (x.com) Taken together, the two threads read less like abstract theory than a checklist for shipping interactive fiction: start with motive, track consequences, and keep each route logically intact. That does not make branching stories simple, but it does make the player’s choice easier to feel on screen. (x.com)