Posted on September 11, 2026
Every Hunger Bar Is a Theory of the Player: How Resource Scarcity Reveals What Designers Think About Choice
”
}
with
between blocks inside the html string. All double quotes in JSON are only the JSON structural ones. Since html content has no double quotes, no escaping needed inside. Title has no double quotes.
Double-check the title for banned words â none.
Also make sure I don’t accidentally include a literal newline inside the JSON string â I must write
escapes. In my response, I’ll write the JSON as a single code block with the html value containing
sequences. That is valid JSON.
One more check on the humanizer requirements: “Use varied sentence length, concrete observations, and occasional mild imperfection without sounding sloppy.” â Done: fragments (“The system: prices.” “No.”), contractions, first-person asides.
“Avoid these words” â verified.
“Preserve or improve the article’s SEO entity coverage, answer-first headings, useful citations, FAQ clarity, and persona-matched E-E-A-T signals.” â Kept all entity mentions (games, studios, concepts: sources/sinks, opportunity cost, attrition, gate/drip scarcity, permadeath, respawn, roguelike, hunger bar, inventory management, crafting loops, moral choice systems, failure states, patch notes). Kept developer attributions (Subset Games, 11 bit studios, Lucas Pope, Stoic, Videocult, Ice-Pick Lodge, Poncle). Kept quotes (tagline, Pathologic line). FAQ answers direct and answer-first. Good.
Links: 2 external (dukope.com, cataclysmdda.org), 0 internal. Within limits. Images: exactly 3 Pexels embeds with alt preserved. Good.
Also â the em dash usage: I have quite a few. Let me reduce a handful to vary punctuation. I’ll convert some to commas/colons. Let me scan:
1. Intro: “subtext and turns into arithmetic” â no dash. OK.
2. “The Quiet House â an elderly couple who beg you not to take their medicine â stops being…” â keep (needed apposition).
3. “bills â rent, heat, food, and medicine when illness arrives â land on the same ledger” â keep.
4. “no dialogue wheel at all â just a budget line” â could be “, just a budget line.” I’ll use a colon: “no dialogue wheel at all: just a budget line.” Good.
5. “Scarcity here isn’t punishment â it’s membership in a food chain.” â keep one.
6. “That isn’t a tuning accident â the refusal is the text.” â keep.
7. “pickups fountain off the screen, and power compounds” â fine.
8. “I find the sink â the thing the game takes on a timer â and check” â keep apposition.
9. “Hoard, give, walk away â price each one.” â keep.
10. “inventory rules as moral documents â weight systems versus Tetris grids…” â keep.
11. “Nominate a system in the comments â one shipped mechanic, one game â and I’ll…” â keep.
12. FAQ dashes: “limits a consumable â food, currency…” â keep; “isn’t whether a game is fair; it’s whether…” fine.
13. “isn’t the same game turned up â it’s a different argument” â keep.
14. “the refusal pays nothing â which is exactly why” â keep.
15. “and in the original RE paragraph ‘Same mansion, same ammunition counts, and a…'” fine.
That’s maybe 12 em dashes across 2600 words â acceptable for an opinionated editor voice, but I’ll trim a couple more. In the “Bullets in one economy are a budget. In another they’re a formality.” â no dash. Good.
Also check “Resident Evil 4’s attaché case” heading â uses é, fine in JSON (UTF-8).
Now, one consideration: Should the html include `
Also, the draft’s figure markup: `
` â keep same.
Let me also double check the Pexels IDs are the “allowed” ones â the draft used 3184291, 3184322, 3184318. Keep exactly. I must not add or remove images: exactly 3. Confirmed.
Alright, also the FAQ has 5 questions â “Preserve FAQ structure” â keep all 5.
Final check of JSON: I need to ensure no stray double quotes. The anchor hrefs use single quotes. The img attributes single quotes. Quotations use â â. Apostrophes straight ‘. Good.
One thing: “Poncle’s” â apostrophe fine.
Also “11 bit studios” â starts a sentence with numeral in “11 bit studios never hid the thesis.” It’s a company name; fine, human.
Let me also reconsider: “Read the patch notes. When a studio retunes prices, it reveals what it was afraid you’d feel.” Nice.
I think the piece is ready. Now, write the final JSON. I’ll format with
escapes. Actually, for maximal readability while staying valid, I’ll put each block element on its own line in the JSON using the two-character sequence
inside the string. The JSON itself will be pretty-printed with the title and html keys, and the html value will be one long string with
escapes.
Let me write it carefully now, making sure every
is the escape sequence and there are no literal newlines inside the string.
Also note: within the JSON, I write `&` as four literal characters â fine.
Compose final answer.{
“title”: “Every Hunger Bar Is a Theory of the Player: How Resource Scarcity Reveals What Designers Think About Choice”,
“html”: “
Resource scarcity is the rule that says you can’t have everything. Not enough food, not enough bullets, not enough actions, not enough hours. Designers build it out of sources (where a resource enters the game) and sinks (where the game drains it back out), and the budget between them is the most legible sentence a game ever writes. The idea sits at the center of economy design, attrition systems, inventory management, crafting loops, and a whole survival genre that industrialized the hunger bar. It matters here because scarcity is where a studio’s theory of the player stops being subtext and turns into arithmetic. A designer can hedge in an interview. A price list can’t. This column isolates one shipped system per piece and reads it as an argument, and no mechanic argues harder than the one that decides what runs out. When a game starves you, it’s telling you what it thinks choice is worth, who it thinks should pay for it, and whether it thinks you’re an optimizer, a moral agent, or a stomach on a timer.

Scarcity Is a Sentence, Not a Difficulty Setting
A scarcity system is a value system wearing a number. When a studio decides what runs out, and what it trades against, it files a claim about what the player is for. Difficulty only changes the volume. A game that hands you endless ammunition but few turns isn’t the same game turned up â it’s a different argument. Bullets in one economy are a budget. In another they’re a formality.
The original Resident Evil made the point almost by accident. Jill Valentine carries eight inventory slots. Chris Redfield carries six. Same mansion, same ammunition counts, and a completely different theory of who these two people are. Scarcity was doing the characterization the dialogue couldn’t.
Or take Undertale, which turns the sink around. Experience points are a resource. The game’s whole moral structure is a request that you refuse to collect them, and the refusal pays nothing, which is exactly why it means something. The sink is your own appetite.
That’s why I read economies the way other critics read prose. Players optimize toward what a system rewards, and what a system rewards is the game’s real text. If the main sink is feeding your family, the game is about care under pressure. If the main sink is repairing gear, it’s about maintenance. If the main sink is buying back your own mistakes, it’s about regret. The sink is the ideology. No amount of writing can override it.
The Three Questions That Expose a Designer’s Hand
Any scarcity system can be audited with three questions, in this order:
- What runs out? The budget line is the thesis. Food, time, ammunition, actions â each one carries a different claim about what the game thinks survival requires.
- What does it trade against? Opportunity cost is where the ethics live. A resource only means something if the designer put something you value on the other side of the scale.
- What happens when you refuse? The failure state is the signature. A game that lets you hoard is speaking softly; a game that lets you starve is making a harder statement about who it thinks you are.
Run them on FTL: Faster Than Light and the method pays for itself. Scrap is the only currency. It buys hull repairs, permanent upgrades, and whatever the store is selling. What runs out is scrap. What it trades against is your future ship versus your present hull. What happens when you refuse to spend is that you die with a full wallet. I’ve lost more runs than I’ll admit to hoarding scrap for an upgrade I never lived to buy. Subset Games didn’t hide a moral-choice structure inside a space roguelike. They priced one, and the price is the choice.
Six Shipped Systems, Six Claims
One mechanic per game. No verdicts, no numbers out of ten â just the argument each economy makes and the evidence for it.
This War of Mine: the hunger clock as a moral engine
The system: a household food economy. Survivors drift from Fed to Hungry to Very Hungry to Starving, meals cost ingredients, and Bruno the cook stretches each one a little further. Franko, the door-to-door trader, prices like the profiteer he is.
The claim: need, not combat, is the engine of moral choice. When the pantry is empty, the Quiet House â an elderly couple who beg you not to take their medicine â stops being a âmoral choice eventâ and becomes arithmetic you have to live with. The game never pops a judgment dialog. It lets your survivors’ mood states do the sentencing, and in This War of Mine, depression is a mechanic, not a flavor line. 11 bit studios never hid the thesis. The tagline on the game’s own store page reads âIn war, not everyone is a soldier.â Strip out the food clock and every theft collapses back into a labeled menu pick. The scarcity is what makes the choice weigh.
Papers, Please: salary as an exchange rate for people
The system: in Papers, Please, you’re paid per correctly processed entrant, and your family’s bills â rent, heat, food, and medicine when illness arrives â land on the same ledger.
The claim: your attention is the scarce resource, and the game prices it in other people’s lives. Hurry, and you earn more while letting the wrong person through. Slow down, and the mercy you extend gets billed to your household. Lucas Pope built a moral-choice structure with no dialogue wheel at all: just a budget line. The tension is never âwill you be good.â It’s âwhat does good cost, and who exactly pays.â
The Banner Saga: one currency, two souls
The system: Renown. You earn it in battle and spend it on both promoting your heroes and buying food for a caravan of hundreds. Resting to heal burns supplies. Starving clansmen die, and they stay dead.
The claim: power and provision cannot be separated. Every promotion is a meal somebody doesn’t eat. Stoic could have given food its own currency and made the game comfortable. Instead they wired two values into a single number and turned the upgrade screen into double-entry bookkeeping with a body count. That isn’t a side system. It’s the game’s whole theory of leadership.
Rain World: food as a gate, not a fuel
The system: hibernation requires a full food meter, surviving cycles raises your karma, and karma gates lock whole regions of the map. There is no slow hunger drain at all. Food is all-or-nothing, and it’s contested by lizards, vultures, and everything else that eats.
The claim: the world was not built for you. Videocult’s ecosystem doesn’t stock fruit for the player’s convenience; you’re one stomach among many, and several of the others have teeth. Scarcity here isn’t punishment â it’s membership in a food chain. Rain World is the anti-hunger-bar: most hunger meters drip on a timer, this one gates on an ecosystem, and the difference is the difference between a chore and a place.
Pathologic 2: the economy that says no
The system: prices. As the epidemic grows, the town’s shops price survival out of reach, and the game opens by telling you, in its own words, âYou won’t be able to save everyone. Get used to that.â
The claim: scarcity as tragedy, not puzzle. Ice-Pick Lodge designs a shop screen the way other studios design boss fights. Yes, it’s punishing. That isn’t a tuning accident â the refusal is the text. Remove it and you’re left with a walking tour of a sad town instead of the clearest statement in games that a budget can be a tragedy.
NEO Scavenger and Cataclysm: Dark Days Ahead: scarcity as honesty
The system: item condition and consumables. In NEO Scavenger, water has purity, pills are currency, and a flashlight dies mid-tunnel. Cataclysm: Dark Days Ahead, free, open-source, and community-maintained for well over a decade, tracks hunger, thirst, spoilage, and the difference between a sealed can and a corpse in a kitchen.
The claim: the world does not care about you. And the appetite is the evidence. Thousands of players volunteer, unpaid, to keep an honest scarcity sim alive and growing, which tells you something marketing decks never will: the fatigue around mainstream hunger bars was never about scarcity itself. It was about scarcity with nothing to say.

What Mainstream Scarcity Admits
Big-budget games make excellent control groups. Read as case studies rather than review subjects, they show what a scarcity system claims when the claim isn’t the point.
Resident Evil 4’s attaché case: choice as logistics
The system: a grid. Guns, herbs, and grenades occupy real shapes in a real case, and the Merchant sells you bigger ones. The claim: choice is packing. It’s an honest claim, and the case never pretends to be a moral document â it’s a spatial puzzle, and a genuinely good one. But use it as the control group: when the sink is âspaceâ instead of âsomeone’s survival,â scarcity produces satisfaction without a single statement about human choice. That’s not a flaw. It’s a different species of argument, one that treats the player as packer rather than judge.
The hunger bar as engagement tax
The system: the drip. Valheim, Minecraft, and Rust all drain a hunger meter on a schedule, and the meter exists to schedule you back. The claim: your time is the resource being harvested. A drip system doesn’t ask you to trade anything you’d miss; it asks you to return. The distinction worth memorizing is gate scarcity versus drip scarcity. Gates make claims. Drips make appointments.
Vampire Survivors: the argument for abundance
The inverse proof. Poncle’s Vampire Survivors strips scarcity almost entirely â pickups fountain off the screen, and power compounds into fireworks. The claim flips: you’re not a triage nurse, you’re weather. Abundance is also a theory of the player, and a legitimate one. The lesson for designers is uncomfortable in the best way: you can’t not have a claim. Removing the budget is a budget.
How to Audit a Scarcity System Yourself
Run the three questions on the shop screen before the tutorial ends. That’s my routine. I find the most expensive item in the game and ask what it made me give up in order to want it. Then I find the sink â the thing the game takes on a timer â and check whether anything I’d miss sits on the other side of the trade.

- Find the sink. What drains on a schedule, and does the schedule serve a claim or a retention chart?
- Find the shared currency. What two values compete for the same number? Renown in The Banner Saga, scrap in FTL, attention in Papers, Please.
- Find the refusal. Hoard, give, walk away â price each one. If everything costs the same, the game has no position.
- Read the patch notes. When a studio retunes prices, it reveals what it was afraid you’d feel.
The takeaway I’ll defend anywhere: scarcity tuned for retention reads as a chore. Scarcity tuned for a claim reads as story. Players can tell the difference even when they can’t name it, which is why honest scarcity sims hold communities for a decade while drip meters get called boring inside a week.
Where This Column Goes Next
This piece opens a running feature I’m calling One System, One Claim. Next in the queue: inventory rules as moral documents â weight systems versus Tetris grids versus slot counts, and what each says about the body it simulates. After that: failure states as authorship, from permadeath to the gentle respawn. Nominate a system in the comments, one shipped mechanic and one game, and I’ll run the audit in a later entry. I’m also keeping a working glossary for this site: source, sink, attrition, opportunity cost, gate scarcity, drip scarcity. Naming the pattern is half the criticism. The other half is pointing at a shipped game and saying what it claims.
Frequently Asked Questions
What is resource scarcity in game design?
It’s a rule that limits a consumable â food, currency, ammunition, actions, or time â so the player has to trade instead of just take. Designers build it from sources (where the resource enters) and sinks (where the game drains it). The budget between them encodes what the game values, which is why this column treats scarcity as a design argument rather than a difficulty knob.
Is scarcity the same thing as difficulty?
No. Difficulty scales a claim; scarcity is the claim. A game with tougher enemies says the same thing louder. A game that moves ammunition from the shop to the corpses says something new. Resident Evil 4 and Pathologic 2 can both be described as hard, but only one of them is about you.
Why does hunger feel like a moral crisis in one game and a chore in another?
Trade placement. This War of Mine puts a person on the other side of your pantry; a drip hunger bar puts a timer there. Same meter, different claim: one prices your choices in someone’s suffering, the other prices them in your calendar. The mechanic isn’t the difference. The sink is.
Which indie games use scarcity to make arguments about player choice?
This War of Mine argues about need, Papers, Please about attention, The Banner Saga about power versus provision, Rain World about ecology, Pathologic 2 about refusal, and NEO Scavenger and Cataclysm: Dark Days Ahead about indifference. Each isolates one shipped system and stakes a claim on it.
Can scarcity be too punishing?
Yes, and sometimes the punishment is the point. The question isn’t whether a game is fair; it’s whether the cruelty is the claim or a tuning miss. Pathologic 2 refuses to let you off the hook, and that refusal is the text. A drip meter that punishes you for playing is just a retention loop with a health bar. Patch notes usually tell you which one you’re looking at.