Spoilers For Star Wars: The Rise Of Skywalker Ahead!
One of the biggest criticisms of The Rise Of Skywalker was the nature of Emperor Palpatine’s return, and the fact that he just sort of…showed up again, literally hanging out on a life-support crane suspended from the ceiling of an ancient Sith amphitheater hidden beneath a floating pyramid on the previously unknown planet of Exegol, which was described as a homeworld of the Sith – which, in and of itself, was confusing: wasn’t Moraband the homeworld of the Sith, according to The Clone Wars, season 6? As if that wasn’t enough, it was revealed soon afterwards that Palpatine had not been idle, and had built a massive army of mini Death Stars on Exegol (because the Death Star is an idea that will never not be reused in the Star Wars franchise), each manned by thousands of ex-Imperial warriors, including a new brand of bright red stormtroopers who were hyped up in the pre-release marketing and barely had a millisecond of screentime in the actual film.
Needless to say, Star Wars fans had a lot of questions about the mysterious planet after leaving the theater – and very few of them were answered at all satisfactorily. But because The Rise Of Skywalker developed something of a reputation for leaving questions unanswered, most fans have already moved on from the subject and stopped theorizing about things like “what even is an Exegol?”, taking it for granted that this, like many other unresolved subplots in the film, would probably be explained someday in a throwaway line from a producer or a semi-canonical graphic novel.
But I’m guessing that very few people, even those of us who actually enjoyed Rise Of Skywalker for what it was, suspected that we would ever get an entire movie set on Exegol. It’s not that a bleak, barren icy wasteland riddled with blinding lightning and haunted by Sith ghosts doesn’t sound like an interesting location for a movie, it’s just that…well, spending two hours there, maybe more, watching Palpatine’s limp dishrag of a body being wheeled around on a crane, overseeing the construction of a fleet of redundant planet-destroying weapons that we, the audience, know will be defeated in a few minutes by a nifty lightsaber trick? I don’t know, I think I’ll pass (I say that now).
We don’t yet know for certain whether the Exegol movie will be released theatrically, or on Disney+ – what we do know is that it is being developed by Sleight director J.D. Dillard and MCU writer Matt Owens, who crafted the two best seasons of the fantastic, underrated series Agents Of S.H.I.E.L.D. We also don’t know anything about the plot, time period, or cast of characters. It could follow a young Sith acolyte during Palpatine’s Final Order, but it’s just as likely that it documents the story of some of the first Sith in the galaxy far, far away – such as the rise of Darth Bane, or one of the characters from the Knights Of The Old Republic video games. Villain origin stories are all the rage nowadays: though typically not from Disney, the studio which not too long ago canceled a planned streaming series, which would have focused on iconic animated villains like Ursula and Maleficent, for being “too dark”. If a business-savvy octopus is too dark for Disney, then I have to imagine that an ancient, bloodthirsty evil that demands human sacrifice and a form of government best described as “murder see-saw” would be too.
Who knows? Maybe it’ll be an ensemble movie about the Knights of Ren: you know, the ones who were rumored to be the greatest Sith warriors in the galaxy and were built up for two movies before becoming quick and easy lightsaber-fodder? You remember their names, right? Trudgen (Trenchen? Trunchen?), and something beginning with an A, and something with too many consonants (or was that the same one whose name began with A?), and the other one, the one whose job was to rebuild Kylo’s helmet? Remember them? Classic additions to Star Wars canon.
I actually did like The Rise Of Skywalker, I swear.
So what do you think of this news? Does the idea of watching a Star Wars movie focused on the Sith interest you, or does it seem too radically different from what we’ve seen before? Should the film follow Palpatine or a past Sith, or no Sith at all? Share your thoughts, theories and opinions in the comments below!
The long-running (and long-canceled) hit TV series The Clone Wars returns for its final season on Disney+ with a solid, if a bit wooden, pilot episode that gets the focus back on the Clones themselves. While the entire “Bad Batch” story arc that will kick off this season was written several years ago, this is the first time we’ve seen it played out onscreen: we’ll need to wait to see how it plays out before passing judgement, but for the moment we can assume that the clues and hints being dropped will lead to some pretty interesting interactions between our core cast of characters in the very near future.
In the pilot, the Grand Army of the Republic, led by Jedi commanders Mace Windu and Anakin Skywalker (voiced by Matt Lanter) find themselves fighting Separatist droids using their own strategies against them. Captain Rex (who, like all Clones, is voiced by Dee Bradley Baker), enlists the help of Clone Unit 99, known simply as the Bad Batch, after whom the pilot is titled, to sneak behind the enemy’s front lines and get to the truth. The Bad Batch’s tactics are unconventional, to say the least, as one would expect from a team comprised of “defective clones with desirable mutations”.
The few action sequences with the Bad Batch are simply okay, however. Since the Batch’s strength comes from their individuality, I would have liked to have seen each of the characters’ skills exploited in clever ways: but only Crosshair, the team’s ultra-precise sniper, gets anything resembling a cool hero moment. Wrecker, the strongman, should have had one when he carries a wounded soldier out of the wreckage of an explosion he caused (one which he prefaces with the word “Boom”, delivered appropriately deadpan), but the shot is strangely framed as a close-up of Wrecker’s face, preventing you from getting the full effect.
Most of my complaints about the episode stem from the editing, which I felt was lacking. Despite ostensibly being the most violent Clones to date, the episode is cautious when it comes to actually depicting that violence: in one scene that I feel I’m probably nitpicking way too much, a transport ship is shot down by enemy fire and crashes – but where was the customary reaction shot of the pilot letting loose one final Wilhelm scream? Such a shot would surely have been shown in earlier seasons, and the whole scene feels oddly incomplete without it. Considering that The Clone Wars has never shied away from showing characters get shot, eaten by alien monsters, cut down by lightsabers, or sucked into the vacuum of space, and had built a reputation (before its cancellation for exactly this reason) of telling mature stories with a kid-friendly twist, this feels like a very different approach to storytelling, and one with which I’m not comfortable yet. Then again, we’re only a single episode in and we haven’t reached what are sure to be some of the entire series’ darkest moments.
Overall, the episode is less focused on the action than it is on the mystery, which it sets up very effectively. If you haven’t seen the episode yet, and are concerned about the SPOILERS AHEAD, then read no further.
Rex’s suspicions about the Separatists are confirmed when he and the Bad Batch break into a cyber station and decode secret communications with a human on the planet Skako Minor, who has been feeding the Separatists top-secret battle strategies. Rex is quickly able to determine that this human is none other than his long-lost teammate Echo, who was believed to have died in the battle of Lola Sayu. The operation to rescue him from the clutches of the Separatists, and specifically the repulsive Admiral Trench (also voiced by Dee Bradley Baker), will be the focus of the next few episodes – after that, we’re all in the dark as to what comes next, and how The Clone Wars, after six incredible seasons, will wrap up this final chapter of the story.
What did you think of the episode, and what are you excited to see next? Share your own thoughts, theories and opinions in the comments below!
The final episode of The Mandalorian‘s first season on Disney+ is quite appropriately titled Redemption – for not only does the title work in-universe, but it’s also an amusingly apt reflection on the fact that Redemption very literally redeems the slow-paced series’ many mishaps. The plot itself often seemed like an afterthought while Mando (Pedro Pascal) and his tiny, adorable sidekick Baby Yoda traveled the galaxy, stopping in at random planets to marvel at the visual spectacle and meet new friends – or enemies. But in the season finale, masterfully directed by Taika Waititi, the story is rich, thrilling, entertaining and emotional; the characters feel more fleshed-out than they have appeared previously; and, most importantly, Baby Yoda is the cutest we’ve seen him yet.
And that’s all I’ll say in the non-spoilers section. If you haven’t watched the episode yet, but plan to, then turn away now! SPOILERS AHEAD!
The finale is chock-full of plot twists and gasp-out-loud revelations, but none more bewildering than the fact that Taika Waititi, who has never directed a Star Wars property previously, is somehow able to ease into the director’s chair for Redemption with all the graceful assurance of Dave Filoni, who at first glance would seem the natural choice to bring this series home to its epic (and thankfully, only temporary) conclusion. Waititi’s work here is surprisingly understated: you’d be hard-pressed to find any clues that this episode comes from the mind that brought you crazy, colorful comedies like Thor: Ragnarok or Jojo Rabbit (though it is amusingly unsurprising that the finale stars Waititi’s own character, assassin turned nurse droid IG-11, in a particularly prominent role). Obviously, directing a single good episode of TV doesn’t warrant immediately getting a three-picture deal with Lucasfilm, but hey, why not give Waititi a shot at his very own Star Wars trilogy?
Another surprise that boggled my mind, at least, was that Mandalorians are cool – for what I feel is the first time, despite everyone else in the world idolizing the very ground that Boba Fett walks upon. And one of the coolest things about them (apart from jetpacks and flamethrowers) is that they’re not a specific race of people, as Cara Dune (Gina Carano) reveals during an emotional moment in the episode: they’re a creed. Not only does it reinforce a particularly Rian Johnson theme in Disney’s Star Wars, that anyone can be a Mandalorian without having to have been born one, but it also makes the Mandalorians seem a lot more noble – in an extended flashback sequence which haunts our protagonist’s mind, we witness a squad of the flying, armored warriors acting as human shields for wounded refugees trying to escape from brutal droid-warfare: and it is revealed that during this battle, a young orphaned boy named Din Djarin was rescued by these Mandalorians and taken to safety with them – that boy was our very own “Mando”, whom I guess we can finally call Din Djarin? We’ve actually known that name for a while (Pedro Pascal ever-so-slightly spoiled it last month), but it’s only now canon, meaning I can only now use it. Yes, the Mandalorians are still vaguely cultish, and more than a little creepy, but at least they’re not solely defined by characters like Jango and Boba Fett anymore, or even just the term of “bounty hunter”. Djarin’s other biggest secret, his face, was also finally revealed in this episode…and, well, it’s Pedro Pascal’s face. I’m not entirely sure what we were all expecting, but honestly, that reveal was a bit underwhelming. It’s not like his face was even altered in any way: he didn’t have any scars or third-degree burns to speak of, no missing eyes or other distinguishing facial features. Not even a different hair color.
Djarin’s secrets weren’t the only ones brought to light: IG-11 is revealed to have been entirely reformed by Kuiil’s repairs, riding in to rescue Baby Yoda from a couple of monstrous stormtroopers who amuse themselves by punching and mocking the adorable little infant – the droid then straps The Child into a baby-backpack and goes on a killing spree around Nevarro, mowing down stormtroopers. He later sacrifices himself to rescue the whole team, self-destructing and blowing an entire legion of enemies sky-high. Baby Yoda himself is given his own hero moment when he faces down a flamethrower-wielding stormtrooper and deflects the attacker’s fire back at him: there’s a couple more reveals about his character, but I need to address those separately. Then there’s Cara Dune, whose home planet is revealed to be Alderaan (Princess Leia’s planet, infamously blown to pieces by the Death Star in A New Hope), thus explaining her undying grudge against the Empire. Greef Karga (Carl Weathers) turns out to have been an ex-Imperial himself, though that big secret falls a little flat due to the fact that we barely even know Karga, and have always been on-the-fence about whether or not to trust him and his Bounty Hunters Guild, anyway.
The person doing a lot of this dramatic-revealing is none other than Moff Gideon (Giancarlo Esposito), who is being set up to be the series’ big bad, and Din Djarin’s arch-nemesis. Gideon toys with his victims as they shelter in the burnt-out rubble of Werner Herzog’s lair, spilling their secrets to the world and promising them tantalizingly good deals if they’ll only hand over Baby Yoda. We never do find out what Gideon or Herzog wanted with The Child (and, come to think of it, we never even found out Herzog’s character name or purpose in the story, before he was unceremoniously murdered in the assault on his hideout), but considering how despicably evil Gideon is revealed to be, I’m going to assume it’s not because either of them just wanted cuddles and hugs. Gideon is also shown to have an alarmingly dangerous arsenal: not only can his tiny little handgun pierce through beskar steel, but the Moff is also a trained TIE-fighter pilot capable of handling his own in a dogfight. Oh yeah, and he just so happens to be in possession of the one black lightsaber in the entire galaxy, no biggie.
The lightsaber in question, better known as the Darksaber, has never been seen in live-action before this day, though it was seen in the animated series, Star Wars Rebels, which gave us a couple clues about the saber’s history. It was crafted by Tarre Vizsla, the first Mandalorian Jedi, during the reign of the Old Republic, and has since meandered across the universe, through the hands of a number of notable peoples and individuals, including the belligerent Mandalorian Clan Vizsla (to whose ranks Din Djarin appears to belong), the legendary Sith Lord Darth Maul, and Nite Owls leader Bo-Katan, who was the last known person to wield the blade, almost a decade before we seen Moff Gideon crawl from the wreckage of his TIE-fighter with the weapon in hand. The Darksaber is something of a mystical item, bestowing upon its wielder the title of Mand’alor, or leader of the Mandalorians – Gideon certainly has a fascination with the religious order, having been personally involved with eradicating them during the Great Purge and keeping tabs on those who survived. And now that he’s back on his feet, we can safely assume Din Djarin and Baby Yoda won’t be safe from his murderous rage anytime soon.
But for the moment, Din has a more urgent problem to worry about: while visiting his old friend The Armorer (Emily Swallow), he was gifted a number of odds-and-ends, including his very own jetpack, a personal sigil, and custody over Baby Yoda – which, apparently, is something that The Armorer can just hand out to anybody she feels like. But there’s a catch: while she tells Djarin to protect and train the baby (and even bestows upon them a title, the “Clan of Two”, which seems to hint at Star Wars’ common theme of duality), she also instructs him to seek out the child’s people – it’s not clearly indicated whether she’s referring specifically to Baby Yoda’s birth-family, or the Jedi in general, but it’s obvious that this will be a central plot-point in the series’ second season. But honestly, as much as we all want to see a whole planet of Baby Yodas, I think I’m just as excited to see The Child training as a Mandalorian – just so long as Din Djarin doesn’t try to make him wear a ridiculous helmet of his own: Baby Yoda’s adorable, expressive little puppet-face will not be hidden from the world, not if I and the internet have anything to say about the matter.
For the record, I think there’s a decent chance that we do actually see the home-planet of The Child’s species in The Mandalorian, and that the Jedi sage Yaddle will be revealed to be his mother. I know, I know, Yaddle is presumed dead – but there’s never been any conclusive evidence that that is the case, and honestly, she deserves so much more recognition than she gets. You know what, I’m just gonna say it: I think Yaddle is a better character than Yoda. Come at me, Yoda stans!
We’ve been left with a number of pressing questions from the season finale, but a bunch of mysteries have also been resolved, and we’ve left Din Djarin and Baby Yoda in a good place, all things considered. What did you think of the finale? Are you excited for Season 2? Share your thoughts and theories in the comments below!
Minor SPOILERS For Star Wars: The Rise Of Skywalker Ahead!
First up, an apology: in my Star Wars: The Rise Of Skywalker Spoiler Review, I made the fictitious claim that a couple depicted kissing near the end of the movie was a lesbian couple. There is, in fact, no clear indication of the sexual orientations of either Commander Larma D’Acy or her partner – they could be lesbian, but there’s also nothing to suggest they aren’t pansexual, bisexual, or a different sexual orientation entirely. And that is part of the problem with Star Wars‘ small, misguided attempt at LGBTQ+ representation.
And it’s not like there wasn’t room in the story for that representation to emerge in a natural, organic method. Fans have long sensed an undercurrent of semi-romantic tension between Star Wars leads Finn (played by John Boyega) and Poe Dameron (Oscar Isaac), and even the actors themselves have made it pretty clear that they would have had no problems if the story had headed in that direction. Boyega himself has been a bit back-and-forth on the subject, and has made friendly jokes about the pairing, while also suggesting that he doesn’t “know how that would work”. But nobody has been onboard with the popular coupling like Oscar Isaac, who has been the unofficial voice of the LGBTQ+ Star Wars fanbase for years: at first, his support seemed like the typical sort of vague hand-waving, with comments like “Poe’s open to any kind of adventure”, but starting this year, the actor has been avidly on the side of Finnpoe fans: “I think he takes his love for Finn very seriously”, Isaac said of his character at Star Wars: Celebration. Since then, he’s noted that a gay romance between the two would be “a great way for the story to go”, admitted that “if they would’ve been boyfriends, that would have been fun”, and just yesterday confessed that, though he tried to advocate behind-the-scenes for a love story between the two men, “Disney overlords were not ready to do that”. Isaac’s strong approval is encouraging, but unfortunately, he’s only an actor and can’t really do much to influence the film’s scripts.
And yet, Rise Of Skywalker director J.J. Abrams himself has revealed that the diversity of Star Wars‘ ensemble cast is supposedly very important to him, and that he felt it necessary that it be increased in the franchise’s final chapter. “And in the case of the LGBTQ community,” he noted, “it was important to me that people who go to see this movie feel that they’re being represented in the film”. When pressed on the issue, Abrams commented with vague assurance that “I did just say what I just said”.
Abrams’ comments should sound eerily (auto-correct suggested wearily, which also works) familiar to fans who may remember Avengers: Endgame directors Joe and Anthony Russo saying virtually the same thing about the LGBTQ+ representation in their blockbuster hit back in April: “It was important to us as we did four of these films, we wanted a gay character somewhere in them…it is a perfect time, because one of the things that is compelling about the Marvel Universe moving forward is its focus on diversity”.
The similarities don’t stop there, though, because when it comes down to it, the LGBTQ+ representation in both films is also strangely identical. In Endgame, a minor, unnamed character played by Joe Russo himself, mentions dating another man in a throwaway line: this character has no purpose in the story, nor any significance beyond being gay, and is only shown this one time – the fact that he’s played by Joe Russo also makes the moment into a surprising cameo, distracting attention from the significance of his words. In Star Wars, the crucial representation is even less noticeable, though technically more significant: here, Commander Larma D’Acy, a minor character portrayed by Amanda Lawrence, is shown kissing another woman in an exceedingly brief moment – due to taking place in a crowd shot, during an emotional scene, you could easily watch the film without even noticing that you had just witnessed LGBTQ+ history. And I’m left wondering…was that the point?
A same-sex kiss of any kind is a strikingly powerful statement in a big franchise film such as this one, but Disney’s use of the kiss feels cheap, as if it’s reducing what should be important into a meaningless moment that, on the surface, looks like great representation. The audience has no emotional attachment to D’Acy and especially not to her girlfriend, who isn’t even named in the film (the newest Star Wars Visual Dictionary apparently does give her a name: Wrobbie Tryce). They have no reason to care about these two women or their two-second long relationship – and since the characters are so minor, and so deliberately overshadowed by other, more important characters, audiences don’t even have any good reason to notice them or their kiss. If it had been Finn and Poe kissing, even if only for two seconds or one, you would notice because it’s Finn and Poe: they’re lead characters, and the audience is familiar with them. Two extras somewhere in a crowd shot? Not so much.
Disney has just proven that simply including a gay kiss isn’t enough to constitute meaningful representation. People around the world have been rightfully outraged, since the film’s release, that this moment was what Abrams was referring to when he claimed that LGBTQ+ representation was one of his priorities when making The Rise Of Skywalker.
And here’s the thing: Abrams didn’t need to put LGBTQ+ representation into the film at all. As far as we know, this was his decision: nobody was forcing him to do it. And that should be applauded, because it is a step forward. What shouldn’t be applauded is the fact that Abrams, knowing full well just how brief and insignificant the kiss was, went around claiming that the two-second snippet of footage could or would make up for all of the lost opportunities with the Finnpoe relationship, or even amount to anything more than what it was – a two-second snippet of footage. Why not just admit upfront that there would be a small nod to the LGBTQ+ community, without stirring up more controversy and trouble for himself?
Because this is queer-baiting 101. Queer-baiting refers to the process of luring LGBTQ+ audiences to consume a product, be it a movie, TV show, book, etc, with the promise or hint of LGBTQ+ representation, only to reveal that there was little to no representation to begin with. Endgame was heavily criticized for queer-baiting, prompting the Russo Brothers to respond with the claim, as yet unverified, that more major Marvel characters will come out as LGBTQ+ in future movies. 2017’s Beauty And The Beast faced queer-baiting critiques after an “exclusively gay” scene hyped up in the film’s pre-release marketing turned out to be a single shot of two male characters dancing. Fantastic Beasts: The Crimes Of Grindelwald was one of those especially awful cases where a director actually tells the truth and goes on record to say that a character will not be depicted as LGBTQ+ in his movie, only to have his working partner release a tweet disputing that claim – the latter being J.K. Rowling, who apparently didn’t realize she was lying, or simply didn’t care: the promised LGBTQ+ representation in that case actually referred to a single line of dialogue with only slightly gay connotations.
And now Star Wars faces those same complaints, for good reason. By promising something he couldn’t deliver, Abrams dug himself into his own grave. He wasn’t obliged to make any statement at all, but he did – and now he’s paying the price, as audiences riot against the director.
What could he have done to rectify the situation? Well, the easiest solution would have been to make D’Acy and her partner more prominent in the film. If that would have taken time away from the main cast, then why not have it be one of the main cast who turns out to be gay? Finn and Poe are literally right there. But if neither option was viable, then Abrams should simply have kept his mouth shut and not said anything at all. His idea of representation is outdated and honestly offensive, making it an unnecessarily problematic element in a movie that already has plenty of those.
I really don’t want to make a scene, and we know Larma D’Acy wouldn’t want me to (that’s her only significant line in two movies: you thought I wasn’t going to use it in some way?): I wish I could simply talk about how nobody, no matter how far away their galaxy is, should have to live with a name with Wrobbie – or Larma, for that matter. But I can’t stay silent when directors and filmmakers continue to shamelessly bait and trap LGBTQ+ audiences, taking their money in exchange for empty, unfulfilled promises. Hollywood is making progress, or at least, I hope that they are: Disney is making a big deal out of having their first openly gay character in next year’s Jungle Cruise (though the fact that the character is played by a straight comedian and described by test audiences as “hugely effete” isn’t exactly encouraging), and Marvel has promised their first gay character in The Eternals – rumored to be the demigod Phastos, a happily married man with children. But until these claims are backed up by hard facts (i.e. the films themselves), be wary of could be just another queer-baiting incident.
For now, let’s just take a moment to acknowledge that, no matter how briefly their relationship may be depicted onscreen, Larma D’Acy and Wrobbie Tryce are, canonically, Star Wars‘ very first same-sex couple, and the two characters deserve a little more respect and congratulatory praise than they received from J.J. Abrams. Hopefully they’ll be joined in the near future by a number of other LGBTQ+ characters: ones who aren’t betrayed by their own creators.