Star Wars: The Last Jedi
Star Wars: The Last Jedi mistake picture

Continuity mistake: When Finn is going to an escape pod to run away, he puts his pack down in front of it, seen again in a later shot. When Rose realises he's trying to run away, his pack has moved itself inside the pod.

Awesomolocity
27

Continuity mistake: During the throne room fight against the red-armoured guards, one of them splits his weapon into 2 blades. In the shot where he gets Rey into an arm lock, the blade in the guard's left hand vanishes from the scene completely, in the middle of a shot. The hand that held the weapon is obscured by Rey's body at the point when the disappearance happens. It could be that the actor dropped it (a strange thing for an elite fighter to do), but then the blade is nowhere to be seen on the floor in the wider shot when Rey kills him.

James Rice
12
Video

Other mistake: In Finn's attempted sacrifice, there are plenty of logical inconsistencies. First, Rose's pod is to the side or behind Finn, but manages to beat Finn's pod to the cannon. The collision had a similarly high chance of killing Finn as would ramming the cannon. Finn then carries Rose back to the hideout faster than it took the speeder pods to reach the cannon.

12
Star Wars: The Last Jedi mistake picture

Continuity mistake: As Poe Dameron starts his attack run against the Dreadnought we initially see him from the side and his helmet microphone is folded out to the left away from his face. The camera cuts to directly in front of Poe and the microphone is now folded in and directly in front of his mouth. (00:03:25)

5

Continuity mistake: After the big cannon blast to open the gate the ground turns red as the salt is blown clear, but when Luke is fighting Kylo it's white again.

oswal13
8
Upvote valid corrections to help move entries into the corrections section.

Suggested correction: The salt is falling from the sky constantly during this bit. We don't see that set-piece for about 2 minutes after or so. Enough salt has accumulated onto the ground during the time that has passed.

1

Plot hole: The entire plot revolves around the First Order chasing the ships, waiting for the Resistance to run out of fuel. They could have easily destroyed the Resistance's fleet by sending a Star Destroyer or two around to cut them off from the other side and blast them into oblivion.

6
Upvote valid corrections to help move entries into the corrections section.

Suggested correction: This is more of character stupidity than a plot hole.

Quantom X Premium member

Maybe. But if the First Order does this the entire plot of the movie as it is is ruined. So, maybe both?

9

Just because you didn't like the movie doesn't change a character stupidity into a plot hole.

lionhead

What prevents a character's stupidity from being a plot hole? Is it wrong to want competent villains? If a character is supposed to be intelligent (let's say, a naval commander or military leader) and has the capability to achieve his or her objective with an obvious decision a character of his or her stature should make but does not and it is the only reason the plot of the movie still exist, is it not both a plot hole and character stupidity? Not just Hux, Snoke, Kylo, and every other First Order officer failed to realise this. How? It does not make any sense. At the very least try to explain in the movie how the FO let the Resistance get away because they refused to let Star Destroyer make a few hyperspace jumps and cut the Resistance off.

7

Hux is an idiot, Snoke is a fraud and Kylo doesn't really strike me as a strategic mastermind.

lionhead

Hux only really becomes an idiot because of this movie. In TFA, he is an established military officer who does come across as more feared and respected. The change in this movie is then character stupidity and/or a character mistake that creates a big plot hole from the start.

9

Well the new movie puts a whole new light into that. Changes the whole discussion.

lionhead

So they retconned to correct this mistake? Still makes it a mistake in my opinion. Especially since it is not just Hux who could have been a better leader. Any FO military officer could have brought it up and executed that idea.

7

To answer the question: a plot hole is something that contradicts something already established in the film that's done to move the plot along or resolve an issue. A stupidity is a minor plot hole, but can also be character acting contradictory to what's been established, usually to keep the plot going. A character mistake is a character making a mistake or error they shouldn't have (usually because the writers don't know the right answer). Characters acting stupid or irrationally or making human errors is not a valid movie mistake.

Bishop73

So by this, it is a plot hole because the Star Destroyers can jump in and out of hyperspace and could make that jump to cut the Resistance off. It is character stupidity because Hux is established as a high ranking military officer in TFA and thus should know basic military strategy along with all of his fellow officers. I think if a character acts stupid which goes against their established personality and traits without a good reason, it is very much a mistake. Hux was not pressured into an irrational decision. In fact, it is the most calming battle to ever take place in Star Wars. There is no reason for him to be this incompetent. He is only this way because Rian wrote him this way, which on your list is a character mistake too. When the general audience is a better military tactician than the FO Commander in the movie, it is a bad sign.

8

The problem is that we as the audience know the Resistance will find a way out of this situation. General Hux believes he has the Resistance trapped and they have no escape. In his mind, the plan was working perfectly well. There's no reason to alter the plan. It's not like they are under a time crunch and need to destroy the ships as quickly as possible. By moving the cruisers out of range and crawling away, it was clear to Hux that the Resistance had run out of options. Hux doesn't need to do anything differently in his mind, so he doesn't. It only seems stupid to us because we know the heroes will find a way out because heroes always do.

BaconIsMyBFF

I am sure the First Order is well aware that the Resistance is doing all they can to find an escape, however unlikely it is. However, contrary to the audience, they do not know how they plan on doing so. All the more reason for the First Order to blow the Resistance to bits while they still can. What is the benefit of just waiting for the Resistance to run out of fuel in the first place? Wouldn't it just be better to end them swiftly? Also, it is not just Hux. There are other military officers and you would think there would be a few of them who would want to destroy the Resistance while the opportunity was present. Its decisions like these that make you wonder how the First Order gained so much power in the first place.

7

It is just Hux. The captain of the Dreadnaught makes it clear that Hux is in general command, as he is irritated that Hux did not scramble fighters as soon as Poe's X-Wing showed up. Overconfidence has been a staple of Star Wars villains from the very beginning, and if it's a movie mistake here then it's also a mistake that Tarkin doesn't evacuate the Death Star; or that Vader doesn't force choke Luke on Bespin instead of trying to trap him in carbonite; or that Jaba doesn't shoot Luke Skywalker instead of taking him to the Sarlaac pit; etc.

BaconIsMyBFF

Comparing Tarkin's overconfidence to Hux's actions is practically insulting. The Empire believed the Death Star was indestructible until the flaw was discovered during the Rebels' attack run. Even with this flaw, the chances of the Rebels' success was incredibly slim. The Rebels have already failed multiple times and the Empire was mere seconds away from ending the Rebellion for good. The probability of the Empire ending the Rebels once and for all was almost a certainty and it was logical to take the chance. Tarkin may have been overconfident, but he had a right to be. The Vader example is dumb too. The Emperor ordered Luke to be taken to him alive. To do that, they were going to entrap him in carbonite. That was Vader's goal, not to kill him with a Force choke. Jabba is a sadistic showman, as seen when he fed Oola to the Rancor. When Luke is captured, he created a show in which he can enjoy. How Luke died was just as important to him as Luke dying.

8

Tarkin said he wanted to destroy the Rebellion with one swift stroke. Key word here being swift, not lazily waiting for some gas just to run out. If Tarkin was in charge of the First Order instead of Hux, the Resistance would have easily been destroyed, no questions asked. Having Hux betray what he was supposed to be from TFA by being a passive, ignorant, and incompetent leader causes the FO to be nonthreatening, terrible villains, and defeats any suspense in the plot. It's illogical for the audience to believe that a military commander could be this stupid.

Completely and entirely disagree with your assessment. Tarkin's overconfidence and Hux's overconfidence both come from the same belief: that their enemies have no means of victory. Both men believe they have already won and it is only a matter of time before they win. Tarkin is flat out told that there is a chance that the rebels will destroy them and he chooses not to evacuate. This overconfidence is a staple of every movie in this series because the major theme of an underdog triumphing over the odds demands this. I did not mean that Vader should force choke Luke to death, but once the plan to freeze him fails he certainly could have tried harder to incapacitate Luke. By not doing so he allows Luke to escape. This isn't dumb, it's just overconfident. Jabba choosing to put on a show rather than just shooting his enemies is the very definition of overconfidence, and it's honestly strange that you seem to be arguing that it isn't.

BaconIsMyBFF

I was arguing against your assessment of Vader and Tarkin and explaining Jabba's view and how it differs from how Tarkin and Hux should go about things. Jabba is an overconfident crimelord and thus has different traits then a military leader so it is unjust to compare him to Tarkin and Hux. Tarkin was given that information mid battle a mere minute away from wiping out of the Rebellion. Here it is believable of him to assess the situation, see the Rebels have already failed multiple attempts, and that the Rebels chance for success was minuscule and waiting was the best option. Hux's ability to end the war is literally right there. Not minutes away, seconds away if he would have just commanded a ship to cut them off. There is no benefit in waiting, whereas Tarkin is operating a Death Star and must wait as it moves differently (slower, less maneuverable) than a Star Destroyer. Even if they have the same belief, Tarkin acts competently and Hux acts unbelievably moronic.

4

I think that's where I'm having a problem with your statements. I don't believe that Hux acted "unbelievably moronic." His plan was working perfectly fine. Just because he didn't wipe out of the ships as fast as he possibly could doesn't make him a moron, or a bad military leader. Hux had just lost Starkiller Base and his Dreadnaught, so it is perfectly reasonable for him to take a safe approach with destroying the remaining Rebel ships; picking them off one-by-one at no risk to his fleet whatsoever. His plan works absolutely fine and the few Rebels that do survive only do because Luke Skywalker projects his image across space to stall Kylo Ren. "Military leader" doesn't mean "infallable" and it certainly isn't a gap in the film's logic, especially in the Star Wars series, to have a leader make questionable decisions in hindsight.

BaconIsMyBFF

You just said Hux was an extremely risk adverse military leader, whereas good military leaders must deliberately accept tactical risks. However, there is no risk here. Destroying the Resistance fleet would have been easy since all of their fighters and bombers were already destroyed fighting the Dreadnaught. Regular sight should have been able to see that waiting for the Resistance to think up an escape plan was a bad idea. Especially since the First Order knows the Resistance has a map to Luke Skywalker and his arrival could completely turn the tide of the battle. Logically, the First Order should destroy the Resistance fleet before Luke could arrive. The only explanation, which makes for a bad movie, is that Hux is unlike what he was represented in TFA and is an incompetent leader. From the beginning, he was never meant to be like is TFA self. He did fall for a "your mama" joke to start the movie and let a Dreadnaught die from the slowest bombers in the galaxy.

4

I did not say that Hux was "extremely risk averse." I said that Hux took a safe approach. Having Hux plan to defeat the Rebels before Luke Skywalker could show up would have also been out of character. The villains in the Star Wars stories consistently believe that not even a powerful Jedi could stop their plans when they have convinced themselves they've already won. Snoke says as much during this very film.

BaconIsMyBFF

You said Hux likes playing it safe, that means he is a risk adverse military leader, or at least made a risk adverse decision when there didn't need to be one. So it is now out of character for Hux to defeat the Resistance until Luke shows up? At this point, the only reason it makes sense for Hux to act this way is what was revealed in TRoS, which would be a retcon to cover the mistake in this movie. I find your villain statement more of opinion then truth. It may only make sense in this trilogy. Palpatine is the true villain of Star Wars and his big plan to rule the galaxy found it necessary to kill all the powerful Jedi, so he obviously was not convinced he could win with them alive. As Emperor, discovering a potential Jedi in Luke was treated like an actual threat, maybe the only true threat. The Emperor wants Luke dead/capture in ESB. The Emperor tries to turn Luke in RotJ. The Emperor does believe he can turn/defeat Luke, and he would have defeated him if Vader hadn't intervened.

4

You are putting words in my mouth. I never said that Hux "likes playing it safe." I said that he took a safe approach in this particular situation.

BaconIsMyBFF

I'm gonna say it here too, the new movie puts it all in a whole new light. So just wait till you see it. (not that it's particularly good though).

lionhead

We do not know exactly when this character decided to do that. Could have been before or after these events. Most likely it occurred after Snoke died and Kylo took power. So that is just speculation. If this character's decision does occur before the events of this movie, then it is a retcon to cover this mistake, meaning the mistake exists.

7

Suggested correction: Why would they need to? They easily outgun what remains of the Resistance, and they're patient enough to wait for the ships to run out of fuel. The First Order was overconfident, but they were not wrong about their plan working.

What is the benefit of the First Order waiting? It would be better to take out your enemy swiftly when given the chance. Especially since we are told this is the last of the Resistance. Destroying these few ships would then end the war and give the First Order control of the galaxy.

8
Star Wars: The Last Jedi mistake picture

Continuity mistake: When Rey is following Luke up the hill in the infamous milk scene, her holster switches from being on her right side, to her left, and then back again.

4

Plot hole: Luke deliberately says he does not want to be found and came to Ach-To to die in The Last Jedi, but The Force Awakens is all about finding a map to Luke Skywalker. Why would Luke leave a map when he never wanted to be found?

4
Upvote valid corrections to help move entries into the corrections section.

Suggested correction: This is a question, not a plot hole. Luke went to find the first Jedi temple. The location of the temple is what they were ultimately needing to try and locate Luke. The map that has the temple was already created before Luke went to the temple, he did not create a map where to find him and then secretly hide it away.

Bishop73

It is a plot hole statement in the form of a question. It ultimately is a continuity error between Episodes 7 and 8. TFA never mentioned it as a map to a Jedi temple Luke might be at. The audience is told in that movie that it is a map to Luke Skywalker. It is believed by the end of TFA that Luke wants to be found if they needed him. It is only after Rian Johnson goes against what JJ Abrams planned for Luke that this error becomes prominent. If this is simply a map to the first Jedi Temple, then the Resistance is betting a lot on the chance Luke went there and still there after all these years.

8

In The Force Awakens, Kylo Ren refers to the map as a navigational chart recovered from the archives of the Empire. According to the spin-off books, the Empire were using it to find the first Jedi Temple and destroy it. So the map was not in fact left by Luke. Since Luke is believed to have gone looking for the first Jedi Temple, my guess is that whoever discovered the map realised where it led to, and knew that was where Luke was believed to have gone, and thus referred to it as a map to Luke.

1

What other choice do they have? The know where he wanted to go. If the do not find him there then the have someplace to look abound for clues as to where he went to afterwards. Also it is not like if he is not there they are stuck and cannot return to the resistance fleet.

A map to the first Jedi Temple is a perfectly fine explanation for what the map actually is and if the Resistance thought Luke was there, it was worth the risk to go there and look for him. However, the very identity of the map seems to change between movies and it is introduce in TFA as a map to Luke, not to a Jedi Temple. So in TFA it is a map to Luke and in TLJ it is now a map to a Jedi Temple Luke might be at. That is the problem, a discontinuity of the map's identity between the two films in the trilogy. This stems from the two directors' view of Luke in this trilogy also being completely different.

5

They think it's a map to Luke, or believe it, or someone else thought it was. It's not a discontinuity, just a semantic difference or miscommunication.

Jon Sandys Premium member

This movie or TFA should have explained this miscommunication as it comes across as a miscommunication to the audience and not to the Resistance. There is nothing in either film to show it is a map to a Jedi Temple Luke might be at. A miscommunication to the audience is poor writing, but since this occurs between two movies, it is a continuity mistake. This mistake is obviously due to the character of Luke changing when it moved on from JJ to Rian. This change makes the plot of TFA more confusing, but ultimately a continuity mistake is a much more just denotation for this than plot hole.

4

Since the Jedi Temple and Luke are in the same place the map is both a map to Luke and to the Jedi Temple. Someone looking for Luke will see it as a map to Luke, someone that is force sensitive may see it a a map to the temple.

This statement does not answer anything. The map was either designed to be a map to where Luke said he was or as map to a Jedi Temple where Luke may be. Not both. Both places can be the same, but the identity of what the map is remains as one or the other. Otherwise we are again back to a bad miscommunication in the Resistance and bad miscommunication to the audience that is just bad writing. Since it is stated in TFA that is is a map to Luke, the audience should believe it as such. It is never described as a map to a Jedi Temple Luke might be at. The continuity error and plot confusion comes from the fact that in TFA it is a map to Luke for when he was needed and in TLJ it is a map to a Jedi Temple that the Resistance hoped Luke would be at. Since TFA came first, it takes precedent and all of Luke's lines of not wanting to be found do not make sense.

4

While initially the audience is told it's a map to Luke, we find out later that the map leads to the first Jedi temple. This is nothing more than building suspense, which doesn't constitute a plot hole. While one could argue it was only after changes to the script or a director's choice that changed what the map was designed to be, the original mistake is still not valid because Luke never created a map to where he was going and then hide it as suggested.

Bishop73
Video

Plot hole: By having Admiral Holdo perform her infamous hyperspace ramming stunt, Rian Johnson created a continuity problem with the rest of the Star Wars universe. Since this maneuver was successful, every space battle before and since should only include a droid piloting spacecraft ramming enemy bases through hyperspace. This tactic would have been more cost effective and less risky than full on space battles seen in previous films. This tactic would no doubt have been tried in a universe filled with space battles often with disposable troops on both sides, such as in the Clone Wars. The Death Star did not need a successful trench run to be destroyed, just an X-wing with a droid ramming it at hyperspeed.

4
Upvote valid corrections to help move entries into the corrections section.

Suggested correction: I think it's a one in a million shot. The damaged caused crippled the large ship but didn't fully destroy it and the other ships destroyed were caused by the debris from the bigger ship and ramming ship. That's just bad tactics. But in the case of for example the death star I doubt highly that ramming it with hyperspace jumps will cause significant damage. It's not like you are firing an armor piercing round and I'm pretty sure ships are equipped with all sorts of anti-debris protection. Plus I think it's bloody difficult even at that range to aim correctly at an enemy ship with a hyperjump.

lionhead

NASA engineers have to be aware of space debris orbiting the Earth that is the size of small particles because when they are orbiting at 18,000 mph around the Earth, they can cause significant damage to spacecraft. Turn that speed up to near or past the speed of light as in hyperspace and an X-wing should be enough to significantly cripple a Death Star sized object, if not completely destroy it. Yes, ships have shields, but these are ray shields meant for cannon fire. Both RotJ and TFA show that a ship can penetrate these shields (TFA displayed it at hyperspace speeds no less). Aiming should be as easy as punching the location into a navicomputer as done for traveling. It is also easier to hit and less difficult to aim at large or close objects, like Star Destroyers, Death Stars, or planets and moons.

7

"The damaged caused crippled the large ship but didn't fully destroy it" This is what was introduced to the fiction by the director. You can dislike that if you'd like but it is not a "mistake."

This was the outcome. Hyperspace ramming was what was introduced. The outcome was also grander than simply crippling a ship. It split the ship in two and the entire fleet or a large portion of it ended up being destroyed. Without a worthwhile explanation as to how this is possible now but not previously, it also introduces plot wholes in the previous movies.

6

You are talking about a long time ago in a galaxy far far away. You simply don't know. Hypespace is not as simple as going faster than the speed of light. They hardly have shields, I'm talking about armor protection, bulkheads, bulges, space armor, netting. Whatever.

lionhead

Hyperspace as defined by Wookiepedia is an alternate dimension that could only be reached by traveling at or faster than the speed of light. So at this stage in the ramming stunt, it is as simple as traveling at or past light speeds as the ship has not yet entered the hyperspace lanes in the parallel dimension. So now the force the FO ship faces is the mass times acceleration and since it is traveling past lightspeed, the force would be extraordinary regardless of the mass. It would be even harder to believe an armor or anything else that could withstand that force, even on a Death Star sized space station.

7

To clarify, this is the hyperspace that Rian Johnson created. Before it was less clear, but the standard that has been followed since the beginning was one could not ram opposing ships with it while entering hyperspace lanes. Han Solo talks about this in A New Hope. Rouge One even has ships just entering hyperspace killing themselves on incoming Star Destroyers. This is the more faithful representation of what hyperspace travel was. Rian Johnson has completely rewritten what occurs in hyperspace which breaks Star Wars canon.

3

The official explanation is that the Raddus had special experimental deflector shields and that is why it worked. With normal shields it would not have worked.

Source? Is it said in the movie somewhere? So one should expect the Resistance to use these "special experimental deflector shields" and hyperspace ramming to combat the hundreds of Star Destroyers in The Rise of Skywalker, correct? Should be pretty effective. Weird that all the promos have the Resistance fighting them the old-fashioned way.

9

It is in the novelization of the movie.

Using a novel to correct a mistake a movie makes still makes it a movie mistake. Movies should not need books, comics, or videos games to explain their obvious flaws.

7

All I was saying is that it was a one in a million shot and that doing it requires a lot more than simply pointing towards the enemy and activating hyperjump. If anyone can do it and it can destroy entire fleets, then everybody would do it. But they don't, so it's not that simple. Since that is a fact, it's not a plot hole.

lionhead

That is why it creates a plot hole because the movie never presents it in a way that only this ship at this time in this way can do it. It comes across as anyone can do it so why didn't anyone else do it in the thousands of years that this universe has existed through the countless wars that have taken place? Saying it is not that simple is not a fact, its an opinion. I watched it and it looked pretty simple. It comes across as anyone can do it, so everyone should have been doing it, thus the plot hole.

7

This scene doesn't create a plot hole since, in the film, nothing was established to show this wouldn't work. Nor would it create a plot hole unless it was previously shown that unmanned ships were used as a regular tactic to destroy bigger ships. Plot holes are when something occurs that contradicts what the story itself (usually as a plot device to further the plot along or conclude the plot).

Bishop73

It coming across as simple doesn't make it simple. The simple fact of the matter is that this fictional universe works that way, in the other movies it hasn't happened so it's not simple. It's as simple as that. In any case it would be a plot hole in those movies, not this one. Look, if you want everything to be logical then these movies will be nothing but automated ships ramming into each other left and right and you still want the story to be told? I don't think so. So, you want to explain why they don't ram everything and you got it. Deal with it. Otherwise the fact they use hyperdrives is a plothole then as well.

lionhead

In this fictional universe, hyperspace did not work as weapons until Rian Johnson changed hyperspace for this movie's plot convenience. In doing so, Rian broke the standard canon that each previous movie followed. This is why its a plot hole in this movie and creates a discontinuity for the entire saga. Everything does not have to be understood or compared to our real world, but each fictional universe has its own set of physical laws and rules that each form of media in that universe needs to follow. Hyperdrives are not plot holes because they existed since the beginning of Star Wars and have a certain set of standards they follow that are understood. Changing these laws without a logical or worthwhile explanation in the film is ultimately disrespectful to the source material. The very idea that you brought up in that this creates plot holes in all the previous films proves that this scene is a terrible addition to the saga.

7

Seems to me like you just dislike the scene. Thats fine and I can understand you feel its a continuity. But it is not a plot hole for the movie.

lionhead

It is more of a continuity error that creates plot holes in the previous movies, so it could be labeled better. However, if we view Star Wars as one story like George Lucas did, then it would be a plot hole for Star Wars as a whole. If it was successful in explaining how they could do it now, but not a few years ago, then it would have been fine, more or less. It failed to do so making it a mistake, no matter how visually pleasing it was.

6

If it were a one in a million shot, then Hux would not have panicked and ordered the cruiser shot down immediately. Furthermore, the Resistance could have used their two escort ships, which were going to run out of fuel and be destroyed anyway, to try the same thing.

Suggested correction: Just because it worked on this occasion, doesn't mean it would always work. It also hadn't been attempted before. It's not a plot hole that they didn't destroy the Death Star like this, since nobody in the rebellion considered it.

But why did no-one in the Rebellion consider it? It was their most desperate hour. They were in similar desperation as the Resistance in The Last Jedi, if not more so. Their were similar desperate times in the Clone Wars when both sides had troops of disposable clones and droids. They did not consider trying it then? They were wars occurring before that and no-one thought about using hyperspace as a weapon? It is illogical to think that there was no-one in the history of that universe that would never even consider using hyperspace as a weapon. The reason it was not considered was before Rian Johnson rewrote it, hyperspace did not operate like that. Plain and simple. Rian Johnson rewrote how hyperspace works, creating a plot holes and discontinuities for the entire saga.

5

Other mistake: Maz Kanata's message is somehow not intercepted by the First Order. It is also projected from various angles and follows her around during her shootout, making one question who is filming the call in the first place?

3
Upvote valid corrections to help move entries into the corrections section.

Suggested correction: Since this particular technology is not fully understood (and is fictional, to boot), this "mistake" is based upon pure speculation and should be disregarded.

zendaddy621

Disrupting transmissions has existed in the Star Wars universe chronologically as early as Episode 1. The First Order had the means to do this but did not. If they were at all competent, they would have disrupted all Resistance transmissions.

5

Given the training remote seen in the first move it would be rather easy to say how Maz was able to "film" the call.

1

True, However, those droids were not subjected to a battle when they are shown in Episode 1. So filming the call is plausible. However, there is no way the call should have gotten to the Resistance without it being disrupted or intercepted by the First Order.

1

Again, fictional technology, and no firmly established rules as to how it works; the same could be said of pretty much all the tech depicted within the SW films (lightsabers, droids, hyperdrive, etc). Probably best just to go with "suspension of disbelief" here.

zendaddy621

But you are wrong. There are established rules on how certain technologies operate in Star Wars through examples in the previous movies, TV shows, etc. Even if we do not know how they work, we know what they do. Disrupting communications and transmissions is a big plot line used in Episode 1, chronologically the earliest Star Wars film. In Return of the Jedi, the Empire jams the Rebels sensors so they do not know if the shield is up or down. The technology exist and the First Order should have used it on the Resistance.

The technology existed forty years ago. Finding a way to thwart the jamming would be a high priority of the rebels' scientists and engineers.

That's an assumption. If that is the case, because of the previous films it needs to be explained in the movie. Otherwise, it goes against established canon, which is a continuity error. You could also just as easily say the First Order developed an unstoppable way to intercept transmissions in those 40 years. It is also an assumption that thwarting transmission jamming would be the Resistance's highest priority. If anything, technology has not progressed very far in this trilogy as the FO is still fighting with TIE Fighters and the Resistance still uses X-Wings.

Continuity mistake: When Rey goes into the dark place that she was drawn to, she reaches out to the cracked glass wall with her right hand. In the next shot she is touching it with her left. (01:14:23)

2

Other mistake: During the big battle between Kylo Ren and Luke Skywalker (as a force projection), Luke appears with his blue lightsaber. While I assume that a force projection probably appear any way he wants, and he did choose to look younger, Luke had lost his blue lightsaber decades ago during his battle with Vader on Bespin Cloud City. He had already built a new green one by the time Return of the Jedi started, so why would he appear with the blue one? It should have immediately given away to Kylo that he was a force projection and not the real Luke.

2
Upvote valid corrections to help move entries into the corrections section.

Suggested correction: This isn't a mistake. He knew that his blue lightsaber still existed because Rey brought it to him. He chose to show the blue lightsaber because it belonged to Anakin and Kylo Ren was obsessed with it. He knew that Kylo Ren would be angry at Luke wielding a lightsaber that looked like Anakin's and that rage would help keep him distracted. Here is a quote from Rian Johnson regarding this: "He knows that Kylo's Achilles heel is his rage, and so that's why he kind of makes himself look younger, the way Kylo would've last seen him in their confrontation at the temple, and that's why he decided to bring Kylo's grandfather's lightsaber down there - the lightsaber that Kylo screamed at Rey, 'that's mine, that belongs to me.'"

Continuity mistake: Towards the end, Leia is talking to Rey in the hanger. In a shot facing Leia she looks down, then we cut to Rey and Leia, seen in profile, is instantly looking up, straight ahead.

Jon Sandys Premium member

Continuity mistake: Rey steps forwards to hand over Luke's lightsaber, then takes a couple of steps back. The shot cuts and they're suddenly much further apart.

Jon Sandys Premium member

Continuity mistake: When Rey is practising with the lightsaber on Ahch-To, she swings it very close to a towering rock. The camera then cuts to a wide shot showing her with the lightsaber, now feet away from the rock she was only inches away from in the prior shot.

Continuity mistake: When Poe realises that Holdo is fuelling up the transports, he is suddenly much closer to her than he was in the rest of the scene.

Continuity mistake: When Leia and Rey feel Luke's force fading, Rey has a dark, burned, non-bleeding wound on her right arm. After Kylo enters the abandoned mine, he sees Rey through the force. The wound from before is now bright red as if it were still fresh and bleeding.

Continuity mistake: When Rey is following Luke upwards the steep terrain, between the two shots in which Luke is visible, there is a shot of Rey kneeling down, following up with her noticing the old Jedi tree. Given the amount of time the camera was focused on Rey, Luke should have been significantly further away as of the second shot in which he is visible. Instead he is seen continuing walking, starting from a point that he had already passed in the previous shot. (There is one dark spot on the ground, in which Luke can be seen walking past to his right in the first shot, which can be used to help identifying the mistake). (00:21:40)

Rassdyt

Continuity mistake: On Finn's and Rose's mission to find the master code breaker, when Finn walks up to the game table, the people around him are completely changed in the following shot. (00:52:40)

Rassdyt

Continuity mistake: While Rey is practicing with the pole, it changes position on the floor.

oswal13

Supreme Leader Snoke: You are no Vader. You are just a child in a mask.

More quotes from Star Wars: The Last Jedi

Trivia: Finn and Rose's mission on Canto Bight is interrupted by the fact that they parked their ship illegally. This also happens to the heroes in the Star Wars parody film Spaceballs by Mel Brooks that came out in 1987.

More trivia for Star Wars: The Last Jedi

Question: In Empire Strikes Back and Return of the Jedi, Luke's replacement hand looks like a normal human one (though it was mechanical). In this film he has a more obviously robotic hand. Other than to remind today's audiences that he previously lost his hand, was there any point to this change?

Gavin Jackson

Answer: The outer skin could have been destroyed when Ben attacked Luke and ransacked the temple. We see Luke's robotic hand rise out of the rubble. Perhaps it had skin before that, and Luke never fixed it as a reminder of his "failure."

Answer: At the beginning of Return of the Jedi Luke gets shot in the robotic hand and just wears a glove over it for the whole movie even though he could have had the skin fixed. Apparently in the many years between the movies he never bothered having any damage to the face flesh and skin fixed.

Answer: After thirty plus years, it could just be the natural degradation of the organic flesh covering the robotic parts.

Answer: He likely downgraded to a simpler, easier to maintain version at some point. Presumably before going off to the island.

The robotic hand Luke has in The Last Jedi has the scorch mark he got from a blaster from Return of the Jedi. It's the same hand, just without the artificial skin covering.

Bishop73
More questions & answers from Star Wars: The Last Jedi

Join the mailing list

Separate from membership, this is to get updates about mistakes in recent releases. Addresses are not passed on to any third party, and are used solely for direct communication from this site. You can unsubscribe at any time.

Check out the mistake & trivia books, on Kindle and in paperback.