Stupidity: The Death Star comes equipped with a powerful tractor beam capable of capturing a ship the size and agility of the Millennium Falcon. Why don't they use it against the rebel fighters attacking them at the end of the film? Okay, Obi-Wan Kenobi turned it off earlier but I find it hard to believe that someone who has never before visited the largest, most complex space station in the Universe and who was previously unaware of its very existence can disable a fundamental security system but the people who designed, built and run the whole thing can't work out how to switch it back on. They should have no problems with this, considering the fact that Obi-Wan didn't damage it.
Suggested correction: Obi Wan disrupted the battle at a critical time causing much confusion. We could chalk this oversight up to "Fog of War" - that in the heat of battle it's normal for commanders to overlook obvious things and seem to act stupidly. It would also be reasonable to assume that the fighters were too close for the tractor beam emitter to target them.
This scenario would require every single person on the Death Star who was involved in the maintenance of vital defence systems not noticing that one of them had been switched off! Not ONE person noticed? Obi Wan did not disable the tractor beam during "the heat of battle." There was a considerable time lapse between his switching off the tractor beam and the climactic final battle, during which time it would have been switched back on. When the Millenium Falcon leavs the Death Star Han Solo remarks that he hopes that "old man" succeeded in disabling the tractor beam, implying that those on the Death Star would be trying to use it. Even then, they didn't notice it had been switched off? Not sabotaged, not disabled, switched off.
Good point. This was definitely stupidity on the part of the Death Star crew, but not stupid as a plot point. It does happen in combat regularly. In 1987 the USS Stark was hit by 2 Iraqi Exocet missiles after challenging a single fighter. The ships' Close-in Weapons System should have easily shot the missiles down, but the investigation showed that no-one had noticed that the system had not been turned on.
They didn't use the tractor beam when the gang was escaping in the Falcon because they WANTED them to get away. The Empire placed a tracking beacon onboard so as to be able to find the hidden Rebel Base. As to how the Falcon was snagged originally: yes, they had just exited hyperspace, but they were not relatively fast; they were preoccupied with the TIE fighter (incapable of light speed) and the small moon right up to the point they were trapped in the tractor beam (and realizing "that's no moon!"
Suggested correction: The Falcon was travelling towards the Death Star when it was caught in the tractor beam. The tractor beam was properly turned back on by the time it travelled to Yavin. The rebel fighters are too small and quick to be held in a tractor beam and there are so many of them so it would be near impossible to trap enough to make a difference.
As I have already pointed out, assigning technical limitations to a wholly fictional piece of technology is absurd. As to "flying towards the Death Star" - the X and Y wing fighters are shown doing just that. As for being too quick, the Millenium Falcon is decelerating from superluminal speeds when it is captured in the tractor beam. That's pretty bloody fast in anyone's books.
It's flat out stated by General Dodonna in the battle briefing that the Death Star's defenses are based around repelling attacks by capital ships, not fighters. The targeting may not be exact enough.
Actually, claiming a fictional piece of equipment can't behave the way you think it should is somewhat silly. The previous explanation that the tractor beam's limitations were the reason for not using it during the battle makes perfect sense.
Stupidity: 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.
Maybe. But if the First Order does this the entire plot of the movie as it is is ruined. So, maybe both?
Just because you didn't like the movie doesn't change a character stupidity into a plot hole.
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.
Hux is an idiot, Snoke is a fraud and Kylo doesn't really strike me as a strategic mastermind.
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.
Well the new movie puts a whole new light into that. Changes the whole discussion.
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.
In the time it takes to switch the hyperdrive on and off again, travelling at light speed you would travel so far ahead of them you would take days to get back to them. In a quarter of a second at lightspeed you travel much farther than the length of the planet Earth.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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).
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.
Exactly. This movie's plot is very flawed and it lacks logic to the big extent. Hux was much more competent in TFA, so his behavior in TLJ was both stupidity and a plothole.
Then they should have written a better plot. Complaining that rational act ruins the plot is a writing issue with the plot. They shouldn't have written this problem in the first place. You can't hide behind the "but it will ruin the film" excuse when the writers could have written literally anything else.
Suggested correction: In the time it takes to switch the hyperdrive on and off they would have travelled so far in front of the rebels that they would be worse off than before. Even switching the drive in for .25 of a second would carry them around 400,000 kilometers if my memory serves. This is still a plot hole. The first order ships are bigger, therefore they should be faster due to larger/ more engines and the "fuel" issue is wrong because all you have to do is switch off your engine and you will not stop.
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.
Stupidity: The commando mission to save Chewbacca starts gunning down a few Stormtroopers in the hangar. The heroes then go on leaving the troopers lying down on the floor in front of the ship, in plain view. They don't hide them nor ask the droids (who have enough strength and tools to pull them in) to, in fact they tell them to stay put. No wonder they are found out later (after a ridiculously long amount of time).
Suggested correction: Hiding the bodies would have been a waste of time, anyone who came to the hangar would immediately notice that the guards stationed there were missing and there was now a strange ship parked there.
The droids have all the time in the world, and people just passing by are "more immediately" bound to notice corpses in the middle of a hangar rather than possibly maybe question the fact that you don't see guards in that part of the hangar or investigate the ship - which could approach without anyone taking exception by appearance alone. At least remove the bodies directly in front of the damn ship!
Why would they be more likely to notice dead guards than no guards?
Anyone passing by might well thing the patrols were just out of sync, or a shift change. Sure they might investigate further, but they might not bother. Whereas a couple of dead bodies? Immediate red alert. Worth taking 30 seconds to hide them, surely.
Perhaps, but then it's made irrelevant 1 minute later as Finn and Poe run down a hallway blasting about a dozen stormtroopers.
For that matter, 1 SECOND later they kill stormtroopers in the far part of the hangar. They are killing people all over the ship during their mission and it's not like they hide every single one of them, but they leave two bodies *exactly* in front of their ship (and telling the droids to stay put). You can even see later that there is a stormtrooper with his weapon pointed exactly where those two corpses are, with the 'smart' commanding officer asking "whose ship is this?" at the sight of that. Maybe I am spoiled by a trope here, but it's the first time that I see someone in an action movie leaving corpses right in front of their only escape route/vehicle, that's so counterintuitive. (Did they even have an escape plan, actually? I don't like hypotheticals, but gee, if only she did the Jedi mind trick thing to those 2 guards who came over to inspect the ship instead of doing it later. But I digress).
Stupidity: When Han tells Drydon Vos that he and Tobias will steal unrefined coaxium from the mines on Kessel, Vos initially says no, as Crimson Dawn's relationship with the Empire would be at risk. Han then explains that the Empire wouldn't know they were working for Crimson Dawn. Vos then agrees but insists his top lieutenant Qi'ra accompany them, even though she is a known associate of Crimson Dawn and literally has their symbol branded on her wrist.
Stupidity: Immediately after Unkar Plutt makes Rey a generous offer for BB-8 and she refuses, he tells someone over his communicator to follow her and bring back the droid. He should have at least waited until she was out of earshot before he said that, especially if he was trying to be covert about it.
Suggested correction: But he was out of earshot of her.
I posted this immediately after watching the scene in question, and it looked as though Plutt spoke into his communicator right after Rey turned around and went on her way; certainly too soon for her to have gotten more than a few steps away. Also, he spoke at a normal, conversational volume rather than anything that sounded like a whisper or "sotto voce", so unless he was relying on the ambient noise of other nearby activity, I still believe this "stupidity" is valid.
That depends on how sneaky you think Plutt is. Rey walks away in quick paces, so she is out of earshot. Also I don't think it bothers him that much if she heard, she is just a scavenger, what can she do about it?
Rey was definitely out of earshot. Rey walks completely out of the shot, which appears to be about 10 feet away. Unkar Plutt then angrily swipes the portions off the counter and picks up his communicator. At the pace Rey was walking she would have been a considerable distance away from him when he spoke. In addition, Unkar Plutt lowered his voice when he spoke because he was being sneaky. She might have been able to hear him speak, but it is totally reasonable that she wouldn't be close enough to make out exactly what he was saying.