The difficulty debate in games is largely stuck because everyone is arguing about a single number that doesn't exist. You don't lower difficulty — you lower some specific kind of challenge. And the players who struggle with one kind rarely struggle with the same ones as the players two comments below them.
This matters because we're now well into the era of robust accessibility options. Games ship with dozens of toggles affecting everything from enemy aggression to time dilation. And yet the arguments about whether easy modes belong persist, mostly because the framing hasn't caught up. We're still talking about one dial.
The six axes (and why they're distinct)
Reaction speed demand. Pattern recognition. Resource management under pressure. Spatial reasoning. Information density. Execution precision. These are meaningfully different skills that map to different parts of a player's experience.
A game that's demanding on reaction speed isn't automatically demanding on pattern recognition. A game with high information density isn't necessarily mechanically precise. The classic "hard games" tend to be high on two or three axes simultaneously, which is what makes them feel coherent — the challenge is layered and integrated, not just turned up globally.
Reaction speed demand is the most obvious and the least interesting. It's also the one that gets scaled most crudely — slow enemies down, extend parry windows, add invincibility frames. These are fine as accommodations but they don't describe the whole challenge space of a game.
Pattern recognition and what players are actually learning
Pattern recognition is where most combat design actually lives. Learning a boss isn't about reacting faster — it's about building a mental model of what the boss will do when, and from which positions, and what those animations predict. The reaction speed comes later, after the pattern is learned. Before that, you're not really playing the boss, you're reading it.
This is why "just memorise the patterns" is both true and misleading. Yes, that's the mechanism. But memorisation requires repeated exposure to readable signal. When a pattern is obscured — ambiguous animation, randomised timings, too much happening visually — the player can't build the model because the game isn't giving them clean signal to work from.
Difficulty on this axis isn't about increasing the number of patterns. It's about how clear the patterns are to read, and how much overlap there is between them. A boss with twelve distinct attacks, each telegraphed clearly, can be easier to learn than a boss with four attacks that share similar windups.
Resource management as its own layer
Resource management is interesting because it operates on a longer timescale than the other axes. It's the challenge of the session rather than the moment. How do I allocate healing items across this dungeon? When do I spend mana and when do I conserve it? Is this fight worth the attrition or should I find a way around it?
Games that are hard on this axis while easy on reaction speed can still produce meaningful challenge — and a meaningfully different experience than games where the inverse is true. But difficulty sliders almost never address this axis. You can lower enemy health and still run out of ammunition in a survival horror game. The adjustment is at the wrong scale.
Execution precision and the feel of failure
Execution precision is the tightest axis and the one most easily confused with skill. It describes how small the margin for correct action is — not how hard it is to know what to do, but how hard it is to do it cleanly.
High execution demand produces a specific kind of failure: you knew what to do, you attempted it, your execution was slightly off. This is satisfying to overcome when the skill is on a short learning curve and the attempt cycle is fast. It's frustrating when the attempt cycle is long and the failure is ambiguous — you're not sure if you executed badly or if the pattern is more complex than you thought.
The best high-execution games either have very fast retry loops or telegraph clearly which kind of failure you just experienced. Both approaches respect the player's time in different ways.
Information density: when more is harder
Strategy games and complex RPGs are demanding primarily on this axis. The challenge isn't whether you can execute — it's whether you can track enough information simultaneously to make good decisions. Build orders, unit counters, cooldown timings, economy management — these all live in working memory, which has a finite capacity that varies between players more than reaction speed does.
This is an axis that almost nobody accounts for in accessibility options. You can add better UI, better tutorialisation, better ability descriptions. But the fundamental challenge of holding a complex state in your head and updating it continuously doesn't have an easy toggle. You can reduce the amount of information — simplify the systems — but that changes the game rather than accommodating different players within it.
What this means for the "should games have easy modes" conversation
The argument against difficulty options — that they dilute the intended experience — assumes there's a unified intended experience. There isn't. A player who struggles with reaction speed and a player who struggles with execution precision are having different problems with the same game. An accessibility option that addresses one might not address the other at all.
The argument for difficulty options — that accessibility expands the audience without affecting other players' experience — is true but also too simple. Some games are structurally about a specific challenge axis. A game built around pattern recognition at high execution precision is a different design object than the same game with pattern timings slowed and execution windows widened. The question isn't whether options should exist — clearly they should — but whether they're changing something cosmetic or something fundamental.
Designers who actually want to address this build games that separate the axes where possible. The intention isn't always to make things easier, it's to let players choose which challenge they want to engage with. That's a different design goal, and a harder one, than simply adding a difficulty slider.