STAR WARS Producer Finally Answers Why Obi-Wan Kenobi Didn't Kill Anakin Skywalker On Mustafar

STAR WARS Producer Finally Answers Why Obi-Wan Kenobi Didn't Kill Anakin Skywalker On Mustafar

Fans have long wondered why Obi-Wan Kenobi didn't make sure Anakin Skywalker was dead following their clash on Mustafar in Revenge of the Sith, and a longtime Star Wars franchise producer has weighed in...

By JoshWilding - Feb 16, 2024 11:02 AM EST
Filed Under: Star Wars
Source: Empire Online

When George Lucas set out to make Star Wars, he didn't have some grand nine-movie plan. A New Hope went through countless iterations, as did The Empire Strikes Back and Return of the Jedi; by the time the prequels rolled around, that story was told, and Lucas had to figure out how to tell what came before them. 

There were continuity issues, but for the most part, The Phantom Menace, Attack of the Clones, and Revenge of the Sith effectively sit alongside the original trilogy. 

The biggest challenge for the filmmaker was taking Anakin Skywalker from the likeable young boy we met on Tatooine to the despicable Sith Lord, Darth Vader. That transformation didn't happen until Episode III's closing moment; however, fans have long blamed Obi-Wan Kenobi for the horrors later inflicted by Vader on the Galaxy because he failed to make sure his former Padawan was dead. 

During their lightsaber duel on Mustafar, Kenobi cut off Anakin's arm and legs, leaving him to burn. Emperor Palpatine arrived just in time to save his new apprentice, using the Empire's technology to create more-machine-than-man Darth Vader. 

Talking to Empire, longtime Star Wars franchise producer Rick McCallum shared his take on why Obi-Wan left Anakin behind without delivering a definitive killing blow.

"I also think he doesn't believe Anakin will recover - he thinks he's going to die," he explains. "It's only because Palpatine comes in and uses everything to save him and create this freak [that he survives]."

Elsewhere in the magazine's feature, Hayden Christensen reflected on being cast as Anakin and admitted he didn't expect to ever land the coveted role.

"I was 18, and I got a call from my agent saying that they were casting for Anakin Skywalker in Star Wars and I thought, 'Wow, how cool.' But it just seemed too big," the actor recalls. "And I remember asking my agent, 'Is there maybe another role that they're also casting right now that you can put me up for? Because Anakin sort of seems unattainable.' And there was not. So I threw my name in the hat like everyone else."

In recent years, we've seen Christensen return to the role of Anakin/Vader in both Obi-Wan Kenobi and Ahsoka. The former explored the emotional and mental toll that the fight on Mustafar had on "Ben," later reuniting the friends-turned-enemies for a confrontation which addressed the apparent plot holes Lucas created. 

Let us know your thoughts on these remarks in the comments section below.

STAR WARS: New Hot Toys Figure Delivers An Epic Take On A Battle-Damaged Darth Vader
Related:

STAR WARS: New Hot Toys Figure Delivers An Epic Take On A Battle-Damaged Darth Vader

THE ACOLYTE Showrunner Talks Possible Season 2 And Reveals Plans For Darth [SPOILER] And More
Recommended For You:

THE ACOLYTE Showrunner Talks Possible Season 2 And Reveals Plans For Darth [SPOILER] And More

DISCLAIMER: SFFGazette.com is protected under the DMCA (Digital Millenium Copyright Act) and... [MORE]

SFFGazette.com, and/or the user who contributed this post, may earn commissions or revenue through clicks or purchases made through any third-party links contained within the content above.

Be the first to comment and get the conversation going!

Please log in to post comments.

Don't have an account?
Please Register.

View Recorder