‘The Bad Batch’ Recreates the Magic of ‘The Mandalorian’

So yesterday’s episode of The Bad Batch was fun. It was simple with a bit of touching moments between Hunter and Omega, invoking that same sense of familial comfort that Favreau and Filoni were able to perfectly create with Mando and Grogu in The Mandalorian.

And I think that’s going to be the main focal point of this newest animated series. The bond between these clones against the adversity the galaxy will bring, the shocking turn of Crosshair and how he will be a major thorn in the Bad Batch’s side, Omega’s story and how she will grow closer and closer to this group of clone misfits, and eventually, toward the end of the series, we will see some of these characters die.

It’s bound to happen because, well, we’ve never seen The Bad Batch beyond this point. Will they all die? I’m not quite sure but I think it’s kind of obvious that Filoni is going to kill Hunter and rip our hearts out in the process. Why do I think this is going to happen? Because he’s already killed so many lovable characters before; Steela Gerrera, Satine Kryze, Kanan Jarrus, and even though Ezra’s technically alive, he still made him sacrifice himself at the end of the show, disappearing for three years now.

So yeah…I have a bad feeling about this.

I’ll give the second episode a solid 4 out of 5 stars. It wasn’t the best thing I’d ever seen nor was I expecting it to be but it was enjoyable, engaging, and yeah, I got a little stressed out.

What did you think of the second episode? Feel free to share your thoughts in the comments below.

I thank you for reading and I hope you have a tremendous day.

9 thoughts on “‘The Bad Batch’ Recreates the Magic of ‘The Mandalorian’”

  1. You’re right, and I hadn’t really climbed into their heads to think of what they were going for, but they’re obviously aiming for the dynamic they got in Mando where a kid softens up the action hero(es). They even redid the second episode there where Mando let Grogu go for money for a bit before coming back for him. This time it’s more altruistic, as they had Hunter sending Omega off with Cut because he thought it’d be better for her, and she comes back on her own.

    I generally liked the episode, but it doesn’t hold up to thinking too much about it. At least one continuity glitch where they changed a previous premise, and a half serious plot hole or three at the end. I found myself in a pretty serious dive down a rabbit hole of rant when I wrote it up myself.

    Liked by 1 person

      1. Well, the plot holes of spaceport operations I can sorta forgive. The continuity glitch they created around chain codes bugged me a bit more. I suppose it could be passed off as an incomplete concept that they decided to refine… except that the entire first season of Mandalorian was based on it being interpreted one way, and now Bad Batch is interpreting it differently and not compatibly with Mando.

        Liked by 1 person

      2. Oh my goodness, exactly! I was trying to remember where I remembered chain codes from. Yeah…that’s kind of confusing.

        Lucasfilm is not Marvel Studios. Their continuity issues are nonstop.

        Liked by 1 person

      3. Yeah. The whole first season of Mandalorian is based on the Client having had a fifty year old chain code for Grogu. It’s how Mando finds Grogu himself, and it’s how the entire rest of the guild tracks the two of them after Mando rescues him. But in this episode, Tech acts like he’s never seen these things before; they’re described as a new system that the Empire instituted in order to track and control their citizens, as a fresh tool of oppression that’s previously unheard of. If that’s the case, then how can Grogu’s chain code be fifty years old (read: that’s about thirty years before this episode of the Batch), and why does that chain code even exist? If the Empire had ever caught Grogu at some point, “registration” was not exactly the going procedure for rogue Jedi on the run, as I said in my blog at the time.

        This sounds like a good thing for a fan theory entry. 😛

        Liked by 1 person

      4. Yeah. So… I wrote a couple of theories that are something other than nonsensical on my blog this morning. The short version is that both of these two explanations (Bad Batch implying that it’s new, and Mandalorian saying that it’s not) can’t both be correct, and that there are different implications of each.

        For reasons I won’t go into here, I like the “Mandalorian is correct” version better, because it has more interesting story implications — both for not invalidating what we previously saw in Mandalorian, as well as explaining why the Empire is suddenly instituting this system on a larger scale. Hint: if the Empire didn’t create the system and create a chain code on Grogu, then the most likely people who would’ve (and secretly enough that Tech wouldn’t have heard of it)… are the Jedi. Buuuuuut the Empire now has that data, including the code for Grogu that the Client ultimately gave Mando 28 years after Bad Batch is taking place… so three guesses why the Empire would suddenly be scaling up a chain code system to oppressive levels across the entire galaxy. 😉

        Liked by 1 person

  2. I thought “Cut and Run” was a solid episode. They cemented that the parent bond will be between Omega and Hunter, basically positioned the rest of the group as possible bumbling uncles, and quickly swept away the possibility of Omega being left with a more suitable guardian for a child all in the second episoe.

    Now they can focus on setting up the overall story with the Bad Batch being deserters on the run picking up missions on the side and catching wise to what’s really going down with The Empire.

    Liked by 1 person

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s