Published:
Summary
Ghosts 'n Goblins (1985) gleefully armed Sir Arthur, knocked his armour off within seconds, and then kept kicking him while he was already down. Set in a nightmarish fantasy world of zombies, demons, and fire-breathing horrors, it demanded pixel-perfect jumps and saint-like patience. Weapons felt unreliable, enemies respawned relentlessly, and the game took obvious pleasure in your suffering. Yet beneath the cruelty lay tight controls, striking visuals, and unforgettable atmosphere. It was punishing, unfair, and utterly addictive - a rite of passage disguised as a platformer.
What it does well
Iconic presentation, tight controls, memorable enemies, superb atmosphere, and a challenge that felt strangely irresistible.
Where it falls short
Extreme difficulty, constant enemy respawns, unreliable weapons, and frustration levels that bordered on sadistic.
Verdict
A legendary arcade tormentor that balanced exquisite design with merciless difficulty, creating one of gaming's most infamous challenges.
Ghosts 'n Goblins - version notes
Version-specific observations from the gameplay video. Tap a time to jump straight to that moment.
Amiga (4 Beats)
- Expectation gap: UK magazines approached the Amiga version expecting a definitive home conversion, not just a competent one.
- Praise: reviews consistently admired accuracy and difficulty, but often added caveats about speed and fluidity.
- Audio restraint noted: sound was rarely criticised outright, but often described as functional rather than exciting.
- Historical positioning: over time, the Amiga version came to be seen as faithful but unforgiving.
Amstrad (3 Beats)
- Infinite trap: enemies respawn instantly in the exact same locations with no cooldown, turning progression into a timing bottleneck.
- Armour bug: on CPC, Arthur cannot lose armour - the game kills you on the first hit, making it harsher than the intended ruleset.
- Design consequence: with no armour buffer, the game stops being about controlled damage and becomes pure no-mistakes execution.
Arcade (3 Beats)
- Spawn pressure by design: enemies are tied to screen regions, not kill counts, ensuring pressure resumes until the player advances.
- Armour buffer: Arthur's armour loss is a teaching tool, allowing one mistake while enforcing immediate behavioural correction.
- Design thesis: the game teaches that forward momentum is survival - stalling increases danger.
Atari ST (3 Beats)
- Awkward middle ground: the ST version sits uncomfortably between 8-bit restraint and 16-bit expectation, shaping how it was judged.
- Enemy pressure intact: core enemy patterns and aggression remain recognisable, preserving the arcade's forward-momentum demand.
- CPU-driven reality: without hardware sprites or a blitter, all animation and scrolling are CPU-handled.
Commodore 64 (3 Beats)
- Pacing via density: fewer simultaneous sprites than the arcade, but lethality is unchanged - difficulty is thinned, not softened.
- Fixed-arc commitment: Arthur's jump physics mirror the arcade closely, keeping timing decisions irreversible once airborne.
- Reception context: UK press often cited the C64 version as one of the stronger home conversions, praised for feel over flash.
NES (3 Beats)
- Input precision shift: the NES controller's tighter D-pad makes micro-positioning more reliable than on many home micros.
- Sprite density advantage: hardware sprites allow smoother enemy animation without increasing lethality.
- Audio reinforcement: music and effects are clearer and more consistent.
Spectrum (3 Beats)
- Monochrome pressure: the lack of colour forces enemies, projectiles, and terrain to be read purely by silhouette and motion.
- Reception reality: contemporary press often framed it as playable but punishing, noting difficulty over presentation.
- Audio minimalism: beeper sound effects are functional rather than dramatic.