Difficulty settings frequently adjust numbers when the actual barrier is something else entirely.
What difficulty is made of
Execution demand, decision complexity, information clarity and punishment for failure.
Which are independent and adjustable separately.
Numerical scaling
Increasing enemy health and damage.
Which is cheap to implement and frequently unsatisfying.
Accessibility
Options separating challenge from barriers unrelated to skill.
Difficulty and audience
Games designed around a specific challenge level as a deliberate choice.
Which is a legitimate design position.
The components people conflate
Whether an action is hard to perform, whether the right action is hard to identify, whether the game tells you what is happening, and what failure costs you.
Which are four separate dials that a single difficulty setting usually collapses into one.
A player struggling because they cannot see what killed them has a different problem from one struggling with execution, and raising or lowering enemy health addresses neither.
Failure cost
Checkpoint spacing and what is lost on death.
Which affects perceived difficulty enormously.
Difficulty curves
Introducing mechanics before combining them.
Which is the standard structure and is frequently rushed.
Accessibility options
Separating skill challenge from barriers unrelated to it.
Playtesting
Watching people who have never played.
Why the single slider is a poor tool
It usually adjusts damage numbers, which changes how long an encounter takes without changing what makes it hard.
Which frustrates players who wanted less execution pressure and got a longer version of the same fight.
Games that expose separate options for aim assistance, timing windows, resource generation and enemy aggression let players fix the thing that is actually blocking them.
Legibility
Whether the player can tell what happened and why.
Which is frequently mistaken for difficulty.
Difficulty as identity
Games where the challenge is the point.
Which is defensible and does not preclude accessibility features.
Adaptive difficulty
Systems adjusting silently to performance.
Which players dislike when they notice.
Testing
Observing new players rather than asking them.
How designers actually tune it
Watching people play, identifying where they stop, and determining whether the cause is execution, comprehension or information.
Which is observational work rather than numerical adjustment.
A designer watching ten players die at the same point learns far more from what they were trying to do than from the death count itself.
Onboarding
Teaching systems before demanding them.
Which is where a large share of players are lost.
Difficulty in multiplayer
Other players as the difficulty rather than the designer.
Which shifts the problem to matchmaking.
Assist features
Options that reduce demand without removing challenge.
Which has become more common and remains contested.
The reasonable position
More options harm nobody who does not use them.
A note on how this industry reports itself
Games is an unusually opaque business for one with such a visible product. Budgets are rarely disclosed, sales figures are announced selectively, player numbers are quoted in whichever metric flatters, and profitability is almost never stated at all.
Most of what is publicly known comes from court filings, leaked documents, regulatory submissions and former employees speaking after the fact. That material is reliable when it exists and covers a small fraction of the industry, which means any general claim about how games perform commercially rests on a limited and non-random sample.
Where the better information is
Developer conference talks are the single best public source on how games are actually made, and a large number are freely available. Regulatory filings during acquisitions have disclosed more real financial detail than a decade of press releases. Trade publications with industry sources are considerably more informative than consumer coverage on business questions.
Treat anything presented as an industry-wide figure with some caution, including in this article, and prefer sources that say where their numbers came from.
Why the business side is worth understanding
A great deal of frustration with games comes from decisions that look inexplicable from outside and are entirely predictable once the commercial structure is visible. Why a game shipped unfinished, why a beloved studio was closed after a successful release, why a sequel dropped features the previous game had, why a service shut down two years in.
None of these are mysteries. They are the outcomes of funding structures, platform economics, publisher portfolio decisions and the fact that games are made by people working to schedules set before anyone knew what the game would be.
Knowing that does not make the outcomes better. It does make them legible, and it makes it easier to tell the difference between a studio that made a mistake and one that was never given the conditions to succeed.
One thing worth remembering
Games are made by people, mostly people who care a great deal about them, working inside commercial structures they did not design and frequently cannot change.
Criticism of a game is fair. Criticism of the decisions behind it is usually aimed at the wrong floor of the building.