“The Mandalorian: Chapter 3” Review!

It’s impossible to talk about this episode of The Mandalorian without making reference to some spoilers, in contrast to last week’s episode, which saw Pedro Pascal’s armored bounty hunter and internet sensation Baby Yoda team up to take down a rhino and do basically nothing else for half an hour. At the end of that episode, titled The Child, the Mandalorian was last seen boarding his spaceship with Baby Yoda in tow, presumably escorting the adorable little green puppet back to his client, the mysterious mastermind played by Werner Herzog. So where does the story pick up this week?

Well, that’s where the spoilers come into play, so if you haven’t seen the episode, you should definitely do so – I know! I’m actually recommending this show now! That’s because director Deborah Chow has actually managed to revitalize my interest in the Mandalorian’s character arc, and his interactions with Baby Yoda, which are the emotional heartbeat of this story so far.

"The Mandalorian: Chapter 3" Review! 1
denofgeek.com

When the episode begins, however, the Mandalorian is forced to make a very tough choice about Baby Yoda’s future: face-to-face with Herzog’s nameless (but unmistakably evil) Imperial client, the Mandalorian – even in-universe, every other character has taken to calling him Mando, so I’m going to do the same, despite my concerns that the name is instead in a disparaging, rather than respectful, way – ends up handing over the adorable little green baby in exchange for a handful of metal slabs that he turns into more armor (and another shoulder-pad to match his current one) with a little help from Emily Swallow’s character, The Armorer. Just as before, Mando gets flashback visions while the Armorer is busy making his new suit of armor; visions which, as before, show a child (presumably him?) being rushed through a war-zone by frightened parents and placed into a bunker. Now, though, we get a tantalizing new glimpse of what happened – barely moments after being carried to safety, an explosion rocks the underground chamber and baby Mando looks up to see the bunker doors thrown open to reveal an intimidating killer robot – one of the B2 super battle droids from the Star Wars prequels, if I’m not mistaken.

We still don’t know why the Mandalorian gets these flashbacks when he’s at the armory, but we do get some insight about the workings of Mandalor culture – emphasis on cult, as the small group of secretive warriors seem to be. With their semi-religious reverence for weaponry and their deference to the weapons-maker, it looks like the way of Mandalor lies in battle and the glory of warfare. Our protagonist, the Mandalorian, is up for a promotion, it seems, for killing the big rhino in the last episode, and the Armorer asks him if he’d like to choose a signet engraved with said rhino’s image – an honor he respectfully refuses, as he had help in killing the creature “from an enemy”, i.e. Baby Yoda.

But the Mandalorian has a heart of gold, or at least something other than Beskar steel, which everybody else in the galaxy is willing to sell their souls for: rather than move on with his life and go hunt down other innocent people for money, he decides to turn around and save Baby Yoda. Helped along by his new, impenetrable armor and his highly-advanced weapons (such as “singing birds”, which is basically a volley of poison darts hidden in one’s glove), the Mandalorian is successful in his mission, and breaks an unconscious Baby Yoda free of creepy Doctor Pershing’s nefarious operating table. Pershing swears up and down he was trying to keep Baby Yoda alive, but the Mandalorian ignores him and goes looking for Herzog’s character – instead, he finds a whole bunch of stormtroopers, whom he dispatches (thanks to those singing birds and a couple of flamethrowers), before making his escape. As of right now, we still have no idea where Herzog’s character has gone, and we’re still no closer to learning his true identity.

So the episode’s titular Sin has been repented for, but the Mandalorian isn’t quite out of the woods yet – or should I say, out of the grungy city full of hundreds of other bounty hunters whose tracking fobs all light up and start pointing the way towards the fleeing Mandalorian. That little predicament (undoubtedly sparked by Herzog, wherever he is) leads to a confrontation at the spaceport between Mando and a crowd of angry killers, assassins and mercenaries led by Mando’s…friend?…Greef Karga, played by Carl Weathers. While it seems at first like little Yoda might use the Force to get them out of trouble, it turns out to be Mando’s other Mandalorian friends who arrive with jetpacks and laser-machine guns to save the day – well, night. And after briefly confronting Karga and throwing him out of his spaceship, Mando and Baby Yoda take off once again to destinations unknown.

And I, as the skeptical audience-member unimpressed with the series’ previous installments, am left feeling very pleased with what I just watched. It was complete, but gave us enough hints and unsolved mysteries to keep us guessing. It was more compellingly acted, though Pedro Pascal is still fighting a losing battle with his helmet (which, according to his character, he has never removed in all his life: he did hesitate slightly when asked if he had ever had it removed for him, though – why, pray tell, is that even a question one asks of someone?).

Next week, we should find out where the Mandalorian and his infant quarry are headed, and what Herzog plans to do about them. I hope we also finally get to see Ming-Na Wen in next week’s episode, since the show is still conspicuously Ming-less.

What did you think of the episode, and what theories do you have about the series in general? Share your own thoughts in the comments below!

Episode Rating: 7/10

 

Greef Karga (Carl Weathers)

“The Mandalorian: Chapter Two” Review!

"The Mandalorian: Chapter Two" Review! 2
bustle.com

Okay, so a quick rundown of everything that happened in Episode 2 of The Mandalorian, a.k.a. Chapter 2: The Child.

Nothing.

Absolutely nothing. That was quite possibly one of the most inconsequential episodes of television I’ve ever watched. I don’t even feel like spoiler tags are necessary for this review, but here’s your quick warning anyway. SPOILERS AHEAD. If you want to call them spoilers. Honestly nothing happened.

The episode picked up where the last one left off, with The Mandalorian (Pedro Pascal) escorting baby Yoda through the desert. The two are immediately attacked by other mercenaries, whom the Mandalorian dispatches without trouble. The rest of the episode follows the pair as they hunt down a group of Jawa aliens who had ransacked the Mandalorian’s spaceship for parts, leaving the bounty hunter and his cargo trapped on the desert planet. Finally, the Mandalorian reaches an agreement with the hostile scavengers: in exchange for the needed parts, he will bring them an egg from some sort of alien rhino monster. He does so, just barely surviving the experience, and the trade happens: with the help of the alien Kuiil (Nick Nolte), he fixes his spaceship and leaves the planet with baby Yoda.

And that’s it. There’s one big “reveal”, but it’s predictable: during the fight with the alien rhino, the Mandalorian is beaten up and on the brink of death when he is saved at the last moment by baby Yoda, who wields the Force, allowing the Mandalorian the time he needs to regain his footing and plunge a knife into the monster’s flank. At which point baby Yoda falls asleep, apparently exhausted by the effort. And all that would be hugely exciting…if the baby in question wasn’t obviously a miniature version of one of the greatest Jedi masters of all time. Whether this Yoda is a clone or a child of the original, it was kind of inevitable that he/she (we still don’t even know its gender!) would have the same powers as the previous Yoda. Honestly, I was expecting a couple of clues, or at least some hints or teases, of what’s to come. But instead we got an entirely pointless escapade with the Jawas, just so we could confirm something that pretty much everybody already guessed was coming.

And beyond that…literally nothing. This little side-quest did not need to be an entire episode – it could have been summed up in maybe five minutes at most. Unless, of course, the Jawas and the Egg have some important part to play later on in the series: though, the Jawas did eat the Egg immediately after receiving it, so it might be a bit late for that.

As we wait for the next episode, I have to wonder what was the point of Chapter 2, and how much longer we’ll have to wait before something of consequence happens. Now that the Mandalorian is finally on the move again, it’s hopefully only a matter of time before something happens: but, in a show that just wasted a half-hour episode on Jawa scavengers, nothing is certain.

Everything frustrating about the first episode is made even more annoying in the second: the Mandalorian himself is, in fact, more clumsy and incompetent than before – he’s easily defeated by the Jawas (the Jawas, who even the notoriously lame stormtroopers were able to kill with ease in A New Hope), and the big rhino almost succeeds in killing him. He’s just not a particularly interesting protagonist as of right now, and this episode does nothing to change my perception of him.

So…until next week, Star Wars fans. Let’s hope that when we rejoin the Mandalorian and baby Yoda, they’re actually doing something important.

Episode Review: 1/10

“The Mandalorian: Chapter 1” Review!

The first segment of Jon Favreau and Dave Filoni’s The Mandalorian is an intriguing introduction to a darker, grittier corner of the Star Wars universe, doing a whole lot of worldbuilding, establishing a compelling mystery spanning several planets, and leaving viewers with plenty of questions.

"The Mandalorian: Chapter 1" Review! 3
comicbook.com

Set sometime after the fall of the Empire in The Return Of The Jedi, the series presents us with a region of deep space that seems unaffected by the peace and prosperity we saw blossom across the universe in Jedi‘s celebratory finale. The aliens and humans we encounter in the pilot episode are barely scraping by, surviving only by hunting down their enemies and killing them – or hiring others to do so. The nameless protagonist played by Pedro Pascal, known only as the Mandalorian (or “Mando”, as he is disparagingly called in one space cantina), is supposedly one of the most legendary bounty hunters in the parsec, though he does surprisingly little to earn that reputation in this episode: the action sequences are few and far between, and the big battle at the end of the episode is really just a whole bunch of red laser-bolts dancing wildly across the screen, leaving the Mandalorian himself with little room to prove his own tactical or military prowess. His uncomfortably awkward encounter with an alien monster named a Blurrg undermines the character even further. As of right now, I can’t understand why everyone is so terrified of the Mandalorian, or how he has somehow established such command in the bounty hunter guild he works with – but his ally, the hunter droid IG-11 (voiced by Taika Waititi), while undeniably more malevolent, is even more clumsy, so perhaps this is a trait shared by all of Star Wars‘ bounty hunters – even the mighty Boba Fett fell into a Sarlac pit, after all.

It’s an unpleasant reality, but Pascal’s Mandalorian is simply not as interesting as some of his co-stars in the first episode, who receive far less screentime but far more personality and character. Even the Armorer, a female Mandalorian who designs a shoulder pauldron for the Mandalorian (I get that they’re a secretive people, but names would be really helpful right about now), is marginally more interesting than him: Mandalorian culture in general is something that I’d love to see explored in greater depth as the series progresses – though at present, there’s a much greater mystery unfolding, one which definitely takes precedence over “why are shoulder-pads so important to the Mandalorians?”

Werner Herzog plays the Mandalorian’s nameless client, who appears to be a survivor of the Empire’s demise: he commands a host of trigger-happy stormtroopers, and is working closely with a suspiciously enthusiastic scientist named Dr. Pershing (Omid Abtahi). The two men employ the Mandalorian to hunt down a dangerous target on the other side of the galaxy, though neither is willing to give many details about their prey – save that Pershing wants it alive at all costs. We’ve known for quite some time that this series could give us crucial details about how the fallen Empire rebuilt itself into the First Order that currently threatens Rey and the Resistance: if I had to make a guess at this early stage, I would assume that Pershing and his mysterious friend have something to do with that. And I’ve even got the beginnings of an idea as to why that might be, but it requires us to get into spoiler territory – so without further ado, here’s your SPOILER WARNING!

At the end of the episode, after the Mandalorian and IG-11 have broken into an alien base on a desert planet, they come face to face with the unidentified asset they’ve been hunting via tracking fob. And while some of us might have been expecting their target to be a prominent Star Wars character such as Obi-Wan Kenobi or Princess Leia, they are instead greeted by…a tiny floating cradle. It would have been absolutely outstanding if the cradle’s occupant had turned out to be baby Rey, but no…

It’s baby Yoda.

Now, The Mandalorian takes place after Yoda’s death, so obviously this isn’t the Jedi Master himself – which means there are only a couple of reasons why this character would even be introduced, and why the Empire would be so desperate to hunt him/her down and capture him/her. It could be that Baby Yoda is a completely unrelated member of the Jedi’s same species (which, let’s face it, isn’t likely). It’s possible that Baby Yoda is Yoda’s child, which is at least theoretically plausible. But I happen to think this baby is none other than Yoda’s clone: an infant messiah who the Empire might want to capture for two reasons – firstly, because letting it live isn’t exactly Imperial protocol; and secondly, most importantly, because at this point in the Star Wars timeline, with the Empire collapsing into ruin across the galaxy, with the forces of evil on the run, the Sith Lords are desperate for something to restore their greatness and glory. What better way to do so than to bring back Emperor Palpatine himself – something we know will happen in The Rise Of Skywalker – through use of cloning technology? Why else would a scientist be so desperate to get his hands on the seemingly harmless child? Why else, unless he wanted to study the secrets of cloning and use that technology to resurrect the Emperor?

But the Empire didn’t count on Pedro Pascal’s Mandalorian being a kind-hearted softie who can’t bring himself to hurt the baby when he confronts it – even killing (or at the very least injuring) IG-11 when the droid tries to “terminate” Baby Yoda. The episode ends with a powerful shot of Baby Yoda holding the Mandalorian’s hand, staring up at him with adorably naive eyes and making cute cooing noises. I don’t know what to expect from Episode 2, but somehow I don’t think that the Mandalorian will be responsible for taking the baby back to the Imperial baddies.

Aside from Baby Yoda, the episode’s finale leaves us with a couple of big questions. Is IG-11 really dead? Will the Mandalorian be able to escape with Baby Yoda? – his Ugnaught guide Kuiil (Nick Nolte) was adamant that people who enter the desert don’t come back alive, but the Mandalorian seems to have taken care of all of the infant’s alien guardians pretty easily. As for the Mandalorian himself, who is he? Glimpses of his backstory as a war refugee played in a montage while the Armorer was designing his shoulder-pad, so it looks like Pascal’s character might have had a tragic past during the Clone Wars.

When all is said and done, the series’ pilot episode is merely good – with hints and teases of better material down the road. At the very least, it’s worth watching for Ludwig Göransson’s beautiful score, which sounds almost more fantasy than sci-fi. And with characters like Ming Na-Wen’s assassin Fennec Shand yet to appear onscreen, there’s plenty to look forward to in later episodes.

Episode Review: 7/10

Benioff & Weiss Depart “Star Wars” Franchise!

What Deadline is reporting as a “Star Wars Setback”, the rest of the world seems to be praising as one of Disney’s greatest business moves in a long time. The bitter war waged against Game Of Thrones screenwriters David Benioff and D.B. Weiss by their enraged ex-fans has now reached a crescendo, with the two men being forced to abandon their newfound place at the helm of an entire Star Wars trilogy. It’s a big win for audience backlash, which is both exciting and a little frightening.

It’s exciting because, in this case, fans really do have a good reason for wanting Benioff & Weiss to exit Star Wars. The duo are pretty much exclusively responsible for the controversial final season of the HBO TV series, Game Of Thrones, that saw character development thrown out the window, expectations subverted in the worst way, plot twists coming out of nowhere – all of it to rush towards a clumsily-structured, badly-written finale that saw the series’ protagonist and most beloved character slain in cold blood. Fans are understandably worried that what happened to Game Of Thrones can happen to Star Wars, and there’s obviously plenty of reason to believe them. I wrote an entire post on this subject yesterday, in which I addressed Benioff & Weiss’ recent interview (which I think must have been a contributing factor in their decision to depart Star Wars), in which they talked about basically scamming HBO into giving them an expensive film school experience while they were supposed to be developing a TV series based off of books they didn’t even try to understand. I’m sure Disney was also more than a little nervous about hiring two men who just unabashedly revealed that they got into a heated argument with a mother who didn’t want them placing her baby fully-naked on a block of ice, both exploiting and endangering the infant.

On the other hand, it’s also a nerve-wracking development: how closely do studios listen to their fanbases, and how much influence and power should audiences exercise over film-making? It’s a question that has been plaguing us for quite some time, but it’s all about context: when fans rioted about the design of Sonic The Hedgehog in Paramount’s Sonic movie, they were justified because the character looked like an asymmetrical weasel rather than a hedgehog; when protesters demanded a boycott of Disney’s Mulan remake because the lead actress expressed her support for the police-state of China, they were definitely coming from the right place, though that story is a very complex one; when heartbroken fans demanded that Johnny Depp’s career be canceled after claims of domestic abuse arose against the actor, well, we still don’t know who’s right or wrong in that case, or if it’s actress Amber Heard who should be canceled instead, or if it’s both of them. Context matters in these situations. So, yes, in my opinion, fans are at least partly justified in wanting Benioff & Weiss to leave Star Wars, because there are many reasons not to trust the two men with a story of that magnitude, so soon after the disastrous finale of Game Of Thrones.

We could also say they deserve a second chance, and that’s true, to some extent: which is why it’s a good thing that Benioff & Weiss already signed a deal with Netflix, which is where they will be headed. If they do a good job over there, with some smaller projects that don’t run the risk of upsetting a franchise that has only just regained its footing to begin with, then maybe they should consider coming back to Star Wars – if Kathleen Kennedy will have them. But in the meantime, Disney is keeping that galaxy far, far away from the divisive duo.

In Benioff & Weiss’ defense, their statement on the matter implies that it was their obligations to Netflix that prevented them from devoting their full time and attention to Star Wars – but while I suppose that could be true, it seems more likely to me that it’s the polite way of flattering Netflix into offering them more job opportunities.

So what do you think? Is this a win for fans – or a loss for Disney? Share your own thoughts and opinions in the comments below!