Quick definition
In multiplayer games, the player is the character — so a traditional scripted character arc competes with, rather than serves, the player's own emotional journey. Where linear storytelling runs on Character + Situation = Condition, multiplayer narrative design runs on Player + Situation = Condition. The writer's job shifts from dictating a story to engineering the conditions where players generate their own.
In one line: Players don't want to be told their story. They want to live it.
Why scripted backstory competes with the real emotional beat
A tragic-childhood cutscene is competing for attention with a live 1v5 clutch, a squad talking trash over comms, a heart-pounding escape at 10% health. The scripted material is one directional; the lived moment is the player's own. When they conflict, the backstory loses — and worse, the player may not have even watched the cutscene establishing it in the first place.
Player journey vs. character arc at a glance
| Character arc (linear) | Player journey (multiplayer) | |
|---|---|---|
| Who defines the character | The writer, through choices in the script | The player, through choices, playstyle, and squad dynamics |
| Where the emotion lives | Scripted beats and dialogue | Lived experience — clutches, wipes, callouts |
| Risk of over-scripting | N/A — scripting is the format | Disrupts agency, creates tonal dissonance, forces unwanted identity |
| Story delivery | Exposition and cutscenes | Environmental storytelling, world evolution, emergent moments |
Think archetype, not arc
Multiplayer characters don't need a full emotional journey — they need clarity of role (what do they bring to a fight?), freedom of expression (can players make them their own?), and mechanical support for playstyle. VALORANT's agents carry just enough personality to set a vibe; the real character development happens when a player lands a perfect ability combo, not in a lore drop. Destiny 2 keeps deep lore in optional flavor text precisely because most players care more about their loadout than a scripted backstory.
The multiplayer trap: scripting fights the format
Over-scripting a multiplayer experience tends to fail in three specific ways: it disrupts player agency ("don't tell me how my character feels"), it creates dissonance ("why is this tragic monologue happening during a squad wipe?"), and it forces an identity the player didn't choose ("what if I don't want to be this guy with this agenda?"). Each failure comes from the same root cause — treating a player-driven format like a passively-consumed one.
Narrative design, not narrative dictatorship
This isn't an argument to cut story entirely — it's an argument to change the delivery mechanism: environmental storytelling over exposition, world evolution over character development, transmedia (comics, trailers, ARGs) as optional deep-dives for the players who want them, and emergent tools like killcams and clip-sharing that let players generate their own narrative artifacts. The writer's job becomes building the world, setting the stakes, and getting out of the way.
Multiplayer character checklist
- Does this character have a clear role, or does understanding them require a cutscene?
- Is there room for the player's own choices to define who this character becomes?
- Would this story beat survive a player skipping it entirely?
- Is deep lore optional, or does it block access to core gameplay?
- Could this world survive without a single central protagonist? If yes, it may be a game. If no, it may be better as a film.
Try it on your own character
Scribbler’s Character Doctor
Use the Character Doctor to check whether a character's role and identity read clearly in a single line — the same clarity-of-role test a multiplayer character needs to work without a forced backstory.
Source note
This maintained reference page develops ideas first published in “Player Journey vs. Character Arc” in Scribbler’s Toolbox on May 30, 2025. The original essay remains part of the editorial archive; this version is structured as a durable craft reference.
Related pages
- Why Character Wants Create Opinions, Conflict, and Better Scenes — the linear-storytelling counterpart this framework deliberately departs from for player-driven formats.
- The Alias ARG: How Early Transmedia Storytelling Turned Fans Into Investigators — another format where audiences generate meaning through participation rather than being told a story.
- Why Helldivers 2 Hit Different: Designing for Tribal Bonding, Not Just Combat — this same framework, proven out in a real, shipped co-op game.
- When to Script and When to Design for Emergence in Interactive Storytelling — the general version of the scripting trap this page diagnoses specifically for multiplayer characters.
About the author
Jesse Alexander is a screenwriter, showrunner, and narrative designer whose work spans film, television, games, and transmedia storytelling. Scribbler’s Toolbox collects practical frameworks developed from professional story development and production.