The Quit Is the Point: Indie Games Designed for the Players Who Walk Away

I have a folder on my PC called, charitably, "backlog." It is not a backlog. It is a graveyard. Games I opened once, played for forty-five minutes, and never returned to. Games I got three hours into and then just... didn't. Games that sat at 12% completion for two years before I quietly uninstalled them to free up space.

For a long time I felt bad about this. The gaming community has a weird relationship with finishing things — there's a low-grade shame that accumulates around games you quit, like you owe them something. Like you failed.

But here's a thought I haven't been able to shake lately: what if some of those games were doing exactly what they were supposed to do?

Designed to Be Left Behind

Most game design operates from a single core assumption — the player will finish. Tutorials lead to mid-game, mid-game leads to climax, climax leads to credits. The whole structure is built around completion as the destination.

But a quiet, strange corner of the indie scene has started questioning that assumption. These are games that seem to understand — at the design level, not just philosophically — that players are going to leave. And rather than treating that as a problem to solve with better retention mechanics, they treat it as the story.

Caves of Qud is a useful starting point. It's a sprawling, procedurally generated roguelike so dense and strange that most players will never come close to seeing everything it contains. The developers know this. The game knows this. There's a kind of melancholy built into its world — the sense that it stretches far beyond what any one person could ever explore. When you die (and you will die, often) or when you simply stop playing, you're not failing to complete the game. You're participating in its central idea: that the world is larger than any one life moving through it.

Walking away from Caves of Qud isn't quitting. It's the experience.

The Guilt Is the Feature

Then there are games that do something more deliberate — they build the emotional texture of abandonment directly into their design.

Dwarf Fortress has been doing this for twenty years. You build something. You invest. You lose it in a cascade of increasingly absurd catastrophes. And then, often, you stop. The community has a saying: "Losing is fun." But what they're really describing is something more nuanced — the way the game turns failure and eventual abandonment into a complete emotional arc. The fortress you walked away from isn't a loss. It's a story that ended.

More recently, games like Norco and Citizen Sleeper have taken a different approach to the same territory. These are narrative games set in decaying, economically gutted versions of America — Norco in the petrochemical corridors of Louisiana, Citizen Sleeper in a kind of off-brand future that feels uncomfortably close. Both games are about people who are running out of time, running out of options, making peace with the fact that not everything gets resolved.

In Citizen Sleeper especially, there are story threads you simply won't finish. The game tells you this. Cycles run out. People leave. The game is not withholding these endings to punish you — it's reflecting something true about what it feels like to be a person with limited time and too many things that matter.

If you put the game down before you've seen everything, you haven't missed the point. You've lived it.

What Quitting Actually Costs

Here's the part that I think gets underexamined in conversations about this: walking away from a game you're invested in doesn't feel neutral. It feels like something.

Sometimes it's relief. You've been white-knuckling your way through a game that was making you anxious, and closing it feels like setting down a weight. Sometimes it's guilt — the specific flavor of guilt that comes from abandoning something you care about, which is its own kind of emotional data worth paying attention to. And sometimes it's just a quiet acknowledgment that you got what you needed and it's okay to stop.

Independent developers who understand this are building games that honor all three of those experiences. They're not designing for the player who will 100% complete everything. They're designing for the player who will show up when they need to, take what the game has to offer, and leave when life calls them back.

That's a more honest picture of how most of us actually play.

The Comparison Nobody Wants to Make (But I'm Making It)

There's a reason this design philosophy resonates in a way that feels bigger than games. We live in a culture that is deeply uncomfortable with incompleteness. Unfinished projects, relationships that ended without resolution, careers that didn't go where we planned — we treat all of it as failure. We pathologize the walk-away.

But sometimes leaving is the healthy thing. Sometimes recognizing that a situation is costing you more than it's giving you — and choosing to step back — is the most emotionally intelligent move available. The games that model this, that treat the quit as a legitimate and even meaningful choice, are doing something quietly countercultural.

They're saying: you don't owe this your completion. You don't have to finish to have mattered here.

A Different Kind of Ending

I'm not arguing that all games should be designed to be abandoned, or that finishing things doesn't matter. Completion is satisfying for real reasons. The feeling of seeing a story through, of earning an ending — that's worth something.

But the indie developers exploring this other territory are pointing at something the mainstream hasn't caught up to yet: that the human relationship with incompleteness is rich and complicated and worth exploring. That the 12% completion rate isn't always a design failure. That sometimes, the player who walked away got exactly what they came for.

My graveyard folder looks a little different to me now. Less like a record of my failures and more like a collection of experiences that ended when they needed to. Some of them I'll go back to. Some I won't.

Both of those are fine. Some of those developers already knew that when they built the thing.