Steel and Silence

LucasArts did not make many games like this. By 1995, they were known for adventure games — Monkey Island, Day of the Tentacle — not for precision action. Metal Warriors came from a small internal team working against that reputation, built by many of the same developers behind Zombies Ate My Neighbors, using an upgraded version of its engine. It wasn’t starting from zero. It was a system looking for a new idea.

Six Mechs, Six Different Games

What they built is closer to a systems experiment than a conventional run-and-gun. You control a pilot inside a mech suit — the Metal Warrior — with a full set of verbs: walk, boost, aim independently in multiple directions, eject, hijack. The last two are the game’s defining ideas. When your mech is damaged, you don’t die. You are thrown clear. The game continues, but now you are fragile, exposed, able to run, climb, and steal another machine if you can reach one. Survival becomes positional rather than purely mechanical. The battlefield becomes a set of opportunities.

What Each Machine Actually Does

The suits are not variants. They are roles.

The basic Drache is balanced — a machine you can rely on, with a clean firing arc and enough mobility to stay alive. The Havoc is heavier, slower, built around sustained firepower. The Ballistic launches arcing explosives that force you to think about space rather than line of sight. The Spider climbs walls and ceilings, turning the level geometry into a weapon. The Nitro trades durability for speed, darting across the screen in a way that breaks the rhythm of everything else. The Prometheus is a boss suit — rare, overwhelming, and briefly yours.

When your mech dies, Metal Warriors does not ask whether you have another life. It asks whether you can survive long enough to steal one.

The Mechanic That Changes Everything

Switching between suits is not cosmetic. It rewrites the encounter. A corridor that is trivial in the Drache becomes a trap in the Havoc. A vertical shaft that slows everything else becomes an advantage for the Spider. The game doesn’t just give you tools; it asks you to read the situation and choose the right one under pressure.

Why It Still Works

What holds up is the feel. Movement has inertia. Turning takes time. Landing has weight. When two suits collide, there is a sense of mass transferring between them — something most 16-bit action games ignore entirely. The controls are demanding without being opaque: shoulder buttons rotate your aim independently of your movement, letting you hold position and control space rather than simply react to it. It’s closer to a fighting game’s spacing than a shooter’s reflex loop.

The levels are built to support this. Not large, but layered — multiple paths, verticality, destructible sections, vehicles placed just out of reach. Enemies are positioned to force decisions: do you push forward in a damaged suit, or abandon it and try to take theirs? Do you hold a strong position, or risk movement to gain a better machine? The game rarely tells you what the right answer is. It trusts you to work it out.

Metal Warriors is also one of the few SNES games where multiplayer is not an extra mode but half the design. It is where the team solved a problem they couldn’t before — split-screen play, abandoned in their previous game because the hardware couldn’t handle it, finally working here. Two players, each choosing from the same roster of suits, fighting across maps that are deliberately constructed to create asymmetry. One player takes the high ground in a Spider; the other pushes with a Havoc through a destructible route. The eject-and-hijack mechanic becomes a mind game. Destroying the opponent’s mech is not enough — you have to control the space around the wreckage, or they will take yours instead.

And sometimes, the game becomes something else entirely.

Two pilots, both ejected, both armed with laser swords, circling each other in tight space — a fight that looks less like a shooter than a duel. It isn’t a mode. The game never calls attention to it. It simply allows it, and trusts you to discover what it becomes.

The presentation is functional, but precise. Sprites are large without being messy. Animation is readable under pressure. Damage is visible — machines degrade, break apart, fail piece by piece. Explosions are quick and heavy rather than decorative. The soundtrack, composed by Ron Soderquist, is restrained and industrial, more interested in maintaining tension than announcing itself. This is not a game trying to impress you with spectacle. It is trying to keep you focused.

The reason it’s overlooked is timing. Originally planned as a Nintendo release and later picked up by Konami in a limited run, it arrived in 1995 as attention shifted toward 3D. Earlier builds carried the name Battledroids, before that was quietly abandoned. There was no sequel, no continuation. Key members of the team moved on soon after. It exists as a single, self-contained idea — complete, but isolated.

SNES (1995)

Original hardware or accurate emulation. Two-player if possible — this is where the design fully reveals itself.

3–4 hours for the campaign · much longer if you stay for multiplayer.

Because very few games — then or since — treat vehicles as systems rather than skins. Because the eject-and-hijack mechanic creates situations modern action games still don’t attempt. And because Metal Warriors understands something most games don’t: that weight, restraint, and limitation can be more interesting than speed.

It was critically admired at the time, but timing and scarcity did the damage. A late SNES release, a limited print run, no sequel, no port, no line of descendants. If LucasArts had made three or four more games like this, Metal Warriors might be remembered as the first chapter of a tradition. Instead it stands alone: a late 16-bit action game about industrial force, mechanical vulnerability, and the constant possibility of losing your advantage. That isolation is part of its mystique. It is not the beginning of a line. It is the exception.