Blade Runner (1997): The Adventure With a Real Detective Problem

Every detective game has the same dirty secret. The culprit is decided before you install it. Your deduction is theatre — you are performing the motions of investigation over a conclusion that was authored months ago, and the game’s job is to make you feel clever on your way to a destination it will reach with or without you. This is true of the good ones as much as the bad. It is true of games I love.

Westwood Studios shipped a game in November 1997 that does not do this. In Blade Runner, when a new game starts, the machine decides which characters are replicants. Roll it again and it decides differently. The suspect you spent four hours building a case against in your last playthrough is, this time, an ordinary human being having a bad week, and someone you barely spoke to is the one with the artificial eyes.

Twenty-nine years later I can count the games that have done this on one hand, and I have never stopped wondering why.

A parallel case, which was the correct decision

The obvious move in 1997 was to let you play Deckard. Westwood declined. You are Ray McCoy, a rookie blade runner working a different case in the same Los Angeles at roughly the same time, and Deckard’s story is happening somewhere off to the side where you cannot touch it.

This is the single most disciplined thing about the game. An adaptation would have to hit the film’s beats, which means the plot is a corridor and your job is to walk it — a structural trap that has swallowed almost every licensed game ever made. A parallel story gets the whole world for free (the rain, the neon, the Voight-Kampff machine, the moral question) and owes the source no beats at all.

The production backs it up. Sean Young, James Hong, Brion James and William Sanderson return to their roles, which anchors the thing as a real continuation rather than a knock-off with the serial numbers filed. Frank Klepacki — the same composer who scored Command & Conquer — writes in Vangelis’s idiom without embarrassing himself, which is a high-wire act I still find slightly astonishing. Four CDs of it.

McCoy opens on a case at Runciter’s, an animal shop where the artificial animals have been slaughtered. Animal cruelty as the inciting crime, in a world where every animal is manufactured. That is a precise and cruel joke about the film’s own preoccupations, and the game makes it in the first ten minutes and then never nudges you about it.

The city keeps moving after you leave

The second radical decision: the world runs on a clock.

Characters in Blade Runner have schedules. They walk from place to place, they meet each other, they act on their own business, and none of it waits for McCoy to arrive and press the plot button. Go to Animoid Row too late and the person you wanted has gone. Spend forty minutes turning over the Bradbury when a suspect is on the move and you will arrive at an empty room with an emptier trail.

The design consequence is that time becomes evidence. If you know where someone is at 9pm and they were somewhere else at 8pm, you have learned something about them, and you learned it by being in the right place rather than by clicking a dialogue node. Nearly every adventure game of the era froze the world into a set of tableaux waiting for the player. Grim Fandango, a year later, would use a four-year time skip to move its world on between acts — an elegant solution to the same staleness problem, and one that still only advances the clock when the script says so. Westwood just let the clock run.

What you get is dread. A city that is doing things while you are elsewhere is a city you can be late for, and being late for a city is the exact feeling police procedurals are made of.

The evidence has to actually work

The tools are a nice piece of adaptation. The KIA — a database in McCoy’s pocket — holds every clue, suspect and photograph, cross-referenced, and it is where the case actually lives. The ESPER machine lets you crawl around inside a photograph, pushing in and panning across, pulling detail out of reflections. The Voight-Kampff kit is there when you need to ask someone about their mother and watch the pupil.

Because the culprits are reassigned per playthrough, these tools have to do real work. A photograph cannot contain “the clue that proves it was Dektora” if Dektora is human this time. So the evidence has to be about things — a serial number, a location, an alibi, a physiological reading — and the game has to assemble a case from whatever the dice handed it.

That is a genuinely different engineering problem from writing a mystery, and it puts Blade Runner in strange company. Return of the Obra Dinn is the finest deduction game ever built, and its answers are fixed in stone — Lucas Pope’s achievement is a chain of inference so tight that a fixed solution feels discovered instead of delivered. The Case of the Golden Idol does the same trick with hand-drawn tableaux and no hand-holding whatsoever. Both are better puzzles than Blade Runner, by a distance.

But both share the secret. The answer was written down before you arrived. Blade Runner is the one that tore the answer up, and that costs it something enormous.

What randomisation costs

Here is the honest reckoning, because the game is usually praised without one.

A mystery writer’s power comes from knowing the answer. Every scene can be built to point at it obliquely, every red herring is placed to exploit a specific misreading, and the reveal lands because six earlier scenes were secretly load-bearing. Randomise the answer and all of that authorial leverage goes. Scenes must work for every possible assignment, so they must be written loose — a suspect who might be a replicant and might be a scared woman has to have dialogue that plays both ways, and dialogue that plays both ways is dialogue that commits to neither.

You feel it. Some conversations in Blade Runner are vaguer than they should be, and some clues have the quality of a form field rather than a revelation. The game is smoother than its ambition in the places where the ambition is doing the most work.

It also inherits the era’s other problems and does nothing about them. There are timed sequences with guns in them, and they are poor. Some scenes have that late-nineties habit of demanding you click a five-pixel object in a rainy alley to advance a plot that is otherwise on rails. Voxel characters over pre-rendered backgrounds — Westwood’s own technology, sharpened on Command & Conquer — meant real 3D actors in a hand-painted city with real lighting on them, which was a marvel in 1997 and now reads as a soft crowd of animate plasticine.

And yet. The trade is worth it, and here is why: the thing Blade Runner is about is the impossibility of telling a person from a machine, and it is the only detective game whose systems have that uncertainty in them rather than merely its script. When McCoy runs a VK test and the reading is ambiguous, the ambiguity is real, because the game itself has not decided in your favour. Every other Philip K. Dick adaptation asks you to feel epistemological doubt. This one gives you a database of facts and a suspect whose status was generated by a random seed, and lets you find out what doubt actually feels like when nobody is holding your hand under the water.

That is a systems read of the source material. That is what an adaptation is for.

Where to find it, and what to expect

The game was effectively lost for two decades — a four-CD Windows 95 title with a bespoke engine that nobody could run. The ScummVM team reverse-engineered it, which is why it is buyable and playable again, and that restoration is one of the great acts of games preservation. Play that version. The 2022 enhanced release was met with a reaction that speaks for itself.

Go in expecting a 1997 adventure game, which means expecting pixel-hunts and awkward shooting and a few hours of learning where anything is. Go in twice, though. The second playthrough is where the design detonates: you walk back into a room you have already solved and the room is telling you something else. Almost no game has ever earned a replay so structurally, and it did it before Blade Runner was a franchise anybody expected to still be arguing about in the 2020s.

Spoilers below

The randomisation is partial, and knowing the shape helps. A core of the story is fixed — Clovis leads the escaped replicants, Lieutenant Guzza is McCoy’s boss and is dirty, the Runciter case runs the way it runs. What moves is the status of the people around the edges: Lucy the runaway kid, Dektora the club performer, and several others can come up human or artificial in any given seed. McCoy himself is on the table.

That last one is the game’s real weapon. Play once and McCoy is a cop hunting replicants. Play again and the same man, saying the same lines, hunting the same fugitives, is one of them and does not know it, and the entire moral weight of every scene inverts without a single word being rewritten. The game has built the film’s central question into its save file.

Guzza is where the plot gets its spine. Your own department is compromised, which means the institution you are enforcing for is corrupt in exactly the way the replicants say it is, and the game hands you that fact without a speech about it. What follows is a genuine fork: keep working the case, or stop.

The endings run to more than a dozen, and the best of them sting. You can go off-world with the replicants. You can hunt them all down and file the paperwork. You can end up somewhere in the middle of the desert with someone you decided to trust. The game never tells you which one was right, and it never scores you, and after all the VK readings and the ESPER scans and the database entries, the last thing it asks is what you personally think a person is.

Twenty-nine years on, that question is still open, and Blade Runner is still the only detective game that put it in the code.