Before writing my previous post – Talkerverse: Vader Kills Maul – my intention had been to write this post. Wanting to discuss (spoiler!) Darth Maul’s incredibly brief cameo in Solo: A Star Wars Story, I sat down to write but my brain had other intentions. Acquiescing to my train of thought, I ran with my imagination and wrote about how I think Vader should have killed Darth Maul in Revenge of the Sith. You can go read all about that (click HERE) but for now let’s chat about that surprising Solo cameo…
Soooooo, yeah, Darth Maul makes an appearance in Solo: A Star Wars Story. How about that? I dunno about you, but I DID NOT see that coming. As I watched the film, and it started to become clear that the film’s antagonist, Dryden Vos, was working on behalf of some shadowy figure, I was thinking it would end up being Snoke. Even up to the moment of Maul’s reveal, when he is contacted by Han Solo’s childhood friend Qi’ra, I believed we would be met by the face of the one-day First Order Supreme Leader. Never-the-less, seeing Darth Maul – and actor Ray Park reprising the character he brought to life in The Phantom Menace – definitely caught me off-guard.
As a die-hard Star Wars fan who has kept up with Star Wars stories across all mediums, it made complete sense that Darth Maul was the shadowy figure who instilled fear in the criminal Dryden Vos. After all, The Clone Wars animated show resurrected Maul from his bifurcated death and elevated him to the status of underworld crime lord. In The Clone Wars, as many of you may know (but some may not), Darth Maul unified a coalition of terrorists and criminal organizations under his authority, in turn using his nefarious organization to take control of the planet Mandalore. Maul’s actions – with the assistance of his brother Savage Oppress – launched him into galactic relevance, making it necessary for the Jedi, and his former Sith Master (Darth Sidious), to take him seriously as a threat. Following The Clone Wars, the four-part Son of Dathomir comic continued his Clone Wars era story-arc, while E.K. Johnston’s Ahsoka novel showed that Maul’s grip on the planet Mandalore was strong even at the wars end. As well, Maul once again re-emerged in Star Wars Rebels, a menace to the Lothal rebels with his life finally coming to end on Tatooine when he confronts, and is killed by, Obi-Wan Kenobi.
While I was surprised to actually see Maul onscreen, I was otherwise unsurprised he was the “phantom menace” directing the actions of Dryden Vos. Having kept up-to-date with Maul’s story-arc, and knowing his criminal dealings, it really made complete sense. That being said, following my first viewing of Solo, I could not help but ask myself: for someone who is more of a casual Star Wars fan, who is only interested in the movies, were they surprised, or perhaps even confused, to see Maul? After all, for those individuals, their experience of Darth Maul would have begun and ended with his introduction and death in The Phantom Menace.
Luckily, I was able to ask two of those “movie-only” Star Wars fans, my neighbors, when I got home from my first viewing of Solo. As I stood outside chatting with them, I asked for their thoughts and they acknowledged that they left the movie theater feeling confused by Maul’s appearance. As I explained that the Sith Lord was resurrected in The Clone Wars, and noted that his story has continued beyond that, one of my neighbors (Sara) said something which caught me off-guard: that she is less likely to watch Star Wars movies in the future if the story is just going to be changed in tv shows, books, and comics.
While her feelings are specific to her experience, I could certainly, sympathize and understand what she was saying. While I really like Darth Maul’s post-resurrection storyline (…with the exception of his demise in Star Wars Rebels…) I can also admit that I was incredibly annoyed by his resurrection in The Clone Wars. Even though Darth Maul is only in a small amount of The Phantom Menace he was never-the-less an exceedingly important part of the story. We knew, in the film, that Maul was serving Darth Sidious, executing the machinations of his Master. While Sidious had to stay behind the scenes – he is “the phantom menace” – Darth Maul revealed himself to the Jedi as a threat they were clearly unprepared to face. And, when he is sliced-in-half by a young Obi-Wan Kenobi – making it pretty damn obvious that Maul was killed – the Jedi are left to wonder: which Sith Lord died, the Master or the Apprentice?
As it turns out, neither died.
While I have since grown to appreciate Darth Maul’s post-resurrection arc, and definitely understand his cameo in Solo: A Star Wars Story – knowing as I do all the nuances and baggage that goes with it – I can also understand and appreciate why my neighbor felt confused and unhappy. For her, and certainly for many others, the Star Wars films represent the pinnacle of Star Wars. For them, the movies, and only the movies, are what matter. Period. Full stop. They are uninterested in TV shows, comic books, novels, video games, precisely because Star Wars is a series of films. And, as a result, suddenly seeing a character you thought was dead – without any explanation what-so-ever regarding how he survived being cut in half – is undoubtedly annoying and off-putting. Which leads me to this:
I really believe that cameo should have been Snoke, not Darth Maul. The connections that could have been made between Solo and the Sequel Trilogy with a small cameo by Snoke would have been incredibly profound and forward-thinking, while simultaneously ensuring that movie-only fans like my neighbors were not left scratching their heads. But I will hold off on offering my “Snokey” thoughts in any greater detail for now, and you can just wait for my future post on the topic – Talkerverse: Snoke Goes Solo.
Leave a comment and tell me what you think about Darth Maul, his story-arc, and his cameo in Solo: A Star Wars Story. AND, be sure to check out all of my other Darth Maul posts (just put his name into the search bar).