“The Bad Batch” Episode 1 Review!

SPOILERS FOR THE BAD BATCH AHEAD!

I’m gonna be honest, the Bad Batch didn’t make much of an impression on me when they debuted in The Clone Wars‘ final season just last year. The concept – an elite team of genetically-defective clones whose individual mutations give them special abilities – was admittedly quite intriguing, but the execution was only okay, never elevating the material. And despite their uniqueness being so crucial to their very existence, there wasn’t ever enough time in that season to clearly distinguish their character arcs; only their physical appearances, skills, and a handful of archetypal traits.

The Bad Batch
The Bad Batch | brickfanatics.com

But now the Bad Batch have an entire sixteen-episode series in which to extensively explore both their team dynamic and individual storylines; and the series’ premiere event (which clocks in at 71 minutes, longer than any episode of The Mandalorian, or even Marvel’s Disney+ originals) sets an appropriately dark and sophisticated tone for that journey, much like the final season of The Clone Wars. The first episode dives into the fascinating question of what happened to the Old Republic’s clone armies after they had played their part in initiating Order 66: mindlessly slaughtering the Jedi and clearing a path for Emperor Palpatine (Ian McDiarmid) to conquer the galaxy.

While most Star Wars media has looked at Order 66 from the perspective of the Jedi who survived it and went into hiding, The Bad Batch picks up with the clones themselves, who have nowhere to hide from the shame and guilt of what they’re slowly beginning to realize was the entire purpose for their existence all along. The Bad Batch themselves didn’t even kill any Jedi – the inhibitor chips planted in their brains are faulty, giving them their unique personalities and casual disregard for orders – but they won’t turn their backs on other clones: especially not the one member of their team unit, Crosshair (voiced, like all clones, by Dee Bradley Baker), whose inhibitor chip is still working strongly enough to give him internal conflict as he fights between his programming and what he knows to be right.

Star Wars loves inflicting an undue amount of pain and grief on its fans, so it’s no surprise that The Bad Batch opens by once again reliving Order 66 – but what did surprise me was that we finally get to see the death of the Jedi Depa Billaba (Archie Panjabi), and the fateful moment at which she told her young padawan, Caleb Dume (Freddie Prinze Jr.) to flee before the clones could kill him too, burdening him with years of guilt and setting him on the path to become the rogue knight Kanan Jarrus, whom we would later meet in Star Wars: Rebels. Is it slightly distracting that Dume – a young teen at this point in the timeline – has an adult man’s voice? Maybe, but Prinze Jr. is iconic and frankly irreplaceable in this role.

What Jarrus left out of his tragic backstory was that the Bad Batch were witnesses to this horrific moment, and that it was the team’s commander, Hunter, who allowed him to escape even though Crosshair was prepared to kill the young Jedi. Much of the episode’s first half revolves around this decision and its ramifications, including the wedge it drives between Hunter and Crosshair – eventually leading the sharpshooter to betray the team and join forces with Admiral Tarkin (Stephen Stanton).

The Bad Batch
Omega | starwars.com

But even with Tarkin and Dume’s cameos, the episode feels like it’s kicking off a fresh and unique story that will organically weave these and other cameos into the narrative (whereas The Mandalorian simply shoehorned them in wherever possible), while keeping the focus on our core cast of characters. The Bad Batch, thankfully, are all pretty interesting once you get to know a little bit more about them: I particularly adore Wrecker, the team’s big scary muscly sweetheart, and Tech, who’s an endearingly snarky know-it-all. Echo is the only member who still feels in need of a personality boost, but his character was originally a regular clone before joining the Batch, so that’s not entirely surprising.

The team also gains a new member in this episode – a young girl (voiced by Michelle Ang) with an adventurous streak, whose backstory is still something of a mystery. Ominously named Omega, she comes from the cloning facilities of Kamino, where she works as a medical assistant to the Kaminoan doctor Nala Se (Gwendoline Yeo), but the episode doesn’t take long to confirm that she is in fact another defective clone. Since all clones are assigned male at birth, Omega’s gender identity is pretty significant – although I’m wary of concluding from this that she’s meant to be a trans character, as some fans have been saying. Unfortunately, I feel her distinctive white-blonde hair and possible Force-sensitivity give away that she’s more likely an early prototype of a Palpatine clone.

But even if that is the case, I like her character a lot – and her wide-eyed reaction to traveling through hyperspace for the first time made the simple plot device feel magical again after nine movies. Hopefully she survives through The Bad Batch, and doesn’t transform into Snoke from the sequel trilogy or something like that, but I genuinely won’t be surprised if her character is meant to explain away some of the plot-holes in The Rise Of Skywalker.

I want to believe that the show is too sophisticated to go down that route, however, because in other regards it displays the same level of subtlety and thematic cohesion found in most of Dave Filoni’s animated projects. On that note, The Bad Batch can certainly be enjoyed by both adults and kids, but the premiere’s longer runtime combined with its darker, more contemplative tone may cause the audience to skew a little older. The action scenes are fun and lively (teamwork is always cool, especially when it involves characters cleverly building off each other’s strengths), but there’s not a lot of fighting in this particular episode.

The Bad Batch
Admiral Tarkin | nbcnews.com

Considering that I went into The Bad Batch expecting to be bored out of my mind by characters who I hadn’t really liked when they first showed up, I regard all of this as a huge win – and I’m excited to see where the series goes from here. I’m not sure if it’ll be my next obsession like Rebels was, but I will continue to review it because I like Star Wars, even when it seems purposefully designed to cause me emotional distress.

Episode Rating: 8/10

“The Clone Wars”: Season 7, Episode 12 Review!

SPOILERS FOR THE CLONE WARS FINALE AHEAD

You knew this day was coming. At some point, we would come to the end of all things, and I would inevitably make a Lord Of The Rings reference because, despite it having nothing to do with the situation at hand it’s still my go-to resource for quotes, and we would all start crying because, yes, The Clone Wars is actually over. And no, not over like it was over the last two times, but over as in it was resurrected from the dead by Disney, a final season was commissioned, and now we’ve breezed through that too. I have very mixed emotions about how I feel right now, so get ready for just a little ranting and rambling.

Clone Wars finale
cinemablend.com

If you’re here, I assume you saw the warning at the top of the post, but one can’t be too careful – we’re about to get into SPOILERS! territory, and, what with this being a finale, there’s sort of a lot of spoilers.

First of all, it’s sad. You may think that’s obvious, given that this is the final episode of a beloved series, but The Clone Wars finale is sad on a whole new level – to a point where it doesn’t even feel sad, it just feels depressing. Other Star Wars stories have seen fit to close out their final chapters with at least a small glimmer of hope (think baby Luke arriving on Tattooine while the galaxy crumbles into chaos at the end of Revenge Of The Sith, or Leia’s shocking but inspiring appearance at the end of Rogue One), but not so The Clone Wars, whose finale abandons all hope and veers into territory so foreign to the series, it makes this episode feel almost like a standalone – an eerie, grimdark, post-apocalyptic dystopian short story.

The melancholy, and occasionally ominous, score accompanying this episode only works to make it even darker, as does the bleak gray color palette. Even the setting is designed to depress: remember the good old days when we could follow our sprawling cast of heroes all around the galaxy, to new and exciting planets untouched by war? Yeah, well, most of this finale takes place on the Republic (technically now Imperial) star-cruiser still hurtling through hyperspace towards Coruscant, and Ahsoka Tano (voiced by Ashley Eckstein) spends most of the time trapped in the cruiser’s suffocating maze of passages, being hunted by her own clones and finding every escape route closed off to her.

Clone Wars finale
cbr.com

With all of the main characters busy running for their lives, it’s unsurprising that nobody has time to suddenly recognize they’re in a finale and start monologuing dramatically to each other. But this episode has shockingly little dialogue at all, and there’s not really that many last words to be said. Ahsoka’s final scene with her old friend Captain Rex (voiced, like all clones, by Dee Bradley Baker) is, in fact, completely silent, as Ahsoka mourns her fallen troopers (what makes it doubly sad is that they were literally a gift to her from Anakin) by creating a vaguely creepy public art display out of their helmets, and Rex huddles by a cheerless fire, trying to stay warm. As for Darth Maul (Sam Witwer), he steals a ship and disappears into space, off on his own quest to cause chaos and exact vengeance on those who wronged him – which at this point is pretty much everyone. At least he tears apart the star-cruiser’s hyperspace engines before he goes, which inadvertently allows Ahsoka to make her escape (and keeps her from falling into Emperor Palpatine’s hands).

The Clone Wars used to be a pretty cheerful, even funny series: but that’s not the case in the finale. There’s no humor at all, and we’re even forced to watch the happy, helpful droids introduced in last week’s episode as they get blown to bits, screaming in their shrill voices, by a merciless clone firing squad. And soon afterwards, every clone on the star cruiser, including ARC Trooper Jesse, dies when their ship hurtles out of hyperspace and smashes into the surface of a remote planet.

Clone Wars finale
cbr.com

The closest thing to a hopeful ending is the haunting final scene, which shows Darth Vader arriving on this planet and finding the strange grave-site built by Ahsoka, alongside one of her lightsabers. The following shot of Vader activating and brandishing the blue lightsaber is both a sad reminder of what he was before his fall, and a subtle nod towards the redemption he would still achieve: redemption that would make him worthy of once again carrying such a saber. But for the moment, Vader is still Vader – and he turns away from the desolate scene, leaving us to follow his diminishing silhouette reflected in the visor of a dead clone-trooper’s empty helmet. Is that what passes for hope these days?

I may sound like I’m complaining about the sadness, but…well, I am a little, actually, but I did enjoy every individual component that went into today’s episode. Everything from the animation to the action scenes was beautiful, even if it was sad – but it does make one wonder: does Star Wars have a problem with happy endings?

Now obviously, The Clone Wars was never a story that was going to end with all the main characters riding off into a double sunset: but for a series that started out as a cartoon meant for kids, this is certainly a dramatic and unexpected heel-turn. Let me try to explain: it’s fine, it’s perfectly natural in fact, for a series to mature as its audience does and get darker as times goes along – with The Clone Wars, it’s been more than a decade since the series’ first episode aired, so quite a lot of growing has been happening in the interim, and people who watched the show as kids are now adults. What I do take issue with, at least a little, is this cheerless, hopeless ending with which we’ve been left.

Clone Wars finale
comicbook.com

Star Wars as a whole started out much like The Clone Wars did, as pure, shameless escapism; that’s exactly why it became the pop culture phenomenon that it did. But in recent years, the franchise has become….much less fun. The prequels, by virtue of being the prequels, were expected to end in tragedy, misery and inescapable despair, of course – but then you’ve got the sequel trilogy, which avoided a traditional happy ending by basically reminding us that nothing, not even victory, is ever final in this universe: no matter how many times you try to balance the Force (which is what we all thought Anakin had done, back in Return Of The Jedi), it will never work. Rogue One ended with all the main cast dead, their bodies battered into specks of cosmic ash. Now The Clone Wars ends with much of the cast dead and the survivors scattered across the galaxy, and I’m left wondering: what did we accomplish, on that journey?

Well, it’s in the finale’s title: Victory And Death. But what that title conveniently leaves out is that the victory in question isn’t really one at all, because it could have happened at any time had not Emperor Palpatine personally constructed, initiated and drawn out the Clone Wars for years by cunningly manipulating both sides, and even his eventual defeat decades later will still only be a temporary one; and the death in the title isn’t just the demise of an individual, but the collapse of a society, the utter annihilation of a way of life, of an idea, of an idealistic concept upon which the Star Wars galaxy had been built. Is that all that Ahsoka Tano, Anakin Skywalker, Obi-Wan Kenobi and their friends actually achieved, after all that time?

It’s at moments like these that I begin to question whether Star Wars‘ recent trend of sad, cynical endings is actually a good one, or if the franchise is even trying anymore to be comforting. It doesn’t really feel brave anymore: in fact, much like how Pixar is increasingly being criticized for attempting to exploit audiences’ emotions, I sense that Star Wars is heading down a similar path, towards a place where all their stories are designed to leave viewers emotionally devastated. I hope that’s not the case, but after watching this episode, I can’t help but feel that way.

But yeah, happy May The 4th, everybody! Honestly, I don’t want to make it sound like I was left disappointed by the finale – I thought it was hauntingly beautiful, and, if despair was the emotion the showrunners were hoping to cultivate from their audiences, they succeeded. But at a time like this, when the real world is already so dark and the future so uncertain, I can’t say I wasn’t a little discouraged by this conclusion, even though, in the end, it won’t affect my overall rating of the episode.

Episode Rating: 8.5/10