10 Things Everyone Gets Wrong About Darth Vader

You probably don't know Vader quite as well as you think.

Darth Vader Obi Wan
Lucasfilm

There's no denying that Darth Vader is one of the most iconic villains in the history of not only cinema but pop-culture and storytelling in general.

Even people who've never seen Star Wars can probably name him, and more than 45 years since he made his debut, he remains about as popular as ever.

Yet just because he's a beloved antagonist doesn't mean that fans have a 100% bead on everything about him, and in fact, may well have some crucial facts totally wrong.

This is admittedly the nature of Star Wars as a whole: the Expanded Universe - both canon and "Legends" - is so ridiculously vast that it's basically impossible for even the most devoted fan to keep up with everything.

And so, there's a good chance you, like most everybody else, has these 10 Darth Vader facts totally wrong, ranging from the basic design of his suit to supposed "plot holes" throughout the Skywalker Saga, and everything else in-between.

But from poring back over the movies and wider Star Wars lore, here comes the cold, hard truth about Vader...

10. His Suit Is Designed To Cause Him Pain

Rogue One Darth Vader
Disney

While there are no arguments that Vader's iconic armoured suit helps keep him alive by basically functioning as a mobile life support system, it's a mistake to assume that its functions are all primarily curative.

In actual fact, the suit is also designed to cause Vader pain. For starters, the helmet sticks needles into Vader's face whenever he's wearing it, with the intent of feeding his brainwave activity back to the central computer on the suit's chest.

Also in the Extended Universe, it's stated that Palpatine (Ian McDiarmid) designed the suit to be intentionally uncomfortable in order to keep Vader's rage free-flowing, and also to ensure that he could maintain a level of control over him while limiting his potential to rebel.

Though aspects of this have technically been jettisoned from the canon continuity and are now considered Legends factoids, it remains true that Vader's suit isn't an entirely restorative piece of wardrobe: it also causes him agony for a number of reasons.


9. He Shouldn't Remember C-3PO

Star Wars The Phantom Menace Anakin C-3PO
Lucasfilm

It's often cited as a plot hole by fans that Vader doesn't recognise C-3PO (Anthony Daniels) in the original trilogy despite the fact that young Anakin (Jake Lloyd) was revealed to have built him in the prequels.

You can chalk this up to George Lucas not having this revelation in mind when he made the original Star Wars movies, but if you look at the facts, it actually makes total sense that Vader wouldn't pay C-3PO any mind at all.

First and foremost, C-3PO isn't exactly the most distinctive looking droid in the galaxy: we've seen hundreds of similar looking droids throughout Star Wars media, so it's absolutely believable that Vader wouldn't give him much of a second thought.

And even if that's not good enough, it's easy to accept that Anakin simply repressed large swaths of his past following his transformation into Vader, whereby C-3PO simply wouldn't exist in his mind.

After all, as Vader told us in the recent Obi-Wan Kenobi series, he "killed" Anakin when he became Vader.


8. He's In The Original Trilogy WAY Less Than You Remember

Star Wars A New Hope Darth Vader
Lucasfilm

Vader casts such a long shadow - both literally and figuratively - over the original trilogy in particular, that it's easy to assume he has tons and tons of screen time throughout the three movies.

But in actual fact, that's not the case at all

Though precise timings vary, it's generally accepted that Vader has around 45 minutes of screen time throughout the original trilogy, gaining slightly more in each successive sequel.

Surprisingly, then, despite A New Hope being his introductory movie, he appears for less than 12 minutes of the two-hour film.

But like so many of cinema's finest villains, it's a classic case of Vader having such show-stopping screen presence that it feels like he's in all the movies so much more.

Like The Joker in The Dark Knight and Hannibal Lecter in The Silence of the Lambs, Vader has a haunting, spectral quality that allows him to linger around the periphery even when he's not physically in a scene.


7. He's Not Superior To Grand Moff Tarkin

Star Wars A New Hope Vader Tarkin
Lucasfilm

Another mistake casual Star Wars fans make is assuming that, outside of the Emperor - who is only briefly mentioned in A New Hope - Darth Vader holds rank as the Empire's top-line villain.

But in actual fact, Vader isn't at all superior to Grand Moff Tarkin (Peter Cushing) in the Empire pecking order. After all, it's Tarkin who commands the Death Star, has Alderaan obliterated, and actually gives Vader orders.

Now, that's not to say that Tarkin is superior to Vader either: Vader is basically outside of the Imperial chain of command and answers primarily to the Emperor, yet it's reasonable to assume that he deferred to Tarkin onboard the Darth Star both to appease Palpatine and out of respect for Tarkin.

After all, Tarkin's position surely commanded a measure of admiration from even someone as Force-choke-happy as Vader, right?

In reality they're basically separate but equal, and Vader knew that taking direction from Tarkin on his own ship was the right call.


6. He Can Survive Without His Helmet For A While

Star Wars Return of the Jedi Darth Vader
Lucasfilm

In Return of the Jedi, a dying Anakin asks Luke to help him remove his helmet, to which Luke (Mark Hamill) remarks, "But you'll die." Many fans have taken this as proof that Vader can't survive more than a few minutes without his helmet, but this actually isn't the case at all.

In several Star Wars comics, Vader has shown himself to be able to last hours and even days with the help of the Force, using hate alone to keep himself alive no matter that his helmet and suit were compromised.

This isn't to say that Vader would want to be without his life support apparatus permanently, given the obvious strain of using the Force to stay alive, but he can most certainly survive without the helmet for more than just a few minutes, even in the most hostile of conditions.


5. The "Choke On Your Aspirations" Joke Wasn't Out Of Character

Rogue One Vader Krennic
Lucasfilm

One of the most polarising lines in recent Star Wars history occurs in Rogue One, when Vader summons Orson Krennic (Ben Mendelsohn) to answer for the Death Star's attack on Jedha and promptly Force-chokes the hell out of him.

As Vader leaves, he cheekily tells Krennic, "Be sure not to choke on your aspirations, Director," which was immediately met with cringe-induced outcry from large swaths of the fanbase, who felt that it was out of character for Vader to make such a cute, punny quip.

But that's not really true. Consider some of the wise-cracks Vader made in the original trilogy, perhaps most memorably telling Captain Needa (Michael Culver) "apology accepted" after Force-choking him to death.

Plus, Vader isn't a literally robotic, inhuman entity, so what's the matter with a dark joke or two? It's not like Anakin (Hayden Christensen) was a total pillar of stoicism in the prequel trilogy, so it follows that Vader would have a penchant for gallows humour.


4. His Corpse Shouldn't Have Disappeared

Star Wars Return of the Jedi Vader
Lucasfilm

Another thing often brought up as a plot hole is Anakin's death - namely, why doesn't his body disappear when he passes away?

After all, we saw the bodies of Obi-Wan (Alec Guinness), Yoda (Frank Oz), and later Luke Skywalker vanish into the ether upon their deaths, so why not Anakin?

Moreover, why does his corpse remain in situ for Luke to burn?

The prequels actually explain this well enough, given that we see numerous Jedi die throughout the prequel trilogy whose bodies remain in place without disappearing - most notably, Qui-Gon Jinn (Liam Neeson).

The vanishing act isn't just something that all Jedi automatically know - Obi-Wan and Yoda specifically learned to become one with the Force from Qui-Gon.

That said, in the Legends continuity it's nevertheless stated that Anakin's body did eventually disappear, and that Luke ended up burning his empty armour on Endor.

But even accepting that despite its dubious canonicity, it isn't a given that those at one with the Force must immediately vanish the moment they die.


3. James Earl Jones DIDN'T Voice Him In Obi-Wan Kenobi

Obi Wan Kenobi Darth Vader
Lucasfilm

Vader of course appears throughout the recent Obi-Wan Kenobi Disney+ series, with many commending the great James Earl Jones for once again reprising his vocal role as Vader with sure, villainous relish.

Except, it's not quite true to say that Jones played Vader in the show - or at least, not in the conventional sense.

Indeed, that is Jones' voice we hear throughout the series, but the lines weren't performed by the 91-year-old actor, who recently announced his retirement from voicing Vader.

As a result, Vader's voice for Obi-Wan Kenobi was produced by Ukrainian machine learning startup Respeecher, whose software used Jones' voice from existing Star Wars media to generate new dialogue.

It's a testament to the quality of Respeecher's efforts that the end result is basically seamless, and it's easy to see why so many assumed that Jones, despite his age, was still performing the part - and in a manner totally consistent with his decades-old portrayals, no less.


2. The "I Am Your Father" Quote

Star Wars The Empire Strikes Back Darth Vader
Lucasfilm

Nothing separates an ultra-casual Star Wars fan from a more dedicated one quicker than getting Vader's iconic "I am your father" line wrong.

Through pop-culture osmosis, it's often repeated that Vader tells his son, "Luke, I am your father," when in fact, Vader replies, "No, I am your father," in reference to Luke's belief from Obi-Wan that Vader killed his dad.

Is it a nitpick? Perhaps - the context is more-or-less the same, and namedropping Luke helps assure people you're making a Star Wars reference in polite conversation - but considering how much we've surely all seen The Empire Strikes Back, we probably should know better.

But nobody's perfect - if a friend of yours parrots the slightly incorrect quote, don't give them too much hell over it. Either way, you'll struggle to find a more misquoted movie one-liner, or something that more people have gotten wrong about Vader.


1. Vader DEFINITELY Kills Obi-Wan

Star Wars A New Hope Obi Wan Vader
Lucasfilm

As iconic as the climactic lightsaber duel between Vader and Obi-Wan is in A New Hope, fans aren't all on the same page about the precise nature of Obi-Wan's exit from the scene.

After all, Obi-Wan basically appears to give up fighting, and when Vader swings his saber at him, he vanishes into thin air. Then the next time we see him, he's a Force ghost.

Some fans maintain that Obi-Wan left the physical plane before Vader struck him, but that's really true.

The ambiguous manner in which the scene is filmed doesn't really help provide fans with clarity, but given that Obi-Wan literally tells Vader moments earlier, "If you strike me down, I shall become more powerful than you can possibly imagine," it appears that he was genuinely killed by Vader and then near-instantaneously became one with the Force.

It's a hairs-splitting debate at the end of the day, but given that a necessity for becoming a Force ghost is, you know, dying, it's safe to say that Obi-Wan didn't find another way to just evaporate into the ether. He was, as he foretold, struck down.


Watch Next


In this post: 
Star Wars
 
First Posted On: 
Contributor
Contributor

Stay at home dad who spends as much time teaching his kids the merits of Martin Scorsese as possible (against the missus' wishes). General video game, TV and film nut. Occasional sports fan. Full time loon.