Sequel Trilogy

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

DJ: Most Wanted (Review)

A while back I was perusing the local comic store when I came across a decently priced copy of DJ: Most Wanted. I didn’t really have an interest in the Marvel one-shot about the slicer named DJ who helps Finn and Rose in The Last Jedi, primarily because I was underwhelmed by his presence in the film. While it was fun to see actor Benicio Del Toro in a Star Wars film, I ultimately left my first (and subsequent) viewings of The Last Jedi not really caring one way or the other for his character. I guess you could say I “nothinged” him, having no opinion of DJ other than to say “he is in the movie.”

Yet, as I stood there looking at the Marvel one-shot – which was released in January 2018 – I decided I would bite the bullet and give it a chance. At the very least, I convinced myself, perhaps the story would make DJ slightly more interesting and help me appreciate him a little bit more. Except, that didn’t really happen. While it took me some time to finally read DJ: Most Wanted, I did eventually get around to it and was left feeling…nothing.

Spoiler Time!

The general story run down for the comic book goes like this: DJ is on Canto Bight doing some gambling, but really he is just stealing money. He finds himself in a lot trouble and as a way of saving his own skin from the casino bosses he willingly gets himself arrested. Thus, he is plopped down in a jail cell and there he will sit until Finn and Rose show up.

DJ, Finn, Rose
DJ (center) with Rose and Finn.
Photo Credit – Star Wars Episode VIII: The Last Jedi

Now, in fairness, there is a bit more to the story than my very basic summary. But ultimately the idea behind this comic book is to tell us how DJ ended up in jail, thus setting up his encounter with our Resistance heroes. Frankly, I have no problem with this. I am all for minor characters from the Star Wars movies (and other stories) getting some interesting depth tacked onto them. This can be fun and can even be used to add fascinating concepts into the galaxy far, far away. Ultimately, this is what DJ: Most Wanted is meant to do – give DJ a little background and some extra dialogue, use him to provide a little more insight into the culture of Canto Bight, all while explaining how his story intersects and merges with The Last Jedi.

Because I was a bit “meh” about DJ in the film, reading DJ: Most Wanted DID give me some more insight into his character. But it didn’t do anything to really make me more interested in him in general.  I am not disappointed for taking the time to read it, or for even spending a few bucks on it (though I would never have paid full price), but I am also not necessarily ever going to say to myself “I need to re-read DJ: Most Wanted.” Perhaps someday I will, and I hope if/when that happens I can more fully appreciate DJ as a character. Although, to be perfectly honest, the likelihood of that happening really hinges on whether DJ makes more appearances in Star Wars stories in the future where he gains added depth from meaningful encounters with other characters in the franchise For example, I could easily see him interacting with Hondo Ohnaka, perhaps on Batuu (at the “Galaxy’s Edge”).

Unfortunately, I don’t get the impression there are any plans for DJ to receive more treatment any time soon. And if I am right, this is really too bad. I mean, at the very least, a Star Wars character played by Benicio Del Toro should be a bigger deal. Right?

Leave a comment and let me know what you think.

The “Sin” of Star Wars Expectations

I recently came across a quote from Frank Oz – the man who brought Yoda to life – where he gave his very direct opinion regarding Star Wars fans who disliked The Last Jedi. Speaking at a SXSW event, Oz states that,

“I love the movie [The Last Jedi]…All the people who don’t like this ‘Jedi’ thing is just horse crap. It’s about expectations. The movie didn’t fill their expectations. But as filmmakers, we’re not here to fulfill people’s expectations.”

How could I, or anyone else, NOT consider what Frank Oz has to say on this point? He is a gifted filmmaker with a perspective and understanding of storytelling which I can only dream of reaching. For a number of days I allowed Oz’s point to marinate in my mind, bouncing around my brain as I reflected on my own expectations for Star Wars, not to mention the expectations of the entire community of Star Wars fans. Of course, I am in no position to speak for the entire Star Wars “fandom.” It is so massive, so diverse, and so damn opinionated that it would be folly to even try to provide any “grand unified theory” to sum-up Star Wars fans. In fact, the ONLY thing that can be said is that Star Wars fans are “unified” around Star Wars, but what Star Wars means for each fan is subjective. It is personal. And because of this, I think Frank Oz is absolutely correct: some fans certainly disliked The Last Jedi because the film did not meet the very personal and deeply held expectations they may have had going into Episode VIII.

The thing is, while I agree with Oz, I only do so up to a point. Beyond that, I fundamentally disagree with him. Why? Well, just as I cannot provide a “grand unified theory” of Star Wars fans, Frank Oz is in no position to provide a definitive answer for why people did not like The Last Jedi. It is a generalization to do so, a fallacy stating that a part (those fans who did not have expectations met by The Last Jedi) actually represents the whole (every fan who did not like The Last Jedi). Logic just doesn’t work that way, and it is important to recognize that a great deal of nuance exists within the Star Wars community precisely because individuals have those deeply personal ties to the decades spanning franchise. And this applies to fans who truly loved The Last Jedi and those who absolutely despise the film, as well as all those who fall somewhere in the middle (which is where I happen to land). My point is: some Star Wars fans didn’t like The Last Jedi because it didn’t meet their expectations, plain and simple, while other fans had a more nuanced reaction and didn’t like it for a trove of entirely different reasons. 

But beyond this  pretty obvious fact, that some fans didn’t like it because of high expectations, the more I thought about what Frank Oz said, the more I was bothered by the implication: that Star Wars fans should have no expectations for the stories which they love. Realistically, how can one NOT have expectations when they go into a Star Wars film (or any film for that matter)? How does one fully set-aside their expectations and experience a story entirely devoid of expectation? Frankly, I do not believe it possible, unless perhaps one ejects every single Star Wars thought from the mind. But going into a Star Wars movie with a “tabula rasa”, a blank slate, is just not possible, at least for me. Maybe someone out there can show me how to do it, how to just sit down with popcorn, Junior Mints and an oversized cup of Diet Coke and watch Star Wars for what it is – just another movie. Me, I cannot set aside my thoughts, and feelings, and ideas about Star Wars because the franchise has seeped into my bones. I live Star Wars, I breathe Star Wars, it infects me like a damn virus. For me, Star Wars is NOT “just another movie,” it is a way of life. And as a result, I am guilty of the sin of expectation, I demand greatness from Star Wars and yes, sometimes, I even expect it to acquiesce to my expectations.

There were a lot of things about The Last Jedi I didn’t like, and some things I absolutely did like, and I lay a number of these out in my post Reflections on The Last Jedi.” But I also know, and can easily admit, that I had expectations for The Last Jedi which were not met. I am not ashamed to say it and why should I hide it? For example, I wrote a post titled The (Mis)Use of Captain Phasma where I blasted writer/director Rian Johnson for not utilizing the First Order villain more effectively in the movie. I absolutely expected her to be a greater factor, especially after a novel and a comic series preceding the release of The Last Jedi built her up as a total badass. How could I not expect more?

Luke and Ben

Many Star Wars fans, myself included, expected Luke to NOT try to kill his nephew given that he threw his lightsaber away at the end of Return of the Jedi. Photo Credit – Star Wars Episode VIII: The Last Jedi

So yeah, I had expectations for The Last Jedi. But you know what, I also had expectations for The Force Awakens, Rogue One, and Solo. I had expectations for The Phantom Menace, Attack of the Clones, and Revenge of the Sith. I had expectations for The Clone Wars, Star Wars: Rebels, and Star Wars: Resistance. And, going forward, I have expectations for Episode IX, The Mandalorian, Galaxy’s Edge, and every other Star Wars movie, novel, comic, video game, etc. But I am under no illusion that all of my expectations will be met. Are Star Wars filmmakers and storytellers supposed to meet every expectation of “the fans”? Certainly not. They can’t do it. At best, they can only hope to meet one very basic, very simple expectation: that the fan will be entertained. That is, after all, what the entire Star Wars franchise is, a massive form of entertainment. Right? We all expect to be entertained, to be transported to the galaxy far, far away so that through the experience we will find some form enjoyment.

And, as a fan, the best I can do is manage my expectations. I have to willing and able to acknowledge that everything will not line up with how I want it to unfold. But managing expectations does not mean jettisoning expectations. Rather, it means having an open-mind and giving things a chance, even when – no, especially when – things do not immediately line-up with those expectations. 

Frank Oz, the voice of Yoda, stated that “…All the people who don’t like this ‘Jedi’ thing is just horse crap. It’s about expectations. The movie didn’t fill their expectations. But as filmmakers, we’re not here to fulfill people’s expectations.” He is right, some fans didn’t like The Last Jedi because it just didn’t meet their expectations; others had more nuanced reasons for their dislike of the movie. And he is correct, filmmakers are not here to fulfill everyone’s expectations; and fans, myself included, do have to manage expectations. However, I am not going to give up my expectations for Star Wars. I am going to continue to demand greatness from it, and yes that means holding the filmmakers and storytellers to a high standard and having expectations for the franchise. And the reason I am going to do this is simple:

Because a long time ago I was mesmerized as I watched a small space ship being chased by a large space ship over a desert planet. From that moment forward, my expectations for Star Wars started to blossom and I can’t change that. So instead, I will live in the sin of Star Wars expectation and, if Frank Oz or anyone else wants to be annoyed with me, I will wear that annoyance as a badge of honor. 

Favorite Star Wars Music (by Film)

A long time ago…in 2017…I wrote a piece detailing why “The Imperial March” is my absolute favorite musical score in the Star Wars franchise. This admission came as little surprise to many of my trove of followers/readers as I have often professed my cultish admiration for The Empire Strikes Back (ESB) on this site. It stood to reason that The Imperial March would top my list considering the fact that the iconic anthem for the Galactic Empire/Darth Vader was first introduced in Episode V. Plus, given my “Casterfoian” obsession with the Empire, it stood to reason that I would likewise adopt the score as my all-time favorite.

While my unadulterated affection for all things ESB stands firm, and “The Imperial March” continues to receive constant replays on my Spotify account, there are never-the-less many other pieces of Star Wars music that have been elevated to the top of my musical mind. Hardly a shock – I am positive you can say the same if you happen to be a Star Wars fan – I wanted to take the opportunity to share a musical composition from each Star Wars film that I hold near and dear to my heart. For the sake of brevity, I have only chosen one from each film and decided to forgo long-winded explanations detailing why I love each piece, in large part because music is so damn personal it would take some of the fun out of it. Still, I may do a post for each at some point if the Force moves me to do so. We shall see.

Enjoy and be sure to comment with your own “faves” list!


A New Hope  “Tales of a Jedi Knight/Learn About the Force”


The Empire Strikes Back – “Yoda’s Theme”

While my heart will always be dedicated to “The Imperial March,” I decided to share another score from ESB in this particular list to mix things up a bit.


Return of the Jedi – “Leia’s New/Light of the Force”


The Phantom Menace – “The Droid Invasion and the Appearance of Darth Maul”

**Surprise! You were expecting “Duel of the Fates” weren’t you? Here is the deal: I love “Duel of the Fates” with a crazy passion but I likewise love “The Droid Invasion and the Appearance of Darth Maul.” I had to pick one and so I went with my gut. Besides, just listen to how the piece shifts when Maul is introduced! Holy frick that is haunting!!!!


Attack of the Clones – “Across the Stars”


Revenge of the Sith – “The Birth of the Twins and Padmé’s Destiny”


The Clone Wars – “Battle of Christophsis”


The Force Awakens “The Jedi Steps”

**I don’t care much for sentimentality but I readily admit that this piece gives me the feels. Like “Tales of a Jedi Knight/Learn About the Force”, “The Jedi Steps” packs an emotional punch by forcing me to imagine the Jedi Order, now a dying remnant, who once served and protected the galaxy far, far away. Between hearing this piece, and watching Rey literally walk the steps of the ancient Jedi, I was brought to tears in my first viewing of The Force Awakens.**


Rogue One“Your Father Would Be Proud”


The Last Jedi – “The Spark”


Solo: A Star Wars Story – “Savareen Stand-Off”

*Leave a comment with your thoughts about my list or share your own favorites!!!*

The Talker Toy Challenge Strikes Back

A long time ago in a galaxy far, far away…

Episode V

The Talker Toy Challenge Strikes Back

It is a dark time for the Star Wars fandom. Although December is approaching, DISNEY will not be releasing a new Star Wars film for another year, instead assaulting fans with a new cartoon show, a legion of mediocre comic books, and toys, lots and lots of toys.

Evading the dreaded lack of a Star Wars film, a group of bloggers led by THE IMPERIAL TALKER have struck back with a new version of THE TALKER TOY CHALLENGE, encouraging fans of the franchise to buy Star Wars toys and donate them to children who are in need this holiday season.

The DISNEY CORPORATION, obsessed with selling merchandise and increasing stock value for their shareholders, has dispatched thousands of new Star Wars products into the far reaches of the globe. Little does DISNEY know that THE IMPERIAL TALKER is ridiculously good at never paying full-price for merchandise, finding troves of fantastic Star Wars toys on sale and on clearance…


Participating in The Talker Toy Challenge is easy!!!! Just follow these steps.

Step One: Purchase Star Wars toys.

Step Two: Donate said Star Wars toys to children who are in need. I bring the toys I collect (see the featured image above) to a local Toys for Tots drop-off site. 

Step Three: Encourage others to do the same by promoting The Talker Toy Challenge on your blog, podcast, social media, etc.!!! Be sure to use #TalkerToyChallenge when you do!

Step Four: Repeat Steps One, Two, and Three.

Leave a comment and let me know if you participate!

Talkerverse: Snoke Goes Solo

In my previous post – Going Solo: Darth Maul – I considered Darth Maul’s (very) brief cameo in Solo: A Star Wars Story. I don’t want to spend a lot of time recapping that post, but I will note that in it I mentioned that his cameo, while certainly intriguing, left open the possibility of confusion for fans who had no idea he had cheated death in The Phantom Menace. I mentioned how in the lead up to his reveal in Solo, I really thought the mysterious figure behind the scenes of the Crimson Dawn criminal organization was going to be Snoke, the Supreme Leader of the First Order. While I was surprised by Maul’s cameo in the film, and otherwise enjoyed it, I cannot help but imagine the possibilities that might have been if Snoke had appeared instead of Maul.

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

Following the death of Dryden Vos, his lieutenant Qi’ra — who is also Han Solo’s friend/romantic interest —  contacts the mysterious figure coordinating the activities of Vos’ Crimson Dawn crime syndicate. Shrouded by a hood, the figure inquires why it is Qi’ra, and not Dryden Vos, contacting him. In reply, Qi’ra responds…

“Dryden Vos is dead.”

“Vos was a fool and deserving of death. Tell me Qi’ra, what of the coaxium?”

“Stolen from Vos by Tobias Beckett.”

“An unwelcome setback.”

Momentarily pausing, the mysterious figure continues…

“I sense conflict within you, young one. There is more to your story.”

“Beckett had an accomplice…someone I knew from my youth.”

“Is that so? And who was this accomplice?”

“A man by the name of Han Solo.”

Removing his hood, the figure in the hologram now reveals himself to be Snoke. Leaning forward, Snoke responds by repeating the name: “Han. Solo.”

“He means nothing to me,” Qi’ra quickly responds. “He is a remnant of my past.”

Snoke’s eyes linger on the woman, pausing to consider her words before he speaks…

“When I found you I saw raw, untamed power, a connection to the Force unlike any I have felt before. I pulled you from the gutters of Corellia, saving your from the life of a scumrat. And yet, my care is rewarded by the naïve feelings of child.”

“The fault is mine, Master. I beg your forgiveness.”

Sitting back in his chair, Snoke replies: “Indeed, the fault is yours. Return to me and I will break the chains of your…feelings…for Han Solo. “

Before delving into the “why” of the conversation I crafted between Qi’ra and Snoke, allow me to point out an obvious thought residing on the surface of my mind. I believe that Snoke should have been the mysterious figure in Solo: A Star Wars Story precisely because he was given no backstory in either The Force Awakens or The Last Jedi. While the need to know every detail of Snoke’s pre-Sequel Trilogy life is not entirely necessary, the desire to know more about Snoke is hard to ignore. That desire is precisely why, following The Force Awakens, individuals started creating theories about Supreme Leader Snoke, attepting to piece together who he might be. Unfortunately, this fun-filled theorizing was met with childish mockery from a the self-proclaimed “elites” of the Star Wars fandom when they chose to insult fan theories with the phrase “Your Snoke Theory Sucks” (I counter this petty derision in my post Your Snoke Theory Doesn’t Suck). But I digress…my base desire, wishing Snoke had appeared in Solo rather than Darth Maul, is a desire to have been given just a small glimpse into Snoke’s backstory, a tiny morsel that fans could run with in their theories.

On this point, Snoke’s presence could have created a connection between Solo: A Star Wars Story and the Sequel Trilogy which “film-only” fans could have more fully understood. As I noted in Going Solo: Darth Maul, the possibility exists (and is true in the case of my neighbors) that fans who only watch the Star Wars films would have a difficult time understanding how Darth Maul is alive since he so obviously died in The Phantom Menace. Instead of this unnecessary confusion, Snoke would have created an enticing connection between Solo and the Sequels Trilogy. Solo: A Star Wars Story could have been even more important, more relevant and necessary, with a brief cameo by the future Supreme Leader of the First Order, a cameo that would have created a connection through presence alone.

But this connection would have been blown wide open with Snoke’s conversation with Qi’ra, especially if the conversation echoed Snoke’s conversations with Kylo Ren. You will notice that in the dialogue I crafted Qi’ra mentions that “Han Solo” meaning nothing to her, an intentional parallel to Kylo Ren telling Snoke that Han Solo, his father, “means nothing to me.” In turn, the same form of parallelism exists in Snoke’s comment that when he found her, he saw raw, untamed power within Qi’ra, a similar statement he makes to Kylo Ren in The Last Jedi. Likewise, he insults Qi’ra, calling her a child, just as he insults Kylo Ren as “a child in a mask.”

Emilia Clarke is Qi’ra in SOLO: A STAR WARS STORY.
Han Solo’s childhood friend/lover: Qi’ra.

Photo Credit – Solo: A Star Wars Story

On one hand, these small dialogical parallels serve to solidify the way(s) in which Snoke manipulates individuals under his guidance, doing so by breaking them down and ensuring they understand that he is in control. But on the other hand, these parallels also, intentionally, link Qi’ra and Kylo Ren as Force-sensitive proteges of Snoke. In this regard, Snoke’s cameo would not have been the only surprise, but it would have included the added shock that Qi’ra can use the Force. In turn, as an added way of tying her to Kylo Ren, Qi’ra could have gone on to become the very first Knight of Ren, the Master of the Knights of Ren. And, in taking the mantle of title of Master for himself, Kylo Ren could have ripped it away from her when he killed her years later. Oh, the possibilities…

But there is one other angle worth considering in regards to Snoke and his imagined cameo in Solo: A Star Wars Story, and that is the fact that Han Solo’s life would play out with Snoke as a presence in the background. Through the manipulation of Snoke, Ben Solo became Kylo Ren and committed an act of patricide, killing Han Solo and freeing himself, albeit only in part, of his familial burden. Snoke’s relationship with Qi’ra could have served a similar fashion, functioning as a catalyst for events in Han’s life which would ultimately end with the smuggler’s death. Consider:

Han and Qi’ra were friends and lovers on Corellia. Han escaped Corellia but Qi’ra did not. Snoke found Qi’ra, freed her from the planet, trained her, and she became the first Knight of Ren. Years later, Ben Solo would become a protégé of Snoke, ripping the title of “Master” away from Qi’ra by killing her and completing his conversion to the Dark Side as Kylo Ren. In turn, as Kylo Ren, the former Ben Solo would end his father’s life on Starkiller Base.

From beginning to end, Han Solo’s fate, his story in Star Wars, would have been pre-determined and framed by the menacing actions of Supreme Leader Snoke.


The “Talkerverse” is my imagined Star Wars canon where I explore different angles on the galaxy far, far away by altering aspects of the Star Wars canon to fit my own wants and desires. Check out these other “Talkerverse” posts to delve even deeper into my Star Wars mind:

Talkerverse: Vader Kills Maul