BoLS logo Tabletop, RPGs & Pop Culture
Advertisement

‘Star Wars: The Mandalorian’: Five Reasons “Guns For Hire” Was the Most Divisive Episode Yet

5 Minute Read
Apr 7 2023
Hot story icon

The Mandalorian “Chapter 22: Guns For Hire” has proven a polarizing force for Star Wars fans.

Season three of The Mandalorian has had its ups and downs. It’s been a real mixed bag of a season and has not lived up to past ones. Things seemed to be on an upswing after Chapter 21 kind of got the show back on track. However “Chapter 22: Guns For Hire” was an episode that was all over the place. Because of that, it’s proven to be very divisive.

Warning: Spoilers

Advertisement

5. The Setting and Main Story Proved Divisive

Most of the plot of the episode takes place on a brand new Star Wars planet, Plazir-15. Din Djarin and Bo-Katan Kryze are trying to meet up with some other Mandalorians. However, their plans get hijacked into a most unrelated adventure dealing with rogue droids on this new planet. Now in the abstract, I really like this episode and the idea. A cool new unconnected adventure on a brand new world is what I love seeing in Star Wars. It’s different and new and kind of fun.

However, I can also understand why a lot of people didn’t like it. It’s not a great fit for a short season of The Mandalorian. This plot doesn’t tie into anything. It really feels like a totally different show.

4. The Droid Problem 

The episode also highlighted a problem Star Wars has always had with droids. Are they people, or are they machines? We find out in the episode that droids have bars and go there in their downtime to chill. They also feel good about serving people, as people gave them life. All of this makes them seem like regular people with feelings and emotions. However, at the same time, the plot revolves around droids doing all the work and getting reprogrammed to do both good and evil. Programming, not free will, controls the droids. So why are they programmed to feel, to have time off, to go to bars? It’s both interesting and nonsensical.

3.  The Prequel Reminders Were Weird

From B-1s and Super Battle Droids to Count Dooku references the episode was full of callbacks to the Prequels. For some people who really don’t like those movies, it proved a point of contention.  However, this was an aspect of the episode that I really loved. Love or hate them, the Prequels happened. I always like it when later shows or books reference them and the history of the Star Wars universe. It makes things richer. Hearing people talk about the history of their world, from the Republic to the Clone Wars, to the Empire and now the New Republic makes the whole setting feel richer. It also reminds us that not a ton of time has passed since the Prequels. That the main villain was an old Separatist was also great.

2. The Cameos Made This the Most Divisive Episode Yet

The most talked about aspect of this episode was the cameos. Between Lizzo, Jack Black, Christopher Lloyd, and some voicework by Tom Holland’s brother Harry, it was full of star (wars) power. For a lot of people, this was very divisive and proved a sticking point. Star Wars has traditionally not gone in for a ton of cameos. Having big names, like Jack Black, show up can break immersion for some people. And I admit this was a bit of the case for me.

Advertisement

However I also really loved all these characters. Lloyd as an unreformed Separatist was a great twist and nod to Star Wars history. Black as a reformed Imperial genuinely trying to do good and make amends was a hopeful addition to the lore. He shows that the New Republic does have successes. And Lizzo and Jack Black playing a genuinely kind and happy couple just having fun most of the time was a breath of fresh air. Seeing something different and crazy, like Lizzo’s wings, was cool. Still, the fact that I’m calling them all by their real names and not the characters kind of proves that there is an issue.

1. The Ending Sucked

After a fun but mostly unconnected episode, the last few minutes bring us back to the main plot. In a single scene, Bo-Katan meets up with the rest of the Mandalorians, fights Axe Woves for command (and wins), and gets the Darksaber. That’s a lot and it all feels very rushed. While the fight with Woves isn’t bad, it feels rushed. The show needs to get back on track and even the characters in this episode don’t have time to wait around it seems.

The Darksaber handoff is really the worst part. Din has never wanted it and offered it to Bo back at the end of Season 2. However, she couldn’t take it as it can only be won, not given. Now however we find out that the Darksaber follows the same ownership rules as the Elder Wand. Back in the second episode of the season, Din was beaten by a crab droid thingy. Bo-Katan then beat the crab droid thingy. So because she beat the thing that beat Din she technically owns the Darksaber. Sure.

But why did the show even give it to Din in the first place? He’s had it for 9 Episodes (including three in Book of Boba Fett) and never did anything with it.

Advertisement

Outside of one or two fight scenes, it served little purpose and never drove the plot or narrative.  Now he’s just given it up. It seems a waste.

Let us know what you thought of the episode, down in the comments! 

 

Avatar
Author: Abe Apfel
Advertisement
  • Star Wars: If You're Over 30 This Was Probably the First Star Wars Ship You Saw - The Blockade Runner Breakdown