I doubt that, he most likely didn't speak for the dramatic value. If the backlash was the issue, they would have just got a sound alike. Either Scott Lawrence or Matt Sloan, those two are usually the go to for sound alikes.Vader doesn't speak. Perhaps because of the SAG-AFTRA backlash last year, regarding the recreated Vader voice in Fortnite
They always have.Wait, they have real-time FTL comms from within hyperspace?
While I understand that sentiment, I don't mind it. I'm watching for Maul himself and all of his machinations. I can go either way with the supporting cast.Well, I'm not so sure that I'm going to be in for season 2. Not that it wasn't good, but as I said up thread, I don't like watching stories where all the characters that I like and am rooting for get killed off (or corrupted). That's why I eventually stopped watching The Walking Dead and it's why I didn't finish that Darth Maul novel that I mentioned previously.
As for Vader not speaking, it really added to the horror movie vibe that this episode was going for.
Yeah, both of those explanations work. It doesn't stand out so much considering the Inquisitors rarely spoke, too, in contrast to Rebels.Given the amount of rage Maul would induce, I can believe one would be silent in the seething rage.
Yeah, that's a good question. Perhaps in the moment, Maul didn't figure it out because he was too taken aback by the sheer Force of Vader and he was too busy trying to save his own skin. I wouldn't be surprised if he figures it out later after some consideration.Also, if Maul was aware that Anakin was central to Palpatine's plans in the Siege of Mandalore are in Clone Wars , why would he not put it together that this is Skywalker here?
I'm finding every time there's a scene with Rook Kast I keep thinking of that fan theory that she eventually becomes the Armorer on The Mandalorian.
We use essential cookies to make this site work, and optional cookies to enhance your experience.