C-3PO

M-3PO: The Rogue Protocol Droid

Introduced in Rogue Squadron, the first novel in Michael A. Stackpole’s fantastic X-Wing series, I have always held a special place in my Star Wars heart for M-3PO. A modified 3PO-series military protocol droid with the unique clamshell head of a spaceport control droid, M-3PO is more commonly known by the nickname “Emtrey.” Introduced in the book by Commander Wedge Antilles, Emtrey is the squadron quartermaster (hence why I have dubbed it “the rogue protocol droid”) and is tasked with using its “scrounging protocol” to find the necessary parts to maintain the squadron’s X-Wings. Additionally, Emtrey is responsible for creating pilot duty assignments and caring for other administrative tasks that are required to keep the famed squadron functioning at peak performance.

While Emtrey’s base programming makes it an integral part of Rogue Squadron’s operations it is a hidden program within Emtrey that makes the protocol droid an oddity. Discovered by squadron executive officer Captain Tycho Celchu while ferrying himself and Emtrey to the planet Talasea, Celchu stumbles upon a “wait-state” when he tells the droid to “shut up” three times in a row which allows one to access the entirety of Emtrey’s database and memory banks. As the Captain explains to the smuggler Mirax Terrik, “we were in combat and he [Emtrey} wouldn’t stop nattering. I ended up yelling at him to shut up and after the third time, this happened.” An obvious homage to the nattering of C-3PO and the penchant of those around the golden droid to tell him to shut up, the funny “little trick” that Celchu discovers leads Terrik to an important observation: “That’s dangerous for a droid doing military work.

Captain Celchu confirms that “there are a number of things odd about this droid…” which, in his role as executive officer working closely with the squadron quartermaster, he discovers. But this wait-state is the oddest, and while there is some obvious humor in someone deactivating a nattering protocol droid by telling it to shut up, Terrik is also correct, this function is dangerous. Even though Celchu and Terrik are able to utilize the wait-state to help Rogue Squadron, in the hands of the enemy Emtrey’s databanks would otherwise be ripe for the picking. Valuable information about the internal workings of the New Republic’s military would be readily available once Imperial operatives told the droid to “shut up” three times.

Except, this IS the point of Emtrey’s odd programming, having been intentionally installed by New Republic Intelligence. This is a fact we do not learn in Rogue Squadron but never-the-less makes perfect sense once it is revealed in a novel later in the X-Wing series. I dare not spoil the reason, though. While these books have been around for 20+ years if you’ve never read them, and this is the first time you have even heard of Emtrey, I would hate to ruin the reason for this “little trick.” And, if you have read the series, and you DO know why Emtrey shut’s down when told to shut up, you can just keep that to yourself 😉


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

U-3PO: The Other Protocol Droid

K-3PO: The Dead Protocol Droid

E-3PO: The Rude Protocol Droid

TC-14: The Federation Protocol Droid

TC-70: The Hutt’s Protocol Droid

R-3PO: The Red Protocol Droid

AP-5: The Singing Protocol Droid

4A-R2: The Pirate Protocol Droid

4-LOM: The Bounty Hunting Protocol Droid

TC-326: The Military Protocol Droid

4-A7: The Caretaker Protocol Droid

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

K-3PO: The Dead Protocol Droid

I recently wrote a short piece about U-3PO, the other protocol droid on that Tantive IV at the beginning of A New Hope. I did so because a friend had asked me about the protocol droid, wondering if I had any information about it. After writing that post, I got this crazy idea to write some more posts about protocol droids which appear off to the side or in the background of scenes throughout the Star Wars saga. And so, in this post, I want to jump into The Empire Strikes Back and offer some brief background, along with my unsolicited thoughts, on K-3PO, the dead protocol droid in the Rebel base on Hoth.

K-3PO behind Toryn Farr
K-3PO stands behind Toryn Farr.
Photo Credit – Star Wars Episode V: The Empire Strikes Back

Easily identified by its white-plating and two red dots on the right side of its chest, K-3PO is a protocol droid that works in the Echo Base command center. The first time K-3PO appears in The Empire Strikes Back is when Han Solo enters the command center to tell General Rieekan that he is planning to leave the Alliance. In that scene, K-3PO is working at a tactical screen as Solo walks by. Later, when the fleet of Imperial Star Destroyers arrive in orbit above Hoth, the protocol droid can be found once again in the command center, just before the ion cannon is fired, standing behind Toryn Farr, the woman who is speaking in this particular scene.

After the Battle of Hoth commences, with the Rebels fighting desperately to hold off the advancing Imperial Walkers, we once again return to the Rebel commander center with Han Solo. Questioned by Princess Leia about why he is still in the base, Solo comments that he heard that “the command center had been hit” by the Empire. The scene suggests as much, with the twisted wreckage of screens and computers strewn about the icy room. And there, among the wreckage, is the “lifeless” form of K-3PO, right arm missing and a massive scorch mark emblazoned on its white chest.

To be honest, I have always appreciated that K-3PO is laying among the wreckage in the command center. I admit this seems a bit strange, an odd expression of enthusiasm over K-3PO’s demise. But this is not to say I wanted the droid to die. Far from it. No, what I appreciate is that the protocol droid’s “death” adds an extra layer, even a small one, to the dire situation the Rebels find themselves in at this moment in the film. While K-3PO is not the focus of the scene, its prominent place in the foreground as Han Solo climbs over debris forces the audience to take notice, to recognize that this Rebel droid is a casualty of the Imperial attack. Every time I watch The Empire Strikes Back I cannot help but look at the dead protocol droid, a droid I have seen, albeit briefly, actively working in this very command center in those two previous scenes. I may not have known this protocol droid, not in the way I know R2-D2 or C-3PO, but a tiny amount of sympathy never-the-less takes hold when I see its broken, inactive form among the mangled screens, wires, and debris of the Rebel base.


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

U-3PO: The Other Protocol Droid

E-3PO: The Rude Protocol Droid

TC-14: The Federation Protocol Droid

TC-70: The Hutt’s Protocol Droid

R-3PO: The Red Protocol Droid

AP-5: The Singing Protocol Droid

4A-R2: The Pirate Protocol Droid

4-LOM: The Bounty Hunting Protocol Droid

U-3PO: The Other Protocol Droid

Knowing that I am fanatical in my love of Star Wars, a friend recently asked me a pretty unsurprising question about A New Hope. The question was this:

“What’s the name of the other protocol droid following R2-D2 and C-3PO at the beginning of A New Hope?”

Answer: U-3PO.

My friend then followed-up with a pretty obvious second question:

“What happened to U-3PO?”

Answer: Hell if I know.

Seriously, I have absolutely no idea. All I can tell you about the silver plated U-3PO beyond it’s name – which it officially received in the 1995 Star Wars Customizable Card Game – is that U-3PO follows the other two droids down a corridor in the Tantive IV before turning off into a different room. Then again, you could have figured that out yourself. What happened to U-3PO once it disappeared from view is a mystery. Admittedly, it is a mystery that has periodically popped into my mind. And if I had to take a guess, I would assume U-3PO was either “…sent to the spice mines of Kessel or smashed into who knows what!” Why? Well, honestly, if I have to explain it I’ll be taking the fun out of allowing you to figure it out for yourself (just re-watch the opening of A New Hope).

So the point is this: U-3PO is just the other protocol droid aboard the Tantive IV and has absolutely no bearing on the events of A New Hope. And yet, I will admit that I have always been intrigued that U-3PO is present in the film for those few brief seconds. It is certainly interesting to think about what happened to the protocol droid, and I hardly think some “canonical” answer is necessary. In this regard, the imagination is good enough for me.

But in closing, I will also say this: I find it equally interesting to imagine what role U-3PO could have played in the events of the film if it had stuck with R2-D2 and C-3PO. Who knows, maybe things would have been incredibly different if there had been three droids, and not two, wandering the barren wastelands of Tatooine.


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

K-3PO: The Dead Protocol Droid

E-3PO: The Rude Protocol Droid

TC-14: The Federation Protocol Droid

TC-70: The Hutt’s Protocol Droid

R-3PO: The Red Protocol Droid

AP-5: The Singing Protocol Droid

4A-R2: The Pirate Protocol Droid

4-LOM: The Bounty Hunting Protocol Droid

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

Luke Skywalker: The Loss of Innocence

Frantic to return to his homestead to warn his family about an impending Imperial raid, Luke arrives too late. Slowing down in his landspeeder, the young man leaps out and calls to his uncle Owen and aunt Beru as black smoke billows from his burning home. Scanning the destruction, Luke locks eyes on the smoldering carcasses of his guardians. Not only was he too late, but the extermination was absolute. Luke may have expected, as he sped closer to home and could see the smoke on the distant horizon, that he would find the limp bodies of Owen and Beru. But he surely did not expect such an abhorrent scene – the grotesque, distorted skeletons of his loving uncle and aunt. One cannot help but wonder -and certainly the thought must go through Luke’s mind – if his uncle and aunt suffered in their final moments of life, tortured by the pain of being burned alive.

Grotesque
The grotesque corpses of Owen and Beru.

Photo Credit – Star Wars Episode IV: A New Hope

This short but disturbing moment in A New Hope is one that never fails to move and pain me. Admittedly, the event is a narrative necessity, albeit a disturbing one, a way of jettisoning Luke from the confines of his childhood connections into a larger world. Seeking adventure and desiring to leave home, even petitioning his defiant Uncle at dinner the night before to allow him to leave, Luke’s adolescent dreams can not be fulfilled. There is no longer any resistance standing in his way and he can join Obi-Wan Kenobi on his valiant quest to defeat the Empire.

And yet, as the scene concludes with Luke standing there in the quiet desolation of his childhood as the smoke billows and the carcasses continue to smolder, I have always wondered: what did Luke do next?

Skywalker Alone
What did Luke do after this moment?

Photo Credit – Star Wars Episode IV: A New Hope

This is not a question that demands a definitive answer. In fact, I would be furious if the Lucasfilm Story Group was to provide an “official” or “canonical” account regarding Luke’s actions (or his thoughts/feelings) when the scene concludes. On one level, this is because this scene in A New Hope, which we can link with Luke’s sad return to Obi-Wan and his admission that he can now join the Jedi Master’s journey, work with seamless fluidity even though they are separated. We do not need to be told what Luke did in the interval because the narrative intention in A New Hope is to move Luke from one stage of life to the next. The innocence of his childhood is literally destroyed and he will now venture forth into the responsibilities of adulthood.

On another level, any “official” explanation would usurp the imaginative faculties of fans, taking away the opportunity for one to insert their own thoughts and feelings into the heart-wrenching moments before, during, and after Luke arrives. Not knowing what Luke does, or the emotional turmoil he experiences, is in many respects what makes the death of Owen and Beru so powerful. Without explanation, other than the pained look on young Skywalker’s face as he views the carnage of his familiar surroundings, we are left to fill in the gaps, all of which enables our own, individualized connections with Luke, and the film, to flourish.

And so, the question – what did Luke do next? – percolates in my mind precisely because my imaginative faculties, aided by the emotion which the scene evokes inside of me, consistently arrives at a number of possible explanations. Just as I can believe Luke simply turned around, walked back to his speeder and left his home, I can just as easily imagine that Luke feel to the ground and broke down in tears. Or maybe Luke dropped to his knees and screamed, bellowing out the agony and guilt of not being there to protect his loving family.

Perhaps Luke sprung into stoic action, choosing to carefully bury the bodies as he internally contemplated the loss of his innocent and simple life. Digging graves next to those of his great uncle Cliegg and great aunt Shmi, Luke placed the wrapped bodies of uncle Owen and aunt Beru in graves he methodically dug. The burial complete, Luke returned to his land speeder and drove off into the Tatooine desert, taking nothing but the memories of his family, his home, and his youth with him.

Haikuesday: Droids

I had been wanting to do a monthly series on this site for some time but had been struggling to decide what to do. Then, one day, it hit me: why not write and post a collection on Star Wars Haiku on the first Tuesday of every month and call it Haikuesday. Simple to pull off but also stunningly brilliant (*pats self on back*). Yet, that was not the only idea I had. “What if,” I thought to myself, “I allowed my followers on Twitter to vote for the Haiku topic.” And that is precisely what I did, presenting four options in a poll which resulted in this inaugural Haikuesday post which is all about DROIDS! 

I hope you enjoy my Star Wars inspired syllabic creations and be sure to follow me on Twitter to vote for the next Haikuesday topic!


Scene: Horizon Base;
Chopper ignores the mission.
Instead, goes shopping.


Interrogator
IT-O deals in torture
Confessions abound


I have to be frank:
That Vader built 3PO
is still really odd.


“Inventory Droid!”
AP-5 gets no respect
Defects to Rebels


Construction droids on
planet Lothal, Leonis
calls them primitive


Techno Union owned
Baktoid built battle droids for
CIS armies


I have to be frank:
I think 3PO’s red arm
is really stupid.


Scene: On Tatooine
Jawa scavengers sell droids.
Stolen? “Utini!”


Guardian Corps built;
at Third Battle of Vontor
Xim’s droids defeated


You know, in a way,
the Force also woke R2 
from low power nap.


K-2 reprogrammed,
He’ll be there for Jyn because
Cassian says so


I can’t help but feel
the Clone War should have been called
the Great Droid War…thoughts?


Jek-14 no more
He is the Maker of Zoh,

repairer of droids


Scene: On Mustafar;
Anakin and Ahsoka
battle nanny droids


Programmed by CorSec,
Whistler joins Corran Horn in
Rogue Squadron battles


Fatal Alliance,
Republic and Sith soldiers
battle Fastbreeders


“Attacked by a droid…
…An old Clone Wars battle droid.”
Bones beat up Solo


Battle of Naboo
Primitive Gungans engage
Wall Street’s droid army


Writing droid haiku
Imperial Talker starts
to feel quite hungry


Upsetting a droid
No one worries about that…
3PO is wrong


“Primary function:
burn holes through meatbags, Master.
…how I hate that term.”


Serpentine Sentries
Roaming ruins on Mataou.
Aphra should beware.


Poor tortured Gonk Droid!
What did you do to upset
His Largeness, Jabba?


Professor Huyang
guides Jedi younglings as they
construct lightsabers


If not much trouble
Could someone ask Pablo if
Droids show is canon?


Scene: On Iego;
Honorable Jaybo Hood
Builds droid servant force


I have to be frank:
I think Triple-Zero and
BT-1 are lame.


ASN transports
lethal kouhun to their prey:
Naboo’s Senator


Rebel base found by
An Imperial Probe Droid!
Time to flee from Hoth


Clone Wars Veteran
Terrified of Jedi Knights
Roger Freemaker


“Those droids were stolen,”
Young Luke tells Uncle Owen.
“Yeah, no shit nephew.”


Scene: Planet Scarif;
Jyn and Cassian in vault
K-2 dies for them


Downfall of a droid
R2 lost at Bothawui
Anakin freaks out


Loathed by Yuuzhan Vong
Droids targeted and destroyed
by the invaders


CZ-1G5
is a very bad droid in
High Noon on Jakku


“Blah Blah Blah Complain
Blah Blah Blah Complain Complain!”
“3PO! SHUT UP!”


I have to be frank:
I think that BB-8 is
so adorable!


Imperial droid
C2-B5 in Rogue One.
Wait! Did it appear???


Droid General Grevious
Killed by a shot to the chest;
How uncivilized. 


The First Droids

When this month’s Star Wars ComLINKS topic – Favorite Droid – was announced over at Anakin and His Angel, my mind initially went blank…for days. As I thought about the topic, about what droid in Star Wars is my favorite, I just couldn’t come up with an answer. I really wanted to contribute to the topic, to give my two cents on which droid I love the most, but the harder I thought about it, the more difficult it actually became to settle on one.

This difficulty really boiled down to a rather basic dilemma. Basically, I have never given the topic of “favorite droid” much thought before writing this piece. While droids are an indelible part of the Star Wars universe, my personal enjoyment of droids has rarely gone deeper than surface level appreciation. This isn’t to suggest I never engage in any thoughtful contemplation of droids and their role(s) in the canon of Star Wars stories. Nor am I suggesting that I don’t have any especially fond appreciation for individual droids. As a matter of fact, I really love Chopper’s attitude, the absurdity of WAC-47, the adorableness of BB-8, would be thrilled to have my own battalion of battle droids, and am particularly fond of HK-47 and his penchant to”burn holes through meatbags…”  Rather, all I am saying is that I don’t get as excited about droids as other fans of the franchise (check out The Astromech Journal to see what I mean), and because that’s the case, no one droid really stands out above any other.

Nevertheless, there is a caveat: R2-D2 and C-3PO occupy their own, special status in my personal “droidom.” While I could have chosen them as my favorite droids, for me these two transcend the confines of mere favoritism. Artoo and Threepio will always and forever occupy the pinnacle of my fascination with Star Wars droids, a pinnacle that no other droid can ever hope to reach. And the reason for this is obvious; Artoo and Threepio were the first droids we ever met in the franchise, setting the bar high for all other droids  (especially those with independent personalities like BB-8 and Chopper). But there is more to this fascination and love. Brought to life in A New Hope by Anthony Daniels (C-3PO) and the late Kenny Baker (R2-D2), these two droid companions are also the very first characters we meet in all of Star Wars, a fact that often feels overshadowed by the endless cacophony of Star Wars stories. For the greater part of A New Hope‘s opening act, Artoo and Threepio drive the film forward, they are the main characters and are, at times, the only “beings” present on screen. Taking us on a journey that begins in space and descends to a desolate, wind and sand-swept planet, the two droids – who add a bit of humor through their bickering –  will only pass off the “main character torch” when they arrive at a lone homestead where a young man named Luke lives with his Aunt and Uncle. And, well, from there you know the rest.

r2-and-3po-desert
R2-D2 and C-3PO stranded on a desolate world.
Photo Credit – Star Wars Episode IV: A New Hope

The first droids we ever meet in Star Wars, the first characters we ever meet in Star Wars. And yet, what truly stands out about Artoo and Threepio, what cemented these two in my heart and mind as a young Star Wars fan, is that until we finally meet Luke Skywalker these two droids are the hope represented in the film’s title. Again, with the cacophony of Star Wars stories in circulation, this is easy to overlook  but necessary to remember. For the better part of A New Hope‘s first act, R2-D2 and C-3PO are the “only hope” for a galaxy terrorized by a galactic empire. While it is obvious that the young Skywalker is the hero of the film, the “new hope” for the galaxy, so too are all those who willingly or unwillingly, consciously or unconsciously, work for the common goal of destroying the Empire’s Death Star. In this way, A New Hope is not a film solely about one young man who will become a hero, but is a collection of individuals – humans, aliens, and yes, even droids – who through their actions radiate a message of hope not only to the galaxy, but more importantly, to you and I. 


This post is part of the Star Wars ComLINKS series. Check out more Star Wars ComLINKS over at Anakin and His Angel.

swcomlinksbanner1