hyperspace

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 

Imperial Interdiction

Two things before the post heats up…

  1. This post is going to have a bit of information from the Star Wars Rebels animated series, and the novels Tarkin and Heir to the Jedi. If you haven’t watched the show or read these novels, then consider this a “spoiler alert.”
  2. This entire post is one very large geek out. As you read, you will understand what I mean.

In a recent episode of Star Wars Rebels (Season 2,  Episode  9 – “Stealth Strike”), the intrepid heroes of the show encounter an Imperial weapon they have never before come across. That weapon is an Imperial Interdictor cruiser, a type of ship that actually made its first appearance in the EU novel Heir to the Empire years ago. I have always had an intense fascination with Interdictors, though this hardly means that other ships interest me less. No, what makes Interdictors so intriguing is that they have the capability of affecting one of the most important concepts in the Star Wars universe: hyperspace travel.

Interdictors work by using gravity-well projectors, devices that can create a gravity field and pull a ship (or ships) out of hyperspace and/or keep ships from entering hyperspace. As hyperspace is the only way to get from one place to another in the Star Wars galaxy, you can see why this sort of technology would be a big deal, especially if you are a Rebel vessel and need to escape a more powerful Imperial ship. If running away isn’t an option, then you’d better have another contingency plan.

In “Stealth Strike,” Ezra Bridger, Commander Jun Sato, and other rebels are traveling through hyperspace when their Corellian Corvette is suddenly ripped from hyperspace by an Interdictor. Unsurprisingly, the rebels are in utter confusion as they attempt to make sense of what happened. As far as the Rebellion against the Empire is concerned, this is the first time that Rebellion encounters this form of technology/weapon. But this shouldn’t be confused as the first canonical appearance of an Interdictor. No, the novel Tarkin was actually the first appearance for Interdictors in the new canon, and Heir to the Jedi closely followed. What is weird, though, is that the Star Wars Databank page for “Imperial Interdictor” doesn’t actually reflect the appearance of Interdictors in Tarkin or Heir to the Jedi. Instead the page makes it seem as though the ship has only appeared in Rebels.

TarkinCover
The cover of the novel Star Wars: Tarkin.
Photo Credit – LucasBooks

Further, while the Databank discusses the “Imperial Interdictor,” it should really mention that there is not just one type of Interdictor, there are actually three: the Detainer CC-2200, the CC-7700 Frigate, and the Immobilizer 418. While it’s an Immobilizer that appears in Rebels and Heir to the Jedi, in Tarkin, which is set 5 years after the events of Revenge of the Sith, the narrator indicates that it is the latest Interdictor to be constructed for the Deep Core Security Zone. As the novel points out, the Immobilizer arrives for an Imperial operation in the Obroa-Skai system “fresh from deepdock in the Corellia system” having yet to be tested, a clear indication that the other two vessels had, at the very least, been put through testing and/or utilized by the Imperial Navy previously.

Still, the Immobilizer,  which we learn in Tarkin has gravity-well projectors that are far more powerful than its cousins, does go on to become an important part of the Imperial Navy. This doesn’t necessarily mean the other vessels didn’t, but they also have not appeared in any other canonical source to date. The use of the Immobilizer by the Navy is confirmed, though, in Heir to the Jedi, a story which takes place between the events of A New Hope and The Empire Strikes Back. In that novel, Luke Skywalker’s vessel is pulled from hyperspace by an Interdictor in the Daalang system. Luke confirms that the vessel is an Immobilizer, and he explains to an individual traveling with him that “…the Empire has been using them against us [the Rebellion] on our raids.” However, Luke also notes in his inner-dialogue that “the Empire had stopped making these particular Interdictor cruisers because of their vulnerabilities” but “there were still plenty of them out there” even though they are no longer in production. In turn, Luke notes that the Empire had begun installing gravity-well projectors on Star Destroyers. From this statement, we can presume that along with the Immobilizer, the CC-2200 and CC-7700 were no longer in production either.

An Issue with Continuity

HeirtotheJediCover
The cover for the novel Heir to the Jedi.
Photo Credit – LucasBooks

For an otherwise less-than-stellar novel in the new canon, the scenario Luke and his companions find themselves in when facing the Immobilizer is a good one. In fact, I find it the best engagement that happens  in the book. But hidden within the situation is an otherwise off-the-cuff comment from Luke about the Immobilizer that makes little sense when we bring “Stealth Strike” into the conversation. In describing the Interdictor, Luke explains that “…this is one of the old models.” With the Immobilizer’s first appearance coming in Tarkin, at the very least 15 years (perhaps more) before Heir to the Jedi, then yes, Luke is correct, it is an older model. HOWEVER, “Stealth Strike,” which takes place 4-6 years before Heir to the Jedi, makes it very apparent that the aspiring Rebel cause has never encountered technology of this kind, which means they have never encountered an Immobilizer. To the rebels in the show, this ship and what it can do is entirely new, so how can it be an  “old model”?

Well, there are certainly some ways that we could fix this little continuity issue, but I also think it didn’t need to become an issue in the first place. Frankly, I am of the opinion that the showrunners of Rebels could have done more to connect the appearance of the Immobilizer in “Stealth Strike” to the vessels appearance in Tarkin. Had the rebels, even if briefly at the end of the episode, discussed the ship making its first appearance ten(ish) years before during an incident in the Obroa-Skai system, then Luke’s comment about the “old model” would make a lot more sense. But this isn’t what happens in the show. Instead, when the rebels are discussing this new ship, it is Sabine Wren, the young rebel and former Imperial cadet who states that when she was at the Academy, the Empire was developing gravity-well projectors. Disregarding the fact that the technology in question was highly classified and that a young cadet in an Outer Rim academy shouldn’t have access to that sort of information, the showrunners could have, at the very least, had Sabine mention the Immobilizer along  with the gravity-well technology when she brings it up. Or, she could have personally identified the ship as one of the models she had seen. Either option would have been fine.

SabineStealthStrike
Sabine Wren tells Hera Syndulla (foreground) about the gravity-well technology while Kanan Jarrus (background) listen on.
Photo Credit – Star Wars Rebels Season 2, Episode 9: “Stealth Strike”

But don’t take this to mean I dislike the use of the vessel in Rebels. Honestly, I love that it’s the centerpiece of the episode and that we get to see it in action. My point is merely that “Stealth Strike” could have, and should have, been used to create a stronger tie between the appearance of the Immobilizer/the gravity-well in Tarkin, the show itself, and Heir to the Jedi. In fairness, though, the show DOES create a fascinating technical tie with Tarkin, something that I think is worth exploring.

Overcurrent Resistors

In Tarkin, the Interdictors are brought to the Obroa-Skai system as part of an operation to capture a stolen Imperial ship. However, before the  operation gets under way, we learn from Kren Blista-Vanee, a member of the Imperial Ruling Council, that “the ships’ gravity-well projectors have not been tested” in the scenario that Moff Tarkin proposes. In short, the Interdictors have never been used to “yank” a ship out of hyperspace, making the situation all the more ripe for a mistake, particularly since the Obroa-Skai system is heavily trafficked.

And a mistake is precisely what happens.

When the Immobilizer powers up its gravity-well projects, the overcurrent resistors fail, causing the gravity-wells to redline and create an inderdiction field that is much too powerful. With the Immobilizer emitting an overly strong gravitational field,  all the ships in the system, Imperial ships and those being torn out of hyperspace, begin to be pulled inwards toward the Immobilizer. One of those ships is a Mon Calamari passenger liner with 10,000 beings on board and it is pulled directly into the Detainer, causing the passenger ship to break in half and many lives to be lost.  A chapter later, then, we learn that after the incident, the Immobilzer was sent back to Corellia so that the failure of the overcurrent resistors could be remedied.

Ten(ish) years later…

As the rebels in “Stealth Strike,” attempt to get off of the Immobilizer (they are literally on the ship for most of the show), the astromech droid Chopper connects with the ships mainframe and sabotages the gravity-well projectors. When the rebels finally make their get away from the Immobilizer, the commander of the Interdictor has his technicians turn on the gravity-wells to ensure that the rebels cannot escape to hyperspace. But something suddenly goes wrong. The rebel vessel, as well as two Imperial escort ships, begin to be pulled towards the Immobilizer. As the two frigates smashing into the Immobilizer, the rebel vessel is able to speed to safety as all three Imperial ships explode in a blaze of glory.

Immobilizer Destroyed
The rebels look on as a ship crashes into the Immobilizer.
Photo Credit – Star Wars Rebels Season 2, Episode 9: “Stealth Strike”

What did Chopper do to sabotage the ship? Answer: the little astromech messed with the overcurrent resistors, either turning them off or causing them to fail. Without the resistors ensuring that the gravity-wells did not redline, the interdiction field, like it does in Tarkin, becomes too strong and pulls all the vessels towards it causing havoc. A different situation, but an issue with the overcurrent resistors; one time due to malfunction, this time due to sabotage. And while the term “overcurrent resistors” isn’t even used in the show, the issue of ships being pulled towards the Immobilizer is really all the proof that is required for me to argue that Chopper did, in  fact, sabotage the resistors.

Then again, maybe the little droid does explain what he did to sabotage the ship and we just can’t understand what the heck he is saying. I mean, I dunno about you, but I don’t speak astromech….yet.