The boss has killed you eight times. You know the move now—there's a window on the left side, half a second, and if your thumb is in the right place you can get through it. Your brain knows it. Your hands don't, yet.
Thirty years ago, you put the controller down. You got up, walked somewhere, came back. The problem waited for you exactly where you left it. Eventually—maybe that session, maybe the next day—your hands caught up to what your brain already knew. That moment, when they finally did, had a specific feeling.
Now you open the menu.
There are hundreds of options. Damage multipliers, checkpoint frequencies, enemy aggression levels. You find the one that fits the problem and you turn it on. The boss dies on the next attempt. The game moves forward.
You moved on. You didn't progress.
"It's your game. Do whatever you want with it."
That's what the developers of Mina the Hollower told players about their options menu—hundreds of modifiers covering speed, difficulty, damage, resource scarcity, and stranger things besides. Players called it generous. Critics called it thoughtful. The word that surfaced most often, offered as the highest compliment anyone had: accommodating.
Accommodating. The word we reach for when a hotel upgrades your room without being asked, when a host moves dinner back an hour because you're running late, when a service bends its standard terms because your situation is a little unusual. It describes the posture of something that has set aside its own requirements to meet yours.
That's the word we're now reaching for to praise a creative work.
When Friction Became a Failure to Accommodate
Subtitles made games available to players who are deaf or hard of hearing. Colorblind modes made color-coded systems legible to players they would otherwise exclude. Remappable controls meant that someone with a motor disability could play a game designed for a standard grip. These weren't concessions to softness. They were designers recognizing that their default assumptions were exactly that—defaults, built around a particular body, a particular set of senses—and correcting for it. The work that got done here was real.
But something came with it. A template, and a vocabulary.
The template: if something prevents a player from engaging with a work, that's a problem to be solved. When the barrier was sensory or physical, the template was coherent. Access meant: here is the experience, let us remove what's standing between you and it unnecessarily. The work had a form. The goal was to get more people inside it.
The template didn't stay there.
Difficulty became legible as a barrier. Not a design choice—a barrier. The hard section wasn't hard because the designer decided it should be hard; it was hard because something had failed to accommodate the player attempting it. Pacing became a barrier. A slow opening, a deliberate withholding of reward, a movement system that took hours to master—these stopped reading as authored decisions and started reading as UX failures waiting to be fixed.
Nobody announced this expansion. It happened through the accumulated weight of a vocabulary that had done real work in one domain being extended, without examination, into another. And with the vocabulary came the moral weight. The people who had advocated genuinely and correctly for sensory accessibility had won. Their framing had won with them. To push back on any friction was now to push back against access—and almost no one was willing to be the person doing that.
Defending difficulty came to read as defending exclusion.
What Difficulty Was Always Saying
A difficult game isn't just a game with obstacles. It's a game with a position.
Positions have edges—an inside and an outside. A work with a position is one that knows what it is, which means it also knows what it isn't. It commits. And in committing, it tells you something: this is the experience. Not every player will meet this work where it is. That's not an oversight.
This is what it means for a work to refuse someone. Not hostility—indifference to the accusation that its form might inconvenience you. A difficult game that won't accommodate isn't saying you're not good enough. It's saying: this is what the experience costs, and the price isn't negotiable.
But there's something more specific happening inside the refusal.
When a game is genuinely hard—when the boss has been killing you for an hour, when the movement system won't click, when the timing feels impossible—the game is making a claim about you. Not explicitly. Nothing is said. But the claim is there in the structure: I think you can do this. The difficulty isn't arbitrary cruelty. It's a posture. The work is addressed to someone capable of meeting it, and it's waiting to find out if you're that person.
That's a relationship. A strange one, between a player and a designed system, but a relationship with real stakes on both sides. The work has a view of you. You're either going to prove it right or you're not.
This is what makes the victory mean something. Not just completion—confirmation. The game thought something of you, and you answered. The difficulty wasn't incidental to the experience; it was the condition under which the experience became meaningful.
Now consider what happens when the difficulty is optional.
A game that lets you take 0.5x damage, reduce enemy aggression, add checkpoints wherever you want, and slow the world to 98% of its original speed doesn't think anything of you. It can't. It has no position from which to make a claim. It asked what you wanted, you configured it, and now you're both inhabiting something that fits your specifications rather than its own.
The relationship is gone. Not made easier. Gone.
No View on What You're Capable Of
The options menu looks like generosity. Hundreds of modifiers, pre-selected accessibility bundles, the ability to tune every parameter of your experience—this reads as a designer who cares about their players, who wants everyone to be able to engage with what they made.
Every slider moved, every modifier enabled, is the game stepping back from a claim it was making. Reduce the damage and the game stops saying this is what survival costs here. Add the checkpoint and the game stops saying I think you can get through this without one. Slow the world and the game stops saying this pace is the pace. By the time you've configured the experience to your specifications, the game has vacated every position it held.
This is different from a cheat code. A cheat code circumvents the game's position—goes around the back of a structure that's still standing. The acknowledgment is built into the act: to use one is to step outside an experience that still exists as a reference point, that still has a claim on you which you've chosen not to meet. The game doesn't revise its view of what you're capable of. You just opted out.
The options menu doesn't circumvent anything. The designer steps to the front of the experience—before it begins, as part of its official presentation—and makes a different announcement: we have no opinion on what this should cost you. Every configuration is equally legitimate. What the cheat code user did in secret, outside the intended experience, the options menu does officially, before any experience has been declared as intended. Not a back door. No front door. Just parameters waiting for your preferences.
"It's your game." That's not a generous announcement. It's a precise one. The designer is telling you accurately what has happened: the authorship has been transferred. The work's position—its claims, its form, its implicit address to someone capable of meeting it—has been replaced by your preferences. The designer stepped back, and something stepped back with them.
We called this accommodating. We praised it as the highest virtue a game could offer.
Accommodation means the accommodating party has set aside their own requirements. They've met you where you are. This is exactly what a good hotel does, and it's genuinely valuable—in that context. The hotel's job is your comfort. The host's job is your ease. A creative work's job is different.
Or it was.
Every position a work holds is a claim it could be wrong about. The difficulty might genuinely exceed you. The experience might not be for you. A work that stands somewhere has no mechanism for apology.
That's what we decided to fix.
Now the game has no view on what you're capable of. It won't ask more than you'll give, because it asked first. It meets you exactly where you are and stays there.
It will never be wrong about you.
It has nothing to be wrong about.