FANDOM


Droidbait
Droidbait-TCWPromo
Biological Information
Species: Human (Clone)
Gender: Male
Biographic Information
Homeworld: Kamino
Occupation/Rank:
Affiliation:

Droidbait, designated as CT-00-2010, was a clone trooper who was in Domino Squad along with Hevy, Cutup, Echo, and Fives. He later participated in defending the Rishi Moon Outpost from General Grievous in his plan to destroy Kamino. When the BX-Series Droid Commandos came in to attack after they killed CT-327, Sergeant O'Niner sent Droidbait and Nub to see what was going on. Soon following, Droidbait and Nub were both killed by the invading Commando Droids.

History

"Guys, we have to follow orders, come on!"
"I don't know. I think it went rather well."
"Quit joking around."
"Can we please stop arguing?"
"Can you stop being droidbait out there? You're getting in my way!"
―Echo, Cutup, Fives, Droidbait, and Hevy arguing at the barracks[src]

Droidbait was one of the clone troopers who was in the Domino Squad during their practices and tests. He got his nickname, "Droidbait" from him always getting shot first in practice. During the test that would let them be clone troopers, Droidbait was shot and splintered his shoulder and only one trooper, Echo stopped to help him, but left afterward, which was an automatic failure for his team. After a complaint to General Shaak Ti, they were allowed to redo the final test and passed, even with no cables, which made them a special team. He was sent to the Rishi Post soon after.

Rookies

One day during his stationing at Rishi Post, the station was ambushed by a squad of Droid Commandos and were taken by surprise. The Droid Commandos quickly kill Nub and Droidbait. The station was later destroyed by Hevy, who sacrificed his life for his squad mates. Fives, and Echo were the only two clones that were originally at Rishi Post to survive.

Appearances

Ad blocker interference detected!


Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.