Fandom

Wookieepedia

Ooroo's homeworld

134,554pages on
this wiki
Add New Page
Talk2 Share
Queicon

The title of this article is conjectural.

Although this article is based on official information from the Star Wars Legends continuity, the actual name of this subject is pure conjecture.

"I wish I could have floated in the seas of my home, one last time..."
―Ooroo[src]

The Celegian Jedi Master Ooroo, who lived at the time of the Great Hyperspace War—a conflict between the Galactic Republic and the Sith Empire—referred to a world with seas on its surface as his home.[1] Ooroo, who was born sometime prior to the year 5000 BBY,[2] floated in those seas on several occasions during his life. During the Republic's battle against invading Sith armies on the planet of Kirrek in 5,000 BBY,[3] Ooroo sacrificed his life in order to defeat the enemy, and, as he lay dying on the battlefield, the Celegian expressed to Odan-Urr, his Draethos Jedi apprentice, his wish to float in the seas of his homeworld for a last time.[1]

Behind the scenesEdit

To date, Ooroo's homeworld has only been indirectly mentioned in the fourth issue of The Fall of the Sith Empire story arc of the Star Wars: Tales of the Jedi series of comic books. The issue was published on September 17, 1997 and was written by Kevin J. Anderson and penciled by Dario Carrasco, Jr.

AppearancesEdit

Notes and referencesEdit

  1. 1.0 1.1 1.2 Tales of the Jedi: The Fall of the Sith Empire 4: The Dogs of War
  2. According to the Star Wars: Tales of the Jedi comics, Ooroo was alive shortly before the end of the Unification Wars of the Koros system, which is dated by pp. 126-127 of The Essential Atlas to the year 5000 BBY. It can therefore be concluded that Ooroo was born sometime prior to this date.
  3. The Great Hyperspace War is dated by p. 127 of The Essential Atlas to the year 5000 BBY.

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.