Star Wars: 5 times the Jedi messed up and doomed the galaxy

Star Wars: Episode 2 - Attack of the Clones (2002). Lucasfilm Entertainment Company Ltd., All Rights Reserved
Star Wars: Episode 2 - Attack of the Clones (2002). Lucasfilm Entertainment Company Ltd., All Rights Reserved /
facebooktwitterreddit
Prev
2 of 6
Next
Star Wars
Star Wars /

Star Wars: Episode 2 – Attack of the Clones (2002). Lucasfilm Entertainment Company Ltd., All Rights ReservedAnakin’s First Solo Mission

We can’t lay this one entirely at the feet of the Jedi Council. I’m going to go ahead and give them a partial pass here. How were they supposed to know Anakin was marinating for 10 years in his extreme sweaty horniness for the senator from Naboo?

But Obi-Wan? He botched it.

He literally called Anakin out in an elevator for being insanely sweaty. Obi-Wan had first-hand knowledge of how missions with a love interest complicate matters. If Obi-Wan was willing to leave the Jedi order for Satine, what did he think would happen if his padawan, who couldn’t control his emotions, let alone the Force, was sent on an all-inclusive paradise retreat with Padme?

I know Obi-Wan was against Anakin’s solo mission from the start but he could have tried a little harder to stop what he already knew was a bad idea. He called him arrogant and immature, which is true, but he left out the tiny detail— his apprentice literally couldn’t keep himself from saying the most absurd cringe pickup lines or turning into a human sprinkler when in the same area code as the senator.

Also when Anakin’s unsupervised, he also tends to have, um, genocidal tendencies.  Look, I’m not saying Anakin’s first solo mission on Naboo was the cause of the death of democracy, the rise of fascism, and plunging the galaxy into darkness for the next 20 years. But it didn’t help.