There's a trap I kept falling into as a game developer: more content equals a better game. More weapons, more missions, more collectibles, more map area. I thought players wanted abundance. They don't.
Last year I spent three months adding a second weapon type to my survival game. A spear, distinct from the starting sword with different range and combo timings. Playtesters barely noticed. Two of them asked if the spear was in the game at all. Meanwhile, the one weapon that consistently got talked about was a rusty pipe with a swing speed slightly faster than the sword and a 4% higher crit rate against infected.
That 4% number shouldn't matter. It does anyway. Why?
The Scarcity Principle Nobody Talks About
Player psychology in games runs on a weird loop: value comes from scarcity, but engagement comes from consequence. The rusty pipe isn't rare. It's present. It sits in a specific garbage pile on day 3, and picking it up instead of the machete is a decision that stays with you because the pipe behaves differently in every encounter that follows.
More content creates dilution. When I added the spear, I wasn't adding a meaningful choice — I was adding noise. The player now had three weapons, but the third one didn't change how they thought about combat. It just sat in the inventory alongside everything else.
This is the problem with modern open-world design. Ubisoft maps bloat with 200 markers per region. The player's brain stops registering individual significance. A quest marker for a collectible carries the same weight as a quest marker for a story mission. Everything becomes... ambient.
The Decision That Haunts You
The games I remember aren't the ones with the most content. They're the ones where a specific choice opened a door I didn't know existed, or closed one I hadn't visited yet.
In Hades, I picked the Challenger's Boon for my first run — Demeter's cast, slow on enemies. It made the run harder. It also taught me that "cast" builds weren't about damage, they were about control. That single choice reshaped how I thought about every subsequent run. Was the game better or worse because I forced myself into that awkward first attempt? Definitely better.
Compare this to Elden Ring, which I love but also got lost in for 40 hours before finding a weapon that clicked. Too many options, too much freedom to optimize incorrectly, and eventually I was just... grinding. The choices didn't feel consequential because I could always respec, always go back, always try something else. Freedom without friction.
What I Build Now
After that survival game project, I changed my design philosophy. Three rules:
One meaningful branch per chapter. Not three weapons on a path — one weapon that fundamentally changes your approach. If the player can do the same thing with option B as they did with option A, the branch failed.
Scarcity of information, not items. Players should stumble into situations they don't fully understand. A locked door that hints at what's behind it. An NPC who mentions a rumor. The scarcity is in the knowledge, not the loot.
Consequence chains. Every choice connects to three future states, not just the immediate next scene. My pipe-vs-machete example worked because the pipe changed how I approached a specific enemy type, which changed how I approached resource management, which changed how I built my base. One early decision rippling outward.
The Real Insight
Content is easy. It's measurable, schedulable, deliverable. But the thing that makes players tell stories about your game five years later isn't the number of weapons you shipped. It's the moment they made a choice they couldn't take back, and it worked out — or didn't — in a way that felt personal.
The pipe in my survival game wasn't content. It was a lesson. And players remember lessons.
Top comments (0)