Fandom

Wookieepedia

Gowix Corporation

135,127pages on
this wiki
Add New Page
Talk1 Share
This article is about the company during the Old Republic era. You may be looking for Gowix Computers.

Gowix Corporation was a company headquartered on the planet Corellia around the time of the Galactic War between the Galactic Republic and the Sith Empire.[1] Founded before 3641 BBY,[2] Gowix maintained offices on the edge of Archival Square, a section of the Axial Park district in Corellia's capital Coronet City, and the company was caught up in the fighting when the Empire invaded Corellia. The corporation's building in Axial Park was captured by Sith forces, and the invaders set up a prototype weapon known as Firestorm Turbolaser in the company's offices with the intention of causing massive casualties in Archival Square. However, the Jedi Knight known as the Hero of Tython infiltrated the building using an assault shuttle and eliminated the Sith forces within the company's offices before destroying the weapon.[1]

Behind the scenesEdit

Gowix Corporation first appeared in the video game Star Wars: The Old Republic, released by BioWare in 2011. Gowix's office tower is one of the buildings that Jedi Knight players are sent to during the class mission "Firestorm" on Corellia.[1]

AppearancesEdit

Notes and referencesEdit

  1. 1.0 1.1 1.2 1.3 1.4 1.5 SWTOR mini Star Wars: The Old Republic—Jedi Knight Mission: "Firestorm" on Corellia
  2. 2.0 2.1 Using comments and information from The Old Republic—The Lost Suns 2, The Last Battle of Colonel Jace Malcom, and The Old Republic: Annihilation, it is possible to place the events of the Prologue and Act I for the Jedi Knight, Smuggler, and Trooper classes in Star Wars: The Old Republic in 3643 BBY, the general events of Act II in 3642 BBY, and the events of Act III for all classes in 3641 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.