Why the Hundred-Hour Open World Is a Budgeting Problem

Marketing copy for a new open-world release almost always leads with a number: a hundred hours of content, or a map twice the size of the last one, or more collectibles than any previous game in the series. It’s worth asking why “how much” became the pitch instead of “how good,” because the answer isn’t really about players demanding longer games. It’s about how a publisher justifies a production budget internally, long before a single trailer reaches an audience, and the length of the finished map is one of the more visible symptoms of that internal argument leaking out onto the shelf.

The pitch a studio has to make upward

A triple-A open-world project now routinely costs hundreds of millions of dollars and several years of a large team’s time to finish, and that budget has to be approved, defended, and re-justified at every stage by people who answer to shareholders rather than players. “A tightly focused thirty-hour game with no padding” is a much harder internal pitch to defend against that kind of spend than “a hundred-hour open world with a map full of activities,” even if the shorter game would be the better one, because the larger map produces something a budget committee can point to: screenshots of scale, a spreadsheet of activity types, a headline hour count for the press release. Density of good design doesn’t photograph well in a pitch deck. Square mileage does, and a map’s dimensions are a number a studio head can put in front of a publisher’s finance team without needing to explain a single design decision underneath it. That asymmetry — scale is legible to people who’ve never played the game, quality of pacing is not — is close to the root of the whole problem, and it exists well before a single line of the game’s actual content has been written.

Towers, icons, and the cheapest kind of content

The mechanism most associated with this problem is the map-filling tower or vista point, a device Jay has traced back to its origins and its descendants elsewhere on this desk — climb a structure, unlock a region’s worth of icons, and now the player has a checklist instead of a mystery. It’s the cheapest kind of content a large open world can produce, because it doesn’t require bespoke writing, unique level geometry, or new mechanical ideas; it requires copying a template across a map that’s already been built for other reasons, then filling the gaps with variations on one or two collectible types. A hundred-hour map padded this way isn’t a hundred hours of design effort. It’s often closer to twenty hours of genuinely authored content, multiplied by five through repetition.

Fast travel as a tell, not a convenience

Fast travel is usually framed as a quality-of-life feature, letting players skip the tedium of crossing ground they’ve already seen. It’s also a quiet admission about how the map was built. Jay’s essay on why fast travel kills the thing you liked makes the case that a world worth walking across doesn’t need a skip button nearly as badly as a world built to hit a size target does — and the games that rely most heavily on fast travel tend to be exactly the ones whose open space between waypoints is thinnest. A map dense enough with bespoke encounters to reward walking rarely needs to apologise for the distance between two points. A map padded to a marketing-friendly size almost always does, and fast travel is the feature that lets a studio avoid admitting the gap between those two kinds of scale out loud.

The map screen’s own confession

The map screen itself, layered with dozens of icon types in a legend running down one side of the pause menu, is its own kind of admission: a system built because the world alone couldn’t communicate what mattered inside it, so a UI layer had to be bolted on top to do that job instead. A densely authored open world doesn’t need forty icon types to tell a player where the good content is, because the good content is findable through play. The icon-heavy map is the budgeting problem made visible in interface form — proof that a huge amount of what’s in the world was placed algorithmically rather than by hand, because nothing placed by hand needs quite that much cataloguing to be found again.

The counter-evidence: length without padding

The strongest rebuttal to the “big equals bloated” assumption is that some genuinely long open worlds don’t feel padded, and the difference is legible in what fills the space between story beats. Jay’s revisit of Elden Ring’s sightline-driven open world argued that FromSoftware built a map you navigate by curiosity rather than checklist, and crucially, most of what you find following that curiosity is a bespoke, hand-placed encounter or a genuine secret rather than a recoloured collectible. The map is enormous and the hours are real, but very little of it is filler in the sense this essay means — each dungeon, each boss, each hidden questline was built individually rather than templated across the map to hit a size target. Length isn’t the problem. Length manufactured to justify a budget, rather than earned by genuinely distinct content, is the problem.

Live service made the incentive permanent

Games-as-a-service models raised the stakes on this problem rather than solving it. Once a publisher’s business model depends on players staying inside a single game for months or years rather than moving on to the next release, the pressure to keep the map, the activity list, and the season-by-season content drip growing indefinitely becomes structural rather than optional. A finite, well-paced hundred-hour campaign is a one-time budgeting problem; a live-service map that has to keep expanding every quarter to justify a season pass is a permanent one, and it’s one of the reasons the padding conversation has only intensified as more publishers have chased that revenue model. The map doesn’t just need to be big enough to justify the initial budget any more. It needs to keep growing to justify the next season’s budget too.

The marketing number and the review cycle

Hour counts have become a specific, quotable marketing asset, repeated in previews and reviews alike as a proxy for value, and that repetition creates its own pressure independent of anything a studio’s designers actually want. A game that reviews well but clocks in shorter than a competitor’s open world risks a value-for-money narrative forming around it regardless of quality — “great but short” is a headline that’s cost several genuinely excellent, tightly made games some of their commercial momentum. Once that dynamic is understood industry-wide, the incentive to pad a map past the point the content justifies becomes close to unavoidable for any studio chasing the top of a sales chart rather than the top of a critics’ list.

Where the padding actually gets made

It rarely happens where you’d expect — writers rarely sit down intending to pad a script. Padding gets manufactured further upstream, in the production planning meeting where a region’s activity budget gets set against the number of hours marketing has asked the map to support, often long before the story’s beats or the region’s actual shape have been finalised. That ordering is backwards from how the best-paced games get built, where the map’s size is a consequence of how much genuinely good content the team can produce in the schedule, rather than a target set first and filled in afterward. A designer told “this region needs six hours of content” with a budget that only covers two hours of bespoke design will fill the remaining four with systemic, repeatable activities, because that’s the only tool available at that point in a schedule that’s already been locked. The padding isn’t laziness. It’s the predictable output of a target set before the content that has to fill it was actually designed.

What a healthier budgeting conversation looks like

The fix isn’t smaller maps by default; some stories genuinely need the space a hundred-hour world provides. The fix is treating “hours of content” as a byproduct of good design rather than a target set independently of it, and being willing to defend a shorter, denser game internally on the strength of its density rather than assuming a budget committee will only fund scale. A few publishers have begun shipping games explicitly built around this idea — tightly scoped, fifteen-to-twenty-five-hour open worlds that don’t apologise for their size — and the fact that those games routinely review as strongly as their hundred-hour counterparts, on a fraction of the budget and development time, is itself the clearest evidence that the padding was never a creative necessity. It was a budgeting habit, formed under a specific set of commercial pressures, and habits like that only change when enough of the industry’s commercial evidence points the other way.

The reader’s actual stake in this

None of this is an abstract industry argument; it’s a direct trade against a reader’s own limited hours. Every checklist icon a game asks you to clear is an hour that could have gone toward a shorter, better-paced game, or toward a different game entirely. Jay’s revisit of Assassin’s Creed Valhalla makes the case directly against one of the clearest examples currently on shelves — a genuinely good fifteen-minute raid loop, buried under a hundred additional hours of map furniture that exists because a spreadsheet somewhere needed a bigger number, not because the game needed it to be good.