Case Study 2: Dear Esther --- When Definitions Break

Walking Into a Fight

In 2012, a small team led by Dan Pinchbeck released Dear Esther as a commercial product on Steam. It began as a free Source engine mod in 2008, a research project exploring first-person shooters stripped of shooting. The commercial release added stunning environmental art by Robert Briscoe and an evocative score by Jessica Curry. It was beautiful. It was atmospheric. It was emotionally affecting.

It was also, depending on who you asked, not a game.

The backlash was immediate and intense. Steam reviews split between players who called it a masterpiece and players who called it a screensaver. Forum threads devolved into shouting matches. Critics argued about whether it deserved review scores, Game of the Year nominations, or even shelf space on a game distribution platform. The phrase "walking simulator" --- coined as a dismissal --- became the name of an entire genre.

Dear Esther is the most important boundary case in modern game design. Not because it settles the "is it a game?" debate, but because it reveals what the debate is actually about: which design elements are essential, which are optional, and what happens when you strip a game down to almost nothing.

What Dear Esther Is

You are on a Hebridean island. You move through the landscape in first person. You cannot run. You cannot jump. You cannot pick things up. You cannot interact with objects. A narrator --- voiced by Nigel Carrington --- reads fragments of a letter to a woman named Esther. The fragments are partially randomized: each playthrough delivers different selections, in different orders, creating a slightly different narrative experience.

The island is hauntingly beautiful. Caves glow with bioluminescent paint. Chemical structures are drawn on cliff faces. A ruined shipwreck lies broken on the shore. The narrator's voice is melancholy, poetic, fragmented. You walk toward a red blinking light on a radio tower, and eventually you reach it, and the game ends.

That's everything. The entire experience takes about ninety minutes. There is no second playthrough twist. There is no hidden mechanic. There is no challenge, no puzzle, no enemy, no resource, no skill to master, no score to achieve.

Dear Esther vs. the Definitions

Huizinga

Is Dear Esther voluntary? Yes. Separate from ordinary life? Yes --- you are inhabiting a digital island and engaging with a fictional narrative. Uncertain? Barely --- the fragments change, but the trajectory (walk to the tower) does not. Governed by rules? The only rule is: you can move forward. You are always moving forward. Unproductive? Yes.

Dear Esther satisfies some of Huizinga's criteria but fails the "uncertainty" and "governed by rules" tests in any meaningful way. If the only rule is "you can walk," and the outcome is the same regardless of what you do, the framework strains.

Caillois

Which category? Not agon (no competition). Not alea (no chance affecting the outcome). Arguably mimicry --- you are occupying a perspective, seeing through someone else's eyes, experiencing a landscape as if you were there. Not ilinx, unless the disorientation of the non-linear narrative counts.

On the ludus-paidia axis, Dear Esther is neither. Ludus implies structured rules and objectives; Dear Esther has neither. Paidia implies freeform play and spontaneity; Dear Esther's path is essentially linear. It sits outside the axis entirely --- or below it, in a space Caillois didn't account for.

Costikyan

Does Dear Esther produce an uncertain outcome through player effort? No. The player's effort (walking) does not influence the outcome (arriving at the tower). The narrative fragments vary, but this variation is not determined by player effort --- it's randomized. The player cannot fail. The player cannot succeed. The player can only continue or quit.

By Costikyan's definition, Dear Esther is not a game. This is arguably the clearest disqualification.

Salen & Zimmerman

• System: Debatable. There is a rendering engine, a physics system (sort of --- you can walk on surfaces), and a narrative delivery system. But these components barely interact.
• Players: Yes. Someone has to walk.
• Artificial conflict: No. There is no conflict. Nothing opposes you. Nothing challenges you. The island is empty.
• Rules: Barely. The "rules" are the constraints of the engine: you can move, you cannot jump, you cannot interact. But these feel less like designed rules and more like the absence of designed mechanics.
• Quantifiable outcome: No. There is no score, no rating, no measure of performance. The "outcome" is the same for every player: you reach the tower.

Dear Esther fails the Salen & Zimmerman definition on at least two counts (artificial conflict and quantifiable outcome) and arguably three (the "system" is barely interactive).

📝 Note: This analysis is not a condemnation. Dear Esther failing traditional game definitions does not make it bad, worthless, or unimportant. It makes it interesting. The failure reveals the assumptions baked into the definitions --- assumptions about what interactive experiences need to include. Those assumptions are worth examining.

The Arguments For "It's a Game"

The medium argument: Dear Esther is built on a game engine (Source), distributed on a game platform (Steam), played with a game input device (keyboard and mouse), and experienced from a first-person perspective familiar to anyone who has played an FPS. The tools are game tools. The grammar is game grammar.

The interaction argument: The player makes decisions: where to look, which path to take (where paths diverge), how long to linger. These decisions are minimal, but they are real. The player's attention determines what narrative fragments they hear and what environmental details they notice. The experience is shaped by the player's choices, even if the outcome is not.

The expanded definition argument: If we use the working definition from Chapter 1 --- "a designed experience in which a player interacts with a system of rules to pursue a goal (explicit or self-imposed) within a space that is understood by all participants to be separate from ordinary consequences" --- then Dear Esther qualifies. The goal is self-imposed (explore, understand, reach the light). The player interacts with the system (by walking, looking, listening). The space is separate from ordinary consequences.

The precedent argument: If Dear Esther is not a game, where do you draw the line? Journey has minimal conflict and no fail state --- is it a game? Flower has you flying through meadows as the wind --- is it a game? Abzu is underwater exploration with no death --- is it a game? Drawing the line at Dear Esther requires drawing it through Journey, and most people are uncomfortable doing that.

The Arguments Against "It's a Game"

The agency argument: In a game, the player's actions matter. They influence the outcome. In Dear Esther, the player's actions do not influence the outcome. Walking is not gameplay; it is traversal. The experience would be fundamentally similar as a short film. The interactivity is decorative, not functional.

The challenge argument: Games provide challenges that the player must overcome through skill, effort, or strategy. Dear Esther provides no challenge. You cannot fail. You cannot improve. You cannot get "better" at Dear Esther. The experience of a first-time player and a hundredth-time player is nearly identical.

The rules argument: Dear Esther's "rules" are the engine's physics. You can walk on surfaces. You fall off ledges (slowly). That's not a rule system --- it's a navigation constraint. Rules in a game create meaning: a chess piece's movement rules create the entire strategic depth of chess. Dear Esther's movement constraints create nothing beyond "you can go here but not there."

The design intent argument: Dan Pinchbeck himself has been ambiguous about whether Dear Esther is a game. In interviews, he's described it as an experiment in interactive storytelling, a first-person narrative experience, and a research project. The team did not set out to make a "game" in the traditional sense. They set out to see what happens when you remove everything from an FPS except the walking.

⚠️ Common Pitfall: The "design intent" argument is weaker than it seems. What the creator intended does not determine what the work is. Marcel Duchamp did not intend for a urinal to be art when he submitted Fountain to an exhibition --- but it became one of the most important artworks of the twentieth century. Whether Dear Esther is a game depends on what "game" means, not on what Pinchbeck thought he was making.

What Walking Simulators Teach Us

The real value of Dear Esther and its descendants is not in settling the definitional debate. It's in revealing the design tools that games have been using all along but rarely isolate.

Environmental Storytelling Works Alone

Most games use environmental storytelling as one tool among many. Dark Souls tells stories through item descriptions and architectural details, but it also has combat, exploration, and progression systems. BioShock uses audio logs and environmental clues, but it also has shooting and plasmid mechanics.

Walking simulators prove that environmental storytelling can carry an entire experience by itself. Gone Home (2013) builds a complete, emotionally devastating family story using nothing but a house full of objects. What Remains of Edith Finch (2017) tells a multi-generational family history through rooms in a house, each containing a unique interactive vignette. These games demonstrate that "explore a space and discover a story" is a sufficient engagement loop if the space is well-designed and the story is worth discovering.

🛠️ Design Exercise: Walk through a room in your house. Imagine a stranger entering this room with no context. What could they learn about you from the objects, the arrangement, the wear patterns, the books on the shelf, the photos on the wall? Now imagine designing a game environment where every detail tells a story. What would you place in the room? What would you remove? Environmental storytelling is as much about what's missing as what's present.

Atmosphere Is a Design Tool

Dear Esther's primary engagement mechanism is atmosphere. The island is beautiful and eerie. The soundtrack is haunting. The narrator's voice is sad and poetic. These elements create an emotional experience that keeps the player moving forward.

In traditional game design, atmosphere is a secondary concern --- something that enhances the gameplay but doesn't replace it. Walking simulators demonstrate that atmosphere can be primary. If your atmosphere is strong enough --- if the world is compelling enough to explore for its own sake --- you don't need enemies, puzzles, or scoring systems to maintain engagement.

This insight is useful even for traditional game designers. If you're making an action game and your atmospheric design is strong, players will tolerate longer stretches between combat encounters. If your atmosphere is weak, players will get restless the moment the action stops. Atmosphere is not decoration --- it is a sustaining mechanism.

Pacing Without Challenge

Games traditionally create pacing through challenge variation: easy section, hard section, boss fight, breather. Walking simulators create pacing through revelation variation: interesting area, quiet transition, narrative fragment, visual spectacle, quiet transition, emotional climax.

Firewatch (2016) is a masterclass in this. You walk through a Wyoming forest. Nothing tries to kill you. But the game controls pacing through the timing of dialogue (your radio conversations with Delilah), the design of the landscape (open meadows alternating with dense forest), and the escalation of narrative mystery. By the end, you are as tense as you've ever been in a "real" game --- not because anything is threatening you, but because the narrative has created stakes through character and mystery.

🔗 Connection: This connects directly to Chapters 16-19 on level design. The principles of spatial pacing --- wide spaces vs. narrow spaces, light vs. dark, busy vs. empty --- apply to every game, whether it has combat or not. Walking simulators make these principles visible because they're the only engagement tool available.

Other Boundary Cases Worth Knowing

Dear Esther opened a door. Here are a few other games that walked through it:

The Stanley Parable (2011/2013): A walking simulator that is also a game about games. You play as Stanley, a man whose job is to press buttons. A narrator tells you what to do. You can obey or disobey. Each choice leads to a different ending, and the game's real content is its commentary on player agency, narrative authority, and the nature of games themselves. The Stanley Parable is a walking simulator that becomes a game through metatextuality --- the "challenge" is understanding what the game is saying about you.

Mountain (2014): You observe a mountain. Occasionally things hit it. You can play musical notes on a keyboard. David OReilly, the creator, insists it is a game. Most players disagree. Mountain is interesting because it tests the minimum viable interactivity: is observing sufficient? Is the mountain a game, a toy, a screensaver, or something else entirely?

Proteus (2013): You explore a procedurally generated island. There is no narrative, no score, no objective. The island changes with the seasons. Animals react to your presence. The soundtrack is generated by your interactions with the environment. Proteus is a walking simulator with more interactivity than Dear Esther (the island responds to you) but less structure (there is no story to discover). It sits in an interesting space between interactive experience and toy.

The Question That Actually Matters

Here is the conclusion I want you to take from this case study:

"Is Dear Esther a game?" is a question about taxonomy. It's interesting for about five minutes. It produces no actionable design insight.

"What design elements does Dear Esther use, and how does it create engagement without the elements most games rely on?" is a question about design. It is useful for the rest of your career.

The answer to the second question reveals tools that every designer can use: atmospheric world design, pacing through spatial and narrative revelation, environmental storytelling, sonic design as emotional architecture, the power of negative space (what you don't show the player). These tools exist in every game. Walking simulators isolate them and prove they can work alone.

Whether or not Dear Esther is a game, it expanded what interactive experiences can be. It proved that first-person navigation through a beautiful environment, accompanied by a fragmentary narrative, is a valid form of designed experience. And it reminded the game design community that "is it a game?" is the wrong question. The right question is always: "does this create a meaningful experience for the player?"

🪞 Learning Check-In: After reading this case study, can you: - Identify which traditional game elements Dear Esther omits and which it retains? - Name three design tools that walking simulators use to maintain engagement without traditional game mechanics? - Explain why "is it a game?" is less useful than "what design elements does it use?" as a question for designers? - Apply the lesson of this case study to your own player fantasy statement --- do you know which engagement tools your game will rely on most heavily?