This trend is being sold as inevitable. It deserves more skepticism than it is getting.
We live in an era where a game's "true" score supposedly arrives only after patches, balance updates, and community feedback reshape the experience weeks or months post-launch. Publishers and outlets alike have bought into the narrative that review scores are living documents, constantly subject to revision based on post-release conditions. It's presented as natural evolution. It's actually a dangerous erosion of what reviews are supposed to do.
Consider what happened recently with Mortal Shell 2. The game arrived to strong critical reception, praising its heavy metal aesthetic and mechanical depth. Then patches rolled out addressing perceived difficulty spikes. Players debated whether the original experience was what reviewers should have assessed. Some suggested scores might need adjustment. This thinking has metastasized across the industry.
The problem is simple: A review score should capture what a critic experienced with what existed at the time of review. That's the whole point. When we allow scores to become fluid, updated as developers tweak and refine, we're not improving criticism. We're dissolving it.
Let's be clear about what's actually happening here. Publishers benefit from this model. A rocky launch followed by patches and updates can generate positive buzz, second-chance narratives, and justifications for "wait and see" attitudes. Outlets benefit too, sometimes getting more engagement from "updated review" content than from original coverage. It feels collaborative and responsive. But it's really just convenience dressed up as accountability.
The dangerous part? It suggests that initial critical evaluation was somehow premature or incomplete. It wasn't. If a game shipped with balance problems, obtuse design choices, or technical issues, reviewers should catch that. Not as a failure to be corrected later, but as relevant information about the product consumers received on day one.
Yes, games are complex. Yes, patches are normal now. But there's a difference between acknowledging that games evolve and pretending that a review's purpose is to predict what a game might become months later.
The gaming press already struggles with perception problems. Accusations of bias, conflicts of interest, and favoritism circle constantly. Adding "our scores might change" to that mix doesn't solve anything. It adds confusion about what a review actually means. Is a 7/10 a judgment of the game as released? As it exists now? As it might be in three months?
This matters because reviews aren't primarily for people who get access to day-one copies. They're for regular players trying to decide whether to spend sixty dollars. Those players need clarity. They need to know: Does this game, right now, at this price, deserve my time and money? That's answerable on launch day. That's what a review should address.
The alternative is worth considering too. Imagine if we treated reviews as actual journalism again, with all that implies. A critic plays a game, forms an opinion, publishes it. If the game changes dramatically, fine, write a follow-up piece. Call it an update, an analysis, a second look. Don't pretend the score itself was somehow incomplete.
Games should absolutely be patched and improved. Developers should respond to feedback. That's healthy. But the critical process shouldn't become hostage to post-launch development. That conflates reviewing with predicting, and criticism with service journalism.
We have tools for monitoring how games evolve. We have forums, communities, and yes, follow-up coverage. Let's use those instead of corrupting the review itself into something that can't be pinned down.
A score is a moment captured in time. It should stay that way.