8 More Star Wars "Plot Holes" That Really Aren't
"BuT WhY DiDn'T ObI-wAn uSe fOrCe DaSh tO sAvE QuI-gOn?!" Well, here's why!
A franchise as gigantic as the galaxy far, far away - one that is still showing no signs of slowing down its growth - and a series with so many moving parts, is always going to struggle when it comes to consistency.
Even before numerous new creators stepped into the worlds of Star Wars to put their own stamp on this universe and occasionally created a few plot holes along the way, the great George Lucas himself occasionally dropped the narrative ball a few times, too, eventually adding moments into his prequels that resulted in a number of frustrating plot holes in the original trilogy - looking at you, Leia remembering her mother!
However, not all of said Star Wars "plot holes" are actually as confusing and nonsensical as they seem, folks.
Sometimes all it takes is picking up a comic book or other piece of media away from the big or small screen adventures, or just thinking a little longer about the issue in question, to discover that these incongruent moments are actually anything but.
So, after already looking at some other "plot holes" that really aren't here, strap in and get ready to learn why everything from a lack of Force Speed to a certain Mandalorian not being aware of the legendary Jedi actually makes all the sense in the world.
8. Why Don't Jedi Use Force Dash More Often?
While it may not have ever been seen during the original trilogy, George Lucas eventually revealed during the prequels that Jedi were capable of sprinting at frankly incredible speeds.
Well, he did once anyway.
After Qui-Gon Jinn and Obi-Wan Kenobi Force Dashed their way out of trouble early on in Episode I - The Phantom Menace, the super useful ability was actually not really seen on the big-screen again - though Mace Windu would use it in the Star Wars: Clone Wars animated micro-series.
But it sure would have come in handy when Kenobi was trying to catch up to his Jedi Master during their duel with Darth Maul, right?
In reality, the reason we never saw this particular version of a Force Dash again was probably because it didn't look all that great on-screen. But said Duel of the Fates plot hole actually does have a rather logical explanation within the universe, however.
You see, according to a number of sources away from the films, including the Mike Chen's Brotherhood novel, using Force Dash drains the user's energy for a short period of time. Meaning that if Kenobi did opt to use it to catch up to Jinn in the scene, he likely wouldn't have been much use to anyone and could have actually been a bit of a liability.
So, he just wisely chose not to.
7. How Did Darth Vader Not Recognise His Own Protocol Droid?
While some felt that the prequel revelation of a young 'Chosen One' being Threepio's maker was a rather fascinating development, others thought the detail just made Darth Vader's lack of reaction to the droid during the original trilogy seem a bit odd in hindsight.
But though Vader may never properly acknowledge his creation and the gift he ultimately gave to his beloved Padme Amidala on their wedding day in those movies, this plot hole of sorts was actually addressed in an Expanded Universe comic.
Said Star Wars Tales #6 shows Vader briefly getting his hands on his old droid after he was blown to pieces on Cloud City in Episode V - The Empire Strikes Back.
Here, before the pair ultimately end up in a scene together in that picture, Vader remembers his childhood for a bit, his mother, repairing Threepio at his home on Tatooine, and even takes a moment to touch the droid's head against his own mask. He'd then go on to order his men to give Threepio to Chewbacca, secretly showing there was still a bit of Ani knocking around in that largely mechanical body (via Reddit).
So, Vader did recognise his old droid - in Legends canon at least - just not in a moment that made it onto the big-screen.
6. How Did Rey Fly The Millennium Falcon?
Making its long-awaited return to the galaxy far, far away during the opening half-hour of Episode VII - The Force Awakens, the likes of Han Solo, Chewbacca, and Lando Calrissian were nowhere to be seen when the Millennium Falcon took flight here.
Instead, it was newcomer Rey who was sat in the cockpit, with Finn on turret duties as the pair fought off some First Order TIE Fighters.
But this pulsating sequence across the Jakku sands did leave a number of fans questioning how a person who'd never left that planet learned to fly such a rapid spacecraft.
Well, as it turns out, Rey actually used her scavenger skills to acquire some useful equipment.
Said equipment, according to the Rey's Survival Guide book by Jason Fry, was none other than a Y-wing computer display, with Rey eventually using this to run flight simulations and sharpen her piloting skills to pass the time.
It would have been nice to see this referenced in the film, sure. But at least the aforementioned guide was able to explain why she was so comfortable sitting in the driver's seat of the Falcon despite never having left Jakku.
No plot holes to see here, folks, just a ton of practice and ingenuity. So, move along.
5. Nobody Mentioning Ahsoka Tano In The Prequels
Back when the prequels first arrived in theatres all those years ago, Anakin Skywalker's apprentice hadn't even made her debut in the galaxy far, far away.
Today, though, Ahsoka Tano is seen as one of the most popular and compelling characters in all of Star Wars.
But with the Togruta Force-user evidently being present throughout the Clone Wars and being so important to Skywalker as a character, to many, the fact no one ever mentioned her in the prequels felt like a noticeable plot hole in hindsight.
The real-life reason for her not being acknowledged is obviously the fact that she was only introduced three years after those films had been released. However, as Star Wars: The Clone Wars unfolded, the animated series was able to finally offer an in-universe explanation for the Jedi Order strangely never talking about Tano and the character being absent during Episode III in particular.
In the series, the former Padawan of Anakin Skywalker left the Order after being wrongly accused of bombing the Jedi Temple, expelled from the Order, and then given the chance to return once her name had been cleared.
But the damage was done. She'd lost faith in the Jedi. And you can see why no one would want to bring up such an awkward moment in the aftermath.
Though she would reconnect with her old Master just before the events of Episode III, she'd then spend much of that Revenge of the Sith period fighting on Mandalore and eventually experienced the execution of Order 66 while aboard the Tribunal Venator.
In other words, The Clone Wars show successfully filled in what was once a Tano prequel "plot hole".
4. How Did Din Djarin Not Know About The Jedi?
The Jedi were present within this galaxy far, far away for thousands of generations.
They played a vital role in the Clone Wars, leading clones into battle against the Separatist forces and eventually being turned on by said troopers.
The icon that is Luke Skywalker, a Jedi, would ultimately help bring down the Empire during the Galactic Civil War.
And it's all that which made the fact that Din Djarin didn't know what a Jedi was during The Mandalorian series seem a little odd to some Star Wars fans.
Despite being rescued by a member of Death Watch during a battle in the aforementioned Clone Wars as a child, Mando didn't have a clue what a rock-floating peacekeeper was.
But the more you think about it, the more it makes sense.
On top of the Empire doing everything they could to erase the Jedi Order post-Order 66, the fact Djarin was raised by the Children of the Watch on Concordia explains why he wasn't aware of the Force-users. It was eventually revealed that this clan was tucked away from the rest of the galaxy, with Djarin not even knowing that other Mandalorians could take their helmets off.
So, with that in mind, Mando also being unaware of the Mandalorians' sworn enemy definitely checks out.
It was also shown all the way back in 1977's Star Wars that the Jedi and the Force weren't exactly things that were seen every day across the galaxy almost two decades after the Clone Wars - Han Solo didn't even believe in the latter!
Djarin was just one of the many who had never stumbled across a space wizard before.
3. Ki-Adi-Mundi's Appearance In The Acolyte Didn't Make Sense
It's safe to say that the return of one Jedi Master in the latest Disney+ live-action Star Wars series did not go unnoticed.
And we're not talking about the pointy-eared icon.
The arrival of Ki-Adi-Mundi in Episode Four "Day" in The Acolyte left some fans scratching their own - not quite as long - heads, however, with many suggesting that his mere presence was a plot hole.
In their minds, the Jedi Master's age was retconned here as the figure who died not long after Order 66 was first executed wouldn't have even been born based on what fans knew of the character.
At the time of Episode I - The Phantom Menace, it was said that Ki-Adi-Mundi was about 60-years-old. So, with The Acolyte being set 100 years before that movie, you can see the problem.
But this apparent "plot hole" is ignoring the fact that said age was only ever made official in the Legends continuity through things like CD-ROMs - his birthdate being 93 BBY in the Expanded Universe.
In the new Canon, though, Ki-Adi-Mundi's age has never been specified. And it's not that tough to accept that this Jedi Master was just one of the many Jedi Council members who were hundreds of years old - like Yoda, Yaddle, Yarrel Poof, and Oppo Rancisis - by the time of the prequels.
2. How Did Snoke Not Sense That Kylo Ren Was About To Kill Him?
Unquestionably one of the most shocking moments to go down in the sequel trilogy, the death of Supreme Leader Snoke during Episode VIII - The Last Jedi had many fans pulling a face similar to the one he did during that throne room scene.
And many of said viewers immediately questioned how Kylo Ren was able to pull a fast one on his Master here without the former having the slightest inkling he was about to join Maul in the bisected villain club.
But that's not entirely the truth.
Snoke was very much aware of and sensed Ren's intentions in this moment as Rey was positioned between them, that he was on the verge of striking down his "true enemy." That much is clear in the scene itself.
However, despite sensing all this, what he failed to realise in this moment was that his own senses and visions had betrayed him and Ren was actually about to cut down Snoke and not Rey.
So, Snoke was actually somewhat in the know, he just didn't clock that he was being fooled by his Apprentice and was said "true enemy" until it was way too late.
1. Why Didn't R2-D2 Tell Luke Skywalker About His Father?
C-3PO had a decent excuse for never explaining what had gone down during the Clone Wars to young Luke Skywalker in the original trilogy. He had his memory wiped, the poor droid.
R2-D2 on the other hand (wheel? leg?), didn't go through that procedure and his memory was still entirely intact in Episodes IV-VI.
So, what was stopping Artoo from explaining to Anakin Skywalker's son that his father was, you know, Darth Vader?
Well, this plot hole actually has a quite tragic answer if you really think about it, folks.
The iconic astromech obviously remains by Anakin's side throughout much of the Clone Wars - Skywalker and Padme Amidala exchanged droids as gifts at their wedding remember? And he even rocks up to Mustafar with a newly christened Darth Vader towards the end of Episode III - Revenge of the Sith.
But R2-D2 never actually sees or hears his own master be called "Vader." He was also told to stay with the ship on that fiery planet. So, when he then rolled off the planet with Kenobi, it was probably safe to assume that Skywalker had been killed.
And even if Artoo did see Skywalker argue and Force choke Padme in the moments before Kenobi began duelling with 'The Chosen One' - as shown in the movie's now non-canon novelisation - and possibly put two and two together and realised that Skywalker had become Vader, the droid keeping his mouth shut about the whole ordeal also makes sense.
Would you really blame him for not wanting to relive such a traumatic series of events? Conversely, maybe this little scamp just enjoyed carrying around the galaxy's biggest secret and keeping it to himself.
That's likely why he didn't pipe up when Kenobi was telling lies to Anakin's son, then, and why he never bothered to drop this important information before Skywalker finally learned the truth in Episode V - The Empire Strikes Back: this loyal droid seemingly either didn't know a thing about Anakin's survival and new life as Vader, understandably didn't want to talk about the horrible things he'd seen, or just didn't feel it was really his place to tell Luke about his daddy.