Key Principle
The Story Stack is a hierarchy of game elements ordered from least to most flexible: Fantasy -> Action -> Economy -> World -> Story. Design must proceed bottom-up. Story sits at the top because it is the most pliable element -- changeable with words alone, while gameplay takes weeks and technology takes months. Protecting story at the expense of costlier lower elements is irrational, yet designers do it constantly because story feels like the soul of the project.
"If ever you find yourself, or someone on your team, saying 'we can't do that... it goes against the story,' it is a clear signal that story has tricked you, trapped you, and taken over your game." -- Jesse Schell, Chapter 17
Five fundamental problems make fully branching interactive narrative unrealized:
- Unity destruction -- branching fractures the connection between beginning and ending.
- Combinatorial explosion -- 10 choices x 3 options = 88,573 outcomes; 20 choices = 5.2 billion.
- Multiple endings disappoint -- players ask "Is this the real ending?" and resist replaying.
- Not enough verbs -- games have run/shoot/jump; stories need talk/negotiate/convince/argue.
- Time travel kills tragedy -- save/reload destroys inevitability; freedom and destiny are polar opposites.
Two pragmatic methods sidestep these problems rather than solving them:
- String of Pearls: Cutscene-gameplay-cutscene sequences. Newer implementations (The Last of Us, The Walking Dead) blur the seams artfully.
- Story Machine: Games that generate stories through play (The Sims, Minecraft). The more prescripting, the fewer stories generated.
Why This Matters
Starting from story (top of the stack) forces inflexible lower elements to conform, producing games that feel wrong despite having "good stories." This is identified as the single most destructive mistake in story-driven game development. Designers who do not understand the five unsolved problems waste years chasing an impossible ideal of fully branching narrative.
The real failure is being "obsessed with story, not with experience, and experience is all we care about" (Ch. 17). Story is a means, not an end. When designers treat it as the end, they sacrifice gameplay, economy, and fantasy -- the elements players actually inhabit -- to protect the element players merely observe.
Good Examples
Pixie Hollow (bottom-up redesign): Designers originally built activities from movie plot (top-down). Focus groups of girls rejected everything, demanding flying as the primary action. The fantasy of being a fairy dictated acceptable actions, not the story. Rebuilding bottom-up -- fairy fantasy, flying action, natural barter economy, forest world, then story -- made the design work. (Ch. 17)
The Sims / Minecraft as story machines: These games generate compelling narrative through play rather than prescripted plot. The explosion of "Let's Play" content proves the story machine method produces narrative people want to share and consume. (Ch. 17)
Simplicity and Transcendence pairing: Successful game worlds combine a world simpler than reality with powers greater than normal. Medieval settings offer primitive technology (simplicity) plus magic (transcendence). Minecraft offers extreme simplicity plus godlike creative power. (Ch. 17)
Counterpoints
Top-down story design (the Pixie Hollow anti-pattern): Building gameplay from plot produces games where the fantasy feels wrong. The story may be coherent, but players reject the experience because lower stack elements were forced into unnatural shapes. (Ch. 17)
Chasing branching narrative: The five unsolved problems compound. Designers who pursue the dream of total narrative freedom without understanding these constraints produce games with meaningless choices, disappointing endings, or unsustainable content budgets. (Ch. 17)
Accuracy over accessibility: Jules Verne used a cannon (not rockets) for moon travel because cannons were accessible to 1865 audiences. Pirates of the Caribbean made ships unrealistically fast. The audience's mental model, not physical reality, determines what feels right. Accuracy that violates expectations breaks immersion more than inaccuracy that confirms them. (Ch. 17)
Key Quotes
"If ever you find yourself, or someone on your team, saying 'we can't do that... it goes against the story,' it is a clear signal that story has tricked you, trapped you, and taken over your game." -- Jesse Schell, Chapter 17
"Obsessed with story, not with experience, and experience is all we care about." -- Jesse Schell, Chapter 17
"The more prescripting, the fewer stories generated." -- Jesse Schell, Chapter 17 (on story machines)
Rules of Thumb
- Always design bottom-up through the Story Stack: Fantasy -> Action -> Economy -> World -> Story
- If story is blocking a gameplay decision, story is the problem -- story is the cheapest element to change
- Neither string of pearls nor story machine solves the five problems; both work by sidestepping them
- Pair simplicity with transcendence: simpler-than-reality world plus greater-than-reality powers
- Prefer accessibility over accuracy -- match the audience's mental model, not physical reality
- The five unsolved problems compound; budget your ambition accordingly
- Story serves the game; the game does not serve the story
Related References
- Indirect Control and Player Freedom - Indirect control resolves story/gameplay tension via collusion and environmental guidance
- The Lens Methodology and Essential Experience - Story is one tetrad element; the Story Stack refines how it relates to the others