1.0 Doesn't Mean What It Used To: How 'Full Release' Became a Marketing Move

1.0 Doesn't Mean What It Used To: How 'Full Release' Became a Marketing Move

There was a time when a version number meant something. 1.0 was the finish line — the moment a development team looked at their product, took a breath, and said this is it. Ship it. That moment still exists in 2026, but it's been quietly rebranded. It's now less a declaration of completion and more a decision made in a boardroom, calibrated to hit a fiscal quarter, trigger a price increase, or unlock a storefront feature. The version number is marketing. The game is still in beta. And players are footing the bill.

The Blur Nobody Wants to Talk About

Early Access was supposed to be a transparent contract between developer and player. You pay less, you get the game early, you accept the rough edges, and the studio uses your feedback to build something better. Steam's Early Access framework, for all its flaws, at least had honesty baked into the label. The problem is that the framework worked too well — it normalized the idea of paying for unfinished software. And once that normalization set in, publishers realized they could drop the Early Access label without dropping the Early Access product.

Look at the last eighteen months of high-profile launches. Games shipping with missing story chapters, placeholder UI, absent multiplayer modes, and day-one patch notes longer than most novels. These aren't Early Access titles. They're full-price, full-release products wearing the 1.0 badge while their studios scramble to build the actual game in public. The patch cadence doesn't slow down after launch — it accelerates. Because launch isn't the finish line anymore. It's the starting pistol.

This isn't a fringe phenomenon. It's the dominant release model for mid-to-large studios in 2026. The aggressive post-launch patching cycle has been reframed as "live service commitment" and "community responsiveness." Which sounds great until you realize those are just euphemisms for we needed more time and we didn't take it.

What Regulators Are Starting to Notice

The FTC has been circling this space for a while now. Consumer advocacy groups — including the Consumer Federation of America and several state-level digital rights organizations — have pushed for clearer product disclosure standards on digital storefronts. The core argument is straightforward: if a product is described as a complete release but materially lacks features listed in its marketing materials at the time of purchase, that's a consumer protection issue, not just a PR one.

Steam, the PlayStation Store, and Xbox's marketplace all have refund policies that nominally protect players — but those policies were designed around the old model, where a game was finished before it shipped. The two-hour playtime refund window on Steam, for example, is essentially useless for a 60-hour RPG that doesn't reveal its missing third act until hour 40. Advocacy groups have flagged this gap repeatedly. Movement from regulators has been slow, but the pressure is building, and at least two pieces of pending state-level legislation in California and New York are specifically targeting digital product disclosure standards.

The Studios Getting Away With It

The pattern is consistent enough to be a playbook. A studio announces a 1.0 launch date, often following a period of Early Access or a game preview program. The 1.0 launch ships with a roadmap — which is, functionally, an admission that the game isn't done. The roadmap promises features in quarterly drops. Some of those features were in the original pitch deck. Some were in the launch trailer. Players who bought in on the strength of those promises are now waiting, post-purchase, for content that was implicitly sold as part of the package.

The roadmap model is particularly insidious because it reframes incompleteness as generosity. "We're adding this for free!" is a better headline than "this should have been in the game at launch." And the gaming press — this outlet included — has been complicit in amplifying roadmap announcements as positive news cycles rather than interrogating what their existence says about the product that preceded them.

The Developers Who Are Being Honest

It's worth noting that not every studio is playing this game. Smaller independent developers — particularly those without publisher pressure — have been more transparent about what 1.0 means for their specific project. Some have explicitly told their communities that their 1.0 is a content-complete build, not a feature-locked one, and have outlined exactly what will and won't change post-launch. That kind of communication is rare, and it stands out precisely because the industry baseline has drifted so far from it.

Larian Studios drew considerable praise for how they handled the Baldur's Gate 3 launch cycle — being explicit about what was in the game, what was being fixed, and what wasn't coming. That transparency became a competitive advantage, which is a damning indictment of how low the bar has sunk everywhere else.

Photo: Larian Studios, via bg3.wiki

Photo: Baldur's Gate 3, via static1.srcdn.com

What a New Standard Could Look Like

If the industry isn't going to self-regulate — and there's little evidence it will — then the pressure has to come from somewhere else. A few proposals have circulated in developer and consumer advocacy circles. One is a tiered labeling system on storefronts: Early Access, Feature Complete, and Content Complete, each with defined minimum criteria. Another is mandatory feature checklists at the point of purchase, updated in real time, so buyers can see exactly what is and isn't in the game before they hand over $70.

Neither of these is a perfect solution. But they're both more honest than the current system, which asks players to trust that 1.0 means something — and then quietly hopes they don't notice when it doesn't.

The Bottom Line

The version number used to be a promise. In 2026, it's a price point trigger and a platform fee unlock. Players have adapted — the savvier ones wait for the "actually finished" patch that drops three to six months post-launch, which has become its own cynical genre of gaming discourse. But adaptation isn't the same as acceptance, and the fact that players have learned to game the system doesn't mean the system is working. It means the system is broken in a predictable enough way that people have built workarounds.

The 1.0 label isn't a quality benchmark anymore. It's a marketing decision. And until storefronts, regulators, or the industry itself decides to make that label mean something again, every full-price launch is going to come with an asterisk the size of a day-one patch.