Once again The Clone Wars conjures up a thrilling mix of action and moral dilemmas. “The Zillo Beast Striks Back” is more than a continuation of the previous installment of the series. Rather, it presents a very clear and multifaceted issue: Animal research and experimentation. And to the credit of the episode, it presents these sides with equal plausibility — even if it, ultimately, endorses one side over the other.

After Palpatine makes the fantastically questionable decision to bring the Zillo beast to Coruscant for testing — he wants to use its “indestructible” scales to help provide armor for the Clone Army — we’re immediately introduced to the primary conflict of the episode: Should the beast be killed in the name of science and in the name potentially saving millions over the course of war? It is, after all, just one violent creature.

But it is also the last of its kind and seemingly intelligent. Isn’t killing the beast akin to murder?

The debate itself is crystallized in a scene featuring Palpatine, Padme and Anakin. It’s a scene that doesn’t overwhelm the episode, but manages to accurately and eloquently present both sides of the issue. Anakin’s hesitation to fully endorse either argument is plausible — both within the confines of the debate and his character. He says he’s on Padme’s side, but concedes that “the Chancellor makes some excellent points.”

Of course, Palpatine renders the debate moot when he summarily orders the beast killed. And, of course, the beast doesn’t take too kindly to being executed; it quite quickly (and effortlessly) breaks free of its constraints and rampages through the streets of Coruscant — straight toward Palpatine.

The rampage itself is the centerpiece to the episode’s action. Once again, The Clone Wars doesn’t soft pedal the devastating effects of war or conflict. People die during the rampage as buildings and bridges and people are all crushed under the weight and power of the beast.

Most remarkable is the portrayal of the beast’s final moments. After a great deal of death and destruction, Palpatine gives an order to have the beast poisoned. In some respects, he’s not wrong for doing so — the rest of the planet needs to be safeguarded from the beast (even if it’s Palpatine who is ultimately responsible by bringing the beast to Coruscant in the first place). But it’s a melancholy scene. As the beast tumbles to its death, with music rising to a doleful crest, it’s clear that even if Palpatine was justified in his order, something unique and special has been lost.

Overall Grade: A-

“The Zillo Beast Strikes Back” features plenty of action and a story with enough depth to be meaningful and worth telling.

“Zillo Beast” is a vehicle for exploring the consequences of warfare — for examining the moral dilemmas that present themselves during any act of aggression. Exceptional production values allow this episode to showcase its central themes in ways that are as meaningful as they are entertaining. The result is yet another stellar installment of The Clone Wars.

The episode opens with a massive droid assault on the planet of Malastare. Anakin and Mace Windu are present not only to repel the invasion, but also to secure a treaty which will provide essential raw materials for the Republic’s war effort. To that end, Chancellor Palpatine has authorized the use of an “electro-proton bomb” to be used against the droid armies. Part nuclear bomb, part electromagnetic pulse, this is a weapon of great power. And it presents the episode’s first moral conflict: How far is too far to secure victory?

Surely this new weapon can help the Republic defeat the Separatist Army and gain a key tactical advantage in the war. But do these outcomes justify the use of such a devastating weapon? Initially, the weapon seems to work flawlessly. The EMP knocks down the entire droid army, leaving the Republic troopers and Dug warriors unharmed. But an unforeseen side effect — the creation of a massive sink hole — threatens not only the treaty negotiations, but also the delicate balance of the planet.

What the Republic has done is to unleash the dreaded Zillo Beast — a godzilla-like creature that is as deadly and as powerful as it is massive in size.

This leads to the episode’s next dilemma: What to do with the beast? Mace Windu wants no part of killing what could be a last-of-its-kind specimen. But the Dugs want it dead, and they threaten to withhold signing the treaty unless the Republic helps them kill it. To that end, Anakin comes up with a plan to try and stun the creature — fooling the Dugs into thinking its dead, so that they will sign the treaty, and allowing Mace Windu to clear his conscience.

Of course, Anakin’s plan works and the creature is subdued.

These themes work very well because they aren’t presented with a particularly heavy hand. The episode spends enough time on cool action sequences (the opening battle is very well-choreographed and executed) as well as fun moments (pay attention for a nod to the old TV series M*A*S*H by way of troopers called Trapper and Hawkeye). The “fun” elements of the episode provide a necessary balance, keeping the story as entertaining as it is meaningful.

Overall Grade: A-

“The Zillo Beast” is a strong installment of The Clone Wars. It presents a meaningful, balanced story that is both fun to watch and deeply provocative.

“Bounty Hunters” is a solid installment of The Clone Wars series. It features a fun story, plenty of action, and a truly fantastic musical score. In almost every respect, the production is solid. It’s also an homage to Akira Kurosawa’s Seven Samurai — which ought to draw the interest of many viewers. As a standalone episode in the Star Wars universe it’s a classic, even if a few awkward moments keep it from being truly exceptional.

I must confess that, despite knowing about the plot, I’ve never seen Seven Samurai, so I can’t say how faithful or competent an homage the episode itself is. But a successful homage doesn’t rely on viewers having explicit knowledge of the source material. Instead, it uses the original work to help tell a compelling tale. And that’s what happens here. Anakin, Obi-Wan and Ahsoka crash land on Felucia and find themselves helping four bounty hunters defend a farming village from marauding pirates led by none other than Hondo (from the Season One Clone Wars episode “Dooku Captured” and its followup “The Gungan General”).

The opening paces of the episode are remarkable for a couple of elements. First, there’s the action sequence in which Anakin’s ship is shot down by Vulture droids. One wonders why a recon mission wouldn’t be made with a more agile ship. But no matter, the sequence is more about the dialogue and interactions between the three Jedi than it is about how they got into their predicament. The dialogue here is filled with playful banter that is absolutely hilarious and revealing. There is a clear camaraderie between these characters, but even so, small rivalries and bickering are also present — the seeds of future strife.

Once the Jedi arrive in the village, we’re introduced to the bounty hunters, led by a female named Sugi. She explains that her band, which includes the wonderfully realized Samurai-like Embo, are there to protect the village. The villagers themselves are small, almost turtle-like creatures who have no history with combat or battle. They beg the Jedi to help but Obi-Wan refuses, citing the need to inform the Republic of a destroyed medical station and the desire to keep the Separatists from learning about the village. It’s sound logic, but it’s also a bit extreme.

Worse still for the episode, Obi-Wan ends up fighting the pirates without actually having explained why he’s changed his mind about fighting. There is the intermediary step of Anakin teaching the villagers how to be fighters — with Obi-Wan’s approval — based on the idea that the Jedi cannot always be there to defend the village. But when the inevitable attack comes, Obi-Wan is on the front line, fighting, with nary a word about why he and his fellow Jedi are suddenly taking such an active role in the battle. This isn’t a critical problem (it is easy to understand why Obi-Wan would defend a nearly helpless village from ruthless pirates), but it is an oversight.

The pirates are led by the colorful Hondo, a character from the first season (who actually managed to capture Obi-Wan and Anakin). Once again he’s an amusing, entertaining villain. His addition to the episode is a decided benefit, not only because of how much fun the character is, but also because of his history with the Jedi.

His assault on the village is swift and deadly, for both sides. It’s remarkable, once again, how realistic the Clone Wars series is in depicting the reality of battle. True, our heroes escape unscathed, but villagers, pirates and bounty hunters all perish. And even the noble, skillful Embo is injured by a cannon blast from a tank.

The tank sequence, though, is the second misstep of the episode. Anakin confronts Hondo in a thrilling battle, showcasing Hondo’s skill with an electro-staff. It sets up what should be a final confrontation in the battle. As expected, Anakin gets the upper hand, with Hondo dangling off of a cliff. Hondo offers a truce in exchange for his life. Anakin agrees, then Hondo pushes Anakin in front of a cannon blast, sending Anakin down to the village below. Hondo is left alone atop a cliff with a cannon trained on the village — and then he leaves, citing the fact that the venture is no longer profitable.

The sequence makes sense — Hondo cannot possible hope to fend off the impending assault of three Jedi, but is abrupt departure is too abrupt, especially with the ominous music and framing shot of Hondo standing diabolically above a village with no immediate defense against the tank. Surely a resourceful pirate could have parlayed the situation into something profitable?

Overall Grade: B

No matter. Like Obi-Wan’s decision, it’s a relatively minor point, which doesn’t significantly diminish the episode’s quality. And when you consider a story about how it is better to teach people how to do something, instead of doing it for them, there’s plenty of value to this installment. Factor in amazing visuals and thoroughly engaging score, and there’s little doubt that “Bounty Hunters” is a classic.

“Cat and Mouse” is a thoroughly entertaining, even visceral installment of the Clone Wars series. There really isn’t a whole lot of thematic work here and while the characters are certainly vividly portrayed, there’s not a lot of development in this area, either. Mostly, this is an action-adventure vehicle and, in that sense, it’s a success, — even if it’s rather straightforward and obvious, it’s still quite enjoyable to watch. Chalk this one up as pure entertainment, even if it doesn’t offer much by way depth.

During an attempt to break a blockade of the planet Christophsis, Anakin and the Republic are stymied by a legendary tactician by the name of Admiral Trench. You have to give the episode credit for making Trench an intelligent and confident leader. But, really, he isn’t much more than your typical mustache-twirling villain. He certainly fits the mold well, and is a lot of fun to watch on screen, but at some point, it’d be nice to see an antagonist who has a bit more depth than being simply a “cool” evil guy (or gal).

At any rate, Anakin’s attack is repelled and Obi-Wan has strategy to, at the very least, deliver much needed relief supplies to the planet below (inexplicably manned by Senator Organa — why? doesn’t really matter). Kenobi’s plan? Use a prototype stealth ship to run the blockade. However, with Anakin in command, it’s easy to see that the mission will not go according to plan.

Put simply: Anakin turns a relief mission into a deadly game of “cart and mouse” after he decides to engage Trench in a head-to-head confrontation.

It has to be said that Anakin’s character is thoroughly fascinating here. His efforts are a wonderful blend of recklessness, arrogance, brilliance and daring. After watching him in action in this episode, it’s easy to see why his impatience and aggressiveness could lead him, eventually, down the path of darkness. And what’s important, is that the audience is meant to sympathize with and support Anakin’s actions. He saves the day (after a daring maneuver or two). But regardless of the results — which neither Obi-Wan, Organa or Admiral Yularen can deny — Anakin’s methods are very much in question.

This is, in fact, the episode’s most important element. Anakin uses the ends to justify the means. In this case, his methods aren’t exactly objectionable. And yet, he still disobeys orders and acts recklessly. He’s likable and charismatic in this episode. But his strident independence is, obviously, one of the factors in his eventual downfall.

Aside from that, what this episode does best is its action. Anakin’s daring methods — questionable though they may be — are absolutely entertaining to watch. He pilots his stealth ship with ease. He outwits the enemy. And he saves the day.

Completely.

The episode works primarily because Anakin is such a compelling character and because the events of the episode are well-paced and executed. Trench, simplistic though he may be, is plenty fun to watch. And the whole concept of the stealth ship evokes a classic “submarine” aesthetic. There are even minor touches, like a rookie clone on his first mission, to flesh out the rest of the story.

Overall Grade: B

All told, “Cat and Mouse” is a classic episode. Anakin’s actions are bold and reckless. But he still saves the day. The episode does a great job of executing its story. The only real criticisms are a relative lack of depth to the characters and the story. Still, it’s plenty fun to watch and fans of the Clone Wars series will find much to like about this installment.

“Senate Murders” continues a remarkable and praiseworthy trend of the Clone Wars series to inject some very topical and mature ideas into what is, otherwise, a wonderfully entertaining installment. In fact, to dismiss this episode simply because it’s presented as a cartoon would involve ignoring major plot, character and thematic elements. What makes the episode successful is the fact that its story matters as much to the audience as it does to the characters.

Not that the death of a Rodian Senator, Onocanda Farr whom we’ve just met, matters a whole lot to the audience. But the story is masterfully framed around a debate over troop escalation in an increasingly costly and devastating war. And, in fact, Senator Farr himself presents a fascinating characterization — an aging man, dealing with the mistakes of his life and professional career, looking a measure of redemption or salvation. He represents, perhaps, some of our worst fears: namely that we will run out time to mitigate the missteps of our past.

This then is the heart of the episode. The ongoing debate in the Senate, over a bill introduced by Farr to reduce military spending, clearly has real-world implications. And whatever side of the debate a viewer might be on, the fact is, the episode treats the issue with a significant degree of respect and balance. Our heroes are, obviously, advocating for troop reduction, but Palpatine’s arguments in the episode’s closing scene aren’t without a bit of merit. Of course, because we know something about the characters that are making these arguments, we can infer which side of the debate advocated by the episode. Still, within the confines of a half-hour narrative, there’s plenty of substance here.

As for Farr, we’re told that, early on, he “brought war” to his home planet. So, for him, this bill is a chance to change course and bring the war to a peaceful conclusion. Unfortunately for him, though, he is the target of murder and before his bill even comes to a vote, he’s been poisoned. Aside from the unfortunately silly name (“Anaconda,” really?), this is a very deep and mature construct for a character. It’s just another reason why the Clone Wars series continues to impress.

And speaking of interesting characters, the episode is rife with them. There is, of course, the inclusion of Bail Organa (featuring some very realistic animations) and Mon Mothma. Farr’s understudy, Lolo Purs, is understated but features prominently. There’s vampire-esque Mee Deechi who serves the role of villainous suspect exceedingly well. Kaminoan Senator Halle Burtoni works well as a condescendingly intrusive persona. And then there’s Lt. Tan Divo, the chief investigator, who seems to be channeling John Lovitz in a wonderfully whimsical performance — lending some necessary humor to an otherwise dark episode.

In fact, the story itself borrows heavily from film-noir, providing some very engaging and atmospheric scenes such as Padme and Bail investigating “the docks.” This is, after all, a murder-mystery story. And as such, we’re treated to a number of twists and turns which play out very well against the thematic and character backdrop established in the opening scenes. The culprit turns out to be a bit obvious, given the episode’s opening tagline of “Searching for the truth is easy. Accepting the truth is hard.” But that hardly diminishes the entertainment value of the story. And that certainly doesn’t diminish the more thoughtful and insightful character and thematic elements.

Overall Grade: A

On the whole, “Senate Murders” is an exceptional Clone Wars episode. Once again, the series manages to convey some important ideas within the context of an entertaining and engaging story.

“Duchess of Mandalore” is a sweeping, cinematic tale. And it just might be the most mature, allegorical story we’ve seen thus far in the series. What’s remarkable is the fact that this episode is successful despite the fact that a promised battle never materializes. Put simply, the story doesn’t need a battle to be compelling, suspenseful and masterfully crafted.

Continuing the story from the past two episodes, Duchess Satine of Mandalore speaks to the Republic Senate in an attempt to prove her planet’s neutrality. But her efforts are undermined by a faked message from her homeworld which makes it appear as though Mandalore is on the verge of civil war. Palpatine quickly suggests that the only way to “protect” Mandalore is to occupy it. This is, in fact, what Count Dooku and the Death Watch armies want — an occupation force which will galvanize the Mandalore people in support of Death Watch.

The parallels to history are indeed striking. Clearly there are shades of the American war in Iraq, which many of its citizens consider to be an occupation. But Palpatine’s arguments in favor of the occupation, “we will save your people” over Satine’s objections and protestations in favor of self-determination move the story beyond simply a reference to one historical moment (even if the story does support such connections).

Instead, this becomes a cautionary tale about the abuse of power. The Republic has the power to occupy Mandalore, superceding Mandalorian autonomy. Mandalore cannot resist. Satine is furious that such a travesty could possibly occur. And the rest of the episode chronicles her efforts to somehow stop the impending occupation of her planet.

What makes the story so compelling is in how skillfully it makes use of characters. Satine’s friendship with Obi-Wan is utilized to great effect. Their previous conversations and debates over pacifism and war find their fullest expression in Obi-Wan’s insistence that Satine rely on her friends — himself and, by proxy, the Republic. Satine utterly rejects the Republic and, therefore, Obi-Wan. The fact that they eventually will be able to overcome their philosophical and political differences and rely on their friendship makes the story that much more complex and nuanced.

Another well-placed character is Padme. Considering parallels between Obi-Wan and Satine, and Anakin and Padme, it’s fascinating watching Satine and Padme working together, toward the same goals. Knowing that Obi-Wan sacrificed his love for Satine, while Anakin will sacrifice everything else for Padme, makes the juxtaposition of Satine and Padme all the more intriguing.

The most immediate conflict in the episode is an assassination attempt against Satine. It’s through this crisis that she finally reaches out to her friend Obi-Wan. And actually, this may be the episode’s weakest element. The assassin proves to be a spectacular failure at accomplishing his mission. Each attempt to kill Satine fails. Even though he tries several times. It’s not a major issue in the grand scheme of the episode, but it does stretch plausibility somewhat.

Also important to this episode are its aesthetics. The cinematography is, truly, cinematic. Whether it’s the sweeping shots of the Senate and the Separatist fleet, the wonderfully designed Mandalore, or the gritty realism of the streets of Coruscant, the visuals are fantastic. And, just as important, the music just as grand and epic.

Overall Grade: A

“Duchess of Mandalore” is a fully-realized, mature episode that doesn’t need a lot of flash or action to create a story that is as entertaining as it is meaningful. Whether it’s the depth of the story and characters, or the shimmering production values, this is one of the best installments of the Clone Wars yet.

“Voyage of Temptation” is another one of those solid installments of The Clone Wars. It doesn’t feature the original conceptualization, riveting pace or pulse-pounding action of some episodes. But it’s a fairly mature and compelling tale, particularly from a character perspective. The concept of “temptation” is prevalent and deftly utilized. And the focus on Obi-Wan’s character, his own history and choices, makes the whole production quite enjoyable. The result is yet another classic installment.

Obi-Wan and Anakin are escorting Duchess Satine of Mandalore, as well as a few Senators, to Coruscant. Not surprisingly, their voyage is fraught with danger — from assassin droids to hidden traitors. Along the way, Obi-Wan and Satine debate (again) about the differences between pacifism and “peacekeeping.” It’s also revealed (confirmed, actually) that Obi-Wan and Satine have a history together — one that, in many ways, mirrors Anakin and Padme. By the end of the episode, Obi-Wan must confront his emotions and Satine must confront her ideals.

And Anakin, almost nonchalantly, takes another step closer to the Dark Side.

The early acts of the episode are split between the assassin droids and Obi-Wan’s many interactions with Satine. The assassin droid sequences are good, if not entirely memorable (the most enjoyable moments were the way R2-D2 was used, and the music). But what they do best is to provide a very real example of what Obi-Wan and Satine argue so strenuously about: When is it necessary to use violence? At what point does one draw the line? Even Satine says that she will act in self-defense. The assassin droids are a very clear and present threat. It’s good to see the debate moving beyond just words and actually taking shape around actual events.

But when Satine is taken hostage by a treacherous Senator, matters become very serious indeed. Eventually, the traitor Tal Merrik, Obi-Wan and Satine end up in a stalemate. Merrik holds a detonator that threatens to blow up the whole ship. Satine holds him at gunpoint, but hesitates in using lethal force. Obi-Wan, too, hesitates, not wanting to have Satine watch him kill another being. It’s a fascinating moment — in terms of character and psychology — which nicely plays on the episode’s themes of “temptation.”

Of course, the solution is one which takes the decision away from both Obi-Wan and Satine, which may seem like an easy way out of making a character commit to a distasteful course of action. But by having Anakin kill Tal Merrik, in such an offhand and flippant manner, the episode *does* have one of its characters make a distasteful choice — and it demonstrates a callousness on the part of Anakin that is part of his descent to the Dark Side of the Force.

Overall Grade: B

One final strength of “Voyage of Temptation,” is the dialogue. Whether it’s the debates between Obi-Wan and Satine, or Anakin’s quips about Obi-Wan’s “girlfriend” or his comment of “What? He was going to blow up the ship!” after killing Merrik, the dialogue is very well-written.

“The Mandalore Plot” is yet another in a long line of The Clone Wars episodes that is filled with action and adventure and is a lot of fun to watch. Visually, the episode is exceptional. And the interactions of the characters are very entertaining. But there’s something about the halting pacing of the episode and, perhaps, some questionable logic to its featured “plot” which hinders the overall production. Still, it’s a classic episode for its introduction of Mandalore — an iconic planet and heritage in the Star Wars mythos.

As the episode begins, the Duchess of Mandalore, Satine, presides as the leader of the Council of Neutral Systems (not aligned with either the Republic or the Separatists). She has led Mandalore into an era of pacifism — a direction which doesn’t agree with a sizable population of her planet. After hearing a rumor that Mandalore is building a secret army for the Separatists, Obi-Wan Kenobi is dispatched to investigate.

From a visual standpoint, I really enjoyed the “cubic” Mandalore design — distinctly alien enough without being impractical. There’s also something of a history between Kenobi and the Duchess and their banter adds a to the fun of the episode. The Duchess is a nicely conceived and executed character and in fact, the comments from her about Kenobi’s role as a “peacekeeper” are both insightful and important for the episode’s plot. Both Satine and Kenobi have good points (namely that being called a “peacekeeper” while conducting a war is a contradiction, but that reality often forces people into unexpected and unwanted actions). It’s an enjoyable development for both the characters and the episode.

But of course, Kenobi’s mission isn’t about fun. And very soon he (and the audience) are introduced to the turbulent political currents of Mandalore politics. It seems that a group of Mandalore warriors, calling themselves “Death Watch,” are opposed to the pacifist government and are causing a disturbance on Mandalore. It is they that are allied with, and receiving support from, Count Dooku.

Here’s where the logic gets a bit fuzzy. The “Death Watch” hopes to cause enough of a disturbance to provoke the Jedi into sending a peacekeeping force to the planet. They then plan to use that Jedi “occupation” as a trigger to spark a public revolt against the pacifist Duchess and her government. But what makes them think that a general populace would actually follow a terrorist organization — responsible for violent acts against that populace — and calling itself “Death Watch”? I know this is just a cartoon, but let’s face it, as plans go, it’s a pretty silly one.

Fortunately, this doesn’t take up much time within the episode itself. Instead, the real emphasis is on the *actions* of those involved in Death Watch. There is a terrorist bombing in a public park. The perpetrator, not wanting to be interrogated by Kenobi, literally throws himself off of a building. It’s a grim series of events — terrorism promptly followed by suicide — which underscores just how desperate the situation on Mandalore is. Just as important is the manner with which the episode portrays these events. Once again, The Clone Wars treats these moments with a sobriety that is both necessary and a bit shocking for a cartoon.

Then it’s off to a moon of Mandalore to, finally, confront the Mandalorian Warriors (aka Death Watch). Given the amount of fiction written about the Mandalorians, this was always going to be a highly anticipated moment. And it doesn’t disappoint. They are disciplined, ruthless and cunning. Kenobi is captured (then rescued by Satine). And there’s a confrontation between Kenobi and (the unfortunately named) Pre Viszla, who owns a black lightsaber — a relic from the Old Republic. The ancient animosity between the Mandalorians and the Jedi is a nice touch, adding important depth to the battle between Viszla and Kenobi, and the upcoming conflict with Death Watch.

The action itself is intense, if relatively brief. Kenobi’s battle with Viszla and his troops is entertaining. And though Kenobi and Satine escape, it’s clear that there is much more to this storyline.

Overall Grade: B

“The Mandalore Plot” is classic Clone Wars. Action, character and theme are tossed together and presented with wonderful visuals. It’s another successful installment.

“Lightsaber Lost” is an amusing diversion. I think it’s safe to say that, of all the Clone Wars episodes to date, it’s easily one of the most “cartoonish” in its approach. The story, the characters, the dialogue all have a simple, juvenile feel to them. The biggest problem for the episode comes from how it compares to typical Clone Wars fare. The juxtaposition of this episode’s approach with that of other, darker, more intense installments will certainly make the mood feel a lot simpler than it actually is. Still, the change in tone can be a barrier for fans of the series.

The episode begins with an enjoyable look at the Coruscant underground, clearly referring to scenes from Attack of the Clones. Even the music is reminiscent of the film’s moodier motifs. But the episode really revolves around another element of Attack of the Clones: lost lightsabers. In this case, Ahsoka Tano’s lightsaber is stolen by a petty pickpocket thief. The rest of the episode, then, is spent on Ahsoka’s quest to find her lighstsaber — before her Master, Anakin, finds out.

The setup is decent enough, but the episode begins as a simple, almost childish affair. Ahsoka’s introduction to the elderly Sinube is handled by way of a pun (and I love puns) which underscores the simple reality that this is an episode geared mostly for the younger fans of the series. That’s not to say that the moment, or the rest of the episode for that matter, is poorly made, rather that it’s a rather significant departure in tone.

In a way, it’s a bit unfortunate. The character of Sinube certainly has the ability to grow on audiences as the episode unfolds. Indeed, he ends up endearing and quite a lot of fun to watch. I’m sure that’s part of the intent (to see him, initially, as a doddering fool when, in fact, his mind is as keen as Ahsoka’s athleticism). But if there’s a criticism here, it’s in the fact that the episode starts off too small, almost as if it wasn’t really giving itself a chance to ingratiate its story and characters with viewers.

The lesson of the episode is simple. Ahsoka is so impatient to find and retrieve her lightsaber that she often overlooks the obvious and, simply, isn’t thinking clear enough to work out the puzzles in front of her (as with the rest of the episode, the puzzles are also really simple). Alongside this lesson is a smaller, though no less important, commentary: a Jedi shouldn’t be defined by a lightsaber. As a case-in-point, Sinube doesn’t use his lightsaber at all, until the very last moment. The bounty hunter who ends up with Ahsoka’s saber even comments that, with the saber, she’s as powerful as a Jedi. But Sinube demonstrates that the powers of a Jedi involve using their minds and emotions to guide them to their goals.

For all its simplicity, there are some solid “adventure” moments tucked into the episode. The discovery of the bounty hunter and the chase through Coruscant is nicely evocative of Attack of the Clones. But more than that, there is Ahsoka’s little foray into the Dark Side. Her brief interrogation of a suspect — in which she quite nearly force-chokes the suspect — is a bit chilling in its implications. Along with her impatience, there’s plenty of reason to see how she might follow in the footsteps of her Master.

Overall Grade: C+

There’s plenty to like about “Lightsaber Lost.” But overall, the episode doesn’t quite measure up to the standard of The Clone Wars. At fault is the stylistic decision to make a more “cartoonish” story. The approach itself isn’t to blame, rather, it’s in the manner with which it was portrayed on screen. Still, a series often needs “change of pace” installments like this one, and it fits the bill rather nicely.

“Deserter” is a fantastic episode insofar as it is a sincere exploration of the clones as individuals. In fact, this installment is perhaps the best the series has to offer into real character drama. Unfortunately, the episode is an uneven affair, balancing the character work with a subplot that doesn’t really amount to a whole lot, either in terms of buildup or payoff. The result is a surprisingly arresting story that isn’t given enough time on screen.

With Grievous on the planet surface, Obi-Wan lands and tries to track down his quarry. After splitting his forces to speed the search, Rex is shot and his men bring him to a farmhouse to recuperate. Once there, they find a Twi’lek woman and two children — one of whom claims that Rex, “looks like my daddy.” After the troops leave Rex to continue their mission, Rex confronts Cut Lawquane, a clone deserter.

That such a thing has happened seems entirely inexplicable to Rex. Cut tells the story of how, just after the battle of Geonosis his team was shot down and all of his comrades were killed. He alone survived and, having been out of the war for so long, he fell in love and *chose* to live a life on his own, without going back to fight for the Republic.

What ensues is something of a debate between the two characters. Rex is firmly entrenched in his “programming” that fighting for the Republic is the *only* thing that matters — well, that and standing by your “brothers” in battle. Cut counters that there is more to life than dying for someone else’s war. He goes on to say that the power of choice matters and that he has chosen his own family. Rex says that he has “chosen” to fight for the Republic and the episode wisely allows both statements to stand on their own merits.

It’s this interplay between characters — between clones — that is the real heart of the episode. By exploring the clones themselves, by humanizing them, the series becomes much more sophisticated in its overall presentation. Clearly, the clones who fight and die in these episodes are not just mindless drones. And that should make each death all the more poignant (without having to reestablish this point in each installment).

Unfortunately, that is the high point of the episode. Rex and Cut will soon have to fight alongside one another (to repel an attack by commando droids). And the two will gain respect for one another through the shared conflict. But the situation is brought about by the whole “children acting stupidly” plot device. I mean, really, did we *have* to see the children inadvertently reactivate the commando droids? Wouldn’t it have been more straightforward to have the commando droids already active and descending upon the homestead after tracking the clones who carried Rex to safety?

Worse yet, the rest of the episode is pretty much filler material. An inordinate amount of time is spent on Obi-Wan searching … then looking for … then tracking … then hunting … Grievous. The sequences themselves are hardly noteworthy or illuminating, much less entertaining. And when juxtaposed with the much more intriguing and moving story between Rex and Cut, they seem more like ill-timed commercial breaks. At best we have the creepy “deaths” of the battle droids who run out of power, but not even a brief-but-intense firefight between Obi-Wan and his troops and Grievous can save the subplot.

Oh, and Grievous escapes.

In a nice touch, though, the episode ends with Rex making a fateful “choice.” He says, of reporting Cut’s desertion, “I have no choice.” But he makes the decision to conveniently “forget” what happened on the homestead, thereby not quite shirking his duty. It’s a subtle distinction, but it still represents what the story was all about: the power of choice.

Overall Grade: C+

“Deserter” gets a lot of credit for its depiction of the clones. Unfortunately, the rest of the episode is entirely forgettable. The result is an installment that is just a “cut” above average, but not quite a classic.

Just in case anyone needed a reminder of how thrilling and heart-pounding The Clone Wars can be, the unfortunately titled episode “Grievous Intrigue” will serve notice that, as far as action-based shows go, there’s almost nothing that can compare to this particular series. Oh sure, the story itself isn’t exactly deep or profound, but in terms of a dark, kinetic episode, you couldn’t ask for a whole lot more than you get from this installment.

The episode begins with an attack by General Grievous on a Republic ship under the command of the Jedi, Eeth Koth. Grievous and his droids board Koth’s ship and a vicious battle ensues. Grievous, along with super battle droids and commando droids overwhelm the clone defenders and soon Grievous is using his lightsabers to cut into the control room — where Koth is waiting for the inevitable duel. Once inside, the commando droids quickly dispense with the clones and Koth is left to fight Grievous and his henchmen droids (seen in Revenge of the Sith) all on his own. Despite his valiant efforts, he is overwhelmed by the sheer number of opponents and is captured by Grievous.

The sequence itself is notable for just how lethal the results are. A fair number of droids end up on the scrap heap, but an even greater number of clones end up being killed. Plus, once Koth and Grievous are engaged in battle, Koth is shot in the arm, then stabbed — repeatedly — by the “electrostaffs” held by Grievous’ henchmen. The lightsaber duel is fast … and intense. And Grievous contacting the Jedi and taunting them with the imminent, and painful, death of Koth is absolutely diabolical.

Fortunately for Koth and the Jedi, during the communication between Grievous and the Jedi Council, Koth is able to use hand signals to convey his location. This sets up the inevitable rescue mission. Obi-Wan will lure Grievous into boarding his own ship as a diversion to allow Anakin and Adia Gallia to infiltrate Grievous’ ship and rescue Koth. If all goes well, they will not only rescue Koth, but also apprehend Grievous.

All does not go well.

The space battle is fantastically rendered. It’s pure spectacle. And consider this: While there are plenty of ships thrown into the mix, the episode is free from the glut of ships seen in the opening battle of Revenge of the Sith. The result is a conflict (in the episode) that is much more immediate and meaningfully engaging. Besides, the pyrotechnics are really, really cool.

Really cool.

At any rate, Grievous seemingly takes the bait — but he doesn’t do so without hedging his bets. Part of what makes Grievous so formidable is his ability to anticipate his opponent’s actions. And to that end, he rightly guesses (after Obi-Wan sets the trap) that Anakin will soon arrive as part of Obi-Wan’s diversion. With that in mind, Grievous sets a trap of his own for Anakin: an overwhelming number of commando droids and a tactical droid set with orders to kill Koth if Anakin resists. Of course, Anakin does resist — and succeeds — but the tactic delays Anakin’s rescue, making it possible for Grievous to escape Obi-Wan.

And as far as the battle between Obi-Wan and Grievous goes, it is quite a bit of fun. It’s far more intense and frenetic than the confrontation between Grievous and Koth. Obi-Wan fares much better (dispatching the henchmen and commando droids), but he doesn’t escape the encounter unscathed. Worse still for everyone involved, Grievous manages to slip past Obi-Wan and return to his ship where he orders the immediate destruction of the Republic cruiser.

What follows is a thrilling escape sequence in which our Jedi heroes survive, along with a handful of clones. But commanders on board the Republic cruiser are still on board when it spectacularly explodes. Grievous escapes to the planet below and so, while the rescue attempt was successful, there is still much work to be done.

Overall Grade: B+

Just about everything in “Grievous Intrigue” works very, very well. The action is well-choreographed and exciting. The episode is absolutely lethal in its portrayal of the battle. And, visually, the whole affair is a feast for the eyes. What the episode is missing, though, is a story that has a deeper meaning aside from just a flat-out action sequence. True, the story doesn’t try to be anything more — and it succeeds in its intent — but without any deeper layers, it just isn’t as good as it could have been.

Plus, there’s the issue of the title. I know Lucas likes pulpy titles (“Phantom Menace,” “Attack of the Clones”) but c’mon … Grievous Intrigue … really? The episode had nothing to do with intrigue — it was about as obvious as it possibly could have been.  Ah, well.

For those that deride the Clone Wars as little more than a disposable kid’s show, there is an episode such as “Brain Invaders” — a middling installment that has no right be anything more than a “mindless” diversion. And yet, despite a decidedly slow and unimpressive buildup, the episode ends with a tremendously ominous development — an example of using the ends to justify the means.But  despite the positive outcome of the episode, it’s clear that this particular course of action will, ultimately, lead to great tragedy.  This then is an example of how, even with a relatively average episode, Clone Wars conveys a meaningful story.

Continuing the storyline established by the invasion and occupation of Geonosis, “Brain Invaders” follows the mission of Ahsoka Tano and Barriss Offee as they rendezvous with a medical supply ship on an urgent mission of mercy. The problem? The clones on their vessel have become infected with the same worms which caused Obi-Wan and Anakin so much trouble in the previous episode. The result is that the two Padawans must find a way to overcome an infiltrated ship — and an unidentified enemy — in order to accomplish their mission.

Much of the episode is spent establishing and developing the premise. Objectively, the scenes aren’t bad, but they really do not do a whole lot to elevate the story. Put simply, it’s a rather clinical affair of putting all the pieces in the right place so that the final act can be as powerful as possible. And, fortunately for the episode, that final act is, indeed, powerful.

Matters become desperate when the clones take over the entire ship, including Barriss, leaving Ahsoka alone and in great peril — not to mention the status of her mission. Anakin, who manages to communicate with Ahsoka, realizes the urgency of the situation. But he has at his disposal prisoner — Poggle the Lesser — who has been less than cooperative. The episode doesn’t actually show it, but it’s heavily implied (including a very effective use of the Imperial March) that Anakin tortures Poggle to get the information he needs.

And here is an example of Anakin using the ends (saving his Padawan and her mission of mercy) to justify the means (torturing a prisoner). For everyone involved in the episode, the results are decidedly beneficial. And yet, it’s another step on Anakin’s journey toward the Dark Side — a journey that will cause untold horrors across the galaxy.

In truth, this is an episode which requires prior knowledge about how Anakin’s character will eventually end up. But with that knowledge, the story becomes a very chilling warning: short-term benefits can come at the expense of long-term tragedy. And this moral foundation becomes a truly valuable element to the episode, nearly trumping the inexplicably pedestrian buildup.

Overall Grade: B-

“Brain Invaders” spends a lot of time being average, at best. But its final act is thoroughly compelling — and a perfect example of why Clone Wars is a fantastic series. Even when it isn’t firing on all cylinders, there is an inherent value to the stories and characters and thematic ideas.

“Legacy of Terror” is an exercise in creating a mood. As the episode unfolds, events become increasingly ominous and spooky – until the final horrific confrontation. Execution is key to stories such as this, and if there’s one thing that the Clone Wars series has proven of late it’s that it can craft stories with exceptional care. Such is the case here. The pacing helps build the increasing suspense and tension. The characters react plausibly – even providing some illuminating aspects of personality – and action kicks in at just the right moments. The result is yet another classic Clone Wars episode.

Following the successful invasion of Geonosis, the Jedi are left to clean up the few remaining loose ends … such as capturing the Geonosian leader, Poggle the Lesser. To that end, Luminara Unduli heads off on a speeder bike across the barren wastes of the planet to hunt down and capture Poggle. As she tracks her quarry, a sandstorm builds, providing the episode’s first moments of tension. Particularly effective is a conversation between battle droids who had been walking with Poggle’s escort convoy. In the midst of the storm, one of them falls and is left behind. It’s plaintive, “Don’t leave me,” carries a surprising amount of emotion for a battle droid.

But that’s only the beginning.

Luminara tracks Poggle to a bombed out temple, complete with “gargoyle” statues of some very strange and creepy-looking Geonosians. During a report to Anakin and Obi-Wan, she is attacked and her fate is left uncertain until the storm passes. Once Anakin and Obi-Wan arrive to investigate her disappearance within the catacombs underneath the temple, the real suspense begins.

Put simply, Luminara has been captured by zombies – or, at the very least, dead Geonosians who have been possessed by the Geonosian Queen and, therefore, are incapable of being killed a second time. As Obi-Wan, Anakin and their clone troopers traverse and explore the catacombs, they are repeatedly attacked by these loathsome creatures. And this, really, is where the execution of the premise becomes so important. Offhand, the notion isn’t especially compelling or interesting. But the manner with which the episode carries out the sudden attacks or disappearances of clones, is quite effective.

But that’s nothing compared to the surreal, alien setting awaiting our heroes in the “throne room” – the place where the Queen Geonosian lays her eggs … and uses worms to exert her mind control over her minions. She’s captured Luminara Unduli in the hopes of controlling the Jedi Master.

When Obi-Wan and Anakin arrive, we get a fascinating contrast between their personalities. Anakin, predictably, wants to charge in to the rescue while Obi-Wan wants to observe matters a bit longer, saying, “must you always rush into things?” This prompts Anakin’s exasperated comment, “You don’t actually want to talk to it, do you?” From here, as they approach the Queen, the two spar verbally, and playfully, about their respective approaches. The scene does quite a bit to establish the natural tensions between the two friends – tensions which, we know, will ultimately grow into rivalry and hatred (additionally, Obi-Wan’s almost clinical interest in The Worms is an amusing quirk).

As for the Queen herself, her mannerisms, voice, and design are all incredibly creepy, adding to the tension and suspense of the episode as a whole. And the final solution – to bring the entire chamber down onto the Queen – seems like an especially brutal tactic, even for the Jedi. Granted, it may have been the only means by which they could survive … but at the risk of killing the Geonosian Queen and, potentially, ending the entire Geonosian race?

Overall Grade: B

“Legacy of Terror” is an effective episode in almost every respect. The story itself doesn’t hold a lot of inherent value, beyond being a very good suspense tale. But for what it sets out to do, the episode is a success, creating palpable suspense, tension and some nicely nuanced character moments.

It’s all about character. And action and impressive visuals. But really, “Weapons Factory” is the kind of episode that illustrates why the Clone Wars series isn’t just another cartoon or just another kid’s show. In fact, behind the glitzy exterior is quite a bit of subtle characterization – through dialogue, action and even body language – particularly for Anakin Skywalker and his Padawan Ahsoka Tano. True, these aren’t quite Shakespearean explorations of the human psyche, but they are purposefully placed within the narrative and provide a significant amount of depth. The result is an episode which is very, very good.

In this installment, Anakin and Ahsoka, along with Luminara Unduli and her Padawan Barriss Offee, must destroy a weapons factory. But this is a backdrop to the more important story of Anakin and Ahsoka – of their relationship as Master and Apprentice, as well as Anakin’s inherent difficulties with letting people go. To contrast these characters, we’re introduced to Luminara and Barriss – who have a much more balanced relationship. This, then, is the heart of the episode.

It begins with Ahsoka’s briefing on a frontal assault of the factory. Anakin repeatedly interrupts his Padawan, causing Ahsoka to question her Master’s faith in her. And really, it’s not that Anakin doesn’t believe in her, rather he’s so concerned about everything going right that he doesn’t stop to think about Ahsoka. The tensions between Anakin and Ahsoka are further reinforced when Luminara and Barriss offer a new plan, which is based on Luminara’s confidence in Barriss’ abilities: Barriss will lead Ahsoka through an underground catacomb to destroy the factory from the inside, while Anakin and Luminara create a diversion with a frontal assault.

The battle sequences are briskly paced. Once again, the series doesn’t hide the fact that in war, people die (a point that finds its way into incidental shots showing dead and wounded clones and Geonosians). There’s good lightsaber action from Anakin and Luminara, funny dialogue from the battle droids, strategizing on both sides (Anakin’s “You shall not pass!” ploy to get rid of the super tanks was fun) and plenty of action. The catacombs through which Ahsoka and Barriss must travel are nicely done, creating a very spooky and ominous mood. These are entertaining scenes, which are nicely paced, but they serve primarily as a bridge to get to the episode’s more profound moments.

Though Ahsoka and Barriss make their way to the reactor, their plans are stymied by Poggle the Lesser and his troops. Left with no other option, they must use a tank to destroy the reactor – bringing the entire factory down onto them in the process. From an emotional standpoint, the moment is handled surprisingly well. But more important is the effect this has on Anakin. Luminara seems almost resigned to the fate of her Padawn, but Anakin is not, provoking his outburst of, “I refuse to let Ahsoka die. She will find a way out.” Anakin’s darker emotions are clearly surfacing and it’s illustrated not only in the dialogue, but also the voice acting and facial expressions. Furthermore, Anakin’s attachment is fully revealed – as well as his anger at even the prospect of letting go.

Of course, Ahsoka’s resourcefulness helps Anakin locate her and both she and Barriss survive. Anakin never did lose faith in his Padawan and all would seem to be well. But, of course, this is just another step along Anakin’s path to the Dark Side. Luminara ominously notes, “Unlike you, when the time comes, I am prepared to let my student go. Can you say the same?”

We already know the answer.

Overall Grade: A-

“Weapons Factory” is an excellent character-driven episode of the Clone Wars. Unlike the early episodes of the series, the Anakin-Ahsoka relationship is much more nuanced and informative for both characters. There’s a great deal of craft going into this show, proving that while it is a show geared for children, it isn’t simply a juvenile tale.

I think it’s safe to say that I’ve never seen an episode like “Landing At Point Rain,” from the increasingly superb Clone Wars series. From start to finish it is a tour de force of action, intensity and the brutal reality of war. It’s an episode that pulls no punches and is easily the best action Star Wars has seen since … well, perhaps ever. If there is a criticism to the episode it’s in a story that is relatively thin on character or theme. But this episode set out to be the most intense, action-packed installment of the series thus far and it succeeded masterfully. Or to put it another way, the episode was impressive. Most, impressive, indeed.

This is the story of how the Republic must re-take the planet of Geonosis. Due to the war, the Republic was unable to maintain control of the planet and now it has reverted to being a foundry for the Separatists’ droid armies. It’s a reality that the Republic cannot allow to continue, so they send Obi-Wan Kenobi, Ki-Adi Mundi, Anakin and Ahsoka Tano to lead a powerful planetary invasion with the goal of shutting down the foundries and capturing the Geonosian leader, Poggle The Lesser.

Of course, their three-pronged attack quickly goes awry and the heroes are left to battle desperate odds in the hopes of not just succeeding in their mission … but actually surviving. And here’s where the episode truly shines. The battle sequences are intense. They are well-scripted, choreographed and executed. They effectively portray the mayhem and danger of an all out ground attack. The cinematography and pacing were nothing short of brilliant. And the structure of the episode was solid, including its many transitions between three distinct plotlines (which were seamlessly interwoven).

This was no “movie battle” where the heroes escape unscathed (even if they do eventually complete their objective). Their ships are shot out of the sky.  Obi-Wan Kenobi is so badly injured that he’s barely able to raise his lightsaber in self defense. They lose troops at an alarming rate. They are consistently outnumbered and outmaneuvered. And it is only through the sheer heroics of not only the Jedi, but the clones as well, that wins the day. And throughout, the action never lets up. There really are too many fantastic moments to mention, but the initial attack and aborted landing sequence served notice: This was an action story that was designed to be much, much better than anything we saw in the prequels. And so it was.

Overall Grade: A

“Landing At Point Rain” is easily one of the best episodes of the series to date. I’d be surprised find another television episode that is filled with this much action. And I’d be even more surprised to find one as nearly flawlessly executed as this one. Still, there is that lingering issue of a lightweight character and thematic story (likely to be addressed in the follow-up episode). And while that’s not what this episode was ever intended to be, it does keep it from perfection.