Fandom

Wookieepedia

Khypes

135,441pages on
this wiki
Add New Page
Talk1 Share

Khypes was a general in the Imperial Army of the Sith Empire during the Cold War between the Empire and the Galactic Republic.[2] Several years before 3641 BBY,[1] Khypes was sent to the recently-discovered planet of Voss with a battle cruiser and several army divisions to conquer the world and its powerful Force-sensitive natives. Khypes arrived in the Voss system, but before the general could contact the Voss, Khypes's battle cruiser exploded, and the escort ships were destroyed only moments later. Khypes's death and the loss of the fleet astonished both the Empire and the Republic, who were unable to find the cause of the explosion, and the Empire declared Khypes to have been a rogue officer as they made diplomatic overtures to the Voss.[2]

Behind the scenesEdit

Khypes was first mentioned in the Codex entry "The Imperial Attack on Voss" in Star Wars: The Old Republic, a video game released by BioWare in 2011, though the general's species and gender were not identified.[2]

AppearancesEdit

Notes and referencesEdit

  1. 1.0 1.1 SWTOR mini Star Wars: The Old Republic—Imperial Agent Mission: "The Prophecy of the Shining Man" on Voss establishes that the Shining Man made a deal with the Three for the Voss to remain neutral for a total of three thousand days, and also establishes that at the time of Act III in Star Wars: The Old Republic, there are still "a few years" remaining in those three thousand days. The Shining Man arrived on Voss only a matter of months after the planet was discovered, meaning that the planet's discovery must have taken place less than eight years prior to Act III, the events of which can be placed in 3641 BBY.
  2. 2.0 2.1 2.2 2.3 2.4 2.5 2.6 SWTOR mini Star Wars: The Old Republic—Codex Entry: "The Imperial Attack on Voss"

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.