Chewbacca

The Death of Chewbacca

In 25 ABY, Chewbacca died on Sernpidal when Dubido, the planet’s smallest moon, crashed into the world. Moments before his death, Chewbacca had heroically saved the life of Anakin, the youngest child of Han Solo and Leia Organa Solo. Having been caught in high winds due to the impending disaster, Chewbacca sprang into action to save the teen, returning him to the Millennium Falcon. But more winds picked up, this time knocking Chewbacca away from the Falcon. With Anakin at the controls of the freighter, Solo stood on the ramp scanning the area, seeing his Wookiee friend in the distance. Anakin though, recognizing the peril they were in, made the difficult but necessary decision to pilot the Falcon away, leaving Chewbacca on the surface of Serndipal, howling in courageous defiance, as Dubido crashed into the planet.

Depicted in the 1999 novel The New Jedi Order: Vector Prime by R.A. Salvatore, the death of Chewbacca was the first major loss of a main character from the Original Trilogy films to take place in Star Wars. It was as shocking as it was unexpected, a heroic but tragic end for the beloved Wookiee. As an adolescent Star Wars fan, only 14-years-old at the time, it was difficult processing Chewbacca’s death. This was not because death was a foreign concept to me, or because I was naïve in thinking our heroes live forever. Rather, it was because his death felt like the loss of a close friend. Chewbacca may have been Han Solo’s loyal companion, but he felt like MY loyal companion as well, and the unexpected loss of the Wookiee left a hole that was, at the time, difficult to fill.

To the intensity of Chewbacca’s death was added the emotional turmoil it exacted on the other characters, particularly Han and Anakin. Almost immediately, even before the Falcon left the Serndipal system, Han blamed Anakin for the death of Chewbacca, a rift opening between the father and son. Anakin justified his decision, pleading that he had no choice, there was no way to save Chewbacca and escape the unfolding cataclysm. Plus, he would remind his dad, they had refugees from Serndipal on-board, they were responsible for these lives and had to get them out of harm’s way. Han was unconvinced, unable to process the pain of his dear friend’s demise, he would continue to lay blame at Anakin’s feet for the remainder of the novel, and while healing the rift between father and son would begin by books end, healing the inner turmoil each felt would not abate. In the next book in the series, Dark Tide I: Onslaught by Michael A. Stackpole, Anakin would continue to question his actions, convinced he had caused Chewbacca’s death. And Han, in his only appearance in the novel, is disheveled and obviously drunk, trying but failing to cope with the Wookiee-sized hole in his heart.

Chewbacca’s image memorialized in a tree on the planet Kashyyyk.
Photo Credit – Star Wars: Chewbacca (Dark Horse Comics)

Shocked by his death I wished that Chewie would miraculously return. Yet, I also knew Chewbacca was not coming back from the dead even though he could and would still appear in stories prior to the cataclysm on Sernpidal. And appear he did in a unique form almost immediately. Published a couple months after Vector Prime was released, the Dark Horse comic series Star Wars: Chewbacca offered unique, in-universe tributes to the recently deceased Wookiee. These stories allowed the most memorable characters like Luke, Leia, and Han to reminisce and offer personal reflections on Chewbacca’s life. Likewise, those who did not feature in the Star Wars films, such as Chewie’s wife Mallatobuck, offer tales which expanded on the Wookiee’s exploits, further illuminating his already remarkable narrative.

While the Chewbacca comic series offered a moment for characters and fans to reminisce on Chewbacca’s life, the fact remained that he was gone. At least, that was the case until Disney wiped the slate clean, removing Vector Prime and the death of Chewbacca from the Star Wars canon. Relegating the Expanded Universe to the realm of “Legends” in 2014, Disney/Lucasfilm chose to resurrect Chewbacca with the introduction of a brand-new storyline. Admittedly, this was an unsurprising move on the part of “the House of Mouse,” one that was even understandable. With new films on the horizon in 2014, the powers-that-be needed to ensure that fans who only watched the Star Wars films did not need to play catch-up on the galaxy, reading and learning about events/characters spanning decades “in-universe.” Thus, if Chewbacca were to die once more it would be under different circumstances, which brings us to a rather jaw-dropping moment in The Rise of Skywalker.

The “Death” of Chewbacca

Having just been captured on the desert planet Pasaana by a couple Knights of Ren, Chewbacca is loaded onto a transport to be whisked off to a First Order Star Destroyer. But as the transport lifts off the ground, it is caught in the middle of a struggle of wills between Kylo Ren and Rey. Seeing the transport with Chewie moving away, Rey reaches out with the Force, stopping the vessel in mid-air. Kylo Ren also reaches out with the Force, attempting to snatch the transport away from Rey. Digging deeper and deeper into themselves and their connections to the Force, Rey suddenly taps into something hiding far beneath the surface: the Dark Side of the Force. Force-lightning shoots from her fingers, hitting the transport and killing all on-board, Chewbacca included.

Rey’s reaction after she kills Chewbacca.
Photo Credit – Star Wars Episode IX: The Rise of Skywalker

The scene is stunning, a prime example of a “holy shit” moment that made my jaw drop. Not only has Rey, the heroine of the Sequel Trilogy, used the Dark Side, her action also results in the death of her friend, her co-pilot, and a beloved Star Wars character. The implications are far-reaching and gut-wrenching. Going forward, her other friends – Finn and Poe – must be exceedingly cautious around her, wondering if Rey will be set-off again, perhaps even killing them! Rey, too, must question the same, struggling with having killed Chewie and considering the threat she poses to the others. As an audience, we too must tread lightly with Rey, the death of Chewbacca serving as the beginning of her turn to the Dark Side of the Force, her premonition of sitting on the Sith throne, which she describes to Finn, now a very real possibility.

Except, none of that happens. Even though The Rise of Skywalker provides an unquestionable “holy shit” moment on par with other “holy shit” moments in the Star Wars franchise, the film goes out of its way to reassure us that Chewbacca is not dead. Exactly two minutes and six seconds after the electrified destruction of the transport we discover out that Chewbacca is now a prisoner on-board a First Order Star Destroyer. Although we initially saw Chewbacca being loaded onto a First Order transport, and we hear Finn emphatically declare that Chewbacca is on the transport which Rey in turn destroys, as an audience we get to breath a collective sigh of relief that our favorite Wookiee has not met his demise because he was, in fact, on a different transport.

Chewbacca, captured by the First Order, expresses his displeasure.
Photo Credit – Star Wars Episode IX: The Rise of Skywalker

Additionally, while the audience discovers right away that Chewbacca is alive, slightly more time will pass, fourteen minutes and nine seconds in film runtime, before Rey discovers that she did not kill her friend. When the aforementioned Star Destroyer arrives in orbit above Kijimi, the planet the Resistance heroes travel to following Pasaana, Rey will sense Chewbacca’s presence, knowing in that moment he is still alive. That Rey can sense him here and now and could not do so right after she “killed” him on Pasaana is a point the film conveniently ignores. Regardless, knowing that he is on the orbiting vessel, the group set out to free their friend, infiltrating the Destroyer and rescuing the Wookiee from his temporary First Order captivity. Although doing so will waste valuable time in their quest to save the galaxy, another point that is otherwise ignored, the rescue mission will end successfully, bringing Chewbacca’s non-death story-arc to its finale.

Facing Death

What begins as a “holy shit” moment in The Rise of Skywalker ends up being nothing more than a narrative bait-and-switch which happens at lightspeed. In all honesty I’m not sure why the movie so rapidly reassures us that Chewbacca is not dead, undercutting the shock of his death just as we begin to process it. It’s as if writer/director J.J. Abrams did not trust the audience to struggle with the emotional turmoil of Chewbacca’s loss, at least not for more than the two minutes and six seconds we believe he is gone.

Additionally, just as I fail understand why we were reassured of his survival so quickly, I likewise find it difficult to grasp why his death was not permanent. As I explained, his death would have added long-term ramifications to the narrative beyond the immediate shock value it provides. Moreover, Chewbacca should have stayed dead because after he is rescued, he has no real utility for the remainder of the film, being given very little and often peripheral screen-time. True, he does momentarily mourn Leia’s passing when he is told she has died, and at the end of the movie he is given a medal by Maz Kanata, an obvious call-back to the medal ceremony in A New Hope (I will address this topic in a separate post). Otherwise, after Chewbacca’s survival/rescue, he is really just along for the ride, offering little but his presence to the plot.

Perhaps most importantly, though, maintaining Chewbacca’s death would have served as a reminder to audiences that death is something we must all face, as terrifying as that may be. I certainly do not begrudge those who were relieved, like Rey, Finn and Poe, that Chewbacca survived in The Rise of Skywalker. I get it, I really do. It is hard to encounter death, especially the death of a beloved character. It can cut you to the core. And discovering they are still alive is a blessing and a huge relief. When Chewbacca became the first Original Trilogy character to die in the Expanded Universe it ripped my 14-year-old heart out. I was in disbelief that the Wookiee was no more, I wanted him to still be alive, but my disbelief and all of the accompanying emotions were necessary parts of the grieving process. I was in denial but, deep down, I knew, just like Han and Anakin did, that Chewbacca was no more. In this way, Chewbacca’s heroic but unexpected demise in Vector Prime reminded me, as I am sure it reminded so many other Star Wars fans at the time, that death, as Yoda would go on to say in Revenge of the Sith, is a natural part of life.

In her book A Short History of Myth, author Karen Armstrong notes that myth “is nearly always rooted in the experience of death and the fear of extinction.” We are, Armstrong points out, “meaning-seeking creatures,” and a great many of the myths we have told for millennia have attempted to find meaning in the reality of death. In this vein, Vector Prime and the stories of The New Jedi Order served then, and still serve today, as a continuation of the modern-day myth that Star Wars was always meant to be, forcing us in this particular case to confront and wrestle with what it means to be mortal. Chewbacca’s death in Vector Prime is a mirror in which we are meant to see ourselves, our fragility, our own extinction. Like Chewbacca, we cannot escape our finite existence, but what we can do is face it, face it with the same howling defiance of a mighty Wookiee.

Haikuesday: Chewbacca

Loyal Companion
Solo’s co-pilot best friend
Mighty Chewbacca

Shiny Bandolier.
Signature Accoutrement.
Oh, and his man purse.

“He’s goes ‘Rrrrrrwwwwwooooooorrrrr’
and they’re all like ‘that’s a good
point bear, let’s try that.'”


If you haven’t watched
How I Met Your Mother then
you won’t get the joke.

In a Cantina,
Old Ben meets with a giant.
A fur-covered beast.

Star Wars, Hendersons:
Chewbacca versus Harry.
Who would win the fight?

Actually, I think
the two would ultimately
end up being friends.

Haiku Addendum:
Chewbacca kinda, sorta
looks like a Sasquatch.

Ode to Bigfoot Craze?
In the seventies, Bigfoot
was all of the rage!

Last thought on subject –
Harry and the Hendersons
is such a great film.

Playing Dejarik.
Not wise to upset Wookiees.
“Let the Wookiee win.”

Aboard the Death Star
Luke Skywalker has a plan
but Chewie hates it.

“Prisoner transfer”
“Where are you taking this thing?”

Chewbacca gets loose!

Hold up a second…
…do you think Bigfoot is real?
It’s possible, right?

Maybe George Lucas
went in the woods and saw one!
That would be crazy!

Garbage Chute Escape:
Chewie doesn’t want to go
because it smells bad.

Compactor Escape:
Chewie is afraid and hides.
It’s adorable.

A royal insult:
Leia is annoyed by the
“Big walking carpet.”

Haiku Addendum:
It’s pretty crappy that she
is mean to Chewie.

Seriously though,
Bigfoot is totally real.
I’ve seen the creature!

Han chases Stormies.
And Chewbacca chases Han.
Stormies chase them both.

Flying the Falcon
The Wookiee pilots the ship
while Han man’s the guns!

Chewie and Leia
embrace in a heartfelt hug.
Now the two are friends!

I have a question:
Did Leia apologize
for insulting him?

Alright, honestly,
it was probably a bear
that looked like Bigfoot.

It would be funny
if Sasquatch are real and they
all wear bandoliers.

It would be funny
if Sasquatch are real and they
all wear a man purse.

Han gets his reward…
…but did Chewie receive a
reward for his role?

To hell with medals!
I hope Chewie got some cash!
#JusticeForChewie

Hold on a second…
Perhaps he gave Han his share
to help pay Jabba.

Loyal Companion.
Chewbacca is a good friend.
Solo is lucky.

Harry is also
a really good friend to the
Henderson family.

Alright, so, medals –
Chewie doesn’t get one and
I don’t really care.

Some people do care.
Like J.J. Abrams, he cares.
But I do not care.

Here’s why I don’t care:
Luke and Han are the focus
Chewbacca is not.

Plus, consider this:
do you see Chewie in the
Battle of Yavin?

Hold up, you know what
I’ll just write a post about
it and go from there.

Moving right along…
Chewie does some stuff in V
and in VI. The End.

Do you like Chewie?
Do you have thoughts on Bigfoot?
Leave comments below!

Oh, before I go…
The Wampa is a yeti.
I’m sure you knew that.

Haiku Addendum:
Bigfoot, Yeti, they aren’t real.
Except they are real.


Check out these other Haikuesday 2.0 posts:

Imperial Atrocities

Luke Skywalker (ANH)

Luke Skywalker (ESB)

Luke Skywalker (ROTJ)

Dark Lords of the Sith

Star Wars Planets

The Great Jedi Purge

Star Wars Aliens

Clone Troopers

Finn (TFA)

E-3PO: The Rude Protocol Droid

The moment in The Empire Strikes Back is brief but memorable, a short exchange between protocol droids. Having just landed on Cloud City, and meeting Lando Calrissian for the first time, Han Solo, Princess Leia, Chewbacca, and C-3PO follow Calrissian through the halls of the atmospheric metropolis. As they all turn a corner, a door on the right opens and standing before C-3PO is a droid that looks similar to him, another protocol droid: E-3PO (first identified by name in the Star Wars Customizable Card Game). Their conversation goes like this…

C-3PO: “Oh, nice to see a familiar face.”
E-3PO: “E chu ta.”
C-3PO: “How rude!”

And, yeah, that’s it. Like I said, the moment is brief, and as E-3PO walks-off, C-3PO goes on to get himself shot by stormtroopers. Where E-3PO goes once exiting the scene is unknown, this short appearance and one-liner being it’s singular moment to shine in the film, doing so by jumping on the C-3PO insult wagon. It is worth remembering that up to this point in The Empire Strikes Back, our favorite protocol droid has been the butt of a number of jokes in the movie, primarily due to his penchant for annoying those around him…especially Han Solo. I won’t list these moments as you should be familiar with them (if not, go watch the movie?), but with these moments in mind we can all pretty easily understand why C-3PO, when he literally comes face-to-face with another protocol droid, would say it is “nice to see a familiar face.” That E-3PO instead reacts by being rude is just fantaaaaaaaastic, a sign that C-3PO doesn’t just annoy his human allies, but instantaneously annoys other droids just by speaking. 

But what does this Huttese phrase which E-3PO levels, “E chu ta“, actually mean? More importantly, does it even matter? The basic fact is that it is clearly an insult, a form of Huttese curse, and it works even better without knowing what it “officially” means. The imagination is more than capable of filling in the blank. And since that’s the case, I will just offer what I like to believe the “rude” E-3PO is saying…

C-3PO: “Oh, nice to see a familiar face.”
E-3PO: “Eat shit.”
C-3PO: “How rude!”

You gotta admit that “E chu ta” does kinda sound like “Eat shit.” 😉


Check out these other posts about random protocol droids in Star Wars:

U-3PO: The Other Protocol Droid

K-3PO: The Dead Protocol Droid

4A-R2: The Pirate Protocol Droid

4-LOM: The Bounty Hunting Protocol Droid

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

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.

Haikuesday: Luke Skywalker (ANH)

Tatooine farm boy.
Dreaming of a greater life.
Craving adventure.


Bad motivator.
3PO suggests R2.
“What about that one?”


As he cleans R2,
Luke stumbles on a message:
“You’re my only hope.”


Binary Sunset.
A New Hope baptized by Light.
Arise, Skywalker.


“I wish I’d known him.”
Star pilot. Warrior. Friend.
Tales of a Father.


Jawa Massacre.
Imperial Stormtroopers.
A burning homestead.


Stopped by Stormtroopers.
“Not the droids you’re looking for.”
A Jedi mind-trick.


Crossing the threshold.
The Mos Eisley Cantina.
A hero’s journey.


Baba. Evazan.
They don’t like Luke very much.
Old Ben saves the day.


With the blast-shield down
Luke is blinded by his doubts
but takes his first steps.


“The Princess? She’s here?”
“What are you talking about?”
“We’ve got to help her.”


Luke has an idea.
Han thinks it’s a bad idea.
Chewie is just mad.


“I’m Luke Skywalker.”
The hero to the rescue!
Leia is just chill.


Death Star Compactor.
A one-eyed beast tries to eat
the youthful hero.


Chased by Stormtroopers,
a hero swings a Princess
across a chasm.

Haiku Addendum:
 Princess Leia could have done
all the heroics.

Haiku Addendum:
Leia was just letting Luke
play the hero part.


Red and Blue collide.
The sacrifice of Old Ben.
“Run Luke, Run!” Ben’s voice.


A mentor is mourned.
Skywalker struggles with loss.
“Can’t believe he’s gone.”


“Got him, I got him!”
“Great kid, don’t get cocky,” the
smuggler declares.


Pleading with Solo,
Luke learns some are driven by
self-preservation.


Childhood friend: Biggs.
Skywalker and Darklighter.
X-Wing Red Squadron.


“Red Five Standing By.”
He wanted more out of life.
Well, he got his wish…


Running the gauntlet.
Protected by Biggs and Wedge.
Going full throttle.


Biggs dead. Wedge knocked out.
Luke is pursued by Vader,
his father’s killer.


“Use the Force…Let go.”
From the beyond, Old Ben speaks.
Faith in something Great.


Han Solo Returns!
“Let’s blow this thing and go home.”
Torpedoes away.


The Death Star destroyed.
Luke and his friends celebrate.
The Force is with him.


Good news! This post is Part 1 of 3 of a special three-week version of Haikuesday exploring Luke Skywalker in the Original Star Wars Trilogy. Be on the lookout next Tuesday for haiku about Luke in The Empire Strikes Back!

Check Out Other Haikuesday 2.0 Posts Below:

Imperial Atrocities

The Mighty Chewbacca in the Forest of Fear! (An Imperial Talker Review)

Absolutely delightful. That is the easiest way I can describe my feelings about author Tom Angleberger’s junior novel The Mighty Chewbacca in the Forest of Fear! From start to finish, I could not help but enjoy myself as I read about Chewbacca’s mission to the planet Ushruu. Accompanied by a young woman named Mayv, the rebel droid K-2SO (masquerading as a cargo droid), and a cadre of adorable tooka cats, Chewbacca and his companions set out on a perilous adventure to retrieve a Dark Side artifact from the depths of Ushruu’s terrifying forest.

At first believing his job is to deliver the mischievous tooka cats to one of Coruscant’s moons, Chewbacca quickly discovers that he has been set up by Alinka Aloo, the daughter of Sim Aloo, a high ranking Imperial official – an official who hopes to gift the artifact in question to the Emperor. With his friend Han Solo held captive by Alinka, our favorite Wookiee must face the deadly forest on Ushruu and find the artifact in order to save Han’s life. But he is not the only one who has been forced into this mission. Young Mayvlin Trillick must also confront the danger’s lurking on Ushruu so that, upon her return, Alinka will return to her a book containing the cultural history of the planet Oktaro, May’s home world. Quickly becoming friends, Chewbacca and Mayv find ways to work together – along with the help of K-2 and one very friendly tooka named “Goldie” – so that they will achieve success.

While I dare not spoil the book, and will keep some of the major moments for you to discover if you choose to read it, I will note that I particularly enjoyed the way the book is narrated. It is rare, in Star Wars books, to find a narrator who speaks so directly, and at times informally, to the audience. In a book with an older target audience this narrative style would probably be hard to stomach. But in The Mighty Chewbacca in the Forest of Fear! the playful narration helps create a more vivid and humorous story, a story which young Star Wars fans will undoubtedly enjoy thanks to this more casual narrative style.

Offering a number of asides and tangential statements throughout the novel, the narrator clarifies aspects of Star Wars lore, ensuring they and the reader are literally on the same page. Likewise, the narrator swings back-and-forth between telling the story and offering their own thoughts about situations and moments. For example, the entirety of Chapter 5 is an aside in which the narrator lets the reader in on a secret they just HAVE to get off their chest right then (lest we find out later and are upset). More often though, the narrator injects him/herself into the story with a line or two here and there, offering a little quip or thought about something in the moment.

This is especially the case whenever Chewbacca speaks since the narrator must provide the reader with some insight into what Chewie is saying. Given that none of us know what Chewbacca is saying anyway when we watch Star Wars, the narrator does their best to ensure we have some basic understanding of what Chewbacca is talking about. The thing is, the narrator doesn’t offer a word-for-word translation. Instead s/he primarily offers the basics, a general sense of what Chewie is getting at and even presumes a handful of times that no translation is required. 

Actually, there are quite a few times throughout the novel when the narrator just skips any translation at all, especially when Mayv, who begins to “understand” Chewie as the book progresses, is speaking with the Wookiee. That the narrator chooses not to translate every garbled statement Chewbacca makes in his native Shyriiwook is important. Just as Mayv begins to “understand” the basics of Chewbacca’s thoughts, we start doing the same (well, I did at least). While the reader cannot hear the inflection in the Wookiee’s voice, nor perfectly translate the difficult Shyriiwook language, like Mayv we are – thanks to context – capable of gleaning what Chewbacca is trying to get across. Plus, it helps that we can understand Mayv when she is talking to Chewie.

Speaking of Mayv, she is another big reason I found this novel so delightful. Resourceful, capable and funny, Mayvillin Trillick provides young readers with a role-model choosing to put herself in harm’s way as she seeks to return the Mola Oktaro – the aforementioned book containing the cultural history of her planet – to her people. Forced to make the deadly journey to Ushruu by Alinka Aloo (who is in possession of the Mola Oktaro), young Trillick quickly befriends the Mighty Chewbacca early in the journey, the two sharing in the pain of losing their worlds to the Imperial war machine. Further, Mayv’s pursuit of the Mola Oktaro is amplified by a curious cultural habit she engages in: painting symbols on her forehead which have different meanings. In one instance, for example, as Mayv and company are about to climb higher into the trees on Ushruu, Mayv paints the symbol for “gracefulness” on her forehead figuring that “it couldn’t hurt when I’m this far off the ground!” In response, the narrator offers younger readers an important lesson: “Whether this symbol – or any of them – worked, I can’t say. But Mayv believed, and maybe that was all that mattered.” Then again, that is a pretty good lesson for adults, too. 

Truthfully, I would really like it if Mayv Trillick was to pop-up again in another Star Wars story. While I won’t be holding my breath, knowing that the likelihood of her re-emergence is small, I’ll never-the-less be holding out hope because she really is a fascinating character. Besides, given her fearless determination and dislike of the Empire, Mayv would make a great Rebel were she to join the Alliance. Who knows, maybe Chewbacca will recruit her into the cause at some point. Fingers crossed.

Finally, I will acknowledge that I was slightly skeptical about K-2SO being in the book, primarily because I thought the irreverent droid from Rogue One would be out of place. I was wrong. Dead wrong. Without K-2SO this book would have been wonderful. With K-2SO, it is absolutely fantastic. Angleberger brilliantly captures the voice of K-2SO, the droids sarcasm and dry-humor bleeding off the page whenever he speaks (especially in those moments when he forgets that he is pretending to be a cargo droid). And why is K-2 present you might ask? Well, he is on a mission for the Rebellion of course! But if you want to know more about that – and if you want to discover who makes a special, surprise appearance late in the story – you’ll just have to pick up The Mighty Chewbacca in the Forest of Fear! Trust me, you won’t be sorry. In fact, I guarantee you will be delighted. 

Star Wars: Last Shot (An Imperial Talker Review)

There are few things I like and a lot of things I dislike about Star Wars: Last Shot by first time Star Wars author Daniel José Older. In fact, the bad so significantly outweigh the good that it is a little overwhelming to figure out where to begin. Perhaps the most obvious place is to just say that this story is entirely inconsequential to the Star Wars universe. While the book centers on Han and Lando coming together three years after the events of Return of the Jedi to stop a maniacal Pau’an who has plans to cause a violent, galaxy-wide droid uprising, the story never truly convinced me of its necessity, or that it was providing the Star Wars universe with any greater meaning. There are certainly a number of Star Wars elements in Last Shot. There are Star Wars places – Takodana, Utapau, Bespin, Kashyyyk – and Star Wars species – Twi’leks, Ewoks, Gungans, Ugnaughts – and a cast of familiar Star Wars characters – Han, Lando, Leia, Chewbacca, Maz Kanata – but as a whole these elements never truly coalesce into a Star Wars story with gravitas.

To save you time, I will just come right out and tell you what happens: Han and Lando survive, the bad guy (Fyzen Gor) dies, and the galaxy is once again saved by everyone’s favorite scoundrels. Thus, we are left with an altogether generic, run-of-the-mill Star Wars novel that is easily forgettable. But what is truly disappointing is that the opportunity for some memorable moments with incredibly profound consequence do exist within Last Shot. When, at the end of the novel, Lando must choose between saving himself or the galaxy at large, he chooses the latter. This IS a profound move, a “holy crap” moment in a book that really REALLY needed one. Yet, Lando’s moment of altruistic sacrifice is undercut when he is saved by a laughable plot device: the offspring? of his former droid L3-37 (who shows up in the novel in flashbacks) known as the “Elthree Assault Team.”

L3-37
L3-37
Photo Credit – Solo: A Star Wars Story

Had Lando died, the Star Wars galaxy would have been shaken to its core. Why isn’t Lando in The Force Awakens or The Last Jedi? Answer: because he was atomized in an explosion in the Mesulan Remnant. Instead, he is saved by a contrived group of vigilante droids made in the image of L3-37 and goes on to live happily ever after with the Twi’lek woman known as Kaasha, wanting to finally (sort of) settle down after years of galactic promiscuity. And who is this Kaasha you ask? I can’t tell you because she is given little development. She is ultimately in the novel because the author needed a sexual/romantic foil for Lando. Their backstory together goes to the Galactic Civil War when they found comfort in each others arms during the battle of…who knows, I can’t remember. She was smitten by the General, has sought him out, and joins him (and Han) on their adventure. While she is given glimpses of agency – she can communicate with their Ewok companion and she aids Han as he attempts to retake a ship during the novels climax – Kaasha is a Twi’lek woman otherwise beholden to the whims and feelings of a man. Shocking!

Kaasha is not the only new character appearing in the book. A human from Alderaan, and the pilot whom Han and Lando hire to assist them, Taka is a gender-neutral character and is referred to as “they” throughout the book. If there is one truly good thing about Last Shot, Taka is it. I appreciate and applaud that Older chose to include such a character in the Star Wars universe, especially since Taka’s gender-neutral status is so banal. I certainly hope more characters like Taka emerge in Star Wars as their inclusion paves the way for more gender-boundaries to be broken. And, I hope Taka shows up again in Star Wars because they are an interesting and fun. Plus, Taka goes out of their way to annoy Han with heavy metal music which is a pretty funny moment in the book.

Taka is one of the few bright spots in Last Shot, and if I were to chose another it would be the inclusion of 2-year-old Ben Solo. Now, I should note that Ben’s appearance(s) in Last Shot primarily serve Han’s story, specifically the smuggler’s inner turmoil about whether he is a good father (I’ll get back to Ben in a moment). Han’s fatherhood questions are dragged out to the very end when, finally, Han talks to Leia and she reassures him that “no one knows how to be a parent before they are one…” (pg. 340). That it takes the entire book for Han and Leia to have the “parenting is hard” conversation is pretty ridiculous (it is a convo he could have had with Leia without going on a galactic mission) but given that this is the core of Han’s character development it is hardly surprising. I don’t begrudge this particular angle on Han, though. We know from The Force Awakens that he and his son had a rocky relationship, so incorporating little bits of that relationship – in this case whether Han feels like he can do the parenting thing – is a fine angle to take. What is truly disappointing, though, is that there was a massive missed opportunity for Han to learn the importance of the parent-child relationship from Taka.

At one point in Last Shot, Han happens upon a recording of Taka’s parents. From the recording we learn two things: Taka’s parent loved them unconditionally and Taka’s parents were Alderaanian which means their parents are dead. Later, Han will mention to Taka that he watched the recording and they will tell Han that it is the last little piece of his parents they own. Han clearly sympathizes with Taka, particularly since he reflects on comforting Leia when she feels down abpout the destruction of her homeworld. But what was missed was the chance to unite Han’s parenting woes with the fact that Taka is holding onto a small remnant of their deceased parents. I cannot help but imagine a different version of Last Shot where Han comes to a fuller appreciation of his role as a parent, as a father, as he listens to someone who lost their parents. In turn, the conversation he had with Taka, and the lessons he learned/chose to reflect on, could have easily tied in with the remained of the novel (particularly the conversation with Leia at the end). Instead, Han’s parenting woes culminate in the final moments of the book when he receives cookie cutter wisdom from his wife. Ugh. Let’s just go back to Ben Solo…

Moments that Left Me Speechless

That Ben Solo makes a handful of appearances in Last Shot was certainly a positive aspect of the novel, enabling the reader to experience the sequel trilogy villain as an innocent toddler. In fact, it is two lines about Ben Solo – coming through the inner thoughts of Han – that left me completely stunned early in the book. The child looking up at his father, Older writers:

“Han had no idea how a two-year-old could have such ancient eyes. It was as if Ben had been waiting around for a millennium to show up at just this moment in history.”

Wow! Like, wow! With clarity and brevity, Daniel José Older captures the entire trajectory of the Sith Order which Darth Bane instituted, an Order based on the Rule of Two, an Order which survived for a millennium, an Order which was finally destroyed with the death of Darth Sidious at the hands. Now, as if he had been waiting for the Sith to die out, Ben Solo’s time has finally come, his conception coinciding with the death of Darth Sidious. Ben Solo’s conception and birth are the prophetic sign of a new era of Darkness, a Darkness which has been waiting to emerge for a millennia, a Darkness the boy will one day help to bring about as Kylo Ren. And the “ancient eyes”? Those are the eyes which Han  will sees when his son pushes a red lightsaber through him on Starkiller Base. They will be the very last thing Han ever sees, and perhaps in that moment he will think back to that moment he saw the “ancient eyes” in his two-year-old son.

Han and Ben
Kylo Ren (Ben Solo) looks at his father with “ancient eyes.”
Photo Credit – Star Wars Episode VII: The Force Awakens

That Han’s small reflection on Ben came early in the novel left me hoping more moments would pop up that packed a punch. But there are really no other Star Wars gems in the book on par with Han’s reflection on Ben. Instead, the opposite is true, with two other lines showing up which left me dumbfounded and at a loss. They are (and I can’t believe I am about to type this):

“Tight enough for a bulge and the insinuation of an ass…” (pg. 41).
“Like a droid orgy of some kind, but with astromechs and those old battle droids from the Clone Wars?” (pg. 335) 

My problem with references to “a bulge” and “an ass” and a “droid orgy” is pretty straight forward: they don’t add anything of value to the novel. Unless, that is, one counts shock value, which, in this case, I don’t. There is a time and place in a story to really shock the audience, to authentically catch the reader off-guard with something that comes out of left field. Lando choosing to sacrifice himself for the greater good is shocking, and if he actually died in the process would have been even more shocking. But “a bulge” and “an ass” and a “droid orgy”, these sexually-charged references caught me off-guard and shocked me in a way that left me thinking only one thing: this book is really bad.

The Bad Outweighs the Good

To be fair, I would say this book is really bad even if it didn’t reference “a bulge” and “an ass” and a “droid orgy.” Here, I will list a handful of other things that are problematic about the book (to go along with things I have already mentioned):

  • The flow of the book is choppy and confusing, the narrative jumping back and forth as it follows four storylines through flashbacks. I am not opposed to flashbacks in general, but the book jumps across timelines far too many times without giving the reader a chance to catch their breath.
  • Speaking of flashbacks, Lando’s storyline (“about 15 years ago”) does not line up with the events of Solo: A Star Wars Story. How do I know this? Because I was paying attention in the 1st Grade and learned addition and subtraction.  But there is a bit more to it: L3-37 was destroyed, and uploaded into the Millennium Falcon, in the Solo movie (which takes place around 10 BBY). However, Lando’s flashbacks in Last Shot take place in 8 BBY and L3-37 is still intact and NOT uploaded into the Falcon. Oh, and let’s not forget that at the very end of Solo, the Millennium Falcon no longer belongs to Lando…
  • The villain, Fyzen Gor, gets his own flashbacks but is completely unconvincing as a bad guy and, even worse, uninteresting. What makes his story all the more confusing is that he is from Utapau, his evil plan involves melding organic body parts with droids, and his evil conversion takes place sometime around 13 BBY, but there is not a single reference to General Grievous!!! At the very least, Gor could have been doing his initial evil organic- droid stuff and reflecting on the droid General who died on Utapau in 19 BBY.
  • The droids Gor activate to kill people literally say “Killlllll.” #facepalm
  • Speaking of those killlllllller droids, when Han and Leia’s kitchen droid is activated and moves to killlllll little Ben, a brilliant opportunity existed for the toddler to destroy the droid with his adolescent connection to the Force. This would have been awesome and a perfect connection the “ancient eyes” moment early in the book. Instead, the droid is activated and then immediately deactivated. Ugh!!!!!!
  • Oh, and what about all of the other droids galaxy-wide that were activated? Even though it was brief, a lot of droids probably killllllllled quite a few organic beings in those moments. And by “quite a few” I mean millions, and by millions I mean tens of millions.
  • Where are R2-D2 and C-3PO? This book is about killllllller droids but the two most famous droids in Star Wars never show up. Were they activated?
    Boss Nass
    “Meeeeeesa don’t lika Aro for being preachy.” – Boss Nass

    Photo Credit – Star Wars Episode I: The Phantom Menace

  • Aro, a Gungan working on Substation Grimdock, gets upset with Han for saying “meesa” and chastises him for assuming all Gungans talk like…like Gungans. I understand what Daniel José Older is TRYING to accomplish here, giving the reader an object lesson in not assuming how individuals speak based on stereotypes. But it comes off as preachy and makes Aro even more annoying than the average Gungan. And besides, there are plenty of Gungans that say “meesa” who do some pretty great things in Star Wars (check out this piece:  The Sacrifice of General Tarpals).
  • Chewbacca doesn’t need to be in the main storyline. Like, at all. He is there…and I know this sounds crazy…just because this novel is partially about Han. Now, to be fair, Older does drum up a reason for Chewie to go on the adventure: young Wookiees being kidnapped by Fyzen Gor for his experiments. However, there is no definitive resolution to this other than Chewie fighting the half droid-half Wookiee abominations. In turn because Chewbacca is “lugging a sack” (pg. 337) following his battle, Han presumes it is full of Wookiee body parts but this is never confirmed. Nor does anyone, at the end, question whether some Wookiees are still being held in some secret laboratory. Oh welllllllllllll….

Here is the deal – if you want to read Star Wars: Last Shot, go for it. It you end up liking it, more power to you. And, if you would like to convince me this book is far better than I have suggested, by all means, leave a comment below. I will gladly give your thought(s) careful consideration. But as of right now, beyond the few things in this book that I actually liked (Taka, Ben Solo, “ancient eyes”) there is just too much stacked against Last Shot for me to give it anymore significant thought. In turn, Last Shot has given rise to an unintended consequence: it has made me less likely to purchase/read Star Wars novels in the future, especially novels by new Star Wars authors. If nothing else, this will (I hope) save me from having Lando’s “bulge” and “ass” shoved in my face again. 


***Page numbers are from the first edition of Star Wars: Last Shot.***

Haikuesday: Millennium Falcon

These haiku are based
on “Millennium Falcon”
by James Luceno

Haiku Addendum:
obviously I’m kidding
so let’s begin here…


The “Falcon” is the
single most important ship
in all of Star Wars.

If you don’t agree,
well, that is perfectly fine.
Except, you are wrong.


Make: Corellian
YT-1300f
And sort of trashy.


Cockpit on the right…
…so how the hell does Solo
see ships to his left?

Haiku Addendum:
the cockpit placement seems like
a big design flaw.


A really fast ship:
it makes point five past light speed…
…whatever that means.


Easter Egg Alert!?!?!
Y’all see the “Falcon” over
Jedha in Rogue One!?!?!?!


“What a piece of junk.”
Luke insults Solo’s baby.
Han just doesn’t care.


A really fast ship:
It made the Kessel Run in
less than twelve parsecs.

Point of inquiry:
wasn’t it fourteen parsecs?
Someone go ask Rey.


Han’s best maneuver:
list lazily to the left.
Family Guy joke.


“You came in that thing,”
the Princess asks the Captain.
“Braver than I thought.”


Dorsal and Ventral.
Quad laser cannons blast TIEs.
Luke gets one; Han too.


Last ship to arrive
at the Battle of Yavin.
A Death Star Destroyed.


Inside Echo Base
Chewie and Han make repairs…
…a lot of repairs.


Tool: hydrospanner
Use: fixing broken “Falcons”
A space screw driver.


On the Avenger,
the “Falcon” hides in plain sight,
which is sort of odd.

Point of Inquiry:
how come no TIE pilots saw
the “Falcon” parked there?


On Cloud City we
learn that Calrissian used
to own the “Falcon.”


We never see Han
piloting his prized “Falcon”
in Episode VI.


A really fast ship:
Solo offers his baby
to Calrissian.


“She won’t get a scratch.”
“I got your word…not a scratch.”
She, ah, gets a scratch…


First ship to arrive
at the Battle of Endor.
A Death Star Destroyed.


Leading Endor charge.
The Millennium Falcon
blasts TIEs left and right.


The Endor gunners –
Two Rebels: Cracken and Blount
They deserve praise, too.


Lando and Nien Nunb
pilot the “Falcon” into
the Second Death Star.


Sub-light: Girodyne
Hyperdrive: An Isu-Sim
Power Core: Quadex


“The garbage will do,”
Rey says to Finn as they flee
First Order Fighters.


Stolen by Ducain,
then the Irving Boys, then Plutt,
then by Rey, then Han.


Stress on hyperdrive.
Ignition line compression.
Some moof-milker’s fault.


Now that Han is dead,
who technically owns his ship?
Leia? Chewie? Rey?

Haiku Addendum:
did Solo have a space will?
Maybe Ben gets it…


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)

Poe Dameron (December 2017)

Continuity Crisis on Kashyyyk

Having recently finished reading Chuck Wendig’s novel Life Debt, the latest addition in his Aftermath trilogy which chronicles events taking place after the Battle of Endor, I felt compelled to write a reaction to the novel. Or rather, I felt compelled to write a reaction to a particular element in the novel, namely, the way(s) in which Wendig masterfully describes the suffering of the Wookiees and their home-world of Kashyyyk. Momentarily, I will share some of these details with you, and in doing so, I hope I am able to paint an equally worthy picture of devastation and enslavement.

But before I begin, I want to note two things. First, if you have not yet read Life Debt and do not want it to be spoiled, I would encourage you to stop reading and check it out. While I do not intend to provide a great deal of spoilers, they will never-the-less be present in the post.

Secondly, and perhaps most importantly, what I am presenting about the imagery in Life Debt is also going to lead to a rather embarrassing continuity issue (hence the name of the post). While I recognize it is slightly annoying for me to say this and not tell you what that issue is right here and now, I promise that the reason I am making you wait is worthwhile. Read on and you will see what I mean.

A Vibrant World, Enslaved

To begin, it’s worth noting that Wendig goes to great lengths in Life Debt to provide an image of life on Kashyyyk before the Empire, often doing so in subtle ways to help the reader recognize that the world was once a lush and thriving place. As a reminder, we see the vibrant Mid-Rim world for ourselves in Revenge of the Sith when the Separatists invade and Master Yoda leads the Republic’s 41st Elite Corps in defense of the Wookiees. Wendig wonderfully captures the same imagery we see in the film, expanding and adding new dimensions to it. When, for example, Han Solo and his allies approach Kashyyyk, it is described as “a green, verdant planet” with “snowcapped mountains and snaking rivers leading to oceans of dark water.” Most notably though, the forests of Kashyyyk particularly  stand out to the characters in the book, “the clouds swirling above the atmosphere” having “to swirl around and through the [giant wroshyr] trees.”

Of course, the planet is not only described from a distance, but also when the characters arrive there and start working towards freeing prisoners and liberating the world. Added to the imagery, then, is a world that was once teeming with life, specifically Wookiee life Incredible Wookiee cities, such as the city of Awrathakka, are depicted as being built in and around the “skytower-like wroshyr trees – trees whose trunks are of an unimaginable circumference.” Further, the symbiotic relationship the Wookiees had with these trees is noted, a “sacred and biological” bond grounded in care. The trees provided nourishment and shelter, enabling the arboreal lifestyle of the Wookiees. In return, the creatures tended to the life of the trees, building their cities in a way that followed “the bends and turns of the trunk,” a clear sign of the respect the  Wookiees showed the magnificent lifeforms.

Sadly, Life Debt describes in even greater detail the devastation Kashyyyk and its Wookiee inhabitants have endured under Imperial rule. Under the protection of an Imperial blockade, Kashyyyk – classified G5-623 by the Empire – is “an occupied world,” “a prison planet.” The Wookiees, we learn, were corralled into labor camps and used as slaves, their impressive size and strength a valuable resource for the Imperial war machine. In fact, in the first Aftermath novel, we learn from Han Solo that the Wookiees were utilized in the construction of both Death Stars. A sad but unsurprising discovery. While Wookiees are shipped off-planet to work on military projects around the galaxy, the vast majority were kept in the camps on planet, forced to participate in the slow destruction of their native world.

One camp in particular is depicted in Life Debt, Camp Sardo. Home to 50,000 Wookiee slaves, the camp is built at the base of the wroshyr tree to which Awrathakka clings. There, like so many other camps that litter the planet, the prisoners toil under the harsh yoke of the Empire, digging into the roots of the tree for its wood and harvesting crystals from its fungal nodes. Additionally, Wookiees in this and other camps are also forced to grow food for the Empire, to fight for entertainment, are bred to keep up the labor population, and even subjected to chemical and medical experiments.

Moreover, we also discover that the Wookiees are kept in check with the use of inhibitor chips placed on the  back of their necks, devices which keep them docile. These chips give a powerful shock to any Wookiee attempting to escape a camp, a shock that could prove to be fatal. Plus, since the Wookiees are family-oriented, any disobedience may harm not just the individual, but members of their family as well. In these ways, the Empire keeps their slaves from revolting.

Still, we know that at least one Wookiee revolt took place about four years prior to events in A New Hope. This is not mentioned in the novel, but rather is an incident detailed in a short HoloNet News report. In it, the reporter explains that a Wookiee revolt was quelled by the 212th Attack Battalion, with tighter restrictions on travel to the planet being put into place by the Imperial overlords. Of course, the report is an obvious form of propaganda, making it difficult to say if the newscaster is telling the entire truth. Still, we can presume that whatever happened would have forced the Empire to use even harsher measures against their slaves (perhaps this is when the use of inhibitor chips began) and Life Debt makes it clear that eight years later, any chance of another Wookiee revolt has been ended.

A Crisis of Continuity

As I said at the outset, Wendig paints a fantastic, albeit incredibly bleak picture of the Wookiees and their beloved Kashyyyk. A world that was once vibrant – vibrancy we can actually see in Revenge of the Sith – is all but devastated. The barest glimmer of life still clinging to the branches of the splintering wroshyr trees; the native Wookies, “slowly being ground to dust” as Princess Leia declares in the novel. As I read Life Debt, I was profoundly moved by this imagery, saddened by the Empire’s flagrant destruction of Kashyyyk, disturbed by the harsh and murderous treatment the Wookiees must endure. In this way, Life Debt did what good storytelling should do, forcing one to dig deeper and mine the depths of their own being, thinking about ways that in our own world we might alleviate the suffering of others. The Wookiees and their world might be fictitious, but their plight should motivate us to want to help those who are also in need.

And yet, all of the devastation and plight in Life Debt, the detailed imagery of destruction and enslavement, doesn’t line up with what is depicted in Issue #005 of Marvel Comics Chewbacca series. In fact, to be entirely blunt, not only does the description of Kashyyyk and the Wookiees in Life Debt not line up with what we see in Chewbacca #005, the two canonical sources are just flat-out contradictory.

I won’t provide an overview of the entire plot of the Five-Part Chewbacca series, but I will note that the premise revolves around a personal mission Chewbacca undertakes sometime after the destruction of the First Death Star. In short, Chewie is heading to Kashyyyk so he can deliver an item to a young Wookiee. And, after an adventure on another world, Chewbacca does just that, flying an A-Wing Starfighter right up to his home-world, a world that is clearly NOT under Imperial blockade. Landing safely in a thriving city among healthy looking wroshyr trees, Chewbacca interacts with many Wookiees, all of whom are quite obvious NOT enslaved, no inhibitor chips stuck to their heads. Plus, to top it off, in the very final panel of Chewbacca #005, the Millennium Falcon descends to the planet with quite ease, no Imperial ships in pursuit.

MarvelChewbacca1
Chewbacca travels to Kashyyyk, landing safely on the planet.
Photo Credit – MARVEL Comics: Chewbacca #005
MarvelChewbacca2
Landing safely, Chewbacca makes his way through a Wookiee city.
Photo Credit – MARVEL Comics: Chewbacca #005

Since finishing Life Debt, I have struggled to reconcile these two disparate versions of Kashyyyk/the Wookiees which have crept into the Star Wars canon. When  I have wrestled with continuity issues in the past, I’ve attempted to smooth over the differences in some logical way while staying true to the source material. However, in this case, the powerful depictions of suffering in Life Debt differ so starkly from the warm and colorful panels in Chewbacca #005 that I am at a complete loss. I honestly cannot figure how to make the two versions work together. Then again, coming up with a fix is purely a thought experiment on my part, one that would not carry any weight unless the Lucasfilm Story Group were to adopt my idea(s). And speaking of the Story Group, the body tasked overseeing the content of the Star Wars canon, I have to ask:

How did they miss this continuity issue?

Frankly, I think Star Wars fans deserve an explanation about why two contradictory versions of Kashyyyk and the Wookiees were allowed to enter the Star Wars canon. While I understand that small errors can and will be show up, an inevitable side-effect of having numerous story-tellers adding to a fictional universe, when far more obvious errors like this one appear, then someone on the Story Group (or at Lucasfilm in general) needs to come forward and at least acknowledge the mistake. Plus, as a fan, I want reassurance that the cohesive and unified story being told will not have these problems in the future, particularly since I spend a lot of money on books, novels, games, movie tickets, etc. Otherwise, I have to be honest: if more and more major continuity issues start showing up, my enjoyment of the canon won’t just diminish, but I will seriously consider closing the door on my Star Wars fandom.


Addition: Having conversed with a number of people about this piece, including a member of the Story Group, I am working on a follow-up which will be posted here in the coming weeks. Stay tuned!