Fandom

Wookieepedia

Raid on the Almas Sith fortress

134,662pages on
this wiki
Add New Page
Talk0 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.

Circa 20 BBY,[2] during the time of the Clone Wars, the Chevin slaver Phylus Mon led an incursion into the abandoned Sith fortress on the planet Almas. Mon sought to both recover the secrets of the creation of Sith battlelords and to perform repairs to the Darkstaff, an ancient Sith artifact entrusted to his care by the criminal Len Markus, and accompanied by his Dark Jedi ally Karae Nalvas and several of his minions, Mon attacked six Jedi Knights who had been stationed to stand guard outside the fortress. The Chevin and his associates killed four of the Jedi, Tresten Agai'i, K'kur, Milak Sonloam and Vorlocca, and took the other two guardians—the Tarasin Constanten and the Skrilling Valiri—as captives. Mon then made his way into the depths of the fortress and recovered a tome that detailed the rituals through which battlelords could be created.[1]

AppearancesEdit

Notes and 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 A Mon Alone
  2. 2.0 2.1 The Living Force Campaign Guide states that the Living Force campaign is set one year after the Invasion of Naboo, an event that is dated to 32 BBY by The New Essential Chronology. As the Living Force adventure Philology moved the campaign forward ten years to the time of the Clone Wars, and the adventure Night's Homecoming established that by Year 4 of the campaign over a year had elapsed since the events of Philology, A Mon Alone can therefore be dated to circa 20 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.