Canon and Continuity

Haikuesday: Clone Troopers

The Muunilist 10
Advanced Recon Commandos
Captain Fordo’s squad


Clone Wars – Chapter 8
Kenobi strikes with a clone
Lancer Battalion.


Boss, Fixer, Sev, Scorch
From Republic Commando.
It’s a damn fun game.


Four Clone Commandos –
Niner, Fi, Atin, Darman
They show True Colors.


A different Niner
was killed on Vassek’s third moon
hunting down Gunray.


The best of the best.
Captain Rex is loyal to
his men and Sky Guy.


Commander Cody.
Leading the 7th Sky Corps
through numerous fights.


The Gauntlet of Death.
Clone sniper Cooker targets
power cells of droids.


Hevy’s sacrifice.
Kamino is protected
thanks to his actions.


Clone Captain Keeli
spends his last moments standing
with Ima-Gun Di.


Clone Commander Bly.
Secura’s loyal trooper.
He helps to kill her.


Fodder for the plot.
Cameron, Lucky, and Flash
are expendable.


The Clone Wars series
is really good at killing
lots of unnamed clones.


Duplicitous clone!
Sergeant Slick betrays his men
at First Christophsis.


Storm over Ryloth.
Clone Pilot Axe dies in his
V-19 Torrent.


“I guess we’re the best.”
Two clones scout a Twi’lek town.
Waxer and Boil.


Boil’s Fu Manchu
is absolutely stunning.
You can’t deny it.


The Battle of Khorm.
Wolffe loses his right eye in
a fight with Ventress.


Name is Cut Lawquane.
Deserted the army but
found a family.


Clone Commander Ponds.
Executed on Slave I
after his capture.


Landmine explosion.
“Oz is down. So is Ringo.”
Umbaran Darkness.


Hyper-active clone.
Hardcase is just a bit off.
It makes him unique.


Battle of Sarrish.
Gregor missing in action.
Found on Abafar.


Clone Commander Doom.
Designed as an homage to
Marvel’s Doctor Doom.


Turning on Tiplar.
“Good soldiers follow orders.”
Tup’s bio-chip fails.


ARC Trooper named Fives
discovers bio-chip truth:
To kill the Jedi.


Clone Medic Kix was
captured, frozen in stasis 
for next fifty years.


Clone Force 99.
Also known as the “Bad Batch.”
“they’re defective clones.”


ARC Trooper Echo.
Believed to be KIA.
But he was captured.


13th Battalion.
Led by Master Tapal and
Padawan Kestis.


“Time for you to leave,”
Appo tells Bail Organa.
Then wounded by Zett.


Clone Commander Gree.
Yoda cuts off the clone’s head.
Then makes his escape.


The Coruscant Guard.
Led by Clone Commander Fox.
Darth Vader kills him.


Check out these other Haikuesday 2.0 posts:

Imperial Atrocities

Luke Skywalker (ANH)

Luke Skywalker (ESB)

Luke Skywalker (ROTJ)

Dark Lords of the Sith

Star Wars Planets

The Great Jedi Purge

Star Wars Aliens

 

Star Wars: On the Front Lines (Review)

Ever since it was published in 2017 I had my sights set on Star Wars: On the Front Lines. I am a sucker for Star Wars reference books, having spent countless hours of my life immersing myself in the minutiae of the Star Wars universe found in these source books. But I did not buy On the Front Lines when it first came out, instead opting to wait to purchase it. Recently, though, the book was gifted to me and needing something new to read I decided to dig in. And, I am happy to report, On the Front Lines definitely did not disappoint. 

Primarily detailing battles from The Clone Wars and the Galactic Civil War, but also one from the Age of Resistance, On the Front Lines takes readers quite literally to the front lines of some of the most important engagements in Star Wars. While author Daniel Wallace limits the number of battles that are explored – a perfectly reasonable decision considering how many battles are in Star Wars – he never-the-less chose one battle to examine from every live-action and animated Star Wars story to date. In fact, the only notable exception is Star Wars: Rebels, with no engagement from that series being discussed. Here is a list of battles that the author examines:

The Battle of Naboo (The Phantom Menace)
The Battle of Geonosis (Attack of the Clones)
The Battle of Christophsis (The Clone Wars movie)
The Battle of Ryloth (The Clone Wars animated show)
The Battle of Coruscant (Revenge of the Sith)
The Battle of Scarif (Rogue One)
The Battle of Yavin (A New Hope)
The Battle of Hoth (The Empire Strikes Back)
The Battle of Endor (Return of the Jedi)
The Battle of Jakku (Various Sources)
The Battle of Starkiller Base (The Force Awakens)

That Wallace chooses well-known battles from the Star Wars saga, battles that we have actually seen in film and on television, makes it easy for both casual and die-hard fans to digest and enjoy this book. Interestingly though, the clash I found myself most interested in reading about was the Battle of Jakku. As you can see from the list above, this is the only engagement discussed in the On the Front Lines that has never been depicted on-screen. Putting his penmanship and imagination to work, Wallace pulls from multiple sources (novels such as Lost Stars and Aftermath: Empire’s End) to piece together details about this relatively unknown fight. In doing so, he presents a vivid picture of the final battle in the Galactic Civil War, a brutal slugfest between the New Republic and Imperial Remnant that leaves wreckage and bodies littering the sandy dunes of the remote world.

Jakku-Starship_Graveyard-The_Force_Awakens_(2015)
Want to know how all those derelict Star Destroyers ended up on the surface of Jakku? On the Front Lines provides some context.
Photo Credit – Star Wars Episode VII: The Force Awakens

While I found myself intensely fascinated by Wallace’s presentation of the Battle of Jakku this does not mean I found the other battles any less interesting. Far from it! In every chapter, Wallace draws on the source material available – movies, television shows, books, comics, etc. – to craft a unique and fairly comprehensive picture of each engagement. Granted, there are points where Wallace does leave out information, or gives details only a cursory glance. For example, the space battle which takes place above Naboo in from The Phantom Menace is only briefly mentioned, with the focus instead being entirely on the ground battle between the Gungans and the Trade Federation’s Droid Army. As well, the space battle over Ryloth, depicted in The Clone Wars Season 1, Episode 19 (“Storm Over Ryloth”), where Ahsoka Tano uses a Marl Sabl maneuver to defeat the Separatist blockade, is entirely ignored. For some die-hard fans of Star Wars, these and other omissions may prove annoying but for this die-hard fan, I found myself enjoying what was in the book rather than brooding over what was not.

That being said, I can admit that I wish the book had even more in it. This is not a criticism, though. Rather, it is an acknowledgment that I really enjoyed the way each battle is presented, with a combination of big picture information, such as why the confrontation took place and how it unfolds, along with more focused detail on things like armor, weaponry, vehicles and tactics. Every chapter also offers little asides about individuals from each engagement, specific commanders from both sides, and a handful of soldiers and/or pilots who displayed incredible courage during the fight. And, to top it off, every chapter is loaded with captivating and wholly unique images courtesy of four superb illustrators (Adrián Rodriguez, Thomas Wievegg, Aaron Riley, and Fares Maese).

Finally, I would be remiss if I failed to mention that On the Front Lines contains a lot of information that I never knew about, or had never even considered,, about each of these Star Wars battles. In closing, then, I thought I would pick just one bit of of insight that I learned from this book. And what comes to mind immediately is a detail about The Battle of Christophsis. Or rather, aftermath of Christophsis. As we see in The Clone Wars movie, towards the end of this fight, Jedi General Obi-Wan Kenobi tricks the Separatist General Whorm Loathsom into believing that the Jedi intends to conditionally surrender his clone forces. However, this is a ruse, done with the hope of giving Anakin Skywalker and Ahsoka Tano more time to deactivate the Separatist deflector shields. Kenobi succeeds in his plan, and actually captures Loathsom moments later, but as Wallace writes,

“General Kenobi’s false surrender at Christophsis was a boon to the Separatist-controlled media, who viewed the incident as clear evidence of the Republic’s duplicity. Almost no conditional surrenders were offered by either side for the remainder of the war” (pg. 31).

Kenobi may have been successful in that moment, but his “false surrender” was not without long-term consequence. As the Clone War intensified, it would be the clones themselves, the actual soldiers doing the fighting on the front lines, who would pay the price for Kenobi’s actions.

R-3PO: The Red Protocol Droid

In my previous two posts about protocol droids I focused on two from the TC-series of droids: TC-14 and TC-70. In this post, I decided to switch things up once again and go back to the 3PO-series by offering some details about R-3PO, the red protocol droid. 

R-3PO, like its counterpart K-3PO, only appears in The Empire Strikes Back. Specifically, the protocol droid can be found in two distinct scenes in the film, both times in the Echo Base hanger. The first scene is in the opening minutes of the film when Han Solo returns from his tauntaun patrol of Hoth. As Solo walks around an X-Wing and heads towards the Millennium Falcon, which is in the background, one will catch a quick glimpse of R-3PO walking by in the foreground. But to see the droid you have to look closely because the foreground is dark and it is slightly difficult to see R-3PO.

Later in the film, when the Rebels are scrambling to evacuate Echo Base, R-3PO shows up once again. Following the death of Admiral Ozzel, and Captain Piett’s promotion to Admiral, the very next scene takes us back to the Echo Base hanger. Now, we see Rebel pilots running to join Princess Leia’s briefing where she is discussing the evacuation and defense of the base. As the pilots run to the assembly of pilots, R-3PO is clearly visible on the right side of the screen, standing near an X-Wing and watching the commotion unfolding around it. 

And, yeah, that is it. As I said, R-3PO pops up briefly in two scenes. Ultimately, like so many other droids in the saga, R-3PO’s role in The Empire Strikes Back is straight-forward: populating the background in the Star Wars universe. Never-the-less, even though R-3PO is an extremely minor character doing very little on-screen, it has been given a sliver of backstory. As the canonical reference book Star Wars: Absolutely Everything You Need to Know notes, R-3PO is a “moody, red protocol droid on the lookout for spies” (pg. 164). This counterespionage role for R-3PO is, in fact, a carry over from the Expanded Universe where R-3PO was first presented as being tasked with weeding out spies among the droid pool in Echo Base. And considering this aspect of R-3PO’s background has been maintained in the Star Wars canon, it is probably safe to assume that the droid was also abandoned by its master, a smuggler who “accidentally” left the moody R-3PO in the hands of the Rebel Alliance. 


Check out these other posts about random protocol droids in Star Wars:

U-3PO: The Other Protocol Droid

K-3PO: The Dead Protocol Droid

E-3PO: The Rude Protocol Droid

TC-14: The Federation Protocol Droid

TC-70: The Hutt’s Protocol Droid

AP-5: The Singing Protocol Droid

4A-R2: The Pirate Protocol Droid

4-LOM: The Bounty Hunting Protocol Droid

Haikuesday: Star Wars Aliens

Desert Scavengers
Brown-robed, yellow-eyed Jawas
Utini,” they say.


Homeworld: Kubindi.
Kubaz with snout-like trunks speak
using vibrations.


Called “Squid Heads” by some,
the Quarren of Mon Cala
are a proud species.


Key trait: cone-shaped horns.
Gotal abilities are
extrasensory.


“Hard to meet a myth.”
Sentient, shapeshifting plants.
Neti from Myrkr.


Keeping to themselves,
the Kaminoans live out
past the Rishi Maze.


Breathing ammonia,
insectoid Gand are hidden
by respirators.


Exoskeletons.
Mathematical species.
Givin from Yag’Dhul.


Force technology.
An Infinite Empire.
Ancient Rakata.


Hailing from Toola.
Tusks protruding from their jaws.
Ferocious Whipids.

Haiku Addendum:
pronounce “Whipid” like Stewie
pronounces “Cool Whip”


Thisspiasian.
Serpentine body and a
very hairy face.


Malastare’s Natives.
Vicious Dugs walk on their arms
and use feet as hands.


Colonizing Gran
take control of Malastare.
The Dugs – furious.


A long-lived species.
Shi’ido first appeared in
Galaxy of Fear.


Short, Green, Pointed Ears.
Vandar, Yaddle, and Yoda.
Species’ Name Unknown.


Cycloptic biped.
Hailing from the planet Byss.
Green-skinned Abyssin.


Cremlevian War –
A galaxy ruined by
war-like Yuuzhan Vong.


The “friend from afar.”
The “stranger to be trusted.”
The Caamasi.


Fur-covered, wolf like.
The Shistavanen are a
rare sight in Star Wars.


Fur-covered, wolf-like.
Is that a Shistavanen?
Nope, it’s a Defel.


Water-based mammals.
A blowhole atop their heads.
The massive Herglic.


Ben Quadinaros.
The famous Toong podracer.
His engines explode.

I have a theory:
Han named Ben after the Toong.
I’m dead serious.


Neimodians.
Related to the Duros.
The latter came first.


Rodent-like beings.
Big ears and very dark eyes.
Chadra-Fan from Chad.


Saurian species.
Invasion of Bakura.
Bipedal Ssi-Ruuk.


Devilish mammal.
Males have horns, females do not.
Devaronians.


Mud as camouflage.
Red-skinned Mimbanese soldiers
ambush Stormtroopers.


Did you know that in
The Phantom Menace you can
see E.T.’s species?

Name: Asogians.
Homeworld: Brodo Asogi.
Lucas. Spielberg. Pals.


Hailing from Tibrin.
Amphibians with eye stalks.
The green Ishi Tib.


Insect-like Yam’rii.
Look for the praying mantis
in the Cantina.


Twelve-eyed insectoid.
A Vuvrian purchases
Skywalker’s speeder.


Eyes a glowing red.
Blue-skin and glint blue-black hair.
They are called the Chiss.


From the planet Merj.
Morseerians breath methane.
And have big cone heads.


I’m absolutely
positive I could outrun
a Gamorrean.


Wookiee. Gungan. Talz.
Trandoshan. Geonosian.
Sullustan. Lasat.


Rodian. Bothan.
Abednedo. Barabel.
Lamproid. Elomin.


Ewok. Dulok. Teek.
Sanyassan. Skandit. Yuzzum.
Jinda. Gupin. Gorph.


I could spend a day
listing Star Wars aliens.
There are so many!


It’s Star Wars quiz time!
Shistavanen or Defel
in the featured pic?


Check out these other Haikuesday 2.0 posts:

Imperial Atrocities

Luke Skywalker (ANH)

Luke Skywalker (ESB)

Luke Skywalker (ROTJ)

Dark Lords of the Sith

Star Wars Planets

The Great Jedi Purge

 

TC-70: The Hutt’s Protocol Droid

With the release of the seventh and final season of The Clone Wars animated show upon us I thought it would be appropriate, as part of my protocol droid series, to recognize a protocol droid that made its debut in the The Clone Wars. To that end, I could think of no better droid to highlight than TC-70, a TC-series protocol droid with feminine programming which as Jabba the Hutt’s translator.

As you undoubtedly already know, before The Clone Wars show debuted in October 2008 it was preceded by The Clone Wars film which was released in August 2008. And it was in this film where TC-70 was first introduced to the Star Wars canon, standing next to Jabba the Hutt in a hologram (see featured image) and ensuring listeners – in the movie and in theaters – could understand what the crime lord was saying as he spoke in his native Huttese. Moreover, what makes TC-70 all the more special – and I guarantee 99.9% of you are unaware of this – is that “she” is the very first character to speak in the The Clone Wars franchise following the introductory narration. Feel free to share this unnecessarily specific bit of Star Wars trivia with others, and/or use it to establish yourself as the dominant Star Wars fan in your group of friends. 

TC-70
TC-70 stands next to Jabba the Hutt.
Photo Credit – The Clone Wars Season 3, Episode 4: “Sphere of Influence”

Following “her” role in The Clone Wars movie, TC-70 also went on to appear in a handful of episodes in Season 3 of The Clone Wars show. While these episodes, and the film, are the only instances where TC-70 shows up in The Clone Wars, “she” does make a rather minor appearance in another Star Wars story. In Marvel’s Star Wars 15, TC-70 pops-up in a few panels, again translating for Jabba, this time as the crime lord speaks with the Wookiee bounty hunter Black Krrsantan. Considering Star Wars 15 takes place in the year 10 BBY, and TC-70 made “her” in-universe debut in 22 BBY, it is comforting to know that the protocol droid was able to stay in Jabba’s good graces for at least twelve years. Then again, given what we know about Jabba the Hutt and his temper, it is safe to assume that at some point after her appearance in Star Wars 15, TC-70 found herself on the wrong end of Jabba’s rage. 


Check out these other posts about random protocol droids in Star Wars:

U-3PO: The Other Protocol Droid

K-3PO: The Dead Protocol Droid

E-3PO: The Rude Protocol Droid

TC-14: The Federation Protocol Droid

R-3PO: The Red Protocol Droid

AP-5: The Singing Protocol Droid

4A-R2: The Pirate Protocol Droid

4-LOM: The Bounty Hunting Protocol Droid

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.

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.”