Game Flavor

tim-cain game-design game-direction creative-vision flavor game-feel

Abstract

Problem: Games need something beyond vision and player experience (qualia) to feel distinct and memorable — but what is that quality, and how do you cultivate it?

Approach: Tim Cain introduces the concept of "game flavor" — a subjective, director-driven quality distinct from both game vision and qualia — and uses a cooking analogy (Salt, Fat, Acid, Heat) to explain how to develop and enforce it.

Findings: Flavor is the personal signature a director imprints on a game. It persists across different visions (Fallout vs. Arcanum) and different qualia (Fallout 1 vs. New Vegas). Choosing not to define a flavor guarantees a bland, forgettable game. Enforcing flavor requires rejecting even high-quality work that doesn't match, which is the hardest part of directing.

Key insight: If you don't consciously choose a flavor for your game, you've still made a choice — you've chosen "unflavored," and your game will be boring and unmemorable.

What Game Flavor Is (And Isn't)

Tim Cain defines game flavor as a subjective, personal quality that a director imprints on a game. It's distinct from two related but different concepts:

Game Vision is what the director holds in their head and expresses through design documents and pillars — how the game will be played, what it will feel like, what you do in it. Arcanum and Fallout had very different visions but very similar flavor.

Qualia is the ineffable quality of direct experience — like seeing the color red or tasting an apple. You can describe it scientifically, but that's not the same as experiencing it. Fallout 1 and Fallout New Vegas have wildly different qualia (isometric vs. first-person, turn-based vs. real-time) but very similar flavor.

Flavor is the "Tim Cain-ness" of a Tim Cain game. It's why people who played Arcanum and then learned it was made by the Fallout team said "oh yeah, I can see that." Your games will have a you flavor.

The Danger of Choosing No Flavor

Tim warns bluntly: if you consciously choose not to define a flavor, you've still made a decision. You've chosen unflavored. He references a Simpsons scene with Ned Flanders offering "nonfat ice milk — wintergreen unflavored" as the perfect illustration.

Trying to avoid offense for broader appeal produces games that are "exceptionally boring." He points to plain vanilla fantasy games (video or tabletop) that have nothing going for them. He also references a Community scene where Abed tells Britta that compulsively filtering yourself makes you "a flavor... kind of a flavor" — and not a good one.

A flavored game can still be boring, but an unflavored game guarantees it.

Enforcing Flavor Is the Hard Part

The real difficulty isn't choosing a flavor — it's enforcing it during development. This means throwing out work that is technically good but doesn't match the game's flavor. Cain notes this is far harder than rejecting bad work, where you can point to clear flaws.

Since flavor is hard to articulate before the game exists, team members struggle to see it. Cain experienced this with Fallout, Arcanum, and early Outer Worlds development. People will accuse you of being a "dictator" for rejecting quality work. Making a sequel (as with Outer Worlds 2) is easier because you can say "play the first game — there's the flavor."

Every team member brings their own flavor, and it takes deliberate effort to keep the game's flavor consistent rather than a random hodgepodge. Sometimes mixing flavors works (a mélange), but usually you can't throw random spices together and hope for the best.

The Salt, Fat, Acid, Heat Framework

Borrowing from Samin Nosrat's cooking method, Cain maps flavor enforcement to four principles:

Salt — Accentuate the Flavor

Salt has its own taste but primarily makes other flavors stronger. In games, these are elements that don't carry the flavor themselves but make it stand out. Like salt in brownies — just a little brings everything forward.

Fat — Spread the Flavor Everywhere

Fat carries flavor throughout a dish. In a game, this means your flavor should permeate everything: lore text, dialogue, location names, world-building details. Junk Town exists in Fallout but not Outer Worlds; Roseway exists in Outer Worlds but not Fallout. That's deliberate. Fat spreads the flavor into every corner.

Acid — Surprise the Player

Acid gives a dish that unexpected bite. In games, it's the moment the player goes "oh!" — surprised that the game's flavor led there. Cain's example: Fallout's end slides, where the game reveals it was watching your choices the whole time. Traits like "Childkiller" or "Chem Addict" and the ending consequences were Fallout's acid — the game saying "I explained the flavor to you, why are you surprised?"

Heat — Add Tension and Pressure

Heat creates pressure and tension. Fallout's original water chip timer was heat — a little pressure pushing the player forward. Storylines that threaten consequences ("all these people will die," or Outer Worlds' brain dequestation) add heat. It doesn't have to be extreme, but it has to be present.

Summary

Game flavor is the director's personal signature — distinct from vision (what the game is) and qualia (what playing it feels like). Every director must consciously choose and enforce their flavor, knowing that refusing to choose is itself a choice for blandness. Use salt to accentuate, fat to spread, acid to surprise, and heat to pressurize — and your game will be memorable.

Source: Game Flavor — Tim Cain

References