- 1 Second Front Continuity
- 2 Commodore Daniel Bast
- 3 Internal Evolution of the GTVA
- 4 Coalition for Free and Open Trade
- 5 GTI Good Hope
- 6 Codex Anathema
- 7 GTVA Weapon Developments (2367 - 2373)
- 7.1 GTW-66 Maxim Cannon
- 7.2 GTW-6d Prometheus II
- 7.3 GTI TAG-C Missile
- 7.4 GTM-10a Piranha A Missile System
- 7.5 GTM-11a Infyrno A Missile System
- 7.6 GTM MX-8 Torrent Rocket Pod
- 7.7 GTM-84a Avalanche Rocket
- 7.8 GTM-84f Avalanche II Missile System
- 7.9 GTW-78 Point-Defense Laser Turret
- 7.10 GTW-79 Extended Range Laser Turret
- 8 Ship List
- 9 External Links
Second Front Continuity
Canon events are highlighted in red and provided for reference. (Dates for canon events are not themselves canon within FreeSpace 2, but they are assumed to be correct for the Second Front continuity.)
The Second Front story arc tracks the GTVA through a slow, seven-year decline in power, beginning with the Shivan Incursion of 2367. This decline culminates with a third and final shivan incursion, which proves to be the death knell of the Alliance.
November 27, 2367: The Altair fleet requests tactical support from SOC forces in Aldebaran. An SOC detachment, under the command of Commodore Daniel Bast, is sent to Altair to oversee and support operations against the shivans.
November 29, 2367: 80 Sathanas juggernauts surround the Capella sun and begin emitting quantum subspace pulses of increasing intensity. GTVA Colossus destroyed by a Sathanas-class juggernaut while defending the Capella-Gamma Draconis node.
November 29 and 30, 2367: All jump nodes in the system beyond Altair, except the Altair node itself, are collapsed by the Altair fleet and SOC forces.
November 30, 2367: GTD Nereid and GTD Bastion, packed with meson bombs, detonate inside the Vega-Capella and Epsilon Pegasi-Capella nodes. Sathanas juggernauts destabilize the Capella star, causing a supernova.
December 1, 2367: The bulk of the shivan force assaulting Altair, consisting of three destroyers, supported by numerous corvettes and cruisers, is destroyed.
March 10, 2368: A derelict shivan cruiser in the system beyond Altair is recovered.
March 12, 2368: Mop-up operations complete in Altair and the system beyond. Martial law ends in Altair, but Commodore Bast places his own command authority above that of the Altair provisional government.
November 24, 2368: The GTC Firestorm, deployed from Altair without authorization, enters Alpha Centauri and suffers a comprehensive system failure.
November 26, 2368: The Firestorm is recovered by the Alpha Centauri fleet and returned to Altair.
December 3, 2368: After destroying the Aldebaran fleet, the Altair fleet, led by its flagship the GTD Galen, enters Alpha Centauri and begins carving a path of destruction toward the GTVA capitol in Delta Serpentis.
December 17, 2368: The Galen, its support fleet destroyed, enters the Delta Serpentis system. In a battle against the GTD Phoenicia and GVD Bilbeis, the Galen is forced to withdraw. The destroyer subsequently disappears into Ross 128, where GTVA forces lose track of it.
August 27, 2372: The Coalition for Free and Open Trade announces its existance in Ross 128. The GTVA makes no distinction between the Coalition and other bandit organizations throughout Allied space.
February 9 and 10, 2373: Battle of Good Hope. The GTCv Boston, the prototype Iceni, is captured by Coalition forces from the Good Hope shipyard and is subsequently recaptured by Allied forces. Despite the defeat, bandit groups in Ross 128 begin uniting under Coalition leadership.
March, 2373: Bandit groups beyond Ross 128 begin uniting under the Coalition.
September, 2373: Most bandit organizations either accept Coalition leadership or are eliminated. The chief exception is the group in power in Altair, Aldebaran, and Alpha Centauri, though significant elements of this organization are sympathetic to the Coalition and undermine the tenuous command structure.
February 1, 2374: The GTD Galen is discovered derelict near the debris field of the GTI Riviera. During a recovery operation, a nearby shivan cruiser, previously powered down, fires upon the Galen, destroying it.
February 3, 2374: GTVA Command reinitiates the search for the jump node that shivan forces used to enter Ross 128 at the onset of the Great War. As additional shivan forces begin appearing in Ross 128, the GTD Liberator, the first of the redesigned Hades-class destroyers, sees its first combat sorties.
February 10, 2374: The defense of Allied space against the shivans deteriorates. GTVA Command cedes its authority to individual system authorities, issuing a final order to evacuate Allied space and flee the shivans.
Commodore Daniel Bast
Daniel Bast (born July 2, 2317, officially declared missing December 18, 2368) was an intelligence officer in the Galactic Terran-Vasudan Alliance and later, the infamous leader of the Altair Insurgency. After a career including numerous experiences with Reconstruction-era governments and the GTVA left him questioning the motives of his leaders, he led the Altair fleet into rebellion, causing an incredible amount of damage to Allied holdings, before he and his command ship disappeared, somewhere in the Ross 128 system.
Early Life and Career
Daniel Bast was born in the first planetary colony on Delta Serpentis II in 2317. Though the colony's infrastructure had been quite well developed in the years since its establishment, Daniel's parents felt that Earth or one of the other colonies in Sol would provide a better environment for raising a child. The Bast family returned to Earth in January, 2321. Daniel was enrolled in the public education system in the Western Eurasian Bloc.
The shivans appeared in Ross 128 late in Daniel's final semester in the public education system. Immediately upon graduation, he volunteered for service in the Galactic Terran Alliance's fleet. This led to him being transferred to a training facility in Delta Serpentis a mere month prior to the collapse of the Sol jump node. Bast was still in pilot training by the end of the Great War and saw no action during the conflict.
In 2336, during the subsequent fracturing of the Galactic Terran Alliance, Bast found himself under the command of the Antares Federation. Bast was highly critical of the Federation's government for complacently allowing the GTA to break up, citing that a divided terran military would be less capable of defending the species, should the vasudans elect to reignite old hostilities. Despite what he felt about his orders, Bast was obedient when ordered into skirmishes with the other regional blocs. It was during the nine years, prior to the founding of the Galactic Terran-Vasudan Alliance, that Bast was able to distinguish himself as a pilot and commander, permitting him rapid advancement though the military hierarchy.
Since the Antares Federation controlled Beta Aquilae, while the BETAC treaty was being negotiated, they had a measure of political leverage that the Vasudan Empire and other terran power blocs did not enjoy. Relevant to Bast, the Federation's government was able to unilaterally propose and approve of changes to the military structure of each terran faction, ostensibly in order to speed the compilation of the four fleets. This power included the ability to choose what officers would remain in service to the GTVA military, as overlapping positions were eliminated.
Not only was Bast guaranteed a position in the GTVA military, his generally careerist behavior during the early Reconstruction Period earned him the opportunity to choose a low-level command position to take in the unified military structure. The intelligence field fascinated Bast, as it seemed to him like the only arm of military command where he would be doing more than overseeing the same straightforward operations that he had been a part of for over two decades.
After fourteen years of war and another twenty of uneasy coexistence, a significant minority of the terran population and the military, in particular, disapproved of an alliance with the vasudans. Between 2358 and 2365, Bast was assigned to half a dozen major covert operations to undermine factions of the disaffected before they could coalesce into threatening political or military force.
When Admiral Aken Bosch led most of the GTVA's Polaris fleet into rebellion, it came as a shock to most of the GTVI. Given their success in dismantling other dissident groups before they could gather any strength, the GTVI leadership was amazed that something so large had managed to evade their attention long enough to develop into such a substantial movement. Not knowing the true extent of the Neo-Terran Front and concerned with the possibility of double-agents remaining in the GTVA fleet and systems beyond Polaris, the GTVI reassigned many of its most loyal command officers. Bast was caught in this redistribution of loyal officers and placed in charge of special operations in Aldebaran.
Special Operations in Altair
Bast's stay in Aldebaran was uneventful, until November, 2367, when the shivans opened a second front in their incursion into GTVA space. The Altair provisional government, unable to deal with a shivan offensive, with the few warships at its disposal, requested support from Special Operations Command in Aldebaran. Commodore Bast was relocated to Altair and assigned to take control of all operations in the system, until the system was secure.
Commodore Bast exploited the open-ended wording of his orders to declare martial law during this crisis and effectively usurp power from the Altair provisional government. Bast's intention was not open rebellion, but the return of the shivans shook Bast to the core. His hope was to use his influence and resources in Altair to study the tactics and strategy of the shivans during their second incursion, in hopes of discovering a better means of defending against them, should they return a third time.
Bast's exploration of shivan capabilities was expanded in March, 2368, when a largely undamaged shivan cruiser was recovered, apparently abandoned after the attack on Altair failed. He urged GTVA command to aggressively study the cruiser with the aim of directly integrating shivan technology into the GTVA fleet. These proposals were repeatedly rejected, citing that existing precedent, with regard to shivan technology, was to derive new terran/vasudan technology, based on reverse-engineering studies of shivan devices. Direct integration or duplication of shivan devices in the GTVA fleet was out of the question, in the words of the Security Council.
In late 2368, Commodore Bast began an operation that he hoped would demonstrate the value of hybrid shivan-terran and shivan-vasudan technology. It was his belief that a small but significant number of shivan vessels were left in a hibernating state throughout GTVA space after the core of the shivans' Great War fleet was destroyed. His plan was to surreptitiously take control of the central communication node of the Alliance, on Delta Serpentis II, in order to send a 'wake up' signal to these hibernating shivan vessels. To deal with this small, manageable threat, he would order the Altair fleet to deploy the GTD Galen, retrofitted with a wide range of shivan technology.
Unfortunately for this plan, the cruiser he ordered deployed for this purpose suffered from technical troubles in Alpha Centauri, and the transport it escorted was captured by local criminals. Dissatisfied with how easily this plan was foiled, Bast opted for the more direct approach of deploying the entire Altair fleet to capture the communication node on Delta Serpentis II. By utilizing the de facto communications blackout in Altair, Bast convinced the military personnel under him that the alliance was facing a widespread rebellion.
Bast's intention during his offensive was to blackout communications in each system the fleet passed through, while avoiding heavily defended areas. This plan failed, first in Aldebaran, when the elements of the Aldebaran fleet individually intercepted the Altair fleet and had to be destroyed. More spectacularly, the Altair fleet faced a blockade just inside Alpha Centauri, at which point, Bast realized that it was going to be impossible to spend the time in each system necessary to deploy communication jamming equipment, without facing counterattack. Though the goal remained the same, the nature of Bast's campaign changed. The Altair fleet proceeded to charge, at top speed, toward Delta Serpentis, destroying whatever stood in its way.
The Altair fleet's offensive was stopped just a few thousand kilometers from the surface of Delta Serpentis II, where Bast's command ship, the GTD Galen, was critically damaged and forced to retreat.
The Galen was last sighted in Ross 128, retreating from the Delta Serpentis jump node. It is unclear if Commodore Bast survived the final assault on the destroyer. In any case, contact with the Galen was lost in Ross 128, and by 2373, ongoing search operations had yet to pick up the destroyer's trail.
Internal Evolution of the GTVA
In 2367, the Galactic Terran-Vasudan Alliance stopped a pair of shivan attacks. At the end of the Great War, it was thought that the shivans had been destroyed, and would not be seen again. Their return in Gamma Draconis and Altair was, in itself, a disturbing surprise. Coupled with the undisputable defeat, measured by the loss of two star systems, over two-hundred-and-fifty million civilian lives, and massive materiel losses to every system's fleet, there was an understandable level of concern among the upper eschelons of the GTVA military authority.
The shivans demonstrated that they were capable of military production beyond the wildest dreams of the terrans or vasudans. A simple, extreme, and apparent solution became the goal of Allied military forces. They would seal jump nodes leading to uncharted star systems, find new jump nodes, and seal them as well. Unfortunately, the destruction of a jump node required large and expensive explosive devices, and seeking out new jump nodes would require numerous ships equipped with similarly expensive sensor equipment. With criminal organizations and Neo-Terran Front holdouts exploiting the weakened GTVA fleet, resources never materialized. Threats from within were simply more immediate than external threats, and so node-sealing operations were placed on the backburner.
Only about a year after the shivan incursions into Capella and Altair, the Alliance's troubles were compounded. With little apparent reason, the entire Altair fleet, under the direction of Commodore Daniel Bast, carved a path of destruction through systems from Aldebaran to Delta Serpentis. In the Altair fleet's wake was more than just a string of corpses and debris, but a power vacuum in three systems and a further-weakened GTVA fleet. Both of these factors further increased the relative strength of bandit and renegade factions.
Given the constant state of military conflict, the constituent states of the GTVA came to concensus that their defense was being compromised in some capacity by the decentralized nature of the civilian government. Planetary and system governments began turning over more and more authority to the GTVA General Assembly between 2369 and 2372. Though the General Assembly had more power handed to it, it made no radical changes, until April, 2372.
On April 1, 2372, the GTVA Security Council authorized the first new ship classes since the loss of Capella. They further called for a comprehensive upgrade of aging point-defense systems used in existing warships. The General Assembly concurred that these changes were necessary, but did not see how the introduction of new ship and weapon production lines could be possible in the so-called 'post-Capella' economy. There was little profit to be made building weapon systems for an indebted government using an increasingly worthless currency. The General Assembly set out to purchase, or failing reasonable offers, commandeer manufacturing centers and resource extraction facilities.
Almost overnight, the GTVA transitioned from a largely free-market economy to a state-controled economy. Within the military realm, this change proved a resounding success. In under a year, upgraded point-defenses had been installed in over sixty percent of warships and installations in the GTVA, and production of the redesigned GTCv Iceni-class corvette had begun.
Coalition for Free and Open Trade
Formation and Composition
As the GTVA General Assembly was given more and more governing power between 2369 and 2372, they hesitated in making any major changes to the government's status quo. There was a fear that any kind of major change brought about by the newly-centralized government would come with major backlash, which would increase the risk of providing bandit factions a single cause around which to unify. When dramatic change was deemed necessary in mid-2372, those risks were realized, albeit not as was widely accepted.
In Ross 128, during the economic reformation, military units, sympathetic to local labor organizations, defected to existing bandit groups, and reorganized them into a new faction. This marked the beginning of the Coalition for Free and Open Trade, a capitalist bandit faction. The Coalition's initial goal was to pressure the GTVA into reversing the public takeover of the galaxy's heavy industry, but as the movement grew, the subtlety was lost, and the intention became overthrowing the GTVA in favor of a new, capitalist government.
Initially, the strength of the Coalition was unimpressive. The group that broke away from the GTVA's military arm brought with them a half-strength fighter squadron, and even efforts to coax members away from other bandit organizations only yielded a few bombers and no facilities to maintain any of these craft.
The Coalition's early military directive was to acquire additional assets by any means available. The only means readily available was piracy, and though successful, it earned the Coalition more than their fair share of enemies. Horning in on existing bandit factions' territory and even directly attacking some of the factions from which the Coalition had drawn members, but the benefits greatly outweighed the costs. Early campaigns yielded small territorial holdings throughout Ross 128, additional fightercraft, and rudimentary support facilities.
In October, 2372, the Coalition was finally becoming confident in their ability to sustain themselves and began to focus in on their long-term objectives, that is, the overthrow of the GTVA. Unfortunately, even given their enhanced strength, the leadership of the Coalition knew that a doctrine consisting solely of violence would do little more than disrupt Allied activities in Ross 128.
During this period, Coalition leaders began meeting with their counterparts in other bandit factions to mend fences. This early diplomatic effort consisted of exchanges of territory as a form of reparation and nonaggression pacts to ensure some measure of stability among the bandit groups. Stability was inadequate, though, as the Alliance had proved capable of dealing with the numerous and uncoordinated attacks of existing bandit factions. Months of holding true to their treaty obligations built a great deal of trust for the Coalition, allowing them to form cooperative alliances with several bandit factions and even absorb another.
Though dominant, by February, 2373 the Coalition was still not the sole faction, opposed to the GTVA, in Ross 128. In their first overture for total bandit unification, rather than making their individual agenda the impetus for unification, as other factions had, they made opposition to the GTVA the idea behind unification. The core of the message that Coalition diplomats delivered was that a new governing system could be decided upon after the existing government was overturned.
The message met with success. On February 9, remaining bandit factions within Ross 128 merged with the Coaltion. The unified Coaltion launched its first operation that day, attempting to capture cruisers in the region around the GTI Good Hope. This operation ultimately culminated in a direct attack on the Good Hope and the capture of the GTCv Boston, one of the first of the redesigned Iceni-class corvettes. Though the station survived, and the Boston was recaptured, the attack demonstrated the threat that a unified bandit faction could pose and gained the Coalition some level of renown among bandit groups across the whole of GTVA space.
Coupling the de-emphasis of their capitalist message with more demonstrations of their capabilities within Ross 128, the Coalition began rapidly absorbing additional bandit factions in numerous star systems. By September, 2373, the only systems without a Coalition presence were Altair, Aldebaran, and Alpha Centauri, though the dominant factions within each of these systems carried large numbers of Coalition-sympathizers. In early 2374, internal pressures within these factions began to sway them toward finally joining the Coalition.
As bandit factions in individual systems united under the Coalition banner, they would initially make small territorial gains against Allied forces in those systems, but once the element of surprise subsided, the pre-unification stalemate would resume. A galactic victory by way of unified, surprise attacks was not forthcoming, and since the GTVA retained control most of the heavy industrial sites and raw materials, a prolonged war of attrition did not favor the Coalition. The diffuse nature of the Coalition did provide them with a number of potential options, however.
Coalition leadership ultimately decided that they would have to give up holdings to gain control of assets necessary to sustain a traditional war. By abandoning holdings in peripheral systems, such as Ikeya, Mirfak, and Altair, the Coalition would be able to mass a force capable of entering and gaining total control of one or more of the Alliance's core systems. That in mind, the Coalition set an ambitious goal of cementing their control of Ross 128, while capturing, in their entirety, Vega, Beta Aquilae, and Delta Serpentis. With this core of four systems, the Coalition would be able to more easily defend their territory, more reliably replace their combat losses, and eventually begin to expand into other systems again.
The chief appeal of this strategy over others was that it split the GTVA in half. In the worst-case scenario, still permitting Coalition success, the Alliance would regain control of all of their territory outside of the Coalition core, but their production capacity would still be markedly weakened. While the most substantial industrial facilities (located in Sirius, Regulus, and Polaris) and richest mining operations (located in the systems surrounding Wolf 359) would remain in Allied hands, they would be nearly useless cut off from one another.
Moreover, the Coalition also planned to resume the Alliance's project to reopen the Sol jump node, using a Knossos-style portal. It was their belief that the first faction to reinitiate contact with Sol would be viewed favorably by the Terran government and be most able to form a military alliance with the system, more awash with natural resources than any other.
Initially, Coalition leadership had planned on setting this plan into motion on February 14, 2374 by abandoning positions in eight systems to begin concerted assaults on Vega and remaining Allied holdings in Ross 128. By the time that day arrived, however, the third shivan incursion had advanced to such a stage where there was no Alliance to fight and no Coalition to fight them.
Originally a student of terran languages, Menkaura gained notoriety for himself during the pre-unification bandit conflicts. He rebelled against the Alliance with an organization that sought to liberate predominantly vasudan systems from the largely terran leadership of the GTVA. The movement lacked the military strength of other bandit factions, though, and was forced to retreat from Vasuda and a number of other systems, until its members finally dispersed and went into hiding in Ross 128.
Without a cause to rally behind, Menkaura remained silent for many months. He became incensed with the Alliance again, when it made the rapid transition to a state economy. Menkaura was quick to show his opposition to this movement by making a number of anonymous network broadcasts. His technical abilities were lacking, though, and both Allied law enforcement and the earliest members of the Coalition of Free and Open Trade began tracking Menkaura.
The Coalition found Menkaura first, and after relocating him, to shelter him from Allied authorities, they began utilizing Menkaura as their primary source for propaganda. Initially, this took the form of more anonymous broadcasts, though with the technical support of the Coalition, Menkaura remained much more anonymous than before.
As the Coalition grew and their influence spread, eventually, Menkaura felt that his message would carry more power, were it not delivered from behind a shield of anonymity. Menkaura's intuition proved correct, and the Coalition's message resonated, not just for the boldness with which Menkaura delivered it, but because his mastery of both the vasudan language and the many terran languages made members of both races feel as if he truly took to heart their individual interests.
Menkaura did not draw only the attention of Coalition sympathizers, though. Word of his broadcasts reached back to the vasudan throne, resulting in a rare action on the part of Khonsu II. Menkaura was declared to be a nonperson by the Vasudan Empire, an action which the GTVA supported. His expatriation did not dampen his will, though, and Menkaura continued his broadcasts and the escalation of his propaganda campaign. In February, 2373, before a 1,000-member Coalition rally on a mining colony, in Ross 128, Menkaura gave his first live, in-person speech, decrying the failures of the Alliance, dating back to the Neo-Terran Front rebellion. This was seen as a seminal moment for the Coalition, ensuring unification in Ross 128, and spreading their call to arms far beyond that system's boundaries.
GTI Good Hope
Construction on the Good Hope began in 2342 as a replacement to Outpost Riviera, which was destroyed in the opening salvos of the Great War. Initially designed as a listening outpost, with the capacity to deploy reconnaissance fighters, Good Hope was only to differ from Riviera with slightly more advanced sensor and communication systems, as well as improved fighter launching mechanisms.
During the station's construction, fleet doctrine changed, such that destroyers would become the primary launch platforms for each star system's fighters, even in a defensive capacity. This led to a large number of existing and pending stations to be sold to private enterprises. Good Hope was completed in 2344, despite the doctrine change, and never privatized, as the local government and later the GTVA Security Council felt that a military listening post in Ross 128 was critical, since that was where the shivans were first encountered.
By 2360, extensive and ongoing upgrades of Good Hope's sensors and communications equipment resulted in reduced crew and space requirements, rendering large sections of the station unused. Maintaining the station was becoming less cost-effective, but since the necessity of a permanent listening post still existed, a shutdown was out of the question. In light of this, and a growing need to modernize the aging Great War fleet, the Security Council authorized the addition of a shipyard, including three Ganymede-class facilities, the first of which was completed in 2363.
In 2372, the Good Hope shipyard had been tasked with the construction of the GTCv Boston, a prototype Iceni-class corvette and was one of two shipyards assigned to construct new Hecate-class destroyers. Security Council plans at that time called for the Good Hope shipyard to complete two new Hecates and six Icenis by the end of 2376, at which point, one of the Ganymede installations would be reassigned to decommissioning the remaining Orion-class destroyers, while fleet construction doctrine would be reevaluated, before determining the production goals of the other two construction facilities.
The Battle of Good Hope, in 2373 resulted in the destruction of one of the Ganymede rings and set back the construction of the GTD Essex by several months.
Fighter Compliment and Defenses
|GTF Hercules Mk. II||0||0||4||4|
In addition to its fighter compliment and twelve sentry guns, two Fenris-class cruisers were assigned to patrol the station, after its completion in 2344. The GTC Kelsan, a Leviathan-class cruiser was added to this defense force, in late 2365, amidst concerns that the Neo-Terran Front may have had sympathizers well outside of Polaris. These cruisers defended the station until their destruction in combat, in 2373.
Codex Anathema is the name of a book, apparently written by Aken Bosch, prior to his disappearance in the shivan nebula. One of the SOC's final missions resulted in the capture of a shivan freighter, carrying a copy of this book. The shivans' purpose for copying and carrying Codex Anathema was never discovered.
When Admiral Aken Bosch conceived an alliance between terrans and shivans, he faced a number of barriers. Most prominently, was the matter of contacting the race, absent from Allied space. When he happened upon information regarding the Knossos portal, the physical obstacle became surmountable. As his rebellion gained momentum, and Bosch resumed the GTI's research, even the technological boundary, separating terran from shivan, began to break down.
Simply being able to produce sound does not mean that one can speak, and while ETAK enabled Bosch to transmit signals to the shivans, he still needed to untangle the mystery of their language. Ideally, Bosch intended to use the NTF fleet to capture the Gamma Draconis system, so that he would be able to utilize the system as neutral ground, while learning the rudiments of communication with the shivans and developing his planned alliance.
Unfortunately, the GTVA's debut of the Colossus and their subsequent charge into Neo-Terra's territory forced Admiral Bosch's to act much more hastily. Prior to his final charge into the nebula, Bosch began poring over all of the GTI's research data relating to shivan prisoners. Bosch compiled his findings and notes into a volume, titling it Codex Anathema, anticipating its rejection among Allied leadership, should it ever reach their hands.
When the GTI researched shivan captives, their interests were in the species' biological and technological capabilities. Communication, even interrogation, were not priorities. (Indeed, though the ETAK experiment evolved, under Bosch's leadership, it was originally intended to confuse and disrupt shivans.) This led to there being almost no data collected about shivan language. Still, interfacing certain shivan technology understanding of shivan words. Though small and focused, GTI researchers developed a vocabulary to aid their other research endeavors.
This vocabulary was the nearest thing Bosch had to a foundation of language. Codex Anathema began with this foundation and attempted to build the whole language from there. Much of the work, therefore, is hypothesis and supposition, with at best, very little supporting evidence.
The later chapters of Codex Anathema are primarily revisions of the rest of the work. Evidence suggests that these chapters were written, at a furious pace, in Bosch's final days aboard the Iceni, after making his initial contact with the shivans. This was apparently Bosch's last opportunity to correct some of his earlier guesses, as timestamps on each entry indicate none were made after the evacuation of the Admiral's frigate.
GTVA Weapon Developments (2367 - 2373)
GTW-66 Maxim Cannon
As of December 14, 2368, the Maxim Cannon was recalled from all GTVA units. The weapon was found to have problems with components wearing heavily in the cooling system, resulting in the weapon jamming and in some cases, self-destructing.
Despite some doubts about whether or not GTI Labs would be able to redesign the weapon, without sacrificing the weapon's viability in combat, the Maxim Cannon was returned to service in July, 2372. The redesign came at the expense of half its range and a modicum of damage, though pilots testing the new Maxim have agreed that it remains a reasonably affective hull-busting weapon.
GTW-6d Prometheus II
While the Maxim was out-of-service, undergoing a redesign of its cooling system, bomber pilots found themselves without a primary weapon appropriate for strafing warships hulls between bombing runs. The Prometheus II was designed, not as a replacement to the Prometheus S, a dogfighting weapon, but as a new variant, meant specifically for supplementing heavy bombing.
Where previous Prometheus weapons struck a balance between per-shot damage and rate of fire, the Prometheus II, being meant for use against quite large, slow targets, fires a small number of remarkably powerful projectiles. The high energy demands of this weapon render it incompatible with most fighters and all but a select number of bombers.
GTI TAG-C Missile
As Pegasus and Ptah recon fighters become more prevalent and plans are made for proper, stealth-capable combat vessels, the issue of how to combat stealthy craft became quite pressing in the Security Council. Though installing more capable sensor systems in all fighters and warships would be ideal, such a measure would take considerable time and resources, even supposing such technology was ready to be deployed. As a stopgap measure, GTI Labs was ordered to refine the TAG missile system for use specifically against stealth fighters.
The TAG-C is more maneuverable than the TAG-B and carries a heat-seeking tracking system, sensitive enough to home in on the faint heat signature of a Pegasus or Ptah. As with other TAG systems, the TAG-C illuminates the target, allowing for ships, otherwise unable to detect the target, to engage the stealth craft. The TAG-C transmitter goes beyond this simple function though, emitting a signal strong enough that it will disrupt the electronics of the ship to which it is attached.
GTM-10a Piranha A Missile System
Since its introduction during the NTF conflict, GTVA Command lauded the GTM-10 Piranha as the weapon system that would liberate bombers from the need of fighter escort. When bomber pilots largely abandoned the weapon, after its introduction, the Sahr Corporation was tasked with redesigning their weapon to address pilots' chief complaints. The GTM-10a is the upgraded Piranha, which is capable of traversing larger distances, producing a much more devastating shockwave, and deploying faster, more agile submunitions. Additionally, a seeker-head has been added to allow the Piranha to track a target's heat signature and detonate closer to its intended targets.
GTM-11a Infyrno A Missile System
Like the Piranha, the original Infyrno failed to live up to its expectations. Its low speed, short range, abysmal accuracy, and relatively narrow submunitions spread rendered it incapable of performing its primary task of breaking bomber formations. Many of the improvements to the Piranha were mimicked, when initially upgrading the Infyrno, including the addition of a heat-seeking tracker head and a more efficient propulsion system, allowing the warhead to travel longer distances. Where the revised Piranha uses fewer, more powerful submunitions than its predecessor, however, the team redesigning the Infyrno opted to use many more, smaller bomblets, deployed in stages, to spread its effect across a wider area.
GTM MX-8 Torrent Rocket Pod
As point-defense capabilities of warships improved, developing the delivery system for antiwarship weaponry took priority over producing more destructive warheads. One of the biggest weaknesses of antiwarship torpedos, such as the Cyclops or Helios, was the incredibly long lock-on time, required before the weapon could fire. Because warships are so large and slow, the Security Council ordered prototypes of antiwarship warheads without any kind of seekerhead.
The first production-model, dumbfire, antiwarship weapon was the Torrent Rocket Pod. The Torrent system fires a salvo of twelve to twenty-four heavy rockets, with a combined payload comparable to a (or a pair of) Cyclops warhead(s). A single-warhead solution would have been preferable for some pilots, as more space can be used for the weapon, with less room spent on the delivery system, but widespread appeal of the Torrent arose among pilots, because warships' point defenses could rarely shoot down an entire salvo, meaning each bombing run with a Torrent would result in at least some damage being dealt.
GTM-84a Avalanche Rocket
The Avalanche was proposed as a single-warhead alternative to the Torrent Rocket Pod. Since the Avalanche only had to fit one engine and one warhead in the same space that the Torrent needed for twelve, the Avalanche is capable of dealing thirty-percent more damage. A concern among veteran Torrent-users was the relative ease with which the single-warhead Avalanche could be shot down. Where a salvo of Torrent rockets will almost always deal some damage to a target, an Avalanche rocket is an all-or-nothing proposition, like a Cyclops.
GTM-84f Avalanche II Missile System
While hitting the hull of a massive warship is little challenge, even for the greenest pilots, hitting a particular turret or subsystem is more difficult. In order to reclaim some of the pinpoint accuracy of more traditional, aspect-seeking munitions, without sacrificing the rapid-deploy capability of the first-generation Avalanche or Torrent, manufacturers fitted an advanced heat-seekerhead to the Avalanche rocket. The cost of the added seekerhead, maneuvering equipment, and fuel necessary to push the heavier warhead was a twenty-percent increase in the size of the weapon.
GTW-78 Point-Defense Laser Turret
By 2367, fighter and bomber shielding had advanced radically, since the Great War, and while flak and beam weaponry marginally mitigated the ability of fighters and bombers to approach capital ships, completely replacing Great War-era turret weaponry with flak and beams was simply impossible. Beam weaponry required more power than older turrets by orders of magnitude, and space for new ammunition storage bays in older warships was simply unavailable. At the same time, though, Great War-era turrets were, by no means, efficient in terms of other weaponry available in the 2360's.
One of two replacement weapon systems ordered in early 2372 was the GTW-78. Though dealing less per-shot damage than the turrets it was designed to replace, it boasts a rate of fire faster than the Subach HL-7. While this makes for only a marginally improved anti-fighter defense, it provides extremely strong screening fire against incoming warheads.
GTW-79 Extended Range Laser Turret
The counterpart to the GTW-78, the GTW-79 was designed to provide extremely long-range fire. At this task, a cluster of extended range turrets excels, providing fire out to a range of approximately four kilometers. The extended range turret also packs an incredible amount of power into each shot and has been utilized effectively against cruisers in testing. This damage is only somewhat mitigated by shielding, making it a very punishing weapon against incoming fighters. The only area where the extended range turret does not excel over its Great War-era counterpart is its rate of fire. There is still a substantial delay between shots, making it less able to surpress incoming fighter attacks than the GTW-78.
Includes all named ships appearing in the Second Front continuity, through the Battle of Good Hope.
- Tables ordered from most recent events to oldest.
- Status indicated represents the ship's status at the end of that particular campaign.
- A question-mark following a ship's status indicates that that is the ship's most likely status by the end of the campaign in which it appears, but its survival/destruction is not necessary for the campaign's continuity.
- The 'Serving System' column indicates where the ship is normally stationed.
- Exploration vessels serve beyond the confines of charted space.
- Ships of the Capella fleet are noted as being displaced, as no assumption is made regarding their evacuation or loss during the Capella supernova.
- 'Local bandits' refers to bandit factions that do not or have yet to join the Coalition for Free and Open Trade.
- 'NTF Remnant' refers to renegade forces coalescing under the NTF banner, despite the absence of Bosch's leadership.
- 'CFOT' indicates the Coalition for Free and Open Trade.
- 'Shivan Forces' are assumed to be one faction, serving a singular purpose, despite attacking through multiple systems.
Battle of Good Hope
|Ship Name||Ship Class||Status||Serving System||Faction||Role and Major Engagements|
|Barataria||GVC Aten||Destroyed (?)||Ross 128||CFOT||Spotted and fired upon at a Coalition-held depot.|
|Bolivar||GVG Anuket||Destroyed||Ross 128||CFOT||Involved in direct attack on the GTI Good Hope.|
|Boston||GTCv Iceni||Operational||Ross 128||GTVA||Captured by Coalition forces and recaptured by GTVA forces shortly thereafter.|
|Bushnell||GTFr Triton||Operational (?)||Ross 128||CFOT||Spotted and fired upon at a Coalition-held depot.|
|Caligula||GTT Elysium||Operational (?)||Ross 128||CFOT||Carried Coalition capture teams to the GTCv Boston.|
|Eclipse||GTT Elysium||Operational||Ross 128||GTVA||Recaptured a Coalition freighter in the Battle of Good Hope.|
|Farina||GVT Satis||Operational (?)||Ross 128||GTVA||Reclaimed from the Coalition during an operation to draw out the GTCv Boston.|
|Good Hope||GTI Arcadia||Operational||Ross 128||GTVA||Major shipyard in Ross 128. Came under massive attack as Ross 128 bandit factions began to unite under the Coalition for Free and Open Trade.|
|Hubertus||GTM Hippocrates||Destroyed (?)||Ross 128||CFOT||Involved in direct attack on the GTI Good Hope.|
|Ionia||GTC Leviathan||Destroyed||Ross 128||CFOT||Involved in direct attack on the GTI Good Hope.|
|Jolo||GVFr Bes||Operational (?)||Ross 128||GTVA||Reclaimed from the Coalition during an operation to draw out the GTCv Boston.|
|Kelsan||GTC Leviathan||Destroyed||Ross 128||GTVA||One of three cruisers assigned to defend the GTI Good Hope. Destroyed during the defense of Good Hope.|
|Lydia||GTC Fenris||Destroyed||Ross 128||CFOT||Involved in direct attack on the GTI Good Hope.|
|Marque||GTSC Faustus||Operational (?)||Ross 128||CFOT||Spotted and fired upon at a Coalition-held depot.|
|Mordvinov||GTT Argo||Operational (?)||Ross 128||GTVA||Carried marines to recapture the GTCv Boston.|
|Morris||GTFr Triton||Operational (?)||Ross 128||CFOT||Spotted and fired upon at a Coalition-held depot.|
|Naxos||GTCv Deimos||Operational||Ross 128||GTVA||Deployed to the GTI Good Hope to reinforce defending vessels.|
|Nefaarud||GVD Typhon||Operational||Ross 128||GTVA||Deployed to the GTI Good Hope to reinforce defending vessels.|
|Neufchatel||GTT Argo||Operational (?)||Ross 128||CFOT||Spotted and fired upon at a Coalition-held depot.|
|Prudhoe||GTG Zephyrus||Destroyed||Ross 128||CFOT||Involved in direct attack on the GTI Good Hope.|
|Serendipity||GTC Fenris||Destroyed||Ross 128||CFOT||Involved in direct attack on the GTI Good Hope.|
|Seshat||GVA Setekh||Operational||Ross 128||GTVA||Deployed as part of the ongoing search operation to find the GTD Galen. Withdrawn for repairs at the onset of the Battle of Good Hope.|
|Tortuga||GVG Anuket||Operational (?)||Ross 128||CFOT||Spotted and fired upon at a Coalition-held depot.|
|Tsar||GTC Aeolus||Destroyed||Ross 128||GTVA||Deployed as part of the ongoing search operation to find the GTD Galen. Served in all parts of the Battle of Good Hope, including the defense of the station and the recovery of the GTCv Boston.|
|Zeppelin||GTFr Triton||Operational||Ross 128||CFOT||Deployed in a quickly-aborted attempt to capture the GTC Tsar at the onset of the Battle of Good Hope.|
|Ship Name||Ship Class||Status||Serving System||Faction||Role and Major Engagements|
|Ajax||GTC Aeolus||Destroyed (?)||Altair||Local Bandits||Attacked rival bandits vying for control of GTI Chimera.|
|Avid||GTFr Triton||Operational||Multiple||Private Owner||Incidental involvement in a battle near the GTI Chicago.|
|Baltoris||GVFr Bes||Destroyed (?)||Alpha Centauri||Local Bandits||Attempted to steal cargo from GTVA forces in Alpha Centauri.|
|Battilus||GTFr Triton||Operational (?)||Multiple||GTVA||Delivered Mjolnir beam platforms from Vasuda to Beta Aquilae to slow the insurgent fleet.|
|Belmar||GTI Ganymede||Operational (?)||Alpha Centauri||NTF Remnant||Renegade staging ground attacked by GTVA bombers.|
|Benedicta||GTT Argo||Operational (?)||Aldebaran||GTVA||Evacuated personnel from Aldebaran.|
|Bilbeis||GVD Hatshepsut||Operational||Delta Serpentis||GTVA||Defended Delta Serpentis against the GTD Galen.|
|Cambria||GTT Argo||Destroyed||Altair||Altair Insurgency||Carried marines intended to attack the GTVA capitol in Delta Serpentis.|
|Chicago||GTI Arcadia||Destroyed||Alpha Centauri||GTVA||Responsible for security of the Aldebaran jump node in Alpha Centauri. Destroyed by the Altair fleet early in the Altair Insurgency.|
|Chieftain||GTFr Poseidon||Operational (?)||Alpha Centauri||GTVA||Removed a large bomb from the GTI Chicago's cargo depot.|
|Chimera||GTI Celestia||Operational (?)||Altair||GTVA||Primary GTVA outpost in Altair. Focal point of conflict between local bandit factions in Altair after being abandoned.|
|Colt||GTFr Poseidon||Destroyed||Alpha Centauri||NTF Remnant||Attempted a suicide-bombing against the GTI Chicago.|
|Corsair||GTC Fenris||Destroyed (?)||Alpha Centauri||NTF Remnant||Attacked by GTVA bombers at the RTI Belmar.|
|Cygnet||GTT Argo||Destroyed||Altair||Altair Insurgency||Carried marines intended to attack the GTVA capitol in Delta Serpentis.|
|Esso||GTFr Triton||Operational (?)||Multiple||GTVA||Delivered Mjolnir beam platforms from Vasuda to Beta Aquilae to slow the Altair fleet.|
|Faiyum||GVCv Sobek||Operational (?)||Beta Aquilae||GTVA||Attacked and destroyed the GTCv Lonestar and GVCv Thutmose.|
|Firestorm||GTC Aeolus||Destroyed||Altair||Altair Insurgency||Fell under bandit attack in Alpha Centauri, just prior to the Altair Insurgency. Destroyed by GTVA forces in an operation near the Delta Serpentis-Beta Aquilae jump node.|
|Frantic||GVFr Bes||Operational (?)||Multiple||Local Bandits||Attacked by renegade forces near the Aldebaran jump node in Alpha Centauri.|
|Galen||GTD Orion||Missing||Altair||Altair Insurgency||Flagship of the Altair fleet. Led the Altair Insurgency and played a large part in the destruction of the GTVA fleets in Aldebaran and Alpha Centauri and numerous other vessels en route to Delta Serpentis. After a major engagement in Delta Serpentis, disappeared into Ross 128.|
|George Smeed||GTT Argo||Destroyed||Altair||Altair Insurgency||Carried marines intended to attack the GTVA capitol in Delta Serpentis.|
|Haruspex||GTCv Deimos||Destroyed||Aldebaran||GTVA||Only military vessel from the Aldebaran fleet to reach Alpha Centauri during the Altair Insurgency. Suffered a catastrophic hull failure shortly after entering Alpha Centauri.|
|Hedetet||GVD Typhon||Operational (?)||Beta Aquilae||GTVA||Assisted in an attempt to stop the GTD Galen from reaching the Delta Serpentis jump node in Beta Aquilae.|
|Helena||GVT Satis||Destroyed (?)||Altair||Local Bandits||Attacked rival bandits vying for control of GTI Chimera.|
|Hella Fos||GTFr Triton||Operational (?)||Multiple||GTVA||Delivered Mjolnir beam platforms from Vasuda to Beta Aquilae to slow the Altair fleet.|
|Hellcat||GTC Fenris||Destroyed (?)||Alpha Centauri||NTF Remnant||Attacked by GTVA bombers at the RTI Belmar.|
|Hurricane||GTC Leviathan||Destroyed||Alpha Centauri||GTVA||Blockaded the Aldebaran node in Alpha Centauri.|
|Ironsides||GTT Argo||Destroyed||Altair||Altair Insurgency||Carried marines intended to attack the GTVA capitol in Delta Serpentis.|
|Kharga||GVC Mentu||Destroyed||Beta Aquilae||GTVA||Attacked by the GTCv Lonestar and GVCv Thutmose.|
|Kinetic||GTFr Poseidon||Destroyed (?)||Alpha Centauri||Local Bandits||Attempted to steal cargo from GTVA forces in Alpha Centauri.|
|Labre||GTM Hippocrates||Operational (?)||Aldebaran||GTVA||Evacuated personnel from Aldebaran.|
|Lawrence||GTT Elysium||Operational||Multiple||GTVA||Part of a Special Operations reconnaissance unit that passed through Aldebaran and Altair, after the Altair fleet left the two systems.|
|Lederman||GTSC Faustus||Operational||Multiple||GTVA||Part of a Special Operations reconnaissance unit that passed through Aldebaran and Altair, after the Altair fleet left the two systems.|
|Lonestar||GTCv Deimos||Destroyed||Altair||Altair Insurgency||Destroyed by GTVA forces in Beta Aquilae.|
|Magnitude||GTFr Triton||Operational||Multiple||Private Owner||Incidental involvement in a battle near the GTI Chicago.|
|Memnon||GVT Satis||Operational||Altair||Altair Insurgency||Recovered the GTC Firestorm from Alpha Centauri just prior to the Altair Insurgency.|
|Meteor||GTC Leviathan||Destroyed||Alpha Centauri||GTVA||Blockaded the Aldebaran node in Alpha Centauri.|
|Mirage||GVC Mentu||Destroyed||Altair||Altair Insurgency||Destroyed by GTVA forces in an operation near the Delta Serpentis-Beta Aquilae jump node.|
|Mustang||GTC Leviathan||Destroyed (?)||Alpha Centauri||NTF Remnant||Ambushed the GTC Spitfire on its approach to Alpha Centauri III. Later attacked by GTVA bombers at the RTI Belmar.|
|Nevis||GTFr Triton||Operational (?)||Multiple||GTVA||Delivered Mjolnir beam platforms from Vasuda to Beta Aquilae to slow the Altair fleet.|
|Odysseus||GTC Leviathan||Destroyed (?)||Altair||Local Bandits||Attacked rival bandits vying for control of GTI Chimera.|
|Ohio||GTC Leviathan||Destroyed||Altair||Altair Insurgency||Destroyed in Antares, during the Altair Insurgency.|
|Omaha||GTC Leviathan||Destroyed||Altair||Altair Insurgency||Destroyed in Antares, during the Altair Insurgency.|
|Orestes||GTC Fenris||Destroyed (?)||Altair||Local Bandits||Attacked rival bandits vying for control of GTI Chimera.|
|Palamedes||GVG Anuket||Destroyed (?)||Altair||Local Bandits||Attacked rival bandits vying for control of GTI Chimera.|
|Phoenicia||GTD Hecate||Operational||Alpha Centauri||GTVA||Flagship of the Alpha Centauri fleet, prior to the Altair Insurgency. Led most critical operations against the Altair insurgents, up to the final assault on the GTD Galen in Delta Serpentis.|
|Portcullis||GTD Orion||Destroyed||Alpha Centauri||GTVA||Blockaded the Aldebaran node in Alpha Centauri.|
|Putnam||GTFr Triton||Destroyed (?)||Multiple||NTF Remnant||Attacked by GTVA bombers at the RTI Belmar.|
|Raneb||GVCv Sobek||Destroyed||Alpha Centauri||GTVA||Blockaded the Aldebaran node in Alpha Centauri.|
|Ranger||GTFr Poseidon||Operational||Multiple||Private Owner||Incidental involvement in a battle near the GTI Chicago.|
|Serket||GVCv Sobek||Destroyed||Alpha Centauri||GTVA||Blockaded the Aldebaran node in Alpha Centauri.|
|Sorkal||GVFr Ma’at||Operational||Multiple||Private Owner||Incidental involvement in a battle near the GTI Chicago.|
|Spitfire||GTC Fenris||Destroyed||Alpha Centauri||GTVA||Led the assault against NTF remnants based on Alpha Centauri III. Shortly thereafter, placed on the blockade of the Aldebaran jump node in Alpha Centauri.|
|Telephim||GVFr Bes||Operational||Multiple||Private Owner||Incidental involvement in a battle near the GTI Chicago.|
|Thebes||GVCv Sobek||Destroyed||Vasuda||GTVA||Outmaneuvered by the Altair fleet, shortly after its entry into Vasuda.|
|Thunderbolt||GTC Leviathan||Destroyed (?)||Alpha Centauri||NTF Remnant||Attacked the GTC Firestorm in Alpha Centauri, during a recovery operation. Later attacked by GTVA bombers at the RTI Belmar.|
|Thutmose||GVCv Sobek||Destroyed||Altair||Altair Insurgency||Destroyed by GTVA forces in Beta Aquilae.|
|Torro||GTT Argo||Operational (?)||Alpha Centauri||Local Bandits||Attempted to capture civilian shipping vessels operating near the Aldebaran node in Alpha Centauri.|
|Troy||GVC Aten||Destroyed (?)||Altair||Local Bandits||Stolen from an Altair scrapyard and used to vie for control of the GTI Chimera.|
|Tura||GVC Mentu||Destroyed||Alpha Centauri||GTVA||Blockaded the Aldebaran node in Alpha Centauri.|
|Xanos||GTT Elysium||Destroyed (?)||Altair||Altair Insurgency||Carried repair teams to the GTCv Lonestar, after the corvette was disabled in Beta Aquilae.|
|Zed||GTT Argo||Destroyed (?)||Alpha Centauri||NTF Remnant||Attacked by GTVA bombers at the RTI Belmar.|
Second Shivan Incursion (Altair)
|Ship Name||Ship Class||Status||Serving System||Faction||Role and Major Engagements|
|Alchemy||SCv Moloch||Destroyed||--||Shivan Forces||Part of the support fleet attacking Altair.|
|Argoth||GVT Satis||Operational||Altair||GTVA||Carried repair crews to the GVC Mirage.|
|Athena||GTSC Faustus||Operational (?)||Altair||GTVA||Monitored the collapse of one jump node beyond Altair.|
|Capital||GTFr Triton||Operational (?)||Altair||GTVA||Carried a meson bomb to collapse a jump node in the system beyond Altair.|
|Chimera||GTI Celestia||Operational||Altair||GTVA||Primary GTVA outpost in Altair. The station became the last line of defense against the shivans.|
|Coal||SC Cain||Destroyed||--||Shivan Forces||Part of the support fleet attacking Altair.|
|Destiny||SD Ravana||Destroyed||--||Shivan Forces||One of the ships leading the shivan attack on Altair.|
|Detonation||SD Lucifer||Destroyed||--||Shivan Forces||One of the ships leading the shivan attack on Altair.|
|Diamond||SC Cain||Destroyed||--||Shivan Forces||Part of the support fleet attacking Altair.|
|Electrode||GTSC Faustus||Operational (?)||Altair||GTVA||Monitored the collapse of one jump node beyond Altair.|
|Expedience||GTS Hygeia||Operational||Altair||GTVA||Captured a shivan bomber during an operation to seal jump nodes in the system beyond Altair.|
|Falcon||GTG Zephyrus||Destroyed||Exploration Fleet||GTVA||Attempted to run the blockade of the Altair jump node.|
|Firestorm||GTC Aeolus||Operational (?)||Altair||GTVA||Led an operation to seal jump nodes in the system beyond Altair. Served on the line at the GTI Chimera.|
|Galen||GTD Orion||Operational||Altair||GTVA||Flagship of the Altair fleet. Deployed to Capella but was turned back after the star was destroyed. Secured the system beyond Altair after shivan control of that system was broken.|
|Ghoul||GTFr Triton||Destroyed||Exploration Fleet||GTVA||Destroyed at the onset of the shivan incursion in Altair.|
|Golem||GTM Hippocrates||Destroyed||Exploration Fleet||GTVA||Destroyed at the onset of the shivan incursion in Altair.|
|Granite||SC Cain||Destroyed||--||Shivan Forces||Part of the support fleet attacking Altair.|
|Guardian||SC Rakshasa||Destroyed||--||Shivan Forces||Escorted the SD Destiny into position near the Altair jump node.|
|Hydra||GTFr Triton||Operational (?)||Altair||Private Owner||Carried a meson bomb to collapse a jump node in the system beyond Altair.|
|Lead||SCv Moloch||Destroyed||--||Shivan Forces||Part of the support fleet attacking Altair.|
|Lonestar||GTCv Deimos||Operational (?)||Altair||GTVA||Led an operation to seal jump nodes in the system beyond Altair. Served on the line at the GTI Chimera.|
|Mirage||GVC Mentu||Operational||Altair||GTVA||Deployed to Capella but was turned back after the star was destroyed. Secured the system beyond Altair after shivan control of that system was broken.|
|Moridor||SC Cain||Destroyed||--||Shivan Forces||Sent to interfere with node-collapsing operations in the system beyond Altair.|
|Mortu||SCv Moloch||Destroyed||--||Shivan Forces||Sent to interfere with node-collapsing operations in the system beyond Altair.|
|Nova||SC Lilith||Destroyed||--||Shivan Forces||Sent to interfere with node-collapsing operations in the system beyond Altair.|
|Ohio||GTC Leviathan||Operational (?)||Altair||GTVA||Served on the line at the GTI Chimera.|
|Omaha||GTC Leviathan||Operational (?)||Altair||GTVA||Blockaded the Altair node against the exploration fleet, prior to the shivan incursion into Altair. Served on the line at the GTI Chimera.|
|Platinum||SC Cain||Destroyed||--||Shivan Forces||Part of the support fleet attacking Altair.|
|Razor||SC Rakshasa||Destroyed||--||Shivan Forces||Sent to interfere with node-collapsing operations in the system beyond Altair.|
|Relinquish||SD Ravana||Destroyed||--||Shivan Forces||One of the ships leading the shivan attack on Altair.|
|Retorphim||SC Cain||Captured||--||Shivan Forces||Abandoned by the shivans during their attack on Altair and subsequently captured by GTVA and Special Operations forces.|
|Silver||SCv Moloch||Destroyed||--||Shivan Forces||Part of the support fleet attacking Altair.|
|Sly||SFr Dis||Destroyed||--||Shivan Forces||Attacked during a mop-up operation in the system beyond Altair.|
|Spectre||GTSC Faustus||Destroyed||Exploration Fleet||GTVA||Destroyed at the onset of the shivan incursion in Altair.|
|Swiftwind||GTT Elysium||Operational||Altair||GTVA||Carried capture teams to the SC Retorphim.|
|Thesius||SCv Eris||Destroyed||--||Shivan Forces||First shivan vessel spotted in the system beyond Altair. Destroyed the exploration fleet and later fell under attack by GTVA bombers.|
|Thutmose||GVCv Sobek||Operational (?)||Altair||GTVA||Served on the line at the GTI Chimera.|
|Titan||GTFr Triton||Operational (?)||Altair||Private Owner||Carried a meson bomb to collapse a jump node in the system beyond Altair.|
|Torment||SCv Moloch||Destroyed||--||Shivan Forces||Attacked by GTVA bombers just beyond the Altair node.|
|Troy||GVC Aten||Operational (?)||Altair||GTVA||Recovered from a scrapyard for use in an attack against the shivan fleet in Altair, then re-mothballed.|
|Wind||GTA Charybdis||Destroyed||Altair||GTVA||Part of a suicide attack against the smaller shivan warships sent to attack Altair.|
Second Shivan Incursion (Capella)
|Ship Name||Ship Class||Status||Serving System||Faction||Role and Major Engagements|
|Alamo||GTC Leviathan||Operational (?)||Displaced (Capella)||GTVA||Sortied to defend the GVD Koreth in Gamma Draconis.|
|Alexandria||GTC Aeolus||Operational (?)||Displaced (Capella)||GTVA||Engaged shivan forces leading the juggernaut fleet to Capella.|
|Armor||GVT Satis||Operational (?)||Displaced (Capella)||GTVA||Carried repair crews to the GVD Koreth.|
|Babylon||GTCv Deimos||Destroyed||Altair||GTVA||Destroyed while on assignment in Capella.|
|Cairo||GVD Hatshepsut||Destroyed||Altair||GTVA||Destroyed while on assignment in Capella.|
|Calypso||GVCv Sobek||Operational (?)||Displaced (Capella)||GTVA||Sortied to defend the GVD Koreth in Gamma Draconis.|
|Comar||SC Lilith||Destroyed||--||Shivan Forces||Part of a task force leading the juggernaut fleet to Capella.|
|Dormen||SD Demon||Destroyed||--||Shivan Forces||Part of a task force leading the juggernaut fleet to Capella.|
|Elexis||GVCv Sobek||Destroyed||Altair||GTVA||Destroyed while on assignment in Capella.|
|Elub||SCv Moloch||Destroyed||--||Shivan Forces||Part of a task force leading the juggernaut fleet to Capella.|
|Eris||SCv Eris||Destroyed||--||Shivan Forces||Encountered and destroyed by a GTVA patrol in the nebular theater.|
|Ezor||SC Lilith||Destroyed||--||Shivan Forces||Part of a task force leading the juggernaut fleet to Capella.|
|Gore||SD Ravana||Destroyed||--||Shivan Forces||Attacked the GVD Koreth in Gamma Draconis.|
|Koreth||GVD Hatshepsut||Operational (?)||Displaced (Capella)||GTVA||Aided the attack against the SJ Twilight in Gamma Draconis.|
|Krag||SC Lilith||Destroyed||--||Shivan Forces||Part of a task force leading the juggernaut fleet to Capella.|
|Reaper||GVA Setekh||Destroyed||Capella||GTVA||Part of a suicide attack against the SJ Twilight.|
|Reken||SC Rakshasa||Destroyed||--||Shivan Forces||Part of a task force leading the juggernaut fleet to Capella.|
|Renewal||GVC Mentu||Destroyed||Altair||GTVA||Destroyed while on assignment in Capella.|
|Selamf||SCv Moloch||Destroyed||--||Shivan Forces||Part of a task force leading the juggernaut fleet to Capella.|
|Tormet||SC Rakshasa||Destroyed||--||Shivan Forces||Part of a task force leading the juggernaut fleet to Capella.|
|Whit||GTC Leviathan||Destroyed||Altair||GTVA||Destroyed while on assignment in Capella.|