Why Games Ship Broken

I think back to playing Super Mario World or Zelda as a kid, and there was something about the basic fact that nothing broke. The game arrived on a cartridge, fully done. If a door didn’t open, that was the world telling you something. If a wall stopped you, that was design. There was no Day-1 patch. There was no version 1.1. What you had was what you got, forever.

Now you buy Skyrim and there’s a patch waiting at startup. Invisible heads floating where faces should be. NPCs walking through walls like they’re ghosts. A quest objective just vanishes if you complete it in the wrong order. The game doesn’t know what to do, so it just stops. Sometimes you laugh at how absurd it is. Sometimes you just sit there wondering if you paid money for an unfinished product.

The obvious answer is scope. Games got too big. Too many systems layered on top of each other. Fix one thing and break three others. Plus the business side: publishers want release dates. Ship it now, patch it later became the actual plan. It’s cheaper than delay.

But I think there’s a stranger thing happening too. Modern games don’t seem to assume they’ll ever be truly finished. They’re designed around being fixed later. The developers know players will find things. The players know the game will improve. It’s almost collaborative, except the collaboration is you debugging someone else’s product for free.

Some bugs are genuinely great—the physics engine deciding gravity works sideways, or a character sliding across the floor with their legs fused together. You remember those. You tell people about them. But the ones that lock you out of a questline or corrupt your save are just dread. They’re the opposite of charming.

I don’t think it’s laziness. I think the systems got too complicated. Too many variables. Impossible deadlines meeting impossible scope. The bug stopped being an oversight and became a cost of production. Which isn’t the same as not caring, but it’s not too far off either.