Takeover of Mandalore


Mission to Oba Diah

Invasion of Oba Diah

Clone Wars[1]


20 BBY[1]


c. 20 BBY[1]


Oba Diah[1]

Major battles




During the Clone Wars, in 20 BBY, the Confederacy of Independent Systems backed the Techno Union and Trade Federation to invade the planet of Oba Diah to take over the Pyke Syndicate. Following several attacks on the capital city of Pykala, including a bombing on the Pyke's spice refinery, the Crime Collective came together to negotiate an alliance with the Galactic Republic, which would allow the Republic safe passage to the rest of the Collective's territories and access to their weapons, in exchange for the Republic's assistance.


The invasionEdit


After the invasion, the Pykes were on the verge from bankruptcy due to the attacks on their spices refineries; however, the Collective came together to put their efforts in the reconstruction of the Spice Cartel. Some weeks after the invasion, the Jedi Order traveled to Oba Diah after finding the lightsaber of Jedi Master Sifo-Dyas on the planet's moon.[2] However, following the Jedi's arrival and a deal being struck between the Jedi and the Pykes, Count Dooku arrived to "eliminate loose-ends," killing aide Silman and Prime Minister Lom in the resultant skirmish.[2] Dekul Pyke succeeded Lom as the head of the Pyke family, the Prime Minister of Oba Diah, and the Syndicate's representative in the Crime Collective.[3]

Also, following the capture of Nute Gunray, the Neimoidian Viceroy escaped Republic custody.[4]


Notes and referencesEdit

  1. 1.0 1.1 1.2 1.3 Hutts: Age of Syndication
  2. 2.0 2.1 TCW mini logo Star Wars: The Clone Wars – "The Lost One"
  3. TCW mini logo Star Wars: The Clone Wars – "Criminal"
  4. It can be said that Gunray escaped their custody as he is seen in the Revenge of the Sith on Utapau.

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.