Week 1: Welcome to the masochism club
Why players choose punishment their wallet would refuse, and how to tell a punishing design from a cheating one before the semester needs the distinction
22 February 2027
Punishing and cheating difficulty can look identical on a death counter. The test that tells them apart — full argument in Punishing difficulty vs. cheating difficulty — is whether the player, the instant after dying, has a specific and legible reason to believe the next attempt can win. Every later week studies one mechanism a Souls-like uses to keep that reason legible: death’s narrative framing, a level’s shape, an attack’s grammar, a boss’s staging.
The argument#
Sekiro’s Lady Butterfly is this course’s reference case for a reason: her double-jump into a dive attack telegraphs for long enough to deflect or dodge on the first honest attempt, and the lesson it teaches — watch the altitude, not the sword — survives being learned once. Set that against the pattern most “cheap” encounters share: an ambush sprung the instant a fog gate closes, three weapons already swinging before the room has told the player it exists. Both can produce an identical death counter. Only one gives the player a specific decision to point at afterward.
The boundary isn’t always this clean, and the genre’s own patch history shows the work of finding it. Elden Ring’s Malenia shipped with a Waterfowl Dance whose dodge window was, by most players’ account, tighter than its telegraph justified — punishing in intent, cheating in practice, until a balance patch widened the window without touching the animation. The fix didn’t make the attack much easier to survive; it made it survivable by reading it, which is the only axis this course grades on. The opposite failure is more common and less interesting: a boss that is simply the previous boss’s health bar tripled, no new tell, no new pattern — the shape this course calls the damage sponge, and the first thing every later week’s workshop is built to avoid producing by accident.
Outline#
- why “difficulty” undersells what the genre is actually doing
- the test: legible failure versus arbitrary failure, not damage numbers
- Lady Butterfly’s dive versus a fog-gate ambush, side by side
- Malenia’s Waterfowl Dance as a case the genre itself had to re-tune, not a settled example
- the damage-sponge failure mode: more health and more damage without a new tell
- why this test has to survive being applied to your own workshop artefacts, not just to games you already admire
- how this semester’s workshops each produce an artefact, not just an essay about one
Into the session#
Today’s session runs the test cold, before any later week supplies vocabulary for it: play or watch one attempt-and-death cycle against a widely agreed punishing case and one you’d call cheap, and log the exact moment each one either earned back your trust or lost it. The log you build today is the same instrument every later workshop hands you a new subsystem to run it against.
Teaching team
- Marisol Quaye — convenor