FANDOM


AT ATs onHoth

AT ATs attacking Echo Base on Hoth

Plot SummaryEdit

After receiving a vision from Obi-Wan Kenobi and fleeing the ice world of Hoth with his friends after an Imperial attack, Luke Skywalker travels to the marsh planet of Dagobah, where he is instructed in the ways of the Force by the legendary Jedi master Yoda. Meanwhile, Han Solo and Princess Leia make their way to planet Bespin, where they are greeted by Han's old friend, a shifty gambler named Lando Calrissian. Ambushed by the Empire shortly after their arrival, Han and his friends are imprisoned by Darth Vader. Luke leaves Dagobah to rescue his friends, and is met by Vader and a startling revelation. Written by Logic <logic@linux.slackware.org>

Errors and ExplanationsEdit

The ladder that Luke uses to climb into his cockpit when leaving Dagobah disappears. Yoda could have removed it using the Force.

As they are walking through Cloud City, Leia is between Han and Lando. As they come around a corner, Han and Lando have switched places.They could have switched before reaching the corner.

When Luke is running out of the beasts cave his lightsaber is on, when he is out, it is in his belt.Luke could have switched it off and attached it to the belt at the mouth of the cave.

During the Battle of Hoth, Luke says of the AT-AT that the armor is too strong for blasters and that wrapping the tow cables around the legs was the only way, yet when the first AT-AT is brought down using the cable a speeder blows it up using blasters.The blasters hit the weaker neck of the AT-AT after the armour had been compromised by the internal explosion. [Confirmed by various sources (including Andrew Darling in the Q&A section in an early edition of the Official Star Wars Magazine).

When Luke uses his lightsaber to cut open the AT-AT to throw the thermal grenade inside it, you can see the panel that he cuts away actually slides open. Luke actually uses the lightsaber to cut the lock on the panel.

The colours of the different buttons on Darth Vader's chest plate were red, green, and white in the previous episode. In this and "Star Wars Episode VI", however, one of the buttons is blue instead of green. This could be due to an upgrade to Vader’s life support equipment.

Yoda speaks of The Force: "Life creates it, makes it grow. It's energy surrounds us and binds us. Luminous beings are we, Not this crude matter [pinching Luke's shoulder muscle]. You must feel the force around you. Here, between you and me... the tree... the rock.. everywhere." In Star Wars: Episode I - The Phantom Menace (1999) Qui-Gon mentions midichlorians as "constantly speaking to us [Force-sensitive beings such as Jedi] telling us the will of The Force." (IMDB) This does not mean that midi-chlorians are The Force; it's clear that they are much more like messengers of The Force.

According to the credits, Luke's gunner in the Snowspeeder is named Dak. However, all other spin-off media (games, books, etc.) spells the name as Dack, which now seems to be official. Later versions of the movie (special edition, DVD release, etc.) do not correct this. Lots of names have more than one spelling - look at Shakespeare!

Towards the end when Chewbacca tries to go up the ramp of the Falcon and into the ship, C3-PO's head bumps one of the lights "attached" to the Falcon. As soon as he bumps it, it goes out. Maybe 3P0's head broke the bulb.


When Darth Vader uses the Force to throw things at Luke, one of them breaks the glass blowing Luke outside. This indicates Cloud City is pressurized. However, when the Millenium Falcon lands earlier, Lando is able to easily walk out the door, indicating there is equal pressure. (IMDB)Luke and Vader are battling in what is very obviously an interior portion of the city which is far more likely to be pressurized than the exposed outer hatches.

SourceEdit

Internet Movie DatabaseIMDB entry

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.