Ghosts 'n Goblins on the C64: The Difficulty as Insult

I finished Ghosts ’n Goblins once, on a friend’s Commodore borrowed for a weekend in 1988, and the game’s reward for that was to tell me I had failed. Not with a game over screen. With a cutscene, a shrug from the wizard who sent Arthur on the quest in the first place, and a instruction to do the whole thing again from the start. That is not a bug. Tokuro Fujiwara built it that way on purpose, and it is the single most honest difficulty design decision I have ever seen a game make.

Capcom’s 1985 arcade original was already a byword for cruelty by the time Elite Systems brought it to the C64 in 1986. Arthur the knight sets out across a graveyard, a village and a castle to rescue a princess, armed with a lance he can barely aim and armour that survives exactly one hit. Take a second hit in your underwear and you die outright. It is a design built entirely around the gap between what a lance-throwing knight should be able to do and what the collision detection actually permits, and the C64 conversion inherited every inch of that gap along with the zombies clawing up out of the graveyard dirt in the opening seconds, still one of the most efficient tone-setting moments 8-bit gaming ever produced.

Why the underwear is the mechanic

Strip away the joke and the armour system is doing real design work. Most action games of the era gave you a health bar or a handful of extra lives and left the moment-to-moment stakes vague. Arthur gives you exactly two states, and both are visible on the sprite. Armoured, you can absorb one careless mistake. Unarmoured, in your shorts, you cannot absorb any. The game is constantly showing you your own margin for error, which means every single hit is legible information rather than an abstract number ticking down somewhere off to the side.

That legibility is what makes the difficulty feel earned rather than arbitrary, at least up to a point. You always know exactly why you died: that plant span up half a second before you expected, the flying red devil clipped your dive, the ogre’s projectile arced further than the last one did. The trajectory maths behind Arthur’s lance is unforgiving and it never lies to you about the shape of the danger. This is the same discipline Dropzone applied to an Atari 800 years earlier — punishing, but never opaque about why.

The second loop, and the actual cruelty

The underwear is a joke. The two-loop requirement is the insult, and it is the thing that made Ghosts ’n Goblins into shorthand for unfair game design for the next three decades.

Fight your way to the end of the game once — genuinely difficult, genuinely a full evening’s work on a home conversion running at a slightly reduced frame rate compared to the arcade board — and you reach the final confrontation, defeat it, and get told that the item you carried through the whole adventure was a trick, and the real quest starts now. The game sends you back to stage one. Same enemies, same layouts, a second full run, at the end of which a different weapon is required to beat the real final boss and see the actual ending.

There is no way to know this on a first attempt. No hint, no clue placed anywhere in the six-hour experience that precedes it. You beat the game and the game’s response is that you have not, in fact, beaten it, and would you like to do all of that again please. It is the single most quoted example, in later decades of retrospective writing about game difficulty, of a design treating the player’s accomplishment with open contempt.

And yet the joke lands rather than just wounding, because Fujiwara had already spent the entire first loop training you to expect exactly this kind of trick. The game telegraphs its own unfairness continuously — a plant that looks harmless spits fire, a suit of armour standing in a corridor turns out to be a monster, a coffin lid opens on the wrong beat. By the time you reach the fake ending you have been conditioned to distrust every single thing the game shows you, so the ultimate trick, played on the game’s own credits sequence, is consistent with everything that came before it rather than a cheap twist bolted on at the end.

What the C64 conversion actually changed

Elite’s port did not, and could not, replicate Capcom’s arcade hardware cycle for cycle, and the differences matter to how the game reads today. The scrolling is coarser, the sprite count during the busiest screens drops, and the parallax that gave the arcade background depth is largely gone. What survived, and survived well, is the animation grammar Arthur runs on and the sound design underneath it — the specific, unmistakable clank of the lance, the crumple when a hit lands.

That the atmosphere carried across a hardware downgrade this steep says something about how the original was built: the horror-comedy tone of Ghosts ’n Goblins lives in its animation timing and its sound cues far more than in raw pixel fidelity, which is exactly why a battered tape-loaded conversion still reads as the same game rather than a diminished cousin of it.

The escalation across a single loop

What the difficulty conversation usually skips is how carefully the six stages are sequenced within a single loop, before the two-loop trick even becomes relevant. The graveyard opener teaches vertical threat — zombies rising from below, bats diving from above — with almost nothing else on screen, a genuine tutorial disguised as an atmospheric cold open. The village stretches that same vertical vocabulary sideways into moving platforms and collapsing walkways. By the time Arthur reaches the castle interior, the game is combining every threat type it has taught in isolation, stacked into corridors barely wider than his sprite.

That escalation is why the game survives being replayed today in a way that a lot of its contemporaries do not. Nothing new is ever introduced without at least one screen of isolated practice first, which means a modern player dying repeatedly to the castle’s combined threats is dying to a failure of their own pattern recognition rather than to a rule the game never explained. The cruelty sits entirely in the execution demanded of you, never in withheld information about what is coming, a distinction that gets lost in the game’s reputation as simply unfair, when the truth is closer to unforgiving of imprecision.

The weapon upgrades reinforce the same idea rather than undercutting it. The dagger throws faster but hits softer; the torch arcs and burns through certain enemy types the lance cannot; the axe drops in a parabola that suits the game’s frequent vertical threats. None of them is strictly better than the lance, which means the player is making a real trade-off every time a weapon capsule appears rather than simply collecting an upgrade and forgetting about it. Losing your preferred weapon to a stray hit is its own small tragedy layered on top of losing the armour, and the game never lets you forget that both systems are ticking at once.

Why the design still lands

Every difficulty conversation in modern games eventually returns to a version of this same question: does punishing the player for something count as fair, if the game was honest about the rule beforehand? Difficulty is a design choice, not a moral one, and Ghosts ’n Goblins is one of the cleanest test cases for that argument, because it commits to the bit so completely that the cruelty becomes the entire authorial voice rather than an accident of bad balancing.

The two-loop trick specifically is a variation on a structure the industry would later formalise and, in places, soften into something more forgiving — the loop is the argument that roguelikes actually make, where repetition itself becomes the content rather than a punishment for failing to escape it. Ghosts ’n Goblins got there first and refused to be gentle about it: there is no meta-progression carried between loops, no permanent upgrade earned from the first failed attempt. You simply do the same brutal six-hour lesson twice, and the game considers that a fair price for its ending.

The case against it

None of this excuses the parts that were simply broken rather than deliberately cruel. Certain enemy patterns in the busier stages spawn faster than the C64’s sprite-multiplexing can comfortably track, producing flicker and the odd genuinely unreadable frame where a hit arrives from an angle you had no way to see coming. That is not design; that is hardware strain, and pretending otherwise does the game no favours. A modern replay also exposes how thin the input vocabulary is — jump, throw, duck, and nothing else, for the entire six-stage, two-loop runtime. The joke of the armour system carries an enormous amount of that weight because there is so little else happening mechanically to vary the experience.

The lance’s fixed trajectory, too, ages worse than the enemy design around it. Later Capcom platformers gave the player aiming options; Arthur throws in one of two directions and that is the full extent of his offence, which flattens a lot of encounters into a memorisation exercise once the surprise has worn off.

Spoilers below

The item that unlocks the true ending on the second loop is the Golden Armour, occasionally sourced from a specific bonus round or from a hidden treasure chest depending on the version, worn instead of the standard steel set. Wearing it into the final confrontation with the demon lord Lucifer/Satan grants a charged shot capable of actually damaging him; without it, the same fight is unwinnable by design and simply loops the player back to the start of loop two indefinitely. The “true” ending reveals the princess’s rescue was engineered by the demon lord all along as a trap for Arthur, a twist that recontextualises every earlier cutscene as a lie the game was telling you in plain sight, consistent with everything else it had already taught you not to trust.