Chapter 16
Chapter Information
Season: 2
Episode No.: 6
Production Code: 116
Airdate: April 2, 2004
  • Unknown
Director: Genndy Tartakovsky

Chapter 16 is the sixth episode of Season Two of Star Wars: Clone Wars. It originally broadcasted on Cartoon Network on April 2, 2004.

Plot summary

Padmé Amidala and Captain Gregar Typho watch the Jedi ice cave with their electrobinoculars. Padmé and R2-D2 are concerned that Yoda has not returned, but Typho and C-3PO assure her that the Jedi Master will be fine. When Typho returns to the ship to check the communications array, Padmé heads off after Master Yoda, telling the two droids that they will accompany her. Artoo's sensors pick up multiple objects approaching, and the trio dive for cover as a barrage of laser fire blasts out of the blizzard. Padmé throws her cloak out as a decoy, and then fires her blaster, destroying the cloaked chameleon droid. However, Artoo says that there are two more. With this, she asks 3PO if he can get her coat but actually carelessly using him as a decoy. All of a sudden, the other two appear and open fire upon C-3PO, while Padmé uses a thermal detonator to destroy the remaining two droids.

Master Yoda appears out of the snowstorm with Luminara Unduli and Barriss Offee. The Jedi are safe, but the cave temple has been nearly destroyed. Master Yoda wonders how the temple's location was known. Artoo patches into one of the chameleon droids, and provides the answer, Count Dooku.



Droid Models





  • This episode contains a variation on the Lawrence of Arabia musical theme. It can be heard when Yoda, along with Barriss Offee and Luminara Unduli, emerge out of the snow on the horizon.
  • The appearance of the J-type 327 Nubian royal starship is a blooper, as the ship was intended to be a H-type Nubian yacht, which is seen in the two previous episodes.

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.