Rambo: First Blood Part II: The Tie-In That Was Secretly Good

Movie licences in the mid-eighties had a well-earned reputation for being the quickest, cheapest way for a publisher to put a recognisable name on a box, with the game underneath the name treated as an afterthought. Ocean Software’s Rambo: First Blood Part II, released for C64, Spectrum and Amstrad CPC in 1985 to coincide with the film, was openly built on the vocabulary of Capcom’s 1985 arcade hit Commando — respawning enemies, a mission through hostile territory, an extraction point at the far end. That’s a template a licence could have copied wholesale and gotten away with. Ocean’s version got compared to it anyway, and came out ahead: Your Sinclair called it “a thinking man’s Commando,” and the game reportedly knocked Commando itself off the top of more than one sales chart in the months after release.

An open jungle, not a corridor

Where Commando moves you forward through a scrolling battlefield with one direction available, Rambo opens the map out. The jungle at the start of the game offers a genuine choice of route into the enemy encampment — pick through a maze of tangled bushes on one side, or blow a hole straight through the perimeter fence with a rocket launcher on the other — and that fork is presented as a real decision rather than a scripted detour, because each route trades a different resource for a different risk. The stealthier bush route costs time and patience. The rocket route costs ammunition you may want later and announces your position to anything nearby. Either way through gets you to the same objective, which is the point: the game is willing to let you solve the problem your own way rather than script a single correct path through it.

That structure carries through the rest of the mission. Once inside the camp you free a captured ally, then push north to reach a helicopter, then fly it back south to extract the remaining prisoners of war, then get out while enemy gunships close in. It’s a longer, more varied shape than a single-screen arcade loop, built from a film’s plot beats rather than from a design document’s idea of what an action game needs, and the variety is doing real work — each stage of the mission asks something slightly different of the player rather than repeating the same wave-clearing loop with new scenery bolted on.

The arsenal is the tactics

Rambo carries a knife and grenades from the start, both with unlimited use, and collects a rocket launcher, an M16 and both explosive and standard arrows for a bow along the way. That spread matters more than it looks on a spec sheet, because the unlimited melee and grenade options give a cautious player a fallback that never runs dry, while the collected firearms and arrows are a finite resource worth rationing rather than spraying. A player who burns through rocket ammunition clearing the opening jungle has less of it left for the moments later in the mission when a straight fight is the only option on the table, and the game never explains that trade-off directly — it just lets the consequence arrive later, the way a resource genuinely running low always does. The result, as contemporary reviewers noted, is a Commando-shaped game that rewards thinking about resource allocation in a way the pure-reflex arcade original never asked for.

Where it actually falls down

It’s worth being honest about the game’s real weaknesses rather than overselling the whole package on the strength of its best ideas. The closing dogfight against an enemy gunship is the section most contemporary and modern accounts single out as a problem — two aircraft circling each other with controls that don’t give the player enough precision to make the exchange feel fair, a finale that reads as tacked-on where the jungle stages that precede it feel considered. And for all the route variety on offer, a skilled player who already knows the map can clear the whole mission in a handful of minutes, a brevity that undercuts the sense of a sustained campaign the opening jungle promises. Neither flaw erases what the design gets right elsewhere, but a fair account of the game has to include both.

The publisher’s fingerprints

Ocean Software built its identity through the mid-eighties largely on licence work at volume, and Ocean Software: the licence factory in Manchester covers that wider pattern — a studio shipping tie-in after tie-in on a production schedule built for speed rather than for individual design statements. Rambo is a useful data point inside that history: proof that the house model still had room in it for a genuine design idea — the route choice, the resource logic around the arsenal — when a team found one worth building out, deadline and licence obligations notwithstanding.

Set against Green Beret: the conversion that got meaner than the arcade, another military action conversion from the same broad stable, the contrast is instructive. Green Beret took an existing arcade game and made a harder version of the same single idea. Rambo had no arcade original to convert and built its own structure from a film’s plot beats instead, arriving at something closer to Commando with a map and a supply line than at a straight port of anything.

Why the comparison matters

Commando: the run-and-gun boiled down to nerve is the template most 1985 military action games were quietly imitating, and it’s worth reading alongside this one to see exactly what Ocean’s team changed. Commando is entirely reflexes and forward momentum, with almost nothing between the player and the next wave of enemies. Rambo borrows that vocabulary of respawning soldiers and a hostile map, then slows the whole proposition down with routing choices and a finite arsenal to manage, arriving at a harder, more considered game built from the same basic parts. That’s not a small licence-era achievement, and the period reviews — Zzap!64 at 96%, ACE at four out of five — back up the sense that this wasn’t a quick cash-in riding a famous name.

An open world before the phrase existed

The game’s map has been described by players revisiting it decades later as feeling like an open world compressed into a single mission — recognisable locations from the film scattered across one continuous space rather than gated behind level-select screens, with the route between them left for the player to work out rather than dictated by a scripted corridor. That’s an ambitious frame for a 1985 licensed release built to a film’s release schedule, and it’s easy to undersell how unusual it was at the time to hand a player that much room to improvise a path through a mission rather than walk them down a single lane with scenery changes. Most action games of the period, licensed or otherwise, simply didn’t trust the player with that much geography at once.

The trade-off is that the openness costs the game some of the immediate legibility a corridor design guarantees for free. A player dropped into the jungle with no clear signpost toward the objective can spend real time simply working out where the camp is relative to the starting position, which is either a virtue or a flaw depending on how much patience you bring to a 1985 action game — a modern player used to markers and mini-maps is likely to find the opening stretch disorientating in a way a contemporary 1985 player, used to reading a static screen for cues, apparently didn’t.

The film the game actually understood

It would have been easy for a licence built this quickly to lean entirely on the film’s most famous image — Stallone with a bow, or an M60 — and ignore everything else the story does. The design instead reaches for the film’s structure of captivity and rescue: an ally to free, prisoners to extract, an escape to survive, staged roughly in the same order the film moves through them. That’s a more faithful adaptation of a plot than most tie-ins bother attempting, and it’s plausibly the reason the game reads today as more than a reskinned arcade clone, even with a finale that doesn’t land as well as the stages before it.

What actually plays now

The C64 version, carrying Martin Galway’s score, is the one worth starting with — the music alone earns the reputation, incorporating themes from the film’s soundtrack into something that still sounds considered on the machine’s limited sound chip decades later. Play it expecting an open, route-choice jungle mission with a genuinely disappointing dogfight bolted onto the end, and the shape of the whole package makes sense: a licence that took its film seriously for most of its length, then ran out of ideas exactly where the film’s own climax gave it nowhere honest to go.

Why a licence rarely tries this hard

There’s a simple business reason most film tie-ins of the period didn’t reach for this much structural ambition: a licence carried a fixed release window tied to a cinema run, and a fixed window rewards a safe, familiar template over a risky new one. Copying Commando’s single-lane structure wholesale would have been the lower-risk choice, and nobody at Ocean would have been penalised for taking it. That a team shipped route choice, a rationed arsenal and a plot-accurate three-act structure instead, on the same deadline a safer choice would have met just as easily, is what makes the game worth revisiting on its own terms rather than as a curiosity that merely happens to share a famous name with a film.

Spoilers below

The bush-maze route through the opening camp is the harder of the two entry options to execute cleanly but preserves the most ammunition for later stages, while the rocket-launcher breach is faster and safer in the moment at the direct cost of the ordnance the gunship finale will make you wish you’d kept. Most players’ first serious loss comes from choosing the loud route early because it feels safer, then arriving at the dogfight with nothing left to fire back with — which is less a bug in the game’s balance than the arsenal doing exactly the job it was built to do, teaching a lesson about rationing that the mission’s later stages then collect on without warning.