Using Mechanics for Storytelling

Abstract

Problem: How can gameplay mechanics reinforce a game's narrative and setting, rather than working against them?

Approach: Tim Cain walks through examples from his own games — Fallout, Temple of Elemental Evil, Vampire: The Masquerade – Bloodlines, and Arcanum — showing how he used mechanics to support storytelling in each.

Findings: The best games bake their core thematic tension into every layer: setting, story, and mechanics. When mechanics contradict the narrative, players experience ludonarrative dissonance — a subtle unease that can make them dislike a game without understanding why. Arcanum exemplifies the ideal, with its magic-vs-tech meter permeating every player decision.

Key insight: Mechanics are not just systems — they are a storytelling channel. Design them after your setting and story so they reinforce the same themes, rather than pulling the player in a conflicting direction.

Source: https://www.youtube.com/watch?v=15pL76IhQjQ

Tim Cain's Design Philosophy

Cain prefers to decide setting and story first, then design mechanics that support them. He acknowledges the reverse approach (mechanics-first) is valid — in that case you build a setting and story that supports your mechanics — but his own method ensures mechanics serve the narrative.

He draws a direct analogy to tabletop RPGs: a DM knows what spells exist, so they create NPC wizards and dragons accordingly. The mechanics are the world. Cain has always wanted to achieve the same unity in his video games, though he admits he didn't always succeed to the same degree.

Game-by-Game Examples

Fallout: Radiation as Environmental Storytelling

In the original Fallout, radiation mechanics were designed to reinforce the post-apocalyptic setting. Radiation was meant to be deadly, omnipresent, and frightening — a silent killer baked into the world.

The Glow exemplifies this: the Brotherhood of Steel sends you there expecting you to die, because everyone who goes there dies. When you arrive, the first thing you see is a dead body. The mechanic matched the fiction — radiation could kill you during fast travel if you'd absorbed enough. Cain acknowledges the UI feedback could have been better, but the intent was correct: radiation should feel dangerous because that's what Fallout's world is about.

Temple of Elemental Evil: Party Alignment

Built on D&D 3.5e rules, Cain added a party alignment mechanic on top. Since players controlled a full party, he wanted the group composition to make narrative sense — no paladins adventuring alongside assassins, no lawful good monks paired with chaotic evil bards.

The mechanic required picking a party alignment, with every character within one step of it. This constraint served the story: it ensured the party that embarked on the adventure was internally coherent, making the unfolding narrative believable.

Vampire: The Masquerade – Bloodlines: The Need to Feed

Bloodlines constantly reminded you that you were a vampire through its feeding mechanic. You needed to feed, and doing so affected your Humanity score. This tension — the necessity of a monstrous act versus the cost to your soul — was the core of the Vampire tabletop game, and Bloodlines translated it directly into gameplay. The mechanic was the story.

Arcanum: The Best Example

Of all his games, Cain considers Arcanum the most successful at mechanic-narrative integration. The game's central theme — the antagonistic tension between magic and technology — was present in every layer:

  • Setting: Whole factions were divided along magic-vs-tech lines. A previous war had been fought over it. Tech was winning again.
  • Story: The conflict drove the plot and NPC relationships.
  • Mechanics: The magic-tech meter moved every time you bought a spell or tech skill, and it affected the effectiveness of everything you used — magic items, tech items, spells, and skills.

The meter was a constant, unavoidable reminder of the world's defining conflict. The player couldn't escape it because every character-building decision pushed them toward one side or the other. Setting, story, and mechanics all said the same thing.

Ludonarrative Dissonance

Cain discusses the concept of ludonarrative dissonance, credited to Clint Hocking, who applied it to BioShock. Cain says he loves BioShock, but Hocking's criticism is valid: the narrative tells the player to be selfless, while the mechanics incentivize selfishness (harvesting Little Sisters for resources, choosing allies based on personal benefit).

The danger of ludonarrative dissonance is that it can make players dislike a game without knowing why. Some players consciously identify the conflict ("the narrative told me one thing but the mechanics told me another"), but others just feel that something is "off." They might blame the story or the mechanics when the real problem is the disconnect between them.

Cain extends this principle beyond narrative: UI friction, poor feedback, or even an unpleasant color palette can create a similar subconscious discomfort. Players may attribute their dissatisfaction to the wrong cause — "I didn't like the story" or "the mechanics were bad" — when the real issue was something they couldn't articulate.

The Takeaway

Game mechanics are a powerful storytelling channel. The best games align their mechanics with their setting and story so that every system reinforces the same themes. When this alignment breaks down, even subtly, players feel it — consciously or not. Cain's advice: approach mechanics as an extension of your narrative, not a separate system layered on top.

References