The following contains spoilers from Star Wars: Darth Vader #27, on sale now from Marvel Comics.

In its basest sense, Star Wars' original trilogy is a heroic story. Luke Skywalker and the Rebel Alliance fought and defeated the evil Galactic Empire. In a way, that's true, but it's actually much deeper and more nuanced than that. Truthfully, the original trilogy is only the final chapter in the rise and fall of Darth Vader, and Vader's story is one of the most tragic in the Star Wars franchise.

As a child, Anakin Skywalker was full of hope and youthful optimism. That's when Qui-Gon Jinn found the boy on Tatooine and took him to become a Jedi. Yet, Palpatine found a way to corrupt Anakin and ruin his life; then he turned the hopeful youth into a callous Sith Lord. Set years after Anakin's fall to the Dark Side, Star Wars: Darth Vader #27 (by Greg Pak, Raffaele Ienco, Carlos Lopez, and VC's Joe Caramagna) is about to make Vader relive his greatest loss.

RELATED: How Star Wars Made an Annoying Return of the Jedi Plot Hole Even Worse

Darth Vader beats Crimson Dawn governor

Lately, the Darth Vader comic issue has been focused on the Crimson Dawn. After the chaos that the hunt for Han Solo caused, Palpatine tasked Vader with hunting down Crimson Dawn sympathizers. Over the past few issues, Vader has allied with Sabe and some of his childhood friends in order to take down a traitorous Governor Tauntaza. Even with his unmeasurable power, Vader has had trouble taking down the governor because of her life-draining weapon and an artificial sandstorm.

In Issue #27, however, Vader had enough. Using a droid to penetrate Tauntaza's shielded machine, Vader finally took her down. Except, the last few pages of the comic threw a wrench into everything. It was all a set-up with Palpatine calling the shots. He wanted to root out Sabe and prove that Vader was still soft for her (as a surrogate Padme). Knowing that Palpatine was using Sabe as a pawn in his game, there can only be a limited time before the former handmaiden gets what's coming to her.

RELATED: Star Wars Keeps Making Darth Vader's Deadliest Move Inconsistent

Vader and Sabe

In The Last Jedi, Kylo Ren infamously said, "Let the past die. Kill it if you have to." While it was kind of forced in that film, it's likely that Palpatine will apply the principle to Vader with grandiose effect. At the moment, Sabe is trying to turn Vader back to the Light Side, and Palpatine clearly doesn't like that. More so, Palpatine doesn't like that Vader is falling for it. Thus, all signs point to Palpatine getting rid of Sabe and doing it in a way that sends a message to Vader.

There seem to be two realistic options. First, Palpatine will kill Sabe in front of Vader. It would be terrible, but it would be par for the course for such an evil Sith. It would also be the perfect way for Palpatine to keep killing off Vader's past because seeing Sabe killed in front of him would be like seeing Padme killed. That would push Vader further down a dark path and help solidify him as an irredeemable Sith.

The other option is that Palpatine will make Vader kill Sabe to prove his loyalty. Seeing a version of Padme killed would be bad, but having to commit the action would be even worse for Vader. On top of that, Vader thought that he was responsible for killing Padme, so having to do it again by proxy would only add to his tragic story. Either way, it looks like Sabe is doomed and Palpatine will enjoy getting rid of her at Vader's expanse.