Canon and Continuity

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

The Fate of Master Sinube

Admittedly, writing a piece about “the fate of Master Sinube” is a rather straightforward endeavor. Barring some freak accident or a natural death, Tera Sinube – the elderly Jedi Master who assists young Ahsoka Tano track down lightsaber in The Clone Wars episode “Lightsaber Lost” – most certainly died during the Jedi Purge, his fate sealed when Order 66 was put into effect. In fact, we can probably be even more specific and say that he died in the Jedi Temple, perhaps shot by clone troopers or struck down by the blade of Darth Vader. True, he may have escaped the Temple on that fateful day, much like Jocasta Nu, perhaps fleeing individually or with other Jedi, but that also seems unlikely. No, I believe it is safe to say that Master Sinube encountered the same fate as most of the Jedi that day, meeting his end in a tragically violent way.

Sinube and Tano
Ahsoka Tano walks with Master Sinube.

Photo Credit – The Clone Wars Season 2, Episode 11: “Lightsaber Lost.”

While we may surmise that Sinube met his end on that fateful day, a question never-the-less persists in my mind: what were his final moments like? Where in the Temple was the elder Jedi and, like others in the Temple, did he put up any form of resistance? Personally, I like to believe he did. Elderly he may have been, his actions in “Lightsaber Lost” demonstrate that he was far from needing geriatric care. Master Tera Sinube most certainly did not go down without an act of resistance. In fact, we might take this thought a step further, extending the faculties of the imagination with a bold suggestion: on that horrible day, Master Tera Sinube stood his ground first against clone troopers, and then against Darth Vader.

Wisdom of a Jedi Elder

It is easy for me to believe that as the Temple came under attack, Sinube took it upon himself to safeguard Jedi younglings against the onslaught, perhaps even rallying a handful of Knights to lead the younglings away from the fray. I can picture Sinube giving orders, demanding that these Knights seek out one of Sinube’s contacts in Coruscants criminal underworld. Master Sinube was, after all, an expert on the underworld, and surely would have known a contact willing to help the Jedi flee the world. Implored by the younglings and Knights to join them, Master Sinube would have been reassuring but firm: “The Cosmic Force beckons me to return home. Go, I will hold off your pursuers.”

Clearly, there are any number of ways to imagine how Sinube’s final moments of life played out. Even as I write these words, the possibilities abound, the imagination running in numerous directions. But what my heart tells me is this: Master Tera Sinube did not even draw his lightsaber, instead leaving it confined in his cane. Wouldn’t this very contradict what I said in a paragraph about, that Sinube most certainly resisted the clones and Vader? Only if we assume that resistance must involve violence. 

A wellspring of Jedi wisdom and knowledge, thoughtful and patient in his actions (as we see in “Lightsaber Lost”), I believe Tera Sinube confronted his clone attackers that fateful day with only the Force as his ally. As the clones burst into the room, DC-15 blasters blazing away at an easy target, Sinube would move quickly, not harming but disarming his assailants. With care and precision, fully attuned to the Force, the Jedi Master systematically incapacitated the clone soldiers, debilitating but not killing, doing so with the gentle touch of the Light Side. 

Unable to break through the stalwart defense of their elderly opponent, comrades falling left and right – some getting back up to rejoin the struggle only to be knocked down again – eventually the word would spread through the Temple that the clones needed reinforcements to break through Sinube’s defense. And a reinforcement would arrive, not in the form of more clone squadrons, but the shadowy figure of a Dark Lord of the Sith. 

Vader March
Darth Vader marches into the Jedi Temple with his clone soldiers.

Photo Credit – Star Wars Episode III: Revenge of the Sith

Undoubtedly, Master Sinube could sense the Dark presence within the Temple from the very beginning of the attack. Now, as the clone assault on his position waivered once again, he felt the Dark figure moving towards him, and was about to enter the room. But Sinube, I am certain, also knew from the very beginning that the Dark Lord in question was, only recently, a Jedi. When the Sith entered the room, Sinube was calm and unsurprised – he knew he was about to see the face of Anakin Skywalker.

Vader’s blue blade already ignited, the two stood for a moment looking at the other. Suddenly, the blade was extinguished and Vader moved forward until he was but a foot or two from the elder Jedi. Extending his right arm, the Sith wrapped his hand around Sinube’s neck. But before he could squeeze, Master Tera Sinube looked into the eyes of his destroyer and, with peace in his voice, uttered his final words:

“I forgive you, Anakin.”

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!

Going Solo: Contispex I

Contispex I is a character who, although minor in the scope of Star Wars lore, has a story that I find intensely fascinating. Mentioned for the first time in a solitary paragraph in Daniel Wallace’s The New Essential Chronology (2005), with his story being expanded in subsequent reference books, Contispex I was a human and an ancient Supreme Chancellor of the Galactic Republic who, along with his descendants, launched numerous crusades against alien species and their human allies. An adherent of the zealous and extremist Pius Dea religion – a faith which, according to The Essential Guide to Warfare (2012), taught followers that  “…fallen communities should be restored to purity by purging their unredeemable elements…” (27)  – Contispex took the reigns of the Republic in the year 11,987 BBY and set about reforming the corruption of the Senate and government by placing Pius Dea faithful in positions of power.

What was, at first, a small religion dedicated to the worship of a Goddess and confined to the shadows of Coruscant where it began, Pius Dea quickly exploded into galactic prominence thanks to Contispex. Referred to as the Pius Dea Era  (ca. 12,000 – 11,000 BBY) in the Star Wars Expanded Universe, the millennia of Pius Dea rule which Contispex I instituted would see galactic purges, imprisonments, forced conversions, inquisitions and executions justified under the rallying cry that “The Goddess Wills It!” But it is the 30+ crusades of Contispex I and his successors which truly stand out, crusades that were launched to rid the galaxy of the scourge of alien civilizations. In 11,965 BBY the first crusade was directed by Contispex, a “pre-emptive strike against the Hutts beyond the Rim” according to The Essential Guide to Warfare (27). Subsequent crusades would be directed against other alien species: the Bothans, Lanniks, Zabraks, Herglics, and more.

Notably, during the Pius Dea Era the Jedi Order abdicated its responsibilities as peacekeepers and protectors, instead choosing to renounce its affiliation with the Republic. While individual members of the Order chose to challenge Pius Dea rule, as a whole the Order was “unwilling to take up arms against the civilization they had safeguarded” (27). This would change after almost 1,000 years had passed when the Jedi Order allied itself with oppressed species to overthrow Contispex XIX, arresting him and installing Jedi Grand Master Biel Ductavis in the Chancellorship (27).

While Contispex I truly is a minor character in the grand scope of Expanded Universe lore, as is the era of Pius Dea rule, I never-the-less find him intensely fascinating precisely because his story opens a vast window to the imagination. As someone who studied religion/theology in college and graduate school, the idea that the Old Republic succumbed to zealous theocratic rule in the name of “The Goddess” for nearly a millennia intrigues me and leaves me wanting to know more. Of course, at this point I have soaked up everything I can about Contispex I and the Pius Dea religion, having mined the tomes of Star Wars reference books for every morsel of information.

In fact, it was one very small morsel in a Star Wars reference book which led me to write this piece, a reference to Contispex I in Solo: A Star Wars Story – The Official Guide. Contained within The Official Guide to Han Solo’s standalone film is a page that is dedicated to the vast collection of rare treasures which Dryden Vos, leader of the Crimson Dawn crime syndicate, displays in the study aboard his star yacht. And, as The Official Guide notes, among this impressive collection of artifacts are “…arks that hold the ashes of Chancellor Contispex I…”

Contispex I
Image Credit:
Solo: A Star Wars Story – The Official Guide

As I said, a very small morsel indeed, but one that immediately caught my attention given my interest in Contispex I. On the one hand, what makes this nod to Contispex I important is that it re-affirms his place in the Star Wars canon. A minor character in the Expanded Universe, Contispex I is now, also, a minor character in Disney’s Alternate Universe. On the other hand, this is hardly surprising. While I was NOT expecting a reference to Contispex I in The Official Guide to Solo, that author Pablo Hidalgo – a member of the Lucasfilm Story Group – found a way to incorporate Contispex I into the book makes perfect sense. With Vos’ study populated by rare and ancient artifacts, Hidalgo could easily mine the ancient history of Star Wars confined within the Expanded Universe and provide readily available information about the artifacts without entirely having to re-create ancient Star Wars lore.

In fact, Hidalgo not only identifies the ashes of Contispex I in The Official Guide but he also attaches other elements of Expanded Universe lore to items in Dryden Vos’ study. A “crystal masthead” is identified as that of Xim the Despot while a dataplaque is noted as containing the location of the Xim’s long-lost treasure ship, the Queen of Ranroon. For those of you who are unfamiliar with Xim the Despot, he was first mentioned in the novel Han Solo and the Lost Legacy while the Queen of Ranroon received it’s first mention in Han Solo’s Revenge. As well, a carver set is noted to be that of Noghri origin, the species first appearing in Timothy Zahn’s popular novel Heir to the Empire, while a set of wraith boxes come from the long-extinct Rakata, a technologically superior civilization which was originally created for the Knights of the Old Republic video game.

While I highly doubt that Contispex I, the Pius Dea era, or other elements of the Expanded Universe which have crept into the Disney Canon will be teased out in greater detail, I am never-the-less pleased by the fact that these legendary aspects of Star Wars continue to have relevance. More importantly, these elements bring with them pre-crafted stories which need-not be reconstructed. Rather, they unify the Expanded Universe and Disney’s Alternate Universe in small, subtle ways. Contispex I may only ever have this one, small reference in The Official Guide to Solo: A Star Wars Story, but that reference is packed with the already rich story about Contispex and the tumultuous era of Pius Dea rule. As far as I am concerned, unless Contispex I receives a brand new tale which changes his narrative – a highly unlikely prospect – I will move forward with my enjoyment of Star Wars knowing that he, and the Expanded Universe I love, continue to add depth and meaning to the galaxy far, far away.

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