FreeSpace Wiki - User contributions [en]

Getting FreeSpace

2011-05-06T09:05:05Z

BlueFlames: Why would we *ever* suggest that piracy as a means of acquiring FreeSpace?

There are a few different ways of getting your hands on FreeSpace 2.

==[http://www.gog.com/en/frontpage Good Old Games] (GOG)==

A new digital distribution service for classic games, including both FreeSpace titles, which launched in late 2008. GOG is selling both games for $5.99 (USD) with no digital rights management strings attached. Definitely the most highly-recommended means of obtaining the games at the present time.

==Physical Copies==

There are still copies of FS2 floating around, but finding them is not always easy.

So where could you grab a copy?
* [http://search.ebay.com/FreeSpace-2 There are usually some up for sale on eBay].
* A Bargain Bin.

FreeSpace 2 has not been mass-produced for several years, so checking places that sell used software is your only recourse if you need to buy locally. The original FreeSpace has been out-of-print (so to speak) for even longer, but luckily for you you can play FS1 by getting the [[FreeSpace Port]], but you'll need FS2 set up first.





[[Category:Acquiring FreeSpace]]
[[Category:Source Code Project]]

EMP Missile

2010-05-31T15:46:01Z

BlueFlames: Redirected page to GTM EMP Adv.

#REDIRECT [[GTM EMP Adv.]]

Talk:SJD Sathanas

2009-06-23T04:00:40Z

BlueFlames: I win, because it's hard-coded.

- I feel that some FRED newbies need to know the difference between the SJ and the SJD Sathanas ships, so I created this article in about 5-6 minutes. [[User:Sigtau|Sigtau]] 15:23, 8 June 2009 (UTC)

==minicap.pof==

"minicap.pof" (the low-poly Sathanas model) was not used to create the target view illusion, I think it was an entirely separate attempt to do the same thing, but was rejected by [V] in favor of this solution. Also, the model minicap.pof is not small either. In fact it has similar dimensions to the normal Sathanas. Just though I should clarify my previous edit in case it caused any confusion. - [[User:Snail|Snail]] 21:32, 8 June 2009 (UTC)
:In retail FS2, minicap.pof does appear in the target view window, when targeting an SJD Sathanas. I don't know if that's been changed in FSOpen or not, though. -- [[User:BlueFlames|BlueFlames]] 03:18, 9 June 2009 (UTC)
::I doesn't. Taken from the retail table:
$Name: SJD Sathanas
$Short name: SDev
$Species: Shivan
+Tech Description:
XSTR("A Sathanas, off in the distance.", 3168)
$end_multi_text
$POF file: Blip.pof
$POF target file: SuperCap2S-01.pof
$Detail distance: (0, 2500, 5000, 14000)
::The phrase "minicap.pof" does not appear anywhere in the FS2 retail ships table. - [[User:Snail|Snail]] 16:26, 22 June 2009 (UTC)
:::[http://home.comcast.net/~blueflames/LionTarget2.png External camera shot of the SJD Sathanas] and [http://home.comcast.net/~blueflames/LionTarget1.png minicap.pof sitting in my target view box]. Are you still going to insist that minicap.pof isn't used, without testing it? -- [[User:BlueFlames|BlueFlames]] 04:00, 23 June 2009 (UTC)

Talk:Machina Terra

2009-06-13T03:27:40Z

BlueFlames: /* Authors */

==Authors==
Many of the community members listed as authors don't have the MT badge on HLP (ex. Woomeister). Many other of them are inactive. Should they be considered team members, even if they're not contributing to Machina Terra? --- [[User:Mobius|Mobius]]
:I'm pretty sure the project has been declared dead, so '''nobody''' is presently contributing to it. That said, the list of former team members should be maintained for archival purposes. -- [[User:BlueFlames|BlueFlames]] 03:27, 13 June 2009 (UTC)

GTD Hecate

2009-06-10T06:03:40Z

BlueFlames: Undo revision 23212 by Chammy (Talk) - Read the veteran comments policy, please.

{{FS12_Ships}}{{shipimage|image=[[Image:Hecate320X240.jpg]]|caption=The GTD Hecate}}The '''GTD Hecate'''-class of destroyers is the advanced, more developed version of the [[GTD Orion|GTD ''Orion'']]. Specifically developed to mount advanced weaponry such as flak or beam cannons, it meant a threat to any capital-sized ships.

One of the most famous of these destroyers was the [[GTD Aquitaine|GTD ''Aquitaine'']], a ship that played a major part in the [[Second Shivan Incursion]].

==Description:==

===FS2 Tech Room Description===
The new GTD Hecate class of destroyers is replacing the Orion class as the flagship of Terran battle groups. More heavily armed than the Orion, the Hecate also carries over 150 combat spacecraft and a crew of 10,000. The GTD Aquitaine is a superb example of this new ship class, serving as the flagship of the Capella-based 3rd Fleet.

===Developer Notes===
None

===Name origin===
At a certain stage in Greek mythology, Hecate was the goddess of hunting and wilderness, much like [[GTB Artemis|Artemis]]. Later she was seen as the goddess of witchcraft.

==Performance:==
===Statistics===
{{Ship Stats|Destroyer|Unknown|N/A|15.0|N/A|N/A|100 000|N/A|2174}}{|-
| style="width:200px"|'''[[Technical_Terms_and_Definitions#Fighter Complement|Fighter Complement]]'''
| style="width:200px"|150+ fightercraft
|}

===Armaments===

*'''[[Technical_Terms_and_Definitions#Turrets|Turrets]]'''
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=2 style="background:#300505;"| '''FreeSpace 2'''
|- align="center"
| style="width:120px" |Turret Type
| style="width:60px" |Amount
|- align="center"
| [[Terran Turret]]
| 5
|- align="center"
| [[Terran Huge Turret]]
| 1
|- align="center"
| [[Standard Flak]]
| 6
|- align="center"
| [[Long Range Flak]]
| 2
|- align="center"
| [[Heavy Flak]]
| 2
|- align="center"
| [[AAAf|Anti-Fighter Beam]]
| 6
|- align="center"
| [[TerSlash|Terran Slashing Beam]]
| 4
|- align="center"
| [[BGreen|Big Green Beam]]
| 1
|}

==Veteran Comments==
{{Comment|''The Hecate is admirably armed for killing fighters and deals with fightercraft threats far, far better than an Orion. However, if you need to form a battle line and handle big targets, the Hecate is not the ship you want.''

''My best guesses as to why the Hecate would, or could replace the [[GTD Orion|Orion]] is that it costs much less, and that it holds an extra four and a half squadrons. (There are twelve combat-craft in a squadron.) Also I suppose in an optimal battle scenario (if there is such a thing) the Hecate would be escorted by corvettes and cruisers.''

''It does work well in a surgical strike role, hitting smaller warships with its considerable forward firepower before they have much chance to fight back. But if attacked by a warship from any direction but the front, it's in real trouble and needs to either leave fast or rely on bomber wings to take care of the threat.''

''Oddly enough, I found this to be more vulnerable to bombers than an Orion.''

''It depends at which side you decide to attack the Hecate. Because it has such a large surface area, it needs many more effective turrets to cover every nook and cranny of the Hecate. At certain angles, the Hecate has enough turrets to easily destroy a lot of bombers, but at others, it has far less coverage.''

''I disagree with the previous posts. The Hecate is designed to be able to defend itself from all angles and not allow itself to be outflanked. While it is not as effective against other destroyers as an Orion, its turret placement means it would be able to outmaneuver other ships and attack them from angles they would not be able to return fire from.''

''It can be outflanked. At certain angles it is a fortress, but at others you can easily fly through light turret fire, or just disable the turret. In addition to this, the Hecate has exactly the same top speed and rotation time as the Orion. In effect, the Orion could also outmaneuver ships and attack from angles that are unguarded. I find the Hecate inferior to the Orion in almost every way.''

''I wouldn't criticize it for its armament so much as the placement of its armament. While the Hecate is well-armed, and can generally pepper targets approaching it from a range, it has several blind spots. Any fighter or bomber approaching from the front will face minimal anti-fighter fire and can hide in the shadow of the frontal fins and blast away, to name the most significant. The rear TerSlash is useless, because it has a very limited field of fire, and is as a weapon especially useless in the rear. In addition, the Hecate is as slow as the Orion, and has no more armour than the Orion. The forward BGreen and TerSlash, while making the destroyer relatively powerful if aimed properly, is outdone by other destroyers. I guess that the fighter bay has got to count for something but overall the Hecate is ruined potential. It could use a serious armament revision, and some of the turrets could be moved to different spots on the hull. ''

''The massive turrets on top carry only Heavy Flak. This leaves them rather unfulfilling, and their size means they're easily taken out, leaving the top part of the ship more or less open to bomber attack.''}}

[[Category:Ship]]

Talk:SJD Sathanas

2009-06-09T03:18:38Z

BlueFlames:

SJD Sathanas

2009-06-09T03:16:29Z

BlueFlames:

{{shipimage|image=[[Image:Sjd.png]]|caption=SJD Sathanas}}

The '''SJD ''Sathanas''''' was a decoy version of the SJ ''Sathanas'' used in the [[FreeSpace 2]] mission, [[Into the Lion's Den]]. Up close, it is a simple textured tetrahedron (a polyhedron with four faces), but in the target view, it appears to be a [[SJ Sathanas|''Sathanas'']]-class ship. The reason this was used was to save memory on the older machines, and in Into the Lion's Den, there are seven ''Sathanas''-class juggernauts that jump in.

Because of the amount of distance between the player and the ships in the aforementioned mission, and the fact that the player only has 15 minutes to complete the mission, the player never actually gets to see the tetrahedronal shape of this ship.

Many user-made mods have deleted the SJD from the list of available ships to save room, since the ship's only use was fulfilled in the official ''FreeSpace 2'' campaign.

On a related note, there was a low-poly ''Sathanas'' model found in the retail VP files. This model is used in the target view window, when an SJD Sathanas is targeted.

Not to be confused with the actual ''[[SJ Sathanas]]''.

[[category:Ship]]

Talk:GTFr Triton

2009-05-30T17:05:56Z

BlueFlames:

Do you guys think there is sufficient info to "assume" that the Triton is created by Triton Dynamics? [[TC-TRI]] containers are, there's a chance the Triton is too. - [[User:Snail|Snail]] 13:12, 30 May 2009 (UTC)
:Nope. The containers could have been designed by one company, while the manufacturing process was subcontracted to Triton Dynamics. There also aren't many (any?) ships we '''know''' to be named for the company that produces them, so there's no basis to make that assumption. -- [[User:BlueFlames|BlueFlames]] 17:05, 30 May 2009 (UTC)

Second Front

2009-05-05T03:51:04Z

BlueFlames: Minor touchups and a "See Also" section.

==General Info==
'''Release Date:''' December 14, 2003 
'''Original Authors:''' Michael '[[User:BlueFlames|BlueFlames]]' Ashworth 
'''Missions:''' 7 
'''Mods included:''' minor ship and weapon table edits 
'''Designed/Tested using:''' FreeSpace 2 Retail v1.2

==Story==

Though the [[Shivan]] invasion of [[Capella]] was certainly one of the most significant occurrences of its time, it did not happen in a vaccuum of events.

As the final evacuation of Capella is put in motion, you are deployed to the other side of the galaxy for an assignment in [[Altair]]. On the other side of the jump node to uncharted space, an exploration convoy has returned after decades away. Oblivious to events elsewhere in the [[GTVA]], the explorers do not understand why they must face continuous delays to be readmitted to alliance space and become evermore belligerent. A [[Leviathan]] cruiser is sent to blockade the node against the convoy, but this show of force only serves to heighten tensions.

You arrive on the scene when the GTC ''Omaha'' requests fighter cover and tensions reach a boiling point.

==Player Comments==

==See Also==

* ''[[Artifice]]'' - Sequel to ''Second Front''
* [[user:BlueFlames|BlueFlames' user page]] - Contains exhaustive information about the events surrounding and following ''Second Front''

==Related Links==
* '''[http://home.comcast.net/~blueflames/SF1site/ Campaign Website]''' 
* '''[http://www.freespacemods.net/download.php?view.33 Download Mirror | FreeSpaceMods.net]''' 
* [http://www.hard-light.net/forums/index.php/topic,19547.0.html Release thread | Hard-Light.net] 

[[Category:User-made_Campaigns]]

Artifice

2009-05-05T03:51:01Z

BlueFlames: Minor touchups and a "See Also" section.

==General Info==
'''Release Date:''' January 7, 2008 
'''Original Authors:''' Michael 'BlueFlames' Ashworth 
'''Missions:''' 11 
'''Mods included:''' minor ship and weapon table edits 
'''Designed/Tested using:''' FreeSpace 2 Retail v1.2

==Story==

Following the destruction of [[Capella]], the [[Galactic Terran-Vasudan Alliance]] has its sights set on regaining stability and rebuilding the lives that had been shattered by the [[shivan]] invasion. Unfortunately, how to go about returning to normality is an issue disputed within the upper eschelons of GTVA Command.

Such high-level debates are none of your concern, though, as a transfer pilot to the 121st Shadow Daggers, in [[Alpha Centauri]]. Still scarred from battles with the [[Neo-Terran Front]] and facing the same economic downturn as the rest of the the Alliance, the officers in this system have more practical and immediate concerns to deal with than how the tax code should treat Capellan refugees or even how the military fleet should look in twenty years' time. Former NTF elements still mark [[vasudan]] civilians for death, and elements of the population have turned to violence and piracy to acquire the resources they desire.

You have your work cut out for you, even before one of these nebulous "high-level issues" explodes, in a very real way, into your corner of space.

==Player Comments==

Artifice is...less than good. It is difficult, certainly; unreasonably so, and a lot of the difficulty stems from cheap mission designer tricks rather than actual combat. As a storytelling device it is not much good either; and there are noticeable bugs in some of the missions. Not show-stopping, but obvious nonetheless. Overall, a difficult campaign to recommend. -ngtm1r

==See Also==

* ''[[Second Front]]'' - Predecessor to ''Artifice''
* [[user:BlueFlames|BlueFlames' user page]] - Contains exhaustive information about the events surrounding and following ''Artifice''

==Related Links==
* '''[http://home.comcast.net/~blueflames/SF2site/ Campaign Website]''' 
* '''[http://www.freespacemods.net/download.php?view.79 Download Mirror | FreeSpaceMods.net]''' 
* [http://www.hard-light.net/forums/index.php/topic,51387.msg1038544.html Release Thread | Hard-Light.net]

[[Category:User-made_Campaigns]]

Ancient-Shivan War (FS1)

2009-05-02T03:13:00Z

BlueFlames: Explanation of the name missed the forest through the trees.

This war fought between [[Ancient]] and [[Shivan]] forces ended with the extinction of the Ancients nearly 8,000 years before the main FreeSpace continuity. It's worth noting that the name used to define the war cannot be found in any canon sources - it's the name the community has given to the war, in light of the principal combatants.

{{stub}}

[[Category: History]]

User:BlueFlames

2009-04-18T15:29:58Z

BlueFlames: /* Ship List - Third Shivan Incursion */ A couple of minor ships that escaped my memory earlier.

{{non-canon}}
{{Spoiler | [[FreeSpace 2]], [[Second Front]], [[Artifice]], and campaigns under development.}}

'''Author's Note:''' Proofreading of this page is welcome. Please seek consultation on the [[user talk:BlueFlames|talk page]] before making any substantial alterations.

==Catharsis 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 Catharsis continuity.)

The Catharsis story arc tracks the GTVA through a slow, seven-year decline in power, beginning with the [[Second Shivan Incursion|Shivan Incursion of 2367]]. This decline culminates with a third and final shivan incursion, which proves to be the death knell of the [[Galactic Terran-Vasudan Alliance]].

===[[Second Front]]===

November 24, 2367: Massive evacuations of the densely-populated [[Capella | Capella system]] begin. Millions of refugees flood into [[Epsilon Pegasi]] and [[Vega]].

November 26, 2367: SJ ''Twilight'', a [[SJ Sathanas | Sathanas-class juggernaut]] leading the fleet moving toward Capella, is destroyed in [[Gamma Draconis]] by an operation titled ''Project Roadblock''.

November 26, 2367: An exploration convoy, seeking to reenter [[GTVA | GTVA space]] through the [[Altair | Altair system]] is destroyed by [[shivan | shivan forces]]. Martial law declared in Altair.

November 27, 2367: The Altair fleet requests tactical support from [[Special Operations Command | 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 | 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|GTD ''Nereid'']] and [[GTD Bastion|GTD ''Bastion'']], packed with [[meson bomb | 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.

===Interim Period===

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.

May 16, 2368: Production of [[GTC Aeolus|Aeolus-class cruisers]] resumes in shipyards in [[Polaris]] and [[Laramis]]. The GTC Tsar, fourth in this new production line, is scheduled for launch in November.

===[[Artifice]]===

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 [[FreeSpace 2 Terran Ship Database#GTD Phoenicia | 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.

===Interim Period===

April 1, 2372: The GTVA Security Council authorizes the design of production models of the [[NTF Iceni | Iceni-class corvette]] and [[GTD Hades | Hades-class superdestroyer]].

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.

===Bounded===

February 1, 2374: The GTD ''Galen'' is discovered derelict near the debris field of the [[FreeSpace 1 Terran Ship Database#GTI Riviera | 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 7, 2374: Epsilon Eridani node discovered in Ross 128. Shivan forces begin appearing in greater number and in other systems, including [[Luyten 726-8]], [[Laramis]], [[Ikeya]], [[Mirfak]], and Altair.

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 [[Destruction of the SD Lucifer|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.

During the [[Hades Rebellion|Galactic Terran Intelligence rebellion]], Bast found himself serving well away from any major battles, guarding convoys and installations in [[Ikeya]] for the duration of 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.

===[[Galactic Terran-Vasudan Intelligence]]===

Since the Antares Federation controlled [[Beta Aquilae]], while the [[The Beta Aquilae Convention|BETAC treaty]] was being negotiated, they had a measure of political leverage that the [[Parliamentary Vasudan Empire|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|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 [[Aken Bosch|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 [[Second Shivan Incursion|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.

===Altair Insurgency===

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.

===Post-Insurgency===

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.

==Fall of [[Khonsu II]]==

''Section Pending''

==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 node|jump nodes]] leading to uncharted star systems, find new jump nodes, and seal them as well. Unfortunately, the destruction of a jump node required [[TC-Meson Bomb|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 [[Terran Turret|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 [[NTF Iceni|GTCv Iceni-class corvette]] had begun.

==Coalition for Free and Open Trade==

===History===

====Formation and Composition====

As the [[Galactic Terran-Vasudan Alliance|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.

====Interbandit Conflict====

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.

====Unification====

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 [[user:BlueFlames#GTI_Good_Hope|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 [[NTF Iceni|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.

====Post-Unification Strategy====

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|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.

===Famous Persons===

====Expatriate Menkaura====

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 Emperor Monthu. Menkaura was declared to be a nonperson by the [[Parliamentary Vasudan Empire|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''==

===Station History===

Construction on the ''Good Hope'' began in 2342 as a replacement to [[FreeSpace 1 Terran Ship Database#GTI Riviera|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 [[GTI Ganymede|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 [[NTF Iceni|Iceni-class corvette]] and was one of two shipyards assigned to construct new [[GTD Hecate|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 [[GTD Orion|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 Complement and Defenses===

{| border="1" cellpadding="2"
|+ '''Standard Fighter Complement'''
!width="120"|Fighter Class
!width="100"|Amount
(2342, proposed)
!width="50"|Amount
(2344)
!width="50"|Amount
(2368)
!width="50"|Amount
(2373)
|-
! [[GTF Apollo]]
| align="center" | 8 || align="center" | 8 || align="center" | 0 || align="center" | 0
|-
! [[GTF Valkyrie]]
| align="center" | 8 || align="center" | 4 || align="center" | 0 || align="center" | 0
|-
! [[GTF Ulysses]]
| align="center" | 4 || align="center" | 8 || align="center" | 8 || align="center" | 4
|-
! [[GTF Hercules]]
| align="center" | 4 || align="center" | 4 || align="center" | 0 || align="center" | 0
|-
! [[GTF Hercules Mark II|GTF Hercules Mk. II]]
| align="center" | 0 || align="center" | 0 || align="center" | 4 || align="center" | 4
|-
! [[GTF Loki]]
| align="center" | 12 || align="center" | 12 || align="center" | 8 || align="center" | 4
|-
! [[GTF Perseus]]
| align="center" | 0 || align="center" | 0 || align="center" | 8 || align="center" | 8
|-
! [[GTF Pegasus]]
| align="center" | 0 || align="center" | 0 || align="center" | 4 || align="center" | 8
|-
! [[GTF Myrmidon]]
| align="center" | 0 || align="center" | 0 || align="center" | 4 || align="center" | 8
|-
! [[GTB Artemis]]
| align="center" | 0 || align="center" | 0 || align="center" | 0 || align="center" | 4
|-
! [[GTB Medusa]]
| align="center" | 4 || align="center" | 4 || align="center" | 4 || align="center" | 0
|}

In addition to its fighter complement and twelve sentry guns, two [[GTC Fenris|Fenris-class cruisers]] were assigned to patrol the station, after its completion in 2344. The GTC Kelsan, a [[GTC Leviathan|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''==

'''''Codex Anathema''''' is the name of a book, apparently written by [[Aken Bosch]], prior to his disappearance in the [[Nebula System|shivan nebula]]. One of the [[Special Operations Command|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.

===Origin===

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 [[Official Volition Node Map|Allied space]]. When he happened upon information regarding the [[Knossos|Knossos portal]], the physical obstacle became surmountable. As his rebellion gained momentum, and Bosch resumed the [[Galactic Terran Intelligence|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 [[Neo-Terran Front|NTF]] fleet to capture the [[Gamma Draconis| 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 [[Galactic Terran-Vasudan Alliance|GTVA]]'s debut of the [[GTVA Colossus|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.

===Contents===

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 [[NTF Iceni|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.

==Ship List==

Includes all named ships appearing in the Catharsis continuity, through the ''Battle of Good Hope''.

Notes
*Tables ordered from most recent events to oldest.
*Status
: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, as no assumption is made regarding their evacuation or loss during the Capella supernova.
*Factions
:'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.

===Third Shivan Incursion===
'''(List incomplete and subject to change.)'''

{| border="1" cellpadding="2"
|+ '''Third Shivan Incursion'''
! width="100" | Ship Name
! width="100" | Ship Class
! width="90" | Status
! width="75" | Serving System
! width="75" | Faction
! Role and Major Engagements
|-
! Asynjur
| [[SFr Dis]] || Destroyed (?) || Epsilon Eridani || Shivan Forces || Encountered at depot, just inside Epsilon Eridani.
|-
! Gaena
| [[SC Cain]] || Destroyed (?) || Epsilon Eridani || Shivan Forces || Principle defense of a depot just inside Epsilon Eridani.
|-
! Halifax
| [[GTD Hades]] || Unknown || Sirius || GTVA || Sister ship to the GTD Liberator. Dropped out of contact with Allied forces, when the GTVA's long range communication grid collapsed.
|-
! Hidimba
| [[SD Ravana]] || Operational (?) || Epsilon Eridani || Shivan Forces || Attacked a GTVA reconnaissance unit.
|-
! Kullu
| [[SD Ravana]] || Operational || Epsilon Eridani || Shivan Forces || Encountered by a GTVA reconnaissance unit.
|-
! Liberator
| [[GTD Hades]] || Destroyed || Ross 128 || GTVA || Deployed ahead of schedule to counter shivan advances into Ross 128. Eventually led a major convoy from Ross 128, during the system's evacuation.
|-
! Mishnah
| [[SFr Asmodeus]] || Destroyed (?) || Epsilon Eridani || Shivan Forces || Suffered engine failure in the vicinity of a GTVA reconnaissance operation.
|-
! Tholos
| [[SCv Moloch]] || Operational (?) || Ross 128 || GTVA || Captured from the shivans, while escorting a convoy, before leading a recon mission to Epsilon Eridani.
|-
! [[FreeSpace 2 Vasudan Ship Database#GVD_Toeris|Toeris]]
| [[GVD Typhon]] || Unknown || Ross 128 || GTVA || Led the final convoy from Ross 128. Dropped out of communication with Allied forces, after entering Laramis.
|-
! Vajra
| [[SC Rakshasa]] || Operational (?) || Epsilon Eridani || Shivan Forces || Encountered alongside the SD Kullu.
|}

===''Battle of Good Hope''===

{| border="1" cellpadding="2"
|+ '''''Battle of Good Hope'''''
! width="100" | Ship Name
! width="100" | Ship Class
! width="90" | Status
! width="75" | Serving System
! width="75" | 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
| [[NTF Iceni | 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
| [[GVFr Satis|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.
|-
! [[FreeSpace 2 Terran Ship Database#GTCv Naxos | 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.
|}

===Altair Insurgency===

{| border="1" cellpadding="2"
|+ '''Altair Insurgency'''
! width="100" | Ship Name
! width="100" | Ship Class
! width="90" | Status
! width="100" | Serving System
! width="100" | 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.
|-
! [[FreeSpace 2 Vasudan Ship Database#GVD Hedetet | 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
| [[GVFr Satis|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
| [[GVFr Satis|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''.
|-
! [[FreeSpace 2 Terran Ship Database#GTD Phoenicia | 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
| [[PVFr Ma%27at | 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''.
|-
! [[FreeSpace 2 Vasudan Ship Database#GVCv Thebes | 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)===

{| border="1" cellpadding="2"
|+ '''Second Shivan Incursion (Altair)'''
! width="100" | Ship Name
! width="100" | Ship Class
! width="90" | Status
! width="100" | Serving System
! width="95" | Faction
! Role and Major Engagements
|-
! Alchemy
| [[SCv Moloch]] || Destroyed || -- || Shivan Forces || Part of the support fleet attacking Altair.
|-
! Argoth
| [[GVFr Satis|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)===

{| border="1" cellpadding="2"
|+ '''Second Shivan Incursion (Capella)'''
! width="100" | Ship Name
! width="100" | Ship Class
! width="90" | Status
! width="100" | Serving System
! width="95" | 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
| [[GVFr Satis|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.
|}

==External Links==

*[http://home.comcast.net/~blueflames/SF1site/ Second Front website]
*[http://home.comcast.net/~blueflames/SF2site/ Artifice website]

Talk:Reciprocity

2009-04-18T15:05:23Z

BlueFlames: /* Mods and such */ Response.

==Mods and such==
I think Reciprocity should at the very least have a page dedicated to it's ships and species and such that have been used for other works. It might help to have them all in one place for easy view. I also have some information on the old campaign itself. -- [[User:BlueLion|BlueLion]] 07:21, 17 April 2009 (UTC)
:Then add that information. We'll help in formatting and such. Also please sign your talk page edits with: <nowiki>~~~~</nowiki> - [[User:TopAce|TopAce]] 16:58, 17 April 2009 (UTC)
::Is it really super important who said it? -- [[User:BlueLion|BlueLion]] 04:52, 18 April 2009 (UTC)
:::Yes. -- [[User:BlueFlames|BlueFlames]] 05:00, 18 April 2009 (UTC)
::::So, err what about the initial idea? - [[User:Snail|Snail]] 11:17, 18 April 2009 (UTC)
The page is a stub, albeit not marked as such. Add whatever information you find relevant. I'd put something up myself, but I don't know a thing about the campaign. -- [[User:BlueFlames|BlueFlames]] 15:05, 18 April 2009 (UTC)

Talk:Reciprocity

2009-04-18T05:00:51Z

BlueFlames: /* Mods and such */ Answer; short and sweet.

Second Front

2009-04-15T19:28:10Z

BlueFlames: /* Related Links */ A little more than just the download at the Comcast page.

==General Info==
'''Release Date:''' December 14, 2003 
'''Original Authors:''' Michael '[[User:BlueFlames|BlueFlames]]' Ashworth 
'''Missions:''' 7 
'''Mods included:''' minor ship and weapon table edits 
'''Designed/Tested using:''' FreeSpace 2 Retail v1.2

==Story==

Though the [[Shivan]] invasion of [[Capella]] was certainly one of the most significant occurrences of its time, it did not happen in a vaccuum of events.

As the final evacuation of Capella is put in motion, you are deployed to the other side of the galaxy for an assignment in [[Altair]]. On the other side of the jump node to uncharted space, an exploration convoy has returned after decades away. Oblivious to events elsewhere in the [[GTVA]], the explorers do not understand why they must face continuous delays to be readmitted to alliance space and become evermore belligerent. A [[Leviathan]] cruiser is sent to blockade the node against the convoy, but this show of force only serves to heighten tensions.

You arrive on the scene when the GTC Omaha requests fighter cover and tensions reach a boiling point.

==Player Comments==

==Related Links==
*'''[http://home.comcast.net/~blueflames/SF1site/ Campaign Website | Comcast.net]''' 
*'''[http://www.freespacemods.net/download.php?view.33 Download | FreeSpaceMods.net]''' 
*[http://www.hard-light.net/forums/index.php/topic,19547.0.html Release thread | Hard-Light Productions.net] 

[[Category:User-made_Campaigns]]

User:BlueFlames

2009-04-14T16:39:34Z

BlueFlames: Some links, spelling fixes, and a prefacing note.

{{non-canon}}
{{Spoiler | [[FreeSpace 2]], [[Second Front]], [[Artifice]], and campaigns under development.}}

'''Author's Note:''' Proofreading of this page is welcome. Please seek consultation on the [[user talk:BlueFlames|talk page]] before making any substantial alterations.

==Catharsis 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 Catharsis continuity.)

The Catharsis story arc tracks the GTVA through a slow, seven-year decline in power, beginning with the [[Second Shivan Incursion|Shivan Incursion of 2367]]. This decline culminates with a third and final shivan incursion, which proves to be the death knell of the [[Galactic Terran-Vasudan Alliance]].

===[[Second Front]]===

November 24, 2367: Massive evacuations of the densely-populated [[Capella | Capella system]] begin. Millions of refugees flood into [[Epsilon Pegasi]] and [[Vega]].

November 26, 2367: SJ ''Twilight'', a [[SJ Sathanas | Sathanas-class juggernaut]] leading the fleet moving toward Capella, is destroyed in [[Gamma Draconis]] by an operation titled ''Project Roadblock''.

November 26, 2367: An exploration convoy, seeking to reenter [[GTVA | GTVA space]] through the [[Altair | Altair system]] is destroyed by [[shivan | shivan forces]]. Martial law declared in Altair.

November 27, 2367: The Altair fleet requests tactical support from [[Special Operations Command | 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 | 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|GTD ''Nereid'']] and [[GTD Bastion|GTD ''Bastion'']], packed with [[meson bomb | 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.

===Interim Period===

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.

May 16, 2368: Production of [[GTC Aeolus|Aeolus-class cruisers]] resumes in shipyards in [[Polaris]] and [[Laramis]]. The GTC Tsar, fourth in this new production line, is scheduled for launch in November.

===[[Artifice]]===

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 [[FreeSpace 2 Terran Ship Database#GTD Phoenicia | 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.

===Interim Period===

April 1, 2372: The GTVA Security Council authorizes the design of production models of the [[NTF Iceni | Iceni-class corvette]] and [[GTD Hades | Hades-class superdestroyer]].

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.

===Bounded===

February 1, 2374: The GTD ''Galen'' is discovered derelict near the debris field of the [[FreeSpace 1 Terran Ship Database#GTI Riviera | 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 7, 2374: Epsilon Eridani node discovered in Ross 128. Shivan forces begin appearing in greater number and in other systems, including [[Luyten 726-8]], [[Laramis]], [[Ikeya]], [[Mirfak]], and Altair.

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 [[Destruction of the SD Lucifer|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.

During the [[Hades Rebellion|Galactic Terran Intelligence rebellion]], Bast found himself serving well away from any major battles, guarding convoys and installations in [[Ikeya]] for the duration of 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.

===[[Galactic Terran-Vasudan Intelligence]]===

Since the Antares Federation controlled [[Beta Aquilae]], while the [[The Beta Aquilae Convention|BETAC treaty]] was being negotiated, they had a measure of political leverage that the [[Parliamentary Vasudan Empire|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|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 [[Aken Bosch|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 [[Second Shivan Incursion|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.

===Altair Insurgency===

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.

===Post-Insurgency===

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.

==Fall of [[Khonsu II]]==

''Section Pending''

==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 node|jump nodes]] leading to uncharted star systems, find new jump nodes, and seal them as well. Unfortunately, the destruction of a jump node required [[TC-Meson Bomb|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 [[Terran Turret|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 [[NTF Iceni|GTCv Iceni-class corvette]] had begun.

==Coalition for Free and Open Trade==

===History===

====Formation and Composition====

As the [[Galactic Terran-Vasudan Alliance|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.

====Interbandit Conflict====

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.

====Unification====

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 [[user:BlueFlames#GTI_Good_Hope|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 [[NTF Iceni|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.

====Post-Unification Strategy====

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|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.

===Famous Persons===

====Expatriate Menkaura====

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 Emperor Monthu. Menkaura was declared to be a nonperson by the [[Parliamentary Vasudan Empire|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''==

===Station History===

Construction on the ''Good Hope'' began in 2342 as a replacement to [[FreeSpace 1 Terran Ship Database#GTI Riviera|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 [[GTI Ganymede|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 [[NTF Iceni|Iceni-class corvette]] and was one of two shipyards assigned to construct new [[GTD Hecate|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 [[GTD Orion|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 Complement and Defenses===

{| border="1" cellpadding="2"
|+ '''Standard Fighter Complement'''
!width="120"|Fighter Class
!width="100"|Amount
(2342, proposed)
!width="50"|Amount
(2344)
!width="50"|Amount
(2368)
!width="50"|Amount
(2373)
|-
! [[GTF Apollo]]
| align="center" | 8 || align="center" | 8 || align="center" | 0 || align="center" | 0
|-
! [[GTF Valkyrie]]
| align="center" | 8 || align="center" | 4 || align="center" | 0 || align="center" | 0
|-
! [[GTF Ulysses]]
| align="center" | 4 || align="center" | 8 || align="center" | 8 || align="center" | 4
|-
! [[GTF Hercules]]
| align="center" | 4 || align="center" | 4 || align="center" | 0 || align="center" | 0
|-
! [[GTF Hercules Mark II|GTF Hercules Mk. II]]
| align="center" | 0 || align="center" | 0 || align="center" | 4 || align="center" | 4
|-
! [[GTF Loki]]
| align="center" | 12 || align="center" | 12 || align="center" | 8 || align="center" | 4
|-
! [[GTF Perseus]]
| align="center" | 0 || align="center" | 0 || align="center" | 8 || align="center" | 8
|-
! [[GTF Pegasus]]
| align="center" | 0 || align="center" | 0 || align="center" | 4 || align="center" | 8
|-
! [[GTF Myrmidon]]
| align="center" | 0 || align="center" | 0 || align="center" | 4 || align="center" | 8
|-
! [[GTB Artemis]]
| align="center" | 0 || align="center" | 0 || align="center" | 0 || align="center" | 4
|-
! [[GTB Medusa]]
| align="center" | 4 || align="center" | 4 || align="center" | 4 || align="center" | 0
|}

In addition to its fighter complement and twelve sentry guns, two [[GTC Fenris|Fenris-class cruisers]] were assigned to patrol the station, after its completion in 2344. The GTC Kelsan, a [[GTC Leviathan|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''==

'''''Codex Anathema''''' is the name of a book, apparently written by [[Aken Bosch]], prior to his disappearance in the [[Nebula System|shivan nebula]]. One of the [[Special Operations Command|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.

===Origin===

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 [[Official Volition Node Map|Allied space]]. When he happened upon information regarding the [[Knossos|Knossos portal]], the physical obstacle became surmountable. As his rebellion gained momentum, and Bosch resumed the [[Galactic Terran Intelligence|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 [[Neo-Terran Front|NTF]] fleet to capture the [[Gamma Draconis| 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 [[Galactic Terran-Vasudan Alliance|GTVA]]'s debut of the [[GTVA Colossus|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.

===Contents===

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 [[NTF Iceni|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.

==Ship List==

Includes all named ships appearing in the Catharsis continuity, through the ''Battle of Good Hope''.

Notes
*Tables ordered from most recent events to oldest.
*Status
: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, as no assumption is made regarding their evacuation or loss during the Capella supernova.
*Factions
:'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.

===Third Shivan Incursion===
'''(List incomplete and subject to change.)'''

{| border="1" cellpadding="2"
|+ '''Third Shivan Incursion'''
! width="100" | Ship Name
! width="100" | Ship Class
! width="90" | Status
! width="75" | Serving System
! width="75" | Faction
! Role and Major Engagements
|-
! Gaena
| [[SC Cain]] || Destroyed (?) || Epsilon Eridani || Shivan Forces || Principle defense of a depot just inside Epsilon Eridani.
|-
! Halifax
| [[GTD Hades]] || Unknown || Sirius || GTVA || Sister ship to the GTD Liberator. Dropped out of contact with Allied forces, when the GTVA's long range communication grid collapsed.
|-
! Hidimba
| [[SD Ravana]] || Operational (?) || Epsilon Eridani || Shivan Forces || Attacked a GTVA reconnaissance unit.
|-
! Kullu
| [[SD Ravana]] || Operational || Epsilon Eridani || Shivan Forces || Encountered by a GTVA reconnaissance unit.
|-
! Liberator
| [[GTD Hades]] || Destroyed || Ross 128 || GTVA || Deployed ahead of schedule to counter shivan advances into Ross 128. Eventually led a major convoy from Ross 128, during the system's evacuation.
|-
! Tholos
| [[SCv Moloch]] || Operational (?) || Ross 128 || GTVA || Captured from the shivans, while escorting a convoy, before leading a recon mission to Epsilon Eridani.
|-
! [[FreeSpace 2 Vasudan Ship Database#GVD_Toeris|Toeris]]
| [[GVD Typhon]] || Unknown || Ross 128 || GTVA || Led the final convoy from Ross 128. Dropped out of communication with Allied forces, after entering Laramis.
|-
! Vajra
| [[SC Rakshasa]] || Operational (?) || Epsilon Eridani || Shivan Forces || Encountered alongside the SD Kullu.
|}

===''Battle of Good Hope''===

{| border="1" cellpadding="2"
|+ '''''Battle of Good Hope'''''
! width="100" | Ship Name
! width="100" | Ship Class
! width="90" | Status
! width="75" | Serving System
! width="75" | 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
| [[NTF Iceni | 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
| [[GVFr Satis|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.
|-
! [[FreeSpace 2 Terran Ship Database#GTCv Naxos | 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.
|}

===Altair Insurgency===

{| border="1" cellpadding="2"
|+ '''Altair Insurgency'''
! width="100" | Ship Name
! width="100" | Ship Class
! width="90" | Status
! width="100" | Serving System
! width="100" | 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.
|-
! [[FreeSpace 2 Vasudan Ship Database#GVD Hedetet | 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
| [[GVFr Satis|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
| [[GVFr Satis|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''.
|-
! [[FreeSpace 2 Terran Ship Database#GTD Phoenicia | 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
| [[PVFr Ma%27at | 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''.
|-
! [[FreeSpace 2 Vasudan Ship Database#GVCv Thebes | 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)===

{| border="1" cellpadding="2"
|+ '''Second Shivan Incursion (Altair)'''
! width="100" | Ship Name
! width="100" | Ship Class
! width="90" | Status
! width="100" | Serving System
! width="95" | Faction
! Role and Major Engagements
|-
! Alchemy
| [[SCv Moloch]] || Destroyed || -- || Shivan Forces || Part of the support fleet attacking Altair.
|-
! Argoth
| [[GVFr Satis|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)===

{| border="1" cellpadding="2"
|+ '''Second Shivan Incursion (Capella)'''
! width="100" | Ship Name
! width="100" | Ship Class
! width="90" | Status
! width="100" | Serving System
! width="95" | 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
| [[GVFr Satis|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.
|}

==External Links==

*[http://home.comcast.net/~blueflames/SF1site/ Second Front website]
*[http://home.comcast.net/~blueflames/SF2site/ Artifice website]

User talk:BlueFlames

2009-04-14T16:34:33Z

BlueFlames: Formatting.

==Weapon pages==

So, i see you have started editing the pages. But one quick question... Should we write the calculated damage vs each potential target (shield, hull, subsys) or just multipliers as in some cases the multipliers are really, really odd? - [[User:Wanderer|Wanderer]] 14:25, 30 July 2007 (CDT)
:Also.. now that we have potentially useful template it would be best (imo) if we would make use of it. - [[User:Wanderer|Wanderer]] 14:27, 30 July 2007 (CDT)
::Most of the multipliers in the default FS2 weapons aren't all that odd. It might be worth adding the fully calculated damage as a parenthetical, after the multiplier. More information can't hurt, after all. I'll round out the player primaries this way, and fill in the extra bits later on. Your point about the template is also valid, but for right now, I'm more interested in getting the correct information assembled. Cleaning things up is a bit secondary to me, at the moment. -- [[User:BlueFlames|BlueFlames]] 16:34, 14 April 2009 (UTC) (post-dated)
:::Thanks for adding my template on the weapon pages, I couldn't be bothered when I made it, sorry. [[User:Bruce89|Bruce89]] 10:00, 1 August 2007 (CDT)

==User page==

Nice... those tables must have took hours. [[User:Mustang19|Mustang19]] 09:06, 24 March 2008 (CST)
:They did turn out to be pretty time-consuming. Would have been a whole lot quicker if the wiki software had a means of importing Excel spreadsheets, but that'd probably wind up being more labor for the administrators than it'd be worth. [[User:BlueFlames|BlueFlames]] 11:02, 24 March 2008 (CST)

==Crossing the Styx==

Yeah, you're right. I meant July 2009. Thanks. [[User:SpaceFreak|SpaceFreak]] 03:51, 8 January 2009 (CST)

== Spoiler template ==

It's here: [[Template:Spoiler]]. - [[User:TopAce|TopAce]] 13:07, 27 March 2009 (UTC)
:Now, I'm wondering that, too. It used to be there. I don't know where it went, but I'm adding a note to the main page. - [[User:TopAce|TopAce]] 16:57, 27 March 2009 (UTC)

==Disambiguations==

Please note that entries in disambiguation pages should not be generic. You need to specify if each entry is canon or non-canon and you also need to point entries to their respective campaigns/mods. --- [[User:Mobius|Mobius]]

GTD Hades

2009-04-14T07:09:55Z

BlueFlames: /* Statistics */ It has a fighter bay, though its capacity is never mentioned.

{{FS12_Ships}}{{shipimage|image=[[Image:hades320x240.jpg]]|caption=The GTD Hades}}The '''GTD ''Hades''''' was a warship of the class of the same name during and after the [[Great War]]. The ''Hades'' was an effort to utilize stolen Shivan technology and mix it with Terran ones. Disagreement from the side of the [[Galactic Terran Alliance]] led to the [[Hades Rebellion]], during which, the GTD ''Hades'' was destroyed by two squadrons and the GTC ''Orff''.

==Description:==

===FS1 Tech Room Description===
Nothing much is known about the GTD Hades. It seems to be the GTI's top project. We believe the goal of the project
is to recreate the SD Lucifer.

The GTD Hades should be considered a Class A threat.

===FS2 Tech Room Description===
The GTD Hades was a fusion of Terran and Shivan military technologies. It was constructed by Galactic Terran Intelligence (GTI), a rogue branch of the GTA. In 2335, GTI leaders sought to overthrow the provisional GTA government established in Delta Serpentis. After the defeat of the GTI and the destruction of the Hades, the GTA classified the details of this research at level Omega. There are rumors that the Alliance has attempted to reconstruct the Hades to learn more about the GTI's activities. These reports have yet to be confirmed by government sources.

===Developer Notes===
None

===Name origin===
In Greek mythology, Hades was the ruler of the Greek Underworld. Hades, along with his brothers Zeus and Poseidon defeated the Titans and claimed rulership over the universe, dividing the world among themselves. The Roman name for Hades is Pluto.

==Performance:==
===Statistics===
{{Ship Stats|Destroyer|Unknown|N/A|15.0|N/A|N/A|800 000/400 000|N/A|3404}}{|-
| style="width:200px"|'''[[Technical_Terms_and_Definitions#Fighter Complement|Fighter Complement]]'''
| style="width:200px"|Unknown
|}

===Armaments===

*'''[[Technical_Terms_and_Definitions#Turrets|Turrets]]'''
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=2 style="background:#351515;"| '''FreeSpace 1'''
| colspan=2 style="background:#351515;"| '''FreeSpace 2'''
|- align="center"
| style="width:120px" |Turret Type
| style="width:60px" |Amount
| style="width:120px" |Turret Type
| style="width:60px" |Amount
|- align="center"
| [[Shivan Turret Laser]]
| 16
| [[Shivan Turret Laser]]
| 16
|- align="center"
| [[FighterKiller]]
| 2
| [[FighterKiller]]
| 2
|- align="center"
| [[Shivan Cluster]]
| 2
| [[Shivan Cluster]]
| 2
|- align="center"
| [[Shivan Super Laser]]
| 2
| [[BGreen|Big Green Beam]]
| 2
|}

==Veteran Comments==
{{Comment|''Has too many hitpoints, in [[Secrets Revealed]], standard practice is to hide in the "trench" halfway between fore and aft of this ship, and jam your keyboard's firing key down. I've found, however, that this is not as effective in [[Portal:FreeSpace 2|FreeSpace 2]]. The weakest point of the Hades is the horrible protection of its subsystems. An [[GTD Orion|Orion]], although it has 1/4 - 1/8 the armor, can win in a fight with a Hades simply because the Hades will be disabled and mostly disarmed within 30 seconds of the battle. I've seen an Orion take out a Hades with relative ease, although it took a while.''

''The Hades is pretty capable in FS2. I've seen it take on multiple Demons and Molochs at once and survive. But its antifighter armament is decidedly FS1-era. The Hades' effectiveness against Shivan ships often surprises people, but it is actually quite simple when one comes down to it: Shivan ships do not have slash beams, greatly decreasing their chances of damaging the Hades' subsystems.''

''I disagree with the last comment; the first is correct. The Hades can be destroyed easily by an Orion because of its pathetic subsystem armor. Although its two BGreens would usually rip most destroyers to shreds, the fact that a single well-aimed Stiletto II can disable this behemoth makes them almost useless.''

''I find, that even though the scope of the Hades is mind boggling (especially the first time you actually fly over the whole thing, and before seeing things like the Colossus), it is fairly weak. In the FS1 mission where you are assigned the task of destroying the Hades, even though I had lost all of my wingmen, and it took me two hours, I found I was able to single-handedly destroy the ship, by disabling its underside cannons, engines, and sensors, and then just floating in the space below it... In an Athena. I actually found the squads of re-spawning Lokis more of a challenge, aside from the sheer amount of HP the Hades had.''

''I find the FS1 Hades to be a bit more difficult to destroy than the Hades in FS2. For some sick reason, in FS2, the Hades has only '''ONE''' engine subsystem...and it's located at, of all places, the point where the destroyer's engines meet! You could fire an [[SGreen]] at that spot and the Hades will be disabled! Even ships smaller than itself have better subsystem defences!''

If you give this thing more subsystem armor (and give it back the Shivan Super Lasers in FS2), it becomes evil incarnate (and the only thing I've ever seen take on the SJ Sathanas '''ALONE''' and live). If the GTVA were to mass-produce this modified version as a Juggernaut killer, the Shivans would be in for a lot of pain. As it stands, however, it's just heavily armored cannon fodder.}}

[[Category:Unique ships|Hades]]
[[Category:Ship]]

User:BlueFlames

2009-04-14T07:04:54Z

BlueFlames: /* Third Shivan Incursion */ A few more ships for the list.

{{non-canon}}
{{Spoiler | [[FreeSpace 2]], [[Second Front]], [[Artifice]], and campaigns under development.}}

==Catharsis 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 Catharsis continuity.)

The Catharsis story arc tracks the GTVA through a slow, seven-year decline in power, beginning with the [[Second Shivan Incursion|Shivan Incursion of 2367]]. This decline culminates with a third and final shivan incursion, which proves to be the death knell of the [[Galactic Terran-Vasudan Alliance]].

===[[Second Front]]===

November 24, 2367: Massive evacuations of the densely-populated [[Capella | Capella system]] begin. Millions of refugees flood into [[Epsilon Pegasi]] and [[Vega]].

November 26, 2367: SJ ''Twilight'', a [[SJ Sathanas | Sathanas-class juggernaut]] leading the fleet moving toward Capella, is destroyed in [[Gamma Draconis]] by an operation titled ''Project Roadblock''.

November 26, 2367: An exploration convoy, seeking to reenter [[GTVA | GTVA space]] through the [[Altair | Altair system]] is destroyed by [[shivan | shivan forces]]. Martial law declared in Altair.

November 27, 2367: The Altair fleet requests tactical support from [[Special Operations Command | 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 | 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|GTD ''Nereid'']] and [[GTD Bastion|GTD ''Bastion'']], packed with [[meson bomb | 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.

===Interim Period===

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.

May 16, 2368: Production of [[GTC Aeolus|Aeolus-class cruisers]] resumes in shipyards in [[Polaris]] and [[Laramis]]. The GTC Tsar, fourth in this new production line, is scheduled for launch in November.

===[[Artifice]]===

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 [[FreeSpace 2 Terran Ship Database#GTD Phoenicia | 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.

===Interim Period===

April 1, 2372: The GTVA Security Council authorizes the design of production models of the [[NTF Iceni | Iceni-class corvette]] and [[GTD Hades | Hades-class superdestroyer]].

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.

===Bounded===

February 1, 2374: The GTD ''Galen'' is discovered derelict near the debris field of the [[FreeSpace 1 Terran Ship Database#GTI Riviera | 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 7, 2374: Epsilon Eridani node discovered in Ross 128. Shivan forces begin appearing in greater number and in other systems, including [[Luyten 726-8]], [[Laramis]], [[Ikeya]], [[Mirfak]], and Altair.

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 [[Destruction of the SD Lucifer|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.

During the [[Hades Rebellion|Galactic Terran Intelligence rebellion]], Bast found himself serving well away from any major battles, guarding convoys and installations in [[Ikeya]] for the duration of 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.

===[[Galactic Terran-Vasudan Intelligence]]===

Since the Antares Federation controlled [[Beta Aquilae]], while the [[The Beta Aquilae Convention|BETAC treaty]] was being negotiated, they had a measure of political leverage that the [[Parliamentary Vasudan Empire|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|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 [[Aken Bosch|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 [[Second Shivan Incursion|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.

===Altair Insurgency===

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.

===Post-Insurgency===

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 node|jump nodes]] leading to uncharted star systems, find new jump nodes, and seal them as well. Unfortunately, the destruction of a jump node required [[TC-Meson Bomb|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 [[Terran Turret|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 [[NTF Iceni|GTCv Iceni-class corvette]] had begun.

==Coalition for Free and Open Trade==

===History===

====Formation and Composition====

As the [[Galactic Terran-Vasudan Alliance|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.

====Interbandit Conflict====

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.

====Unification====

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 [[NTF Iceni|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.

====Post-Unification Strategy====

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.

===Famous Persons===

====Expatriate Menkaura====

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''==

===Station History===

Construction on the ''Good Hope'' began in 2342 as a replacement to [[FreeSpace 1 Terran Ship Database#GTI Riviera|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 [[GTI Ganymede|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 [[NTF Iceni|Iceni-class corvette]] and was one of two shipyards assigned to construct new [[GTD Hecate|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 [[GTD Orion|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===

{| border="1" cellpadding="2"
|+ '''Standard Fighter Compliment'''
!width="120"|Fighter Class
!width="100"|Amount
(2342, proposed)
!width="50"|Amount
(2344)
!width="50"|Amount
(2368)
!width="50"|Amount
(2373)
|-
! [[GTF Apollo]]
| align="center" | 8 || align="center" | 8 || align="center" | 0 || align="center" | 0
|-
! [[GTF Valkyrie]]
| align="center" | 8 || align="center" | 4 || align="center" | 0 || align="center" | 0
|-
! [[GTF Ulysses]]
| align="center" | 4 || align="center" | 8 || align="center" | 8 || align="center" | 4
|-
! [[GTF Hercules]]
| align="center" | 4 || align="center" | 4 || align="center" | 0 || align="center" | 0
|-
! [[GTF Hercules Mark II|GTF Hercules Mk. II]]
| align="center" | 0 || align="center" | 0 || align="center" | 4 || align="center" | 4
|-
! [[GTF Loki]]
| align="center" | 12 || align="center" | 12 || align="center" | 8 || align="center" | 4
|-
! [[GTF Perseus]]
| align="center" | 0 || align="center" | 0 || align="center" | 8 || align="center" | 8
|-
! [[GTF Pegasus]]
| align="center" | 0 || align="center" | 0 || align="center" | 4 || align="center" | 8
|-
! [[GTF Myrmidon]]
| align="center" | 0 || align="center" | 0 || align="center" | 4 || align="center" | 8
|-
! [[GTB Artemis]]
| align="center" | 0 || align="center" | 0 || align="center" | 0 || align="center" | 4
|-
! [[GTB Medusa]]
| align="center" | 4 || align="center" | 4 || align="center" | 4 || align="center" | 0
|}

In addition to its fighter compliment and twelve sentry guns, two [[GTC Fenris|Fenris-class cruisers]] were assigned to patrol the station, after its completion in 2344. The GTC Kelsan, a [[GTC Leviathan|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''==

'''''Codex Anathema''''' is the name of a book, apparently written by [[Aken Bosch]], prior to his disappearance in the [[Nebula System|shivan nebula]]. One of the [[Special Operations Command|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.

===Origin===

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 [[Official Volition Node Map|Allied space]]. When he happened upon information regarding the [[Knossos|Knossos portal]], the physical obstacle became surmountable. As his rebellion gained momentum, and Bosch resumed the [[Galactic Terran Intelligence|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 [[Neo-Terran Front|NTF]] fleet to capture the [[Gamma Draconis| 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 [[Galactic Terran-Vasudan Alliance|GTVA]]'s debut of the [[GTVA Colossus|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.

===Contents===

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 [[NTF Iceni|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.

==Ship List==

Includes all named ships appearing in the Catharsis continuity, through the ''Battle of Good Hope''.

Notes
*Tables ordered from most recent events to oldest.
*Status
: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, as no assumption is made regarding their evacuation or loss during the Capella supernova.
*Factions
:'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.

===Third Shivan Incursion===
'''(List incomplete and subject to change.)'''

{| border="1" cellpadding="2"
|+ '''Third Shivan Incursion'''
! width="100" | Ship Name
! width="100" | Ship Class
! width="90" | Status
! width="75" | Serving System
! width="75" | Faction
! Role and Major Engagements
|-
! Gaena
| [[SC Cain]] || Destroyed (?) || Epsilon Eridani || Shivan Forces || Principle defense of a depot just inside Epsilon Eridani.
|-
! Halifax
| [[GTD Hades]] || Unknown || Sirius || GTVA || Sister ship to the GTD Liberator. Dropped out of contact with Allied forces, when the GTVA's long range communication grid collapsed.
|-
! Hidimba
| [[SD Ravana]] || Operational (?) || Epsilon Eridani || Shivan Forces || Attacked a GTVA reconnaissance unit.
|-
! Kullu
| [[SD Ravana]] || Operational || Epsilon Eridani || Shivan Forces || Encountered by a GTVA reconnaissance unit.
|-
! Liberator
| [[GTD Hades]] || Destroyed || Ross 128 || GTVA || Deployed ahead of schedule to counter shivan advances into Ross 128. Eventually led a major convoy from Ross 128, during the system's evacuation.
|-
! Tholos
| [[SCv Moloch]] || Operational (?) || Ross 128 || GTVA || Captured from the shivans, while escorting a convoy, before leading a recon mission to Epsilon Eridani.
|-
! [[FreeSpace 2 Vasudan Ship Database#GVD_Toeris|Toeris]]
| [[GVD Typhon]] || Unknown || Ross 128 || GTVA || Led the final convoy from Ross 128. Dropped out of communication with Allied forces, after entering Laramis.
|-
! Vajra
| [[SC Rakshasa]] || Operational (?) || Epsilon Eridani || Shivan Forces || Encountered alongside the SD Kullu.
|}

===''Battle of Good Hope''===

{| border="1" cellpadding="2"
|+ '''''Battle of Good Hope'''''
! width="100" | Ship Name
! width="100" | Ship Class
! width="90" | Status
! width="75" | Serving System
! width="75" | 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
| [[NTF Iceni | 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
| [[GVFr Satis|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.
|-
! [[FreeSpace 2 Terran Ship Database#GTCv Naxos | 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.
|}

===Altair Insurgency===

{| border="1" cellpadding="2"
|+ '''Altair Insurgency'''
! width="100" | Ship Name
! width="100" | Ship Class
! width="90" | Status
! width="100" | Serving System
! width="100" | 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.
|-
! [[FreeSpace 2 Vasudan Ship Database#GVD Hedetet | 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
| [[GVFr Satis|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
| [[GVFr Satis|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''.
|-
! [[FreeSpace 2 Terran Ship Database#GTD Phoenicia | 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
| [[PVFr Ma%27at | 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''.
|-
! [[FreeSpace 2 Vasudan Ship Database#GVCv Thebes | 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)===

{| border="1" cellpadding="2"
|+ '''Second Shivan Incursion (Altair)'''
! width="100" | Ship Name
! width="100" | Ship Class
! width="90" | Status
! width="100" | Serving System
! width="95" | Faction
! Role and Major Engagements
|-
! Alchemy
| [[SCv Moloch]] || Destroyed || -- || Shivan Forces || Part of the support fleet attacking Altair.
|-
! Argoth
| [[GVFr Satis|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)===

{| border="1" cellpadding="2"
|+ '''Second Shivan Incursion (Capella)'''
! width="100" | Ship Name
! width="100" | Ship Class
! width="90" | Status
! width="100" | Serving System
! width="95" | 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
| [[GVFr Satis|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.
|}

==External Links==

*[http://home.comcast.net/~blueflames/SF1site/ Second Front website]
*[http://home.comcast.net/~blueflames/SF2site/ Artifice website]

GVD Toeris

2009-04-14T06:38:26Z

BlueFlames: Redirecting to FreeSpace 2 Vasudan Ship Database#GVD Toeris

#REDIRECT [[FreeSpace 2 Vasudan Ship Database#GVD_Toeris]]

User:BlueFlames

2009-04-13T16:21:34Z

BlueFlames: Adding to the ship list.

{{non-canon}}
{{Spoiler | [[FreeSpace 2]], [[Second Front]], [[Artifice]], and campaigns under development.}}

==Catharsis 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 Catharsis continuity.)

The Catharsis story arc tracks the GTVA through a slow, seven-year decline in power, beginning with the [[Second Shivan Incursion|Shivan Incursion of 2367]]. This decline culminates with a third and final shivan incursion, which proves to be the death knell of the [[Galactic Terran-Vasudan Alliance]].

===[[Second Front]]===

November 24, 2367: Massive evacuations of the densely-populated [[Capella | Capella system]] begin. Millions of refugees flood into [[Epsilon Pegasi]] and [[Vega]].

November 26, 2367: SJ ''Twilight'', a [[SJ Sathanas | Sathanas-class juggernaut]] leading the fleet moving toward Capella, is destroyed in [[Gamma Draconis]] by an operation titled ''Project Roadblock''.

November 26, 2367: An exploration convoy, seeking to reenter [[GTVA | GTVA space]] through the [[Altair | Altair system]] is destroyed by [[shivan | shivan forces]]. Martial law declared in Altair.

November 27, 2367: The Altair fleet requests tactical support from [[Special Operations Command | 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 | 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|GTD ''Nereid'']] and [[GTD Bastion|GTD ''Bastion'']], packed with [[meson bomb | 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.

===Interim Period===

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.

May 16, 2368: Production of [[GTC Aeolus|Aeolus-class cruisers]] resumes in shipyards in [[Polaris]] and [[Laramis]]. The GTC Tsar, fourth in this new production line, is scheduled for launch in November.

===[[Artifice]]===

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 [[FreeSpace 2 Terran Ship Database#GTD Phoenicia | 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.

===Interim Period===

April 1, 2372: The GTVA Security Council authorizes the design of production models of the [[NTF Iceni | Iceni-class corvette]] and [[GTD Hades | Hades-class superdestroyer]].

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.

===Bounded===

February 1, 2374: The GTD ''Galen'' is discovered derelict near the debris field of the [[FreeSpace 1 Terran Ship Database#GTI Riviera | 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 7, 2374: Epsilon Eridani node discovered in Ross 128. Shivan forces begin appearing in greater number and in other systems, including [[Luyten 726-8]], [[Laramis]], [[Ikeya]], [[Mirfak]], and Altair.

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 [[Destruction of the SD Lucifer|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.

During the [[Hades Rebellion|Galactic Terran Intelligence rebellion]], Bast found himself serving well away from any major battles, guarding convoys and installations in [[Ikeya]] for the duration of 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.

===[[Galactic Terran-Vasudan Intelligence]]===

Since the Antares Federation controlled [[Beta Aquilae]], while the [[The Beta Aquilae Convention|BETAC treaty]] was being negotiated, they had a measure of political leverage that the [[Parliamentary Vasudan Empire|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|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 [[Aken Bosch|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 [[Second Shivan Incursion|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.

===Altair Insurgency===

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.

===Post-Insurgency===

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 node|jump nodes]] leading to uncharted star systems, find new jump nodes, and seal them as well. Unfortunately, the destruction of a jump node required [[TC-Meson Bomb|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 [[Terran Turret|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 [[NTF Iceni|GTCv Iceni-class corvette]] had begun.

==Coalition for Free and Open Trade==

===History===

====Formation and Composition====

As the [[Galactic Terran-Vasudan Alliance|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.

====Interbandit Conflict====

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.

====Unification====

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 [[NTF Iceni|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.

====Post-Unification Strategy====

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.

===Famous Persons===

====Expatriate Menkaura====

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''==

===Station History===

Construction on the ''Good Hope'' began in 2342 as a replacement to [[FreeSpace 1 Terran Ship Database#GTI Riviera|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 [[GTI Ganymede|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 [[NTF Iceni|Iceni-class corvette]] and was one of two shipyards assigned to construct new [[GTD Hecate|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 [[GTD Orion|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===

{| border="1" cellpadding="2"
|+ '''Standard Fighter Compliment'''
!width="120"|Fighter Class
!width="100"|Amount
(2342, proposed)
!width="50"|Amount
(2344)
!width="50"|Amount
(2368)
!width="50"|Amount
(2373)
|-
! [[GTF Apollo]]
| align="center" | 8 || align="center" | 8 || align="center" | 0 || align="center" | 0
|-
! [[GTF Valkyrie]]
| align="center" | 8 || align="center" | 4 || align="center" | 0 || align="center" | 0
|-
! [[GTF Ulysses]]
| align="center" | 4 || align="center" | 8 || align="center" | 8 || align="center" | 4
|-
! [[GTF Hercules]]
| align="center" | 4 || align="center" | 4 || align="center" | 0 || align="center" | 0
|-
! [[GTF Hercules Mark II|GTF Hercules Mk. II]]
| align="center" | 0 || align="center" | 0 || align="center" | 4 || align="center" | 4
|-
! [[GTF Loki]]
| align="center" | 12 || align="center" | 12 || align="center" | 8 || align="center" | 4
|-
! [[GTF Perseus]]
| align="center" | 0 || align="center" | 0 || align="center" | 8 || align="center" | 8
|-
! [[GTF Pegasus]]
| align="center" | 0 || align="center" | 0 || align="center" | 4 || align="center" | 8
|-
! [[GTF Myrmidon]]
| align="center" | 0 || align="center" | 0 || align="center" | 4 || align="center" | 8
|-
! [[GTB Artemis]]
| align="center" | 0 || align="center" | 0 || align="center" | 0 || align="center" | 4
|-
! [[GTB Medusa]]
| align="center" | 4 || align="center" | 4 || align="center" | 4 || align="center" | 0
|}

In addition to its fighter compliment and twelve sentry guns, two [[GTC Fenris|Fenris-class cruisers]] were assigned to patrol the station, after its completion in 2344. The GTC Kelsan, a [[GTC Leviathan|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''==

'''''Codex Anathema''''' is the name of a book, apparently written by [[Aken Bosch]], prior to his disappearance in the [[Nebula System|shivan nebula]]. One of the [[Special Operations Command|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.

===Origin===

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 [[Official Volition Node Map|Allied space]]. When he happened upon information regarding the [[Knossos|Knossos portal]], the physical obstacle became surmountable. As his rebellion gained momentum, and Bosch resumed the [[Galactic Terran Intelligence|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 [[Neo-Terran Front|NTF]] fleet to capture the [[Gamma Draconis| 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 [[Galactic Terran-Vasudan Alliance|GTVA]]'s debut of the [[GTVA Colossus|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.

===Contents===

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 [[NTF Iceni|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.

==Ship List==

Includes all named ships appearing in the Catharsis continuity, through the ''Battle of Good Hope''.

Notes
*Tables ordered from most recent events to oldest.
*Status
: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, as no assumption is made regarding their evacuation or loss during the Capella supernova.
*Factions
:'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.

===Third Shivan Incursion===
'''(List incomplete and subject to change.)'''

{| border="1" cellpadding="2"
|+ '''Third Shivan Incursion'''
! width="100" | Ship Name
! width="100" | Ship Class
! width="90" | Status
! width="75" | Serving System
! width="75" | Faction
! Role and Major Engagements
|-
! Gaena
| [[SC Cain]] || Destroyed (?) || Epsilon Eridani || Shivan Forces || Principle defense of a depot just inside Epsilon Eridani.
|-
! Hidimba
| [[SD Ravana]] || Operational (?) || Epsilon Eridani || Shivan Forces || Attacked a GTVA reconnaissance unit.
|-
! Kullu
| [[SD Ravana]] || Operational || Epsilon Eridani || Shivan Forces || Encountered by a GTVA reconnaissance unit.
|-
! Tholos
| [[SCv Moloch]] || Operational (?) || Ross 128 || GTVA || Captured from the shivans, while escorting a convoy, before leading a recon mission to Epsilon Eridani.
|-
! Vajra
| [[SC Rakshasa]] || Operational (?) || Epsilon Eridani || Shivan Forces || Encountered alongside the SD Kullu.
|}

===''Battle of Good Hope''===

{| border="1" cellpadding="2"
|+ '''''Battle of Good Hope'''''
! width="100" | Ship Name
! width="100" | Ship Class
! width="90" | Status
! width="75" | Serving System
! width="75" | 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
| [[NTF Iceni | 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
| [[GVFr Satis|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.
|-
! [[FreeSpace 2 Terran Ship Database#GTCv Naxos | 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.
|}

===Altair Insurgency===

{| border="1" cellpadding="2"
|+ '''Altair Insurgency'''
! width="100" | Ship Name
! width="100" | Ship Class
! width="90" | Status
! width="100" | Serving System
! width="100" | 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.
|-
! [[FreeSpace 2 Vasudan Ship Database#GVD Hedetet | 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
| [[GVFr Satis|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
| [[GVFr Satis|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''.
|-
! [[FreeSpace 2 Terran Ship Database#GTD Phoenicia | 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
| [[PVFr Ma%27at | 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''.
|-
! [[FreeSpace 2 Vasudan Ship Database#GVCv Thebes | 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)===

{| border="1" cellpadding="2"
|+ '''Second Shivan Incursion (Altair)'''
! width="100" | Ship Name
! width="100" | Ship Class
! width="90" | Status
! width="100" | Serving System
! width="95" | Faction
! Role and Major Engagements
|-
! Alchemy
| [[SCv Moloch]] || Destroyed || -- || Shivan Forces || Part of the support fleet attacking Altair.
|-
! Argoth
| [[GVFr Satis|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)===

{| border="1" cellpadding="2"
|+ '''Second Shivan Incursion (Capella)'''
! width="100" | Ship Name
! width="100" | Ship Class
! width="90" | Status
! width="100" | Serving System
! width="95" | 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
| [[GVFr Satis|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.
|}

==External Links==

*[http://home.comcast.net/~blueflames/SF1site/ Second Front website]
*[http://home.comcast.net/~blueflames/SF2site/ Artifice website]

User:BlueFlames

2009-04-12T06:13:15Z

BlueFlames: Overarching continuity gets a proper name.

{{non-canon}}
{{Spoiler | [[FreeSpace 2]], [[Second Front]], [[Artifice]], and campaigns under development.}}

==Catharsis 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 Catharsis continuity.)

The Catharsis story arc tracks the GTVA through a slow, seven-year decline in power, beginning with the [[Second Shivan Incursion|Shivan Incursion of 2367]]. This decline culminates with a third and final shivan incursion, which proves to be the death knell of the [[Galactic Terran-Vasudan Alliance]].

===[[Second Front]]===

November 24, 2367: Massive evacuations of the densely-populated [[Capella | Capella system]] begin. Millions of refugees flood into [[Epsilon Pegasi]] and [[Vega]].

November 26, 2367: SJ ''Twilight'', a [[SJ Sathanas | Sathanas-class juggernaut]] leading the fleet moving toward Capella, is destroyed in [[Gamma Draconis]] by an operation titled ''Project Roadblock''.

November 26, 2367: An exploration convoy, seeking to reenter [[GTVA | GTVA space]] through the [[Altair | Altair system]] is destroyed by [[shivan | shivan forces]]. Martial law declared in Altair.

November 27, 2367: The Altair fleet requests tactical support from [[Special Operations Command | 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 | 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|GTD ''Nereid'']] and [[GTD Bastion|GTD ''Bastion'']], packed with [[meson bomb | 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.

===Interim Period===

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.

May 16, 2368: Production of [[GTC Aeolus|Aeolus-class cruisers]] resumes in shipyards in [[Polaris]] and [[Laramis]]. The GTC Tsar, fourth in this new production line, is scheduled for launch in November.

===[[Artifice]]===

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 [[FreeSpace 2 Terran Ship Database#GTD Phoenicia | 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.

===Interim Period===

April 1, 2372: The GTVA Security Council authorizes the design of production models of the [[NTF Iceni | Iceni-class corvette]] and [[GTD Hades | Hades-class superdestroyer]].

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.

===Bounded===

February 1, 2374: The GTD ''Galen'' is discovered derelict near the debris field of the [[FreeSpace 1 Terran Ship Database#GTI Riviera | 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 7, 2374: Epsilon Eridani node discovered in Ross 128. Shivan forces begin appearing in greater number and in other systems, including [[Luyten 726-8]], [[Laramis]], [[Ikeya]], [[Mirfak]], and Altair.

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 [[Destruction of the SD Lucifer|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.

During the [[Hades Rebellion|Galactic Terran Intelligence rebellion]], Bast found himself serving well away from any major battles, guarding convoys and installations in [[Ikeya]] for the duration of 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.

===[[Galactic Terran-Vasudan Intelligence]]===

Since the Antares Federation controlled [[Beta Aquilae]], while the [[The Beta Aquilae Convention|BETAC treaty]] was being negotiated, they had a measure of political leverage that the [[Parliamentary Vasudan Empire|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|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 [[Aken Bosch|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 [[Second Shivan Incursion|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.

===Altair Insurgency===

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.

===Post-Insurgency===

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 node|jump nodes]] leading to uncharted star systems, find new jump nodes, and seal them as well. Unfortunately, the destruction of a jump node required [[TC-Meson Bomb|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 [[Terran Turret|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 [[NTF Iceni|GTCv Iceni-class corvette]] had begun.

==Coalition for Free and Open Trade==

===History===

====Formation and Composition====

As the [[Galactic Terran-Vasudan Alliance|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.

====Interbandit Conflict====

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.

====Unification====

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 [[NTF Iceni|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.

====Post-Unification Strategy====

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.

===Famous Persons===

====Expatriate Menkaura====

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''==

===Station History===

Construction on the ''Good Hope'' began in 2342 as a replacement to [[FreeSpace 1 Terran Ship Database#GTI Riviera|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 [[GTI Ganymede|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 [[NTF Iceni|Iceni-class corvette]] and was one of two shipyards assigned to construct new [[GTD Hecate|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 [[GTD Orion|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===

{| border="1" cellpadding="2"
|+ '''Standard Fighter Compliment'''
!width="120"|Fighter Class
!width="100"|Amount
(2342, proposed)
!width="50"|Amount
(2344)
!width="50"|Amount
(2368)
!width="50"|Amount
(2373)
|-
! [[GTF Apollo]]
| align="center" | 8 || align="center" | 8 || align="center" | 0 || align="center" | 0
|-
! [[GTF Valkyrie]]
| align="center" | 8 || align="center" | 4 || align="center" | 0 || align="center" | 0
|-
! [[GTF Ulysses]]
| align="center" | 4 || align="center" | 8 || align="center" | 8 || align="center" | 4
|-
! [[GTF Hercules]]
| align="center" | 4 || align="center" | 4 || align="center" | 0 || align="center" | 0
|-
! [[GTF Hercules Mark II|GTF Hercules Mk. II]]
| align="center" | 0 || align="center" | 0 || align="center" | 4 || align="center" | 4
|-
! [[GTF Loki]]
| align="center" | 12 || align="center" | 12 || align="center" | 8 || align="center" | 4
|-
! [[GTF Perseus]]
| align="center" | 0 || align="center" | 0 || align="center" | 8 || align="center" | 8
|-
! [[GTF Pegasus]]
| align="center" | 0 || align="center" | 0 || align="center" | 4 || align="center" | 8
|-
! [[GTF Myrmidon]]
| align="center" | 0 || align="center" | 0 || align="center" | 4 || align="center" | 8
|-
! [[GTB Artemis]]
| align="center" | 0 || align="center" | 0 || align="center" | 0 || align="center" | 4
|-
! [[GTB Medusa]]
| align="center" | 4 || align="center" | 4 || align="center" | 4 || align="center" | 0
|}

In addition to its fighter compliment and twelve sentry guns, two [[GTC Fenris|Fenris-class cruisers]] were assigned to patrol the station, after its completion in 2344. The GTC Kelsan, a [[GTC Leviathan|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''==

'''''Codex Anathema''''' is the name of a book, apparently written by [[Aken Bosch]], prior to his disappearance in the [[Nebula System|shivan nebula]]. One of the [[Special Operations Command|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.

===Origin===

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 [[Official Volition Node Map|Allied space]]. When he happened upon information regarding the [[Knossos|Knossos portal]], the physical obstacle became surmountable. As his rebellion gained momentum, and Bosch resumed the [[Galactic Terran Intelligence|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 [[Neo-Terran Front|NTF]] fleet to capture the [[Gamma Draconis| 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 [[Galactic Terran-Vasudan Alliance|GTVA]]'s debut of the [[GTVA Colossus|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.

===Contents===

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 [[NTF Iceni|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.

==Ship List==

Includes all named ships appearing in the Catharsis continuity, through the ''Battle of Good Hope''.

Notes
*Tables ordered from most recent events to oldest.
*Status
: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.
*Factions
:'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''===

{| border="1" cellpadding="2"
|+ '''''Battle of Good Hope'''''
! width="100" | Ship Name
! width="100" | Ship Class
! width="90" | Status
! width="75" | Serving System
! width="75" | 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
| [[NTF Iceni | 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
| [[GVFr Satis|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.
|-
! [[FreeSpace 2 Terran Ship Database#GTCv Naxos | 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.
|}

===Altair Insurgency===

{| border="1" cellpadding="2"
|+ '''Altair Insurgency'''
! width="100" | Ship Name
! width="100" | Ship Class
! width="90" | Status
! width="100" | Serving System
! width="100" | 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.
|-
! [[FreeSpace 2 Vasudan Ship Database#GVD Hedetet | 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
| [[GVFr Satis|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
| [[GVFr Satis|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''.
|-
! [[FreeSpace 2 Terran Ship Database#GTD Phoenicia | 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
| [[PVFr Ma%27at | 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''.
|-
! [[FreeSpace 2 Vasudan Ship Database#GVCv Thebes | 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)===

{| border="1" cellpadding="2"
|+ '''Second Shivan Incursion (Altair)'''
! width="100" | Ship Name
! width="100" | Ship Class
! width="90" | Status
! width="100" | Serving System
! width="95" | Faction
! Role and Major Engagements
|-
! Alchemy
| [[SCv Moloch]] || Destroyed || -- || Shivan Forces || Part of the support fleet attacking Altair.
|-
! Argoth
| [[GVFr Satis|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)===

{| border="1" cellpadding="2"
|+ '''Second Shivan Incursion (Capella)'''
! width="100" | Ship Name
! width="100" | Ship Class
! width="90" | Status
! width="100" | Serving System
! width="95" | 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
| [[GVFr Satis|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.
|}

==External Links==

*[http://home.comcast.net/~blueflames/SF1site/ Second Front website]
*[http://home.comcast.net/~blueflames/SF2site/ Artifice website]

User:BlueFlames

2009-04-12T05:46:47Z

BlueFlames: New section

{{non-canon}}
{{Spoiler | [[FreeSpace 2]], [[Second Front]], [[Artifice]], and campaigns under development.}}

==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 [[Second Shivan Incursion | Shivan Incursion of 2367]]. This decline culminates with a third and final shivan incursion, which proves to be the death knell of the Alliance.

===[[Second Front]]===

November 24, 2367: Massive evacuations of the densely-populated [[Capella | Capella system]] begin. Millions of refugees flood into [[Epsilon Pegasi]] and [[Vega]].

November 26, 2367: SJ ''Twilight'', a [[SJ Sathanas | Sathanas-class juggernaut]] leading the fleet moving toward Capella, is destroyed in [[Gamma Draconis]] by an operation titled ''Project Roadblock''.

November 26, 2367: An exploration convoy, seeking to reenter [[GTVA | GTVA space]] through the [[Altair | Altair system]] is destroyed by [[shivan | shivan forces]]. Martial law declared in Altair.

November 27, 2367: The Altair fleet requests tactical support from [[Special Operations Command | 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 | 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|GTD ''Nereid'']] and [[GTD Bastion|GTD ''Bastion'']], packed with [[meson bomb | 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.

===Interim Period===

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.

May 16, 2368: Production of [[GTC Aeolus|Aeolus-class cruisers]] resumes in shipyards in [[Polaris]] and [[Laramis]]. The GTC Tsar, fourth in this new production line, is scheduled for launch in November.

===[[Artifice]]===

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 [[FreeSpace 2 Terran Ship Database#GTD Phoenicia | 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.

===Interim Period===

April 1, 2372: The GTVA Security Council authorizes the design of production models of the [[NTF Iceni | Iceni-class corvette]] and [[GTD Hades | Hades-class superdestroyer]].

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.

===Bounded===

February 1, 2374: The GTD ''Galen'' is discovered derelict near the debris field of the [[FreeSpace 1 Terran Ship Database#GTI Riviera | 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 7, 2374: Epsilon Eridani node discovered in Ross 128. Shivan forces begin appearing in greater number and in other systems, including [[Luyten 726-8]], [[Laramis]], [[Ikeya]], [[Mirfak]], and Altair.

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 [[Destruction of the SD Lucifer|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.

During the [[Hades Rebellion|Galactic Terran Intelligence rebellion]], Bast found himself serving well away from any major battles, guarding convoys and installations in [[Ikeya]] for the duration of 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.

===[[Galactic Terran-Vasudan Intelligence]]===

Since the Antares Federation controlled [[Beta Aquilae]], while the [[The Beta Aquilae Convention|BETAC treaty]] was being negotiated, they had a measure of political leverage that the [[Parliamentary Vasudan Empire|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|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 [[Aken Bosch|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 [[Second Shivan Incursion|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.

===Altair Insurgency===

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.

===Post-Insurgency===

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 node|jump nodes]] leading to uncharted star systems, find new jump nodes, and seal them as well. Unfortunately, the destruction of a jump node required [[TC-Meson Bomb|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 [[Terran Turret|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 [[NTF Iceni|GTCv Iceni-class corvette]] had begun.

==Coalition for Free and Open Trade==

===History===

====Formation and Composition====

As the [[Galactic Terran-Vasudan Alliance|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.

====Interbandit Conflict====

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.

====Unification====

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 [[NTF Iceni|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.

====Post-Unification Strategy====

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.

===Famous Persons===

====Expatriate Menkaura====

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''==

===Station History===

Construction on the ''Good Hope'' began in 2342 as a replacement to [[FreeSpace 1 Terran Ship Database#GTI Riviera|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 [[GTI Ganymede|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 [[NTF Iceni|Iceni-class corvette]] and was one of two shipyards assigned to construct new [[GTD Hecate|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 [[GTD Orion|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===

{| border="1" cellpadding="2"
|+ '''Standard Fighter Compliment'''
!width="120"|Fighter Class
!width="100"|Amount
(2342, proposed)
!width="50"|Amount
(2344)
!width="50"|Amount
(2368)
!width="50"|Amount
(2373)
|-
! [[GTF Apollo]]
| align="center" | 8 || align="center" | 8 || align="center" | 0 || align="center" | 0
|-
! [[GTF Valkyrie]]
| align="center" | 8 || align="center" | 4 || align="center" | 0 || align="center" | 0
|-
! [[GTF Ulysses]]
| align="center" | 4 || align="center" | 8 || align="center" | 8 || align="center" | 4
|-
! [[GTF Hercules]]
| align="center" | 4 || align="center" | 4 || align="center" | 0 || align="center" | 0
|-
! [[GTF Hercules Mark II|GTF Hercules Mk. II]]
| align="center" | 0 || align="center" | 0 || align="center" | 4 || align="center" | 4
|-
! [[GTF Loki]]
| align="center" | 12 || align="center" | 12 || align="center" | 8 || align="center" | 4
|-
! [[GTF Perseus]]
| align="center" | 0 || align="center" | 0 || align="center" | 8 || align="center" | 8
|-
! [[GTF Pegasus]]
| align="center" | 0 || align="center" | 0 || align="center" | 4 || align="center" | 8
|-
! [[GTF Myrmidon]]
| align="center" | 0 || align="center" | 0 || align="center" | 4 || align="center" | 8
|-
! [[GTB Artemis]]
| align="center" | 0 || align="center" | 0 || align="center" | 0 || align="center" | 4
|-
! [[GTB Medusa]]
| align="center" | 4 || align="center" | 4 || align="center" | 4 || align="center" | 0
|}

In addition to its fighter compliment and twelve sentry guns, two [[GTC Fenris|Fenris-class cruisers]] were assigned to patrol the station, after its completion in 2344. The GTC Kelsan, a [[GTC Leviathan|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''==

'''''Codex Anathema''''' is the name of a book, apparently written by [[Aken Bosch]], prior to his disappearance in the [[Nebula System|shivan nebula]]. One of the [[Special Operations Command|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.

===Origin===

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 [[Official Volition Node Map|Allied space]]. When he happened upon information regarding the [[Knossos|Knossos portal]], the physical obstacle became surmountable. As his rebellion gained momentum, and Bosch resumed the [[Galactic Terran Intelligence|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 [[Neo-Terran Front|NTF]] fleet to capture the [[Gamma Draconis| 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 [[Galactic Terran-Vasudan Alliance|GTVA]]'s debut of the [[GTVA Colossus|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.

===Contents===

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 [[NTF Iceni|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.

==Ship List==

Includes all named ships appearing in the Second Front continuity, through the ''Battle of Good Hope''.

Notes
*Tables ordered from most recent events to oldest.
*Status
: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.
*Factions
:'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''===

{| border="1" cellpadding="2"
|+ '''''Battle of Good Hope'''''
! width="100" | Ship Name
! width="100" | Ship Class
! width="90" | Status
! width="75" | Serving System
! width="75" | 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
| [[NTF Iceni | 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
| [[GVFr Satis|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.
|-
! [[FreeSpace 2 Terran Ship Database#GTCv Naxos | 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.
|}

===Altair Insurgency===

{| border="1" cellpadding="2"
|+ '''Altair Insurgency'''
! width="100" | Ship Name
! width="100" | Ship Class
! width="90" | Status
! width="100" | Serving System
! width="100" | 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.
|-
! [[FreeSpace 2 Vasudan Ship Database#GVD Hedetet | 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
| [[GVFr Satis|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
| [[GVFr Satis|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''.
|-
! [[FreeSpace 2 Terran Ship Database#GTD Phoenicia | 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
| [[PVFr Ma%27at | 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''.
|-
! [[FreeSpace 2 Vasudan Ship Database#GVCv Thebes | 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)===

{| border="1" cellpadding="2"
|+ '''Second Shivan Incursion (Altair)'''
! width="100" | Ship Name
! width="100" | Ship Class
! width="90" | Status
! width="100" | Serving System
! width="95" | Faction
! Role and Major Engagements
|-
! Alchemy
| [[SCv Moloch]] || Destroyed || -- || Shivan Forces || Part of the support fleet attacking Altair.
|-
! Argoth
| [[GVFr Satis|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)===

{| border="1" cellpadding="2"
|+ '''Second Shivan Incursion (Capella)'''
! width="100" | Ship Name
! width="100" | Ship Class
! width="90" | Status
! width="100" | Serving System
! width="95" | 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
| [[GVFr Satis|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.
|}

==External Links==

*[http://home.comcast.net/~blueflames/SF1site/ Second Front website]
*[http://home.comcast.net/~blueflames/SF2site/ Artifice website]

Altair

2009-04-11T23:49:59Z

BlueFlames: Deorphaning Altair V

===Celestial Information===
*''Name, meaning and Constellation:'' Alpha Aquilae, Aquila. "Altair" is Arabic for "The flying".
*''Other name(s) and meaning:'' Atair(same meaning of Altair)
*''Distance from Sol:'' 16.774 ly, 5.143 pc
*''Type of System:'' Singular
*''Spectral Class:'' A7-White Main Sequence
*''Right Ascension:'' 19h 50m 46.999s
*''Declination:'' +8° 52' 5.959"

===Known Planets===
*Altair I
*Altair II
*[[Altair III]]
*[[Altair IV]]
*[[Altair V]]

===Important Events===
*2335: Fleeing the wrath of the [[Shivans]], a group of [[Vasudans]] land on Altair and discover the remnants of an alien civilisation. Their investigations into the "[[Ancients]]", as they are later called, reveals information on how to track vessels into, and through, subspace.
*2367: Admiral Bosch uses [[Ancients|Ancient]] artifacts from [[Altair]] and other systems to unlock the [[Knossos]] portal located at [[Gamma Draconis]].

===Jump Nodes===
*[[Aldebaran]]
*[[Deneb]] ([[Node Inconsistencies#Pseudocanon|Pseudocanon]])
*Unknown System

[[Category:Stars and Planets]]

Talk:Main Page

2009-04-11T03:25:38Z

BlueFlames:

==Categories==
Categories? Do you know how to make new categories? I thought I did, but it seems I did not. Is it possible to make categories at all? - [[User:TopAce|TopAce]] 23:51, 15 Nov 2005 (CET)

It's easy. You just need to add <nowiki>[[Category:Category name]]</nowiki> (without the nowiki tags, obviously) and then go to the Category:Category name page. The wiki will auto generate the basic page for you. [[User:Black Wolf|Black Wolf]] 11:53, 16 Nov 2005 (CET)

== Featured Article ==

Aren't there any other articles besides the one on Shivans? It kinda makes this place feel like it's dead.

:Sure there are lots of other articles than one on Shivans, and the article can be changed too, i just haven't really seen any propositions lately. - [[User:Wanderer|Wanderer]] 00:07, 7 April 2007 (CDT)

==Admin Control?==
Do you have to be like...an Admin to change the main?
:ATM, AFAIK no. - [[User:Wanderer|Wanderer]] 15:04, 16 June 2007 (CDT)

==More features?==

Do you agree on having more than a "Featured Campaign of the Moment" section in the main page? Something like highlights on recent articles and such? --- [[User:Mobius|Mobius]]
:No thanks, I think the main page is fine as it is now. - [[User:Snail|Snail]] 16:35, 7 April 2009 (UTC)
::Agreed. - [[User:TopAce|TopAce]] 16:51, 7 April 2009 (UTC)
:::You have to admit that it's very poor compared to the average Wiki's Main Page. --- [[User:Mobius|Mobius]]
::::No, it's not. It's simple. It says what's needed. And that's all which is required of a Wiki Main Page. - [[User:Snail|Snail]] 08:26, 10 April 2009 (UTC)
While I wouldn't mind seeing the featured campaign cycle a little more often, my chief complaint about the "average" Wiki main page is that it's too busy. Less is more. -- [[User:BlueFlames|BlueFlames]] 15:32, 10 April 2009 (UTC)
:What do you mean? Are there too many links? - [[User:TopAce|TopAce]] 17:56, 10 April 2009 (UTC)
::I mean the FS Wiki's main page looks better than other Wikis because it doesn't have seventeen sections of useless, trivial clutter. -- [[User:BlueFlames|BlueFlames]] 03:25, 11 April 2009 (UTC)

Talk:Main Page

2009-04-10T15:32:55Z

BlueFlames: Adding my two cents to the till.

Their Finest Hour

2009-03-29T20:00:20Z

BlueFlames: Found the source of the beam troubles and revised the notes accordingly.

{{Mission|next=Clash of the Titans II|previous=Dunkerque|campaign=FreeSpace 2 Campaign Walkthrough}}

'''ACT 3, MISSION 8'''

'''Fighter squadron:''' [[70th Blue Lions]]

'''Description:''' The title says it all. Maybe.

----
==Background==
The [[70th Blue Lions]] are, along with the [[GTVA Colossus]] and a small contingent of warships, to create a diversion while the Meson Bomb-laden [[GTD Bastion]] collapses the [[Capella]]-[[Epsilon Pegasi]] jump node.

==Walkthrough==
A recommended loadout is the [[GTF Ares]], armed with two [[GTW Maxim]]s and a bank of [[GTM Trebuchet]]s. Alternatively, you can use a [[GTF Erinyes]], armed with a [[GTW UD-8 Kayser]], GTW Maxim and two banks of [[GTM Tempest|Tempest dumbfire missiles]].

This mission was planned big and executed small; the Colossus has a complicated set of waypoints that are never executed. Also, although all allied ships are beam freed, they are beam freed ''before'' they jump in, so they hardly fire their beams, if ever at all.

Your objective in this mission is extremely simple: survive, and get as many kills as possible. You will face off against multiple Shivan fighters and cruisers. If you want some extra protection from the enemy fighters, stay near the [[GVCv Sobek|Sobek-class]] Khepri. If you have loaded your ship with a Maxim cannon and a bank of Trebuchet missiles, use both to destroy the Shivan warships at long range.

Near the end, a [[SD Ravana|Ravana-class destroyer]], the Beast, jumps in to attack the Colossus. The Colossus destroys it, but sustains moderate damage. When the Ravana has been destroyed, a [[SJ Sathanas|Sathanas-class juggernaut]] jumps in. As the Colossus takes heavy damage from the Sathanas' main guns, Command orders the warship to jump out. The captain of the Colossus, however, defies Command order, and instead chooses to hold off the Sathanas to buy some extra time for the Bastion. In the ensuing engagement, the Colossus is destroyed.

You will be ordered to return to base when the Colossus goes down.

==Notes==
===Real-life Reference===
"This was their finest hour" was a speech made by Winston Churchill in 1940 during World War II, referring to the [http://en.wikipedia.org/wiki/Battle_of_France ''Battle of France'']. The name of the mission [[Dunkerque]] (SM3-07), another mission in Act III, was also reference to World War II. Here is an excerpt from the speech:

:''Let us therefore brace ourselves to our duties, and so bear ourselves that, if the British Empire and its Commonwealth last for a thousand years, men will still say, "'''This was their finest hour.'''"''

===Allied Warships===
The event that allows the Allied fleet to fire its beam cannons triggers before the bulk of the fleet has arrived. The [[FreeSpace 2 Vasudan Ship Database#GVC_Heket|''Heket'']], [[FreeSpace 2 Vasudan Ship Database#GVCv_Khepri|''Khepri'']], and [[FreeSpace 2 Terran Ship Database#GTC_Stalwart|''Stalwart'']] begin to arrive just over twenty seconds into the mission, moments after the [[beam-free-all]] event is triggered. The warships are then limited to firing [[Terran Turret|turret lasers]] and [[Standard Flak|flak]], since beams can only be freed for ships already in play.

===Actions of the ''Colossus''===
Many community members have noted that the ''Colossus''' last stand, although bold, was rather illogical as she was destroyed in just a few seconds by Sathanas 17, which never jumped to attack the ''Bastion'', as mission dialogue would suggest they were trying to prevent. The ''Colossus'' may not have been able to escape because she begins the mission moderately damaged and with engines disabled, but this is never mentioned in the briefing or messages even when Command orders the ship to jump out.

However, examination of the mission file shows that the Colossus was intended to have a much longer and more dramatic battle with the Sathanas, but this was scrapped. The scripting and waypoints for much of this battle still exist, but the Colossus' engines were disabled, rendering it largely irrelevant.

==Notable ships present==
*[[GTVA Colossus]]
*[[FreeSpace_2_Shivan_Ship_Database#SD Beast|SD Beast]]
*[[FreeSpace_2_Shivan_Ship_Database#SJ_Sathanas_17|SJ Sathanas 17]]

[[Category:Main FreeSpace 2 Campaign]]

Stalwart

2009-03-29T19:40:02Z

BlueFlames: Made a mistake with my Wiki syntax.

#REDIRECT [[FreeSpace 2 Terran Ship Database#GTC_Stalwart]]

Stalwart

2009-03-29T19:38:31Z

BlueFlames: Redirecting to FreeSpace 2 Terran Ship Database#GTC Stalwart

#REDIRECT [[FreeSpace 2 Terran Ship Database#GTC Stalwart]]

Khepri

2009-03-29T19:37:04Z

BlueFlames: New page: {{disambiguation}} *GVCv Khepri, a GVCv Sobek-class warship, deployed as part of a decoy operation, during the ...

{{disambiguation}}

*[[FreeSpace_2_Vasudan_Ship_Database#GVCv_Khepri|GVCv Khepri]], a [[GVCv Sobek]]-class warship, deployed as part of a [[Their Finest Hour|decoy operation]], during the shivan invasion of Capella.

*[[GVF Khepri]], a user-made, vasudan fightercraft.

Heket

2009-03-29T19:32:30Z

BlueFlames: New page: {{disambiguation}} *GVC ''Heket'', a Mentu-class cruiser deployed as part of a decoy operation, during ...

{{disambiguation}}

*[[FreeSpace 2 Vasudan Ship Database#GVC_Heket|GVC ''Heket'']], a [[GVC Mentu|Mentu-class]] cruiser deployed as part of a [[Their Finest Hour|decoy operation]], during the shivan invasion of Capella.

*[[GVF Heket]], a user-made, vasudan fighter.

Talk:FreeSpace Chronicled: The First Three Months

2009-03-28T16:09:53Z

BlueFlames:

==Article Title==

Is this indeed "Chronicled" or is it a typo that should be "Chronicles"? - [[User:TopAce|TopAce]] 11:49, 28 March 2009 (UTC)

:[http://en.wiktionary.org/wiki/chronicle Chronicle] can be used as both a noun or verb, so unless Zarathud comes in and says otherwise, I'm inclined to say the title is correct as-is. -- [[User:BlueFlames|BlueFlames]] 16:09, 28 March 2009 (UTC)

User talk:TopAce

2009-03-27T14:28:08Z

BlueFlames:

I tested with category:history page and it seemed to function just fine. All i had to do was to create a page named Categoty:History and add some text into it, And then correct all the category links from the concerning three articles. Also if you are doing the Ship Names could you take a look at 'Freespace 2 Ship Database' to see if there is a way of combining these quite overlapping articles. - [[User:Wanderer|Wanderer]] 05:56, 16 Nov 2005 (CET)

Thanks for the Category hint. As for the Ship names, some-one has already created a page that is the same as my Ship Names project. I will not finish it since it is already done - [[User:TopAce|TopAce]] 17:32, 18 Nov 2005 (CET)

TopAce, our formatting on the timeline is conflicting. Please observe the gray/silver text to seperate the canon from the non-canon. Thanks! [[User:Galemp|Galemp]] 22:26, 21 Nov 2005 (CET)

==Grammar==
Grammar evolves; how old is your book? But, yes, actually it does matter how something sounds spoken aloud. If you want your spoken language to sound stilted or stylized that's your problem, but don't come complaining to me when other people come along and decide it sounds just like what I said. - ngtm1r
*''However'' (in the meaning of "nevertheless") must *always* be preceded and followed by punctuation marks, that's the rule. All grammar books that I have seen—older and newer, including the most recent Oxford Advanced Learner's dictionary—say that. Check any that deals with punctuation; it will say just that. That's the way I learned it at high school, and now at university in Language Practice classes. - [[User:TopAce|TopAce]] 07:22, 15 May 2008 (CDT)

==By the by==

"[http://en.wiktionary.org/wiki/by_the_by By the by]" carries essentially the same meaning as "by the way." The former sees less use in contemporary English, but it is no less correct. It's good to see you keeping up with grammatical issues, but this one wasn't a problem. -- [[User:BlueFlames|BlueFlames]] 20:07, 9 January 2009 (CST)

==Valkyrie==
The problem I have with it is that it's factually '''wrong'' as far as I can tell, as the Apollo is more than capable enough at the roles in the missions you cited as only feasible in the Valkyrie. Indeed, the Apollo is the default ship for both those missions and most people probably completed them in it. [[User:Ngtm1r|Ngtm1r]] 19:27, 18 January 2009 (CST)

==Spoiler Template==

In reference to your comment on [http://www.hard-light.net/wiki/index.php?title=Operations_inside_the_Shivan_Nebula&oldid=21531 this edit] can you point me to where the general spoiler warning for the canon FS campaigns is? I failed to find it on the HLP main page, the FSWiki main page, or the FS2 portal. (Honestly, I think article-specific spoiler warnings are better than a general warning, that may inadvertantly put new players off of reading spoiler-free parts of the Wiki, but if there's concensus against them, so be it.) -- [[User:BlueFlames|BlueFlames]] 12:31, 27 March 2009 (UTC)
:Not exactly what I was going for. I meant, where, on the "main page" is the warning to new players that the Wiki contains spoilers? -- [[User:BlueFlames|BlueFlames]] 14:28, 27 March 2009 (UTC)

User talk:TopAce

2009-03-27T12:31:20Z

BlueFlames: Spoiler tag question.

Inferno

2009-03-22T13:05:39Z

BlueFlames: Level-one headers are for page titles only.

==General Info==
'''Original Authors:''' Steven 'Woomeister' Woosey, SadisticSid 

'''Additional Team Members:''' [[User:Mobius|Francesco "Mobius" D'Amico]], Michal "Shiv" Cywinski, Freespaceking 

''Number of missions:'' 

'''INFR1:''' Main campaign: 15 

'''INFA:''' Main campaign: 20 

'''INFASA:''' Main campaign: 30+ 
TeOO: *classified* 
THoD: *classified* 

'''INFA2:''' Main campaign: 30+ 

'''INF SCP:''' Chapter One: 30+ 
Chapter Two: 20+

'''Mods included:''' Various 
 

===Story and general notes===

Inferno is without any doubt the largest mod based on the FreeSpace universe and surely one of the oldest since it's been in development for several years.

There are separate Inferno continuities - the old and the new one. No mods of the new continuity have been released yet, with INFASA being the only one sufficiently close to release.

===Criticisms===

Many community members found what appear to be a few glitches in Inferno:

*Presence of extremely large and unused warships
*Poor plot
*Overpowered weapons

While the old continuity may be affected by those problems, the new one will try to solve them in the most effective way.

==Old Continuity==
===[[Inferno Release 1]]===
'''Also known as: INFR1, INF:R1, Inferno: R2, Inferno R2, Inferno: Release 1'''

Mostly known with the abbreviation INFR1, this is the first release of the Inferno MOD, now compatible with FS Open thanks to a patch.

[[Inferno R1 Ship Database]]

===[[Inferno Release 2]]===
'''Also known as: INFR2, INF:R2, Inferno: R2, Inferno R2, Inferno: Release 2'''

Originally supposed to be INFR1's sequel, all progress on INFR2 stopped and the mod has no longer been in development for several years.

===[[Inferno: Alliance]]===
'''Also known as: INFA, INF:A, INFA1(may also refer to INFASA)'''

Inferno: Alliance, or INFA, is another MOD ideated by Woomeister and released in late 2006. It takes place in Sol many years after the collapse of the jump node connecting the system to Delta Serpentis.

An upgrade of INFA, INFASA, is currently in progress. INFASA is intended to fully replace its predecessor.

[[Inferno: Alliance Ship Database]]

==New Continuity==
===[[Inferno: Alliance Standalone]]===
'''Also known as: INFA:SA, INFASA, INFA1(may also refer to INFA)'''

Currently a WIP MOD, INF:A SA(or INFASA) is intended to replace Inferno: Alliance with a more complex story and several new combat assets. The plot background is the same seen in INFA - after the collapse of the Delta Serpentis jump node, Sol colonies regain their independence and GTA authorities are progressively removed.

The mod is compatible with the FS Port and the presence of small VP files ensures full compatability with many FS Port campaigns using MODs.

The release date has yet to be defined because of intense feature creeping, testing and upgrading.

===[[Inferno: Alliance 2]]===
'''Also known as: INFA2, INFA:2'''

Although it's a sequel of INFASA, INFA2 is considerably different from its predecessor. Closer to INF SCP than INFASA, INFA2 will tell the story of the [[Earth Alliance|Earth Alliance's]] efforts in taking full control of Sol by defeating the feared [[Jovian Coalition]].

===[[Inferno SCP]]===
'''Also known as: INF SCP, INFR2(incorrect name)'''

Like INF:A SA, INF SCP will rewrite the story of its predecessor(INFR1) and its supposed sequel, INFR2. The new MOD has been in the works for many years and features a lot of models and new effects. Changes to the first part of the storyline, the one already seen in INFR1, are considerable under many points of view.

Due to the lack of free time, the release date of INF SCP is yet to be defined. FREDding is somewhat in progress but modelling and texturing still requires many efforts.

==Related Links==
[http://inferno.hard-light.net/ Inferno: SCP Site] 
[http://www.hard-light.net/forums/index.php/board,20.0.html Forums] 
[http://inferno.hard-light.net/SOL Inferno Alliance Site] 

[[Category:User-made_Campaigns]]
[[Category:Inferno]]
[[Category:Non-canon]]

Talk:GTD Eisenhower

2009-03-16T22:37:17Z

BlueFlames: Response

=="Name Origin"==

Are you sure it fits? I see it more as a Trivia instead. --- [[User:Mobius|Mobius]]

:It makes sense to me. The section explains where the name comes from, hence "origin". Moreover, while I know the FS Wiki isn't the Wikipedia, trivia sections [http://en.wikipedia.org/wiki/Wikipedia:Trivia_sections aren't very encyclopedic]. -- [[User:BlueFlames|BlueFlames]] 22:37, 16 March 2009 (UTC)

GTD Eisenhower

2009-03-16T00:23:02Z

BlueFlames: "Name Origin" instead of "Name Trivia".

{{Unique ship|''Unknown, possibly an [[GTD Orion|Orion]]''|[[Terran-Vasudan War|The Terran-Vasudan War]]|''Unknown''|''Unknown''|Destroyed by the first Vasudan [[PVD Typhon|''Typhon'']]-class destroyer encountered by [[GTA]] forces|''Unknown''|Eisenhower}}

Nothing is known about the GTD ''Eisenhower'' other than that it was apparently destroyed by one of the early [[GVD Typhon|''Typhon'']]-class destroyers during the [[Vega Engagement]], important battle of the [[Terran-Vasudan War]]. Almost certainly, the warship was part of the 4th Fleet.

==Name Origin==
[http://en.wikipedia.org/wiki/Dwight_D._Eisenhower Dwight David Eisenhower] served as commander of Allied forces fighting in Europe during World War II and later become the 34th President of the United States.

Various Terms

2009-03-16T00:16:48Z

BlueFlames: Clarification of the GoG entry.

This is a list of '''terms, abbreviations, and other jargon''' that the FreeSpace community uses.

==Fan Terminology==
* '''AAA''' - Anti-figther beam
* '''AWOL''' - Absent without leave. In FreeSpace, it is used to refer to the debriefing stage that tells the pilot when he left the area without being authorized to do so.
* '''CM''' - Countermeasure
* '''CB''' - Command Briefing.
* '''CBAnim''' - Command Briefing animation.
* '''Colly''' - The [[GTVA Colossus|GTVA ''Colossus'']]
* '''[[FRED]]''' - FReespace EDitor. The program created by Volition to make the mission and campaigns for both FreeSpace games. Released to the public along with said games.
* '''SEXP''' - Symbolic EXPressions. Special function strings within FRED that allow for complex mission objectives and other things to be carried out by a mission bulider.
* '''[[Portal:FreeSpace 1 | FS1]]''' - Descent: FreeSpace, The Great War. Also called Conflict: FreeSpace, The Great War in Europe. The first game of the series.
* '''[[Portal:FreeSpace 2 | FS2]]''' - FreeSpace 2. The second game of the series.
* '''[[FreeSpace 3 | FS3]]''' - FreeSpace 3. Would be the third game of the series, but it won't happen. There is no FS3.
* '''FS2_Open''' - The open source version of FS2.
* '''FSO''' - The open source version of FS2. Used interchangably with FS2_Open.
* '''GOG''' or '''GoG'''- Good Old Games. A digital distribution website that sells copies of FreeSpace 2. See [[Getting FreeSpace]].
* '''Retail''' - The original, unaltered version of FreeSpace 2. (=not FreeSpace Open)
* '''RTB''' - "Return to base." Used to refer to the directive that tells the player to return to base.
* '''SCP''' - Source Code Project. The people responsible for creating, maintaining and debugging FS2_Open.
* '''V''' or '''[V]''' - [[Volition]] Inc., the developer of FreeSpace and FreeSpace 2.
* '''VBB''' - Volition Bulletin Board. The boards Volition maintained as a centre for the FS community. Now defunct.
* '''HUD''' - Heads-up Display.
* '''HOTU''' - Home of the Underdogs. A website used to have some copes of FreeSpace 2 for purchase. See also GOG
* '''HLP''' - [[Hard Light Productions]], the hub of the FreeSpace community.
* '''Lucy''' - The [[SD Lucifer|SD ''Lucifer'']]
* '''VW''' - Volition Watch, developer fansite covering the FreeSpace, Red Faction and Summoner series. Awaiting demolition.
* '''F2S''' - FreeSpace 2 Sector - Smaller FS2 community.
* '''MediaVP''' or '''MVP''' - VP files with graphical enhancements for FreeSpace Open
* '''SG''' - Sectorgame - Network which hosts F2S. Often used interchangably (though inaccurately) with F2S.
* '''TC''' - Total Conversion. See [[Total conversions]]
* '''FS2NetD''' - FS2 Network Game Monitor - Utility used to monitor FS2 network games being operated on the FS2Net servers.
* '''FSPort''' - FreeSpace 1 ported to run on FreeSpace 2.

===Abbreviations of campaign names===
:''This list is incomplete and not necessarily up-to-date. See also [[Narwhal's Campaign List]]
*The 158th: The 158th Banshee Squadron
*AAB: Ascension and Beyond (dead)
*AHTW: All Hands to War (not hosted at HLP)
*AotD: Angels of the Damned (not hosted at HLP)
*TAP: The Apocalypse Project
*TBP: The Bablyon Project
*BtRL: Beyond the Red Line (not hosted at HLP, it can be found on GW)
*BWO: Blackwater Operations
*CoW: Casualties of War
*CoS: Nukemod - Children of Shiva (also refered to as Nukemod-CoS or just Nukemod)
*DEM: Deus Ex Machina
*FA: FRED Academy (This is not a campaign)
*FotG: Fate of the Galaxy (also known as the Star Wars Conversion)
*FSC or FSPort: FreeSpace Conversion or FreeSpace Port (they're the same project)
*FSU: FreeSpace Upgrade Project
*INF: Inferno, can refer to any Inferno mod
*INFA or INFA1: Inferno Alliance
*INFA2: Sequel of INFA1 or INFA
*INFR1: Inferno Release 1
*INFASA: Inferno Alliance Standalone
*INF SCP: Inferno SCP
*ITHOV: Into the Halls of Valhalla
*JAD: Just Another Day
*JtEP: The Journey to Epsilon Pegasi
*LM: The Lightning Marshal
*MT: Machina Terra
*MG: Mind Games
*NTV: Neo-Terra Victorious
*PI: The Procyon Insurgency
*RR: Renegade Resurgence
*SA: Scroll of Antankharzim
*SoL: Shadows of Lylat (not hosted at HLP, it can be found on GW)
*ST: Silent Threat
*ST:R: Silent Threat: Reborn (a FreeSpace Port campaign)
*SWC: See FotG (Fate of the Galaxy)
*TI: Twisted Infinities
*TotT: Teeth of the Tiger (Also ToT)
*TTP: The Titan Project
*TS: Technological Superiority (discontinued)
*TVWP: Terran-Vasudan War Project
*WCS: Wing Commander Saga

===File extensions===
These are FreeSpace-related extensions only.
*.ani - Animation files such as explosions
*.fc2 - FreeSpace 2 campaign
*.fs2 - FreeSpace 2 mission
*.fsm - FreeSpace 1 mission
*.pof - Model files with additional gameplay-related information like position of subsystems, turrets, etc.
*.tbl - Table file
*.tbm - Modular table
*.vp - Volition package files

===Multiplayer Terminology===
Following lists some of the terms commonly seen on multiplayer chat screens.
*'''AE''': Area-Effect weapon. These include EMP missiles, Infyrnos and Piranhas.
*'''AI:''' Computer-controlled ships
*'''Coop''': Cooperative game. All players are on the same side and work together to accomplish the mission objectives.
*'''Dogfight''': A free-for-all type of game, essentially the Deathmatch of FreeSpace. All players are on their own and fight for survival.
*'''EMP:''' The EMP missile
*'''Fire:''' The Infyrno missile
*'''Fish:''' The Piranha missile
* '''Lag''': "Jumpiness" in a multiplayer game due to slow Internet connections. FreeSpace has always had a lag problem, and even modern, high-speed connections have trouble hosting and playing online FreeSpace games. Can be greatly migitated by having all players set their "Object Update" setting to Low.
* '''Lag bombing''': Double-linking your secondary slot, firing, then quickly switching to your other secondary slot and firing it. Continue cycling and firing secondary slots until the server finally updates and you must wait to reload. This is often outlawed in multiplayer games.
*'''Lock/Unlock:''' Refers to the "Lock" button on the mission briefing screen. The host (or in TvT game, team captains) have to click the "Lock" button to allow other pilots/wingmates to make ship/loadout changes.
*'''LOW (object updates):''' Setting the "Object Updates" on "LOW" on the multiplayer options page - the preferred setting for MP clients. Limits the connection bit rate between the MP host and the client in order to make the game run smoother for everyone. Using something else than LOW against host instructions may get you kicked! Later FS2 Open builds provide a means for the host to force low object updates (the -cap_object_update flag).
*'''SD:''' Self Destruct (by pressing SHIFT+END)
*'''STD rules:''' Standard Rules - A set of rules commonly followed in TvT matches: no AI, no EMP, no Fire, no Fish, no SD allowed during the game.
* '''Tab loading''': A procedure by which server lag allows one to load a ship with a weapon that it isn't able to carry by default, eg, Helios on a Perseus. Specifically, keep the TAB key held down while you switch ships and quickly jump to the weapons loadout screen to load a prohibited weapon on to your new ship. The server still thinks that you have your old ship selected, and so its "weapons permissions" will not update in time to prevent you from loading something illegal. This usually considered a cheat, but some of the old multiplayer maps were actually made to acommodate this tactic.
*'''TvT''': Team versus Team game. The players are divided into two sides and fight for supremacy.

[[Category:Multiplayer]]

==Ingame Terminology==
*'''ETS''' - Energy Transfer System
*'''HUD''' - Heads-up Display. The interface the player uses while flying.
*'''Subsystem''' - Targetable and destroyable systems of a ship, e. g. radars, engines.

===Designation Prefixes===
* GT_ - [[Galactic Terran Alliance | Galactic Terran]]
* NT_ - [[Neo-Terran Front | Neo-Terran]]
* GV_ - Galactic Vasudan
* PV_ - [[Parliamentary Vasudan Empire | Parliamentary Vasudan]]
* GTV_ - [[Galactic Terran-Vasudan Alliance | Galactic Terran-Vasudan]]
* S_ - [[Shivan]]
* A_ - [[Ancient]] (non-canon)
* HL_ - [[Hammer of Light]] (non-canon, but very commonly used)

===Designation Suffixes===
* _A - [[Advance Warning and Control System | AWACS]]
* _B - Bomber
* _C - Cruiser
* _Ca - Carrier (non-canon)
* _Cv - Corvette
* _D - [[Destroyer]]
* _Dr - Drone
* _Dn - Dreadnaught (non-canon)
* _EP - Escape Pod
* _F - Fighter
* _Fg - Frigate (non-canon)
* _Ff - Frigate (non-canon)
* _Fr or FR - Freighter
* _G - Gas Miner
* _H - Hive (non-canon)
* _I - Installation
* _J - [[Juggernaut]]
* _M - Medical Ship
* _NB - Navigation Buoy
* _S - Support Ship
* _SG - Sentry Gun
* _SJ - Super Juggernaut (non-canon)
* _T - Transport
* _W - Weapon ([[Weapon Comparison (FS1) |FreeSpace 1]])([[Weapon Comparison (FS2) |FreeSpace 2]])

===Fighter Units and Roles===

*'''Wing''' - A unit of fightercraft, varying in size from one to six ships. The normal number is four. Ships of a wing are labelled by their wing name and a number (i.e. Alpha 1, Alpha 2, and so on). The GTVA uses the Greek alphabet for its wings and the signs of the zodiac for hostile wings. In FS1, Shivan wings were named after Hindu gods. '''Wing''' is also sometimes used for freighter or transport groups.
*'''Squadron''' - Refers to an organized group of pilots, e. g. [[242nd Suicide Kings]]
*'''Stealth Recon''' - Fighters that specialize in infiltrating hostile territory and acquiring information without being detected. The [[GTF Pegasus|GTF ''Pegasus'']] and the [[GVF Ptah|GVF ''Ptah'']] are the only canon stealth fighters.
*'''Interceptor''' - A fighter role that aims at the destruction of hostile fighters and bombers. Interceptors are fast and agile, but are weakly shielded and armored.
*'''Space Superiority''' - A versatile fighter role that is capable in all sorts of roles, except for bombing. A celebrated example of a Space Superiority fighter is the [[GTF Myrmidon|GTF ''Myrmidon'']]
*'''Heavy Assault''' - Heavy Assault fighters have tremendous secondary capacity, heavy shielding and armoring at the expense of speed and maneuverability
*'''Bomber''' - A bomber is a very heavy craft that specializes in carrying bombs. They attack freighter-size ship and above. Bombers are very slow and easily taken down without fighter escorts. Bombers are further categorized into light, medium, and heavy bombers.

===Ship Types===

'''Cruiser''' - Smallest combatant capital craft classification. Cruisers are at least several times the size of a fighter or bomber and possess mainly antifighter weaponry, with one or two (or in the case of the [[SC Rakshasa|SC ''Rakshasa'']], three) anticapital weapons. The defensive fire of a cruiser is rarely capable of stopping a determined bomber wing, and most are vulnerable to even a well-handled lone fighter. Unable to carry fighters. Canonical examples include the [[GTC Fenris|''Fenris'']] and the [[GTC Leviathan|''Leviathan'']]. In FS1, cruisers were deployed for both offensive and defensive tasks by all sides to any situation not requiring the attention of a destroyer. In FS2 Shivan cruisers are often deployed in mainline antiship and strike roles, while GTVA cruisers tend to be used as escorts and patrol craft.

'''Corvette''' - Middle ground combatant capital craft, falling between the cruiser and the destroyer in size and capablity. Equipped with between two and four anticapital weapons and considerably more impressive antifighter armament than a cruiser. Corvettes are capable of defending themselves adequately against a small number of enemy fighters or bombers. With the exception of the [[SCv Moloch|SCv ''Moloch'']], corvettes are unable to carry fighters of their own. Corvettes appear to handle most of the antiship and strike duties for the GTVA fleet; Shivan corvettes are extremely rare and have only been deployed against GTVA destroyers canonically. Whether this is their role or not is guesswork.

'''Destroyer''' - Large combatant capital craft, combining the functions of destroying enemy ships and transporting fighters. Destroyers vary wildly in armament and effectiveness against different types of targets. They will have at least one heavy-calibur anticapital weapon and probably several more, plus a number of cruiser-corvette anticapital weapons. Destroyers tend to need fighter cover more than corvettes; some of them actually mount fewer antifighter weapons, and all have much larger amounts of surface area that needs to be defended. Any situation with the direct involvement of a destroyer-class ship is by definition serious.

'''Superdestroyer''' - Bigger, meaner, and tougher than a destroyer, yet too small for the juggernaut classification; first applied well before the juggernaut classification came into existence. Only the [[GTD Hades|''Hades'']] and [[SD Lucifer|''Lucifer'']] have canonically been given this classification. The nature of the canonical superdestroyers was such that any appearance by them indicates ''the'' major effort by the controlling side. Their success is often decisive for that system, while their failure is a blow that is difficult to recover from.

'''Juggernaut''' - The pinnacle of combatant capital craft, a juggernaut is capable of making mincemeat out of an enemy fleet singlehanded and is superbly equipped to combat other capital craft. Due to its large surface area its defenses against fightercraft attack are generally somewhat thinly spread, but a juggernaut's sheer ability to absorb damage means that only another juggernaut or a mass attack by corvettes and destroyers is capable of destroying one in anything like a timely manner. Only the [[SJ Sathanas|SJ ''Sathanas'']] has canonically been given this classification, though the ''Colossus'' could also be classified as juggernaut. The presence of a juggernaut, like a superdestroyer, indicates the controlling side considers the mission absolutely essential; decisive for the system if not the campaign or the entire war.

'''Installation''' - A space station, described as "installation" because of its size, self-sufficiency, and permanence. The only installation class canonically known is the [[GTI Arcadia|Arcadia]]. The [[Galactic Terran-Vasudan Alliance|GTVA's]] naming system for installations generally includes something indicating their nature. Installation Riveria, Tombaugh Station, [[Enif Station]], and the Vega Installation are examples.

{{non-canon section|

'''Carrier''' - Ship of any size whose primary purpose is to carry fightercraft, whether directly into combat or standing off and lending fightercraft support to ongoing operations as needed.

'''Frigate''' - Semi-canonical ship class, both the Hippocrates and the Iceni have been referred to as frigates; the normally accepted role of a frigate is that of a pocket destroyer, lacking a fighterbay and fighter support facilities/crews enabling the ship to be shrunk down to only slightly bigger than a corvette.

'''Dreadnought''' - Generally understood to be a destroyer-sized craft, but built for the sole purpose of ship-to-ship combat and lacking a fighterbay or supporting a very limited number of fighters purely for self-defense.}}

===Weapons===
*'''AAA''' or '''AA''' - Anti-fighter beam cannon
*'''Aspect-seeking''' - A type of secondary that must acquire a lock to track the target. See [[GTM Harpoon]].
*'''Blob turret''' - A primary weapon-based, warship-mounted turret. [[Terran Turret]] is a prototypical example of it.
*'''Countermeasure''' or '''CM''' - An anti-missile defensive mechanism for fighter-sized craft.
*'''Dumbfire''' - Secondary weapons cannot acquire any kind of lock on the target. See [[GTM Tempest]].
*'''Heat-seeking''' - A type of secondary weapon that acquires instant lock on the nearest target and chases it until it gets out of its cone.
*'''Primary''' - Primary weapons in ''FreeSpace'' are energy-based lasers.
*'''Secondary''' - Secondary weapons in ''FreeSpace'' are missiles and bombs.
*'''Slash beam''' - A slash beam is a type of beam weapon.
*'''Swarm missile''' - Swarm missiles are secondary weapons that are fired in multiple numbers. See [[GTM Hornet]]

==Terms related to modelling==
*Greeble: Small piece of detail which serve no other purpose only to make a ship look better.
*LOD: Level of Detail. The further you get away from a ship, the less detailed it will be rendered.
*TrueView: A plugin utility for [[trueSpace]]. Ideal for building hierarchy. However, not a must.
*Single-part turret: A single-part turret, is, in a word, a turret without any barrels.
*Multi-part turret: A multi-part turret is, in a word, a turret with one, two or three barrels.

[[Category:Lists]]

Talk:POFCS2Help/HelpHome

2009-03-09T02:45:56Z

BlueFlames: New page: Kazan, was this page intended to be more than an index? If so, that's dandy. Otherwise, I've set up a category to automatically index related articles, so that they won't require the pag...

Kazan, was this page intended to be more than an index? If so, that's dandy. Otherwise, I've set up a category to automatically index related articles, so that they won't require the page title prefix, and you won't have to babysit this page. -- [[User:BlueFlames|BlueFlames]] 02:45, 9 March 2009 (UTC)

POFCS2Help/HelpHome

2009-03-09T02:42:15Z

BlueFlames: Catagorizing & grammar.

This is the stub page for the PCS2 Help Cooperative authoring. Please add all pages to the PCS2 Cooperative Authoring category.

Once this project is finished, [[User:Kazan|Kazan]] will export and include it with PCS2 releases as the official help.

{{Stub}}

[[Category:Modding]]
[[Category:PCS2 Cooperative Authoring]]

Blender to POF Conversions

2009-03-09T02:38:27Z

BlueFlames: Catagorizing.

==General requirements for the Blender scene:==
===Orientation:===
For those who can understand it: 
:Stern to Bow axis = Freespace Positive Z axis = Blender Positive Y axis
:Starboard to Port axis = Freespace Positive X axis = Blender Negative X axis
:Belly to Topside axis = Freespace Positive Y axis = Blender Positive Z axis

For those who don't: 
:Go to a top down view of the scene with Numpad-7. You should be looking down at the topside of your ship, with the ships bow pinting up your screen.

===Scale:===
1 Blender unit = 1 Freespace meter, so scale your model to the exact in-game dimensions you want it to be.
To do this, press N to bring up the Transform Properties window and pay attention to the DimXYZ section bottom right. Those are the dimensions of the selected object in Blender units. 
To avoid potential problems with scale and orientation during conversion, you want the RotXYZ and ScaleXYZ fields to read 0,0,0 and 1,1,1 respectively - which you can achieve by pressing Ctrl+A->"Scale and Rotation to ObData" for the selected objects. Doing this will basically hold that object still while setting those fields to 0s and 1s.

===Geometry:===
As far as I have been able to tell, all geometry the PCS2 Collada importer will accept must be fully triangulated. (Ctrl+T to triangulate selected object) 
All mirror or edgesplit modifiers must be applied before exporting or they won't work and you'll end up with half your model or something. ;) 
Messy geometry will ''usually'' convert correctly anyway, but I would suggest making it a point of pride to produce clean meshes that will ''definitely'' convert. That is, avoid faces that exactly overlap onto each other, faces that are formed between 3 verts in a row (ie, 0 area faces), shattered faces where all or parts of a face are completely detached from surrounding geometry for no good (eg, smoothing) reason.

An excellent error checking tool in blender is the 'select non-manifold' function, which highlights holes in the mesh. To use it, select the object you wish to investigate, enter edit mode and toggle A until you have nothing selected. Set your mode to edge mode (Ctrl + Tab->'Edges' or press the edge icon at the bottom of the 3d View panel) and go to the Select menu in the 3d View panel and click Non-Manifold. All edges that form the perimeter of a hole will be selected, so you can identify areas that should be repaired. (Note: When used with the mirror modifier, this function will select all the edges that form the place where the mirrored side will attach to the 'real' side. This is normal so don't worry about it there.)

===Smoothing:===
Blender does not use smoothgroups as they are seen in other modelling programs, but it has something pretty close and just as effective. It involves a Three-stage process:
# Select the edges that will make up the perimeter of the area you want to be smoothed (ie, the area you want to become a single smoothgroup) and press Ctrl+E->'Mark Sharp'.
# Use Ctrl+E->'Loop to Region' to select the faces that are inside that perimeter and set them to be smoothed by either the 'Set Smooth' button in the editmode button panel or Ctrl+F->'Shade Smooth'.
# Outside of edit mode, add an Edge Split modifier set only to 'From Marked as Sharp'.

If you apply this modifier before the final export, these smoothgroups will survive the conversion intact and can GREATLY enhance the apeal of an in-game model.

===Textures:===
The PCS2 Collada importer will read textures from whatever images are assigned to each face of an object in Blenders UV editor (NOT from the materials button panel!) 
As such, assuming you have UV mapped the model and have an associated texture ready, select all the faces of the model that use that texture and in the UV/Image Editor view open up that image. (If it's loaded already it will be in the drop down list, if not go to Image->Open)

===Levels Of Detail:===
LODs are lower detail duplicates of the main mesh used when the ship is so far away from the player that rendering it at full detail would be a big waste of your graphics card's resources. While not a requirement (FS will work fine without them), it's standard practice to include at least two lower LODs as well as the main hull. 

The main lod object should be named ''''detail0'''' (case sensitive), first LOD ''''detail1'''' second ''''detail2'''' and so on. Don't use more than 4 LODs in total as the LODs themselves will become a waste of memory. 

These LODs should not be parented to any other object as they're basically the top of the hierarchy of the model. Also, they should all have their object centres set to the origin of 0,0,0. 

Example:
detail0
|-<subobjects of detail0>
detail1
|-<subobjects of detail1>
detail2
|-<subobjects of detail2, though by this stage there shouldn't be any>

===Nameplates/Cockpit Glass:===
Transparent objects are handled quite badly by FSO at the time of writing, and so the following technique is basically a hack to get around that. 

If you have anything that requires transparency as a part of the hull or any subobject, you must:
# Select all faces that will need to be transparent. (For cockpits this means all the polys that would be the glass, and for nameplates it means just the floating nameplate rectangle polys)
# Detach these faces from the mesh they're a part of so they form their own mesh.
# Assign them the texture if nessecary. (For cockpit glass just give it any old image called 'glass' and for nameplates give it any old image called 'nameplate'. Both these textures exist in the 3.6.10 MediaVPs and so will be used on your model with no further worry about it. If you need some other form of transparency you'll have to make your own transparent texture and use that.)
# Name the object in the form of ''''<Object the transparent polys came from>-trans''''. So for example, the glass or nameplate would be called 'detail0-trans', because they were pulled off the main hull.
# Parent the transparent polys object to whatever object they originally came from. (Select the transparent object, then the parent object and press Ctrl+P->'Make Parent' ) For glass or a nameplate this would of course be detail0.

What basically happens is that PCS2 will re-attach the transparent polys to their parent object last in the list, which lets Freespace draw them last of all and so correctly transparent. 

Example:
detail0
|
|-radardish
| |
| |-radardish-trans
|
|-detail0-trans (nameplate)

===Debris:===
Debris chunks are the pieces that hurl themselves in all directions when a ship explodes. A ship that has no debris will have nothing left at all when it explodes which is really boring! I would recommend constructing full-ship-volume debris for the best explosion effects, as it means that when it explodes the ship essentially just cracks apart and drifts off, which looks much cooler than nothing or a piece here or there. 

Anyway, to make debris objects ready for conversion they should be named ''''debrisXX'''' where XX starts at 01 and can go up to 99, though typically any more than about 20 is excessive.. 

Example:
detail0
detail1
detail2
debris01
debris02
debris03 etc

===Single-part Turrets:===
All turrets should be named with the word ''''turret'''' or ''''gun'''' in them so FS knows to treat them differently to normal subobjects. Beyond that they can be called whatever you like, though standard practice is just ''''Turret01'''', ''''Turret02'''' etc. 

NOTE: Many people myself included much prefer to set up turret firepoints, paths and properties in PCS2 after the conversion, where it's a bit easier and less likely to break during conversion. 

To set up the firepoints of a turret in blender, you'll need to use Empties (also known as helpers). (To create an empty, just press Ctrl+A->'Empty' ) 

The basic layout for empties is to have a parent empty attached to each subobject, and then several empties attached to it for things like firepoints, path and properties, looking like this: 

Example:
detail0
|
|-turret01
|
|-helper01 (NOTE: This top level empty must begin with the word 'helper' )
|
|-Firepoints01
| |
| |-Firepoint1 (NOTE: The orientation of these empties is important - the turret will fire down their Z axis)
| |-Firepoint2
|
|-Path07
| |
| |-Path07-01
| |-Path07-02
|
|-Properties01
|
|-$fov=180
|-$name=laser_turret
|-$special=subsystem

===Multi-part (rotating) Turrets:===

Multi-part turrets consist of two parts: the Base and the Arm. Since the arm needs to inherit the rotation of the base it's attached to, you need to parent it to the base (ie, select arm, base and press Ctrl+P->'Make Parent' ). Note that each turret can only have ONE arm object, but within that object you might have three separate pieces of geometry or so to form three barrels. The turret base should be parented to the LOD it is associated with - typically detail0. 

As multi-part turrets need to rotate in-game, they need to have careful attention paid to where their object centres are, or they could spin right off the ship or something equally stupid looking. Place the centres at the points where each piece (arm and base) of the turret would pivot around. Turrets on the topside of the ship must face forwards while turrets on the belly must face backwards. 

'''All''' turret arms must point straight up out of their base or they will not rotate correctly. 

As with single part turrets, the naming must include ''''turret'''' or ''''gun'''' in it somewhere so FS knows to treat it differently, and standard practice is to call the base ''''Turret01-base'''' and the arm ''''Turret01-arm''''. Also again it is easier to set up turret data in PCS2 after conversion (Setting the turret axis rotation MUST be done in PCS2 in the subobjects field after conversion or else your turrets won't work at all) 

Setting up firepoints, paths and properties in Blender is the same as for single part turrets.. 

Example:
detail0
|
|-Turret01 (single part turret)
|
|-Turret02-base
|
|-Turret02-arm
|
|-helper02
|
|-firepoints02
| |
| |-firepoint02-01
| |-firepoint02-02
|
|-path07
| |
| |-path07-01
| |-path07-02
|
|-properties02
|
|-$fov=180
|-$name=main%turret (The % will be converted to a space automatically)
|-$special=subsystem

===Subobjects/Modeled Subsystems:===

These are just done like single part turrets if they don't need to rotate and like multi-part turrets if they do (like radar dishes). You can have an empty system as with turrets if you like, but again this is better done post-conversion. 

To make destroyed models for modeled subsystems or turrets, create a model of the wrecked subsystem and put it in the position it will be in when that subsystem is destroyed. Name it ''''<Subobject name>-destroyed'''' and Freespace will only make it appear when that subobject has been destroyed. Ie, ''''Turret01-destroyed''''. 

As with rotating multi-part turrets, rotating subobjects axis rotation must be set up in PCS2 after conversion. 

Example:
detail0
|
|-radardish
|-radardish-destroyed

===Regular Subsystems:===

Subsystems are done by placing empties, and then scaling them up to the diameter of the desired subsystem. As with turrets, they can have their properties of '$special=subsystem' added (in the same hierarchy - ie, children of the helper, as seen with the turrets) either in Blender or preferably in PCS2 after conversion. 

To name them correctly, simply call them ''''subsystemcommunications'''' or ''''subsystemweapons'''' etc. Subsystems should not be children of anything. 

Example:
detail0
detail1
detail2
subsystemweapons
|
|-helper
|
|-path03
| |
| |-path03-01
| |-path03-02
|
|-properties
|
|-$special=subsystem

===Gun/Missile ports:===

For fighters and bombers, you can set up gun and missile points by creating empties representing the gun/missile banks, with children empties representing the individual firing points contained in that bank. 

So for example, you would have the parent empty ''''gunbank01'''' with children ''''gunbank01-01'''' and ''''gunbank01-02'''' representing the locations and orientations (down the emtpies' Z axis) of the two individual firing points in that bank. Gun and missile banks should not be children of anything. 

Example:
detail0
|
|-gunbank01 (This will create a gunbank with two firepoints on it)
|
|-gunbank01-01
|-gunbank01-02

===Shields:===

Shields are usually made of only 80 polygons and must be fully triangulated, enveloping the entire model. Name the object ''''shield''''. Shields should not be children of anything. 

Example:
detail0
detail1
detail2
shield

===Insignia:===

Squadren Insignia should be treated similarly to nameplates in terms of making them on a set of faces that floats just above the hull. 

UV map them and apply a texture called 'insignia' (it's a good idea to use an actual insignia texture here), and call them: ''''insigLODXX-YY'''', where XX is the LOD number and YY is the number of this particular insignia (for if you have more than one). As you may be able to tell, you can create insignia that will appear on LODs too which is a good idea to do or else it will suddenly vanish when the ship moves out a way and the LOD clicks over. 

Insignia should not be children of anything. 

Example:
detail0
detail1
detail2
insigLOD01-01 (This and the one below will '''actually''' be assigned to detail0. The two last ones will be assigned to detail1)
insigLOD01-02
insigLOD02-01
insigLOD02-02

===Docking Points:===

Docking points consist of '''two''' individual docking points, an associated path and properties. You can do all of this in PCS2 after conversion where it's a lot easier, but if you really want to you can do it in Blender too: 

Make two dockpoints (''''dockpoint01-01'''' and ''''dockpoint01-02'''') the children of a parent ''''dockpoint01'''' empty (which should not be the child of anything). The first point is the location and outwards normal of dockpoint01, and the second defines the 'front' of the dockpoint so that docking ships know which end is the front of the ship. 

Dockpoints can have paths and properties set up as with single part turrets, though dockpoints need 4 path verticies instead of the usual two, and can take the property of ''''$name=<dockport name>''''. 

Example:
detail0
detail1
detail2
dockpoint01
|
|-dockpoint01-01
|-dockpoint01-02
|
|-helper
|
|-path09
| |
| |-path09-01
| |-path09-02
|
|-properties
| |
| |-$name=DockingPort

===Engine Glows:===

These can be done in one of two ways:
# Just basic thrusters involves an empty called ''''thrusters'''' representing the glow bank, and children empties that represent the location and scale of the individual thruster glows. Here ''''thrusters'''' should not be the child of anything. 

Example:
detail0
detail1
detail2
thrusters
|
|-thruster01-01
|-thruster01-02

# Linked to an engine subsystem. Here the setup is the same as in 1), but ''''thrusters'''' is set as the child of the helper of the engine subsystem that is meant to be providing these particular engine glows. This way, when that particular engine subsystem is destroyed, only the glows linked to it are removed. 

Example:
detail0
detail1
detail2
subsystemengine
|
|-helper
|
|-path04
| |
| |-path04-01
| |-path04-02
|
|-properties
| |
| |-$special=subsystem
|
|-thrusters
|
|-thruster01-01
|-thruster01-02

===Glow Points:===

These involve a parent empty that must begin with the name ''''glowbank'''', and be the child of whatever subobject the glowpoints are attached to. Any children of ''''glowbank'''' will define the location and scale of individual glowpoints. They also use a helper->properties setup as seen previously, taking only the texture name the glowpoint to be drawn there in-game, such as: ''''properties''''->''''$glow_texture=yellowglow''''. 

Blinking settings can only be done in PCS2 after conversion, and in fact the entire glowpoint making process can be done there too. 

Example:
detail0
|
|-helper
|
|-glowbank01
| |
| |-glowpoint01-01
| |-glowpoint01-02
| |-glowpoint01-03
|
|-glowbank02
|
|-glowpoint02-01
|-glowpoint02-01

===Eyepoint:===

The eyepoint can again be done after conversion, but in Blender it is handled simply with a lone empty named ''''eyepoint01'''' that is not the child of anything. The Z direction of the empty indicates the direction it's facing in. 

Example:
detail0
detail1
detail2
eyepoint01

[[Category:Modding]]
[[Category:PCS2 Cooperative Authoring]]

POFCS2Help/BlenderToPOFConversions

2009-03-09T02:37:55Z

BlueFlames: POFCS2Help/BlenderToPOFConversions moved to Blender to POF Conversions: Using catagories for organization, rather than page title prefixes.

#REDIRECT [[Blender to POF Conversions]]

Blender to POF Conversions

2009-03-09T02:37:55Z

BlueFlames: POFCS2Help/BlenderToPOFConversions moved to Blender to POF Conversions: Using catagories for organization, rather than page title prefixes.

Category:PCS2 Cooperative Authoring

2009-03-09T02:36:51Z

BlueFlames: New page: Below are articles related to PCS2 Cooperative Authoring. Category:Modding

Below are articles related to PCS2 Cooperative Authoring.

[[Category:Modding]]

Alcibiades gamble

2009-02-23T10:54:08Z

BlueFlames: Redirecting to Alcibiades' Gamble

#REDIRECT [[Alcibiades' Gamble]]

Template:Main nav

2009-02-19T23:14:14Z

BlueFlames: Reflecting the move.

{| border=0 align=right cellpadding=4 cellspacing=0 width=30% style="margin: 0 0 1em 1em; background: #302020; border: 1px #AA2020 solid; border-collapse: collapse; font-size: 95%;"
! style="color: white; height: 30px; background: #512020; 70%;"|''Retail FreeSpace''
|-
| [[Portal:FreeSpace 1|FreeSpace 1]]
|-
| [[Portal:FreeSpace 2|FreeSpace 2]]
|-
! style="color: white; height: 30px; background: #512020; 70%;"|''FreeSpace Source Code Project''
|-
| [[Getting Started (FreeSpace Open)|Getting Started]]
|-
| [[Installing mods for fs2 open|Mod installation instructions]]
|-
| [[SCP_Additions|List of added capabilities]]
|-
| [[Portal:Multiplayer|Multiplayer]]
|-
| [[Command-Line_Reference|Command-Line Reference]]
|-
| [[Development_Reference|Development Reference]]
|-
| [[Feature Requests|Feature Requests]]
|-
! style="color: white; height: 30px; background: #512020; 70%;"|''Modding FreeSpace''
|-
| [[Portal:Modding|Modding Portal]]
|-
| [[Mod Database]]
|-
| [[Portal:FRED|FRED]]
|-
| [[User-made_Campaigns (FS2)|User-made Campaigns]]
|-
| [[Total conversions|Total Conversions]]
|-
! style="color: white; height: 30px; background: #512020; 70%;"|''Freespace Universe''
|-
| [[Portal:FreeSpace Universe|The Universe]]
|-
! style="color: white; height: 30px; background: #512020; 70%;"|''Other''
|-
| [[Various Terms|FreeSpace Jargon]]
|-
| [[FreeSpace Alpha]]
|-
| [[Freespace_Wiki:Community_Portal|FreeSpace Community]]
|-
| [[Getting FreeSpace]]
|-
| [[Guide to FS Open on Linux]]
|-
! style="color: white; height: 30px; background: #462424; 70%;"|Alternately, explore the '''FreeSpace''' universe through ''[[:Category:Main|categories]].''
|-
|}

<noinclude>[[Category:Templates|Main nav]]</noinclude>

Talk:The fs2 open on Linux Guide

2009-02-19T23:13:43Z

BlueFlames: Talk:The fs2 open on Linux Guide moved to Talk:Guide to FS Open on Linux: Capitalize your acronyms.

#REDIRECT [[Talk:Guide to FS Open on Linux]]

Talk:Guide to FS Open on Linux

2009-02-19T23:13:43Z

BlueFlames: Talk:The fs2 open on Linux Guide moved to Talk:Guide to FS Open on Linux: Capitalize your acronyms.

= Overhaul =

Due to the major overhaul this article has undergone, this page has been cleared. Revise and rollback at you discretion. [[User:Ni1s|ni1s]] 19:11, 3 September 2007 (CDT)

The fs2 open on Linux Guide

2009-02-19T23:13:43Z

BlueFlames: The fs2 open on Linux Guide moved to Guide to FS Open on Linux: Capitalize your acronyms.

#REDIRECT [[Guide to FS Open on Linux]]

Guide to FS Open on Linux

2009-02-19T23:13:43Z

BlueFlames: The fs2 open on Linux Guide moved to Guide to FS Open on Linux: Capitalize your acronyms.

{{Warning|This guide assumes some fundamental command line knowledge. As a rule of thumb, do not copy & paste commands without fully understanding them, especially as root. With great power comes great responsibility.}}

*[[Fs2_open_on_Linux/Introduction|Introduction]]
*[[Fs2_open_on_Linux/Preparation|Preparation]]
**[[Fs2_open_on_Linux/Installing Subversion|Installing Subversion]]
**[[Fs2_open_on_Linux/Installing the Development Libraries|Installing the Development Libraries]]
*[[Fs2_open_on_Linux/Acquiring the Code|Acquiring the Code]]
*[[Fs2_open_on_Linux/Pre-Compile Configuration|Pre-Compile Configuration]]
**[[Fs2_open_on_Linux/Optimization|Optimization]]
*[[Fs2_open_on_Linux/Compiling|Compiling]]
**[[Fs2_open_on_Linux/Compile Script|Compile Script]]
*[[Fs2_open_on_Linux/Acquiring the Game Data|Acquiring the Game Data]]
**[[Fs2_open_on_Linux/Extracting data from CD|Extracting data from CD]]
***[[Fs2_open_on_Linux/Installing unshield|Installing unshield]]
****[[Fs2_open_on_Linux/Data Installation script|Data Installation script]]
*[[Fs2_open_on_Linux/Post-Compile Configuration|Post-Compile Configuration]]
**[[Fs2_open_on_Linux/Graphics Settings|Graphics Settings]]
**[[Fs2_open_on_Linux/StartUp Script|StartUp Script]]
*[[Fs2_open_on_Linux/Troubleshooting|Troubleshooting]]
**[[Fs2_open_on_Linux/Common Compile-time Errors|Common Compile-time Errors]]
***[[Fs2_open_on_Linux/Novell SuSE and the Dependencies|Novell SuSE and the Dependencies]]
***[[Fs2_open_on_Linux/SDL: undefined reference to ...|SDL: undefined reference to ...]]
***[[Fs2_open_on_Linux/Missing -lGLU compile error|Missing -lGLU compile error]]
**[[Fs2_open_on_Linux/Common Runtime Errors|Common Runtime Errors]]
***[[Fs2_open_on_Linux/ERROR: "Web cursor bitmap not found."|ERROR: "Web cursor bitmap not found."]]
***[[Fs2_open_on_Linux/I18n and Key mapping problems|I18n and Key mapping problems]]
***[[Fs2_open_on_Linux/Dedicated X Display|Dedicated X Display]]
***[[Fs2_open_on_Linux/Joystick Errors|Joystick Errors]]

[[Category:FreeSpace Open on Linux]]