Flashback: In Defense of Namco's Bizarre 1987 'Star Wars' Game

Making sense of the most nonsensical Star Wars game ever

Load Previous
Namco got crazy with its story (fan-translated screenshot). LucasArts just got wrong with it3/8


There's no doubt that Namco's Star Wars doesn't pay much heed to the plot of A New Hope – it just borrows the movie's very basic structure with some diversions like the water planet of Iskalon (ripped straight out of the pages of Marvel's Star Wars #74) along the way. "As an action game, it did everything right in terms of developing a playable game," says Kawada. "But the concessions that had to be made in terms of story and characters in order to make it a game, I think, were difficult for some fans of the movie to accept."

Still, that doesn't mean Super Star Wars' interpretation was without its own imperfections in adapting the tale. Though basically faithful in structure, it made some amusing changes worth pointing out.

Early on, Luke is in the desert when he simply encounters C-3PO, who asks him to help liberate his counterpart from the ruthless Jawas. "Sure, I'll go commit some mass genocide," Luke probably thinks, as he agrees to assist this droid he's never met. Once R2-D2 is freed, Leia's "help me" message says to relay the Death Star plans to her father on Yavin (not Alderaan). Despite these clear instructions, Obi-Wan tells Luke they must go to save the princess, whose whereabouts are never actually revealed to them. With no mention of a blown-up planet en route, the Millennium Falcon finds its way to the top-secret battle station no one has ever heard of to rescue Leia. As our heroes depart, Obi-Wan fights Darth Vader in a cutscene, telling him the "strike me down" line – but no striking down occurs – so as far as we know, he's still on the Death Star once Luke blows it to smithereens. And come to think of it... shouldn't Bail Organa be alive and well on Yavin?

Back to Top