Poe Dameron

The (Mis)Use of Rose Tico

I wasn’t a huge fan of The Last Jedi. I explain as much in my piece Reflections on The Last Jedi (which you can read for yourself). But while I did not find it as groundbreaking as other Star Wars fans, neither did I fully despise the film. I could appreciate the film at points, acknowledging that the movie presented clever and unique ideas, along with some interesting new characters.

Two of those characters were the Tico sisters: Paige and Rose. While Paige Tico only appears at the beginning of The Last Jedi as a ball gunner in a Resistance bomber, her small role is massive in that she sacrifices herself to destroy a First Order dreadnaught which threatens the Resistance fleet. Grasping the crescent necklace around her neck, Paige Tico dies in order for others, including her sister Rose, to live.

Rose, in turn, makes her appearance after Paige’s death, when Finn comes across  her as he attempts to leave the Resistance fleet. Rose, grasping her own crescent necklage, sits in tears. Introduced by this obvious connection to her sister – and subsequently mentioning her sister to Finn – Rose ends up going on an adventure with Finn and BB-8 to the planet Canto Bight. In turn, Rose, Finn and BB-8, accompanied by the slicer DJ, eventually make their way to the First Order fleet chasing the Resistance fleet in the hopes of disabling the First Order’s hyperspace device. Captured while aboard the First Order Mega-Star Destroyer thanks to the betrayal of DJ, Tico and company end up stealing an enemy shuttle in order to make it to the new Resistance base on the nearby planet Crait.

Once on Crait, Rose participates in a desperate ground battle with her allies, piloting a ski speeder against overwhelming First Order numbers in the hopes of destroying the enemy battering ram cannon. Finn, whom Rose has grown close to by this point in the film thanks to the adventure to Canto Bight and the First Order Star Destroyer, chooses to sacrifice himself when all hope seems lost, piloting his ski speeder towards the massive cannon. But at the last minute, Tico crashes into Finn, pushing him off course. In turn, Finn will run to Rose, pulling her from the wreckage but first questioning why she crashed into him. Rose, bleeding and shaken, will explain to Finn that  “…we’re gonna win, not fighting what we hate, but saving what we love.” Rose then kisses Finn before she passes out from her wounds. Dragged back to the Resistance base by Finn, the unconscious Rose will survive the Battle of Crait with the remaining Resistance fighters aboard the Millennium Falcon.

Rose Finn Kiss
Rose and Finn kiss during The Battle of Crait
Photo Credit – Star Wars Episode VIII: The Last Jedi

When I saw The Last Jedi, I thought Rose Tico was an interesting and well-developed character even though I did not entirely care for the adventure she takes to Canto Bight or the First Order Star Destroyer. What drew me to Rose was her hopeful spirit, her resilience, her internal confidence, and her desire to help others. She is introduced in The Last Jedi as a character who is overwhelmed by the loss of her sister but also inspired by her sister’s heroic sacrifice. When she meets Finn, she is equally overwhelmed, amazed she is speaking with the First Order stormtrooper-turned-Resistance hero who also inspires her to keep fighting the good fight. Filled with deep admiration for the heroes in the Resistance, Rose Tico is the embodiment of the heart and fighting spirit which keeps the Resistance going, a perfect example of the “spark that’ll light the fire that’ll burn the First Order down.” 

But this brief overview of Rose and her role in The Last Jedi is a means to an end, a small set-up to arrive at the larger point of reflection I wish to discuss: the way Rose Tico was (mis)used in The Rise of Skywalker.

The (Mis)Use of Rose Tico

When I went into my first viewing of The Rise of Skywalker, the final installment of Disney’s Star Wars sequel trilogy, I did so with the presumption that Rose Tico would be an important player in the events which would transpire. My presumption, unfortunately, was wrong.

Violet Kim, a journalist for Slate, recently published a short piece about Rose Tico’s notable absence from The Rise of Skywalker. In the piece, which you can read HERE, Kim notes that Rose appears on-screen in The Rise of Skywalker, a movie with a run-time of 2 hours and 22 minutes, for only 1 minute and 16 seconds.  As a point of contrast, Kim goes on to note that in The Last Jedi, which has a run-time of 2 hours and 32 minutes, Rose is on-screen for 10 minutes and 53 seconds. 

Even without the breakdown into minutes and seconds – which is, admittedly, pretty eye-popping – it is obvious that Rose’s role in the film is lacking. And I am not going to lie, this (mis)use of Rose Tico left me feeling equally perplexed and upset. In part, I felt this way because after The Last Jedi, actress Kelly Marie Tran, who plays Rose, was assailed online with racist and sexual harassment which in turn led Tran to delete her social media presence. In a sense, the lack of screentime for Rose in The Rise of Skywalker makes it seem as though these online trolls actually got their way, that they were successful in getting a principal character, a woman of color, sidelined in the film. Because of the nasty vitriol which Kelly Marie Tran was subjected to following The Last Jedi, it was even more critical and important for J.J. Abrams and Chris Terrio, co-writers of The Rise of Skywalker, to find ways to raise Tico’s profile in the movie. That this did not happen is not only unfortunate, but it makes one wonder if Abrams and Terrio took Tran’s harassment seriously or considered the possibility that if Rose was not featured more prominently in the film that her absence would embolden the trolls who attacked Tran in the first place.

In their defense, Terrio did come out and explain that Rose was intended to be more prominent in the film. As he explains in an interview with Clarence Moye of Awards Daily, he and Abrams,

“…wanted Rose to be the anchor at the rebel base who was with Leia. We thought we couldn’t leave Leia at the base without any of the principals whom we love, so Leia and Rose were working together. As the process evolved, a few scenes we’d written with Rose and Leia turned out not to meet the standard of photorealism that we’d hoped for. Those scenes unfortunately fell out of the film.”

That Rose was to be featured more in the film, albeit before the editing process took over, is certainly positive. And that she was to be the principal character interacting with Leia is notable even if a number of those scenes were cut from the film. But while I can grant this point to Terrio and Abrams, applauding them for wanting Rose to work closely with Leia, I can simultaneously admit that I find Terrio’s response vague and unconvincing . It is all well-and-good to say that he and Abrams intended for Rose to be in the film more than she is, working alongside Leia, but the fact remains that she is barely in the film (even though Tran herself has noted that she filmed other scenes for the movie). And as a result, her story feels truncated, abruptly cut-off in the wake of The Last Jedi without any sense of finality.

This is all the more disappointing when we consider that the signature moment for Rose in The Last Jedi, the moment she saves Finn from his hatred for the First Order and then kisses him, is entirely ignored in The Rise of Skywalker. Given the adventure they go on in The Last Jedi, Rose obviously started having strong feelings for the former Stormtrooper. Whether Finn felt the same way is left unanswered at the end of The Last Jedi, but The Rise of Skywalker is uninterested in exploring this possibility, or even addressing it. Instead, The Rise of Skywalker seems content to ignore Rose’s kiss and her feelings altogether, instead focusing more on Finn’s connection with Rey, and his relationship with Jannah (another former Stormtrooper who is introduced half-way through the movie). It is as if The Rise of Skywalker is engaged in the narrative “ghosting” of Rose, with Finn purposefully ignoring her because he has other things to do and people (Rey, Poe, C-3PO, Chewbacca, BB-8,and the new droid D-O) to be with. 

Rose Tico Exegol
Rose Tico during The Battle of Exegol, one of the few times we actually see her in the movie.
Photo Credit – Star Wars Episode IX: The Rise of Skywalker

Again, in fairness, this is not to say Rose is not given the chance to join Finn and the others on their galactic scavenger hunt. When she is asked to come along, Rose responds with a narratively contrived reason she needs to stay at the Resistance base: because the General, Rose explains, needs her to analyze the specs of the old, Imperial-class Star Destroyers. With the intention of making Rose the principal with Leia, this ensures that we are all filled-in on why Rose is hanging back. Sadly, with her scenes with Leia being edited out of the film, her need to analyze Star Destroyers instead feels like an excuse to remove her from the main plot of the film, sidelining her so the real heroes can hang out on the Millennium Falcon and save the galaxy. 

But the thing is, as I watched The Rise of Skywalker and went on the galactic adventure with the films principal heroes – Rey, Finn, and Poe – I found myself missing Rose even more. I sat and wished she was part of the team, having the chance not only to have a heart-to-heart with Finn during their travels, but also the opportunity to get to know Rey, laugh with Poe, play (and even beat!) Chewbacca at dejarik, work side-by-side with BB-8 and C-3PO, and show kindness to the skittish D-O. Moreover, I found myself wishing Rose Tico was there so she could continue to be “the spark” of Resistance she so fully embodied in The Last Jedi, her heart and fighting spirit, and the crescent necklace around her neck, used as a constant reminder to the heroes (and viewers) that winning would be accomplished  “not fighting what we hate, but saving what we love.”

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)