Poe Dameron

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 

Haikuesday: Recap

Haikuesday: Recap
Looking Backward and Forward
A New Haiku Dawn

In January 2017 I had this crazy idea: what if I wrote Star Wars-inspired haiku and posted them on the first Tuesday of every month. Thus, my Haikuesday series was born. Since the first Haikuesday was posted in February 2017, I have written fifteen other Haikuesday posts, the topic for each being chosen via polls on Twitter. Allowing my followers and others on Twitter to vote for each Haikuesday topic was a way to garner some fun and “fan”tastic support for the monthly series, and while all those who voted may not have gone on to read the haiku I wrote, it was never-the-less fun to know so many people were voting!

I am incredibly proud of the Haikuesday posts I have written, in large part because these posts have enabled me to explore my love of Star Wars in really unique ways. Never would I have imagined, when Haikuesday began, that I would have be scouring the Expanded Universe novel The Truce at Bakura for inspiration, or that I would be obsessively listening to Carl Orff’s O Fortuna (from Carmina Burana) as I wrote haiku about Darth Vader. I dug into my knowledge of the Star Wars: Uprising mobile-game (which I played obsessively before it was cancelled) for the haiku about Cloud City and was inspired by the poetry of Toru Dutt and Hindu mythology as I wrote about Queen Amidala. Long story short, Haikuesday has enabled me to explore not just Star Wars, but a wealth of other music, art, literature, and more in really interesting ways.

At the same time, the writing of Haikuesday posts has taken numerous forms, and happened at pretty random times. For many of the sixteen posts, I would work on the haiku over the course of the week leading up to Haikuesday. Sometimes my inspiration would come late in the process, and I would still be writing haiku an hour before I planned on actually publishing. More often than not, though, the haiku would be completed in advance of Haikuesday. As well, many of the haiku were first written by hand, and I have two notebooks filled with my Star Wars-inspired poetic creations. As I told my friend Kiri from the site Star Wars Anonymous (who write some of her own Star Wars haiku!), I often keep a notebook with me to ensure that I can write a haiku if it pops into my mind. And, in those moments when I do not have a notebook, my iPhone comes in pretty handy.

There are definitely some other little things about Haikuesday I could mention, but realistically, and for the sake of brevity, I will skip all of that. Like, you don’t really care that I wrote most of The Battle of Scarif haiku in the backseat of a car, Rogue One: The Visual Dictionary by my side, on a road trip from Detroit, MI to Alexandria, VA…do you? Naw, of course you don’t care, so I won’t share that with you. And I definitely won’t share that I wrote all of The Battle of Umbara haiku in a note on my phone (I remember when phones were just used for making calls and not writing haiku. Those were the good ole days…in the 1990s). 

So, what is next for Haikuesday? Well, first and foremost, a much-needed creative break. I love rendering Star Wars in haiku form but my brain is tapped out right now. For right now – meaning for a few months – I am taking a break from Haikuesday to focus on some other Star Wars posts I have wanted to nail down for this site. In fact, now that this site is over three years old, I have quite a few ideas moving forward…including plans to FINALLY do Wookiee Week (but more on that later). As for Haikuesday, I already have some fun and innovative ideas to revamp it, changing how I approach it – from when/how I write, to the topics, and getting Star Wars fans (you!) involved in writing haiku! I even have this crazy idea to do an entire Haikuesday post in Aurebesh…

But all of that is in the future. For now, I hope you will take some time to read (or re-read) and share my Haikuesday posts. Leave a comment on them, tell me what you like, and if you have any thoughts/ideas on helping me make Haikuesday even more successful I am all ears!

Below are all of the featured images I used for every Haikuesday (with links to each post in the captions).


oom_battle_droids-2
Droids















Thrawn TIEFighter
Thrawn

Haikuesday: Poe Dameron

Star Wars Trivia:
Poe’s parents fought for Rebs at
Battle of Endor


Mission to Jakku.
Poe handed crucial info.
First Order arrives.


A battle ensues,
Dameron sprints to his ride.
“Come on BB-8!!!”


His X-Wing damaged,
Poe passes the mission off
to his trusted droid.


Taking aim, Poe shoots.
A trooper is hit, goes down.
Blood. Pain. Death. Panic.


Lor San Tekka killed.
Dameron reacts, fires.
Frozen by the Force.


Interrogation.
Torture. Pain. Resilience. Grit.
Kylo will break Poe.


“The right thing to do.”
“You need a pilot,” Poe says.
“I need a pilot.”


TIE Fighter stolen.
Dameron heads to Jakku.
Finn isn’t happy.


TIE Fighter crashes.
Poe is no where to be found.
His jacket remains.


I have to be frank:
I never understood how
Poe just disappears.


Fast-forward the film:
Now we’re on Takodana
and Poe reappears.


“Fighters incoming!”
“It’s the Resistance,” Han says.
Poe leads Black Squadron.


Star Wars Trivia:
Poe flies a T-70
known as the Black One.


Dameron blasts TIEs.
“That’s one hell of a pilot!!!”
Ace in a dogfight.


Poe and BB-8,
pilot and droid reunite
at Resistance base.


Finn looks on, sees Poe.
Dameron looks up, sees Finn.
The two friends embrace.


Scrubs: Turk and J.D.
“It’s guy love between two guys.”
Star Wars: Finn and Poe


I have to be frank:
Oscar Isaac, who plays Poe,
is one handsome dude.


Star Wars Trivia:
Poe flew with the Republic’s
Rapier Squadron


“Disable the shields.”
“Take out the oscillator.”
“Blow up their big gun.”


 Preparing to fight,
the Resistance springs to life.
Poe readies his ship.


Base to Black Leader:
“…go to sub-lights on your call.”
Poe gives his orders.


Leading the X-Wings.
“Hit the target dead center.”
TIE Fighters inbound.


Hole in the target,
Dameron creates a plan.
He just needs cover.


Into a long trench,
Poe is pursued by TIEs and
targeted by guns.


“I need some help here.”
Ello Asty is destroyed.
Black Leader persists.


Threading the needle.
Poe blasts the oscillator.
Proton torpedoes.


Thermal Exhaust Port
and Thermal Oscillator.
Thermal Bros – Luke, Poe.


“Starkiller” destroyed.
“Our jobs done here, let’s go home.”
Hard fought victory.


I’m of the belief
that Poe should be given the
nickname “Starkiller”


Leia: Huttslayer
Poe Dameron: Starkiller
You know you want this.


Haikuesday is a monthly series on The Imperial Talker, a new post with poetic creations coming on the first Tuesday of each month. The haiku topic is chosen by voters on Twitter so be sure to follow @ImperialTalker so you can participate in the voting. Now, check out these past Haikuesday posts:

Droids (February 2017)

Ahsoka Tano (March 2017)

Darth Vader (April 2017)

The Battle of Scarif (May 2017)

The Truce at Bakura (June 2017)

Queen Amidala (July 2017)

Ryloth (August 2017)

Cloud City (September 2017)

General Grievous (October 2017)

Millennium Falcon (November 2017)