// START HERE
For screenwriters writing games, not just watching them get made
In linear storytelling, Character + Situation = the condition that generates story. In interactive formats, Player + Situation replaces it — and that one substitution changes what a writer's job actually is. This path exists for scribblers extending an existing craft into games, immersive media, and cross-platform IP, not for people starting narrative design from zero. Follow it in order to make the full transition, or jump to the stage where a current project is actually stuck.
- 01
THE FUNDAMENTAL SHIFT
Learn why Player + Situation replaces Character + Situation
In multiplayer games, the player is the character, so a scripted arc competes with the player's own lived emotional journey instead of serving it. The job shifts from dictating a story to engineering the conditions where players generate their own.
Learn Player Journey vs. Character Arc →Linear counterpart:The version of this framework built for scripted characters - 02
TRANSLATE WHAT YOU ALREADY KNOW
Use existing vocabulary as a bridge, not a barrier
Most game-narrative terms already have a direct TV or film equivalent — episodes are levels, NPCs are supporting cast, side quests are subplots. Learning the translation is faster than learning the craft twice, and it's just as useful for spotting exactly where the analogy breaks down.
Translate the vocabulary → - 03
PROOF IN A REAL GAME
See the shift working in a game your audience already loves
Helldivers 2's hook isn't graphics or spectacle — it's mechanical design that makes strangers genuinely necessary to each other. A working case study in building shared stakes instead of solo progression, with zero dialogue doing the emotional work.
Study the Helldivers 2 case → - 04
THE CORE DECISION
Decide which beats are guaranteed and which are generated
Every interactive project mixes two authorial modes: scripted beats every player experiences identically, and designed conditions players generate their own version of. The craft is knowing which one a given moment actually needs, beat by beat — plus a real test for telling the two apart under pressure.
Learn the script-vs-emergence test →Tool for the scripted half:Run a scripted beat through Scene Doctor - 05
THE PRIMARY TECHNIQUE
Let the space carry the story instead of a script
World logic, faction rules, environmental detail, and naming systems all deliver narrative without a line of dialogue — as long as the deep lore stays optional instead of gating comprehension of the actual gameplay.
Build environmental storytelling → - 06
BORROWED WISDOM
Absorb twenty rules from outside your own discipline
Chris Avellone spent decades shaping Fallout 2, Planescape: Torment, and Pillars of Eternity. His rules were written for game makers; they translate cleanly for anyone building character-driven, interactive worlds — chase resonance, trust the audience, let limits sharpen the story.
Read Avellone's rules, translated → - 07
THE CAPSTONE DELIVERABLE
Build one engine, deploy it across formats
A bible written for a single format has that format's assumptions baked invisibly into its canon. Document what has to stay fixed — canon, character cores, tone, world logic — and what's genuinely free to flex, and the same IP can move from a script to a playable build without the world breaking.
Build the cross-format story bible →Single-format version:The IP & Worldbuilding path