FANDOM


Pride of Hiigara
Pride of Hiigara
Ship Information
Classification
Purpose
Fleet Command
Technical Information
Mass
3,000,000 tons
Speed
40 m/s
Hyperdrive
Armaments
12 Hull Defence Guns
Usage
Eras
Affiliation

The Pride of Hiigara is the upgraded version of the original Mothership designed solely for warfare. After the Battle for Sajuuk, the ship was abandoned in Balcora in favour for Sajuuk.

Background Edit

In terms of similarity the Pride of Hiigara once again served as a mobile ship factory and home for a crew of several thousand. Once again it served as the flagship of the Kushan fleet, now called the Hiigarans. Not only that but the flagship even had the same commanding officer, Karan Sjet, who once again by a remarkable turn of events, returned to the post of Fleet Command. Furthermore, Fleet Intelligence again made their HQ on the Mothership and the original's hyperspace core, now known definitively to be the Second Core.

In terms of differences there are many. As noted earlier the Pride of Hiigara was designed essentially as a warship, not as a civilian colony ship. For this reason the design was more refurbished, more defensible, and stronger under fire. Fewer weak spots were designed and the beautiful command deck of the Mothership was built into the hull rather than a gap built into it.

Purpose and MissionEdit

The purpose of the Pride of Hiigara is fairly unclear (mainly because of the lack of a backstory for Homeworld 2) although it seems that it was designed to carry the battle to the heart of Makaan's vast dominion and hence draw the battle away from Hiigaran space. If that was the case then it was poorly carried out as the Mothership's construction was somehow discovered and it was intercepted by a Vaygr task force at Tanis Shipyards. In fact, Hiigara itself was blockaded only shortly after the Pride of Hiigara was launched.

Even so, the Mothership was able to carry the battle eventually to Vaygr space and lead the new Mothership Fleet to victory against Makaan.

ConstructionEdit

Whereas the original Kushan Mothership took six decades to construct, it is believed that Pride of Hiigara was designed and completed in the span of a mere month.

The Pride of Hiigara was constructed with total secrecy, or so it was thought at first. It was not a publicly known project and was constructed within the Great Wastelands, a vast region of the galaxy filled with asteroid fields, derelicts, and nebulae, most notably the Great Nebula. The region, Tanis, was filled with ancient derelicts and megaliths and not well-known, a perfect place to build a secret ship. One of the megaliths was used to build a new scaffold much like the one used to build the original Mothership, though nearly twice as large.

The construction of the Pride of Hiigara was only just completed when a Vaygr task force attacked.

Tactical Capabilities Edit

Unlike the first Kushan Mothership from the Homeworld War the Pride of Hiigara is more capable of movement during combat, albeit slowly. Its hull defense guns will protect it from light strike-craft attacks but anything bigger, or even a massed Bomber attack, can destroy it; it is not intended for front-line combat.

Its construction arrays are always capable of building Scouts, Probes, Mobile Refineries and Resource Collectors, but to build anything more advanced Facilities need to be built.

It has 4 Facility slots, 4 Module slots and 1 Sensor slot available.

Fate of the Pride of HiigaraEdit

The Pride of Hiigara, though a symbol of the Hiigaran people and well-scarred with memories of its battles with the Vaygr, was later abandoned at Balcora in exchange for Sajuuk, a massive battlecruiser of unrivaled power, which was then used to save Hiigara from destruction.

The Pride of Hiigara was left unpowered and empty at the Balcora site, and its fate is unknown, though it is likely still there.

SourcesEdit

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.