Contents

Paradroid: Braybrook's Perfect Little System

One takeover minigame does the work of an entire progression tree, and Andrew Braybrook wrote down how he built it

Contents

There’s a particular kind of design that makes everything else in a game unnecessary. You find one mechanic that carries the progression, the combat, the difficulty curve and the theme at once, and every system you were planning to build around it turns out to be scaffolding you can take down. It’s rare. It’s mostly a matter of luck and obsession in some ratio nobody can specify.

Andrew Braybrook found one in 1985, Hewson published it, and the thing that makes Paradroid worth writing about forty years on is that we know exactly how he found it, because he was writing it all down at the time.

The premise, which is nearly nothing

Advertisement

You are droid 001, an Influence Device. You have no weapons of your own. You are a small, defenceless thing let loose on a freighter full of robots that would like you gone, and your entire capability set is the ability to become one of them.

The ships are laid out as flat, top-down decks — corridors, lifts, consoles — and they’re full of numbered droids. The number is the whole hierarchy. A 123 is a servo-mechanic that barely notices you. A 999 is a Command Cyborg, and it is the reason you’re here. Everything in between is a ladder, and the numbers are readable at a glance, which is the first small piece of craft worth pointing at: the game never explains its power curve because the power curve is printed on the enemies.

You clear a ship of droids and move to the next one. That’s the shape. On paper it’s a top-down shooter with a gimmick.

The duel

Touch a droid and press fire and the game stops being a shooter.

The screen becomes a circuit board, split down the middle. You’re on the left, the droid’s on the right, and there’s a clock. Both sides pull from the same supply of connector paths, racing to claim more of the board than the other before the timer runs out. Whoever owns the majority when it stops wins. Win, and you’re inside the droid — its speed, its armour, its gun are now yours, and your old shell is discarded. Lose, and you’ve paid for the attempt.

That’s it. That’s the whole progression system.

Look at what it’s doing. In a normal action game of the period, getting stronger meant finding a weapon crate. Paradroid replaces the crate with a duel, and in doing so it makes power something you take off a specific opponent, at a specific moment, with a specific risk attached. There’s no abstraction layer. The 476 with the annoying gun that’s been chasing you down a corridor is also the gun, and if you want it you have to walk up and out-think it.

The tuning is where it goes from clever to genuinely excellent: the difficulty of the duel scales with the distance between what you are and what you’re grabbing at. As a bare 001 you can take a low-class drone almost casually. Reach straight for a 999 from the bottom of the ladder and the board will eat you. So you climb. You take a 249 to get the legs, use those legs to corner a 493, use the 493 to survive long enough to find a 711, and the game’s entire mid-section is you working your way up a hierarchy one rung at a time because the maths won’t let you skip.

That is an RPG levelling curve. It has no experience points, no menus, no numbers going up in a stat block, and no tutorial. It’s a minigame and a hierarchy of enemies, and between them they produce a sense of escalating power that most games need a character sheet to fake.

Why the tug-of-war is the right shape

Advertisement

Plenty of games have takeover mechanics. Almost all of them resolve as a dice roll or a quick-time button. Braybrook’s duel is a contest with a topology — a board you can read, where a good player develops actual technique, where the shared middle supply means every claim you make is a claim the droid can’t have. It’s tug-of-war with geography.

Which means the takeover is skill-expressive rather than random, and skill-expressive in a way that’s completely different from the skill the rest of the game asks for. The corridors want reflexes and spatial memory. The duel wants a cold head and about four seconds of planning. Slamming those two demands together is the reason the loop never gets boring: you’re constantly switching from twitch to think and back, and the switch is the rhythm of the game.

There’s a cruelty in it as well, and the cruelty is load-bearing. Losing a duel does not just deny you the droid — it leaves you standing in a corridor next to something that now knows exactly where you are, in a body you were trying to get rid of. Failure has a location. The game’s tension comes from the fact that the riskiest thing you can do is also the only way forward, and the decision to try is always made in the open, with the thing you want to become already shooting at you.

The consoles complete it. Wander into one and you can pull up the deck plans and the droid roster — what’s on this ship, what class it is, what it’s carrying. Information as a resource. You come out of a console with a plan instead of a reflex, which is a sentence you could apply to most immersive sims made since, and Paradroid got there in 1985 on 64 kilobytes.

The diary

Here’s the part I find genuinely remarkable, and it’s why Paradroid belongs in any serious conversation about game design rather than just any nostalgic one.

Braybrook wrote a development diary and ZZAP!64 published it, across several issues in 1985, while the game was being made. It’s an actual working record of a bloke sat in front of a Commodore 64 figuring out whether the thing he was building was any good, written years before the industry invented the sanitised postmortem. It ran alongside the magazine’s reviews, and a generation of British teenagers read it and learned that games were made, by people, who made mistakes.

I don’t think we’ve had many things like it since. Post-release GDC talks are performances. Dev blogs are marketing. The diary was published before anyone knew whether the game would be good, which makes every doubt in it real.

Its existence also gives us something almost nothing else from the era has: a paper trail. When I say the transfer duel is the design’s spine, the record shows the work. No reverse-engineering of intent from the finished artefact required.

Braybrook and Steve Turner would formalise Graftgold around this kind of methodical craft, and you can trace the sensibility straight through Braybrook’s next one — Uridium turned the same obsessiveness on a scrolling shooter and produced something equally over-engineered in the best sense. Turner’s own Spectrum riff on Paradroid, Quazatron, tilted the whole thing isometric and rebuilt the duel, which is as close to a genuine descendant as the game ever got.

Where the ancestors are

Trying to place Paradroid on the family tree is where it gets awkward, because the generation it belongs to is the generation of one-person C64 games that were solving completely different problems from each other. Elite compressed a galaxy into an algorithm; The Sentinel built a puzzle out of sightlines; Paradroid built an RPG out of a minigame. What they share is a machine small enough that you couldn’t build a system by throwing content at it. Constraint produced elegance because elegance was the only affordable option.

The descendants are everywhere and mostly unaware of it. Every game where possessing an enemy is your progression owes Paradroid something. Every game that puts a skill-based contest where a stat check would go is working the same seam. The open-source Freedroid project kept the letter of it alive for decades; Paradroid 90 on the Amiga and ST gave it a sharper coat of paint and lost a little of the original’s stark legibility along the way.

Playing it now

The C64 original holds up with almost no allowances required, which is the genuinely surprising part. The decks are still readable. The droids still telegraph their class on their chest. The duel is still tense, still learnable, and still has a skill ceiling you can spend an evening finding. It’s tape-era in its unfriendliness — it explains nothing and expects you to work it out — and that’s a fair trade for a game that respects you enough to hand over its entire rule set in the first two minutes and then get out of the way.

The one concession the years demand is patience with the opening minutes. Paradroid drops you in as a 001 with nothing, and a 001 with nothing is a frustrating thing to be if you haven’t yet understood that the duel is the answer to every question the game will ask. Push through two or three ships and the architecture snaps into focus: the roster on the console, the ladder of numbers, the board in the middle. After that it stops being an old game and starts being a good one.

Find it however you find C64 games now. What you’re looking for takes about ninety seconds to reveal itself: a small helpless thing walks into a corridor, meets something much bigger, and takes it apart on a circuit board. Everything else the game does grows out of that. Forty years of design and it’s still hard to name a system that does more with less.

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.