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. Properly named CC-2224, Commander Cody first appeared onscreen in Revenge of the Sith, after which the TV show Star Wars: The Clone Wars would go on to cover some of his history in the war. Throughout the titular Clone Wars, Cody often served with Jedi General Obi-Wan Kenobi, building the respect that can be seen between the two in Revenge of the Sith.
As shown in Revenge of the Sith, Cody and Kenobi were engaged in a mission to capture General Grievous on Utapau. However, when Palpatine announced Order 66, Cody immediately began moving his forces against Obi-Wan Kenobi. As Palpatine transitioned the Galactic Republic into the Galactic Empire Cody remained somewhat loyal. Although, recent insights into Cody’s life after Order 66 from Star Wars: The Bad Batch say otherwise. That being said, here’s the full story of everything that happened to Commander Cody after The Clone Wars.
Cody's Fate Is One Of Star Wars' Most Unfair Endings![]()
In serving the Empire after the Jedi were eliminated, Commander Cody was one of the last waves of clones to see action. Almost as soon as the Empire declared victory against the Trade Federation, the Imperial Army discontinued the Kaminoan program and from then on recruited conscripts for Stormtroopers. While some groups of clones, including Cody's 212th Legion, would be kept together, many of the final clone generations were dispersed among Imperial territory to make room for the new human recruits filling the ranks.
The transition from clone troopers to stormtroopers was swift, and by Solo: A Star Wars Story, a mere 6 years after Episode III, they'd been all but phased out. Even as their practical impact declined, however, 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, the clone's legacy lives on for better or worse.
Vague veneration as war heroes for propaganda wasn't enough to protect most clones from a bleak fate though, as demonstrated by Temuera Morrison's homeless clone veteran cameo in Obi-Wan Kenobi. Fortunately, Cody managed to avoid becoming a persona non grata in the eyes of the Empire, but his story is still one of the most unfair character arcs in Star Wars. Commander Cody was uncommonly skilled as a combatant and tactician, but ultimately he was still susceptible to the programming impressed upon him since birth.
Many feel that Star Wars should have found a narrative way to work around Commander Cody and Star Wars' Order 66, similar to Clone Force 99 in The Bad Batch. Cody was a hero of The Clone Wars series, and ending as just another lackey for the Empire felts like an unfitting finale for him. 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, Cody 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 Revenge of the Sith.
Commander Cody's Story Continues In The Bad Batch Season 2![]()
Lucasfilm considered giving Commander Cody a cameo in Obi-Wan Kenobi, although the studio ultimately decided otherwise. Instead, he appeared in Star Wars: The Bad Batch season 2, still working for the Empire - but questioning their decisions. He was seen in Star Wars: The Bad Batch season 2, episode 3, which saw him work with the only member of Clone Force 99 to remain with the Empire, Crosshair. Cody led a mission to a former Separatist planet called Desix to recover a captured Imperial governor by the name of Grotton. Cody, Crosshair, and their men attacked the facility, successfully reaching Grotton and Desix's governor Tawni Ames.
Code attempted to peacefully resolve the situation, insisting the Empire strives for peace and order, but his faith in the new regime was shaken when Grotton insisted Ames be executed - even after she had surrendered. This was made all the worst by the revelation Amex and her ally, Mina Bonteri, had submitted peace terms between the Republic and the Separatists during the Clone Wars - with Chancellor Palpatine declining to acknowledge them. Cody refused to execute Ames, but Crosshair chose to do so - not yet ready to refuse the Empire.
This led to the biggest change in Cody's character since Revenge of the Sith. Upon returning to Coruscant, Cody talked to Crosshair about whether the Empire really is making a change for better throughout the galaxy. Crosshair insisted they were soldiers, following orders and doing what needs to be done. Cody, however, noted their ability to question and make choices is what makes them different from droids - and that they must also live with the consequences of their actions. The dialogue seemed to hint at his discomfort with these consequences, his reflected on Order 66. The episode revealed Cody deserted the Empire shortly after this.
[圖擷取自網路，如有疑問請私訊]
As shown in Revenge of the Sith, Cody and Kenobi were engaged in a mission to capture General Grievous on Utapau. However, when Palpatine announced Order 66, Cody immediately began moving his forces against Obi-Wan Kenobi. As Palpatine transitioned the Galactic Republic into the Galactic Empire Cody remained somewhat loyal. Although, recent insights into Cody’s life after Order 66 from Star Wars: The Bad Batch say otherwise. That being said, here’s the full story of everything that happened to Commander Cody after The Clone Wars.
Cody's Fate Is One Of Star Wars' Most Unfair Endings
In serving the Empire after the Jedi were eliminated, Commander Cody was one of the last waves of clones to see action. Almost as soon as the Empire declared victory against the Trade Federation, the Imperial Army discontinued the Kaminoan program and from then on recruited conscripts for Stormtroopers. While some groups of clones, including Cody's 212th Legion, would be kept together, many of the final clone generations were dispersed among Imperial territory to make room for the new human recruits filling the ranks. The transition from clone troopers to stormtroopers was swift, and by Solo: A Star Wars Story, a mere 6 years after Episode III, they'd been all but phased out. Even as their practical impact declined, however, 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, the clone's legacy lives on for better or worse.
Vague veneration as war heroes for propaganda wasn't enough to protect most clones from a bleak fate though, as demonstrated by Temuera Morrison's homeless clone veteran cameo in Obi-Wan Kenobi. Fortunately, Cody managed to avoid becoming a persona non grata in the eyes of the Empire, but his story is still one of the most unfair character arcs in Star Wars. Commander Cody was uncommonly skilled as a combatant and tactician, but ultimately he was still susceptible to the programming impressed upon him since birth.
Many feel that Star Wars should have found a narrative way to work around Commander Cody and Star Wars' Order 66, similar to Clone Force 99 in The Bad Batch. Cody was a hero of The Clone Wars series, and ending as just another lackey for the Empire felts like an unfitting finale for him. 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, Cody 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 Revenge of the Sith.
Commander Cody's Story Continues In The Bad Batch Season 2
Lucasfilm considered giving Commander Cody a cameo in Obi-Wan Kenobi, although the studio ultimately decided otherwise. Instead, he appeared in Star Wars: The Bad Batch season 2, still working for the Empire - but questioning their decisions. He was seen in Star Wars: The Bad Batch season 2, episode 3, which saw him work with the only member of Clone Force 99 to remain with the Empire, Crosshair. Cody led a mission to a former Separatist planet called Desix to recover a captured Imperial governor by the name of Grotton. Cody, Crosshair, and their men attacked the facility, successfully reaching Grotton and Desix's governor Tawni Ames. Code attempted to peacefully resolve the situation, insisting the Empire strives for peace and order, but his faith in the new regime was shaken when Grotton insisted Ames be executed - even after she had surrendered. This was made all the worst by the revelation Amex and her ally, Mina Bonteri, had submitted peace terms between the Republic and the Separatists during the Clone Wars - with Chancellor Palpatine declining to acknowledge them. Cody refused to execute Ames, but Crosshair chose to do so - not yet ready to refuse the Empire.
This led to the biggest change in Cody's character since Revenge of the Sith. Upon returning to Coruscant, Cody talked to Crosshair about whether the Empire really is making a change for better throughout the galaxy. Crosshair insisted they were soldiers, following orders and doing what needs to be done. Cody, however, noted their ability to question and make choices is what makes them different from droids - and that they must also live with the consequences of their actions. The dialogue seemed to hint at his discomfort with these consequences, his reflected on Order 66. The episode revealed Cody deserted the Empire shortly after this.
[圖擷取自網路，如有疑問請私訊]
|
本篇 |
不想錯過? 請追蹤FB專頁! |
 | 喜歡這篇嗎？快分享吧！ |
相關文章
tag_starwar
