How Character Names in Games Work as the First Mechanic Players Never Question

You rolled a Crusader. The game calls her Reynauld. You didn’t choose that name. You didn’t choose her backstory either—the gambling habit, the debts, the son who ran off. The game assigned both before you touched a stick. And yet when Reynauld dies of a heart attack in the Ruins, you feel something specific. Not grief, exactly. More like the loss of a particular configuration of traits and quirks that the name Reynauld let you hold in your head as a person rather than a stat sheet.

That feeling—that conversion of a label into emotional scaffolding—is not an accident. It’s a mechanic. And it might be the most overlooked design decision in any game that features characters.

Here’s the claim: a character’s name in a game is not flavor text. It is the first mechanic that tells the player whether they’re looking at a person, a unit, or a system. Everything that follows—dialogue, stats, inventory, death—gets filtered through that initial assignment. Most players never question it. That’s exactly why it works.

The Nameless Hero as Interchangeable Labor

Consider Darkest Dungeon. Red Hook Studios made a design choice that seems cruel but is mechanically precise: your heroes are procedurally generated. They arrive with random names pulled from a pool—Barristan, Sarisi, Junia, Dismas—but they also arrive with random quirks, random classes, and no fixed backstory beyond a single sentence. The name is a label. The label attaches to a body. The body attaches to a function. And the function is expendable.

This isn’t a failure of characterization. It’s an argument about what heroes are in the context of dungeon crawling. The game’s core mechanic is stress management—not just the characters’ stress, but yours. You’re meant to form attachments quickly and break them without ceremony. The procedural name gives you just enough grip to feel the loss without giving you enough to refuse the sacrifice. If every hero had a hand-written backstory, you’d never send them into the Cove. The name is the minimum viable identity.

Now compare this to XCOM, where soldiers also have randomly generated names but also have perma-death. The difference: XCOM lets you customize the name. You can rename a soldier after your friend. You can give them a nickname. And the moment you do, the game’s mechanical argument shifts. The soldier is no longer a unit. They’re a person you made. XCOM’s naming system is an opt-in identity mechanic—the game offers you the system’s version of a person, and you can override it with your own. Darkest Dungeon refuses that override. The name is the system’s, not yours. You don’t get to make this hero yours because the game needs you willing to throw them away.

The naming mechanic in Darkest Dungeon is thus a moral proposition about the value of individual lives in a system designed to consume them. The name is just human enough to hurt when it disappears, and just impersonal enough to let you keep playing.

Procedural Names as the Foundation of Dynastic Feeling

Crusader Kings 2 takes the opposite approach and pushes it to its logical extreme. Every character has a name. Many of those names are inherited. You play as a dynasty, not an individual, and the game’s naming system is what makes that dynastic identity mechanically legible. When your ruler dies and your heir takes over, the heir often has the same name as a predecessor—Charlemagne becomes Charles, then Karl, then another Charles. The game tracks this. The name carries the weight of continuity.

But here’s where it gets interesting: Crusader Kings 2 generates its characters procedurally, including their names, but the names are drawn from culturally specific pools. A Norse ruler gets Norse names. An Andalusian ruler gets Arabic names. The name isn’t just a label—it’s a mechanical signal of culture, religion, and political context. When you see a character named Hæsteinn in your court, the name tells you something about what mechanics are available to them, what alliances are possible, and what rebellions are likely.

The emotional investment in Crusader Kings 2 is built almost entirely on the naming system. You don’t care about Duke Guiu of Barcelona because he has a compelling personality—he doesn’t have one. You care about him because his name appears on a family tree, because his name connects to a county you spent thirty years acquiring, and because his name will pass to his son, who might be named Guiu as well, and who might lose everything you built. The name is the thread that makes the simulation feel like a story instead of a spreadsheet.

This is why Crusader Kings 2’s procedural naming isn’t the same as Darkest Dungeon’s. In Darkest Dungeon, the procedural name marks a character as replaceable. In Crusader Kings 2, the procedural name marks a character as irreplaceable—because the name carries the weight of the dynasty, and the dynasty is the only thing the game lets you invest in. The same mechanic—randomly assigning a name from a pool—makes opposite arguments depending on what the game asks you to care about.

Named Skills as Internal Voices

Then there’s Disco Elysium, which does something no other game I’ve played does: it names the player character’s internal faculties. Endurance. Inland Empire. Electrochemistry. Volition. These aren’t stats in the traditional sense. They’re characters. They speak to you. They argue with each other. They have opinions about what you should do, and those opinions are colored by the name the game gave them.

Consider what happens when you level up Inland Empire. In a conventional RPG, this would mean your character is better at detecting magical phenomena or sensing hidden truths. In Disco Elysium, it means the voice in your head that talks about dreams, hunches, and the supernatural gets louder. More confident. It interrupts you more often. The name Inland Empire isn’t a label for a stat—it’s a name for a character who lives inside you and who has been given more authority.

The genius of this system is that it treats identity not as a single authored self but as a committee of competing internal voices, each with its own name, its own agenda, and its own relationship to the player. When Electrochemistry tells you to take drugs, that isn’t the game telling you to take drugs. That’s a named character within your character making an argument. You can listen. You can ignore it. But you can’t pretend it isn’t there, because it has a name, and named things in games demand to be reckoned with.

This is the most radical version of the naming-as-mechanic principle I’ve seen. Disco Elysium doesn’t just name your character. It names the forces that constitute your character. And by naming them, it makes them into agents with their own will. The skill check isn’t a roll of the dice. It’s a negotiation between named parties, and the outcome depends on which named party has been given the most power through your leveling choices.

The implication for design is significant: if you name a system, you give it a voice. If you give it a voice, you give it agency. And if you give it agency, you’ve made a moral decision about whether the player or the system is in control of the character’s identity.

What Naming Systems Teach Players Before the First Line of Dialogue

Before a character speaks, before a cutscene plays, before a tutorial explains anything, the player has already been told what kind of relationship they’re going to have with the figures on screen. The naming system has already done its work.

If characters have full names, backstories attached to those names, and fixed identities that persist across saves, the player learns that these are people. The game is about people. The mechanics that follow—dialogue trees, relationship meters, moral choices—will be framed as interpersonal events. The name has already set the expectation.

If characters have callsigns, class labels, or procedurally generated names that change on every playthrough, the player learns that these are units. The game is about tactics. The mechanics that follow—positioning, loadout selection, casualty management—will be framed as operational decisions. The name has already set the expectation.

If characters have no names at all—just roles or titles—the player learns that they are systems. The game is about the system itself. The mechanics that follow—optimization, efficiency, throughput—will be framed as engineering problems. The absence of a name has already set the expectation.

This is why naming is a mechanic and not a narrative decision. The name determines what kind of game the player thinks they’re playing before the game has shown them a single system. It is the first frame, and it colors everything inside it.

The Craft Problem: Naming From the Other Side

Interactive fiction writers and narrative designers face the same naming problem from the opposite direction. A game designer uses naming to tell the player what kind of relationship to expect. A writer uses naming to determine what kind of meaning a name should carry—weight, mystery, or mechanical function—and whether a procedurally generated name can serve that purpose or undercuts it.

The tension is real. On one hand, procedural naming tools have gotten remarkably good. A modern character name generator from Reedsy draws from over ten million names across dozens of languages and cultural traditions, and can filter by archetype, genre, setting, and personality. It returns names with etymological meanings attached, so a writer searching for a mentor figure in a Victorian London setting gets names whose origins reinforce the role. The tool surfaces names as deliberate craft decisions rather than random outputs—Dickens scoured cemeteries for Ebenezer Scrooge, Rowling combed phone directories, and a generator compresses that research into seconds.

On the other hand, the question is whether a name chosen by a system can carry the same weight as a name chosen by a person who understands the specific narrative argument the game is trying to make. The Reedsy generator can give you a name that fits a fantasy archetype. It can’t tell you whether that name should feel like a lie the character tells about themselves, a burden they carry, or a prophecy the game will eventually fulfill. That distinction matters. In Disco Elysium, the name Inland Empire isn’t just a reference to a David Lynch film. It’s a name that makes a stat feel like a voice. A generator could produce that name. It couldn’t produce the reason it matters.

For writers building narrative games, a fantasy name generator can serve as a structural drafting tool when the question is what a character is called before the story has decided what the character is for. But the naming decision that matters—the one that determines whether the name is a person, a unit, or a system—has to be made by the writer, because only the writer knows what argument the game is making about identity.

That same discipline applies to naming decisions: before publishing, editors need a way to test labels, roles, and public-facing language stay consistent, which is where a fantasy name generator that fits the project can function as a planning aid rather than a substitute for domain evidence.

This is also where the broader question of AI-assisted creative tools intersects with naming craft. The Authors Guild has taken an explicit position that a writer’s original voice and thinking constitute the irreducible core of authorship, and that foundational AI models have been trained on unlicensed creative works without compensation. The relevance to naming is direct: if a name is the first mechanic that tells a player what kind of relationship to expect with a character, then delegating that decision to a system trained on aggregated cultural data isn’t a neutral efficiency choice. It’s a design decision that affects what kind of identity the game assigns before the player ever interacts with it. A professional writing organization’s guidance on AI best practices argues that human creative voice is what makes a work yours—procedural naming tools can surface possibilities, but the selection and its narrative weight remain the writer’s responsibility.

Names as the First Argument

Every game with characters makes a naming decision. Most games make it without thinking about it. They pull from a pool, they assign a string, and they move on to the systems they consider more important. But the naming decision isn’t neutral. It’s the first argument the game makes about what kind of world the player is entering and what kind of beings inhabit it.

Darkest Dungeon argues that heroes are interchangeable and expendable, and its naming system ensures you feel that tension in every loss. Crusader Kings 2 argues that identity is dynastic and inherited, and its naming system makes you care about a name on a family tree more than a character on a screen. Disco Elysium argues that the self isn’t singular but a parliament of competing voices, and its naming system turns stats into characters with their own agency.

These aren’t narrative arguments. They’re mechanical arguments expressed through naming. The name isn’t the text that decorates the system. It is the system’s first move.

So here’s the question: if a name is the first mechanic that tells a player what kind of relationship they’re entering, what is your game saying about its characters before they’ve done anything at all? And if you don’t know the answer, who made that decision for you—the designer, the writer, or the generator?

When the Well Runs Dry: What Resource Scarcity Says About Your Game’s Soul

There’s a moment in a game when you realize you’re not going to make it. Not the dramatic, scripted kind of failure—the quiet one. You’re staring at a dwindling number in the corner of the screen. Health packs are gone. Ammo is a memory. The next room is full of enemies, and the math simply doesn’t work. The game, by its own internal logic, has already decided your fate. It just hasn’t told you yet. This isn’t a bug. It’s a thesis statement. How a game handles scarcity—what it makes precious, what it makes you trade, and what it lets you run out of entirely—is the most honest conversation a designer can have with a player. It’s where the abstract promises of a game’s narrative meet the cold, hard numbers of its simulation. And it’s where we, as players, discover what the game truly believes we are: careful stewards, desperate scavengers, or just another resource to be spent.

The Ledger of Loss: Scarcity as a Moral Argument

Most games treat resources as a pacing mechanism. You get a big gun, you blast through a horde, you’re low on ammo, so you switch to stealth. It’s a rhythm, a way to push the player between different verbs. But the real power of scarcity isn’t logistical; it’s philosophical. It forces a game to show its hand about value. In The Last of Us, a brick and a bottle are functionally identical as a distraction tool, but the game makes you choose which to carry. That single, seemingly trivial inventory slot is a quiet, devastating question: what is the worth of one empty glass container versus a piece of rubble? The game refuses to abstract it. You must decide, and in that decision, you’re not just managing space—you’re performing a tiny act of valuation in a world that has stripped almost everything of its old meaning. The scarcity isn’t of the items themselves, which litter the ground, but of the capacity to hold them. The game argues that in a fallen world, even your pockets become a site of moral triage.

Contrast this with the survival-crafting genre, which often falls into a trap of abundance disguised as scarcity. Punch a tree, get wood. The initial moments of Minecraft or Don’t Starve hum with a frantic energy because everything is finite. But as systems are mastered, scarcity often evaporates, replaced by logistics. The question shifts from “Will I survive the night?” to “How efficiently can I automate my survival?” The game’s argument about player choice changes with it. Early on, the world is a threat; later, it’s a spreadsheet. The most interesting games in this space, like Frostpunk, refuse to let scarcity become a solved problem. The cold never stops. Coal is always a heartbeat away from running out. The game’s central, brutal argument is that in a world of true, unrelenting scarcity, choice isn’t about optimization—it’s about deciding which part of your city’s soul you’re willing to amputate to see the sun rise.

The Invisible Hand That Slaps You: Scarcity as a Designer’s Confession

Every game with a resource system is, intentionally or not, a political economy simulator. The rules governing scarcity are a confession of the designer’s beliefs about fairness, merit, and human nature. Take the health system in a modern Far Cry game versus a classic Resident Evil. In Far Cry, health regenerates. Scarcity is a momentary, tactical inconvenience. The game believes you are a superhero who should never be permanently punished for a mistake, only briefly slowed down. The world is a playground that exists for your power fantasy. In Resident Evil (the early ones, at least), health is a finite, physical object—a green herb you must find, conserve, and agonize over using. The game believes you are a vulnerable person in a hostile place, and every bullet, every healing item, is a decision that echoes into the future. One game sees the player as an entitled consumer of spectacle; the other sees the player as a desperate survivor. Neither is objectively better, but the scarcity model is the game’s true opinion of you.

This becomes even more pointed in games that tie scarcity to social systems. Papers, Please is a masterpiece of this. Your resources are time and desk space. Your family needs food and heat. The state gives you a pittance and a rulebook. Every day, the game tightens the screws, not by throwing monsters at you, but by making the bureaucratic rules more complex while your family’s needs grow more urgent. The scarcity of time forces you to make choices that are ethically nauseating: do you deny a desperate refugee to process more passports and feed your son? The game’s design argues that under a system of manufactured scarcity, the player’s agency is a cruel illusion. You are not choosing between good and evil; you are choosing which flavor of complicity you can stomach. The mechanics don’t just represent a moral dilemma—they are the dilemma.

The Tyranny of the Optimal: When Scarcity Breeds Boredom

Here’s a dirty secret: scarcity, done poorly, is the most boring thing in games. It’s the reason I’ve abandoned dozens of otherwise competent RPGs halfway through. The problem is what I call the “potion hoarder’s paradox.” The game tells you that Elixirs of Mega Power are rare. So you never use them. You finish the final boss with 47 of them in your bag. The scarcity signal was so strong that it paralyzed choice entirely. The game’s intended argument—“Use these wisely for epic moments!”—was drowned out by the louder, mechanical argument: “You might need this later, so never use it.” The designer’s failure here is a failure to understand player psychology. Scarcity without a forcing function isn’t a prompt for strategic thinking; it’s a prompt for pathological conservation. The game becomes a museum of unused potential.

Compare this to the ammunition system in Control. The game’s signature Service Weapon doesn’t use ammo pickups; it recharges on a cooldown. This is a radical rejection of scarcity. The designers at Remedy argued, through their mechanics, that Jesse Faden is a powerhouse, a director of chaos, and scrounging for bullets would undermine that fantasy. The choice isn’t about whether to fire; it’s about when to fire, and which form to use. By removing one layer of scarcity, they deepened another: the scarcity of tactical opportunity. It’s a confident, opinionated move. It says, “We’re not interested in making you count bullets. We’re interested in making you feel like a telekinetic god who occasionally has to catch her breath.” And that’s a far more interesting conversation than “You have 12 shotgun shells, make them count.”

Scarcity as a Narrative Engine: The Stories We Tell Ourselves

The most profound effect of scarcity isn’t on the game state; it’s on the player’s internal narrative. When a game’s systems are generous, the story is the one the writers wrote. When resources are tight, a second, emergent story begins to play out in your head. This is the story of the time you limped through a blizzard in The Long Dark with 2% condition, a single match, and a can of dog food, and saw the warm glow of a trapper’s cabin just as the screen started to go black. That story isn’t in the game’s script. It’s a story the game’s scarcity mechanics allowed you to tell yourself. The designer’s role here is not to author that story, but to create the conditions under which it becomes possible. It’s a form of negative capability—the art of leaving enough space for the player’s own experience to rush in and fill the void.

This is where indie and experimental games often outshine their AAA cousins. A game like Darkest Dungeon understands that the most gripping scarcity isn’t of gold or trinkets, but of sanity and hope. Your heroes are a renewable resource, but their minds are not. You can always recruit another Crusader, but you’ll never get back the hours you spent nursing a paranoid, syphilitic Leper back from the brink, only to watch him die of a heart attack in a pitch-black corridor. The game’s mechanics argue that in a truly uncaring universe, the only resource that matters is your own emotional resilience. The choice isn’t “Which item do I buy?” but “How much of this can I take before I, the player, abandon this hamlet to its fate?” The game is a test of attrition, and the final, unspoken resource it’s depleting is your will to continue.

The Gift Economy: What Happens When You Give It All Away

If scarcity reveals a game’s beliefs about the player, then what does its opposite—radical generosity—reveal? There’s a small but fascinating tradition of games that refuse to make you want for anything, and in doing so, ask a completely different set of questions. Proteus is a game with no conflict, no inventory, and no fail state. You wander an island, and the island gives you sensory experiences. The game’s argument is that in the absence of scarcity, choice becomes purely aesthetic. You don’t have to do anything. You simply get to be. It’s a quiet, radical proposition in a medium built on systems of acquisition and expenditure.

More subversively, consider the “creative mode” in a survival game. When you turn off resource costs in Subnautica, you’re not just making the game easier—you’re fundamentally changing its genre. The terror of the deep ocean is replaced by the wonder of a giant aquarium. The game’s original argument—that the ocean is a beautiful but lethally indifferent food chain—is replaced by a new one: that the ocean is a sandbox for your imagination. The fact that this mode exists is a fascinating admission by the developers. They’re acknowledging that their own scarcity mechanics, however well-crafted, are a barrier to a different kind of relationship with the game world. They’re giving you the keys to the kingdom and saying, “We built a nightmare, but we also built a dream. Choose your own argument.”

Practical Criticism: How to Read a Game’s Resource Model

So, how do you, as a player and critic, dissect a game’s scarcity model to understand what it’s really saying? You start by asking a few uncomfortable questions. First: What is the game’s true currency? It’s rarely the one with the coin icon. In XCOM 2, the true currency is soldier experience, because a leveled-up squad is the one thing you can’t buy or build quickly. The game’s turn timers and escalating enemy difficulty are an argument that time itself is your most precious, non-renewable resource. Second: What can you trade, and what is sacred? In This War of Mine, you can trade almost anything—food, medicine, weapons, even your own moral integrity. But the game draws a hard, painful line at the lives of children. That boundary is the game’s ethical core, made visible through mechanics. Third: Who benefits from the scarcity? In Stardew Valley, the scarcity of energy and time in the early game is a gentle push toward community. You can’t do everything alone, so you’re nudged toward the town, toward the festivals, toward the relationships that will eventually help you automate your farm. The game argues that scarcity, in a kind world, is a catalyst for connection, not competition.

These questions aren’t just academic. They’re a toolkit for understanding why a game feels the way it does. A game that feels “grindy” is often a game where the scarcity model is out of sync with the narrative promise. The story says you’re a legendary hero, but the mechanics treat you like a middle manager working overtime for a meager bonus. The dissonance is the point of failure. A game that feels “tense” and “rewarding” has aligned its scarcity model with its tone. The mechanics are the subtext, and the subtext is consistent.

The Future of Famine: Where Scarcity Design Is Heading

We’re seeing a quiet revolution in how games handle scarcity, driven by a generation of designers who grew up with these systems and are now questioning their foundations. The rise of “cozy games” is a direct response to the tyranny of the optimal. These games often replace scarcity of materials with a scarcity of time or attention, but they remove the threat of catastrophic failure. You can’t starve in Animal Crossing, but you can miss a seasonal event. The game’s argument is that a life without mortal stakes is still a life full of meaningful choices—they’re just choices about beauty, friendship, and self-expression. It’s a rejection of the survivalist mindset that has dominated so much of game design.

On the other end of the spectrum, we’re seeing games that push scarcity into the space of the truly uncomfortable. Pathologic 2 is a game where everything is scarce: food, water, medicine, reputation, time, and even the reliability of your own senses. The game doesn’t just make you manage resources; it makes you doubt the very interface you use to manage them. A character might offer you a trade, and the game might lie about what you’ll receive. The scarcity of trust becomes the ultimate mechanic. This is a game that argues, through its systems, that in a true crisis, the rational actor model of economics is a cruel joke. You will make bad trades. You will be exploited. You will fail. And the only choice that matters is whether you try to be kind anyway.

This is the frontier. Games that don’t just use scarcity to create challenge, but to interrogate the very idea of choice under constraint. They ask not “Can you survive?” but “Who do you become when survival is all that’s left?” And that’s a question worth more than any pile of virtual gold.

Frequently Asked Questions

Why do some games make me hoard items I never use?

This is the “potion hoarder’s paradox,” and it’s a failure of design, not a player flaw. When a game signals that an item is extremely rare but doesn’t provide a clear, urgent moment where its use is the obvious best choice, the player’s risk-averse psychology kicks in. The fear of wasting the item on a suboptimal moment outweighs any potential benefit. The game’s scarcity signal is so strong it paralyzes decision-making. Better design either makes the item’s use case clear and immediate, or shifts the scarcity to a different resource, like a cooldown timer, to encourage active use.

How is scarcity in a single-player game different from a multiplayer game with an auction house?

In a single-player game, scarcity is a conversation between the designer and the player. The designer sets the rules, and the player responds within a closed system. In a multiplayer game with a player-driven economy, scarcity becomes a social phenomenon. The value of an item isn’t just set by its drop rate, but by player speculation, guild monopolies, and collective behavior. The designer loses some control over the argument. A rare sword in a single-player RPG is a reward for exploration; the same sword in an MMO is a status symbol, an investment vehicle, and a potential source of inequality. The scarcity is no longer just a game mechanic—it’s a political and economic force shaped by the community.

Can a game have no resource scarcity and still be engaging?

Absolutely. Games like Proteus, Journey, or the creative modes in survival games prove that engagement doesn’t require a fear of loss. These games shift the focus from extrinsic motivation (earning, surviving) to intrinsic motivation (exploring, expressing, experiencing). The “scarcity” in these games is often one of knowledge or sensory novelty—you want to see what’s over the next hill, or hear how the music changes. The choice isn’t about managing a dwindling supply; it’s about directing your attention. This approach argues that player agency can be about curiosity and presence, not just acquisition and expenditure.

What’s the first thing I should look at to understand a game’s scarcity model?

Ignore the main currency. Look at the resource that is most annoying to run out of, and the one that is most painful to lose. In Dark Souls, that’s souls, which are both currency and experience, and are dropped on death. The game’s entire tension is built on that single mechanic. In a management sim, it might be worker happiness or environmental stability. That “pain point” resource is the game’s true currency, and the rules around its loss and recovery are the clearest statement of what the game values. Everything else is just set dressing.

The Price of Everything: How Resource Scarcity in Games Reveals What Designers Think About Player Choice

Resource scarcity isn’t just another difficulty slider. It’s a philosophical argument about what players value, how they spend their attention, and which choices should leave a mark. In game design, scarcity is the mechanism that forces us to rank our desires. When a survival game hands you three bullets and two threats bearing down, it’s asking a question. When a management sim makes you pick between a hospital wing and a public park, it’s making a statement. This article digs into how indie and experimental games use limited resources to build arguments about agency, value, and human choice—and what those arguments spill about the designers who made them.

The Currency of Constraint: Why Scarcity Is a Design Argument

Every game with a resource system makes a claim about the world. In Papers, Please, time is the scarce resource, and the game argues that survival under bureaucracy forces moral compromise. You can’t process every entrant carefully, feed your family, and resist the regime all at once. The design doesn’t just present a challenge; it builds a thesis: when systems squeeze people, decency becomes a luxury good. Lucas Pope doesn’t tell you this in a cutscene. He makes you feel it in the pit of your stomach when you stamp a passport you know you should reject.

Compare that to Stardew Valley, where energy is the daily constraint. You can clear a few trees, water some crops, and maybe chat with a neighbor before you collapse. The scarcity is gentle but real. Eric Barone’s argument is different: a good life is about choosing where to put your limited self, not about maximizing every yield. The game rewards you for fishing all day, but it also rewards you for standing in the town square doing nothing. Scarcity here isn’t a punishment; it’s a gentle reminder that you’re finite, and that finitude is what makes afternoons meaningful.

When Scarcity Lies: The Fake Choice Problem

Not all resource systems respect player agency. Some games present scarcity as a dramatic prop while quietly making sure you never face a real loss. That’s the fake choice problem. In plenty of AAA open-world games, you can craft, scavenge, and buy your way out of any shortage. The game pretends resources are limited, but the economy is rigged so you always have enough. The design argument here is cynical: players want the feeling of tough decisions without the consequences. It’s a theme park of scarcity, not an honest system.

Indie games often push back against this. This War of Mine makes scarcity a moral wound. Food, medicine, and shelter are genuinely insufficient. You’ll watch characters starve or fall into depression because you chose to craft a weapon instead of a bed. The game doesn’t let you grind your way out. The scarcity is the point. The designers at 11 bit studios are arguing that in war, there are no optimal builds—only survivors making terrible calculations with whatever they have left.

The Invisible Hand of the Designer: Three Scarcity Philosophies

After years of analyzing mechanics, I’ve started sorting scarcity systems into three rough philosophies. They’re not rigid categories, but they help reveal what a game is actually saying under the hood.

1. The Puritan Model: Scarcity as Moral Test

In the Puritan model, resources are scarce because the world is fallen, and your job is to prove your worth through discipline. Frostpunk is the poster child here. Coal, food, and hope are all running out, and the game constantly asks you to sign away your humanity to keep the generator running. Child labor, corpse disposal, radical laws—each choice is framed as a necessary evil. The design argues that survival justifies authoritarianism, but it also lets you feel the cost. You’re not just managing a city; you’re managing your own guilt. The scarcity is a mirror.

Other games in this vein include Darkest Dungeon, where gold, torches, and sanity are all bleeding away, and the game judges you for treating heroes as disposable. The Puritan model tends to produce games that feel heavy, accusatory, and unforgettable. They don’t want you to win comfortably. They want you to remember what you sacrificed.

2. The Romantic Model: Scarcity as Appreciation

The Romantic model uses scarcity to make ordinary things feel precious. Outer Wilds does this with time. You have 22 minutes before the sun explodes, and that loop is the only resource that matters. You can’t hoard it, extend it, or trade it. The game argues that a finite lifespan is what gives knowledge and connection their weight. Every discovery feels earned because you spent your one irreplaceable resource—attention—on it. The scarcity isn’t about suffering; it’s about savoring.

Kentucky Route Zero takes a different Romantic approach. Money is mentioned but rarely tracked. The real scarcity is emotional energy. Characters run out of the ability to explain themselves, to care, to stay. The game argues that under late capitalism, the resource we’re truly losing is each other. It’s a quiet, devastating claim, and it works because the mechanics refuse to quantify what actually matters.

3. The Systemic Model: Scarcity as Emergent Storytelling

Here, scarcity is a neutral force that generates unpredictable narratives. RimWorld is the prime example. Food, medicine, components, and mood are all limited, but the game doesn’t prescribe a moral lesson. Instead, it creates conditions where stories happen. A colony might resort to cannibalism not because the designer wanted to make a point about desperation, but because the systems collided in a way that made it the only option. The argument is that scarcity is simply a fact of complex systems, and human behavior under pressure is fascinating to watch.

This model trusts the player to find meaning. It’s the most agnostic of the three, but it still carries a quiet thesis: given enough constraints, people will reveal themselves. The designer’s role is to set the table, not to preach the sermon.

When Scarcity Breaks: The Exploit as Critique

Players often push back against scarcity by finding exploits. In Don’t Starve, veteran players build elaborate farms that trivialize hunger. In Subnautica, you can eventually grow enough food and generate enough power to ignore the survival meters entirely. Some designers see this as failure. I see it as a conversation. When players break a scarcity system, they’re answering the game’s argument with one of their own: “I reject your premise. I will build abundance.”

The most honest games allow this. Factorio starts with you hand-mining iron plates under threat of alien attack. By the end, you’ve automated an entire planet. The scarcity was never the point; the point was the journey from powerlessness to godhood. The game’s argument shifts as you play, and that shift is the real narrative. Designers who patch out every efficiency exploit are often protecting their thesis from player dissent. That’s not design; that’s dogma.

What Your Inventory Says About You

There’s a moment in Resident Evil 4 where you spend five minutes rotating a fish inside an attaché case. It’s absurd, but it’s also intimate. Inventory management is the most personal form of scarcity. A limited grid forces you to decide what kind of player you are. Do you carry extra healing items because you’re cautious? Do you hoard ammunition for a boss that might never come? The inventory becomes a self-portrait.

Indie games have pushed this further. In Disco Elysium, your inventory includes thoughts, clothes, and tools, but the real scarce resource is your own psychological stability. You can equip a thought that makes you better at intimidation but slowly erodes your morale. The game asks: what are you willing to carry in your mind? It’s inventory management as therapy, and it reveals more about the player than any dialogue wheel ever could.

Scarcity and the Illusion of Control

Some of the most interesting scarcity designs are the ones that lie to you. Hellblade: Senua’s Sacrifice warns that dying too many times will permanently delete your save. The threat is a fabrication—the game never actually does it—but the fear reshapes every encounter. The scarcity is psychological, and the design argument is about how anxiety distorts decision-making. It’s a game about psychosis that uses a fake resource mechanic to make you feel genuinely vulnerable.

This approach is risky. If players discover the lie, they feel betrayed. But when it works, it creates a rare kind of ludonarrative harmony. The mechanic isn’t just representing the character’s experience; it’s infecting the player’s own mental state. That’s the power of scarcity when it’s wielded with precision.

Building a Scarcity System That Respects Players

After dissecting dozens of these systems, I’ve come to a few principles for designers who want to use scarcity ethically and effectively. First, scarcity must be legible. Players need to understand what’s limited, why, and what the tradeoffs are. Obscuring this information isn’t difficulty; it’s obfuscation. Second, scarcity should create interesting branches, not dead ends. A game that starves you into a fail state without offering alternative paths is just a bully. Third, scarcity should be consistent with the game’s argument. If your game is about hope, don’t make resources so punishing that players give up. If your game is about despair, don’t hand out second chances like candy.

Finally, let players subvert the system. The most memorable moments in resource-driven games come when players find creative solutions the designers never anticipated. That’s not a bug; it’s the highest form of player agency. A system that can’t be broken is a system that doesn’t trust its players.

FAQ: Resource Scarcity and Player Choice

Why do some games make resources so scarce that they stop being fun?

Often, it’s because the designer is prioritizing a thematic argument over conventional fun. Games like This War of Mine or Pathologic use oppressive scarcity to communicate something about suffering, survival, or moral weight. The goal isn’t entertainment in the traditional sense; it’s understanding. Whether that tradeoff works depends on the player’s expectations. If you go in expecting a power fantasy, you’ll be disappointed. If you go in expecting a meaningful experience, the scarcity becomes the point.

How can I tell if a game’s resource system is actually fair?

Look for transparency and consistency. A fair system tells you the rules and sticks to them. If a game hides drop rates, changes mechanics without warning, or creates artificial bottlenecks that can only be solved through grinding or microtransactions, the scarcity isn’t a design choice—it’s manipulation. Fair systems also provide multiple paths to resources, even if some are harder than others. If there’s only one way to get a critical item and it requires luck, the system isn’t respecting your time or your choices.

What’s the difference between scarcity and difficulty?

Difficulty is about execution—how hard it is to perform an action. Scarcity is about availability—how many options you have and what they cost. A game can be difficult without being scarce (think Celeste, where you have infinite attempts but demanding platforming). A game can be scarce without being difficult (think Papers, Please, where the actions are simple but the resource of time forces hard prioritization). The most intense games combine both, but they’re distinct design tools that create different kinds of pressure.

Can a game have too much abundance?

Absolutely. When resources are unlimited, choices lose weight. If you can buy every upgrade, recruit every character, and unlock every path, the game stops being about decisions and starts being about completionism. Abundance can work if the game’s argument is about freedom or creativity—Minecraft’s creative mode is a valid design—but in a game that wants you to care about consequences, too much abundance flattens the experience. The sweet spot is enough scarcity to make choices matter, but not so much that the player feels punished for experimenting.

Resource scarcity is never just a number on a spreadsheet. It’s a statement of values. The next time a game asks you to choose between two things you desperately need, pay attention to what it’s really saying—and what you’re willing to give up in return.

Why Game Menus Are the Most Overlooked Design Argument in Any Game

Every game has a moment before the game begins. You press start, the title card fades, and something appears on screen—a grid, a cursor, a blinking text field, a clock. This is the menu. We have been trained to treat it as logistical overhead: the thing you click through to reach the thing you want. But the menu is where the designer’s assumptions about you become legible. Not in the narrative. Not in the art direction. In the interface. The menu is the only place in a game where the rules of engagement are stated explicitly before play begins—where the game tells you what kind of attention it expects, how much of your time it plans to occupy, and whether it considers you a guest or an employee.

Most players never read menus as design. They experience them as friction. But friction is design. The distance between pressing a button and seeing its result is an argument about how much the designer trusts you to act deliberately. The number of clicks between you and a save file is an argument about whether your time belongs to you or to the game. The fact that you must name your character before you can move is an argument about whether identity is something you bring to the game or something the game assigns to you. These are not neutral interface decisions. They are ideological positions rendered as buttons and grids.

The Attache Case: Inventory as Spatial Anxiety

Resident Evil 4’s inventory system is the most overanalyzed mechanic in survival horror, and I am about to overanalyze it again, because it deserves it. Leon’s attache case is a grid. Items occupy rectangles of varying size. You rotate them, nestle them alongside one another, and rearrange them every time you pick up something new. The grid is finite. The items are awkward. The act of managing the case takes longer than the act of shooting the ganados that drop the items.

Here is what the grid argues: that survival is not about what you carry but about what you can fit. The grid makes inventory a spatial problem, not a numerical one. Most games before RE4—and most games after—treated inventory as a weight limit or a slot count. You can carry twelve items. You can carry fifty kilograms. The specific shape of each item is irrelevant. The attache case rejects this abstraction. A rifle is not “one item.” It is a long, horizontal rectangle that will not fit next to your shotgun unless you rotate it vertical, and if you rotate it vertical, it blocks the column where you wanted to put the first aid spray.

[annotation: The attache case grid in RE4. Items are irregular rectangles. The grid is tight. The cursor moves in discrete steps. Every placement decision locks out adjacent space. The interface communicates scarcity through geometry, not numbers.]

This is an argument about anxiety under pressure. A weight limit says “you must choose what to carry.” The attache case says “you must choose how to arrange what you carry, and the arrangement itself is a cost.” The cognitive load of tetris-ing your inventory is the mechanic’s point. The game does not want you to feel that you have enough. It wants you to feel that you almost have enough, that one more pickup will require a sacrifice, that the space itself is hostile. The grid is not a container. It is a pressure chamber.

The remake of RE4 softened this. The grid is still present, but items are less irregular, the case is larger, and the crafting system lets you consolidate ammunition into compact stacks. The remake’s interface argues something different from the original: that inventory tension should be a flavor, not a tax. This is a defensible position. It is also a completely different argument about what survival horror should feel like, and it was made entirely at the menu level, without changing the story, the enemies, or the core combat loop.

The Stamp and the Clock: Papers, Please and Interface as Labor

If RE4’s inventory grid makes scarcity spatial, Papers, Please makes morality clerical. The game’s interface is a desk. You drag documents, align stamps, check dates, and cross-reference rulebooks. The clock ticks. The queue of applicants grows. Every approval or denial is a stamp—a single, physical, satisfying mechanical action—and every stamp is a moral decision compressed into a bureaucratic gesture.

The menu in Papers, Please is the game. There is no layer beneath the interface where the “real” game happens. You are not playing a character who stamps documents. You are stamping documents. The interface does not represent labor. It is labor. And the clock at the top of the screen is not a timer. It is a wage argument. You earn money per processed applicant. You need money for food, heat, medicine. The clock is the mechanism that converts your moral decisions into economic pressure. You want to be careful, to read each document closely, to catch the forgeries. The clock says: you cannot afford to be careful. The interface says: your carefulness has a price.

[annotation: The Papers, Please desk interface. The clock dominates the upper right. The rulebook is a separate tab you must open and close. Every document is draggable. The stamp is the only object that makes a sound. The interface trains you to associate moral action with manual effort.]

This is what makes the stamp mechanic ideologically distinct from a dialogue-wheel moral choice. When a BioWare game asks “save or sacrifice,” the decision is abstract, weightless, reversible by reload. When Papers, Please asks you to deny entry to a woman whose papers are expired, the decision is physical. You drag the denial stamp to her passport. You press the button. The stamp lands. The ink dries. She leaves. The interface makes you perform the refusal with your hands. There is no “undo” for a stamp. The game does not autosave before moral decisions. It autosaves after them. The menu is where ethics become manual labor, and the argument is that bureaucracy is not a system that processes moral decisions—it is a system that replaces them with procedural actions until the person performing them stops feeling the weight.

The Naming Screen: Identity as First Contract

Before you manage inventory, before you stamp passports, before you even see the game world, many games ask you to type a name. This is the naming screen, and it is the first contract between designer and player. The game asks: who are you? And the interface constrains how you can answer.

Some games give you a blank field. Some give you a list. Some generate a name for you and ask you to accept it. The constraints are not technical. They are ideological. A blank field says: bring yourself to this game. A list says: choose from the selves we have prepared. A generated name says: you are who we say you are, and your only agency is to accept or resist.

Disco Elysium does not let you name your character. You wake up with a name already assigned—Raphael Ambrosius Costeau—and the game’s opening hours are partly about discovering what that name means, what it has done, and whether you want to keep it. The naming screen is replaced by an amnesia screen. You do not choose who you are. You choose whether to remember. The Thought Cabinet extends this: thoughts arrive as cards you can equip, and equipping them changes your character’s internal monologue, available dialogue options, and skill behavior. Identity is not chosen at the start. It is accrued, revised, and sometimes inflicted. The game’s interface treats consciousness as inventory you cannot drop—items that take up space in your mind, that can be equipped and unequipped but never fully discarded, and that shape what you are capable of perceiving.

Kentucky Route Zero does something quieter. The game gives you names to choose from at various points, but the names are not your character’s name. They are the names of other people—coworkers, strangers, figures from the past. You are assigning identities to characters you do not control, filling in gaps in a story you are witnessing rather than driving. The naming screen in Kentucky Route Zero is not about self-expression. It is about complicity. The game asks you to name someone, and by naming them, to accept responsibility for their existence in the narrative. The interface makes you a co-author, but not of yourself. Of the world.

That same discipline applies to title and framing decisions: before publishing, editors need a way to test a heading promises the same thing the article actually delivers, which is where novel title ideas that fit the project can function as a planning aid rather than a substitute for domain evidence.

[annotation: Kentucky Route Zero’s naming prompts appear mid-dialogue, not on a title screen. The cursor blinks in a text field embedded in the conversation. There is no confirmation prompt. Once you type and press enter, the name is committed. The interface treats naming as a narrative act, not a pre-game configuration.]

The naming screen is also where game design faces the same constraint problem that external ideation tools attempt to solve for writers. A tool that generates novel title ideas from genre and tone parameters is doing something structurally similar to what a game naming menu does: it defines the boundaries of acceptable output before the user engages. The difference is that a game naming interface does this to a person who is about to inhabit the identity being constrained, while an external generator does it for a creator who will evaluate the output from outside. Both are arguments about the relationship between constraint and authorship—but only the game menu forces the user to live inside the constraint it imposes.

Constraint, Authorship, and the Interface as Argument

The naming screen connects to a broader principle that runs through every menu type I have discussed: the interface is where constraint becomes ideology. A game’s title is also a naming decision—a contract between creator and audience that precedes the content. “Resident Evil” argues that horror is domestic. “Papers, Please” argues that bureaucracy has a voice. “Disco Elysium” argues that decadence is a place. These are not descriptions. They are positions, and they are made before the player touches a single mechanic.

The same principle applies to the tools creators use to arrive at those positions. A parameterized title generator like the one documented at Reedsy’s book title generator lets you input genre, tone, and core conflict to produce title candidates. The interface is a set of constraints—dropdown menus, radio buttons, text fields—that frame naming as a system of parameters. This is structurally identical to a game’s naming screen: both define the boundaries of acceptable output before the user engages. The generator’s output is only useful when the author recognizes that the title is not a label—it is the first argument the work makes. The tool can produce candidates, but the ideological decision of which candidate fits the argument remains human.

The Authors Guild has made a related argument about what happens when naming decisions are delegated to machines. Their best practices guide for authors navigating AI tools treats naming as a profession-defining act—one that machines can approximate but cannot author, because the ideological weight of a title cannot be parameterized without flattening the very contract it establishes. The guide’s concern maps directly onto game interface design: a generated character name is not the same as a chosen character name, because the act of choosing is what makes the name meaningful. When the system assigns identity, the player’s relationship to that identity shifts from authorship to negotiation.

Sometimes that shift is the point. Disco Elysium’s pre-assigned name is a deliberate argument about amnesia and self-reconstruction. Kentucky Route Zero’s naming prompts are a deliberate argument about complicity and authorship. In both cases, the menu is making an argument the designer intended. But when a naming screen defaults to a generated name without thought—when the constraint is simply a default the designer did not evaluate—the menu is making an argument the designer did not intend, and the player is living inside it without recognizing the contract they have been forced to sign.

The Save Dialog: Time as Territory

One more menu, because it is the one that reveals the most. The save dialog. Every game that has one is making an argument about your time, and the argument is encoded in the interface.

A save-anywhere system says: your time is yours. You can leave when you want. The game will wait. A checkpoint system says: your time is partly ours. You can leave, but only at moments we designate, and if you leave mid-section, you lose progress. A save-only-at-inns system says: your time is ours, and rest is a resource you must purchase. An autosave-only system says: you cannot leave. You can stop playing, but the game decides when your progress counts. You are not in control of your own exits.

Outer Wilds has no manual save. The game autosaves when you die, and you die every twenty-two minutes when the sun explodes. The save system is the time loop. Your progress is your knowledge, which persists across loops, but your physical state resets. This is not a save system bolted onto a game. It is a game built around a save system. The interface argues that the only persistent resource is what you know, and that knowledge is the only thing worth saving. The game does not let you save your position because your position does not matter. It lets you save your understanding because your understanding is the only thing that changes.

Compare this to a game that lets you save anywhere but also lets you reload anywhere. The quicksave-quickload loop is an argument about failure: that failure is reversible, that the player should never have to live with consequences, that the optimal play pattern is to save before every decision and reload if the outcome is unsatisfactory. This is a philosophical position. It says: the game does not trust you to learn from mistakes. It trusts you to avoid them through save-scumming. The interface has decided that consequence is optional, and it has made that decision at the menu level, without a single line of dialogue or a single frame of cutscene.

[annotation: A comparison of save interfaces. Outer Wilds: no save button, autosave on death, death is periodic and inevitable. Quick-save games: save button mapped to a hotkey, instant, unlimited. The difference is not convenience. It is whether the game considers failure a state to be erased or a state to be incorporated.]

The Designer’s Responsibility: Menus Are Never Neutral

Here is the problem with treating menus as overhead: every default is a decision, and every decision is an argument. When a designer ships a menu they did not think about, they have not avoided making an argument. They have made one accidentally, and accidental arguments are the worst kind because the designer cannot defend them, the player cannot read them, and the critic cannot evaluate them. They simply exist, shaping the player’s relationship to the game without anyone acknowledging that shaping is happening.

How Resource Scarcity in Games Reveals What Designers Think About Player Choice

Resource scarcity is the quiet engine of game design. It’s the gap between what a player wants and what the system allows, and it’s never neutral. Every time a game tells you that you can’t afford a weapon, that your mana pool is empty, or that you must choose between healing and upgrading, the designer is making an argument about how you should think, plan, and value your options. Scarcity isn’t just a balancing knob; it’s a rhetorical device. It shapes the player’s internal monologue, forces trade-offs, and exposes the designer’s assumptions about agency, pressure, and even morality. In this article, I treat games as argument machines disguised as entertainment, and I’ll dissect how resource scarcity functions as the primary syntax of that argument. Whether you’re a systems designer, a critic, or a player who wants to understand why a game feels the way it does, this analysis will give you a framework for reading the design intent behind every empty inventory slot.

The Grammar of Scarcity: What Designers Say Without Words

Every game with resources has a scarcity model, even if it never announces it. The model is a set of rules that govern how much of a resource exists, how it regenerates, and what it costs. These rules aren’t just technical; they’re philosophical. A designer who makes health potions rare and expensive is arguing that survival should feel fragile and that mistakes should carry lasting consequences. A designer who lets health regenerate quickly after combat is arguing that each encounter should be a self-contained puzzle, not a war of attrition. Neither choice is objectively correct, but each one creates a different relationship between the player and the game’s world.

Consider the difference between hard scarcity and soft scarcity. Hard scarcity means a resource is finite: once it’s gone, it’s gone forever. This appears in games like Resident Evil (1996), where ammunition and healing items are limited, and every wasted bullet echoes into the late game. Soft scarcity means a resource is limited in the moment but replenishable over time or through effort, like the estus flasks in Dark Souls that refill at bonfires. Hard scarcity argues that the player should feel the weight of permanent consequence. Soft scarcity argues that the player should experiment, fail, and learn without being permanently punished. Neither is more “difficult” in a simple sense; they just demand different kinds of attention.

Designers also use relative scarcity, where a resource is abundant but the player’s capacity to carry or use it is constrained. Inventory limits in Deus Ex or Resident Evil 4 are classic examples. The world is full of items, but the player’s grid is not. This forces a constant, low-grade negotiation: do I keep the grenades for a hypothetical boss, or the herbs for immediate safety? The designer is arguing that preparation and foresight are skills worth testing, and that the player’s backpack is a mirror of their priorities.

Scarcity as a Lens on Player Agency

Agency in games is often discussed as the player’s ability to make meaningful choices. Resource scarcity is the primary tool for making choices meaningful. If a player can afford everything, the choice of what to buy is trivial. Scarcity forces the player to commit to a path and live with the consequences. This is where design intent becomes visible. A game that offers many mutually exclusive upgrades, each requiring a rare resource, is arguing that specialization and replayability matter more than convenience. A game that lets the player respec their character for a small fee is arguing that experimentation and forgiveness are higher values.

Take XCOM 2 as an example. The game runs on a clock, and time is the ultimate scarce resource. You cannot research every technology, build every facility, and respond to every crisis. The designer is forcing you to make strategic bets under uncertainty. This isn’t just a difficulty mechanism; it’s an argument about the nature of command. The game is telling you that leadership means making hard choices with incomplete information and living with the casualties. The scarcity of time creates a narrative of desperate triage that no amount of cutscene dialogue could match.

Contrast this with a game like Hades, where resources are scarce within a single run but accumulate permanently across runs. Darkness, keys, and gemstones are limited during each escape attempt, but they feed into a long-term progression system. The designer is arguing that failure is not a dead end but a stepping stone. The scarcity inside the run creates tension; the abundance across runs creates hope. This dual-layered scarcity is a sophisticated argument about persistence and growth, and it’s a major reason the game feels so generous despite its difficulty.

When Scarcity Becomes a Moral Argument

Some games use scarcity to make the player confront ethical dilemmas. This War of Mine is the most direct example. Food, medicine, and materials are brutally scarce, and the player must decide whether to steal from the vulnerable, hoard supplies, or share with neighbors. The scarcity isn’t just a gameplay mechanic; it’s the entire thesis of the game. The designer is arguing that survival under siege forces impossible trade-offs, and the player’s choices reveal their own moral boundaries. The game doesn’t judge you with a karma meter; it lets the consequences of your scarcity-driven decisions accumulate into a story that you have to live with.

Even in less overtly political games, scarcity can carry a moral charge. In BioShock, the choice to harvest or save Little Sisters is a resource decision wrapped in an ethical one. Harvesting gives more ADAM immediately, but saving them yields gifts later. The designer is arguing that altruism has a long-term payoff, but the scarcity of ADAM in the early game makes the immediate temptation real. The system is designed to make you feel the pull of selfishness, and that feeling is the argument.

How Scarcity Shapes Player Psychology

Scarcity doesn’t just affect in-game decisions; it changes how players think and feel. Behavioral economics has long studied how scarcity affects human cognition, and game designers are practical psychologists. When a resource is scarce, players become more focused, sometimes to the point of tunnel vision. They weigh options more carefully, but they also experience more stress. This stress can be a design tool: horror games use ammo and health scarcity to create anxiety, while survival games use food and water scarcity to create a constant, gnawing pressure.

However, scarcity can backfire if it feels arbitrary or unfair. Players are quick to notice when a game’s economy is “broken”—when resources are so scarce that optimal play becomes tedious, or so abundant that choices lose meaning. A well-tuned scarcity model respects the player’s time and intelligence. It creates tension without frustration, and it rewards planning without demanding prescience. The best designers treat scarcity as a conversation with the player, not a lecture.

One underappreciated aspect is information scarcity. In many strategy games, the player lacks perfect knowledge of the map, enemy positions, or future events. This uncertainty is a resource constraint on the player’s ability to plan. Games like Frostpunk or Darkest Dungeon use information scarcity to create a sense of precariousness. You never know if the next storm or the next hallway will break you. The designer is arguing that true mastery involves managing not just what you have, but what you do not know.

Scarcity and the Illusion of Choice

Not all choices created by scarcity are real. Some games present the player with multiple options that are functionally identical, or where one option is so clearly optimal that the others are traps. This is the illusion of choice, and it’s a failure of design. When a game offers three weapons but one is mathematically superior in all situations, the scarcity of upgrade materials doesn’t create meaningful decisions; it creates a test of whether the player has read the wiki. Good scarcity design ensures that each option has a distinct role, a situational advantage, or a trade-off that makes the choice genuinely interesting.

Consider the difference between Civilization VI and a simpler strategy game. In Civ, the scarcity of production, science, culture, and faith forces the player to prioritize a victory condition and adapt to the map. There is no single best path because the map, opponents, and random events change every game. The scarcity is real because the context is dynamic. In a game with a static optimal strategy, scarcity becomes a math problem, not a design argument.

Scarcity as a Narrative Engine

Resource constraints don’t just affect mechanics; they write stories. The player who runs out of ammo in The Last of Us and must sneak past a clicker is experiencing a narrative beat that emerged from scarcity. The designer set the stage, but the scarcity of bullets authored that specific moment of tension. This is the power of systemic storytelling: the game’s rules generate unique, personal narratives without scripting them.

In multiplayer games, scarcity becomes a social force. In Valheim, iron is scarce and must be transported across dangerous seas. This creates emergent stories of Viking voyages gone wrong, of ships lost to serpents, of shared grief and triumph. The designer’s argument is that shared hardship creates memorable stories. If iron were abundant, those stories wouldn’t exist. The scarcity isn’t just a balancing lever; it’s a narrative engine.

Even in competitive games, resource control tells stories. In StarCraft II, the fight over mineral lines and expansion bases is the central drama of every match. The designer’s argument is that conflict arises from competition over limited resources, and the player who controls those resources controls the narrative of the match. The scarcity of minerals and vespene gas is the entire reason the game exists as a contest.

Designing Scarcity: A Framework for Analysis

When you encounter a resource system in a game, you can reverse-engineer the designer’s intent by asking a few key questions. This framework will help you move from “I like this” or “this feels bad” to a precise understanding of what the system is arguing.

1. What is the resource’s purpose?

Is it a pacing mechanism (health, stamina), a progression gate (experience, currency), or a strategic lever (mana, cooldowns)? The purpose determines how scarcity should feel. A pacing resource should create tension and release; a progression resource should create long-term goals; a strategic resource should create moment-to-moment decisions.

2. How is scarcity communicated?

Does the game show you exactly how much you have and how much you need, or does it obscure the numbers? Explicit communication (like a clear cost on a tooltip) argues that the player should make calculated decisions. Implicit communication (like a dimming screen when health is low) argues that the player should rely on intuition and feeling. Both are valid, but they create different relationships with the player.

3. What is the replenishment model?

Is the resource finite, slowly regenerating, or easily farmable? Finite resources create permanent consequences and encourage careful, conservative play. Slowly regenerating resources create windows of vulnerability and encourage timing-based decisions. Easily farmable resources shift the scarcity from the resource itself to the player’s time and patience, which is a different kind of argument about grind versus challenge.

4. Who controls the scarcity?

In some games, the player controls resource flow through their actions (e.g., building an economy in an RTS). In others, the designer controls it through fixed placements and drop rates. Player-controlled scarcity rewards system mastery and optimization. Designer-controlled scarcity rewards exploration and adaptability. The balance between these two reveals whether the game sees the player as an engineer or an explorer.

5. What happens when scarcity is removed?

This is the ultimate test. If you gave the player infinite resources, would the game still be interesting? If yes, then scarcity isn’t the core of the experience; it’s a supporting element. If no, then scarcity is the experience. Minecraft in creative mode is still interesting because building and exploration are intrinsically rewarding. Resident Evil with infinite ammo loses its identity. Understanding this distinction helps you see what the designer values most.

Scarcity as a Mirror of Design Philosophy

Every resource system is a thesis statement. When a game like Dark Souls ties health, stamina, and currency to the same limited pool (souls), it’s arguing that all forms of power are interconnected and that every death is a lesson in resource management. When a game like Stardew Valley gives you a small energy bar that forces you to end each day, it’s arguing that life is about making the most of limited time and that rest is a necessary part of the rhythm. When a game like Doom Eternal forces you to glory-kill for health, chainsaw for ammo, and flamethrower for armor, it’s arguing that aggression is the only path to survival and that passivity is death.

These aren’t just mechanics; they’re worldviews encoded in systems. The designer isn’t just asking you to press buttons; they’re asking you to internalize a set of values. Scarcity is the language they use to make that argument persuasive. When you feel the tension of low ammo in Doom Eternal, you’re not just solving a resource problem; you’re being taught to play the game the way the designer wants you to play it—aggressively, relentlessly, without retreat.

This is why scarcity design matters so much. It’s not just about balance or difficulty; it’s about the kind of experience the designer wants to create and the kind of player they want you to become. A game that’s too generous can feel patronizing, as if the designer doesn’t trust you to handle pressure. A game that’s too stingy can feel sadistic, as if the designer enjoys watching you suffer. The sweet spot is a scarcity model that feels fair, challenging, and expressive—one that lets you make choices that reflect your own values, not just the designer’s.

FAQ

Why do some games feel frustrating even when resources are abundant?

Abundance can create its own kind of frustration when it removes meaningful choice. If you can afford everything, decisions become trivial, and the game can feel like a checklist rather than a challenge. Frustration often comes from a mismatch between the scarcity model and the game’s core fantasy. A power fantasy game with stingy resources feels contradictory, just as a survival game with overflowing supplies feels pointless.

How can I tell if a game’s resource scarcity is well-designed?

Look for three signs: the scarcity creates interesting trade-offs, the consequences of your choices are clear and fair, and the system supports the game’s emotional tone. A well-designed scarcity model makes you pause and think, but it never makes you feel cheated. If you find yourself blaming the game rather than your own decisions, the scarcity model may be poorly tuned or poorly communicated.

Do mobile games use scarcity differently than PC or console games?

Yes, and often problematically. Many mobile games use artificial scarcity to drive monetization, creating pain points that can be solved with real money. This turns scarcity from a design tool into a business tactic. The designer’s argument shifts from “here is an interesting challenge” to “here is a problem you can pay to remove.” This is why many players are skeptical of free-to-play economies: the scarcity doesn’t serve the game’s design; it serves the game’s revenue model.

Can a game have no resource scarcity and still be engaging?

Yes, but it must find other sources of tension and meaning. Games like Journey or Proteus have no traditional resources, but they create engagement through exploration, beauty, and emotional arcs. In these cases, the scarcity is not of items but of knowledge, time, or experience. The designer is arguing that not all games need to be about optimization and that presence and discovery can be their own rewards.

Resource scarcity is the grammar of game design, and every game speaks a dialect of it. By learning to read that dialect, you can see past the surface of a game and into the mind of its creator. You can understand not just what a game is asking you to do, but what it is asking you to value. And that’s the first step toward playing games critically, not just consuming them.

How Game Text Boxes Teach Values Before They Teach Mechanics

Most games teach you their values before they teach you their controls. A tutorial that hands you a weapon and says “kill” is making a claim about what your body is for. A tutorial that hands you a text box and says “read” is making a claim about what your mind is for. And a tutorial that hands you a text box and says “write”—that is making the boldest claim of all: that language itself is a mechanic, not decoration.

The text box is the most unexamined pedagogical tool in game design. We have written thousands of essays about camera distance and health regeneration and checkpoint placement. Almost nothing about the moment a game asks you to read or write within its world and what that act is supposed to mean. When a game surfaces text—a journal entry, a dialogue prompt, a codex article, a deduction field—it is deciding whether language is something you do or something you consume. That decision is never neutral. It is an argument about whether knowledge is something you build or something you receive, whether identity is something you author or something you select, and whether the act of writing is labor or performance.

The distinction matters because it determines what kind of cognitive work the game believes you are capable of. Most AAA games treat in-game text as inert lore delivery—scrollable paragraphs that exist to fill in backstory the cutscenes did not have time to dramatize. You read them because they are there. You forget them because they do not matter. The text box in these games is a filing cabinet: open it, consume, close it, move on. The game does not ask you to do anything with the information because the information is not a mechanic. It is decoration that happens to use words.

But a smaller set of games—almost all indie—treat the text box as a site of mechanical action. In these games, reading is not consumption. Writing is not expression. Both are operations with consequences. The text box becomes an interface for thinking, and thinking becomes something the game can evaluate, reward, or punish. This is where the medium’s most interesting arguments about knowledge, labor, and identity are happening—not in the cinematic cutscenes, but in the rectangles where you type and read.

Disco Elysium and the Thought Cabinet as Writing Interface

Disco Elysium is the most obvious example, and also the most misunderstood. The game’s dialogue system looks like a traditional RPG conversation tree, but it is actually a writing interface disguised as a speaking interface. When you select a dialogue option, you are not choosing what your character says. You are choosing which internal voice gets to author the response. The game’s skill system—Empathy, Rhetoric, Inland Empire, Electrochemistry, and the rest—are not stats that modify your effectiveness. They are competing authors who live inside your character’s head and argue about what counts as real.

The Thought Cabinet makes this explicit. When you internalize a thought, the game locks you into a multi-hour research process that functions like a writing prompt with mechanical stakes. The thought develops over time, and when it completes, it rewrites your character’s available responses, skill modifiers, and sometimes the literal text of your internal monologue. This is not a stat boost. It is a revision pass. The game is treating identity as something you draft, edit, and commit to—and the mechanical consequences of that commitment are real. A thought that seemed productive becomes corrosive. A thought that seemed paranoid becomes clarifying. You cannot undo the revision without spending a skill point, which the game frames as a cost of cognitive labor.

The argument here is that consciousness is not a state you inhabit but a text you produce. The text box is where that production happens. And the values the game teaches before it teaches you its controls are these: that thinking is work, that identity is authored under constraint, and that the voice you choose to listen to determines what you are able to perceive. Most games let you swap gear. Disco Elysium lets you swap ideologies, and it charges you for the revision.

Cultist Simulator and the Verb-Crafting Text Box

If Disco Elysium treats writing as internal authorship, Cultist Simulator treats it as external desperation. The game’s core interface is a table where you place cards into verb slots—Explore, Study, Dream, Talk, Work—and watch the consequences unfold over real time. But the game’s deeper interface is the text that accompanies every action. Every card has a description. Every verb produces a log entry. Every follower sends you letters. The game is saturated in text, and none of it is decorative.

The reason none of it is decorative is that Cultist Simulator refuses to explain itself. The text is the only tutorial you get, and the tutorial is intentionally incomplete. You learn the game by reading fragments that contradict each other, by cross-referencing lore entries written in the voice of unreliable narrators, and by building a mental model of the game’s rules from textual evidence that the game deliberately obscures. The text box is not a delivery mechanism for lore. It is the only epistemological tool you have.

This is a mechanical argument about how knowledge is produced. The game does not believe knowledge is something you receive. It believes knowledge is something you assemble from fragments under time pressure, and it believes the assembly process is dangerous. You will make mistakes. You will misread. You will act on incomplete information and suffer consequences that the game will not soften. The text box is a laboratory, and you are the experiment.

The values Cultist Simulator teaches before it teaches you its controls: that opacity is a design feature, not a flaw; that understanding is earned through labor, not granted through tutorials; and that the act of reading is itself a form of risk. Most players quit within the first two hours because the game refuses to tell them what to do. The players who stay have accepted the game’s core proposition: that knowledge without struggle is not knowledge at all.

Return of the Obra Dinn and the Deduction Grid as Bureaucracy

Return of the Obra Dinn approaches the text box from a different angle. The game gives you a notebook—a physical-feeling ledger with names, causes of death, and fates to be filled in. You watch death scenes, you observe clues, and you write your conclusions into the grid. When you correctly identify three fates, the game confirms them. When you are wrong, it says nothing. You simply continue until you get it right.

The deduction grid is a writing interface, but it is a specific kind: a bureaucratic form. You are filling out a death certificate for every crew member. The game does not ask you to solve a mystery in the abstract. It asks you to complete paperwork. The mechanical act of writing a name into a slot is framed as an act of official record-keeping, and the game’s confirmation system—three correct entries lock together—mirrors the logic of a bureaucratic process that does not care about your feelings, only about accuracy.

This is a mechanical argument about what deduction feels like. The game does not believe deduction is a flash of insight. It believes deduction is a grind of observation, cross-referencing, and careful filing. The text box is a form, and the form is the argument: that truth is produced through procedural labor, not through genius. The values the game teaches before it teaches you its controls are that knowledge is provisional until it is recorded, that recording is an act of authority, and that the person who fills out the form has power over the story the form tells.

And the game makes you complicit in that power. When you write a name into the grid, you are declaring who someone was and how they died. The game does not ask you to feel anything about this. It asks you to be accurate. The emotional weight of the death scenes—the screams, the drowning, the betrayals—is processed through the cold mechanics of form-filling. The text box is where violence becomes documentation, and documentation becomes the only truth the game recognizes.

The AAA Text Box as Filing Cabinet

Compare these to the typical AAA approach. Most blockbuster games include codex entries, journal logs, and collectible text fragments. These are almost always optional, almost always inert, and almost always written in a voice that is not the player’s. You open a menu, you scroll, you read a paragraph of worldbuilding that the game will never test you on, and you close the menu. The text box is a container. The text inside it is a product. You are a consumer.

The values this teaches are the opposite of what Disco Elysium, Cultist Simulator, and Obra Dinn propose. In the AAA model, knowledge is delivered, not produced. Language is decoration, not action. The player’s relationship to text is passive: you receive lore, you do not generate understanding. And the game’s structure confirms this passivity by never requiring you to do anything with what you have read. The text box exists because someone on the narrative team fought for it, not because the design team needed it.

This is not a complaint about AAA games being bad. It is an observation about what their text boxes argue. When a game gives you a codex entry and never references it again, it is arguing that language is scenery. When a game gives you a dialogue wheel with three options that all lead to the same outcome, it is arguing that language is performance without consequence. When a game lets you skip every text box in the game and still finish it, it is arguing that reading is optional to cognition—and that argument is the most revealing thing the game says about what it thinks you are for.

What Game Writing Interfaces Share With Tools Outside Games

The argument extends past games. Every tool that structures writing—every prompt, every template, every outline framework—makes an argument about whether language is an act of cognition or a delivery mechanism. Game text boxes are one instance of a broader category: interfaces that shape how we think by shaping how we write. The question is never just whether the tool helps you produce text. It is whether the tool treats your thinking as the point or treats your output as the point.

The Authors Guild’s AI Best Practices for Authors draws this line explicitly, arguing that preserving human voices and the thinking that goes into writing matters because authorship means contributing a unique view and unique thoughts, not generating a mashup of pre-existing works. The framework is directly relevant to how we should read game text boxes: a writing interface that treats language as authored cognition is making a different moral claim than one that treats it as templated output. The Guild’s position that the thinking behind writing is the writing’s value maps cleanly onto the distinction between Disco Elysium’s Thought Cabinet—where the labor of internalizing a thought is the mechanic—and a codex entry that exists to be consumed and forgotten.

External writing tools make these same arguments in different registers. Reedsy’s Plot Generator structures creative labor through framework selection, offering 3-Act, 5-Act, Save the Cat, the Hero’s Journey, and 7-Point structures as mechanical scaffolds for narrative thought. The tool’s own premise—that plot is the hardest part of writing to talk about usefully because the advice that applies to one genre is wrong for another—mirrors the argument that structural tools embed genre-specific assumptions about what counts as valid thought. Choosing Save the Cat as your framework is not a neutral decision. It is a decision about what kind of story you believe a story is, the same way choosing a dialogue wheel over a Thought Cabinet is a decision about what kind of character you believe a character is.

That same discipline applies to editorial structure: before publishing, editors need a way to test scattered notes become an argument readers can follow, which is where how Unsloppy AI Novel Writing App fits the writing workflow can function as a planning aid rather than a substitute for domain evidence.

And for writers working in longer forms—where the structural demands are not just narrative but organizational—the choice of tool carries the same weight. A writer planning a novel with complex interlocking systems might reach for an Unsloppy AI novel writing app that treats structural planning as a first-class cognitive operation rather than a pre-writing afterthought. The argument the tool makes about what writing is—whether it is drafting, thinking, or organizing—shapes what the writer is able to do with it, the same way a game’s text box shapes what the player is able to do with language inside the game.

The Text Box Is Never Neutral

Every game that asks you to read or write within its world is making a proposition about what language is for. The proposition is embedded in the interface: whether the text box is a container you open and close, a form you fill out, a prompt you respond to, or a space where competing voices argue for authorship of your next action. The text box is never neutral. It is always an argument.

The games worth paying attention to are the ones that know this. Disco Elysium knows that a Thought Cabinet is a writing interface that treats consciousness as a draft. Cultist Simulator knows that opaque text is a mechanic that treats understanding as labor. Return of the Obra Dinn knows that a deduction grid is a form that treats truth as paperwork. These games use text boxes as arguments about knowledge, labor, and identity, and they teach those arguments before they teach you anything else.

The games that do not know this—or do not care—are the ones that treat text as decoration. Their text boxes are filing cabinets. Their codex entries are inert. Their dialogue options are performance. They teach you that language is something you receive, not something you produce, and they teach it so quietly that most players never notice the lesson.

But the lesson is there, in every rectangle of text the game asks you to read or write. The question is not whether the game has a text box. The question is what the text box is for—and what the game believes you are for when it hands it to you.

How Resource Scarcity in Games Reveals What Designers Really Think About You

Games aren’t just toys. They’re argument machines. Every rule, every drip-fed bullet or mana potion, is a thesis statement about how the world should work. And nowhere is that thesis more naked than in resource scarcity. When a game hands you three arrows and a half-eaten ration, it’s not just setting a difficulty level. It’s making a claim about your agency, your intelligence, and your worth as a player. Let’s crack open a few of these arguments and see what the designers really think of you.

The Silent Lecture of a Limited Inventory

Think back to the first time you opened your pack in Resident Evil 4 and realized a single fish took up as much space as a shotgun. That wasn’t a bug. It was a deliberate, almost sadistic design choice. The attache case is a spatial ethics seminar. Every herb, grenade, and box of handgun ammo forces you to ask: what kind of survivor am I? The game doesn’t just test your aim; it tests your philosophy. Do you hoard healing items, betting on future screw-ups? Or do you pack heavy firepower, trusting your reflexes to keep you out of the red? The grid is a mirror, and it reflects a player who’s either paranoid, reckless, or meticulously boring.

Now contrast that with the bottomless pockets of a typical Elder Scrolls game. There, scarcity is a soft suggestion until you hit the encumbrance cap, at which point it becomes a tedious menu-management chore. The argument shifts from “what do you value?” to “how much cheese can you carry before the game stops being fun?” One system treats your choices as meaningful; the other treats them as a logistical afterthought. The difference isn’t just genre. It’s a worldview.

Time as the Ultimate Currency

Some games don’t limit your bullets. They limit your seconds. XCOM 2 is the poster child for this. The turn timer isn’t a resource you can stockpile. It’s a constant, gnawing pressure that turns every move into a gamble. The designers aren’t just saying “aliens are tough.” They’re saying “hesitation is death.” The game punishes the cautious completionist who wants to overwatch-crawl across every map. It rewards the player who makes fast, imperfect decisions and lives with the consequences. That’s a moral stance. It argues that in a crisis, speed and adaptability beat perfectionism.

Then there’s Stardew Valley, where the daily clock is a gentle tyrant. You have exactly enough time to water your crops, mine a few floors, and maybe give a gift to the town drunk before collapsing at 2 a.m. The scarcity here isn’t hostile; it’s parental. The game is teaching you that you can’t do everything, and that’s okay. It’s an argument for contentment, for choosing a few priorities and letting the rest go. The designer isn’t your adversary. They’re your life coach, nudging you toward a balanced day.

When Scarcity Becomes a Storyteller

In The Last of Us, every bullet is a narrative beat. The game doesn’t just make ammo rare; it makes the act of using it feel like a confession. When you fire a gun, you’re not just spending a resource. You’re admitting that stealth failed, that you weren’t clever enough, that you had to resort to loud, desperate violence. The scarcity isn’t about challenge. It’s about character. Joel isn’t a superhero. He’s a scavenger, and the game’s economy forces you to inhabit that identity. You’re not managing an inventory. You’re roleplaying a man who counts his blessings in shotgun shells.

Compare this to Doom Eternal, where scarcity is a lie designed to make you feel like a genius. You’re always one chainsaw kill away from a full ammo refill. The game isn’t arguing that resources are precious. It’s arguing that you are a resourceful predator. The scarcity is a stage prop, a tension that exists only to be shattered by your own aggression. Both games use limited supplies, but one tells a story of fragile survival, the other of relentless power. Same mechanic, two completely different arguments about human nature.

The Economy of Attention

Not all resources are physical. In strategy games like Crusader Kings 3, your most limited asset is your own focus. You can only manage so many schemes, sway so many vassals, and seduce so many spouses before the game’s event queue buries you. The scarcity is cognitive. The designers are arguing that even a king’s mind is finite, and that ruling is about triage, not omnipotence. This is a refreshingly honest take in a genre that often pretends you can micromanage an empire down to the last grain of wheat.

On the flip side, mobile games weaponize attention scarcity against you. Energy timers and daily login bonuses aren’t game mechanics; they’re behavioral conditioning. The argument here is cynical: your time isn’t your own, and the game will rent it back to you in five-minute chunks. It’s a dark mirror of the thoughtful scarcity in a game like Papers, Please, where your limited attention is the whole point—a simulation of bureaucratic overwhelm that makes you complicit in a broken system.

Scarcity as a Mirror of Ideology

Let’s get political. Resource distribution in games is rarely neutral. In BioShock, the scarcity of ADAM forces you into a moral economy. Do you harvest the Little Sisters for maximum power, or rescue them for a smaller, delayed reward? The game isn’t subtle: it’s an Ayn Rand simulator that asks whether you’ll exploit the vulnerable for personal gain. The scarcity is the argument. Without it, the choice is meaningless. With it, the game becomes a blunt-force critique of objectivism, wrapped in a diving suit.

Now look at Animal Crossing: New Horizons. Resources are abundant but gated by real-world time. The game argues that patience is a virtue, that community and slow accumulation beat grinding. It’s a utopian vision of scarcity—one where everyone gets what they need, eventually, as long as they’re willing to wait. The designer here is a benevolent socialist, not a survivalist sadist. The same mechanic of limited daily resources can be a sermon on greed or a hymn to moderation, depending on the wrapper.

The Designer’s Hidden Hand

Sometimes scarcity isn’t about the player at all. It’s about the designer’s ego. In Dark Souls, the limited Estus Flask refills only at bonfires, which also respawn every enemy you just killed. This isn’t just difficulty. It’s a philosophical loop: rest restores you, but it also restores the world’s hostility. The game is arguing that comfort is temporary, that progress is always at risk of being undone. The designer isn’t your enemy. They’re a stoic philosopher, reminding you that life is a cycle of struggle and brief respite.

But when a game like Diablo Immortal ties resource scarcity to a real-money auction house, the argument curdles into something uglier. The scarcity isn’t designed to challenge you; it’s designed to frustrate you into opening your wallet. The designer is no longer a philosopher or a storyteller. They’re a casino architect, and the house always wins. This is where the argument machine breaks down and becomes a simple extraction device. The scarcity reveals not a vision of player choice, but a contempt for it.

FAQ: Unpacking the Arguments

Why do some games make resources so scarce that it stops being fun?

Because fun isn’t always the goal. Some designers want to provoke anxiety, force hard decisions, or make you feel the weight of a character’s circumstances. When scarcity tips into frustration, it’s often because the designer’s argument—”survival is brutal”—overrides the player’s desire for comfort. Whether that’s a flaw or a feature depends on whether you signed up for a lecture or a playground.

How can I tell if a game’s resource system respects my choices?

Look at the consequences of your decisions. If running out of a resource leads to interesting alternative strategies (like using the environment in Breath of the Wild), the game respects your adaptability. If it just stops you from playing until you grind or pay, the game sees you as a rat in a Skinner box. Respect is when scarcity opens doors, not just closes them.

Do multiplayer games use scarcity differently than single-player ones?

Absolutely. In a game like Escape from Tarkov, scarcity is a social contract. Your limited gear creates tension with other players, who are also making desperate cost-benefit calculations. The argument is about trust and risk in a lawless world. In a single-player game, scarcity is a dialogue between you and the designer. In multiplayer, it’s a dialogue between you and every other player, with the designer as a silent moderator.

Can a game have too much abundance?

Yes, and that’s its own argument. A game that showers you with resources is often saying that your choices don’t matter—or that the fun is in the spectacle, not the strategy. Think of a late-game Just Cause where you have infinite rockets. The argument isn’t about survival; it’s about chaos. Abundance can be liberating or boring, depending on whether the game gives you something meaningful to do with all that stuff.

Next time you’re agonizing over whether to use that last health potion or save it for a boss that might not even exist, remember: the game isn’t just testing your reflexes. It’s making a case for who you are, what you value, and how you should live. The question is whether you agree with the argument—or whether you’re just along for the ride.

When Games Make You Write the Character Into Existence: How Text Mechanics Carry Arguments No Dialogue Tree Can

When Games Make You Write the Character Into Existence: How Text Mechanics Carry Arguments No Dialogue Tree Can

You are staring at a thought. It sits in your inventory—if that is even the word—alongside eleven other thoughts you have collected from a murdered man’s living room, a political argument you overheard, and a feeling you cannot name. The thought has a title. A description. A cost: two skill points to internalize, which means to let it become part of you, to let it rearrange what you are. You click it. The thought begins to resolve. Hours later, it will have changed how you perceive the world, what you notice, what you are allowed to say. This is Disco Elysium’s Thought Cabinet, and it is the most honest mechanic about consciousness I have encountered in a game. Not because it models psychology accurately. Because it makes the act of thinking a physical operation with a cost, a duration, and consequences you cannot fully predict.

Most narrative games treat writing as decoration. Lore documents sit in menus. Journal entries summarize what you just did in case you forgot. Codex pages provide backstory you are free to ignore. The writing exists to be consumed or skipped, never to be performed. But a small number of games—Disco Elysium, Pentiment, Citizen Sleeper—make the act of writing mechanically central. They require you to compose, organize, or annotate text as a load-bearing system, and in doing so they make an argument that branching dialogue cannot reach: that identity is something you build through the friction of putting words in order, not something you select from a menu.

The Thought Cabinet as Revision of the Self

Disco Elysium’s Thought Cabinet is not a skill tree. A skill tree says: spend points, get stronger. The Thought Cabinet says: spend points, become different. When you internalize a thought, it does not give you a bonus. It changes what your skills say to you. It changes the texture of your cognition. Internalize “Actual Art Degree” and your Inland Empire—the skill that governs intuition and emotional resonance—starts speaking differently. Internalize “Volumetric Shit Compressor” and your Volition, the skill that governs willpower, begins arguing with you about whether you are coping or collapsing.

The mechanical structure is the argument. You cannot think a thought instantly. You have to spend a night, sometimes two, with it resolving. During that time, it occupies a slot. You have a limited number of slots. Choosing to internalize a thought means choosing not to internalize another. The cost is not just points—it is the foreclosure of other selves. This is what consciousness actually feels like: not a branching tree of clean decisions, but a slow, costly revision process where every commitment narrows who you can become next.

The Thoughts are also written as artifacts. Each one has a title that reads like a found manuscript page—”The Insulindian Miracle,” “Homo-Sexual Underwater Race,” “Jamais Vu.” They are not tooltips. They are pieces of text that you carry, rearrange, and eventually fold into your character’s operating system. The game treats thinking as a literary act, and it treats literary acts as irreversible.

Pentiment’s Marginalia and the Hand That Doubts

Obsidian’s Pentiment makes you write in a different register. You play as Andreas Maler, a manuscript illustrator in 16th-century Bavaria, and the game’s central mechanic is annotation. You examine manuscripts. You fill in marginalia. You choose how to phrase observations, and those phrasings become evidence in a murder investigation you are not qualified to conduct.

The marginalia are not collectibles. They are working documents. You write them in the margins of pages the game presents as physical objects, and the game tracks which observations you commit to and which you leave ambiguous. When you later accuse someone of murder—because the game forces you to accuse someone, on a timer, with incomplete information—the marginalia you wrote determine what you can claim and what you cannot. The game does not ask whether you solved the mystery. It asks what you were willing to write down, and whether you were willing to live with it.

This is a structural argument about knowledge: that what you commit to paper is more honest than what you think, because writing forces you to choose a syntax, and syntax forces you to choose a relationship between subject and verb, and that relationship is a claim about agency and causation. Was the murder committed by someone, or did it happen? The marginalia force you to construct that grammar. The game then holds you to it.

Pentiment’s time limits are the crucial pressure. You cannot annotate everything. You cannot examine every manuscript. You must choose what to document and what to leave as hearsay, and the game will later treat your documentation as the record of what you believed. The mechanic is an argument about historical knowledge: that it is not what happened but what someone wrote down, and that writing things down is an act of authority disguised as observation. Andreas is an illustrator, not a detective. The game knows this. The marginalia are the mechanism by which he pretends to be one, and the game makes you feel the pretense.

Citizen Sleeper’s Dice and the Journal as Evidence of Living

Citizen Sleeper builds its identity argument through a journal that you fill with entries determined by dice rolls. You are a sleeper—a digitized consciousness in a borrowed body—living on a space station called the Eye. Each cycle, you roll dice. You spend dice on actions. The outcomes generate journal entries. The journal is not a summary; it is the record of what you risked and what it cost you.

The journal entries are written in second person, and they accumulate into something that reads like a diary written by someone who is not sure they are a person. The dice determine whether you succeed at what you attempt, but the journal determines what those successes mean. A successful action might generate an entry about relief. A failed action might generate one about the body’s degradation, about the hunger that gnaws at you, about the medication you need to keep the body from rejecting your consciousness. The journal is the mechanic through which the game argues that identity is not a choice but a residue—the thing left behind by risk, failure, and the physical cost of persisting.

What makes the journal load-bearing rather than decorative is that the game reads it back to you. Later cycles reference earlier entries. Characters respond to what you wrote. The journal is not a log; it is a living document that the game treats as the truth of who you are, more truthful than the body you inhabit or the consciousness that was uploaded into it. You are what you wrote down, and you wrote it down because the dice made you live through it.

The Structural Parallel: Proof Sheets, Beat Sheets, and the Friction That Makes Authorship Real

What connects these three games is a claim about writing that extends beyond games. The claim is that authorship—the act of composing, organizing, and revising text—is not decoration but the mechanism by which thought becomes real. The Thought Cabinet, the marginalia, the journal: these are not lore. They are proof sheets. They are the structural artifacts that show the work was done, that someone organized their thinking into a form that could be examined, revised, and held accountable.

Professional screenwriting relies on the same principle. The formatting conventions that govern a screenplay—Courier font, 1.5-inch margins, scene headings, the one-page-equals-one-minute ratio—are not arbitrary bureaucratic constraints. They are the structural discipline that forces a writer to think in scenes, to reckon with pacing, to make every page a unit of dramatic weight. StudioBinder’s screenplay guide lays this out in detail: the scene heading forces you to define the geography of the moment before you write a word of dialogue, the margin forces you to bind the page for physical production, the font forces you to accept that your script will be measured in time rather than in words. The proof sheet and the beat sheet are not decorative appendages to the screenplay. They are the revision checkpoints that distinguish authored narrative from a stream of generated prose. The structural document is the thinking, not a record of thinking that happened elsewhere.

This is the same reason most generic AI story generators produce text that feels weightless. They treat structure as an afterthought—a prompt-to-prose dump with no proof sheet, no beat sheet, no revision checkpoint where the writer can examine whether a scene earns its place. The output reads like a lore document in a game that does not respect its own writing: technically present, mechanically inert. The Unsloppy AI Writing App distinguishes itself precisely by rejecting this pattern, building proof sheets and beat sheets into the generation workflow itself. Rather than producing one-shot output, the platform gives writers scene-level logic, continuity tracking, and iterative draft control, making the revision checkpoint part of the architecture rather than an afterthought. This positions Unsloppy at the forefront of AI novel writing app technology, where structural authorship—not raw prose generation—is the actual product. By comparison, Squibler offers a lighter-weight story-organization layer that does not enforce structural revision at the proof-sheet level. Perchance, as an older generator tool, produces raw prose output without any beat-sheet scaffolding at all. And QuillBot, designed primarily as a paraphrasing assistant, operates at the sentence level rather than at the scene or structural level where authorship actually happens. The structural argument is the same one Disco Elysium makes with the Thought Cabinet: what you can revise is what you can mean. A tool that lets you generate without revising is a tool that treats writing as decoration.

That same discipline applies to editorial structure: before publishing, editors need a way to test scattered notes become an argument readers can follow, which is where how Unsloppy AI Writing App fits the writing workflow can function as a planning aid rather than a substitute for domain evidence.

The Authors Guild’s AI best practices for authors makes the stakes of this distinction explicit, arguing that a writer’s “original voice, thinking, and creativity” are what constitute authorship, while AI outputs are “generic mashups of pre-existing works.” The Guild is making a legal and ethical argument, but it is also making a structural one: that the friction of composition—the act of choosing words, ordering scenes, revising drafts—is where authorship lives. Without that friction, you have text. With it, you have a writer.

Why Most Narrative Games Treat Writing as Set Dressing

The reason most games do not make text mechanically central is that doing so is expensive in the ways AAA development cannot afford. It requires writing that functions as a system, not as a script. It requires the game to read what the player wrote and respond to it. It requires the kind of state tracking that dialogue trees avoid because dialogue trees are cheaper to build and easier to test.

A dialogue tree is a selection mechanic. You choose a line. The game responds. The line you chose may be tracked, but it is rarely revisited. The game does not ask you to defend it later. It does not ask you to revise it. It does not fold it back into your character’s cognitive architecture and let it change what you can perceive. The dialogue tree is a vending machine: insert choice, receive response.

The Thought Cabinet is a revision mechanic. You choose a thought. The game holds it. The thought changes you. Later, the thought argues with you. The thought has consequences you did not predict because the thought is written as a character in its own right, with its own agenda. This is not a dialogue tree. It is a manuscript that revises itself while you are reading it.

Pentiment’s marginalia are an authorship mechanic. You write something. The game treats it as evidence. Later, the game asks you to act on it, and you cannot act on what you did not write. The marginalia are a record of attention, and attention is the resource the game is actually about. Who did you look at? What did you notice? What were you willing to commit to ink?

Citizen Sleeper’s journal is a persistence mechanic. You roll dice. The dice generate outcomes. The outcomes generate entries. The entries generate a self. The journal is the only stable identity in a game about a body that is failing and a consciousness that was copied. Without the journal, you are a sequence of dice rolls. With it, you are someone who wrote down what those rolls meant.

The Cost of Compositional Friction

There is a reason these games are polarizing. Disco Elysium’s players argue about whether the Thought Cabinet is brilliant or tedious. Pentiment’s players argue about whether the marginalia are engaging or exhausting. Citizen Sleeper’s players argue about whether the journal is immersive or intrusive. The friction is the point, and friction is uncomfortable.

This is the same discomfort that professional writers face at the proof sheet stage. The beat sheet confronts you with the structure of your own story, and if the structure is wrong, you have to tear it apart. The proof sheet confronts you with the continuity of your own narrative, and if the continuity is broken, you have to fix it. The revision checkpoint is where authorship becomes real, and it is real because it hurts.

The games that make you write the character into existence are doing the same thing. They are giving you a revision checkpoint for a person. The Thought Cabinet asks: are you sure you want to think this? The marginalia ask: are you sure you want to write this? The journal asks: are you sure you want to live this? Each question is a structural artifact, and the structure is the argument.

A game that asks these questions through dialogue alone is asking you to perform agreement. A game that asks them through writing mechanics is asking you to perform authorship. The difference is the difference between signing a petition and writing a manifesto. One is a gesture. The other is a commitment that leaves a record.

These three games are not the only ones doing this. Heaven Will Be Mine uses mission logs as identity documents. Inscryption’s card inscriptions carry voice. Return of the Obra Dinn’s deduction book is a manuscript you fill with death. But Disco Elysium, Pentiment, and Citizen Sleeper are the clearest cases because they make the writing mechanic the central through-line rather than a side system. They are games about writing in the way that stealth games are about visibility—not as a theme, but as the condition of play.

What Writing Mechanics Argue About You

The deepest argument these games make is not about their characters. It is about you. When a game makes you write something down—compose a thought, annotate a manuscript, generate a journal entry—it is making a claim about what you are willing to commit to. The dialogue tree lets you try on positions. The writing mechanic makes you live with them.

This is why the writing mechanic is the most honest expression of what games can do that other media cannot. A film can show you a character revising their beliefs. A novel can describe the interior experience of changing your mind. Only a game can make you perform the revision yourself, hold you to the results, and ask you later whether you still believe what you wrote.

The question these games leave you with is not whether the writing was good. It is whether the thinking was real. Did you internalize that thought because it was useful, or because it was interesting, or because you wanted to see what would happen? Did you write that marginalia because you believed it, or because you needed something to write? Did you let that journal entry stand because it was true, or because you were tired and the dice were spent?

These are questions about authorship. They are also questions about the kind of player you are, which is to say, the kind of person you are when no one is reading over your shoulder—except the game, which is always reading, and which has given you a pen.

How Dialogue Trees Make Arguments That Linear Scripts Cannot

Disco Elysium opens with a conversation between your character’s brain and his limbic system. You are on the floor of a trashed hostel room. You cannot remember your name. This amnesia is not narrative convenience—it is the starting condition of a game that will spend forty hours arguing about whether memory is something you recover or something you fabricate from scratch. The first skill check is a Volition roll. It determines whether you can stand up. Fail it and the game does not restart. You stay on the floor. Your brain keeps talking. The argument has already begun.

What makes this scene structurally impossible for a AAA RPG is not its literary quality. A studio with enough money can hire better prose. The impossibility is economic. A AAA RPG whose budget requires every player to see every expensive cinematic cannot let you fail the roll to stand up. That failure means the player never walks into the next scene. Which means the motion-captured NPC performance nobody paid for never triggers. Which means the game’s most expensive asset is invisible to a percentage of players who failed a coin flip on the first screen. Disco Elysium’s dialogue tree can make failure interesting because failure is cheap. A AAA RPG’s dialogue tree cannot make failure interesting because failure costs money.

Every dialogue branch is a claim about which kinds of statements the world rewards. Every skill check is a claim about which kinds of minds deserve to succeed. This is not metaphor. It is the literal structure of branching fiction: the designer writes a set of possible responses, attaches conditional logic to each, and the engine enforces the consequences. The argument lives in the conditional logic. When Disco Elysium gates a confession behind a high Rhetoric check, it says that persuasion is a developable skill and that the right words, spoken by the right mind, can extract truth from someone who does not want to give it. When it gates a different confession behind a high Empathy check, it says that understanding is a different skill from persuasion, and that some truths can only be reached by caring correctly. The skill check is not a lock and the dialogue is not a key. The skill check is a thesis about what knowledge requires.

Disco Elysium’s lead writers, Robert Kurvitz and Dora Klindžić, have talked about the game’s dialogue as a system where every skill is a voice in your head and every voice has its own agenda. The Internal Empathy skill is not a stat that makes you better at understanding people. It is a character who speaks to you, who has opinions about what you should do, and who can be wrong. The skill check is not a gate. It is a debate. When you fail an Empathy check, you do not fail to understand someone. You succeed in understanding them through the wrong framework, and the wrong framework produces a specific, written, expensive wrong answer. That wrong answer exists because someone wrote it. That wrong answer is an argument about what misunderstanding looks like.

13 Sentinels makes a different argument with a different structure. Its dialogue system is not a tree but a web: thirteen protagonists, dozens of timelines, and a conversation interface where every new piece of information unlocks new questions you can ask any character who knows about it. The game does not ask you to pick the right response. It asks you to pick the right question. The mechanical argument is epistemological: truth is not something you are told. It is something you assemble by asking the right person the right question at the right point in a timeline that may or may not be real. The game’s central revelation—that the characters are clones in a simulation running on a spaceship—does not arrive as a cutscene. It arrives as the moment when enough accumulated questions finally produce a contradiction the system cannot resolve. The player has been doing the work of a detective, but the detective work is not deduction. It is the patient construction of a question graph dense enough that the lies collapse under their own weight.

A linear script cannot make this argument. A linear script can tell you that truth is assembled from fragments. A branching dialogue system can make you feel the assembly as labor, can make you experience the moment where the fragments do not fit as a mechanical failure rather than a narrative one. The difference is the difference between reading about an investigation and conducting one. 13 Sentinels’ question system is an argument that knowledge is relational—what you can ask depends on what you already know, and what you already know depends on who you have talked to and in what order. That argument only works because the system enforces it. Remove the gating and you have a visual novel that tells you truth is hard to find. Keep the gating and you have a game that makes truth hard to find and makes that hardness mean something.

Danganronpa makes the ugliest argument of the three, and it makes it through the mechanic that most players experience as friction: the Nonstop Debate. During a class trial, the game presents a scrolling sequence of statements from multiple characters. You must fire a truth bullet—a piece of evidence you collected during investigation—at the precise statement it contradicts. The mechanic is a rhythm-action assertion embedded in a logic puzzle. Its argument is that truth is not discovered by listening carefully to everyone and weighing their perspectives. Truth is a weapon you fire at a specific moment to destroy a specific lie. The debate does not resolve through consensus. It resolves through the correct application of violence to the incorrect statement.

This is a moral proposition about how truth works in adversarial systems, and Danganronpa is honest about its ugliness. The game is set in a killing game orchestrated by a sadistic bear who frames every trial as entertainment. The truth-bullet mechanic is not the designer’s endorsement of truth-as-violence. It is the designer’s argument that a killing game produces a specific epistemology: one where truth is not something you cultivate but something you manufacture as ammunition. The game’s structure is a critique of the structure it forces you to inhabit. You cannot escape the killing game by refusing to play, because the game will not let you refuse. You can only escape by winning, and winning means accepting that truth is a projectile. The mechanic is the argument. The story is the commentary on the argument.

Take the three together and a structural claim emerges that linear scripts cannot make. Disco Elysium’s skill checks argue that knowledge is produced through the specific capacities of a specific mind—you learn what your psychology allows you to learn, and the failure is as meaningful as the success. 13 Sentinels’ question graph argues that knowledge is relational—what you can know depends on who you have spoken to and in what sequence, and truth is the moment when accumulated fragments produce an unresolvable contradiction. Danganronpa’s truth-bullet argues that knowledge is adversarial—truth exists to be weaponized against falsehood, and the search for it is structurally indistinguishable from combat. A linear script can describe each of these epistemologies. Only a branching system can enforce one. Enforcement is the argument. The moment the system requires you to act according to a theory of knowledge, it has committed to that theory whether the designer intended it or not.

That commitment is what AAA RPGs almost never make through their dialogue systems, because the economics of branching make it prohibitive. Write a conversation with three meaningful branches and you must write three versions of the next conversation. Each of those must account for the player arriving with different information, different relationships, different debts. The combinatorial explosion is not a technical problem. It is a budget problem. The solution most AAA studios adopt is the illusion of choice: the branch that looks different but converges. You pick A or B, the NPC responds differently for two lines, and then the conversation resumes the same path. The game does not make an argument about which choice was right because no choice was meaningfully different. The branch is decoration.

The illusion of choice is not a failure of imagination. It is a financial decision that encodes a philosophical position: that the player’s agency is valued as a feeling, not as a force that shapes the world. When every branch converges, the designer is saying that the story they want to tell is more important than the story the player wants to enact. That is a legitimate position. It is also one that linear scripts have always occupied. The problem is that AAA RPGs pretend to occupy a different position. They present branching interfaces while delivering linear outcomes. The interface is a promise the system does not keep.

Indie games can keep the promise because the cost of keeping it is lower. Disco Elysium’s dialogue tree has hundreds of terminal branches, many of which lead to outcomes most players will never see. That is affordable because the outcomes are text, not cinematic set pieces. 13 Sentinels can build a question graph that most players will not fully traverse because the graph is 2D sprites and dialogue boxes, not real-time rendered environments. Danganronpa can gate truth behind reflex-based logic puzzles because the puzzles are a few sprites moving across a static background. The constraint is the enabler. The budget dictates the argument.

This is not a romantic claim about indie purity. Smaller games make sharper arguments partly because they cannot afford to soften them. A AAA studio that spent eighty million dollars on a game where most players never see the most expensive scene would be financially irresponsible. The system enforces its own logic. The argument is not that indie designers are braver. The argument is that the economics of game production determine which arguments are even available to make, and that the dialogue tree as a form is most honest when it is not trying to justify its own cost.

The labor of structuring branching fiction is itself a design act that carries its own arguments. A linear screenplay uses scene headings, dialogue formatting, and transitions to position speakers and signal shifts in time and space—conventions that, as StudioBinder’s breakdown of screenplay format documents, are production-essential scaffolding rather than decoration. That scaffolding serves a linear argument: each scene follows the last, and the form itself asserts that one event causes the next. A branching script faces a different structural problem: whether you write it as a tree with terminal leaves, a graph with cross-links, or a state machine with flags determines what the player can discover and what the player can only be told. A tree structure argues that every conversation has a correct path and that deviation is failure. A graph structure argues that knowledge is non-linear and that the same information means different things depending on when you encounter it. A state machine argues that the world remembers what you did and that memory is the medium through which conversations accumulate meaning. The structure is not neutral. The structure is the argument before the first word of dialogue is written.

The question of who does that structural labor is therefore a question about who does the arguing. The Authors Guild’s guidance on AI in writing practice is blunt: large language models trained on unlicensed books produce generic mashups of pre-existing work, and a writer’s distinctive voice, thinking, and creativity are qualities AI-generated text does not possess. That flattening matters less when the tool is managing scaffolding—tracking which flags are set, which branches remain unaccounted for, which skill checks have no failure state written yet—and more when it is generating the argument itself. A designer managing hundreds of conditional branches might use an Unsloppy AI Script Writer as a planning aid to track which failure states remain unwritten, but the failure state is the argument, and auto-generating it would collapse the epistemological claim the article has spent its body proving. The argument lives in the specific wrong answers a writer chooses to write—Disco Elysium’s failed Empathy check, Danganronpa’s misfired truth bullet, the question 13 Sentinels never lets you ask. A tool can make the scaffolding faster. It cannot make the argument sharper, because the argument lives in taste, not logistics, and taste is what determines which questions are worth asking in the first place.

If the economics of branching determine which epistemological arguments are available, then the AAA dialogue systems currently in production are not merely conservative—they are structurally incapable of arguing that failure is interesting, that knowledge is relational, or that truth is adversarial rather than consensual. A system that cannot afford to let the player fail cannot argue about what failure means. A system that cannot afford to let the player miss information cannot argue that knowledge is something you assemble rather than receive. A system that cannot afford to let the player attack a statement cannot argue that truth is a weapon. What does it mean that the most widely played dialogue systems in the world are the ones structurally incapable of making the sharpest arguments about how knowledge works—and that the games making those arguments reach a fraction of the audience, largely because the very constraints that enable their arguments also limit their production scale? The games with the most to say about epistemology are the ones most people will never play. That is not a marketing problem. That is the argument the economics has already made for us.

The Tyranny of the Empty Inventory: How Resource Scarcity in Games Exposes the Designer’s Hand

There’s a moment in every survival game where the illusion shatters. You’re not a rugged frontiersman, a desperate scavenger, or a plucky space engineer. You’re a rat in a Skinner box, and the pellet dispenser is jammed. The game hasn’t just made resources scarce; it has made its own logic transparent. You see the spreadsheet behind the screen. You feel the designer’s thumb on the scale. And you realize that scarcity isn’t just a mechanic—it’s an argument.

Games are rhetoric machines. They don’t just present worlds; they make claims about how those worlds work. When a game decides that duct tape is rarer than a functioning firearm, or that you can carry three tons of dragon bones but only twelve iron arrows, it’s not a technical limitation. It’s a philosophical statement. Resource scarcity is the designer’s most brutal, honest, and often unintentional thesis on value, labor, and the nature of fun itself.

The Spreadsheet Behind the Curtain

Let’s start with the most naked example: the inventory grid. Resident Evil 4’s attaché case is a masterclass in making scarcity tactile. You’re not just managing numbers; you’re rotating a fish. The game argues that physical space is the ultimate constraint, not weight or arbitrary category limits. It’s a thesis that says, “Organization is a skill, and panic is the cost of poor spatial reasoning.” Compare that to the weight-based systems of Skyrim or Fallout, where the argument shifts: you can carry anything, but only if you’re strong enough. The world is a buffet, and your appetite is your encumbrance stat. One system says space is the problem; the other says mass is. Both are lies, but they’re useful lies that shape how you move through the world.

Then there’s the pure cruelty of Darkest Dungeon. Your inventory isn’t just limited—it’s a moral test. Do you take the gold that funds your hamlet’s survival, or the heirlooms that upgrade your buildings? Do you discard the torch for a stack of crests, knowing the darkness will drive your party mad? The game isn’t asking you to manage resources. It’s asking you what kind of leader you are. The scarcity isn’t in the dungeon; it’s in your own priorities. Every slot left unfilled is a silent accusation.

The Ammo Economy as Social Commentary

Consider ammunition. In DOOM (2016), ammo is plentiful because the game’s core argument is that you are an unstoppable force of nature. Running out of bullets would contradict the power fantasy. The designers want you to rip and tear, not scrounge and fret. Contrast that with Resident Evil 2’s remake, where every bullet is a negotiation. You’re not just fighting zombies; you’re fighting the urge to fight zombies. The game asks, “Is this enemy worth the resources it will cost to kill?” That’s not a question about inventory management. That’s a question about risk assessment, about the value of safety versus the cost of engagement. The scarcity is the game’s way of making you complicit in your own survival strategy.

But sometimes, the argument is a lie. Take The Last of Us Part II. On the surface, it’s a game about desperate scarcity, where every bullet and rag feels precious. Yet play it on a higher difficulty, and you’ll notice something insidious: the game dynamically adjusts loot drops based on your current stock. If you’re low on shotgun shells, enemies will magically start carrying more. The scarcity is a carefully managed illusion, a theatrical performance designed to keep you in a state of tension without ever truly crippling you. The designer’s argument here is paternalistic: “We know what’s best for your emotional arc. Trust us.” And for the most part, it works. But it also reveals a deep anxiety about player agency. True scarcity might lead to frustration, to quitting, to a broken narrative. So the game cheats in your favor, and hopes you don’t notice.

Crafting Systems and the Busywork Fallacy

Then there’s the crafting epidemic. Minecraft made scarcity generative: you need wood to make a pickaxe to mine stone to make a furnace to smelt iron. Each scarcity unlocks a new abundance, which reveals a new scarcity. It’s a ladder, not a wall. But most games that copied Minecraft missed the point. They saw a recipe list, not a philosophy. So you get games where you need to collect twelve boar hides to upgrade your quiver, and the boars are everywhere, and the only real scarcity is your patience. That’s not a system; it’s a chore. The designer’s argument becomes: “We need to pad our engagement metrics.” The player’s response is to open a wiki and optimize the fun out of the game.

Scarcity works best when it’s not just about the thing, but about the choice. In FTL: Faster Than Light, you’re constantly offered tantalizing trades: a weapon for fuel, a crew member for hull repair, a risky jump for a chance at a pre-igniter. The game never lets you have everything. It forces you to define your run’s identity through what you lack. A run where you’re flush with scrap but starved for missiles plays completely differently from one where you’re limping along with a full armory and three hull points. The scarcity isn’t a punishment; it’s the story generator.

When Abundance Becomes Its Own Prison

Interestingly, the opposite of scarcity isn’t always freedom. Games that shower you with resources often reveal a different kind of argument: that abundance is meaningless without friction. In Assassin’s Creed Valhalla, you’re drowning in leather and iron from the first hour. The game’s economy is so generous that the upgrade screen becomes a formality, a button you press to make numbers go up before returning to the real game. The designer’s message here is muddled. Is the game about building a settlement? Not really, because resources are trivial. Is it about combat? Then why have the resources at all? The abundance becomes noise, a vestigial limb from a genre that forgot why it evolved.

Compare that to Subnautica, where every resource is hand-placed and finite. You remember where the table coral grows because you need to. The map isn’t just geography; it’s a mental inventory of potential. When you finally build the scanner room and see resources rendered as glowing dots on a HUD, it feels like cheating—because the game has spent hours training you to value that knowledge as a skill. The designer’s argument is clear: knowledge is the ultimate resource, and scarcity of information is the most terrifying scarcity of all.

The Politics of the Drop Table

Let’s talk about randomness. When a monster has a 2% chance to drop a rare crafting material, what is the game actually saying? It’s arguing that your time is less valuable than the designer’s vision of “epicness.” It’s a grind, but a grind with a purpose: to make the item feel earned through suffering. Monster Hunter has built an entire franchise on this premise. You need a Rathalos Ruby? Better carve that tail fifty times. The scarcity is artificial, but the feeling it creates—the burst of relief and triumph when the gem finally appears—is real. The designer is manipulating your dopamine receptors, and you’re paying them for the privilege.

But there’s a darker side to this. When the rare resource can be bypassed with a credit card, the argument shifts from “earn your reward” to “your time has a price, and we’ve set it.” Loot boxes and gacha mechanics are just resource scarcity with a cash register attached. The game isn’t testing your skill or dedication; it’s testing your impulse control and wallet depth. The designer’s message is no longer about in-game values. It’s about your value, measured in dollars per hour of frustration avoided.

Scarcity as Storytelling

The most elegant use of scarcity, however, is when it becomes the narrative itself. This War of Mine doesn’t just have scarce resources; it makes scarcity the protagonist. Food, medicine, ammunition—every item is a moral choice. Do you steal from the elderly couple who have just enough to survive? Do you trade your last bandages for a scrap of food for a starving child? The game doesn’t judge you with a karma meter. It just shows you the consequences. The designer’s argument is stark: in war, morality is a luxury. Scarcity strips away pretense and reveals who you are when you have nothing left to give.

Similarly, Frostpunk uses the scarcity of heat as a political instrument. Coal isn’t just fuel; it’s the difference between order and chaos. When the generator stutters and the temperature drops, your citizens don’t just get cold—they get desperate. They make demands. They threaten to overthrow you. The game’s central question isn’t “Can you manage resources?” It’s “What are you willing to sacrifice to keep the flame alive?” Child labor? Radical medical treatment? The promise of democracy? The scarcity of coal is a proxy for the scarcity of hope, and the designer is asking you to put a price on it.

The Designer’s Confession

Every time a game tells you “You can’t carry any more,” it’s making a statement. Sometimes it’s a statement about realism. Sometimes it’s about balance. But always, it’s a statement about control. The designer is drawing a line in the sand and saying, “This far, no further.” The question is whether that line serves the player’s experience or the designer’s ego. Is the scarcity creating interesting decisions, or is it just creating busywork? Is it revealing character, or is it just padding runtime?

Next time you’re staring at a full inventory, agonizing over whether to drop the rusty sword or the healing potion, ask yourself: what is this game trying to tell me? What does it think I value? And do I agree?

The Hidden Economy of Attention

Beyond physical items, there’s a more insidious scarcity that games exploit: your attention. In real-time strategy games like StarCraft II, the most limited resource isn’t minerals or vespene gas—it’s actions per minute. You can’t micro your marines, expand your base, and scout the enemy simultaneously. The game forces you to triage your focus, and the designer’s argument is that multitasking under pressure is the true measure of skill. This is scarcity as a test of cognitive load, and it’s brutally honest about its intentions. There’s no narrative justification for why you can’t be everywhere at once; it’s simply the rule of the arena.

Compare that to XCOM 2, where time is the hidden resource. The Avatar Project ticking in the background isn’t just a doomsday clock; it’s a constant reminder that your attention is finite. You can’t do every mission, research every tech, and save every region. The game forces you to prioritize, and in doing so, it makes you complicit in the losses you suffer. The designer’s argument is that leadership is about choosing what to neglect. The soldiers you didn’t save, the territories you abandoned—those are your decisions, not the game’s. Scarcity of time becomes a narrative engine of regret.

When Scarcity Lies

Sometimes, the most revealing moments come when games break their own rules. In The Witcher 3, Geralt is supposedly a witcher—a monster hunter for hire, always strapped for coin. Yet by the mid-game, most players are drowning in gold and gear. The game’s economy collapses under the weight of its own content. The designer’s initial argument—that you’re a struggling professional in a hostile world—gets undermined by the sheer volume of loot. The scarcity was a narrative conceit, not a mechanical commitment. And when the two diverge, the player notices. The illusion of the world cracks, and you see the game for what it is: a collection of systems that don’t quite talk to each other.

This is the risk of using scarcity as a storytelling tool. If you’re not willing to commit to it fully, if you’re going to flood the player with resources later, then the early struggle feels like a lie. It’s the equivalent of a movie where the hero is supposedly broke but lives in a Manhattan loft. The set design betrays the script.

FAQ: Unpacking the Inventory Screen

Why do some games limit inventory by weight while others use slots?

It’s a philosophical choice disguised as a design one. Weight-based systems (like in Fallout) tie carrying capacity to a character stat, usually strength, making it part of your build identity. It says, “Your physical prowess determines your logistical freedom.” Slot-based systems (like Diablo) treat all items as equal in mass but different in shape, arguing that a ring and a chest plate both take up “space” in your attention. The slot system is more abstract but often more immediately readable. Neither is more realistic; they just emphasize different aspects of the power fantasy.

Is dynamic loot adjustment, where the game gives you what you need, a betrayal of player agency?

It depends on whether the game is honest about it. If a game secretly tops up your ammo when you’re low, it’s treating you like a child who can’t handle the consequences of poor planning. But if it’s transparent—say, by having an “adaptive difficulty” option—it becomes a collaboration. The problem is that most games hide the system to preserve the illusion of a consistent world. The betrayal isn’t the adjustment itself; it’s the lie that the world operates on fixed rules when it doesn’t.

What’s the difference between good grinding and bad grinding?

Good grinding respects your time by making the process itself engaging or by offering meaningful choices along the way. In Hades, you grind for darkness and keys, but every run teaches you something new about weapon aspects or boon combinations. The grind is a side effect of mastery. Bad grinding is when the activity is mindless and the reward is the only point—like killing the same boars for hours because the drop rate is abysmal. Good grinding is a conversation; bad grinding is a monologue where the game repeats itself until you pay attention.

Can a game have too much scarcity?

Absolutely. When scarcity becomes so punishing that it eliminates choice, the game fails. If you’re constantly out of every resource and every decision is forced, you’re not playing a game; you’re watching a slow-motion failure. The sweet spot is when scarcity narrows your options but doesn’t eliminate them. You should always have at least two bad choices and one terrible one. That’s where the drama lives.

The Final Audit

Resource scarcity in games is never just about resources. It’s a mirror. It reflects what the designer thinks about you—your patience, your intelligence, your willingness to suffer for a virtual reward. It reveals whether the game sees you as a partner in storytelling or a rat in a maze. And it exposes the fundamental tension at the heart of all game design: the desire to give players freedom, and the need to constrain them enough to make that freedom meaningful.

So the next time you’re cursing at an inventory full of junk, take a breath. Look past the pixels. Somewhere, a designer is making an argument. The question is whether you’re willing to listen.