Progressive Difficulty:
Why Old Games Were So Hard

Try to explain modern gaming to someone who only played '80s arcade games: unlimited lives, checkpoints every two minutes, difficulty settings, hints when you're stuck. Their reaction would probably be somewhere between bewilderment and mild contempt.

Now try the reverse. The three-life Game Over screen. No save points. Start over. The full difficulty curve of the early levels again, just to reach the point where you died last time. The modern reaction is equally predictable: frustration, abandonment, a one-star review.

Both reactions are wrong. Here's why.

Why They Were So Hard - Really

Honest answer: for more than one reason, and not all the expected ones. The difficulty of '80s games wasn't uniform or random - it had precise and distinct causes depending on the context in which the game lived.

Arcade games were hard for an economic reason: a cabinet earned every time a player inserted a coin. A too-easy game got finished in twenty minutes, saturated the player, and the cabinet sat idle. A game calibrated to end the average player's session in three-to-five minutes guaranteed a constant flow of coins. Difficulty was literally the business model.

Console games were hard for a technical reason: in NES and Atari games, memory was measured in kilobytes. No room to save, no selectable difficulty levels, no explicit tutorials. The game needed to be long enough to justify the price - and without save states, the only way to extend product life was to raise difficulty. Dying and starting over was the content.

There was also no shared language for tutorials yet. The vocabulary was developed in subsequent decades. Nintendo pioneered with Super Mario Bros. (1985): the first level is still considered the perfect tutorial without a single word of text - the pipe, the question blocks, the Goomba at the right distance all teach through play. But that was the exception, not the norm.

The Arcade Model: Difficulty as Monetization

An arcade hall owner paid thousands of dollars for each cabinet. ROI depended entirely on how many coins went in. Namco, Taito and Konami designers worked with a precise goal: the average player's session needed to last long enough to seem fair, but end fast enough to push them to reinsert the coin.

This created a mathematics of game design we now call the difficulty curve.

Crucial point: arcade difficulty wasn't designed to be overcome by everyone. It was designed to create a visible skill hierarchy: the kid who reached level 10 while others reached 3 was a public spectacle. They attracted a crowd. The crowd watched, wanted to emulate, inserted coins. Extraordinary skill was free advertising for the cabinet - and difficulty design made it rare and therefore visible.

"We wanted players to say 'one more time'. If the game was too easy, it ended. If too hard, they gave up. The sweet spot was in between: hard enough to make you want to try again."

- Masanobu Endo, designer of Xevious (Namco, 1982)

The Difficulty Curve: From Breathing Room to Suffocation

The best '80s games had a precise difficulty curve, even if designers of the time didn't have this vocabulary to describe it. The structure was almost always the same:

• Level 1 - breathing room: accessible, simple enough to understand mechanics, satisfying enough to build confidence. The player learns without knowing they're learning.
• Levels 2–4 - gradual escalation: enemies move faster, arrive in more complex patterns, space decreases. Skills from Level 1 are tested and extended.
• Level 5+ - the wall: difficulty stops being gradual, rises vertically. Patterns that worked no longer work. The player must relearn almost from scratch, integrating the new challenge with existing skills.

The kill screen: many arcade games had no ending - they increased difficulty infinitely until making the game physically impossible. Space Invaders accelerated the aliens. Donkey Kong raised barrel speed. Pac-Man broke at level 256. The "ending" was death - not victory. The game's implicit message was always: you will lose eventually. The only question is how far you get.

This structure was functional: the average player hit the wall around levels 4–6, stopped there, and came back the following week to overcome it. The game was engineered to create return visits.

No Saves, No Tutorials: Learning by Dying

Total Game Over - starting from the beginning with no saved progress - is the characteristic that most divides modern players from 8-bit veterans. Yet it had a profound logic.

Without saves, progress in the game was entirely muscle and cognitive memory. Not data on disk that remembered where you were - your brain remembered the level 3 patterns, the move sequence to beat the boss, the exact point to jump. This created intense and lasting learning. Every run taught something new because you had to face from the beginning all the sections already passed - often finding mistakes you'd corrected only by luck, not competence.

Game Over wasn't a punishment: it was an educational reset.

The absence of explicit tutorials worked the same way. Games were designed to be legible through failure: you died, understood why, corrected. No text explaining "press A to jump" - you discovered it by jumping and getting it wrong. This type of learning is slower and more frustrating on the surface, but produces a deeper and more lasting understanding of the system.

Modern games with explicit tutorials risk the opposite paradox: the player follows instructions without truly understanding why things work a certain way. The tutorial done, they're alone - and the system isn't internalized, only executed.

The Flow State: Where Difficulty and Skill Meet

Psychologist Mihály Csíkszentmihályi described in the '90s the concept of flow: an optimal concentration state where task difficulty perfectly matches the executor's skill. Neither too easy (boredom) nor too difficult (anxiety) - right at the limit of what you can do.

'80s arcade designers didn't know Csíkszentmihályi, but were empirically working on the same principle. The difficulty curve was built to keep the player in the flow zone as long as possible.

Flow state in video games has precise characteristics anyone who has played intensely will recognize:

• Loss of time perception - "How is it already 3am?"
• Automatic actions without conscious thought - your thumb avoids the bullet before you've "decided" to avoid it. Muscle memory has taken control.
• Intrinsic satisfaction of the process - you're not playing to win. You're playing because playing is already the reward.
• Immediate frustration when flow breaks - an unjust death, input lag, an impossible pattern. Flow breaks abruptly.

The difference between a great difficult game and a simply frustrating game: the great difficult game breaks flow because of you, not itself. You die because you made a mistake you could learn. The frustrating game kills you because of an unjust, random or poorly communicated system.

Today: Dark Souls, Roguelikes and the Return of Real Difficulty

In the 2000s and 2010s, difficulty in mainstream games had become almost a taboo. Publishers wanted to reach the widest possible audience - and difficulty excludes people. Automatic easy modes appeared, contextual help, infinite lives, checkpoints every two minutes.

Then, in 2011, Dark Souls by FromSoftware arrived. No explicit tutorial. No waypoint on the map. Quick and repeated death. No explanation of systems. And it became one of the most influential games of the decade - with a passionate and vocal player community like no other AAA title of the era.

Dark Souls wasn't a success despite its difficulty - it was a success because of it. It proved that a significant portion of players was hungry for authentic challenge, earned progression, unspoken satisfaction. The market had forgotten about them. FromSoftware had found them.

In parallel, the roguelike genre exploded in the indie scene: Spelunky, The Binding of Isaac, Hades, Dead Cells. All founded on the same arcade premise: die, restart, learn something new each run. Permadeath - definitive death that erases all progress - was no longer a technical limitation but a deliberate design choice.

What these modern games have understood from the '80s - and what the easy games of the 2000s had forgotten - is that difficulty isn't an obstacle to satisfaction: it's the source of satisfaction.

An obstacle you overcome easily gives you nothing. An obstacle that made you sweat, that you overcame after twenty attempts and a real change in your approach - that stays with you.

Try Again? - yes. Always.