Star Wars What Happened To Commander Cody After Executing Order 66

Star Wars: What Happened To Commander Cody After Executing Order 66

Commander Cody went on to serve the Galactic Empire for years after Palpatine’s Order 66 turned the clone troopers against the Jedi.



You Are Reading :Star Wars What Happened To Commander Cody After Executing Order 66

Star Wars What Happened To Commander Cody After Executing Order 66

When Emperor Palpatine initiated Order 66 in Star Wars: Episode III – Revenge of the Sith, Commander Cody was among the clone troopers that turned against their Jedi compatriots – but he survived long after betraying Obi-Wan Kenobi. An event first mentioned off-handedly in A New Hope, the Clone Wars was a conflict between the Galactic Republic and the Confederacy of Independent Systems that served as the backdrop to the TV series and film of the same name, as well as to Revenge of the Sith. The Republic’s forces were composed primarily of a large clone army grown by Kaminoan scientists from the genetic blueprint of bounty hunter Jango Fett. Although born identical for all practical purposes, some of these clones, Cody among them, were given additional training meant to qualify them for positions of greater power and responsibility.

Properly named CC-2224, Commander Cody first appeared on screen in Revenge of the Sith, after which The Clone Wars would go on to cover some of his history in the war. Throughout this time, Cody often served with Jedi General Obi-Wan Kenobi, building the respect that can be seen between the two in Revenge of the Sith. Together, they would lead the 212th Attack Battalion in several large-scale battles against the droid armies.

See also  Star Wars Looking for Leia Documentary Explores Women Fans

Engaged in a mission to capture General Grievous on Utapau when Palpatine announced Order 66, Cody nevertheless immediately began moving his forces against Obi-Wan Kenobi. Despite being good friends with the Jedi, Cody – like all clone soldiers – had an inhibitor chip implanted in his brain during his youth, making resistance to the Order impossible. His pursuit only ended when he was (erroneously) convinced that Kenobi had fallen to his death in one of the planet’s massive sinkholes. In the aftermath, as Palpatine transitioned the Galactic Republic into the Galactic Empire, Cody remained loyal to his government, adopting the new mantle of stormtrooper. In this capacity, he participated in many campaigns of the Imperial war machine, including the so-called pacification of Kashyyyk, wherein the planet of the Wookiees was completely subjugated.

In serving the Empire, Cody was one of the last waves of clones to see action, as the Imperial Army would transition to a system of recruitment and eventually discontinue the Kaminoan program altogether. While some groups of clones, including Cody’s 212th Legion, would be kept together, many of Cody’s generation would be gradually dispersed among Imperial territory as new human recruits filled the ranks. Even as their practical impact declined, the clones’ influence could still be felt in both the iconography of the stormtroopers and the mythologized legacy of the Grand Army of the Republic that greatly encouraged Imperial enlistment.

Commander Cody was uncommonly skilled as a combatant and tactician, but ultimately he was still susceptible to the programming impressed upon him since birth. Unlike fellow clone Rex, who assisted the Rebel Alliance in his later years after resisting his inhibitor chip, Cody’s legacy is complicated by the Empire that he was made to serve, especially in a campaign as oppressive as the pacification of Kashyyyk. However, he unarguably lived an impactful life to both extremes, so at the very least he should not be judged solely by the moment of coerced betrayal shown in Star Wars: Episode III – Revenge of the Sith.

See also  Star Wars Battlefront 3 Everything We Know So Far About The Rumored Game

Link Source : https://screenrant.com/star-wars-commander-cody-clone-after-order-66/



Leave a Reply

Your email address will not be published. Required fields are marked *