Missile Command

Overview

Dave Theurer, a programmer at Atari, designed Missile Command in 1980 while having recurring nightmares about nuclear war. He has said this directly: the game’s subject matter got into his sleep. The Soviet Union had invaded Afghanistan. SALT II was stalled in the Senate. The Bulletin of the Atomic Scientists’ Doomsday Clock was at seven minutes to midnight.

In this context, Theurer made a game about defending cities from nuclear missiles — a game designed so that the cities always eventually fall, the screen always eventually reads THE END, and there is never, under any circumstances, a victory.

The Mechanics of Doom

Missile Command’s setup is simple. Six cities sit along the bottom of the screen. Three missile batteries — left, center, right — defend them. From the top of the screen, incoming ballistic missiles descend in white streaks, each targeting a city or battery. Players move a crosshair cursor across the field and fire defensive missiles: they explode at the targeted position in a blast radius that destroys any incoming ordinance caught within it.

Accuracy matters more than volume. The defensive missiles are finite — each battery has a supply of 10, rechargeable only between waves. Missing wastes ammunition. A well-aimed shot that catches three incoming missiles simultaneously is exponentially more valuable than three individual shots.

The resource allocation problem deepens with every wave. Protecting all six cities requires distributing defensive fire effectively across the full width of the screen. Protecting the batteries — which when destroyed take their remaining ammunition — requires additional attention. Every target that hits destroys either city or capability. As waves intensify, perfect defense becomes mathematically impossible.

The Cold War Game

Most arcade games offered victory conditions. Space Invaders’ invaders stop — eventually, theoretically. Pac-Man has a kill screen at level 256. Donkey Kong runs indefinitely but through repetition rather than design. Missile Command was different: it was designed around the premise that there is no victory. The screen eventually goes dark, cities fall, and THE END appears.

Theurer has confirmed that this was intentional, reflecting his understanding of the subject matter. Missile Command was a game about the impossibility of nuclear deterrence working indefinitely. You could delay. You could be skilled. You could prioritize targets efficiently and extend the game considerably past a casual player’s limit. But the missiles kept coming faster and denser, and eventually they won.

This made Missile Command philosophically unusual. The game’s ending wasn’t a failure state in the conventional sense — it was the acknowledgment of what the game was about. Ballistic missile defense doesn’t win. It delays.

The Cultural Footprint

Missile Command arrived at the right moment to accumulate meaning. TIME magazine wrote about the game. Rolling Stone cited it decades later as a Cold War cultural artifact. It became a reference point in discussions about how popular entertainment processed nuclear anxiety — the specific fear that not skill or determination but only luck and time delay separated survival from annihilation.

The Atari 2600 port sold millions of copies. The game appeared in compilations for every subsequent Atari platform and in Atari’s licensed compilations for PlayStation, Xbox, and modern systems. The 1999 remake and the 2004 Missile Command: Recharged updated the visuals while preserving the core design.

What persisted from all of these versions is the ending that isn’t an ending: THE MISSILE COMMAND HAS BEEN DESTROYED. THE END. Games about winning have game overs. Missile Command has a final statement.