Section214 | Fresh Perspectives

Balance is the holy grail of game design. Developers chase it through endless patches, player feedback loops, and telemetry data. The assumption is simple: a perfectly balanced game is a perfectly fair game, and fairness keeps players engaged. But if you look at the titles that have dominated competitive scenes and casual play for decades, a strange pattern emerges. The most meticulously balanced games are often the least memorable. Marcus Kettner here, and I want to walk through why equilibrium can be the enemy of excitement, using concrete examples from fighting games, shooters, and strategy titles.

The Paradox of Perfect Symmetry

When every option is equally viable, no option feels special. This is the core problem. In a perfectly balanced system, the choice between character A and character B becomes a matter of aesthetic preference rather than strategic commitment. The decision loses weight. Take Street Fighter II as a case study. The original Street Fighter II: The World Warrior was a broken mess by modern standards. Guile’s handcuff glitch could lock opponents in infinite blockstun. Zangief’s lariat had absurd priority. Yet that imbalance created a metagame of legends. Players didn’t just pick a character; they picked a cause. Maining Dhalsim meant accepting a brutal learning curve in exchange for unmatched zoning potential. Choosing Zangief meant gambling on close-range dominance. The asymmetry gave the game texture.

Compare that to Street Fighter V’s later seasons. Capcom’s balance patches sanded down the extremes. Almost every character gained a reliable anti-air, a workable reversal, and a V-Trigger comeback mechanic. The result was a roster where individual identity blurred. Tournament representation became more diverse, which statisticians celebrated, but viewership and casual engagement declined. When everyone is viable, no one is exciting. The game became a spreadsheet with hitboxes.

Imbalance as Narrative Engine

Competitive games thrive on stories, and stories require conflict. A perfectly balanced game is a flat line. There are no villains, no underdogs, no forbidden techniques that the community whispers about. Super Smash Bros. Melee is the definitive example. The game’s tier list has been debated for two decades, but Fox and Falco have always sat at the top. Marth, Sheik, and Jigglypuff form a second tier. The rest of the cast is largely unviable at high-level play. This imbalance should have killed the scene. Instead, it created a narrative engine. When a low-tier hero like Axe’s Pikachu or aMSa’s Yoshi makes a deep tournament run, the crowd erupts. The imbalance gives those moments meaning. If every character were equally strong, those upsets would be unremarkable.

Nintendo’s approach with Super Smash Bros. Ultimate is instructive. The game launched with a roster of over 70 characters, all tuned to be tournament-legal. The balance team has issued regular patches to keep outliers in check. The result is a game where tier lists are compressed, and character specialists can compete with almost anyone. It is a triumph of design. It is also, for many spectators, less compelling than Melee. The compressed skill gap and homogenized matchups reduce the potential for Cinderella stories. When everyone is special, no one is.

The Overwatch Dilemma: Balance by Spreadsheet

Blizzard’s Overwatch provides a modern cautionary tale. At launch, the game was gloriously unbalanced. Bastion could set up in a corner and melt an entire team. Mercy’s mass resurrection could undo a minute of coordinated effort with a single button press. These elements were frustrating, but they gave the game a wild, memorable identity. As the competitive scene matured, Blizzard chased perfect balance. They reworked Mercy. They reworked Symmetra. They reworked Torbjörn. They introduced role queue to enforce 2-2-2 compositions. Each change made the game more mathematically fair. Each change also stripped away a piece of what made Overwatch feel like Overwatch.

By the time Overwatch 2 arrived, the philosophy had calcified. The shift to 5v5 removed a tank, reducing the chaos of six-player interactions. Heroes were tuned to fit neatly into defined roles with predictable damage breakpoints. The game became a cleaner, more legible esport. It also became, for many players, a less interesting one. The lesson is not that imbalance is good. The lesson is that balance achieved by sanding off every rough edge produces a smooth, featureless surface. Players need friction to care.

Chess: The Exception That Proves the Rule

Chess is often cited as the ultimate balanced game. White has a slight first-move advantage, but otherwise the pieces are identical. The game has survived centuries. Yet chess is not balanced in the way a modern video game is balanced. The asymmetry comes from the players themselves. Human beings are wildly imbalanced in skill, preparation, and psychological fortitude. The game is a perfectly symmetrical canvas on which deeply asymmetrical humans paint. That is why it works. When a game is both mechanically symmetrical and populated by players of similar skill, it collapses into a coin flip. The drama evaporates.

Digital games attempt to balance both the system and the players through matchmaking. The result is a double symmetry: equal tools and equal opponents. This is the recipe for a forgettable experience. A game needs at least one axis of asymmetry to generate tension. Either the tools must be uneven, or the players must be. Chess relies on the latter. Most esports rely on the former, and when they over-polish the former, they lose the latter’s ability to compensate.

Magic: The Gathering’s Color Pie as Controlled Chaos

Magic: The Gathering is a masterclass in managed imbalance. The five colors of mana each have mechanical identities with deliberate strengths and weaknesses. Blue can counter spells but struggles to remove resolved permanents. Black can destroy creatures but cannot handle artifacts. Red is fast and fragile. Green has the biggest creatures but limited interaction. White has efficient answers but relies on small creatures. This asymmetry is the game’s engine. When one color becomes too dominant, the metagame warps, and players demand bans. But the goal is never perfect balance. The goal is a rotating imbalance that keeps the puzzle fresh. Each set release tilts the scales in a new direction, forcing players to adapt. The imbalance is the content.

Wizards of the Coast learned this lesson painfully with Magic: The Gathering Arena’s digital-only formats. When they introduced cards that could be rebalanced via server-side patches, they gained the ability to fix overpowered cards instantly. But they also lost something: the community-driven process of discovering counters, the organic metagame shifts, the sense that a broken card was a shared challenge to overcome. Perfect balance, delivered by fiat, felt sterile.

The Fighting Game Character Crisis

Fighting games live and die by their character rosters. A diverse cast with distinct playstyles is the genre’s lifeblood. When developers over-balance, they risk creating what the community calls “function characters” — fighters who differ only in their animations while sharing identical frame data, hitboxes, and game plans. Street Fighter V’s early seasons suffered from this. Ryu, Ken, and Akuma all had similar shoto toolsets, but balance patches gradually gave everyone a reliable invincible reversal, a crush counter button, and a V-Trigger comeback mechanic. The characters began to feel like skins rather than distinct entities.

Contrast this with Guilty Gear Strive. Arc System Works deliberately designed characters with extreme strengths and glaring weaknesses. Happy Chaos has oppressive zoning but requires meter management that can leave him vulnerable. Potemkin has the highest health and devastating grabs but no dash. Nagoriyuki has massive range and damage but a blood rage mechanic that can kill him. These sharp edges create identity. Players do not just pick a character; they pick a lifestyle. The imbalances are the game’s personality.

The Data-Driven Death of Surprise

Modern game development is increasingly data-driven. Telemetry tracks every kill, every death, every ability usage. Developers can see with mathematical precision which heroes are overperforming and which are underperforming. This leads to a cycle of micro-adjustments: a 5% damage nerf here, a 0.2-second cooldown increase there. The goal is to bring every option within a narrow band of statistical parity. The result is a game that feels designed by a committee of actuaries.

League of Legends is the poster child for this approach. Riot Games balances over 160 champions with a cadence of bi-weekly patches. The balance team aims for every champion to hover around a 50% win rate. When a champion spikes to 52%, they get nerfed. When they drop to 48%, they get buffed. This creates a metronome effect where the meta never settles. Players are constantly chasing the latest patch notes rather than mastering a stable set of tools. The game becomes a treadmill of adjustments. Mastery is devalued because the target is always moving. The pursuit of perfect balance creates a state of permanent instability.

Asymmetry as the Soul of Strategy

Strategy games are built on asymmetric starts. Civilization VI gives each leader unique abilities, units, and infrastructure. Some are objectively stronger on certain map types. Russia’s Lavra district gives them a massive advantage on tundra maps. Korea’s Seowon makes them a science powerhouse. These imbalances are not bugs; they are the game. Players choose a civilization not just for its flag but for its brokenness. The fun comes from exploiting a lopsided advantage against opponents who are doing the same with their own lopsided advantages. Perfect symmetry would turn Civilization into a spreadsheet simulator.

StarCraft is the gold standard of asymmetric balance. The three races — Terran, Zerg, and Protoss — share almost no units or mechanics. Terran relies on ranged firepower and positional play. Zerg swarms with numbers and map control. Protoss uses expensive, high-impact units. The game is balanced not by making the races equal but by making their inequalities interact in a stable rock-paper-scissors dynamic. This is the hardest kind of balance to achieve, and it is also the most rewarding. When Blizzard over-patched StarCraft II in response to community complaints, they often flattened the very asymmetries that made the game compelling.

The Casual-Competitive Divide

One of the most destructive patterns in modern game design is balancing for the top 1% of players while ignoring the experience of everyone else. Developers see a character dominating in Grandmaster and apply a nerf that makes the character unplayable in Gold. Apex Legends has wrestled with this. When Wraith’s pick rate soared in ranked play, Respawn repeatedly adjusted her abilities. Each change made her less forgiving for casual players while barely affecting her viability at the highest level, where her strength came from coordinated team play rather than her individual kit. The result was a character that felt punishing to play for anyone below Diamond rank.

The opposite problem is equally damaging. When developers balance exclusively for the median player, they often remove the tools that skilled players use to differentiate themselves. Halo Infinite’s launch-state melee system is a case study. The lunge range and magnetism were tuned to feel satisfying for controller players on couches, but they removed the precision that separated good melee players from great ones in earlier titles. The result was a system that felt fair but shallow. Balance that ignores skill expression is balance that ignores the reason people invest thousands of hours into a game.

When Balance Patches Become Content

Some games have turned balance patches into their primary content delivery mechanism. This is a dangerous game. When the only thing that changes in a live-service title is the numbers, players begin to see the game as a math problem rather than a world to inhabit. Diablo IV’s first year illustrates this trap. Seasonal updates brought extensive balance changes to classes and skills. Players would solve the new meta within a week, then spend the rest of the season waiting for the next set of adjustments. The game became a cycle of waiting for buffs to their favorite class and complaining about nerfs to the current top performer. The actual gameplay — the visceral experience of slaying demons — became secondary to the spreadsheet.

This is not to say balance patches are inherently bad. They are necessary. But when balance becomes the primary form of content, the game loses its identity. Players stop asking “What crazy thing can I do today?” and start asking “What is the optimal build this patch?” The game shifts from a playground to a homework assignment.

The Beauty of Broken Things

Some of the most beloved games in history are objectively broken. Super Smash Bros. Melee was never intended to be a competitive game; its advanced techniques are exploits of the physics engine. StarCraft: Brood War’s balance was never patched; the metagame evolved over a decade as players discovered new strategies within a fixed, imperfect system. Team Fortress 2’s rocket jumping was a bug that became the Soldier’s defining feature. These games are not loved despite their brokenness; they are loved because of it. The rough edges give players something to grab onto, something to master, something to argue about.

When a game is too polished, too balanced, too fair, it becomes a smooth sphere. There is nothing to grip. Players slide off. The games that endure are the ones with texture — the ones where a particular character is “cheap,” where a particular strategy is “broken,” where the community has to develop its own norms and counterplay. These imperfections are not flaws to be patched out. They are features that give a game its shape.

Finding the Right Kind of Imbalance

This is not an argument for abandoning balance entirely. A game where one option dominates all others is not interesting either. The goal should be managed imbalance — a state where multiple options are viable but meaningfully different, where some options are stronger in specific contexts, where player skill can overcome statistical disadvantages. The best games are not balanced; they are tuned. They have a curve, not a flat line. They give players hills to climb and valleys to explore.

Dota 2 is perhaps the best example of this philosophy. The game is famously complex, with over 120 heroes each possessing unique abilities. Some heroes have win rates that dip below 45% in public games but are first-pick material in professional play because of their specific synergies. IceFrog, the game’s long-time balancer, does not aim for a 50% win rate across all heroes. He aims for every hero to have a situation where they are the best choice. This creates a metagame of niches rather than a metagame of averages. It is a far more interesting and sustainable approach.

The lesson for developers and players alike is that balance is a tool, not a goal. It should serve the larger purpose of creating a compelling, varied, and deep experience. When balance becomes the goal itself, the experience suffers. The most balanced games are often the least interesting because they have optimized away the very things that make games worth playing: surprise, discovery, mastery, and the thrill of beating the odds.

FAQ

Does perfect balance actually exist in any competitive game?

No. Even in games with identical starting conditions, like chess, the first-move advantage creates a measurable imbalance. In asymmetric games, perfect balance is mathematically impossible because different tools will always have different utility in different contexts. The pursuit of perfect balance is a pursuit of an unattainable ideal. What developers should aim for is a state where no single strategy dominates all others and where player skill is the primary determinant of outcomes.

Why do developers keep chasing perfect balance if it makes games boring?

Because player complaints are loudest when something feels unfair. A player who loses to a “broken” strategy will often blame the game rather than their own skill. Developers respond to this feedback with balance patches to reduce complaints. The problem is that the players who appreciate imbalance — the ones who enjoy finding counters, who relish the challenge of an uphill matchup — are quieter. Developers hear the squeaky wheels and sand down the edges, not realizing they are also sanding away the game’s soul.

How can I tell if a game is over-balanced?

Look for these signs: character or class pick rates that cluster tightly around 50% with no outliers; frequent small numerical adjustments in patch notes (2% damage changes, 0.1-second cooldown shifts); a metagame that shifts entirely with each patch rather than evolving organically; and a community that talks more about balance than about strategy. If the conversation is always about what the developers should change rather than what players can discover, the game is likely over-balanced.

What is the difference between a broken game and a productively imbalanced one?

A broken game has one or more options that are so dominant they invalidate all others. In a productively imbalanced game, multiple options are viable, but they are viable in different situations or at different skill levels. The key is that player choice matters. If you can pick a low-tier option and win through superior skill, the imbalance is productive. If the low-tier option cannot win under any circumstances, the game is broken. The line is not always clear, but the test is whether the imbalance creates interesting decisions or removes them.

The Future of Balance Philosophy

There are signs that some developers are learning. Riot Games has experimented with “balance thrashing” in League of Legends — intentionally over-buffing underplayed champions to force them into the meta, then dialing them back once players have discovered them. This creates artificial imbalance as a form of content. It is a recognition that a perfectly flat metagame is boring. Valorant’s agent design shows a similar awareness. Each agent has a sharply defined role with clear strengths and weaknesses. The balance team does not try to make every agent equally viable on every map; instead, they design maps that favor different agents, creating a rotating imbalance that keeps the game fresh.

The indie scene has been more willing to embrace productive imbalance. Slay the Spire does not try to make every card equally good. Some cards are intentionally weak, serving as traps for inexperienced players or as niche combo pieces for advanced strategies. The imbalance is part of the learning curve. Discovering that a card you thought was good is actually bad is a moment of growth. A perfectly balanced card pool would rob players of that discovery.

The path forward is not to abandon balance but to redefine it. Balance should mean “every option has a context where it shines” rather than “every option is equally good in all contexts.” It should mean “player skill can overcome statistical disadvantages” rather than “statistical disadvantages do not exist.” It should mean “the game is a conversation between designers and players” rather than “the designers have solved the game and delivered the solution.” The most interesting games are not the most balanced. They are the ones where balance is a journey, not a destination.

I’ve been reviewing games for more than ten years, and I’ve watched the industry tie itself in knots over a single, reductive number. A 7.8. An 8.5. A 9.2. These digits are supposed to summarize dozens of hours of play, layered systems, narrative ambition, and technical execution. They don’t. They can’t. And yet we keep stamping them onto every release as if a game’s worth can be measured like a toaster’s energy rating. The real problem isn’t just that scores are subjective—it’s that they actively warp how we discuss, design, and remember games.

The Origin of the Score: A Shortcut That Became a Crutch

Review scores started as a convenience. In the print magazine days, flipping through Electronic Gaming Monthly or GamePro, you’d spot a bold number and decide whether to drop $50. The score was a filter, not a final judgment. But somewhere along the way, that filter hardened into a verdict. Metacritic, launched in 2001, turned the aggregate score into a weapon. Publishers started tying bonuses to Metacritic thresholds—Obsidian famously missed a Fallout: New Vegas bonus by a single point, an 84 instead of an 85. One digit cost a studio millions. That should have sparked a reckoning. Instead, it normalized the idea that a game’s commercial fate could rest on a weighted average of opinions from outlets with wildly different standards.

Look at the scoring scales themselves. Some sites use a 10-point scale with decimal increments, as if that precision means something. Others use a 5-star system that mashes nuance into broad buckets. IGN’s 10-point scale once reserved a 10 for “masterpiece,” but the definition of masterpiece shifted so often the score lost all meaning. God of War (2018) got a 10, and the text praised its reinvention of a tired series. The Last of Us Part II got a 10, and the text wrestled with its divisive narrative. Same number, completely different justifications. The score tells you nothing about why a game matters—only that someone decided it does.

What a Number Erases: The Case of Disco Elysium

Take Disco Elysium. It launched with a Metacritic score of 91, a number that screams near-universal acclaim. But that 91 erases the fact that the game has no combat, that its core mechanic is internal dialogue, that it asks you to fail skill checks and live with the consequences. A player who buys it based on the score alone might expect a traditional RPG and bounce off the first hour of existential despair. The score doesn’t communicate that the game is a slow, literary burn—it just says “good.”

Worse, the score flattens the game’s actual flaws. Disco Elysium had performance issues at launch, a clunky inventory system, and a final act that some critics felt lost momentum. A 91 implies near-perfection, but the game is fascinating because of its rough edges, not despite them. When we reduce it to a number, we lose the texture that makes criticism valuable. We’re left with a hollow endorsement that serves marketing departments more than players.

The 7/10 Trap: How Scores Kill Interesting Games

There’s a graveyard of games that scored in the 70s on Metacritic and were dismissed as “just okay.” But many of those games are more memorable than their 85+ counterparts because they took risks that didn’t land cleanly. Alpha Protocol sits at a 72. It’s a spy RPG with a dialogue system that forces you to choose a stance—aggressive, professional, suave—on a timer, and the story branches so aggressively that entire characters can vanish based on your choices. The shooting is mediocre. The stealth is inconsistent. But no other game has replicated its reactive narrative. A 72 tells you it’s flawed. It doesn’t tell you it’s one of the most ambitious conversation systems ever built.

Compare that to Assassin’s Creed Valhalla, which holds an 80 on Metacritic. It’s a polished, enormous, competent open-world game that does nothing particularly new. The score is higher because it’s safer, more technically stable, and fits a familiar template. The scoring system rewards games that avoid big swings. It punishes games that try something different and stumble. The result is an industry that learns the wrong lesson: don’t innovate if it might cost you five points.

The Aggregation Problem: Mixing Oil and Water

Metacritic’s methodology is a black box, but we know it weights outlets differently. A review from a major publication counts more than one from a niche site. That weighting assumes that a generalist outlet’s opinion is more valid for all players, which is absurd. A hardcore strategy fan doesn’t care what a mainstream reviewer thinks about Crusader Kings III—they want the perspective of someone who understands succession laws and casus belli. But the aggregate score buries those specialized voices under the weight of outlets reviewing for a hypothetical “average gamer.”

Even worse, Metacritic converts qualitative scores into quantitative ones. A 4/5 becomes an 80. A B+ becomes an 83. These conversions are arbitrary and inconsistent across publications. A “Recommended” badge from Eurogamer—which explicitly avoids scores—gets turned into a number anyway. The system forces everything into a single dimension, then claims that dimension is objective. It’s not. It’s a statistical fiction.

When Scores Become the Story: The Review Bombing Phenomenon

User scores on Metacritic have become a battleground for culture wars that have nothing to do with a game’s quality. The Last of Us Part II was flooded with 0/10 scores within hours of release, before anyone could have finished its 25-hour campaign. The score became a proxy for anger over narrative decisions, representation, and leaks. The actual game—its level design, its accessibility features, its technical polish—was irrelevant. The number was a weapon.

This isn’t an isolated case. Borderlands 3 was review-bombed over an Epic Games Store exclusivity deal. Warframe caught negative scores because of a Discord moderator controversy. In each case, the user score told you nothing about the game. But because Metacritic displays it alongside the critic score, it creates a false equivalence. A curious player sees a 5.7 user score next to a 94 critic score and assumes there’s a hidden flaw. There isn’t. There’s just a number that’s been hijacked.

The Developer’s Dilemma: Designing for the Score

I’ve spoken with developers who admit they make design decisions with Metacritic in mind. One told me they cut a divisive ending because they feared it would drag the score below 80. Another said they padded their game with repetitive side content because “reviewers equate length with value.” When a score becomes a target, games become checklists. You get open worlds littered with towers to climb, camps to clear, and collectibles to gather—not because those activities are fun, but because they signal “content density” to a reviewer who has 40 hours to play before embargo lifts.

The most damaging effect is on difficulty. A game that’s too hard risks frustrating reviewers who are rushing to meet a deadline. So we get default difficulty settings that are trivial for experienced players, with the “real” game locked behind a menu option. Doom Eternal is a masterpiece of first-person combat design, but its default difficulty undersells the game’s rhythm. Many players never discover the weapon-switching ballet because the game doesn’t force them to learn it. The score doesn’t reflect that the default experience is a diluted version of the intended one.

The Alternative: Contextual Criticism Without a Number

Some outlets have abandoned scores entirely. Eurogamer uses a “Recommended” badge, with occasional “Essential” and “Avoid” tags. Rock Paper Shotgun writes verdicts in plain English. Kotaku doesn’t score. These approaches force the reader to engage with the text, to understand why a game is worth their time. They also free the critic to write honestly about a game’s flaws without worrying that a 7/10 will be misinterpreted as a pan.

But the industry resists. Publishers want scores for marketing. Aggregators want scores for traffic. And readers, conditioned by decades of habit, often scroll straight to the number. Breaking that cycle requires a cultural shift, not just an editorial one. It requires players to value their own preferences over a consensus. It requires them to ask, “What does this game do that I care about?” instead of “Is this game good?”

How to Read a Review in a Post-Score World

If you’re stuck with scored reviews, here’s how I recommend you use them. First, ignore the aggregate. Find one or two critics whose tastes align with yours and read their full text. If you love immersive sims, follow someone who dissected Prey (2017) with the same enthusiasm you felt. If you bounce off open-world fatigue, find a critic who called out Horizon Forbidden West for its map clutter. A critic’s history is more predictive than any number.

Second, read the last paragraph of a review first. That’s where the critic usually summarizes what the game feels like, not just what it scores. A verdict that says “this is a messy, brilliant game that will frustrate you as often as it delights you” tells you more than an 8.5 ever could. If that description intrigues you, read the rest. If it sounds exhausting, skip it—even if the score is high.

Third, look for specific complaints, not general ones. “The combat is clunky” is useless. “The dodge has a half-second input delay that makes fast enemies feel unfair” is actionable. That level of detail tells you whether the problem will bother you. A score can’t do that. Only words can.

FAQ

Why do so many sites still use review scores if they’re flawed?

Scores drive traffic and provide a quick reference for readers who don’t have time to read a full review. They also feed into Metacritic, which publishers use for marketing and, in some cases, developer bonuses. Removing scores can reduce a site’s visibility and influence, so many outlets keep them despite recognizing their limitations.

What’s a better way to quickly judge a game’s quality?

Instead of looking at a number, scan the review’s summary paragraph and check for specific praise or criticism that matches your tastes. For example, if a review highlights a game’s deep crafting system and you love crafting, that’s a stronger signal than an 85. Also, watch gameplay videos to see the mechanics in action—nothing replaces your own eyes.

Do user scores on Metacritic ever provide useful information?

Rarely. User scores are vulnerable to review bombing, where coordinated groups post extreme scores to manipulate the average. They can be useful for spotting technical issues—like a bad PC port—if you read the actual user reviews and look for patterns in complaints. But the number itself is almost always meaningless.

How have review scores affected game development?

Developers often target specific Metacritic thresholds for bonuses or publisher approval, which can lead to safer design choices. Games may avoid controversial narratives, pad content to appear longer, or default to easy difficulty to prevent reviewer frustration. This focus on scores can stifle innovation and result in homogenized experiences.

I caught myself staring at a number again last night. A 7. Perfectly respectable, stamped at the bottom of a review for a game I’d spent sixty hours pulling apart. That 7 is supposed to stand for labyrinthine level design, a combat system that rewards patience over twitch reflexes, and a narrative that deliberately refuses to hand you closure. But it doesn’t. It flattens all of that into a digit that sits right next to a 7 for a competent but forgettable racing sim from the same outlet. The two games share nothing except the number, and that’s exactly the problem.

Review scores have become the default shorthand for quality—a numerical anchor readers skim for and publishers obsess over. But when a game is built on contradictions—intentionally frustrating mechanics that serve a thematic point, or a story that sacrifices pacing for atmosphere—a single digit erases the very texture that makes it worth talking about. I’m not arguing against criticism or evaluation. I’m arguing that the method we’ve settled on is intellectually bankrupt for the medium we claim to love.

The Metacritic Effect: When 74 Becomes a Failure

Metacritic didn’t invent review scores, but it perfected their tyranny. By aggregating dozens of outlets into a single weighted average, it created a pseudo-objective benchmark that publishers now treat as scripture. Bonuses get tied to Metacritic thresholds. Studios get shuttered when a game lands at 74 instead of 75. The difference between those two numbers isn’t a measurable decline in quality—it’s the opinion of one reviewer who used a slightly different internal rubric.

Consider Alpha Protocol, Obsidian’s 2010 espionage RPG. It sits at a 72 on Metacritic. That number tells you nothing about its revolutionary dialogue system, where conversations happen in real time and choices lock you into responses before you’ve fully processed the situation. It doesn’t capture how the game’s buggy shooting mechanics are almost irrelevant if you build a character who talks their way through every mission. The 72 implies mediocrity. In reality, it’s one of the most ambitious reactive narrative systems ever shipped, buried under a score that compares unfavorably to dozens of polished but forgettable shooters.

The flattening effect gets worse when scores are stripped of context. A 7 from a critic who values mechanical depth means something entirely different from a 7 awarded by someone who prioritizes accessibility. But on Metacritic, they’re identical. The number becomes a blunt instrument that erases the conversation it supposedly represents.

The Genre Bias Embedded in Every Scale

Review scales are not neutral. They carry baked-in assumptions about what makes a good game, and those assumptions overwhelmingly favor specific genres. Action games benefit from criteria like responsiveness, visual spectacle, and moment-to-moment excitement. A slow-burn strategy game or an experimental walking simulator gets measured against the same yardstick, and the results are predictably absurd.

Take Pathologic 2, Ice-Pick Lodge’s survival horror remake. It’s a game about futility, about being a doctor in a town ravaged by plague where you cannot save everyone. Resources are scarce. Time is your real enemy. The game is deliberately punishing, and that punishment is the point—it’s a thematic device, not a design flaw. Yet many reviews docked it for being “frustrating” or “unfair,” applying standards from power-fantasy RPGs to a work that explicitly rejects power fantasies. The score didn’t reflect a failure of design. It reflected a failure of the scoring system to accommodate the game’s actual goals.

This genre bias extends to indie and experimental titles. Kentucky Route Zero is a magical-realist point-and-click adventure that abandons traditional puzzle design in favor of atmospheric storytelling and thematic resonance. It’s widely celebrated now, but at launch, some outlets struggled to score it because it didn’t fit their rubric. How do you assign a number to a game that intentionally subverts the concept of player agency? The answer, too often, is to penalize it for not being something it never tried to be.

The Technical Dimension That Scores Ignore

Games are not static texts. They’re software that runs differently across hardware configurations, receives patches, and evolves over time. A review score assigned at launch captures a snapshot that may be unrecognizable six months later. Cyberpunk 2077 is the obvious cautionary tale—some outlets scored it based on pre-release PC code, others on broken last-gen console versions. The scores ranged from 9 to 4, not because critics disagreed about its artistic merits, but because they were reviewing fundamentally different products.

But the problem runs deeper than high-profile launch disasters. No Man’s Sky launched in 2016 to scores averaging around 6. Today, after dozens of free expansions that added base building, multiplayer, underwater exploration, and a full narrative campaign, it’s a dramatically different game. Those original scores remain frozen in time, permanently affixed to the product like a scar. A new player researching whether to buy it sees a 6 and reasonably assumes mediocrity, unaware that the number describes a version of the game that no longer exists.

Even without catastrophic launches, technical performance varies wildly across systems. A game that runs at a locked 60fps on a high-end PC might stutter on a base PS4. The reviewer’s experience is not universal, but the score is presented as if it were. This is particularly damaging for PC strategy games and simulators, where performance is heavily dependent on hardware and where the community often resolves issues through mods and configuration tweaks that a reviewer on deadline never touches.

When Ambition Gets Punished

There’s a perverse incentive structure at work. A game that takes no risks and executes a familiar formula competently will reliably score between 7 and 8. A game that reaches for something unprecedented but stumbles in places might score a 6. The scoring system, as currently implemented, rewards safety and punishes ambition. This isn’t a theoretical concern—it shapes what gets funded and what gets greenlit.

Look at Deadly Premonition, Swery’s surreal open-world murder mystery. It’s technically atrocious. The controls are clunky, the graphics look a generation behind, and the PC port was borderline non-functional at launch. It also features one of the most memorable casts of characters in gaming, a genuinely unpredictable plot, and a tone that oscillates between horror and absurdist comedy in ways no other game has managed. Scores ranged from 2 to 10. The 2s focused on the technical failures. The 10s focused on the artistic achievement. Neither number alone captures the experience, but the aggregate score—around 68 on Metacritic—leans negative, effectively warning players away from something singular.

The same dynamic played out with Vampire: The Masquerade – Bloodlines in 2004. Troika’s RPG shipped in a broken state, and review scores reflected that. It sold poorly, Troika closed, and the game was only salvaged years later by a dedicated fan patch. Today, it’s rightly regarded as a masterpiece of atmosphere and writing. The scores that helped kill it were accurate about the bugs but blind to everything else.

The Subjectivity That Numbers Pretend to Erase

Numbers create an illusion of objectivity. An 8.5 feels precise, scientific, the result of careful measurement. But the process behind that number is anything but. Reviewers weigh different elements according to personal preference, then perform a kind of mental arithmetic to arrive at a final digit. One critic might assign 40% weight to story, 30% to gameplay, 20% to graphics, and 10% to sound. Another might invert those priorities. The resulting numbers look comparable but are built on incompatible foundations.

This pseudo-precision becomes absurd when you examine the sub-scores some outlets provide. A game receives a 9 for graphics, an 8 for sound, a 7 for gameplay, and a 9 for story, then gets an overall score of 8.5. What formula produced that average? Was it weighted? If so, how? The reader is never told, but the decimal point implies rigor. It’s a magic trick—a way of dressing up subjective judgment in the clothes of empirical measurement.

The problem intensifies with games that defy easy categorization. Disco Elysium has no combat. Its entire gameplay consists of walking, talking, and failing skill checks—and the failures are often more interesting than the successes. How do you score “gameplay” for a game that deliberately rejects the conventions of gameplay? Some outlets gave it a separate score for “narrative” and averaged that with a lower “gameplay” score, producing a final number that penalized the game for its own design philosophy. Others simply gave it a 10 and moved on. The inconsistency isn’t between games—it’s between the frameworks applied to them.

The Player’s Burden: Decoding What a 7 Actually Means

As a reader, I’ve developed an internal translation layer for review scores. An 8 from Edge magazine means something very different from an 8 from IGN. Edge uses the full 1-10 scale, where 5 is average and 7 is genuinely good. IGN’s scale, like many mainstream outlets, effectively runs from 6 to 10, where anything below 7 signals significant problems. But this translation requires institutional knowledge that most consumers don’t possess. A casual browser sees two 8s and assumes equivalence.

This decoding burden falls heaviest on players looking for niche experiences. If you love dense military simulators, a 6 from a critic who specializes in the genre carries more weight than a 9 from someone who clearly bounced off the learning curve. But aggregators don’t surface that context. They present a single number as if it represents a consensus, when it often represents a collision of incompatible perspectives.

The solution isn’t to abolish criticism—it’s to abandon the pretense that complex evaluations can be reduced to digits. Some outlets have already moved in this direction. Eurogamer dropped scores in 2015, replacing them with tags like “Essential,” “Recommended,” and “Avoid.” This system forces readers to engage with the text rather than skipping to the number. It’s not perfect—tags can still be reductive—but it’s a meaningful step away from the false precision of a 7.8.

The Publisher’s Weapon: How Scores Get Deployed Against Developers

Review scores don’t just mislead consumers—they get weaponized internally. Developers have told me, off the record, that publishers use Metacritic scores to justify withholding bonuses, canceling sequels, or reassigning teams. A game that scores 84 instead of the contractually specified 85 can cost a studio millions. That one-point gap might reflect nothing more than a few reviewers who didn’t connect with the art style, but the financial consequences are real and devastating.

This creates a chilling effect on design. If your bonus depends on hitting an 85, you’re going to sand off every rough edge that might alienate a reviewer. You’re going to prioritize broad appeal over distinctive vision. You’re going to make the game that scores well rather than the game that matters. The scoring system, in this context, becomes a mechanism for homogenization—a force that pushes the medium toward the safe, the familiar, and the forgettable.

Obsidian again provides the case study. After Alpha Protocol’s 72, the studio narrowly survived and eventually produced Fallout: New Vegas, which scored an 84 on Metacritic—one point short of the 85 threshold in their Bethesda contract. That single point allegedly cost them a substantial bonus. The game is now considered one of the finest RPGs of its generation, but the score-based contract turned a triumph into a financial disappointment. The number mattered more than the legacy.

What Should Replace the Number?

I’m not naive enough to suggest that scores will disappear. They’re too convenient for marketing departments, too embedded in consumer habits, too profitable for aggregators. But I can describe what a better system would look like, and I can point to the outlets that are already building it.

A useful review should answer three questions. First, what is this game trying to do? This requires the critic to engage with the work on its own terms, not against an abstract checklist. Second, how well does it achieve that goal? This is where technical analysis and design critique belong. Third, who is this game for? A horror game that’s too intense for casual players might be perfect for genre veterans, and the review should make that distinction explicit.

Some outlets structure their reviews around these questions without ever assigning a number. Rock Paper Shotgun’s reviews often conclude with a paragraph that synthesizes the critic’s experience and recommends the game to specific audiences. Kotaku’s reviews sometimes include a “should you play this” section that addresses different player profiles. These approaches treat readers as individuals with distinct tastes rather than as a monolith that needs a single verdict.

For outlets that insist on keeping scores, the minimum improvement would be transparency. Show the rubric. Explain the weighting. Acknowledge the platform and hardware used for testing. Update the score when major patches release. These steps wouldn’t solve the fundamental problem, but they would at least make the number’s limitations visible rather than hiding them behind a veneer of authority.

The Games That Defy Scoring

Some works are so resistant to numerical evaluation that they expose the entire system’s bankruptcy. The Stanley Parable is a game about games, a meta-commentary on choice and agency that deliberately frustrates completionist impulses. Assigning it a score feels like missing the joke. Outer Wilds is a knowledge-based exploration game where progression depends entirely on what the player understands, not what they’ve unlocked. A score can’t convey that the entire experience changes once you know certain things—and that the game is designed to be played exactly once, with full attention, like a novel you can’t reread.

Then there’s Dwarf Fortress, a game so procedurally deep and aesthetically impenetrable that it’s essentially its own genre. A review score for Dwarf Fortress is meaningless unless it’s accompanied by a detailed explanation of what the game simulates and why that simulation matters. The number tells you nothing. The stories the game generates—of fortress collapses, were-lizard infestations, and cats dying of alcohol poisoning after walking through spilled beer and cleaning themselves—are the actual review.

These games aren’t outliers. They’re the leading edge of a medium that’s still discovering what it can do. As games continue to diversify—into autobiographical experiences, generative storytelling, and forms we haven’t yet named—the single-digit score will look increasingly absurd. It’s a relic of a time when games were simpler products, evaluated like toasters on a consumer reports scale. That time is over.

Frequently Asked Questions

Why do review scores still exist if they’re so flawed?

Review scores persist because they serve multiple entrenched interests. Aggregators like Metacritic build their business model around them. Marketing departments use high scores in promotional materials. Consumers, overwhelmed by choice, use scores as a quick filtering mechanism. The system is self-reinforcing, even though everyone involved—critics, developers, and readers—acknowledges its limitations in private conversations.

Don’t some games deserve a simple numerical rating?

Some games are straightforward enough that a number feels adequate. A basic match-three puzzle game or a competent but unambitious sports title might not suffer much from being reduced to a digit. The problem is that the same system gets applied to everything, from those simple games to sprawling narrative experiments. A tool that works for one type of product fails catastrophically for another, and the industry uses the same tool across the board.

What can I do as a reader to get better information about games?

Read the full review text, not just the score. Follow critics whose tastes you understand, even if they don’t always align with yours—knowing a critic’s preferences helps you interpret their judgments. Seek out outlets that have dropped scores entirely or that provide detailed context about their evaluation process. And when a game sounds interesting despite a middling score, investigate further. Some of the most rewarding experiences in gaming sit at 72 on Metacritic, waiting for players who look past the number.

Have any major outlets successfully moved away from scores?

Yes. Eurogamer abandoned numerical scores in 2015 in favor of a recommendation system. Kotaku has experimented with score-free reviews. Rock Paper Shotgun has never used scores. These outlets demonstrate that it’s possible to build an audience without reducing criticism to digits. Their success suggests that the industry’s dependence on scores is more about habit and institutional inertia than genuine necessity.

I’ve been writing about games for over ten years, and I keep seeing the same two traps swallow smart people whole. On one side, the shill—the writer who treats every new release like a gift from the heavens, hand-waving broken mechanics because the art direction is pretty. On the other, the hater—the critic who can’t separate personal taste from structural failure, declaring a game garbage because it doesn’t cater to their specific muscle memory. Neither one does anybody any good. The real work of game analysis lives in a narrow, uncomfortable band between those poles. You have to be methodical. You have to back every claim with a specific example. And you have to admit when a game simply isn’t built for you without dismissing its value for someone else. Here’s how to do that.

Start with the Game’s Own Promises

Before you type a single word of judgment, figure out what the game claims to be. Not what you wanted it to be. Not what the marketing department exaggerated. Look at the tutorial, the first hour of gameplay, the mechanics the game actually teaches you. Dark Souls doesn’t promise a power fantasy; it promises methodical, punishing combat where patience gets rewarded. Stardew Valley doesn’t promise high-octane action; it promises a slow, systems-driven farming loop. If you criticize Dark Souls for lacking a relaxing fishing minigame, you’ve already failed the analysis. You’re not a critic; you’re just a person with a preference.

I use a simple framework: list the three core mechanics the game introduces in its first 30 minutes. For Hades, that’s dash-strike combat, boon-based build crafting, and narrative progression through failure. Every subsequent judgment I make about Hades has to reference at least one of those pillars. If the dash-strike feels unresponsive on a technical level, that’s a valid critique because it undermines a core promise. If I simply don’t enjoy roguelike repetition, that’s a personal note, not an objective flaw. The distinction matters.

Separate Technical Performance from Design Intent

This is where most game discussions collapse into shouting. A game can run at a locked 60 frames per second with zero bugs and still be poorly designed. Conversely, a game can be a technical disaster and still deliver on its design goals brilliantly. Conflating the two is lazy.

Take Cyberpunk 2077 at launch. The technical performance on base last-gen consoles was abysmal—sub-20 FPS, constant pop-in, crashes every hour. That’s a technical failure, period. But separate from that, the game’s narrative structure, side quest design, and environmental storytelling were genuinely ambitious and often successful. You can say both things in the same review without contradiction. I wrote at the time: “The game underneath the bugs is a sprawling, reactive noir RPG with some of the best side quests I’ve played in years. The game on my screen right now is a broken mess that shouldn’t have been sold.” Both statements are true, and both are backed by specific examples—the Delamain questline for the former, a crash log for the latter.

Use the “Three Examples” Rule

I never let myself make a broad claim about a game without three concrete examples. “The level design is repetitive” is a worthless sentence on its own. “The level design falls into a repetitive pattern: the three fortress dungeons in Elden Ring’s Mountaintops of the Giants—Castle Sol, the Guardians’ Garrison, and the Forge—all use the same enemy placement template of two banished knights at the entrance, a narrow corridor with fire traps, and a commander-type boss in a circular arena” is an argument. It names the locations, the pattern, and the specific elements that repeat. The reader can agree or disagree, but they can’t dismiss it as vague whining.

This rule also forces you to check your own biases. If you can’t find three specific examples to support a claim, the claim might be emotional rather than analytical. I’ve scrapped entire paragraphs after realizing I was reacting to a single frustrating death rather than a systemic issue. That’s the discipline.

Distinguish Between “I Don’t Like This” and “This Is Bad”

This is the hardest skill to develop, and I still catch myself slipping. The test is simple: can you imagine a player who would genuinely enjoy this mechanic, and can you articulate why? If the answer is yes, you’re dealing with a preference, not a flaw. Your job is to describe the mechanic accurately enough that the hypothetical player can recognize their own taste in your description.

I despise weapon degradation systems. Breath of the Wild’s fragile weapons drove me up a wall. But I can’t call it bad design, because I can articulate exactly what it achieves: it forces constant improvisation, prevents players from settling into a single dominant strategy, and turns every enemy encounter into a resource calculation. For a player who thrives on adaptability and moment-to-moment decision-making, that system is a feature, not a bug. My review said: “The weapon fragility will alienate players who prefer mastery and consistency, but it’s a deliberate tool to keep combat fluid and exploratory.” That’s analysis. “The weapons break too much” is a complaint.

Contextualize Within the Genre and the Developer’s History

No game exists in a vacuum. A competent but unremarkable open-world game from a AAA studio with a $200 million budget deserves harsher scrutiny than a competent but unremarkable open-world game from a five-person indie team. Resources, experience, and precedent all matter. When I reviewed Forspoken, I didn’t just compare it to some platonic ideal of an action RPG. I compared it to Final Fantasy XV, the previous major title from Luminous Productions, noting where it improved (traversal fluidity, spell variety) and where it regressed (side quest depth, world interactivity). I also placed it against contemporaries like Horizon Forbidden West, not to punish it for falling short, but to establish the standard that players in 2023 could reasonably expect from a $70 open-world action game.

This also means acknowledging when a developer is deliberately working against genre conventions. Disco Elysium removed combat entirely from the CRPG formula. Judging it for “lack of action” would be missing the point. Instead, the analysis should focus on whether the replacement systems—the skill-check dialogue, the Thought Cabinet—carry the weight that combat normally bears. They do, and I can prove it: the measure of a CRPG’s encounter design is whether it creates tension, meaningful choice, and character expression. The tribunal sequence in Disco Elysium achieves all three without a single health bar.

Address the Audience, Not the Developer

Too many critiques read like an open letter to the studio: “You should have done X,” “Why didn’t you fix Y?” That’s not analysis; that’s backseat game development. Your reader isn’t the developer. Your reader is someone trying to decide whether to spend $70 and 40 hours on this game. Write for them. Frame your observations as information the reader can use to make a decision, not as demands for a patch.

Instead of “The developers should have added a quest marker here,” write “The absence of quest markers in this section means you’ll need to rely on environmental clues and NPC dialogue. If you enjoy piecing together directions from a torn journal entry, this will feel immersive. If you find that tedious, you’ll be frustrated.” The first version assumes the developer made a mistake. The second version describes the experience and lets the reader decide if it matches their taste. The second version is also more accurate, because you don’t actually know whether the omission was a mistake or a deliberate choice.

When a Game Is Genuinely Bad, Show Your Work

Sometimes a game is just broken, shallow, or incompetently made. When that’s the case, you still need to prove it. “This game is terrible” is not a review; it’s a tweet. A proper negative analysis walks the reader through the failure step by step, with receipts.

I reviewed The Day Before when it briefly existed, and I didn’t just call it a scam. I documented: the Steam store page promised an open-world MMO survival game; the actual executable contained a small extraction-shooter map with no persistent world, no MMO features, and assets that matched a previously cancelled project from the same developer. I listed the missing features by name, cross-referenced them with the store description, and included timestamps from gameplay footage. That’s how you dismantle a bad game without sounding like a hater—you let the evidence do the shouting.

Credit What Works, Even in a Disaster

Conversely, almost no game is 100% irredeemable. Finding and acknowledging the one thing a game does right isn’t being soft; it’s being thorough. It also makes your criticism more credible, because it shows you’re paying attention rather than just piling on.

Anthem was a structural failure in nearly every respect—loot system, mission variety, endgame, narrative coherence. But the flight mechanics were genuinely excellent. The sense of weight, the transition from running to hovering to full jet-powered flight, the heat management that forced you to skim waterfalls and rivers to cool your thrusters—that was a well-designed system. I said so in my review, and I backed it with a description of a specific moment: diving into a canyon on a legendary contract, weaving through rock pillars while managing heat, popping up to unleash an ultimate ability, then diving again. That paragraph didn’t soften my overall verdict, which was harsh. It just made the verdict fair.

Build a Consistent Scoring or Evaluation Framework

You don’t need to publish a numerical score, but you should have an internal framework that you apply consistently across every game or piece of content you analyze. Mine has five categories: mechanical integrity (do the systems work as intended?), design coherence (do the systems support each other?), artistic execution (does the aesthetic serve the design?), technical performance (does it run properly?), and emotional resonance (does it leave a lasting impression?). I weigh these differently depending on the genre. For a competitive shooter, mechanical integrity and technical performance get more weight. For a narrative adventure, artistic execution and emotional resonance dominate.

This framework prevents me from reviewing a walking simulator and a battle royale by the same criteria, which would be absurd. It also forces me to articulate why a game succeeds or fails in terms that are relevant to its genre. When I reviewed What Remains of Edith Finch, I barely mentioned “mechanical integrity” because the mechanics are intentionally minimal—walking and interacting. Instead, I focused on how each vignette’s interaction design served its narrative theme, like the cannery sequence where you split your attention between a monotonous fish-chopping task and a fantasy world unfolding in your peripheral vision. That’s design coherence and artistic execution working in tandem.

FAQ: Common Questions About Game Critique

How do I review a game in a genre I don’t normally play?

You have two ethical options. Option one: decline the review. If you’ve never played a fighting game and can’t tell a good frame-data implementation from a bad one, your review will be useless to fighting game players. Option two: disclose your inexperience upfront and frame the review as a newcomer’s perspective. “I’ve spent five hours with Street Fighter 6 as someone whose last fighting game was SoulCalibur II in 2003. Here’s what the modern controls and tutorial systems did for me, and here’s where I still felt lost.” That’s honest and potentially valuable to other newcomers. Just don’t pretend to evaluate high-level balance when you can’t.

What if I genuinely can’t find anything positive to say?

First, triple-check your “Three Examples” rule. If you’ve documented specific failures across every relevant category and still have nothing positive, you’re probably dealing with a genuinely broken product. In that case, your review serves as a consumer warning, and that’s a legitimate function. But also ask yourself: did the game’s concept have potential? Can you articulate what a successful version of this game would look like? That’s not praise for the existing product, but it’s useful context that elevates the critique above pure negativity. “Babylon’s Fall had the kernel of an interesting idea—combining character-action combat with live-service progression—but the execution failed at every level. A game that actually delivered fluid PlatinumGames combat in a persistent multiplayer framework could work, but this isn’t it.”

How do I avoid being influenced by a game’s community or hype cycle?

I have a strict rule: I don’t read other reviews or engage with community discourse until after I’ve published my own analysis. Hype and backlash are both contagious. If you absorb a week of “this game is a masterpiece” discourse before playing, you’ll either conform to the consensus or overcorrect into contrarianism. Neither is honest. Play the game cold, form your own conclusions, write them down, and only then see what others are saying. If the community has identified a technical issue you missed—like a memory leak that only manifests after 20 hours—you can update your review with that information, clearly labeled as a post-publication addition. But your core analysis should be yours alone.

Final Thoughts: The Critic’s Responsibility

Game criticism isn’t about being right. It’s about being useful. A useful review helps a reader predict their own experience with the game, regardless of whether you personally enjoyed it. That requires precision, honesty about your own biases, and a willingness to do the unglamorous work of documenting specifics. The next time you sit down to write about a game, ask yourself: if someone who loves everything I hate reads this, will they still find it helpful? If the answer is yes, you’ve done your job.

Nobody really remembers the first ten minutes of a game. They remember the exact moment they fell for it. That moment almost never happens by accident. Someone built it—usually with a tutorial so well hidden you never realized it was teaching you anything. Tutorial design isn’t some box to check on a production spreadsheet. It’s the difference between a game that assumes you have a brain and one that treats you like you’re holding a plastic hammer for the first time. I’ve watched genuinely brilliant mechanics suffocate under clumsy introductions, and I’ve seen dead-simple ideas become unforgettable because the game knew exactly when to shut up and let me figure it out.

The Invisible Handshake Between Player and Designer

A great tutorial is a conversation. The game puts a situation in front of you, you react, and the system acknowledges that you understood—often without a single word on screen. Portal is still the textbook example. That first room gives you a portal gun and a single orange portal already sitting on a wall. You can’t move forward until you walk through it. No pop-up says “Press X to place a portal.” The room itself asks the question, and your own curiosity answers it. By the time you’re juggling multiple portals, the game has taught you momentum, flinging, and object redirection without ever dropping character. That’s not just good teaching. That’s a designer looking you in the eye and saying, “I know you’ll get this.”

Now put that next to Final Fantasy XIII, a game that spent its first twenty hours locking mechanics behind a slow-motion tutorial drip. The battle system—once it finally opened up—was genuinely inventive. The paradigm shift mechanic rewarded rapid role-switching in ways few JRPGs had even attempted. But the game didn’t trust you to handle it. It rationed complexity like a miser, and by the time the training wheels came off, a lot of players had already made up their minds: shallow, restrictive, boring. The tutorial didn’t just fail to teach. It actively poisoned how people saw the entire combat system.

When Tutorials Become the Game

Some of the best tutorials aren’t separate levels at all. They’re the first act of the story, the opening biome, the initial set of tools that define your whole relationship with the world. The Legend of Zelda: Breath of the Wild uses the Great Plateau as a masterclass in self-directed learning. You get four runes, a paraglider, and a landscape littered with quiet prompts. A cliff too high to climb without more stamina. A cold region that kills you unless you cook spicy peppers. A boulder that rolls downhill and crushes enemies if you give it a push. The game never says “Here is how physics works.” It builds a playground where physics is the only way forward.

Nintendo understood something that a lot of studios miss: failure is a teacher. Dying from cold isn’t punishment—it’s data. The player thinks, “Okay, that didn’t work. What else can I try?” That loop of hypothesis, experiment, and conclusion is the scientific method dressed up as entertainment. And it works because the stakes are low enough to encourage messing around but real enough to make success feel like you earned it.

The Tyranny of the Text Box

Nothing kills momentum faster than a wall of text explaining a mechanic you haven’t touched yet. It’s like handing someone a bicycle manual before they’ve ever seen a bike. Doom Eternal understands this in its bones. The game does have tutorial pop-ups—brief, one-sentence cards that appear when you grab a new weapon—but they’re optional to read and immediately testable. The first time you meet a Cacodemon, the game flashes “Shoot a grenade into its mouth.” You try it. It works spectacularly. The lesson lands in half a second, reinforced by the visceral feedback of the demon’s eyeball popping out. That’s not a tutorial card. That’s a dopamine hit with a footnote.

Compare this to the average 4X strategy game, where the tutorial often means forty-five minutes of reading tooltips before you’re allowed to make a meaningful decision. Civilization VI improved on its predecessors by weaving in advisor prompts that react to your current situation instead of front-loading an encyclopedia. But plenty of games in the genre still treat the tutorial as a manual, not a mentor. The result is a learning curve that feels like a cliff face—scalable, sure, but only if you’re already committed. Great tutorials lower that barrier without flattening the mountain.

Teaching Through Constraint, Not Explanation

One of the most elegant tutorial techniques is strategic limitation. Give the player a restricted toolset, then expand it once they’ve shown they can handle it. Half-Life 2 does this with the gravity gun. You first use it to pick up a can and play catch with a robot dog. It’s a toy. Later, you’re hurling sawblades at zombies. The tool didn’t change. Your understanding of it did. The game never explains the sawblade interaction. It just places a sawblade in a room full of zombies and trusts you to connect the dots.

This approach respects a basic truth about how humans learn: we understand things better when we discover them ourselves. The designer’s job isn’t to transfer knowledge. It’s to create conditions where knowledge is inevitable. Dark Souls takes this to an extreme. Its tutorial is a series of messages on the ground in the Undead Asylum. You can ignore them. You can miss them entirely. But if you pay attention, they teach you movement, combat, and the cruel logic of the world—all before you face the Asylum Demon. The game doesn’t care if you fail. It knows failure is the best teacher it has.

When Tutorials Insult the Player

Bad tutorials aren’t just ineffective. They’re actively hostile. They assume you’re incompetent, strip away your agency, and pad the runtime with unskippable hand-holding. Pokémon Sun and Moon are notorious for this. The first two hours are a relentless barrage of cutscenes and dialogue boxes explaining mechanics that anyone who’s played a game in the last decade already understands. You can’t skip them. You can’t speed them up. You just endure, waiting for the game to finally trust you with a Poké Ball. The irony is that Pokémon’s core audience skews older now—veterans who’ve been catching creatures for twenty years. The tutorial is designed for a player who no longer exists.

This is a stark contrast to Super Metroid, a game that trusts you from the first screen. You start with nothing. No map, no abilities, no direction. The game teaches you to shoot, jump, and explore through environmental cues that feel like discoveries, not instructions. The famous “noob bridge” moment—where you’re forced to run across a crumbling bridge to escape rising lava—teaches you the run button without a single word. It’s a tutorial that respects your intelligence so completely that many players don’t even recognize it as one.

The Hidden Cost of Skipping Tutorial Design

When developers treat tutorials as an afterthought, the damage ripples through the entire experience. Players who don’t understand core mechanics will blame the game, not themselves. They’ll call it clunky, unfair, or broken. Monster Hunter World faced this exact criticism at launch, despite having one of the most satisfying combat systems in action gaming. The problem wasn’t the mechanics. It was the onboarding. The game dumped weapon tutorials into a separate menu, buried under nested options, and expected players to voluntarily study them. Most didn’t. They picked up a Great Sword, whiffed five attacks, and uninstalled.

Capcom learned from this. Monster Hunter Rise introduced the Wirebug—a mobility tool that fundamentally changed combat—and made sure the first quest required you to use it. Not in a tutorial pop-up. In a situation where you had to wire-dash to reach the monster. The lesson was immediate, physical, and unforgettable. Player retention improved. Not because the game was easier, but because it was clearer.

Pacing: The Invisible Architecture of Learning

Tutorial pacing is a rhythm problem disguised as a content problem. Introduce a mechanic too early, and the player forgets it before it’s relevant. Introduce it too late, and they’ve already developed bad habits. Hades nails this rhythm by tying tutorial moments to death. Every time you die—and you will die, often—you return to the House of Hades, where new dialogue, weapons, and mirror upgrades await. The game teaches you dash-striking, boon synergies, and weapon aspects not through a single tutorial level, but through a drip-feed of discoveries spread across dozens of runs. Each death is a lesson. Each return is a syllabus update.

This approach solves the retention problem elegantly. The player never feels stuck in a tutorial because the tutorial is the game. Learning is progression. Compare this to Red Dead Redemption 2, a masterpiece of storytelling that stumbles badly in its opening hours. The snow chapter teaches you hunting, camp management, and combat through a linear sequence of missions that feel more like a checklist than an adventure. By the time the world opens up, many players have already formed the impression that the game is slow and restrictive. The tutorial didn’t just teach mechanics. It taught a false expectation about the entire experience.

Feedback Loops That Teach Without Words

The most powerful tutorial tool isn’t text or voiceover. It’s feedback. When a game responds to your actions with clear, immediate consequences, you learn faster than any explanation could achieve. Celeste is a brutal platformer that kills you hundreds of times per level. But respawn is instant. The death animation is quick. The screen resets before frustration can build. This rapid feedback loop turns every death into a data point. You learn the dash distance, the wall-jump timing, the crystal heart mechanics—all through trial, error, and instant retry. The game never says “Hold jump longer for more height.” You figure it out because the alternative is falling into spikes for the fortieth time.

Contrast this with Assassin’s Creed tutorials, which often pause the action to display a control diagram. The feedback is delayed, the lesson abstract. By the time you’re allowed to try the move, the context has shifted and the instruction is half-forgotten. The series has improved over time—Valhalla integrates tutorials more naturally into early raids—but the legacy of intrusive hand-holding still lingers in player expectations.

When the Tutorial Is the Hook

Some games don’t just teach you how to play. They use the tutorial to sell you on the entire premise. What Remains of Edith Finch opens with a walk through a forest, then a house, then a series of rooms each containing a story. The tutorial is simply “look at this” and “interact with that.” But each interaction reveals a narrative fragment so compelling that you forget you’re learning controls. By the time you reach the first full story—Molly’s transformation from girl to cat to owl to shark—you’re fully invested. The tutorial didn’t just teach mechanics. It established tone, stakes, and emotional vocabulary.

This is tutorial design as seduction. The game doesn’t demand your attention. It earns it, one curiosity at a time. Outer Wilds operates similarly. You wake up, walk around a village, talk to people, play hide-and-seek, and test a model spaceship. Every interaction teaches a system—gravity, signalscope, jetpack, ship controls—but feels like exploration. By the time you launch for the first time, you’re not thinking about button mappings. You’re thinking about the mystery of the Nomai. The tutorial has already made you care.

Accessibility Is Not a Tutorial Shortcut

A dangerous trend in modern game design is conflating accessibility options with tutorial quality. Adding a “skip tutorial” button, offering difficulty modes, or providing text-to-speech for tooltips doesn’t fix a fundamentally broken onboarding experience. These are accommodations, not solutions. A well-designed tutorial should make the game accessible to its target audience without requiring them to opt into a separate learning track. The Last of Us Part II offers an extraordinary suite of accessibility features—over sixty options—but its tutorial design is also strong on its own merits. The opening Jackson chapter teaches stealth, crafting, and combat through natural scenarios that escalate in complexity. The accessibility features enhance that foundation. They don’t replace it.

When a game relies on accessibility options to compensate for poor tutorial design, it’s admitting defeat. It’s saying, “We couldn’t figure out how to teach this, so here’s a menu that might help.” That’s not inclusivity. That’s a design failure with a settings bandage.

FAQ: Tutorial Design Questions Worth Asking

Why do some games force unskippable tutorials?

Often, it’s a lack of confidence in the game’s ability to teach through play. Developers fear that if players skip the tutorial, they’ll bounce off the game and leave negative reviews. The irony is that unskippable tutorials cause exactly that outcome for experienced players. Pokémon Sun and Moon is the poster child here—its tutorial is so long and restrictive that it actively drives away the series’ most loyal fans. A better approach is Dark Souls‘ method: make the tutorial optional but embedded in the world, so players who need it find it naturally, and players who don’t can sprint past it.

What’s the difference between a tutorial and a learning curve?

A tutorial is a designed sequence of lessons. A learning curve is the player’s subjective experience of gaining competence. Great tutorials flatten the learning curve without eliminating it—they make the climb feel like gameplay, not homework. Hades has a steep learning curve; you’ll die dozens of times before your first clear. But the tutorial is so well-integrated into the death loop that you never feel like you’re in a separate “learning phase.” You’re just playing, improving, and unlocking story with every attempt.

Can a game have no tutorial and still be great?

Absolutely. Minecraft launched without any tutorial whatsoever, and it became the best-selling game of all time. But “no tutorial” is a design choice with consequences. Minecraft‘s opacity forced players to collaborate, share knowledge, and build a community around discovery. That worked because the game’s core loop—punch tree, craft tools, build shelter—is intuitive once you stumble into it. For a game with more complex systems, “no tutorial” can be disastrous. The key is matching the tutorial approach to the complexity of the mechanics and the expectations of the audience.

The Tutorial as a Promise

Ultimately, a tutorial is a promise. It says, “This is what the game will ask of you. This is how it will treat you. This is the kind of fun you’re going to have.” When that promise is broken—when the tutorial is tedious but the game is thrilling, or when the tutorial is exciting but the game is shallow—players feel betrayed. Great tutorials don’t just teach mechanics. They establish a relationship. They set the tone for every hour that follows.

Portal promised a game that respected my intelligence. Breath of the Wild promised a world that rewarded curiosity. Dark Souls promised a challenge that was fair but unforgiving. Each of those promises was kept, and each of those games is remembered not just for what they were, but for how they began. The first ten minutes might fade from memory. But the feeling of being taught well—or being taught poorly—lasts forever.