The Problem With Game Reviews That Spend More Time on Graphics Than Mechanics

There’s a quiet tragedy unfolding in game criticism. You click on a review expecting a deep look at how a game plays, but instead you get three paragraphs on the shimmer of light through a stained-glass window, the pore density on a protagonist’s nose, and the way shadows dance across a wet cobblestone street. The mechanics—the actual verbs of the game—get a sentence or two, often reduced to “the combat feels responsive” or “the controls are tight.” It’s a pattern that treats games as art galleries first and interactive systems second, and it’s doing a disservice to players and developers alike.

I’m Rin Kowalski, and I spend most of my gaming hours in the laboratory of indie design. That’s where mechanics are born, tested, and sometimes broken in fascinating ways. When a review glosses over those systems to wax poetic about how the pixel-art sunset references 16-bit nostalgia, I feel a spike of frustration. Graphics are the skin; mechanics are the skeleton and muscle. A review that ignores the skeleton is telling you how the corpse looks, not how it moved when it was alive.

”

When Visuals Become a Crutch for Shallow Criticism

Part of the problem is that graphics are easy to talk about. A screenshot is static, shareable, and instantly legible. You can point to the volumetric fog and say, “Look, it’s beautiful,” and nobody will argue. Describing a mechanic takes more work. You have to explain how a dash-cancel interacts with enemy telegraphs, or why the inventory tetris in a roguelike creates friction that makes every decision feel heavy. That requires playing the game with analytical intent, not just letting the spectacle wash over you.

I’ve read reviews for big-budget action games that burn 40% of the word count on ray-traced reflections and maybe 10% on the actual move sets. The result is a review that tells me if the game is pretty, but not if the dodge roll has invincibility frames that feel generous or stingy, or if the skill tree actually changes how I approach encounters. That’s the stuff that decides whether I’ll still be playing after the initial visual wow fades.

Indie Games Expose the Flaw

Indie games are where this imbalance becomes painfully obvious. Take a game like Rain World. It’s not a graphical powerhouse by conventional standards—its pixel art is evocative but deliberately murky and oppressive. Yet the mechanics are a masterclass in systemic ecology. The way predators learn your hiding spots, the procedural animation that makes every movement feel precarious, the rain timer that turns the entire world into a drowning clock—these are the things that make the game unforgettable. A review that lingers on the “grimy pixel aesthetic” without unpacking the simulation underneath hasn’t actually reviewed the game; it’s reviewed a slideshow of the game.

I see this pattern again and again in coverage of experimental indie titles. A game like Baba Is You gets praised for its “charming” visuals, but the real story is how it treats game rules as manipulable objects. That’s a radical design idea, yet many reviews treat it as a cute puzzler with a clever hook, completely missing how the mechanic rewires the player’s relationship to logic itself. When graphics dominate the conversation, mechanical innovation gets flattened into a novelty.

The Rise of the Tech-Demo Review

There’s a particular genre of review I’ve come to dread: the tech-demo review. It evaluates a game primarily as a benchmark for hardware. You’ll see sentences like “This is the new Crysis” or “Your GPU will weep.” These reviews measure frames per second, texture detail, and draw distance, but they often fail to ask whether the game underneath all that visual grunt is actually interesting to play. A game can be a technical marvel and still be mechanically hollow—a corridor of scripted set-pieces where the player’s input barely matters.

The tech-demo review feeds a cycle where graphical fidelity becomes the main yardstick for a game’s worth, and studios respond by pouring resources into visuals at the expense of systems. We end up with games that look incredible in trailers but feel like interactive museum exhibits. The reviewer’s job should be to puncture that illusion, not reinforce it.

What a Mechanics-Focused Review Looks Like

A good review treats mechanics as the primary text. It asks: What are the player’s verbs? How do they chain together? Where is the friction, and is that friction intentional or the result of sloppy implementation? Does the game teach its systems through level design or through pop-up tutorials? How do the mechanics create emotional states—tension, flow, frustration, discovery?

In a fighting game, for instance, I want to know about frame data, not just how shiny the character models are. Does the combo system favor links or cancels? How punishing is the recovery on a blocked heavy attack? These details tell me if the game rewards reactive play or memorized sequences, which in turn tells me if I’ll enjoy it. A review that skips this for a paragraph about how the sweat on the fighter’s brow is rendered in 4K has failed me as a reader.

When Visuals and Mechanics Work Together

I’m not arguing that graphics don’t matter. They matter enormously. A game’s visual language can clarify mechanics: a red flash on a parryable attack, a subtle color shift to indicate a status effect, the way an enemy’s silhouette telegraphs its next move. The problem arises when the review treats the visual layer as the main course rather than the plate the meal sits on.

Consider Hades. Its art style is gorgeous, but the best reviews of that game focused on how the boon system creates run-time build decisions, how the dash-strike rhythm feels in your fingers, and how the narrative progression is tied to death—a mechanic that turns failure into forward momentum. The visuals were discussed as part of that cohesive whole, not as a standalone selling point.

The Consequences for Players and Developers

When reviews prioritize graphics over mechanics, players make uninformed purchases. They buy a game that looks stunning in screenshots, only to find that the core loop is repetitive or the controls are mushy. That leads to refunds, negative user reviews, and a general erosion of trust in game criticism.

For developers, the signal is equally damaging. If a studio sees that its game received high scores primarily because of its visual fidelity, it’s incentivized to invest even more in art and less in systems design. This is especially dangerous for indie teams with limited resources. I’ve spoken to developers who felt pressure to polish their game’s look to the detriment of mechanical depth, because they knew reviewers would fixate on the first and skim the second.

We need a critical culture that treats games as the interactive medium they are. That means holding reviewers accountable for explaining how a game plays, not just how it looks. It means celebrating outlets and creators who do deep mechanical analysis. And it means, as readers, we should demand more than a catalog of pretty pixels.

FAQ

Why do so many game reviews focus on graphics?

Graphics are immediately accessible and easy to describe. A reviewer can point to a screenshot or video clip and the audience instantly sees what they mean. Mechanics require more time to explain, and they often involve abstract concepts that are harder to convey in a short review format. Additionally, the games industry has long marketed titles based on visual spectacle, which sets an expectation that graphics are the headline feature.

Can a game with simple graphics have great mechanics?

Absolutely, and indie games are the best proof of this. Titles like Spelunky, Into the Breach, and Cave Story use modest or retro visuals, yet their mechanics are so finely tuned that players sink hundreds of hours into them. In these games, every system feeds into every other system, creating emergent complexity that has nothing to do with how many polygons are on screen.

How can I find reviewers who emphasize mechanics over graphics?

Look for critics who use specific, technical language about gameplay. They might mention frame data, input buffering, systemic interactions, or design intent. Outlets that cover indie games extensively often have writers who prioritize mechanics, because indie titles can’t rely on graphical wow-factor to stand out. Also, follow developers on social media—they frequently share and praise the kind of criticism that digs into the craft of game design.

Is it possible for a review to talk about graphics without ignoring mechanics?

Yes, and the best reviews do exactly that. They treat graphics as part of the overall design language, explaining how the visual choices support or undermine the mechanics. A good example is discussing how a game’s color palette affects enemy readability, or how animation quality impacts the feel of combat. The key is that the visual discussion is in service of understanding the play experience, not a substitute for it.