FANDOM


Cody (1)
"This article is fully operational."
―Doom's Unit

This article was a featured article on the Clone Trooper Wiki homepage.

Doom's Unit
Doom'sUnit
Information
Leader(s):
Notable member(s):
Location(s):
  • Ringo Vinda[1]
Main soldiers:

Clone troopers

Equipment:
Era(s):
Class1

This unit was under the command of clone commander Doom and Jedi generals Tiplar and Tiplee. They fought alongside the 501st Legion during the Battle of Ringo Vinda.[1]

HistoryEdit

In 20 BBY[2] the Republic battled the Separatists on a space station ring of the planet Ringo Vinda. Led by Jedi Generals Tiplar and Tiplee and Commander Doom, Doom's Unit advanced and fought alongside the 501st Legion. They battled in hallways against BX commando droids, with troopers blocking blaster bolts using blast shields while two troopers behind them blasted the droids using rotary cannons. However, as they defeated the commando droids, several destroyer droids approached.[1]

Tiplar and Tiplee ordered a shield wall, and five troopers formed an impenetrable barrier. After Tiplar pushed the destroyers back using the force, the troopers slipped droid poppers under the droidekas' shields, destroying them. They proceeded to battle to the communications center, where they met up with the 501st Legion and discussed a battle plan to destroy a Separatist command center. Tiplar and Tiplee would go on the sides, while Jedi General Anakin Skywalker would press through the middle. They would all meet up at the command center.[1]

They began phase two: capturing Separatist Admiral Trench, the droid forces' ground commander. As the clone troops pushed on for the conquest of Trench's command center, they battled dozens of squads of droids, with spider droids on crates, firing down at them. Tup, a trooper from the 501st Legion, fell into a trance in the heat of the battle. He walked up to general Tiplar, and shot her in the head.[1]

ARC trooper Fives jumped on Tup, restraining him. In the confusion, the Republic was distracted as destroyer droid and rocket droid reinforcements arrived. The clone forces retreated and pulled back from the command post. The troopers blasted droids as they continued through hallways back to their base, the communications room. A trooper from the 501st Legion set up an E-Web turret on auto-fire, and the troopers locked the blast doors, safely inside the center. They mourned the loss of Tiplar and questioned Tup for his actions.[1]

Notable MembersEdit

DoomIconDoomUnitIconDoomUnitIconDoomUnitIconDoomUnitIconDoomUnitIcon
DoomWeapons specialist 1Weapons specialist 2Clone trooper 1Clone trooper 2Clone trooper 3

Armor and EquipmentEdit

This unit was equipped with DC-15S blaster carbines as their weapons, and some troopers were equipped with Z-6 rotary cannons. They wore Phase II armor with yellow, green and gray markings. They also carried large blast shields as mobile cover, and occasionally used plasma welders to seal doors.[1]

Out-of-UniverseEdit

  • In The Unknown, Commander Doom states that his men are depleted, and that they need backup. Ironically, in the episode, no trooper from Doom's Unit is shown being hit; only the 501st Legion suffers casualties.[1]

AppearancesEdit

  • CW Star Wars: The Clone Wars – "The Unknown"
  • CW Star Wars: The Clone Wars – "Conspiracy" (Appears in flashback(s))

SourcesEdit

  • CW Star Wars: The Clone Wars – "The Unknown"
  • The Official Star Wars Fact File Part 52 (20 BBY 55–56, Battle of Ringo Vinda)

External LinksEdit

TimelineEdit

20 BBY[2]
Battle of Ringo Vinda[1]

ReferencesEdit

  1. 1.00 1.01 1.02 1.03 1.04 1.05 1.06 1.07 1.08 1.09 1.10 1.11 1.12 1.13 1.14 1.15 1.16 1.17 1.18 1.19 1.20 1.21 1.22 1.23 1.24 1.25 1.26 CW Star Wars: The Clone Wars – "The Unknown"
  2. 2.0 2.1 The Official Star Wars Fact File Part 52 (20 BBY 55–56, Battle of Ringo Vinda)

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.