Wikia Gaming

Star Wars: The Empire Strikes Back (NES)

27,364pages on
this wiki
Add New Page
Talk0 Share

Star Wars: Empire Strikes Back is a video game released for the Nintendo Entertainment System in 1991. The object is to destroy an Imperial Probe Droid, escape a Wampa-infested ice cavern, fight during the Battle of Hoth, meet Master Yoda on Dagobah to train with him, and attempt to rescue your friends in Cloud City from Darth Vader.

Playing as Luke Skywalker, you can fight with a blaster pistol or a lightsaber. You can also board a snowspeeder during the Battle of Hoth. As Luke learns about the Force, he develops multiple Force Powers to help during the misson.

The NES version was released in 1992, the same year as JVC's Super Star Wars for the Super Nintendo Entertainment System. As Empire was released towards the end of the NES's lifecycle, a corresponding sequel to the film Return of the Jedi was never developed or released.

This is the second of three video games released under the Empire Strikes Back title for home video game systems. It was preceded by a version for the Atari 2600 and succeeded by Super Empire Strikes Back for the SNES.

A "port," or conversion, of this game was released for the Game Boy. That product was reprinted and distributed by several publishers over the course of three years.


The Empire Strikes Back was a side-scrolling action game that was broken into ten areas, or levels. The level structure is comparable to such titles as Metroid, with multiple paths and slightly nonlinear progression.

Level 1: Hoth

Level 2: The Battle of Hoth (vehicle-based level following the design of the Atari 2600 game)

Level 3: Rebel Base

Level 4: Dagobah

Level 5: Jedi Training

Level 6: Bespin Approach (vehicle-based level)

Level 7: Bespin

Level 8: Slave 1

Level 9: Rescue of Leia

Level 10: The Carbon Freezing Chamber

Ad blocker interference detected!

Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.