Rampage on the C64: The Pleasure of Knocking Things Down

Bally Midway’s Rampage hit arcades in 1986, designed by artist Brian Colin and programmer Jeff Nauman, and Activision brought it to home computers over the following two years, with the C64 and Spectrum among the ports arriving through 1987 and 1988. What separates it from almost everything else in the arcade action catalogue of the period is a single reversal of intent: most games of the era treat destruction as an obstacle you cause on your way somewhere else. Rampage makes destruction the entire point, and Colin has said outright that he set out to build a game with no wrong way to play — no fixed objective to fail at, no traditional death penalty waiting to punish an unconventional approach. That’s an unusually permissive design brief for 1986, and it’s the reason the game still feels distinct four decades later.

Three monsters, one origin logic

The cast is George, Lizzie and Ralph — a scientist transformed into a King Kong-styled gorilla by experimental vitamins, a woman turned reptilian after swimming in radioactive waste, and a man turned into a werewolf by a hot dog laced with an unknown additive. Colin has pointed to King Kong and 20 Million Miles to Earth as his reference points, and specifically clarified that Lizzie draws on that second film’s Ymir creature rather than Godzilla, on the grounds that Godzilla was simply too large a concept for what the hardware and the screen could accommodate. That’s a small but telling piece of design honesty: the monsters aren’t scaled to whatever felt most impressive on a poster, they’re scaled to what a cabinet’s screen and processing budget could actually depict convincingly, and the source material was chosen to fit the constraint rather than the other way round.

Why the destruction loop works

The core verb — climb a building, punch it, watch it crumble a floor at a time — is satisfying for reasons that have as much to do with feedback as with the premise. Buildings don’t simply vanish when depleted; they come apart in stages, each hit visibly reducing the structure and revealing whether a smashed window holds something useful (food, money) or something dangerous (a bomb, a live appliance), which turns every strike into a small gamble rather than a rote animation cue. Health comes from eating people and food items scavenged from the wreckage, army vehicles — helicopters, tanks, police cars, boats — return fire and have to be weathered or destroyed, and reverting from monster back to human form mid-rampage gets you eliminated outright unless another player’s monster eats you first, which gives even the cooperative multiplayer sessions a genuine edge of betrayal-adjacent tension.

None of that structure would land as satisfying destruction if the game didn’t sell the physical sense of a building actually failing under repeated punishment. The staged collapse — floor by floor, with visible cracks and dust accompanying each hit rather than a building simply popping out of existence — is doing the same job a good combo counter does in a fighting game: it turns a single input into a readable escalation, so the player feels the weight of the fifth punch differently from the first.

The constraint that shaped the design

Colin has spoken about working within a hardware limitation that could really only render rectangular shapes convincingly, which is precisely why the whole design ended up centred on building destruction rather than on more organic scenery or terrain — a rectangle is the one shape the hardware of the period could depict falling apart believably, so the entire game got built around the one object type that constraint could sell. Identical city layouts reused across levels, palette-swapped monster sprites standing in for different characters, and dust effects deployed partly to mask animation seams are all quiet examples of a team turning a technical ceiling into a stylistic choice rather than fighting it and losing. That’s a pattern worth recognising across the arcade era generally — plenty of the decade’s most memorable design decisions started as workarounds for exactly this kind of hardware ceiling, the arcade conversion problem: eight bits against a dedicated board covers the wider version of that same negotiation between ambition and silicon.

What the C64 port kept and lost

Activision’s home computer conversions inevitably traded away some of the arcade cabinet’s screen presence and colour depth, and the C64 version in particular compresses the scale of a falling building into a smaller, chunkier silhouette than the arcade original commands. What survives the downgrade is the part of the design that never depended on spectacle in the first place: the staged collapse, the window-smashing gamble, the vehicle threat forcing you to keep moving rather than camp a single building. A game built around a rectangle’s failure state travels reasonably well to a machine with a smaller rectangle to work with, in the same way Supremacy: the empire game with one bad decision in it survived its own C64 downgrade a few years later even as its presentation shrank. Rampage on C64 isn’t the definitive version of the experience, but it’s a legitimate one, because the mechanic that made the arcade version worth playing was never really about how large the building looked.

Later console ports diverged from the arcade cast in ways worth noting for anyone comparing versions today. The NES release, handled separately by Data East rather than Activision, dropped Ralph the werewolf from the roster entirely, and a subsequent Atari Lynx version years later added an entirely new character, Larry the rat, rather than simply reproducing the original trio. Each of those decisions reflects a different publisher solving the same cast-and-cartridge-space equation differently, and it’s a reminder that “the definitive version” of a game this widely ported is a genuinely contested question rather than a settled one — the C64 edition at least kept the original three monsters intact, which the NES conversion didn’t manage.

The ancestry worth tracing

Rampage sits in a lineage that runs back through giant-monster cinema rather than through other video games, which is unusual for an arcade design of its period — most 1986 arcade hits were answering other arcade hits, while Colin was explicitly answering King Kong and its B-movie descendants. That’s worth taking seriously as a design decision rather than dismissing as flavour text: building the whole moment-to-moment loop around a cinematic image of destruction, rather than around an existing genre template, is why the game reads as a genuine original rather than a reskin of something else already on the arcade floor that year. Operation Wolf: the light gun you never had is a useful comparison from the same broad arcade generation — another game selling a single, uncomplicated physical fantasy (this time marksmanship rather than demolition) through hardware built specifically to make that one fantasy feel as direct as possible.

Permission as a design ingredient

It’s worth dwelling on Colin’s stated goal of a game with no wrong way to play, because it’s a genuinely rare design ambition to state outright and then actually build toward. Most arcade games of the mid-eighties were built to extract a coin’s worth of controlled failure from the player as efficiently as possible — a clear objective, a clear death condition, a clear incentive to feed the machine again. Rampage removes the fail state almost entirely for as long as a player keeps a monster alive, replacing “avoid losing” with “keep finding something satisfying to break,” which is a fundamentally different relationship between player and machine than the coin-op economics of the period usually rewarded. That permissiveness is also a large part of why the game translated so comfortably to a home-computer context where there was no coin slot demanding a quick loss to justify another twenty pence — the design was already built around sustained, open-ended destruction rather than around a scored run toward a high-score table, which made it an unusually natural fit for a living room rather than an arcade floor.

What actually plays now

Multiplayer is where the design earns its keep most fully — contemporary reviews at the time noted that a solo session can run out of things to discover faster than a session with two or three monsters loose on the same map, competing for buildings and occasionally eating each other’s revealed human forms out of opportunism as much as strategy. The C64 version is worth approaching as a smaller-scale but structurally faithful rendition of that same multiplayer chaos, rather than as a definitive substitute for the arcade cabinet’s scale.

The genre it opened rather than closed

Rampage didn’t invent the idea of a giant monster smashing a city — the cinema it drew from had been doing that for decades before Colin and Nauman built a controllable version of it — but it’s a reasonable claim that the game established destruction-as-objective as a viable arcade proposition in its own right, distinct from the disaster-avoidance framing most contemporaries defaulted to. Later games built entire structures on top of that same permission, letting a player be the disaster rather than the party fleeing one, and it’s worth remembering that the idea had to be argued for once, against a design culture that mostly assumed a clear objective and a punishing fail state were non-negotiable ingredients. Colin’s insistence on removing both, and building outward from what remained, is the reason the game still reads as a genuine design statement rather than a period curiosity that happened to feature famous-looking monsters.

Spoilers below

The genuinely difficult stretch in any extended session comes once the army’s response escalates past a threshold where a monster staying in one place to finish a stubborn building takes sustained fire from multiple vehicle types simultaneously — the design punishes greed for a specific building’s remaining floors exactly as much as it rewards the initial climb-and-punch satisfaction, which is the game’s one real balancing lesson underneath all the permissive, no-wrong-way-to-play framing. Reverting to human form at the wrong moment, with no other monster nearby to eat you back into the game, is the single most common way a session actually ends, and it’s a fittingly undignified way for a creature this destructive to go.