Contents

The Way of the Exploding Fist: The Fighting Game as Ritual

Beam Software gave the Commodore 64 sixteen moves, a bow before every round and the best-selling game of 1985

Contents

Every bout of The Way of the Exploding Fist starts the same way: both fighters bow. It is a half-second of stillness before either combatant is allowed to throw a kick, and it is doing more design work than half the health bars in the genre it created.

Beam Software, the Melbourne studio better known internationally under its publisher’s name, Melbourne House, released the game for the Commodore 64 in 1985. The development team — Gregg Barnett, Bruce Bayley, Neil Brennan and David Johnston — built a one-on-one karate duel around sixteen distinct moves, animated with over six hundred sprite images on a machine that most contemporary reviewers assumed could not hold a fighter’s full range of motion in memory at all. It became the best-selling computer game in the UK that year, sold 150,000 copies for the Spectrum alone by 1987, and topped half a million units across Europe on all formats combined. It also won Game of the Year at the third Golden Joystick Awards, with Melbourne House picking up Best Software House the same night.

The arcade prototype it argued with

Advertisement

The game did not arrive from nowhere. Data East’s Karate Champ, developed by Technōs and released to arcades in mid-1984, had already established the one-on-one fighting duel as a legible genre, with dual-joystick controls and a points-based scoring system across rounds. Barnett has been direct about the debt: a virtual prototype of Karate Champ appeared early in development, and he has said it would have been hard not to be influenced by it, though Exploding Fist would probably have looked different without that coin-op sitting in the room. Konami’s Yie Ar Kung-Fu, released the same year as Exploding Fist, was working the same arcade lineage from a different angle, with a wider and more fantastical move roster.

What Beam did with the inheritance is the interesting part. A dual-joystick arcade cabinet is a different physical object to a single joystick and a keyboard at home, and the home version had to translate Karate Champ’s directional-input vocabulary into something a C64 owner’s one-stick setup could execute cleanly. The compression of that arcade grammar into a single-joystick scheme, without losing the readability of the moves, is the actual engineering achievement underneath the sales figures.

Sixteen moves, no wasted ones

The move set reads modestly on paper: kicks, punches, jumps, somersaults, a roundhouse, sweeps low and high. What made it feel enormous at the time was how the sixteen were selected — by the direction you were facing, your joystick position, and whether you were holding the fire button, rather than a special-move code or a menu. There was no manual to memorise, because the entire vocabulary was reachable through the same handful of physical inputs recombined, which is the design principle every fighting game since has rediscovered under different names.

That compactness mattered because the C64 simply did not have the memory budget for a deep frame-data system. Beam’s answer was to make every move legible at a glance and to make the distance between two fighters, not a hidden numeric range, the determining factor in what would land. A high kick thrown from too far away just missed, visibly, the way a real kick would. There was nothing to look up. You learned the spacing by getting hit, which is the oldest fighting-game tutorial there is and still the only one that actually works.

The bow is the whole argument

Advertisement

The opening bow is easy to read as decoration, a nod to the karate setting rendered as a courtesy animation. It is not decoration. It establishes, before a single frame of combat, that this is a contest with form — that hitting your opponent is not the point, winning the exchange cleanly is. The scoring reinforces the same idea: matches are won on points across rounds rather than a single knockout, so a fight is a conversation across several exchanges rather than one lucky connect, and the bow at the start of each round resets that conversation with the same formal courtesy it began with.

This is a harder thing to build into software than it sounds. A fighting game with no health bar draining toward zero has to make every point feel consequential on its own terms, or the whole structure reads as arbitrary. Beam’s solution was pacing: the gap between successful hits is long enough, and the whiffed attempts visible enough, that a landed kick reads as an event rather than a tick on a counter. You remember which kick won a given round because so few of them actually connect.

The dispute that followed the sales

The game’s commercial success attracted an imitator close enough that Melbourne House pursued the matter through the courts — International Karate, released the following year by System 3, shared enough of the same structure and presentation that the resulting legal dispute became one of the defining intellectual-property fights of the early British software industry. The case is a useful reminder of how young the whole business still was: a genre this legible to imitate, on hardware this uniform across competing studios, was always going to produce exactly this kind of argument over where inspiration ends and duplication begins.

International Karate survived the dispute to become a landmark in its own right, and its looser, funnier descendant, IK+, pushed the same disciplined, distance-based combat to three simultaneous fighters, turning the austere one-on-one duel into something closer to a slapstick free-for-all. The throughline across all three games is identical: a fighting game built on a small, honest move set and a strict read of spacing, rather than a deep combo system, can carry an entire genre on a machine with barely enough memory to hold the moves at all.

The two-player living room

However good the computer opponent was, the game’s real engine room was the second joystick port. Two players sitting side by side, trading rounds, is a different social object than a single-player ladder, and Exploding Fist was built for it from the ground up rather than treating it as a bolt-on mode. The scoring across rounds meant a single lucky hit did not settle an argument between two people in the same room the way a one-hit knockout would have — you had to actually win the majority of a best-of-several exchange, which is a structure that produces rematches rather than resentment.

This landed at a moment when martial-arts films were mainstream cinema — the Karate Kid had opened in 1984 — and British teenagers with a C64 and a single cassette deck had, for the first time, a way to stage that fantasy against a friend rather than just watch it happen to someone else on a screen. The game did not need to dress up in that cultural moment with licensed characters or a tie-in deal to benefit from it; the karate setting alone was legible enough that no explanation was required, which freed the design budget entirely for the mechanics rather than any framing narrative.

Why the restraint still reads as the better design

Modern fighting games have solved problems Exploding Fist never had to face — frame-perfect input windows, cancel systems, characters with wildly different toolkits. But the specific discipline of a small vocabulary, cleanly readable at a glance, distance-governed rather than combo-governed, is a design lesson that keeps getting rediscovered rather than superseded. Every fighting game that has since tried to make its neutral game — the pre-hit spacing dance — the actual point of the match, rather than a preamble to a combo, is doing a version of what Beam built by necessity in 1985.

The computer opponent deserves credit here too. It did not simply react to your last input; it read distance and timing well enough that beating it required actually learning the spacing rather than memorising a fixed pattern, which is precisely why the game held up as a two-player experience and a single-player one in equal measure. A fighting game whose computer opponent can be solved once and never again is a fighting game with a shelf life measured in afternoons. Exploding Fist’s did not have that problem, and the sales figures across three years bear that out — a game does not sell half a million units on novelty alone; it sells that many because people kept coming back to a fight they had not yet fully solved.

The genre’s later, more famous arcade lineage — Street Fighter II, and everything built on its formal system of hitboxes and frame data — would eventually give the same spacing-based insight a vocabulary and a stopwatch precision that an eight-bit home computer could never have afforded. But the underlying claim, that the gap between two fighters is the actual game and the moves are just how you argue about it, is one Exploding Fist had already made, in public, on a machine that measured its memory in kilobytes rather than megabytes.

Where to play it: the C64 version is the one to seek out first — the one with the six hundred-plus sprite frames that made reviewers doubt their own eyes — though the Spectrum, Amstrad, BBC Micro, Acorn Electron and Commodore 16 ports all carry the same design intact, at whatever cost each machine’s colour depth exacted on the animation.

Spoilers below

There is no ending to spoil in the conventional sense — the game is a tournament ladder against increasingly skilled computer opponents, and the “reveal,” such as it is, comes late: the final opponents read your spacing and punish hesitation far more aggressively than the early ladder does, to the point that several contemporary reviewers noted the difficulty curve steepens sharply rather than gradually. There is no boss with a new move set, no twist beyond the game insisting, by the final rounds, that you have actually learned what it spent the earlier fights teaching you. That is the entire design philosophy, delivered as difficulty rather than narrative, and it is consistent with everything above the line.

Advertisement
Advertisement
Jay
Written by Jay

vo.rs's games critic. Jay covers the medium as a system rather than a spectacle — this month's release, the indie nobody bought, and the Amiga game it's quietly descended from — asking what a mechanic makes you feel and why the loop holds. Learned to wait through a C64 tape load, never stopped playing since, and still finishes the odd 60-hour RPG out of spite. Expect argued verdicts, no score ever, spoilers below the line, and a running list of older games worth your weekend.