A World Building Tip

tim-cain world-building narrative-design game-design sequels mystery lore

Abstract

Problem: How much world building should you do for your first game?

Approach: Tim Cain distills decades of game development experience into a single guiding principle, then unpacks it with examples and reasoning.

Findings: Do just barely enough world building — and no more. Build a solid foundation for consistency, but leave mysteries unanswered, keep details vague, and preserve room for sequels and player-driven reinterpretation.

Key insight: Over-building your world kills mystery, eliminates sequel potential, and prevents you from incorporating players' better ideas after launch.

Source: https://www.youtube.com/watch?v=8QmRDRbcLkg

1. The One-Sentence Tip

Tim Cain's core advice: "Do just barely enough world building, and no more." He describes this as the most compressed, insightful thing he can offer to someone making their first game — a lesson he learned slowly over decades.

2. What "Enough" Means

2.1. Consistency for the Design Team

The designer and team need to know what's going on in the world — even if the player never learns it all. This means understanding:

  • What events set the story in motion
  • How the universe's mechanics work
  • What can and cannot happen within the world's rules

This prevents contradictions like establishing a world without flight and then handing the player a fly spell for no reason. The foundation keeps everything coherent.

2.2. Player Satisfaction With Lingering Curiosity

Players should finish the game feeling satisfied about the world they explored, but still wanting more. They should walk away thinking: "That was a really interesting world — but I want to know where the gods came from" or "Who was that mysterious guy who kept giving me advice?"

2.3. The Building Metaphor

Tim tells his designers: build a good foundation that your game rests on, but you don't have to build every floor. You don't need to know what's in the attic by the end of your first week of design. You might even ship without knowing. Maybe the player hears some thumps from above, maybe the house shakes a little — but nobody knows what's up there yet. And that's a good thing.

3. Why Too Much Is Dangerous

3.1. Mystery Is Valuable

Unanswered questions are not a failure — they're a feature. When every question has been answered and everything is explained, players are done. They don't want to explore that world anymore. The sense of wonder evaporates.

Tim cites Blade Runner as a masterful example: the question of whether Deckard is a replicant is never definitively answered. The original cut didn't even hint at it. The director's cut added the unicorn dream and the origami unicorn — just enough to make you wonder "how would Gaff know what Deckard dreams unless those dreams were implanted?" That ambiguity is what keeps the story alive decades later.

3.2. Answers Should Generate New Questions

When you do reveal something, let the answer open new mysteries. Tim gives an example: a mysterious character who kept appearing throughout the game is finally revealed to be "a scientist who created you." Now the player is reeling — "What? Am I a robot? Am I synthetic? What do you mean, created?" One answer spawns a cascade of new questions.

3.3. Vagueness Preserves Wiggle Room

If you're not overly specific, you can adapt after launch. Players will inevitably find things that don't quite fit — contradictions in how magic works, technology that behaves inconsistently, plot elements that feel off. If your lore is vague enough, you can incorporate player feedback and even adopt their better ideas:

  • Players speculate about a mysterious character
  • Some of their theories are better than what you had planned
  • Because you never locked in an answer, you can use their ideas in the sequel

3.4. Sequel Potential

If you answer everything, dot every i, and cross every t, there may not be a big story left to tell. All the grand mysteries are resolved. Leaving world-building space open means you have room for another major narrative — side quests left unresolved, characters whose fates remain unknown, cosmological questions still hanging.

Tim gives the example of a queen whose son disappeared years ago. Side quests hint at possibilities — kidnapped, fled the country due to an illegal power, joined a monastery — but it's never resolved. That's sequel material sitting right there, and it's fine to leave it open.

4. The Meta-Lesson

This advice is deliberately high-level rather than specific and actionable. Tim frames it as a guideline he wishes he'd followed in his first few games. The specific techniques — the "What If" method, setting-creation questions, IP maintenance — are covered in his other videos. This is the philosophical frame that should govern all of them: just enough lore for your game, but not too much.

5. References