Superhero Video Games Codexery

Batman (1986 video game)

First Batman game; introduced isometric gameplay and early save system.

Batman (1986 video game)

İncelemeelemani · CC BY-SA 3.0

Batman, a 1986 isometric action-adventure title from Ocean Software, was the first game to feature the character. It was released for the Amstrad PCW, Amstrad CPC, ZX Spectrum, and MSX. The goal is to rescue Robin by gathering seven Batcraft hovercraft parts scattered throughout the Batcave. The game uses a 3D isometric view, a style that programmer Jon Ritman and artist Bernie Drummond would later refine for 1987's Head Over Heels. It also includes an early save system: after losing all lives, players restart from the point where Batman collected a "Batstone," rather than from the beginning. The game earned strong reviews, with Crash scoring it 93%, Your Sinclair 9/10, and Sinclair User awarding five stars and a "classic" rating.

developer
Ocean Software
platforms
Amstrad PCW, Amstrad CPC, ZX Spectrum, MSX
release_year
1986
genre
Isometric action-adventure
notable_feature
Early save game system using Batstones

Lore & Background

The object of the game is to rescue Robin by collecting the seven parts of the Batcraft hovercraft scattered around the Batcave. The gameplay takes place in a 3D isometric universe, which programmer Jon Ritman and artist Bernie Drummond would further develop for 1987's Head Over Heels. The game is notable for implementing an early example of a save game system that allows players to restart from an intermediate point on the loss of all lives rather than returning to the start, specifically the point at which Batman collects a 'Batstone'.

Reader's Guide

Batman (1986) holds significance as the first Batman video game and as a technical milestone in isometric game design. Its isometric perspective, developed by Jon Ritman and Bernie Drummond, directly influenced their later work on Head Over Heels. The game's save system, using Batstones to mark restart points, was an early innovation in player-friendly design. Commercially, it achieved chart-topping success across multiple formats in May 1986, and critical reception was strong, with Crash rating it 93%, Your Sinclair 9/10, and Sinclair User awarding five stars and a 'classic' designation. An unrelated Batman game, Batman: The Caped Crusader, was released two years later.

Did You Know?

A First for the Dark Knight

When Ocean Software shipped Batman in 1986, they were doing something no one had done before: bringing the DC Comics superhero into the world of home computing. This was the very first Batman video game ever developed, a milestone that predated the franchise's later forays into interactive entertainment by years. The title launched simultaneously across four platforms—the Amstrad PCW, Amstrad CPC, ZX Spectrum, and MSX—giving a wide slice of 1980s home-computer owners a chance to step into the role of the Caped Crusader. Its existence also sets a clear historical boundary: when a separate, unrelated Batman title called Batman: The Caped Crusader appeared two years later, it was a completely different project with no development lineage to this original. In the broader timeline of licensed superhero gaming, this 1986 Ocean release stands as the starting point, the proof-of-concept that proved a comic-book icon could translate into a playable, isometric adventure on a modest 8-bit machine.

Isometric Innovation and the Batstone

The core loop of the game is deceptively simple in its goal: Robin has been taken, and Batman must recover the seven scattered components of the Batcraft hovercraft hidden throughout the Batcave to rescue him. What makes the experience technically noteworthy, however, is the 3D isometric universe in which all of this unfolds. Programmer Jon Ritman and artist Bernie Drummond built this engine with an eye toward the future, as they would refine and expand the same visual and spatial framework for the 1987 platformer Head Over Heels. Perhaps the most forward-thinking design choice is the save-game system. Rather than forcing a player who loses all remaining lives to restart from the very beginning, the game lets progress be checkpointed at the moment Batman collects a Batstone. This intermediate restart point was an early example of the save-system concept that would later become standard across the industry, and it dramatically reduced the frustration of navigating a multi-room isometric world on 8-bit hardware.

Critical Acclaim and Chart-Topping Success

The computer gaming press of the mid-1980s did not hold back on its praise. Crash magazine awarded the game a 93 percent score, Your Sinclair gave it a 9 out of 10, and Sinclair User went so far as to bestow five stars and label it a classic—a designation that carried real weight in a market still young enough for such superlatives to feel earned rather than routine. The commercial numbers matched the critical enthusiasm. In May 1986, Batman climbed to the number one position simultaneously on the Amstrad chart, the ZX Spectrum chart, and the All-Format chart, a remarkable triple top in a single week that underscored how broadly the title resonated across the home-computer audience. For Ocean Software, the achievement validated their decision to license a major comic-book property and invest in a bespoke isometric engine. For players, it confirmed that a superhero adventure could be as compelling on a ZX Spectrum or an Amstrad PCW as any arcade experience, and it cemented the game's reputation as a defining title of the 1986 home-computer year.

The Engine That Would Become Head Over Heels

While Batman the 1986 game is remembered primarily as a licensed superhero adventure, its lasting technical legacy actually belongs to the people behind the scenes. Jon Ritman and Bernie Drummond used the project as a proving ground for an isometric rendering and spatial-navigation system that they would carry forward and significantly expand the following year. The result of that evolution was Head Over Heels (1987), a title widely regarded as one of the most innovative platformers of the era, which built directly on the 3D isometric universe first prototyped in the Batcave. In other words, the very engine that let players chase seven Batcraft parts through a multi-level cave became the foundation for a completely different genre and a far more ambitious design. This lineage also helps explain why the 1986 Batman game feels technically ahead of its contemporaries on the ZX Spectrum and Amstrad platforms: it was, in a sense, a dress rehearsal for something bigger. The game's save-system checkpoint, its isometric depth, and its multi-room architecture all point toward the ambitions Ritman and Drummond would fully realize a year later.

Gallery

Frequently Asked Questions

What is Batman (1986 video game)?

Batman (1986) is an isometric action-adventure game developed by Ocean Software, making it the very first video game to put the Caped Crusader on screen. It launched in 1986 across several home computer systems of the era.

Which platforms can you play Batman (1986) on?

The title shipped for the Amstrad PCW, Amstrad CPC, ZX Spectrum, and MSX. No other platforms received an official release at the time.

What is the player's goal in Batman (1986)?

You control Batman as he navigates the Batcave to collect seven separate Batcraft hovercraft components. Once all pieces are assembled, the objective is to rescue Robin.

Why do retro gaming fans consider Batman (1986) a landmark title?

It was the first video game ever to feature Batman and helped pioneer the isometric 3D perspective that would later define titles like Head Over Heels. It also introduced an early checkpoint-save mechanic that was unusual for 1986.

How does the Batstone save system work in Batman (1986)?

Batstones function as checkpoint markers scattered around the Batcave. If you run out of lives, the game restarts you at the most recent Batstone you picked up instead of forcing a full run from the beginning.

More in Superhero video games 1-24

Spotted an error? Know more?

This is a living reference — every entry is fact-audited, and reader corrections feed straight into our audit queue. Suggest an edit · See this site's audit record

Comments

Loading…
Open in the interactive codex →