Topics

Han Shot First

Standing on a cliff overlooking one of Savareen’s oceans, Han Solo aims a blaster at Tobias Beckett, his mentor-turned-adversary. It was Beckett who gave Solo the opportunity to flee the frontlines of the Imperial army and join his crew. As they worked together, traveling from Mimban and Vandor to Kessel and now Savareen, Beckett bestowed his vast knowledge of a scoundrel’s life on the young Corellian, offering insights into how to survive and thrive in the galaxy’s dark underworld. Now, on this sandy, wind-swept cliff the two square-off: Beckett attempting to flee with the coaxium the crew stole and Solo attempting to stop him.

Engaging in conversation, Solo explains to his “buddy” that he came as quickly as he could. Beckett in-turn goads the young man, explaining that Qi’ra, Solo’s childhood friend and romantic interest who joined them in stealing the coaxium, is a “survivor” and out to protect herself, not Han. To this, Solo tells Beckett that his problem is that he believes everyone is like him, but Beckett admits to Han that “you’re nothing like me.” It is at this point that Beckett slowly puts his finger on the trigger of the gun he holds in his hand. Distracting Han, Beckett emphatically states that “I hope you’re still paying attention because now I’m gonna tell you the most important…”

…a blaster shot echoes across the landscape and Beckett, in stunned silence, falls to the ground, a hole sizzled in his chest. Running over to him, Han grabs Tobias and holds him upright. Shocked and breathing hard, Beckett compliments Solo, admitting “…that was a smart move, kid, for once. I woulda killed ya.” Moments later, Tobias Beckett dies.


While Solo: A Star Wars Story was met with mixed reviews and a disappointing box office return, I will admit that I enjoyed the film even though I had some reservations before seeing it. Frankly, I did not believe that a Han Solo origin story was necessary, especially on the big screen, and I feared that offering too much about Solo’s past would dilute the iconic character whom Harrison Ford brought to life. Yet, after seeing the movie, I found myself impressed by a number of aspects of the film, especially  those aspects which offered insight into the character we met in the Original Trilogy. This is not to say I agreed with every way Han Solo is depicted in the film, but it is to say that I appreciate many of the ways Solo: A Star Wars Story adds fascinating and obvious (and at times subtle) background to Han’s thoughts/actions in the original Star Wars films in general, and A New Hope in particular.

One such point in Solo: A Star Wars Story which does this is the scene I described above where Han Solo shooting Tobias Beckett on the Savareen cliff. That Han shot first, before Beckett could draw his own weapon, is absolutely brilliant, a clear indication that Solo really has been listening to Beckett’s advice throughout the course of the film. And tragically, for Tobias Beckett, it is his advice to Han – to always be on guard, to trust no one, to be a survivor, etc. – which turns out to be his downfall. Plus, to add to this tragic twist of fate for the scoundrel, it is the DL-44 blaster which Beckett assembled and gifted to Solo which the Corellian uses to kill his former mentor.

Alone, this scene does a fantastic job of showing that throughout the course of the movie, Han has grown considerably in his understanding of living a scoundrel’s life. He has internalized the wisdom Beckett offered, recognizing the need for constant vigilance and realizing that the decision to shoot first is the surest way to save his own skin in a dire situation. In this regard, what is equally brilliant about this scene is how it parallels and informs the infamous scene in A New Hope where the bounty hunter Greedo confronts Han Solo.

Han Shot First

The smuggler, Han Solo, whom we have just met for the first time moments before, attempts to leave the Mos Eisley Cantina but is immediately stopped by the Rodian bounty hunter and is forced, at gunpoint, to sit back down. Doing so, he and Greedo engage in a back-and-forth over Han’s debt to the gangster Jabba the Hutt, with the Rodian explaining that Jabba has “put a price on your head so large every bounty hunter in the galaxy will be looking for you…” Han, for his part, does his best to talk himself out of the predicament, even suggesting he already has the money owed to the Hutt. But this is really his attempt to stall for time and, as he and Greedo talk, he slowly removes the DL-44 blaster from his holster. Taunting the smuggler by saying Jabba may only take his ship, Han adamantly declares that Jabba will take the ship “over my dead body.” With this, Greedo admits that he has “been looking forward to this [killing Han] for a long time.”

“I bet you have,” Han replies and without hesitation shoots Greedo, the bounty hunter’s body slumping forward onto the table.

To me, it seems rather obvious that the standoff between Solo and Beckett in Solo: A Star Wars Story was crafted with the Cantina scene in mind. The parallels are clear, even if the context for both confrontations are different and Han Solo’s role in both situations are flipped. Consider the following:

  • Greedo confronts Han at gunpoint in the Cantina; Solo confronts Beckett at gunpoint on the cliff.
  • Greedo holds his blaster in his right hand; Solo holds his blaster in his right hand.
  • Han stalls for time, forcing Greedo to maintain eye-contact, while making a move for the holstered blaster on his right hip; Beckett stalls for time, forcing Solo to maintain eye-contact, while moving his finger onto the trigger of the blaster he holds by his right hip.
  • Han shoots first, killing Greedo; Solo shoots first, killing Beckett.

On the surface, the scene on the Savareen cliff is meant to mirror the Cantina scene. However, if we dig down a little, one recognizes that the standoff between Solo and Beckett can inform Han’s confrontation with Greedo. We can now read a new layer into the Cantina scene and assume that Han knows he has been in this type of situation before, albeit in reverse. Staring at Greedo across the table, Han must recognize that just as he shot and killed Beckett years before, Greedo will do the same unless he acts to save himself. And surely Han knows he has an advantage which his former mentor did not: his own blaster is out of view, below the table he and Greedo sit at. Beckett’s blaster, though, was out in the open, and Han could keep his eye on it even as he listened to Tobias. This was why Han shot first, killing the man before Beckett could act. Later, in the Cantina, Han does exactly the same, carefully drawing his DL-44, not allowing Greedo to notice his movements, taking aim and firing the first shot, ending the Rodian’s life.

Ultimately, it is this parallel, that Han shot first, which is what truly makes these scenes work in tandem. I am certainly aware, of course, that the Cantina scene has been changed over the years, with one edit having Greedo shot first and Han second, and more recently another showing Han and Greedo firing at the exact same time. Frankly, I just ignore these edits and dismiss them outright. The original version of the Cantina scene is all that matters to me, nay it is the only version that makes sense to me because it affirms that he is a man who is in control of his own destiny, a man who will always act first and foremost with his own interests and self-preservation in mind.  And frankly, I am confident that the original version of the Cantina scene was all that mattered to the writer(s)/director of Solo: A Star Wars Story as well because, as he stood on the Savareen cliff, Han Solo was also in complete control and, when the moment for action arrived, it was Han, and not Beckett, who shot first.

U-3PO: The Other Protocol Droid

Knowing that I am fanatical in my love of Star Wars, a friend recently asked me a pretty unsurprising question about A New Hope. The question was this:

“What’s the name of the other protocol droid following R2-D2 and C-3PO at the beginning of A New Hope?”

Answer: U-3PO.

My friend then followed-up with a pretty obvious second question:

“What happened to U-3PO?”

Answer: Hell if I know.

Seriously, I have absolutely no idea. All I can tell you about the silver plated U-3PO beyond it’s name – which it officially received in the 1995 Star Wars Customizable Card Game – is that U-3PO follows the other two droids down a corridor in the Tantive IV before turning off into a different room. Then again, you could have figured that out yourself. What happened to U-3PO once it disappeared from view is a mystery. Admittedly, it is a mystery that has periodically popped into my mind. And if I had to take a guess, I would assume U-3PO was either “…sent to the spice mines of Kessel or smashed into who knows what!” Why? Well, honestly, if I have to explain it I’ll be taking the fun out of allowing you to figure it out for yourself (just re-watch the opening of A New Hope).

So the point is this: U-3PO is just the other protocol droid aboard the Tantive IV and has absolutely no bearing on the events of A New Hope. And yet, I will admit that I have always been intrigued that U-3PO is present in the film for those few brief seconds. It is certainly interesting to think about what happened to the protocol droid, and I hardly think some “canonical” answer is necessary. In this regard, the imagination is good enough for me.

But in closing, I will also say this: I find it equally interesting to imagine what role U-3PO could have played in the events of the film if it had stuck with R2-D2 and C-3PO. Who knows, maybe things would have been incredibly different if there had been three droids, and not two, wandering the barren wastelands of Tatooine. 

Haikuesday: Dark Lords of the Sith

Hundred-Year Darkness:
Jedi exiles become
Jen’ari, Dark Lords

The Left-Handed God:
Dark Jedi Ajunta Pall
First Lord of the Sith

Greatest of his Age
A fierce Sith-human hybrid
Lord Marka Ragnos

Great Hyperspace War:
Naga Sadow’s Empire
invades Republic.

On a Deep Core World
Darth Andeddu rules as an
Immortal God-King.

Sadow’s apprentice:
Fallen Jedi, Freedon Nadd.
Onderon entombed.

“I was the greatest
Dark Lord of the Sith,” he states.
“I am Exar Kun.”

Haiku Addendum:
Exar Kun is a badass!
You should check him out.

Reviled, Dreaded.
A Jedi leaves, Sith returns.
He is Darth Revan.

A Sith Apprentice.
Darth Malak betrays Revan
and becomes Master.

Malak’s Shadow Hand:
Darth Bandon, former Jedi.
Vanquished by Revan.

Sith Triumvirate:
Darth Traya suffers betrayal
by Hunger and Pain

The Lord of Hunger.
Draining the Force of all Life.
Dark Lord Nihilus.

Sion, Lord of Pain.
Body fractured and rotting.
And yet, immortal.

“For three hundred years,
we prepared, we grew stronger.”
Malgus leads the charge.

Immortality:
Darth Scabrous’s dream results
in the walking dead.

“The Last Survivor”
Darth Bane, the architect of
the Sith Rule of Two.

A child named “Rain”
sent to war by the Jedi
becomes Darth Zannah.

Iktotchi Huntress
Gifted in divination
The Dark Lord Cognus

Three-eyed mutant Sith
Apprenticed to Darth Cognus –
Darth Millennial

Haiku Addendum:
Darth Millennial enjoys
avocado toast.

Starship Designer
but really, he’s Tenebrous
Dark Lord of the Sith

Darth Plagueis the Wise
Murdered by his apprentice
while he was asleep.

The first Emperor,
a galactic Empire.
Dark Lord Sidious

Devilish Sith Lord
Double-bladed lightsaber.
The Zabrak named Maul.

Elegant Evil.
Former Jedi: Count Dooku.
Dark Lord Tyrannus

Once known as “Anni”
He spirals to the Dark Side
and becomes Vader.

A Son of Solo.
Jacen Solo, Darth Caedus.
Killed by his sister.

Born A’Sharad Hett
Founder of a new Sith Cult:
Darth Krayt’s Rule of One

Anointed by Krayt.
Body covered by tattoos.
Twi’lek Darth Talon.

What about Kylo?
Well, this is awkward because
he is not a Sith.

Haiku Addendum:
Kylo Ren verses Caedus?
Darth Caedus would win.


Check out these other Haikuesday Posts!

Imperial Atrocities

Luke Skywalker (ANH)

Luke Skywalker (ESB)

Luke Skywalker (ROTJ)

Where Are The Dead Bodies?

In my last post – Continuity Confusion in Resistance – I outlined the plot of the Season 2 episode of Star Wars Resistance titled “A Quick Salvage Run.” In turn, I examined how, at the end of that episode, when the Colossus makes its getaway from the First Order, the ship is not tracked through hyperspace, an outright confusing fact considering the First Order possess the technology to do so. For the sake of brevity, I will let you go read that post to see what I say about the topic. Here, though, I wanted to return briefly to “A Quick Salvage Run” to pose a question that popped into my mind as I was watching. Allow me to set the stage.

In the episode, Kazuda Xiono leads a salvage team comprised of the members of the Warbird pirate gang to the Fulminatrix, the First Order Dreadnought destroyed by the Resistance at the beginning of The Last Jedi. The intention of the salvage run is pretty straightforward for Xiono: find the hyperfuel (coaxium) still in the ship and bring it back to the Colossus. Of course, the pirates have ulterior motives, salvaging any other materials they deem valuable, although they do not hinder the primary objective. 

As one can imagine, the “quick salvage run” to the Fulminatrix is the core of this episode, and many scenes are devoted to Xiono and his confederates scouring the wreckage of the massive vessel. And it is was during these scenes aboard the Fulminatrix where my question popped into my head:

Where are the dead bodies?

Seriously, there are no bodies of First Order crew members anywhere to be found within the wreckage of the Fulminatrix. Not even one. According to the reference book Star Wars: The Last Jedi: Incredible Cross-Sections, the dreadnought had the following personnel aboard:

  • 53,000 officers
  • 140,000 enlisted
  • 22,000 stormtroopers

That is a total of 215,000 crew aboard the Fulminatrix when it was bombed by the Resistance!!! Are we really to believe that Xiono and company are running about the vessel and no dead bodies would be present? I mean, it stands to reason that some of the crew were probably able to evacuate the doomed dreadnought, while the bodies of thousands of others  – like Captain Canady – were completely incinerated in the inferno triggered by the Resistance bombs. Never-the-less, it is difficult to believe that not a single dead body would be laying about as Xiono and the pirates navigate the debris-strewn corridors of the dreadnought. Surely, hundreds, if not thousands, of bodies should be strewn about the ship, contorted and mangled by the explosions that ripped through the Fulminatrix. 

Fulminatrix Explosion
The destruction of the Fulminatrix.
Gif Credit – Star Wars Episode VIII: The Last Jedi

I mean, I guess someone could argue that because Star Wars Resistance is a kids show – it is animated and on Disney XD – the presence of dead bodies would be upsetting to children. Frankly, I find that reasoning entirely unconvincing, especially because animated Star Wars programs have been known to show death/dead bodies in the past. Besides, “war” is in the name of the franchise and this means there is an obligation not to sanitize warfare. This is not to suggest that every Star Wars story must depict the exact same level of death, horror, and destruction. I hardly think a “kids show” needs to show the grotesque, burnt corpses of First Order ensigns and gunners littering the hallways of a destroyed dreadnought. No, in this case, a few dead stormtroopers lining the darkened hallways as Xiono and the pirates walk-by would have been enough, a clear reminder to kids and adults alike that when the Resistance bombs exploded, people died. 

Continuity Confusion in Resistance

In a recent episode of Star Wars: Resistance – “A Quick Salvage Run” – Kazuda Xiono and his compatriots aboard the Colossus find themselves in orbit above the planet D’Qar. There, they discover the Resistance base on the surface abandoned – nay, destroyed! – and the wreckage of Resistance and First Order ships drifting aimlessly above the world. At the center of the debris field is the wreckage of the Fulminatrix, the First Order Dreadnaught destroyed by the heroic sacrifice of Paige Tico during the Evacuation and Battle of D’Qar at the beginning of The Last Jedi.

That the second episode of Resistance’s final season brings fans back to D’Qar following the opening battle of The Last Jedi is an intriguing piece of connectivity between stories. It is a connection that goes beyond superficiality to show that events taking place at one moment can have ramifications for others later on. And this is particularly true for Xiono and those aboard the Colossus. As their ship is in desperate need of hyperspace fuel to escape the First Order, Xiono leads a crew to the wreckage of the Fulminatrix to salvage fuel from the destroyed dreadnaught. 

STAR WARS RESISTANCE
The Colossus
Photo Credit – Star Wars Resistance Episode 2, Season 2: “A Quick Salvage Run”

While aboard the Fulminatrix, a First Order Star Destroyer tracking the Colossus appears above D’Qar, led there by an ill-advised communication from Xiono to his friend-turned-First Order pilot Tam Ryvora. A battle ensues, the hyperfuel is salvaged, and just before the Colossus is decimated it zips into hyperspace, the First Order is foiled in their attempt to destroy the massive ship.

Except, the Colossus does not get away! Immediately after exiting hyperspace, far from the planet D’Qar, the First Order Star Destroyer reappears. It has tracked the Colossus through lightspeed! Turning it’s full compliment of 1,500+ turbolasers, point-defense lasers, and ion cannons against the Colossus, the Destroyer rips the massive refueling station to bits and leaves the wreckage, and dead bodies, floating in the vacuum of space.

Okay, I made that last part up (it’s why I put it all in italic), but I did so to point out that there is a “Fulminatrix”-sized continuity hole in the ending of this episode. While “A Quick Salvage Run” does a wonderful job of directly tying itself to the events at the beginning of The Last Jedi, the showrunners completely and utterly forgot to factor in one of the biggest and most important plot points from the movie. Namely, that the First Order has the technology to track ships through hyperspace! 

Point of Continuity Confusion

In my previous post – Continuity Confusion in The Last Jedi – I highlighted some thoughts regarding the First Order’s pursuit of the Resistance in The Last Jedi. I won’t rehash the post here but I will note that one of the points I make is that The Last Jedi used, as a central plot point, a concept first teased in Rogue One: the concept of hyperspace tracking. In The Last Jedi, the Resistance is completely caught off-guard when the First Order tracks their fleet through lightspeed, and the actions of the Resistance leadership going forward in the film are driven by the reality that they cannot simply re-jump to hyperspace to flee their enemy.

In turn, The Last Jedi also goes out of its way to fill us in on a handful of key points, also important to the plot, regarding hyperspace tracking. For our sake, the one that truly matters is that even blowing up the ship doing the tracking, the lead Destroyer in the First Order fleet, will be pointless. Why? Because another Star Destroyer will just start doing the tracking. Here is the dialogue where Finn explains this very point to Poe Dameron:

Poe: “Just give it to me one more time, simpler.”

Finn: “So the First Order’s only tracking us from one Destroyer, the lead one.”

Poe: “So we blow that one up.”

Finn: “I like where your heads at but no, they’d only start tracking us from another Destroyer.”

Did you catch that? Finn explains that the First Order can track them using any Destroyer. Blow one up, another will do the tracking. The implication is that every First Order capital ship has hyperspace tracking capabilities.

So, with that in mind, turning back to Star Wars Resistance, I am left utterly confused by the fact that the Colossus jumps to hyperspace at the end of  “A Quick Salvage Run” but the First Order Star Destroyer does not track it through lightspeed. It has the ability to do so, but it doesn’t…??? 

Honestly, I am not just confused by this, I am dumbfounded. Hyperspace tracking is THE plot point driving a major portion of the narrative in The Last Jedi, and yet, the showrunners for Star Wars: Resistance just happened to forget? The film was clearly on their minds considering the Colossus travels to D’Qar and Xiono salvages fuel from the destroyed Fulminatrix. Yet, for reasons I cannot figure out, the Colossus is able to slip away at the end of the episode without a care in the galaxy, completely safe even though the First Order harbors the technology to follow and destroy Xiono and his friends. 

Oh, and for the record, I did my due diligence and waited patiently to watch Episode 3 (“Live Fire”) before I wrote this post. I figured, at the very least, maybe the showrunners had a surprise for the audience and the First Order DID track the Colossus. Well, I don’t want to spoil anything but I will say this: they didn’t track the Colossus.

#facepalm #sigh #continuityconfusion 

Continuity Confusion in The Last Jedi

The overarching plot to The Last Jedi is pretty straight-forward:

Fleeing their hidden base on D’Qar just as a First Order fleet shows up, the four vessels in the Resistance fleet zips into hyperspace following a deadly battle. However, when they exit hyperspace, the First Order fleet also re-appears and it quickly dawns on General Leia Organa that the enemy has tracked them through hyperspace, a concept thought to be impossible! Having only enough fuel for one more hyperspace jump, and knowing that the First Order will just track them through hyperspace once more, the Resistance fleet simply maintains a steady pace, chased by the Star Destroyers of the First Order but staying out of distance from their heavy guns.

With the First Order fleet chasing the Resistance fleet, writer/director Rian Johnson proceeds to tack subplots onto the pursuit. The first is Poe Dameron’s annoyance with Vice Admiral Holdo after she takes over for General Organa, an annoyance steming from being kept out of the loop regarding Holdo’s plan to escape the First Order. In turn, his annoyance will eventually lead to outright mutiny on the part of Dameron and a handful of co-conspirators. The second subplot, which is tied directly to the fleet pursuit AND Dameron’s annoyance, is the side-journey Finn and Rose take to Canto Bight in order to find a code-breaker who can disable the First Order’s hyperspace tracker.

There are, of course, other aspects to the plot of The Last Jedi which primarily revolve around Rey, Luke Skywalker, Kylo Ren, and Supreme Leader Snoke. For the sake of this post, though, I am uninterested in analyzing these other plot elements. This is not to suggest they are unworthy of consideration. Far from it. In fact, I do look at these other plot points in a prior piece titled “Reflections on The Last Jedi.” Here, though, I want to focus solely on the plot as described above, namely the fact that the movie centers on the First Order fleet chasing the Resistance fleet. And, in doing so, I wish to highlight two points of continuity confusion which I find rather apparent in this plotline.

Points of Continuity Confusion

An Imperial research initivative first teased in Rogue One: A Star Wars Story which Jyn Erso comes across as she searches the Scariff database for the Death Star plans, hyperspace tracking resurfaces in The Last Jedi as the critical piece of technology which the First Order uses to follow the Resistance fleet. Without it, the First Order would have been incapable of pursuing the General Organa’s forces after the evacuation and battle of D’Qar. The Resistance, obviously surprised by the First Order’s capability to track them through hyperspace, must then turn to a different plan to escape their adversary.

Supremacy's_hyperspace_tracker
The First Order’s hyperspace tracker.
Photo Credit – Star Wars Episode VIII: The Last Jedi

That hyperspace tracking is mentioned in Rogue One and is then used as a critical plot device in The Last Jedi is, in and of itself, a worthwhile and interesting point of Star Wars continuity. Never-the-less, I cannot help but be confused by the use of hyperspace tracking in the The Last Jedi in one very specific way:

If the First Order can track the Resistance through hyperspace, then how come they didn’t exit hyperspace slightly ahead, and not directly behind, the Resistance fleet?

This is a question that I have struggled to fully grasp ever since watching The Last Jedi. While I certainly understand, and can appreciate, that the fleet chase is what provides the movie a core part of its narrative, it seems rather silly that the First Order would willingly exit hyperspace at a point that is not advantageous to their primary cause: destroying the Resistance. One would presume that hyperspace tracking enables the First Order to exit lightspeed behind AND ahead of the Resistance, thus ensuring that they are trapped and destroyed.

Yet, exciting lightspeed directly behind the Resistance fleet is what the First Order chooses to do. Okay then, fair enough. But this is also where ANOTHER piece of continuity confusion comes into play – the “Microjump.” In brief, the concept of the microjump is one that has only been used a handful of times in the Star Wars Canon, but it is, never-the-less, a critical and intriguing capability. Essentially, it is the ability to make a tactical jump into hyperspace and travel a very short, precise distance. In effect, a ship enters and then immediately exits lightspeed.

Canonically, the microjump is used for the first time in The Clone Wars Season Two episode “Grievous Intrigue” when Anakin Skywalker makes a tactical hyperspace jump into the middle of the Battle of Saleucami. In Solo: A Star Wars Story, the Millennium Falcon performs a microjump as it is traversing The Channel through the Akkadese Maelstrom towards the planet Kessel. As well, microjumps are also used in three Star Wars novels: Tarkin, Thrawn: Alliances, and Thrawn: Treason. Admittedly, the microjump is a concept that is not widely used by Star Wars storytellers and prior to the release of The Last Jedi, only The Clone Wars and Tarkin provided examples as Solo: A Star Wars Story and the two Thrawn novels were released after The Last Jedi. Then again, prior to The Last Jedi, the concept of hyperspace tracking had only ever been mentioned, and never before used, in any Star Wars tales. And so, this leads me to another, pretty obvious question:

After exiting hyperspace behind the Resistance, why didn’t the First Order fleet – even just one Star Destroyer in the fleet – perform a microjump to get ahead of the Resistance fleet?

Again, I am confused that a fleet chase is even necessary in The Last Jedi considering that the very concept of the microjump provides an easily accessible maneuver for the First Order to trap their enemy. In fact, multiple Star Destroyers could jump in multiple directions, creating a web to ensure that every direction in which the enemy chooses to travel is covered. And yet, for whatever reason, the First Order chooses to just slowly and methodically chase their enemy, simply waiting for the Resistance ships to run out of fuel…

Okay, fine. I will begrudgingly accept that for whatever reason the First Order leadership, obsessed as it is with destroying the Resistance, chooses not to take advantage of the ability to easily get ahead of the Resistance fleet using a microjump. But the thing is, this is only one side of the coin. You see, even if we presume that the First Order just chooses NOT to perform a microjump, the Resistance leadership – namely General Organa and Vice Admiral Holdo – have no way of knowing if any First Order Star Destroyers are already ahead of their fleet.

Seriously, just think about it for a second. This aspect of the plot of The Last Jedi is premised on the notion that the First Order can, and has, tracked the Resistance through hyperspace. Even in figuring this out, the Resistance has absolutely no way of knowing if any First Order Star Destroyers jumped PAST them and are lying in wait. Further, Organa and Holdo have no way of knowing if, at any moment, the First Order will perform a microjump to get ahead of their fleet. In other words, the actions of the Resistance leadership really make no sense given that they should be able to deduce the possibility that there might be now, or will be very soon, First Order ships directly ahead of them.

The Raddus
The Raddus
Photo Credit: Star Wars Episode VIII: The Last Jedi

And this is even more confusing when we consider that the Resistance plan is quite literally straight-forward: traveling in a line which will take them past the planet Crait where they will secretly slip away in transports while their main cruiser – the Raddus – continues traveling in that straight-line. Seriously, that is the plan. Go in a straight-line past the ONLY planet they can possibly escape to while ignoring the fact that the First Order could just microjump to Crait before they even arrive.

Yet, the thing is, The Last Jedi completely and utterly ignores this possibility which is precisely why I am confused by the fleet chase. It isn’t that a fleet chase is an implausible plotline, or something that has never happened in Star Wars (see: The Clone Wars Season 1, Episode 2 “Destroy Malevolence”). Rather, it’s the basic fact that the film fails to account for the canonical concepts- hyperspace tracking and microjumping – which render the purpose of the entire chase unnecessary in the first place. At the very least, The Last Jedi should have included a few lines of dialogue on the part of the First Order and the Resistance stating WHY the First Order fleet did not exit hyperspace ahead of the Resistance and why the First Order fleet will not microjump ahead of the Resistance fleet. 

That’s it, that is ALL the film needed to account for these possibilities. Just a few lines of extra dialogue about hyperspace tracking, and some brief explanation of microjumps, would have sufficed.  Except that would have required a little extra work on the part of Rian Johnson and the Lucasfilm Story Group, but let’s be honest, they were too busy acting self-satisfied about The Last Jedi on Twitter. 

I have the time, though, so here are some possible exchanges that could have been added to the film. Enjoy (and leave a comment below):

[Scene: Bridge of Star Destroyer Finalizer after exiting hyperspace behind Resistance]

General Hux: “Our tracker worked perfectly. The Resistance fleet is doomed!”

Captain Peavey: “Genera Hux, the captain of the Harbinger is requesting permission to perform a microjump ahead of the Resistance fleet.”

General Hux: “Permission denied. Organa and her scum will not escape us.”

 

[Scene: Secondary Battle Bridge of the Raddus]

Poe Dameron: “Vice Admiral, Commander Dameron. With our current fuel consumption there’s a very limited amount of time we can stay out of range of those Star Destroyers.”

Vice Admiral Holdo: “Very kind of you to make me aware.”

Dameron: “We also don’t know if the First Order jumped out ahead of us and I’d like to not walk into a trap.”

Holdo: “That is certainly a possibility, although I think you give General…Hugs…too much tactical credit.”

Dameron: “Okkkkkay, so, what we are gonna do to shake them? What’s our plan?”

 

[Scene: Medical Bay in the Raddus]

Finn: “So the First Order is only tracking us from one Destroyer, the lead one.”

Rose: “It tracked us to the exact spot we left hyperspace, which must mean the tracker entirely controls the navicomputer once it is turned on. The First Order couldn’t jump past us because the tracker is locked once the jump to lightspeed takes place.”

Poe: “They could only exit hyperspace behind us…but they could still perform a microjump and get ahead of us now.”

Finn: “Right.”

Poe: “Okay, I think I get it….so we blow up the lead Destroyer and zip away before we run into any other Destroyers that are waiting for us.”

Impressed by Paploo

Allow me to paint you a picture with my imagination brush:

I had just returned home around 8:30pm – I had been at a volleyball game coaching my team to another victory (boo yeah!) – and ended up on the couch flipping through the channels trying to find something to watch. Lo and behold, I came across Return of the Jedi during the speeder bike chase and said to myself “You know, I haven’t watched ‘Jedi’ in a while so I might as well keep watching.” So, there I am, on the couch, watching Return of the Jedi as the film continues. The Rebel heroes meet their soon-to-be Ewok allies, Luke tells Leia they are siblings, Han gets jealous and Leia wants a hug, Vader and Luke end up discussing Vader’s moral compass, the Rebel fleet enters hyperspace, and the Rebels discover, thanks to the Ewoks, that there is a “back-door” to the Imperial facility on Endor. 

Paploo with Wicket

Paploo discusses his plan with Wicket. Photo Credit – Star Wars Episode VI: Return of the Jedi

Okay, so, the Rebels are led to the back-door by the Ewoks. Unfortunately, as you already know, the entry is guarded by four scout troopers milling about and chatting without a care in the galaxy. As Han Solo and his Rebel pathfinders do not want to alert the Empire to their presence, he and the group discuss their options. As they do so, the highly strung C-3PO learns from an Ewok counterpart that “…our furry companion has gone and done something rather rash.” Telling this to the group, Leia expressing an audible “Oh, no” the group watches as one Ewok moves towards the scout troopers.

Or rather, Paploo, the Ewok in question, moves towards the scout bikes sitting at the end of the clearing. Getting onto one of the bikes, Paploo proceeds to turn it on and zips off into the forest pursued by three of the four scouts. “Not bad for a little furball. There is only one left,” Han professes, obviously impressed by Paploo’s ingenuity. 

Like Han, I too have always been impressed by Paploo’s quick-thinking decision to steal a speeder bike. But what truly impressed me during this particular viewing of Return of the Jedi as I sat on my couch was the fact that Paploo seems to know PRECISELY how to operate the scout bike. This realization had never dawned on me prior to this moment, the fact that this primitive creature with absolutely zero technological understanding knew the exact sequence of buttons and switches that needed to be activated for the bike to work. Impressive, Paploo, most impressive.

Granted, it is entirely possible that Paploo just gets lucky, that he randomly flips the correct switches and the bike ends up working. I’m hardly opposed to this possibility. It is, after all, the most likely way the scene is meant to be viewed. Never-the-less, as I sat on my couch watching Paploo start the bike, for the first time it dawned on me that the Ewok furball knew what to do. And, as a result, a second thought, a question, popped into my mind: how can we explain the primitive Paploo’s expertise in Imperial technology?

Honestly, I think explaining Paploo’s actions as intentional is easy, and actually works in conjunction with the thoughts I laid out about the Ewoks in my piece “Cute, Funny, and Very Deadly” way back in 2015. In that post – which was part of Ewok Week – I made the point that the Ewoks were either preparing to fight the Empire, or they had already started the fight when the Rebels show up. You can go read that post to get a deeper look at these ideas, especially since I believe Paploo’s apptitude with a scout bike can easily be tacked onto them. 

Paploo Speeder
Paploo pilots the stolen speeder.
Photo Credit – Star Wars Episode VI: Return of the Jedi

If the Ewoks were already fighting the Empire, or just preparing for their war, it would make logical sense that the primitive beings took the time to learn about their foreign invaders. We can assume, then, that Paploo, and perhaps a number of other Ewoks, had already stolen scout bikes in order to learn more about these curious and unfamiliar machine. When he sneaks up on the bikes to steal one in Return of the Jedi, Paploo would already have an understanding, even a basic one, about how the contraption works. Not to mention, he also seems to know how to drive the speeder once it zips off into the forest. The initial acceleration surprises Paploo, but he regains control with relative ease and pilots the bike deeper into the forest with the three Imperial scouts hot on his tail. 

Again, it could just be that Paploo gets lucky. Maybe he did. Honestly though, I find it far more likely, and way more interesting, if he and other Ewoks had taken the time to learn about the bikes as part of an attempt to better understand their enemy. But you can decide for yourself.

Leave a comment and let me know what you think about Paploo and his speeder bike excursion!

Haikuesday: Luke Skywalker (ROTJ)

Hologram of Luke
Speaking to Jabba the Hutt
Bargaining for Han


Token of Goodwill:
C-3PO and R2.
Both have served him well.


Scene: Jabba’s Palace.
Main gate opens, Luke walks in.
Confronted by Guards.

Shrouded in Darkness,
Luke draws on the Force and chokes
the Gamorreans.


Threatening Jabba.
“Master Luke, you’re standing on…”
The floor drops away.


“OH NO! THE RANCOR!”
Once, Luke fought a big Wampa.
Rancors are larger…

The Rancor eats pork.
Then it turns towards Skywalker.
How will Luke survive!?!?!

First – use a large bone.
Next – hit its fingers with rocks.
Last – throw human skull.


The Rancor is dead!
But Luke is still in trouble.
Onto the Sarlacc…


The Pit of Carkoon.
Luke preps for Jabba’s justice…
…then springs to action!


A green lightsaber!
Luke built a Jedi weapon!
How’d he manage that?


Slashing and blasting.
A chaotic desert scene.
And Luke’s hand is shot!


What are your thoughts when
Luke blows up Jabba’s sail barge?
Kinda messed up, right?


Back to Dagobah:
Skywalker returns so he
can finish training.


Yoda, very frail.
Tries to avoid Luke’s question:
“…is Vader my dad?”


Obi-Wan Appears!
“From a certain point of view…”
Luke learns a lesson.


Spoiler Alert!
The Princess is Luke’s sister!
O-M-G!!! THEY KISSED!!!!!


Scene: Sullust System.
The Rebel Fleet amasses.
Luke decides to join.


Passing the “Super,”
Luke can sense a dark presence…
“Vader’s on that ship.”


Endor Excursion.
Luke, Han, Leia, Chewie, Droids.
And Rebel Soldiers.


Chasing Scout Troopers
through a Forest on Endor.
Team Luke and Leia.


Captured by Ewoks.
Luke will be a main course in
3PO’s honor.


Emotional Talk.
Luke reveals truth to Leia:
Brother and Sister


Taken to Vader – 
“I know there is good in you.”
“I feel the conflict…”


Before Palpatine –
“I have been expecting you.”
Verbal sparring match.


Battle commences:
Rebels caught in an Imp trap
fight for survival.


Watching the battle
Luke is tormented by the
unfolding drama.

“You want this, don’t you?”
Luke looks at his lightsaber.
“Strike me down with it.”

Haiku Addendum:
Palpatine’s “Trap” was always
for Luke Skywalker.

“My young apprentice…”
Luke watches as the Death Star
fires on the fleet.

Filling with anger,
He can no longer resist –
Luke takes his weapon.


Red and Green Collide.
Father and Son engage in
a duel of the fates.


“Twin sister…if you
will not turn to the dark side,
then perhaps she will.”


A rage-filled assault.
Consumed by the darkness, Luke
presses his attack.


“…take your father’s place.”
The hero arrives at his
most critical point.


A farewell to arms.
Luke declares who he shall be:
“I am a Jedi.”


Baptized by Lightning.
The Son pleads to the Father.
The Father responds.


Vader is no more.
Luke burns his father’s body.
Now, the Last Jedi.


Joyful reunion.
Luke celebrates with his friends.
Saga is complete.


This post is Part 3 of 3 in a special three-week version of Haikuesday exploring Luke Skywalker in the Original Star Wars Trilogy. Check out the other two posts below!

Luke Skywalker (ANH)
Luke Skywalker (ESB)