FreeSpace Wiki - User contributions [en]

SFr Iksura

2026-08-21T11:47:01Z

Mobius: A valuable hint from the mission designer

{{SRArticle}}
[[Image:SFr Iksura.jpg|thumb|right|650px|{{PAGENAME}}]]
[[Image:SFrIksuraCargo.jpg|thumb|right|650px|With several cargo attached. Cain for scale.]]
[[Image:SAC 4.jpg|thumb|right|450px|SAC4]]

SFr Iksura is fan-made Shivan freighter. It's capable of forming enormous cargo trains from multiple cargo units.

==Description:==
===Tech Room Description===
The Iksura is a new class of freighter that has been encountered for the last time at the very end of the war with the Shivans. Its capacity to carry sets of Shivan cargo containers makes it the most effective transportation asset ever seen in the history of known space travel. Many pilots have nicknamed it the 'Doomtrain', due to its capacity to carry up to ten SAC 4 units, each armed with defensive turrets. It is also believed that Iksuras emit powerful jamming fields which make them very difficult to locate and destroy. Due to their logistical capabilities, Command has classified the Iksura a non-active combatant Class A threat for the Alliance. Taking down an Iksura convoy and its cargo seems as vital as taking down a Shivan destroyer.

===SAC 4 Description===
The SAC 4 is a heavily armored bulk container that is only towed by the Iksura freighter. Its considerable durability suggests that it is intended to carry sensitive or valuable equipment and ammunition. It is also the only cargo container in the history of space travel to be equipped with defensive turrets. Although its turrets’ weapons are light compared to standard Shivan armaments, it is worth noting that Iksuras can carry up to ten of these units, resulting in a combined firepower more than capable of repelling interdictors.

===Credits===
* Lowpoly version by '''Woomeister'''
* Upgraded version by '''Nyctaeus'''

===Designer's Comments===

==Performance:==
===Statistics===
{{Ship_box
|name = SFr Iksura
|yaw_pitch_roll = 25 - 25 - 25
|max_velocity = 45 (40)
|hitpoints = 20000
|length = 327.99
|width = 150.25
|height = 101.43
|turrets = 10
|cargodocks = 1
}}

{{Ship_box
|name = SAC 4
|yaw_pitch_roll = 20 - 20 - 20
|hitpoints = 3500
|length = 184.69
|width = 149.13
|height = 203.68
|turrets = 2
|cargodocks = 1
}}

===Armaments===
*'''SFr Iksura'''
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=2 style="background:#351515;"| '''Default Statistics'''
|- align="center"
| style="width:120px" |Turret Type
| style="width:60px" |Amount
|- align="center"
| Emuzu
| 8
|- align="center"
| Guno
| 2
|}

*'''SAC 4'''
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=2 style="background:#351515;"| '''Default Statistics'''
|- align="center"
| style="width:120px" |Turret Type
| style="width:60px" |Amount
|- align="center"
| Emuzu
| 2
|}

==Gallery==
<gallery mode="packed-hover" heights="300px"></gallery>

==Modding Resources==
:$POF File: SerRes_Iksura.pof
:Texture list: Lucifer-HTL;damage

===Veteran Comments===
{{comment|It looks like the severed head of an [[SD Lucifer]] but it's actually a massive, unique kind of freighter. Its most distinct feature is a cargo dockpoint located on the aft. The cargo that comes with the Iksura features paired dockpoints at front and the back, so you can actually attach multiple cargo containers to a single freighter, creating a superfreighter of immense proportions. Note that the more cargo units you add to the train, the slower it will be. To balance this drawback, both the Iksura and the cargo are armed with multiple point-defense turrets and much more hitpoints than other Shivan freighters. These clustered turrets are really dangerous for light strikecrafts, but heavy fighters such as the [[Hercules]] and anything larger provide enough survivability to engage the Iksura. 
 
In older versions of FSO, an Iksura loaded with multiple SAC4 units generated an enormous subspace vortex during jumps. This is actually a bug caused by the additive nature of object masses in FSO. 
 
The Iksura is inspired by an official concept art from FS1. 
 
In [[Series Resurrecta]], these things are nothing more than the seventh level of hell for people who hate EMP effects. They generate a consistent, persistent EMP effect until destroyed, essentially forcing you to rely on your own primaries or Furies/Hornets to remove it from the equation. Taking down an Iksura helps making the EMP fade away, and the destruction of several Iksuras would finally allow the player to issue proper orders to wingmen and coordinate strikes against the remaining freighters. Killing the Iksura itself will also destroy all of the cargo containers behind it, but this will not happen in any other campaigns that use the Iksura unless specifically FREDded to do so. If crossfire from the containers is an issue, aim for the first container in the chain: its destruction will trigger a reaction, wipe out the entire chain at once, and leave the freighter completely exposed to allied attack.}}

==External links:==
*Series Resurrecta:
**[https://fsnebula.org/mod/SeriesResurrecta Series Resurrecta on Knossos | FSNebula]

[[Category: Series Resurrecta]]
[[Category:User-made Ships]]

Fiction Viewer

2026-08-01T12:25:30Z

Mobius: /* Syntax */

[[Image:2_fictionviewer.png|thumb|right|250px|The Fiction Viewer, FS2 style (click to enlarge)]][[Image:FictionViewer.jpg|thumb|right|250px|The Fiction Viewer (Wing Commander Saga style) with the first few paragraphs of [http://web.archive.org/web/20010308090656/vbb.volition-inc.com/ubb/Forum1/HTML/001723.html Tell A Story] (click to enlarge)]]

'''Fiction Viewer''' is a feature of [[Source Code Project|FreeSpace Open]] 3.6.10 implemented by [[User:Goober5000|Goober5000]]. It is sort of an advanced Command Briefing that mission designers could use to deepen the story that they want to tell without using the actual Command Briefing.

The Fiction Viewer is the first window that will come up in a mission, followed by the Command Briefing—if the mission has both.

==Using the Fiction Viewer (3.6.12 and newer)==
*Create a text file (.txt) that you want to show off with the Fiction Viewer, then put it into FreeSpace 2/data/fiction or FreeSpace 2/<your mod's directory name>/data/fiction.
*Open the mission in FRED. Select Editors --> Fiction Viewer and type in the file's name that you want to display, with its extension (for example: intro.txt).
*The fiction viewer requires additional interface art not provided by Volition, since this is a FSO enhancement. Without this, the game will not be able to display the fiction viewer and will skip right to the standard briefing (or command briefing). These files are available in mv_core in the mediavps, or you can download them separately from http://blueplanet.fsmods.net/E/fictionviewer.7z. The files in that archive must be extracted into the mod's data/interface folder.
*There are two modes for the fiction viewer. The default one is the "FS2" style, which retains the standard layout used by the FS2 interface art. The other is the "Wing Commander Saga" style, which moves the "Accept" button to the lower left side of the screen, and is customized for the interface art style of WCS. If you have interface art for the "WCS" style, you need to use "fictionviewerb" as the filename for the main interface background, and a fitting interface mask file named "fictionviewer-mb.pcx". For the 1024x768 resolution art, the filenames must be prefixed with "2_" (2_fictionviewerb, for example).

==Syntax==

<pre>

#Fiction Viewer

$File: r1-2-fiction.txt
$Font: sans
$Voice: 1-2 janus.ogg
</pre>

==General notes==
*You must provide the file's extension (.txt), otherwise the game engine will assume the file has no extension, and look for that.
*Since the text file is not in the mission file, semicolons (;) and double quotation marks (" ") will not break the mission code.
*The length of the text is effectively unlimited, since it is loaded on the fly and not subject to any of the hard-coded string limits.
*Color tags such as $r and $h will work.
*Characters that are not in the English alphabet (such as á, é) will not be displayed.
*The interface art can be modified by extracting the files from the VP.
*In 3.6.12 and later, the filename for the main interface screen has changed from "fvw" to "fictionviewer", to better follow the precedent set by the rest of the interface. Old interfaces must be adjusted for this, else it will cause a "No interface graphics found for the fiction viewer" error.
*In 3.6.12 and later, the fiction viewer allows a music track and a font to be defined for the fiction viewer. The font must also be listed in [[fonts.tbl]].

==External links==
*[http://www.hard-light.net/forums/index.php/topic,50565.0.html Fiction Viewer release thread]
*[https://www.hard-light.net/forums/index.php?topic=96226.0 Official FreeSpace Open 19.0.0 release thread] (most recent stable release)

[[Category:FRED]]
[[Category:Source Code Project]]

Guide to FS mod translations

2026-05-29T09:09:56Z

Mobius: Created page with "Translations have been quite rare in FreeSpace 2 despite the longevity of the community, so community member '''Achille44''' decided to create this guide, hoping it will m..."

Translations have been quite rare in [[FreeSpace 2]] despite the longevity of the community, so community member '''Achille44''' decided to create this guide, hoping it will motivate some people to join the endeavor. The objective of this tutorial is to explain how to translate FreeSpace 2 mods into non English languages.

This guide will be divided in 2 parts:
1. Internationalization - this part will be interesting for modders who want to make their mod easily translatable, or translators really motivated and who are ready to dive into technical stuff themselves.
2. Localization - this part will focus on the translation itself, so translators can directly skip to this part.

===Internationalization (i18n)===
Let's start with a bit of wikipedia explanation: "internationalization is the process of designing a software application so that it can be adapted to various languages and regions without engineering changes."

Historically, FreeSpace 2 has always been terrible in terms of internationalization, many parts of the original game were "hardcoded", which means that they were just not translatable, so translations could only be partial. But thanks to the hard work of the SCP devs, most of the game is now translatable.

BUT so far, most of the modders don't use the recent internationalization features for their mods, probably because the process is quite tedious and difficult to maintain. And given the small number of translations and translators, the effort may not seem worth it.

Here is the list of folders/files which may contain strings that need to be internationalized: 
/data 
/fiction: if the mod uses visual novel briefings, those cannot handle localized files by just appending the language suffix, unlike fiction viewer files. so you need to adapt the vn script to use XSTR features. You can find an example in the French translation of Solaris. 
/missions: 
*.fc2 files: all '$Name' properties must use XSTR. 
*.fs2 files: 
'$label', '$Callsign', and '$Name' properties must use XSTR. 
Convert sexp show-subtitle to show-subtitle-text, and then extract hardcoded strings from show-subtitle-text and put them into new messages so they can be translated. 
Convert ship alt names to sexp variables so that they can be translated via modify-variable-xstr sexp. 
Convert hardcoded texts in hud-set-text sexp to variables to be treated by XSTR. 
Convert the special senders to variables in the following sexps: send-random-message, send-message, send-message-list, send-message-chain. 
Add +Display Name property for all jump nodes. 
Convert the first sexp parameter to variable for the following sexps: add-nav-waypoint, add-nav-ship, del-nav, hide-nav, restrict-nav, unhide-nav, unrestrict-nav, set-nav-visited, unset-nav-visited, select-nav, unselect-nav, is-nav-visited, lua-mark-ship, lua-mark-wing, ship-create, lua-staged-countdown-start, set-cargo, ship-change-alt-name. 
Convert the second sexp parameter to variable for the following sexps: change-subsystem-name, lua-mark-subsystem. 
Convert the fourth sexp parameter to variable for the following sexp: lua-turrethotkey-add. 
Convert all sexp parameters to variables for the following sexps: set-nav-color, Add-Object-Role. 
All the new variables must be modified at the beginning of the mission in a new event with the modify-variable-xstr sexp. 
/tables: 
credits.tbl and *-crd.tbm files: all lines to be translated must be wrapped into XSTR function. 
cutscenes.tbl and *-csn.tbm files: all '$Name' properties must use XSTR. 
hud_gauges.tbl and *-hdg.tbm files: all 'Text' properties must use XSTR. 
mainhall.tbl and *-hall.tbm files: all '+Door description' properties must use XSTR. 
medals.tbl and *-mdl.tbm files: all '$Alt Name' and '$Name' properties must use XSTR. 
rank.tbl and *-rnk.tbm files: all '$Name' properties must use XSTR. 
ships.tbl and *-shp.tbm files: 
All ships must have an '$Alt Name' property with XSTR. If the ship is present in different files (using +nocreate), you only need one $Alt Name. 
For each '$Subsystem', unless it is 'untargetable' or it's 'afterburner', you'll need to add '$Alt Subsystem Name' (and '$Alt Damage Popup Subsystem Name' only for playable ships) with XSTR. 
'+Tech Description' and '+Length' (only the one before '$thruster') must use XSTR. 
weapons.tbl and *-wep.tbm files: 
All weapons must have '$Alt Name', '+Title' and 'Tech Title' properties with XSTR. If the ship is present in different files (using +nocreate), you only need one $Alt Name. 
'$Turret Name', '+Description' and '+Tech Description' properties must use XSTR. 

In order to automate the process of internationalization across several mods, I developed a tool to do most of the work automatically. You can try it here if you are interested: https://codeberg.org/AchilleParmentier/FreeSpace2TranslationTools/releases.

===Localization (l10n)===
====Setting your language====
The first step is to make your language supported by the game. To do so, create a file with the *-lcl.tbm pattern (e. g. fr-lcl.tbm) with the following content:

<pre>$Language: French
+Extension: fr
+Special Character Index: 164

#End</pre>

$Language property is the name of the section you will have to use in all the strings/tstrings files where you put your translations. This name will also be displayed in the language choice in the in-game settings.
+Extension property is the suffix you will use in all the language-specific files (see the list in the next chapter).

Note that this step is not required if you translate a mod not using SCPUI with the French, German and Polish languages, as they are already supported by the original game.

====In case your language uses special characters not provided by the original fonts====
In such case, you'll need an extra step to use another font. I can't help you to find what font you need to use, but you'll need to use a ttf file. Once you have found your desired font file, put it into /data/fonts.

Then you have to tell the mod to use that font instead of the original file. To do so, find the fonts.tbl (and/or *-fnt.tbm) file in /data/tables, and change the $TrueType property with the name of your new font file for each font you want to change.

Be aware that your new font might have a different size from the original and change how the text is displayed ingame. In that case you can modify the +Size, +Top offset and +Bottom offset properties to try to replicate the original display.

====The files to translate====
From here we consider the mod we want to translate is technically ready, so as a translator I just want to know where to find the texts to translate.

Regarding the tools, all txt/tbl/tbm files are simple text files and can be opened and modified with any text editing software, like notepad++ or VSCode.

You'll find below the list of folders/files which can contain texts to be translated.

=====Fiction=====
The *.txt files here can be translated by creating a copy of the same file with a language suffix (e. g. db_bosch.txt => db_bosch-fr.txt).

Some mods may include briefing files here, and these files cannot be translated this way. You'll have to either overwrite the original file, or modify the custom briefing script to make the content internationalized (check the French translation of Solaris to see an example).

=====Movies=====
Here you can add subtitles to cutscenes by creating a *.srt file with the name of the video with language suffix (e. g. colossus.mp4 => colossus-fr.srt).

Subtitle Edit (https://www.nikse.dk/subtitleedit) is a good user-friendly tool to create your subtitles.

If you want to use a distinct font for movie subtitles, create a new one in fonts.tbl, and in game_settings.tbl or any *-mod.tbm file, add the $Movie Subtitle Font property (in the following example, 'Movie' is the name of the new font):

<pre>#OTHER SETTINGS
$Movie Subtitle Font: Movie

#END</pre>

=====HUD and interface=====
Some mods use custom interfaces, with images containing text. You will need some basic image editing skill to translate them. Beware that these files are not internationalized, so you will have to overwrite the original files!

=====Maps=====
In some mods you can find *.dds files which contain nameplates for terran ships. You will need some basic image editing skill to translate them. Beware that these files are not internationalized, so you will have to overwrite the original files!

=====Tables=====
The following files are the most important, as they contain most of the text displayed in the game:

strings.tbl, and all files with the *-lcl.tbm pattern (these contain all the menu strings)
tstrings.tbl and all files with the *-tlc.tbm pattern (these contain the mod content strings, so all missions, ship and weapon descriptions, credits...)

They can be translated by adding a new section with the name of your language copying inside all the original XSTR entries replaced with your new translation.

Example of an original strings.tbl:

<pre>#Default

0, "Player ship changed to %s"

#End</pre>

Example of a translated strings.tbl:

<pre>#Default

0, "Player ship changed to %s"
;the rest of the strings

#End

#French

0, "Vaisseau du joueur à présent %s"
;the rest of the strings

#End</pre>

The number at the beginning of each row must stay the same, as it is the ID used by the game to look for the matching string.

Note that the new translated section can also be placed in a distinct *-lcl.tbm/*-tlc.tbm file if you are familiar enough with modular tables.

Some variables can be used inside the strings for special uses:
$quote: replaces the " character, as it is already used by the table format to recognize the string
$rank: this will be replaced by the current rank of the player ($Alt Name property in rank.tbl)
$rtitle: similar to $rank, but can be used in case your language uses different names for the same rank depending on the context ($Title property in rank.tbl)

=====Voices=====
Contains all the voice acting files, if you are extremely motivated. Beware that these files are not internationalized, so you will have to overwrite the original files!

====Updating your existing translation====
Let's say you previously translated the v1 of a mod, and now you want to translate v2 but you are not sure what strings changed or were added between both versions.

For this case, I developed a tool you can use: https://codeberg.org/AchilleParmentier/FreeSpace2TranslationTools/releases.
In the second tab 'Update translations' of this tool, you can automatically transfer all unchanged texts from your translated v1 to your new translated v2 file (even if they don't have the same ID anymore). Then you will only have to translate the new and modified strings.

That's all for now, this guide does not cover how to test or publish the translation mod, because there are already other guides covering it.
If you need more detailed information or advice, please don't hesitate to ask; I'll do my best to update this guide accordingly.

===Related Links===
[https://www.hard-light.net/forums/index.php?topic=99978.0 '''Discussion thread | Hard-Light Productions'''] 

[[Category:Tutorials]]

Solaris (TC)

2026-05-08T10:33:40Z

Mobius: Reverted edits by Mobius (talk) to last revision by Darius

{{SolarisTC}}

'''Solaris''' is a total conversion set in an original universe using the FreeSpace Open engine.

==General Information==
Solaris takes combat in the FSO engine to another level. Face down dynamic fighter enemies who weave and dodge incoming fire. Lead assaults against heavily armoured capital ships armed with relentless point defense cannons and powerful anti-ship missiles. Every dogfight is an event, every victory significant.

Use the right tools for the right job. Fighters are the hunters of enemy strike craft, agile and deadly. Interceptors cannot be beaten for raw speed and have the firepower to back up their boast. Strikers are well armoured, armed with heavy cannons for strikes against capital ship subsystems.

You are piloting an agile war machine with the ability to drift and strafe. Use every dimension to your advantage, but beware: your enemies will do the same to you.

==Campaigns==
*[[Solaris (campaign)|Solaris]] (10 missions)
*[[Black Sun]] (12 missions)
*[[Albion]] (6 missions)

[[Solaris Campaigns Walkthrough|Campaigns Walkthrough]]

==Background==
[[Image:SpeciesMIR.png|left|360px]]
The 25th century should have seen the start of a new Golden Age.

Humanity did not launch itself to the stars unified. The web of international rivalries, alliances and intrigues prevalent throughout human history accompanied the first colonisation efforts out of Earth's orbit. To the stars humanity brought art, philosophy, technology, commerce...and war.

The Great War of the 2430's was the climax of Earth's efforts to maintain control of the colonies. The war forged the national identities of fledgling nations while past empires died.

The remnants of the Old World were swept away in nuclear fire and a new international order was born.
==Factions and Organizations==
===Great Powers===
====Atlantean Federation====
[[Image:FederationLogo.png|left|120px]]
[[Image:FedHyperion.png|thumb|right|360px|The archetypical Federation ship: the ''Hyperion''-class fleet carrier.]]

'''''"Populi, a populo, pro populo."'''''

The Atlantean Federation is the largest and most politically dominant of the Terran powers. Founded on liberal democratic values and forged in the aftermath of the Great War, the Federation sees itself as the vanguard of civilization. The executive government functions in concert with a powerful defense establishment and a sprawling legislative assembly.

The Federation operates not only as a military bloc but also as a cultural and economic juggernaut. Member systems enjoy internal autonomy, but defense, foreign affairs, and trade are centralized under a strong federal executive government. Federation citizens are raised in a civic culture that combines frontier optimism with post-industrial privilege. Critics argue this fosters complacency and hubris, while supporters claim it’s the reason for the Federation's ascendancy.

Its foreign policy is one of preemptive engagement and soft power projection. Officially, it promotes stability, free markets, and democratic values. In practice, it often intervenes to secure trade corridors, install "friendly" regimes, or counter threats from autocratic rivals. Peacekeeping deployments and military aid are routine, as are covert operations in systems deemed strategically fragile. Its navy is an enormous, carrier-led force designed for rapid response and long-range power projection.

The Federation defines the galactic order. Whether viewed as a benevolent hegemon or a veiled empire, its influence is everywhere.

====Sinarus Combine====
[[Image:CombineLogo.png|left|120px]]
[[Image:ComBattlecruiser.png|thumb|right|360px|The ''Archon''-class battlecruiser is the product of contemporary Combine Navy battle doctrine.]]
'''''"One people. One future."'''''

The Sinarus Combine is a technocratic autocracy built on the ruins of the old Sol Combine, forged in the fire of collapse and civil war. Where the Federation champions liberty and identity, the Combine champions discipline, sacrifice, and the rule of systems. It presents itself as a society free from the chaos of populism, where the state ensures prosperity through centralized planning, social engineering, and unflinching authority.

The Combine is governed by a collection of Directorates and Ministries under the oversight of the Archon, with all activity aligned toward a central Strategic Doctrine. Citizens are assigned roles based on aptitude metrics and are subject to rigorous social credit systems that measure productivity, loyalty, and "civic resilience". Surveillance is ubiquitous but precise. Rather than brute repression, the Combine relies on predictive analytics and social conditioning to maintain internal cohesion.

Externally, the Combine projects strength through a doctrine of calculated deterrence. Its navy is mobile, hard-hitting, and optimised for pre-emptive strikes, especially in disputed border zones. The Combine seeks to reclaim territories it considers historically or strategically vital, and is unafraid to use economic blackmail or covert destabilization to achieve its aims. Unlike the Federation, it does not dress its actions in moral language. Efficiency is justification enough.

Critics describe the Combine as dystopian. Its citizens, when asked, call it ''safe''. To live in the Combine is to live under scrutiny, but with guarantees of shelter, education and order. The state may be intrusive but it never forgets you exist.

====Alban Commonwealth====
[[Image:CommonwealthLogo.png|left|120px]]
[[Image:CwLion.png|thumb|right|360px|''Lion''-class light cruisers are ubiquitous in trade lanes throughout Terran space.]]

'''''"For Crown and Country."'''''

The Alban Commonwealth is a constitutional monarchy that blends ceremonial tradition with hard-edged strategic clarity. Though smaller in territory and military strength than its rival Great Powers, it plays an outsized role in interstellar politics through cultural prestige, naval quality, and diplomatic finesse. King Edward Wynson rules as part of a dynastic monarchy stretching back generations, a widely respected sovereign believed by many to possess a gift for political foresight.

The Commonwealth’s internal structure is federal but loyal to the Crown. Member worlds are granted local autonomy within a shared legal and military framework, anchored by a deeply ingrained sense of civic honour. The upper echelons of society include hereditary nobles, knighted professionals, and elected representatives, all bound by a shared ethic of service. Titles are earned more by action than birth.

The Alban Crown Navy is renowned for its professionalism, discipline, and operational efficiency. It favours cruiser-led task groups and long-range strike platforms, prioritising quality over volume. Though often outnumbered, Commonwealth fleets routinely outperform expectations, especially in coalition environments. Commonwealth officers are in high demand as trainers, advisers, and diplomats.

On the galactic stage, the Commonwealth is a quiet kingmaker. It builds coalitions, brokers treaties, and offers sanctuary to reformers and dissidents from more extreme regimes. While not as aggressive as the Federation or as controlling as the Combine, it is no less ambitious. Its diplomacy is deliberate, and its restraint a form of power in its own right.

===Middle Powers===

====Republique Jacobine====
[[Image:RepubliqueLogo.png|left|120px]]
[[Image:RepCruiser.png|thumb|right|360px|Republique Navy warships such as the ''Merveilleux''-class light cruiser have advanced engines and weapons systems, but are lightly armoured.]]

'''''“Through Reason, Liberty. Through Sacrifice, Justice.”'''''

The République Jacobine is an authoritarian parliamentary republic forged in revolution and sustained by national myth. To its citizens, it is the truest expression of people’s sovereignty: a nation where liberty is preserved not through compromise, but through vigilant civic engagement, ideological clarity, and unwavering sacrifice. Governed by the General Assembly and led by the Citizen-President, the République practices an assertive, rationalised form of governance where public virtue is enforced, not assumed.

Its institutions operate under the supervision of the Bureau of Virtue, a powerful civic authority responsible for ideological coherence and social conduct. Political parties exist, but only within the framework of the revolutionary consensus. Education, media, and military training are geared toward cultivating the citoyen éclairé: the enlightened citizen. In the République, patriotism is a moral duty, and revolution is a continuous process.

The La Marina is compact, modern, and ideologically hardened. It is not just a fighting force but an instrument of republican idealism, often deployed in support of democratic uprisings and anti-corporate revolts. Jacobine officers are both soldiers and commissars, trained in both naval tactics and revolutionary philosophy.

To foreign observers, the République is paradoxical: a state that preaches liberty while surveilling its citizens, that seeks peace through continual struggle. But to its people, this tension is the Republic’s greatest strength. It is not a utopia, but it is a crucible in which civic virtue is tested and refined.

====Greater Yamatan Union====
[[Image:UnionLogo.png|left|120px]]
[[Image:UnionCarrier.png|thumb|right|360px|Union warship aesthetics tend to match the Yamatan temperament, as seen with this Union battlecruiser (unknown class).]]

'''''"Only in duty do we endure."'''''

The Greater Yamatan Union is a techno-feudal empire, rigidly hierarchical and deeply spiritual, where technology serves not to liberate the individual but to perfect their role in society. Governed by the Shogunate under the rule of the High Kensei, the Union merges ancient Yamatan warrior traditions with advanced neural augmentation and biotechnological modification. Every citizen is born into a caste, every action is ritualised, and every war is sacred.

Citizens are stratified by service and obedience. Higher castes receive elite education and enhancements, while lower castes perform logistical, agricultural, or menial duties. While the system appears oppressive, many citizens embrace it, believing that honour, not freedom, is the highest human value. Education reinforces this through philosophical teachings, martial training, and programmed reverence for the Union’s hierarchy. "Everyone in their place, and a place for everyone."

The Yamatan Navy is compact, elite, and heavily reliant on cybernetic command networks and autonomous squadrons. Each fleet operates as a self-contained shrine of battle. Officers duel over disputed targeting solutions, and victory is not merely measured in territory gained but in ritual fulfilment. While the Union avoids foreign entanglements, it reacts with overwhelming force to threats or slights against its honour.

Externally, the Union is regarded as both enigmatic and formidable. Its refusal to modernise diplomatically frustrates its neighbours, but its cultural resilience and strategic discipline make it a long-term player few dare provoke.

====Rheinische Kaiserreich====
[[Image:KaiserreichLogo.png|left|120px]]
[[Image:ReichCarrier.png|thumb|right|360px|Kaiserreich warships are sturdy and heavily armoured, remaining combat capable after significant damage that would otherwise cripple peer equivalents.]]

'''''"A Reich of Steel and Spirit."'''''

A constitutional empire that shares space borders with both the Commonwealth and Combine spheres of influence, the Rheinische Kaiserreich is a proud and industrious state emerging from decades of postwar retrenchment. Once a formidable military power during the Great War, the Reich was left diminished by peace treaties, domestic fatigue, and the loss of key colonial holdings. Under the current Kaiserin, Marianne Therese von Hohenrath, the Reich has embarked on a carefully managed rearmament and industrial modernization campaign, seeking to reclaim strategic autonomy without provoking its more powerful neighbours.

Geopolitically wedged between two superpowers, the Reich has become adept at balancing diplomacy and deterrence. It shares cultural and political affinities with the Alban Commonwealth and maintains cordial, if cautious, relations with it. At the same time, it exports raw materials and heavy industrial goods to the Sinarus Combine, an arrangement viewed as pragmatic necessity rather than ideological alignment. Though its navy is a fraction of its former size, the Reich’s forces are well-trained and increasingly well-equipped, favoring quality over quantity. The Kaiserin’s government walks a deliberate middle path (neither fully aligned with the Commonwealth nor hostile to the Combine) hoping to preserve stability while rebuilding national strength.

===Non-State Actors===

====Malika People's Militia====
[[Image:MilitiaCutter.png|thumb|right|360px|The majority of Malikan "warships" are armed mining ships utilising whatever the Militia had at hand.]]

'''''"No lords. No chains."'''''

The Malika People’s Militia is a diffuse revolutionary movement composed of miners, defectors, ex-intelligence officers, trade unionists, and disaffected civilians. Originally formed in the wake of a collapsed corporate regime in the Malika Belt, the Militia has since metastasised into dozens of cells scattered across neglected frontier systems. Its structure is loose, its ideology inconsistent, but its message clear: resist the return of oligarchy, seize local autonomy, and dismantle the mechanisms of systemic exploitation.

Militia forces operate out of asteroid colonies, derelict mining platforms, and half-abandoned orbital rigs. While lightly armed and underfunded compared to the navies of major powers, their agility and local support make them a serious threat to colonial garrisons and mercenary fleets. They rely on salvaged equipment, decentralised encryption networks, and sympathetic merchants for supplies. Some factions dabble in piracy; others govern liberated territories with varying degrees of order and legitimacy.

External powers see the Militia as a useful pressure valve, or a dangerous destabiliser. Regardless of how they are categorised, the Militia fights wherever the promise of freedom sounds loudest.

====Children of Renewal====
[[Image:ChildrenCovenant.png|thumb|right|360px|Huge hub vessels like ''Covenant'' are used to spread the word of the Lord. Most Renewal ships are resourced and funded by wealthy investors.]]

'''''“All Stars Lead to the Promised Land.”'''''

The frontiers of Terran Space are a region of intense religious activity. The absence of established institutions and an overwhelmingly practical worldview in a hardscrabble existence divested traditional religious organisations of authority. Ad-hoc spirituality took hold in the region, democratising religion and legitimised individual spiritual expression. Hardship and strong community ties formed the basis of this egalitarian landscape.

The Children of Renewal are a pacifist spiritual movement with roots in frontier Christianity and neo-Mormon theology. Unlike most factions, they possess no standing army. Instead, they operate as a constellation of missionary fleets and humanitarian outposts, bound together by faith in the coming “Promised Land”. All souls, regardless of origin, are equal before the divine.

Renewal vessels travel the edge of settled space, providing medical aid and repairs to stricken ships. They fund their operations through a combination of donations, patronage from wealthy Federation sympathisers, and communal labor. While non-proselytising in tone, they distribute devotional texts and offer spiritual counsel to those who seek it.

Many dismiss the Children as eccentric cultists, and their pacifism as naivety. Yet they are quietly respected across the frontier. In lawless systems, a Renewal mission is often the only source of food or medicine.

==Videos==
Solaris introduction cutscene. 
<videoflash type="youtube">XgVaMGPsrtQ</videoflash> 

Video showcasing Solaris gameplay and visuals 
<videoflash type="youtube">9hz_9lnf4UE</videoflash> 

==Ships and Weapons Databases==
*[[Solaris ship tables]]

==Related Links==
[https://www.hard-light.net/forums/index.php?board=278.0 '''Solaris forum board | Hard-Light Productions'''] 
[https://discord.com/channels/223511295431933953/627182827494178827 '''#solaris subchannel | Discord''']

[[Category:Non-canon]]
[[Category:Solaris (TC)]]

Solaris (TC)

2026-05-08T10:33:31Z

Mobius: Reverted edits by Darius (talk) to last revision by Mobius

{{SolarisTC}}

'''Solaris''' is a total conversion set in an original universe using the FreeSpace Open engine.

==General Information==
Solaris is set in an original universe using the FreeSpace Open engine to create a fast-paced, challenging and engaging space combat game.

This is combat in the FSO engine taken to another level. Face down brutal and dynamic AI enemies who weave and dodge incoming fire and have the same goals as you, the player: Stay alive and bring the other guy down first. Lead assaults against heavily armoured capital ships armed with relentless point defense cannons and powerful anti-ship missiles.

Use the right tools for the right job. Utilise various craft at your disposal - each one specialised for different roles. Fighters are the hunters of enemy strike craft, agile and deadly. Interceptors cannot be beaten for raw speed and have the firepower to back up their boast. Strikers are well armoured, armed with heavy cannons for strikes against capital ship subsystems.

Solaris embraces the concept of player movement equals player power. You are piloting an agile war machine with the ability to drift and strafe around incoming fire and obstacles. Use every dimension to your advantage, but beware: your enemies have just as much mobility as you do.

==Released Campaigns==
Two Solaris campaigns have been released so far:

*[[Solaris (campaign)|Solaris]] (10 missions)
*[[Black Sun]] (12 missions)

[[Solaris Campaigns Walkthrough|Walkthroughs]]

==Background==
[[Image:SpeciesMIR.png|left|360px]]
The 23rd century should have seen the start of a new Golden Age in humanity's history, but instead was witness to a cataclysmic series of events that shook humankind to its core.

Humanity did not launch itself to the stars unified. The web of international rivalries, alliances and intrigues prevalent throughout human history accompanied the first colonisation efforts out of Earth's orbit and took on new context through the Orion Arm. To the stars humanity brought art, technology, commerce...and war.

The Great War of the 2230's was the climax of Earth's last efforts to keep the colonies under its rule, set against increasingly powerful nationalistic independence movements among the colonies. The war forged the national identities of fledgling nations while past empires died. The remnants of the Old World were swept away in nuclear fire.

With the end of the Great War a new international order was born. Humanity had been freed from the fetters of its history, and could finally set its sights out towards the stars.
==Factions and Organizations==
===Great Powers===
The Miranda Accord of 2236 was signed into effect amongst the ashes of the Great War. The war was remarkable in the excesses of the tactics and weapons used, harkening back to the unrestrained industrial warfare of centuries ago. Unrestricted nuclear orbital bombardment had left several planets ecologically devastated, including Earth. By the time of ceasefire, billions of souls had perished. Humanity would not survive another such war.

A conference attended by representatives of every sovereign star nation set into motion a solemn, binding vow - never again will such destruction visit humanity's homes among the stars.

In addition to finalising the terms of armistice, a major tenet of the treaty was drafted to prevent a repeat of this tragedy by restricting the storage and deployment of spaceborne nuclear weapons to capital ships. Further treaty restrictions to nuclear proliferation limited capital ships to the three recognised Great Powers: the Atlantean Federation, Sinarus Combine and Alban Commonwealth. If any nation violated these restrictions, an automatic declaration of war by the three Great Powers would be enacted to enforce the treaty.
====Atlantean Federation====
[[Image:FederationLogo.png|left|80px]]
[[Image:FedHyperion.png|thumb|right|480px|The archetypical Federation ship: the ''Hyperion''-class fleet carrier.]]

'''''"Liberty. Independence. Justice."'''''

The Alantean Federation is the pre-eminent military and economic power in the galaxy. Federation borders make up a vast area of territory in the Orion Arm almost 500 light years across, and encompasses dozens of multi-system subnations under the umbrella of a mutual defense pact. The Federation is by far the most heterogenous of the Terran Great Powers, which it champions as its biggest strength. However, this heterogeneity makes for an administrative nightmare, and the Federation strains under the tension of balancing member systems economic and political autonomy with the need for a centralised government to efficiently manage an increasingly hungry military budget.

The Federation is a federal republic and a representative democracy. Sovereignity is shared between the national and subnational levels of government, with subnational governments representing the various polities that make up the Federation. Military spending and procurement is traditionally under the purview of the National Fleet Department but there have been increasing calls from subnational members for more financial autonomy, including military funding.

Federation naval doctrine begins and ends with working around the difficulties of covering a vast area of space. The Federation Navy is numerous, with a focus on maximising power projection and strategic reach of its task groups. Carrier strike groups are thus highly represented in the Federation Navy, with a fleet doctrine based around utilising numerous strikecraft as the mainstay of power projection. Supporting cruisers and other escorts armed with multiple small-calibre autocannons are effective enough in ship-to-ship combat but these units are not designed to provide the primary offensive punch. As a result, the Federation makes limited use of anti-ship missiles in its direct combat units, opting instead to install them on carriers and heavy bombers.

The Federation Navy is the largest of the Great Powers by numbers and tonnage, and is the primary tool for advancing national interests outside of the Federation's territory. The Navy operates a National Service model with those undertaking compulsory military service primarily assigned to support or logistics duties. Combat elements of the fleet are made up by regular servicemen and volunteers, with occasional representatives from other navies rotating through as part of an exchange program.

====Sinarus Combine====
[[Image:CombineLogo.png|left|80px]]
[[Image:ComBattlecruiser.png|thumb|right|480px|The ''Archon''-class battlecruiser is the product of contemporary Combine Navy battle doctrine.]]
'''''"One people. One future."'''''

The successor state of the Sol Combine is a shadow of its progenitor. Rising from the ashes of Earth's devastation, the leaders of the once-monolithic administrative and political core of Humanity collectively dusted themselves off and set about rebuilding anew. The economic fortunes of the Old World were left in ruins and significant challenges were faced by it's inheritors - densely populated systems previously dependant on Earth's infrastructure needed to be supplied, with resource-rich systems in the periphery ceded to the Federation in the aftermath of the Great War.

What the Combine did have was population - a population made up of skilled, driven workers. The ruling government mobilised entire swatches of this population into rebuilding the industrial infrastructure. Investment from resource-rich nations was encouraged and economic output strengthened in the years to come. Combine leaders had to be ruthlessly efficient and utterly dedicated - there was very little room for error. Political dissent was relentlessly pursued and quashed, and power was concentrated at the upper echelons of the single-party government. Effective propaganda dissemination by the government ensured the nation's citizens knew this was a necessary sacrifice to ensure a future for generations to come.

As the economy recovered, the Sinarus Combine star fleet benefited from an extensive modernisation program. Heavily-armed warships are designed with less specialised roles than Federation equivalents with an emphasis on flexibility of movement and independent operations. The Combine Navy emphasises an "Alpha Strike" battle doctrine, utilising shock jump attacks with large-calibre weapons and heavy missiles. Combine battlecruisers with their balance of mobility and firepower have developed a fearsome reputation in the galaxy after successful demonstrations of these attacks.

The Combine extensively utilises heavy anti-ship missiles in its fleet units as well as batteries of large-calibre mass drivers. Rather than concentrate fighters and other strike craft in large carriers, Combine battle squadrons are often supplemented by numerous small support carriers for defensive purposes. These support carriers are often produced in substantial numbers: the Khopesh aviation frigates are by far most widely produced warship in the galaxy.

====Alban Commonwealth====
[[Image:CommonwealthLogo.png|left|80px]]
[[Image:CwLion.png|thumb|right|480px|''Lion''-class light cruisers are ubiquitous in trade lanes throughout Terran space.]]

'''''"For Crown and Country."'''''

In the political landscape of the 23rd century, a monarch as the head of state of a Great Power seems almost fanciful. Despite this, the Alban Commonwealth has emerged as the standard bearer for tolerance, social justice and non-partisanship in an increasingly hostile galaxy. The Commonwealth is a constitutional monarchy ruled by the youthful Edward Wynson, a perspicacious and well-loved sovereign. Rumours circulate regarding House Wynson's ability to read and influence people, a trait shared by each generation of Wynson monarchs. This ability has taken on an almost mystical status from various embellishments over time, and the origin of King Edward's talent is kept a closely guarded national secret.

Fortune and foresight secured Commonwealth power. The capital system of Alba is the nexus of a densely populated hyperspace network, with extensive trading lanes established rapidly after the system was colonised. The Commonwealth's economy almost exclusively relies on trade, with Alban corporations maintaining some of the largest merchant navies in the galaxy.

During the final stages of the Great War, the Commonwealth took advantage of a unique opportunity to offer its services at mediation. In a diplomatic triumph, the Commonwealth arbitrated terms that satisfied both the Federation's territorial demands and the Combine's need to save face to its citizens. In 2236, the Alban Commonwealth chaired a conference attended by representatives from every independent star nation to draft the Miranda Accord. The prestige secured the recognition of the Commonwealth as a Great Power. Though not the military or industrial equal of the Federation or Combine, the Commonwealth still commands substantial economic and cultural power.

Commonwealth military strengths lie in research and development, personnel training and naval intelligence. His Majesty's Navy is the smallest of the three Great Powers but emphasis on these strengths goes some way to offset the disadvantage in tonnage. Commonwealth military doctrine revolves around numerous cruiser patrols safeguarding the extensive trade lanes - the source of the nation's wealth. With the added clout of being a Great Power came increasing calls for naval funding of capital ship construction and increased power projection. However, financing the significant operating expenses of the new Regent-class dreadnoughts remains a point of contention in the Alban parliament.

===Middle Powers===

The central powers of the Combine and Federation dominate the heavily populated first colonies of humankind. Out in the anti-Spinward peripheries of the Orion arm, however, smaller powers jostle amongst each other for advantage. Middle powers can often approach Great Powers in terms of conventional military. For example, though the rising power of the Alban Commonwealth helps acts as a tempering force for regional tensions, the newly minted Great Power lacks the monolithic influence of the two premier powers in Terran space, and the primacy of its conventional military remains fragile.

====Republique Jacobine====
[[Image:RepubliqueLogo.png|left|80px]]
[[Image:RepCruiser.png|thumb|right|480px|Republique Navy warships such as the ''Merveilleux''-class light cruiser have advanced engines and weapons systems, but are lightly armoured.]]
The Republique Jacobine is a Terran Middle Power born out of the rapid and tumultous colonisation throughout the Cygnus Reaches, with a combination of shrewd economic management and military successes consolidating Jacobine power in the region. The Republique is an ambitious rising power convinced of it's place among the stars, willing to advance Jacobine national interests where possible. Several naval outposts based in neutral or friendly nations form the mainstay of Jacobine power projection.

Though officially a democratic parliamentary government, the Republique government tends to employ authoritarian practices as part of nation building, social engineering and promoting of civic values. Part of this is a self-described necessity against the unstable and hostile environment of the Cygnus Reaches. Other justifications include ensuring the Republique remains a strong and stable nation able to overpower rival nations and competitors. Economically the Jacobines benefit from proximity to the dense trade lanes shared by the Alban Commonwealth, though proximity to these trade lanes formed the basis for tensions and competition with the Commonwealth for decades.

Decades of tensions with the Alban Commonwealth ended with the Pour Toujours Entente, signed in 2236 shortly after the nuclear destruction of Earth. This marked the beginning of forty years of scientific, military and economic cooperation between the two nations. Recent years have seen a concerted effort by the Jacobine and Alban Parliaments to create a bloc separate to the Sinarus and Atlantean behemoths.

The La Marine is one of the most capable spacefaring navies in Terran space, operating a fleet of advanced warships. Recent territorial expansions and establishment of distant naval bases has increased the operational requirements of the Republican Navy, with a concomitant increase in shipbuilding and hull numbers. Republique military doctrine favours employing large numbers of fast, high-endurance warships able to operate far from friendly bases and infrastructure. Regular combined exercises with Commonwealth forces ensure a high degree of interoperability between the two navies. As part of a combined expeditionary force, Jacobine warships are expected to provide the bulk of escort hull numbers for the Commonwealth's dreadnought battle groups. In this role, the Jacobine Navy expects to complement, rather than compete with the Commonwealth Navy.

====Greater Yamatan Union====
[[Image:UnionLogo.png|left|80px]]
[[Image:UnionCarrier.png|thumb|right|480px|Union warship aesthetics tend to match the Yamatan temperament, as seen with this Union battlecruiser (unknown class).]]
The powerful Greater Yamatan Union ranks among the Middle Powers. The vast regions of the Cygnan Wastelands belong to those strong enough to claim them, and strongest among these is the Khan-like Kamaro, overseer and High Dragon of the Union. Militant and isolationist, the Yamatan people have embraced a mechanistic, materialistic worldview, leaving little room for luxury or frivolity.

The Yamatan Union is ruled by the overseer Shin Kamaro, whose iron hand has been credited with forging a powerful nation state in the hostile but resource-rich regions of the Cygnus Wastelands. A sprawling region of space known for intense gravitational anomalies and magnetic storms, astrogation is hazardous, often requiring the use of navigational buoys and waystations to guide spacecraft. Yamatan space lies at the very edge of colonised space in the Orion Arm, and the extent of the Union's territory is unconfirmed. Estimates place the size and extent of the Union's domain as second only to that of the Federation.

A dearth of Earth-like planets has forced swathes of the Yamatan population to adapt to hostile environments, with a substantial proportion of Yamatans living in monolithic megacities or self-sustainable space habitats. The Yamatan Union routinely applies bioprosthetic enhancement technology to its citizens, with labourers and soldiers receiving particularly drastic augmentations. The psychological unease from outsiders regarding the extent of these modifications as well as condemnation over the sometimes brutal regimentation of Yamatan citizens has placed the Union at odds with other Cygnus Region nations. The Yamatan Union is particularly hostile towards the Alban Commonwealth, who it sees as undermining expansion of the Yamatan sphere of influence.

The Greater Yamatan Navy is the primary tool for advancing national interests in a nation with ambitions towards Great Power status with a conventional space military that rivals the Alban Commonwealth. Compulsory military service is enforced for all Yamatan citizens above a certain age, who upon completing their service hold reservist status for life. Union warships are stripped down, heavily armed weapons platforms that seem primitive in comparison to warships of other Middle Powers, but the martial nature of Yamatan society combined with comprehensive military training has given the Union Navy a formidable reputation.

===Non-State Actors===
Though hyperspace lanes provide natural points of interest and roads for expansion, the huge distances involved present challenges for national governments to maintain the infrastructure required for effective and cohesive running of a state.

When weaker nations are unable to provide security or maintain the loyalty of their populations, non-state armed groups such as citizen militias, criminal organisations and warlords develop as alternatives to governance by the state. These groups vary widely in capability and goals, but all contribute to the challenges faced by governing states in the 23rd century.

====Malika People's Militia====
[[Image:MilitiaCutter.png|thumb|right|480px|The majority of Malikan "warships" are armed mining ships utilising whatever the Militia had at hand.]]

The Malika People's Militia is officially classified as a Violent Non-State Actor.

The Fringe is a vast, sparsely populated region of space at the rimward edge of the Orion Arm, notable for an abundance of mineral resources. The Sulsian Hegemony had an iron grip on the major population centres, but corrupt bureaucracy and underdeveloped infrastructure allowed various militia groups in the region to flourish. Chief among these groups was the Malika People's Militia.

The Malika People's Militia is a disparate coalition of paramilitary organisations, warbands and armed worker groups across Fringe space, mustering under the banner of mercenary-turned-corsair Andri Gadaria. The overarching creed of the Militia is the "liberation of all indentured workers from exploitation," and "the right to Self-Determination". In practice, this means utilising violence to disrupt or control Sulsian resource operations, bringing "what is rightfully ours" to the Malikan people. Despite Gadaria's stated aims to found a Malikan nation, the Malikans do not yet have a centralised government, with various groups in the Fringe still maintaining their own localised rule. Alban Naval Intelligence's impressions of Gadaria's activities suggest that he is making preparations to transition these groups to a central planetary government, despite the Malikans not yet having settled a capital world.

The Militia had an unassuming beginning as an armed rebellion on the asteroid mining hub Jotram Station in 2273. Already a precarious situation due to unsafe working conditions with minimal pay, the powder keg exploded when an engineering failure led to a loss of critical supplies and the deaths of several workers. Seeing an opportunity, Andri Gadaria diverted several captured supply ships to Jotram with the intention of winning over the worker population and create a new base of support. Gadaria's charity and charisma combined with an unyielding sense of social justice ensured his message of worker liberation propagated widely across Sulsia, making him a popular figure amongst indentured labourers.

From these humble beginnings, the Militia forces are beginning to organise into a cohesive, coordinated institution. Supplied with powerful modern weapons by a mysterious benefactor, the Militia Navy has been able to challenge the Sulsian Hegemony for control of the resource-rich Fringe. However, the majority of the Malikan navy still consists of converted mining ships and transports - low-performance and low-maintenance hulls that the Militia could find and convert at short notice.

====Children of Renewal====
[[Image:ChildrenCovenant.png|thumb|right|480px|Huge hub vessels like ''Covenant'' are used to spread the word of the Lord. Most Renewal ships are resourced and funded by wealthy investors.]]
The frontiers of Terran Space are a region of intense religious activity. The absence of established institutions and an overwhelmingly practical worldview in a hardscrabble existence divested traditional religious organisations of authority. Ad-hoc spirituality took hold in the region, democratising religion and legitimised individual spiritual expression. Hardship and strong community ties formed the basis of this egalitarian landscape.

In the fertile ground of the Fringe, the Children of Renewal found a people primed to receive their message. The Renewal emphasis on the individual ability of a person to effect his or her own salvation resonated greatly. The message of charity and emphasis on personal development was especially popular with wealthy investors in the Federation, which provided finance for several major projects for expansion in the Fringe. These investors helped fund the construction of the hub vessel ''Covenant'' which serves as the administrative centre of the Children of Renewal, as well as the explorer ship ''Pillar of Fire''.

The Children of Renewal believe in salvation through charity and have several outreach programs throughout the Fringe. Flotillas of repair ships and supply transports crewed by volunteers are deployed to areas of need, all in the name of the Lord. A core belief of the Renewal is that the most important work is the most difficult, which means Renewal ships are often found in disaster zones and contested regions thought too dangerous for other organisations to operate.

The end goal of the Children of Renewal is focused around the discovery of the "Promised Land", a mystical, mythical paradise in the vein of Eden or Elysium where humankind can live free from want or suffering. Though no different to previous renditions of the paradise myth, the Promised Land dream has been sufficiently compelling to garner significant support and resourcing. Investigations are underway as to whether this manifestation is based on a verifiable location in space.

==Videos==
Solaris introduction cutscene. 
<videoflash type="youtube">4MdkiKK4x1Y</videoflash> 

Video showcasing Solaris gameplay and visuals (contains spoilers for Solaris' campaign) 
<videoflash type="youtube">vDfRKJ-fz3k</videoflash> 

==Ships and Weapons Databases==
*[[Solaris ship tables]]

==Related Links==
[https://www.hard-light.net/forums/index.php?board=278.0 '''Solaris forum board | Hard-Light Productions'''] 
[https://discord.com/channels/223511295431933953/627182827494178827 '''#solaris subchannel | Discord''']

[[Category:Non-canon]]
[[Category:Solaris (TC)]]

User talk:Kietotheworld

2026-05-07T09:15:50Z

Mobius: GTVA Colossus

====[[GTVA Colossus]]====
Good job with your edit, I think it makes perfect sense to clarify that the Colossus was not designed as a pure "anti-Lucifer". - [[User:Mobius|Mobius]] ([[User talk:Mobius|talk]]) 09:15, 7 May 2026 (UTC)

Eishtmo's Terran-Vasudan War timeline

2026-05-06T15:59:31Z

Mobius: The events of Jan. 15th-18th are reorganized so that the Vasudan proposal of a cease fire is actually mentioned for the 18th

{{non-canon}}

Shortly after first contact, the '''Terran-Vasudan War''', or the '''14-Year War''', broke out. Heavy and sustained casualties were suffered on both sides, but both species learned valuable lessons in adaptation and the development of new technologies. This timeline will span from the first Vasudan contact to the first contact with the [[Shivans]] in [[Ross 128]].

'''Almost all dates and events below are taken from Eishtmo's FreeSpace fan fiction. This fanfic is being used by the [[Terran-Vasudan War Project]] team, although little of it is grounded in canon.'''

Canon events in silver and non-canon events are in gray. Events with canon dates are in white. Please note that, due to differing sources and interpretations of the war, some information may conflict.

===2320:===

=====March:=====
First official contact with the [[Vasudan Parliamentary Empire]].


=====April:=====
First diplomatic meeting in [[Antares]].

=====July:=====
The [[Pan-Galactic Treaty]] is agreed to by diplomats. Taken to respective governments. GTD ''Gaia'' completed.

=====December:=====
[[Pan-Galactic Treaty]] rejected by legislators on both sides.

===2321:===

=====January:=====
Prince Mihos killed during drug gang battle. Vasudan politicians blame the [[Galactic Terran Alliance]] outright.

=====February:=====
Diplomats Knum and Andrews meet. Meeting ends in bloodshed. War declared by both sides the next day.

=====April:=====
Vasudans launch raid on Sol system. Crushed by GTD ''Gaia'' and 1st Fleet.

=====May:=====
Vasudans begin construction on their own destroyer, the ''Thanatos'' class.

=====September:=====
First Thanatos, PVD ''Thanatos'', completed.


===2322:===

=====November:=====
GTA officials determine the war will not be short. Authorizes the construction of the [[GTC Leviathan|GTC ''Leviathan'']] cruiser.

===2323:===

=====March:=====
First Battle of the [[Vasuda]]-[[Antares]] node. Marks the first time Terran warships enter the [[Vasuda]] system. Terrans only managed to hold the node for a week before being driven back.

===2324:===

=====June:=====
Battle of Vega III. In an attempt to get around the Terran hold on [[Antares]], the PVN launches its first major assault on a Terran system at Vega. The battle was the bloodiest to date, with the loss of nearly 50,000 on both sides. The Terrans managed to drive the Vasudans back to Deneb, but didn't have the strength for a counterattack.

===2326:===

=====August:=====
The first ''Savior''-class destroyer, PVD ''Savior'', come off the lines. Over the next two years, the Vasudans would completely replace their ''Thanatos''-class destroyers with these powerful ships.

=====October:=====
Second Battle of Antares-Vasuda node. To show off the new ship, Vasudan Prince Amon organizes an attack on Antares. The PVD ''Savior'' tears through Terran lines. The Vasudans gain a powerful foothold in Antares.


=====November:=====
[[Battle of Gulnara]]. As the Vasudans poured into the system, the [[Terrans]] launched a massive counterattack. Near the Antares IV moon, Gulnara, the [[Vasudans|Vasudan]] fleet is beaten back to the node. This defeat leads GTA command to believe that victory is on the horizon. Leviathan production is halted, and the GTA initiates a major offensive.

===2327===

=====January:=====
Realizing the end is coming, the Vasudan parliament unofficially moves to [[Alpha Centauri]] where it would stay until after the [[Great War]]. The Third Battle of the Vasuda-Antares node happens days later. Terrans establish a strong foothold in [[Vasuda]].

=====February:=====
The last element of the Vasudan navy is forced out of [[Vasuda]]. The GTA begins building up forces for the invasion of Vasuda Prime.


=====March:=====
Battle of [[Talania]]. 
In an attempt to avenge the invasion of Vasuda, a group of Vasudan admirals, under the leadership of Prince Imhotep, launch an attack on Talania] destroying the Terran 6th Fleet and the supply base there. After the raid, PVN command realized that the attack had crippled GTA supply lines, and orders the group to capitalize on their initial success. By then, the GTA had reinforced Talania, and the fighting was much fiercer.

=====April:=====
With their defenses weakened, the Vasudans launch a renewed attack on the Terrans in Vasuda, finally driving them out by May. The GTA orders Leviathan production resumed with new weapons and technologies.

===2328:===

=====February:=====
First cease-fire established. After regaining lost territory, the Vasudans prepare for an assault on Terran systems when a rare Vasudan holiday comes up. Forced by religious leaders, the Vasudans offer the GTA a short cease-fire. The GTA eagerly accepts, and uses this time to establish new defensive lines. The cease-fire is ended before the treaty is half over with no progress toward a lasting peace.

=====March:=====
Battle of [[Ribos]]. Using information gotten via a spy amongst the Vasudans, the GTA counters an invasion of Ribos by easily destroying the pride of the PVN fleet, the PVD ''Savior''.

===2329:===

=====January:=====
Second cease-fire established. Following a series of crushing defeats, the Vasudan parliament offers the GTA terms for a cease-fire during which a lasting peace treaty would be discussed. Negotiations lasted only an hour before breaking down, but the cease-fire held until the beginning of February, during which the Vasudans strengthen their own lines.

=====August:=====
Battle of [[Deneb]]-[[Sirius]] node. After surprising Vasudan forces in [[Deneb]], the GTA attempts to take the Deneb-Sirius node. The defeat at this battle begins a chain of defeats for Terran forces that would eventually force them into [[Beta Aquilae]].

=====December:=====
Third cease-fire established. In an attempt to stave off certain defeat, the GTA asks for a cease-fire during the holiday season. It is agreed to, and lasts the five days after Christmas. The GTA uses this time to reinforce its lines and prepare a counter attack it launches on New Years' Eve day.

===2330:===

=====June:=====
[[Betelgeuse]] Siege. After a dramatic counter-offensive, the Vasudans had managed to capture and hold [[Antares]] and [[Beta Cygni]]. It is decided by Prince Imhotep to lay siege to Betelgeuse and force the system to surrender. The siege lasts nearly six months, costing the Vasudans dearly. While they busied themselves trying to starve out Betelgeuse, the rest of the GTA attacked multiple supply bases in Antares, crippling PVN supply lines. By December, the [[Vasudans]] are forced to withdraw from Beta Cygni.

===2331:===

=====January:=====
The collapse of the Talania nodes. Though known for their instability, the nodes to the Talania system had been stable enough for the GTA to use the system as a major supply dump. In late December 2330, however, the system was contested when a PVN fleet entered via the [[Vega]] system forcing the GTA to withdraw key equipment and personnel. By January, Vasudan and Terran scientists had independently determined that both nodes into the system were due to collapse to an unusable state within only a few weeks. The commanding officers of both the GTA and PVN fleet called a cease-fire and jointly organized an evacuation of the system. By late February, the nodes were no longer stable for anything to travel through. For years it was hoped that the nodes would restabilize, but hopes would be dashed after the destruction of the [[Sol]]-[[Delta Serpentis]] node and the system was finally removed from maps.

=====March:=====
Fourth cease-fire established. Considered the last serious attempt at peace, Vasudan and Terran officials meet for the bulk of the one-month cease-fire. Serious talks of an end to the war come up, but are dashed when no agreement is made.

=====November:=====
Fifth cease-fire established. By odd coincidence, Terran and Vasudan election dates overlapped during 2331, encouraging the ruling groups to ask each other for a cease-fire so they could remain in power. The cease-fire lasts two days, and the ruling parties were both soundly defeated. There would be no further cease-fires until the arrival of the Shivans.

===2332:===

=====January:=====
After being sworn in, Senator Williams makes a speech proclaiming that the Vasudans should be "bled white" as the only way to win the war. Similar statements by Vasudan legislators trigger a stalemate in the war that lasts for the next three years.

=====March:=====
Designs for the new Vasudan destroyer, the [[PVD Typhon|PVD ''Typhon'']], are approved and construction begins in Altair. Any Saviors currently in production are scrapped and used to build the new warship.

===2333:===

=====March:=====
Nearly one year to the day, the first Typhon, [[PVD Typhon|PVD ''Typhon'']], leaves the [[Altair]] shipyards. Its first assignment is to take [[Vega]].

=====April:=====

Operation Thunderbolt; the GTA succesfully forces the last Vasudan forces out of the Beta Aquilae system, in preparation for an attack upon Antares. ''(Continuity with the defunct 20k campaign)''

 The [[Vega Engagement]]. The GTA's first encounter with the ''Typhon''-class destroyer ends with the destruction of the [[GTD Eisenhower|GTD ''Eisenhower'']] and the [[4th GTA Fleet|4th Fleet]]. The GTA launches a counterattack on Vega, forcing the ''Typhon'' to retreat but taking horrendous losses in the process.

=====June:=====
(12-19th June) Operation Mako; the GTA launches an invasion of the Vasudan-held Antares system from Beta Aquilae, in order to relieve the 5th fleet (trapped in the Ribos system). Despite the destruction of the PVD ''Typhon'' and significant Vasudan losses, the GTA only makes minimal gains at a heavy cost, resulting in stalemate. ''(Continuity with the now-defunct 20k campaign)''

===2334:===

=====June:=====
Battle of Vega-Deneb Node. The last major battle of the 14-Year War sees the Terrans take the Vega side of the node. The first Typhon destroyed in combat occurs during the battle.

=====September:=====
In an attack that surprised both sides, a second Typhon is destroyed in Antares.


===2335:===

=====January 8th:=====
GTA launches Operation Thresher, also known as the Fifth Battle of the Vasuda-Antares Node. Initial losses cause Thresher to be declared a failure only two days after it started. GTA command estimates 504 pilots dead, fourteen missing (and presumed dead).


=====January 15th:=====
The Shivans attack Vasudan and Terran forces near the Antares-Ribos node. The the PVC ''Taurus'' and GTSC ''Plato'' are lost.

=====January 18th:=====
The Vasudans formally propose a cease-fire.

=====January 25th:=====
GTA and PVE sign a cease-fire and non-aggression pact based on the [[Pan-Galactic Treaty]]. The 14-Year War officially comes to an end.

[[Category:History|Terran-Vasudan War]]

SGs Asura

2026-03-19T15:13:22Z

Mobius: Typos

{{User-made Ships|''{{PAGENAME}}''}}
[[Image:Solaris-SGs Asura.jpg|thumb|right|650px|{{PAGENAME}}]]
==Description:==
===Tech Room Description===
little is known of this vessel at this time...

===Credits===
*Model by '''Axem'''
*Textures by '''Nighteyes'''

===Designer's Comments===

==Performance:==
===Statistics===
{{Ship_box
|name = SGs Asura
|yaw_pitch_roll = 20 - 20 - 20
|max_velocity = 15 - 15 - 35 (60)
|rear_velocity = 25
|max_ab_velocity = 65.0
|max_ab_duration = 3.33
|hitpoints = 12000
|shields = 4500
|length = 149.62
|width = 59.93
|height = 43.27
|gun_bank_1 = 3
|gun_bank_2 = 2
|missile_bank_1 = 100
|missile_bank_2 = 100
|missile_bank_3 = 50
|countermeasures = 20
|turrets = 12
}}

===Armaments===
*'''[[Technical_Terms_and_Definitions#Gun Mounts|Gun Mounts]]'''
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=4 style="background:#351515;"| '''Default Statistics'''
|- align="center"
| style="width:40px" |Bank
| style="width:60px" |Guns
| style="width:60px" |Capacity
| style="width:160px" |Standard Loadout
|- align="center"
| 1st
| 3
|
| Shivan Heavy Laser
|- align="center"
| 2nd
| 2
|
| Shivan Mega Laser
|}

*'''[[Technical_Terms_and_Definitions#Missile Banks|Missile Banks]]'''
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=3 style="background:#351515;"| '''Default Statistics'''
|- align="center"
| style="width:40px" |Bank
| style="width:60px" |Capacity
| style="width:160px" |Standard Loadout
|- align="center"
| 1st
| 100
| Unknown Bomb
|- align="center"
| 2nd
| 100
| Unknown Megabomb
|- align="center"
| 3rd
| 50
| Trebuchet
|}

*'''[[Technical_Terms_and_Definitions#Turrets|Turrets]]'''
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=2 style="background:#351515;"| '''Default Statistics'''
|- align="center"
| style="width:120px" |Turret Type
| style="width:60px" |Amount
|- align="center"
| Shivan Turret Laser
| 4
|- align="center"
| Heavy Flak
| 1
|- align="center"
| SAAA
| 2
|- align="center"
| Standard Flak
| 2
|- align="center"
| Shivan Megafunk Turret
| 3
|}

==Modding Resources==
:$POF File: asura shield1.1.pof
:Texture list: Asura;asura-debris

==Gallery==
<gallery></gallery>

===Veteran Comments===
{{comment|The version from FSMods uses bomber flag and has functional primary and secondary firepoints. Also most of its turrets aren't rotated properly and will look bizarre due to lack of UVec and FVec values. A variant using cruiser AI can be found in Blue Planet, that also comes with fixes for all the turrets.
}}

==External links:==
*[http://freespacemods.net/download.php?view.767 Download | FSMods]

GTD Intrepid

2025-05-16T20:48:23Z

Mobius: Rephrasing

{{Gtvaship
| name = GTD ''Intrepid''
| class = [[GTD Orion|GTD ''Orion'']]
| 1stapp = [[Avenging Angels]] (mentioned) [[Silence All Voices]] (conditional)
| inservice = [[Terran-Vasudan War]] [[Great War]]
| faction = [[Galactic Terran Alliance]]
| commander = Admiral Po
| fate = Unknown
}}
The '''GTD ''Intrepid''''' is an ''[[GTD Orion|Orion]]''-class destroyer that served during both the [[Terran-Vasudan War]] and the [[Great War]]. It is known that Lieutenant [[Alexander McCarthy]] was stationed on the ''Intrepid'' before his attempt to [[Heist of the Avenger Prototype|steal the Avenger prototype]]. The player character of ''Silent Threat'' is also said to have transferred to [[Galactic Terran Intelligence]] because of his excellent service record under "Admiral Po of the GTD ''Intrepid''".

The ''Intrepid'' appears in-game only if the player exceeds the time limit in [[Silence All Voices]].

===Early Versions of FS2===

Intrepid was supposed to appear in [[Mystery of the Trinity]] but apparently it was replaced by Aquitaine in late stages of development process. This is evidenced by the names of waypoints and events found in the mission file. It is unknown whether the Intrepid was meant to be the player homeship in the early version of FreeSpace 2's main campaign, or it was just acting as a carrier delivering strikecraft to the new nebula theater.

===Fanmade Campaigns===

* GTD Intrepid appears in [[Between the Ashes]], as player homeship in [[Slaves of Chaos]] and [[Antwerp]] campaigns.

[[Category: GTD Orion-class destroyers|Intrepid, GTD]]

The Sixth Seal

2025-04-06T22:37:08Z

Mobius: Added link to intel entries

[[Image:TheSixthSeal.png|center|650px]]

==General Info==
'''Author:''' Shiv 
'''Missions:''' 16 (part one) 
'''Release:''' March 24th, 2025 
'''Mods included:''' new music tracks 

'''The Sixth Seal,''' also referred to as '''TSS''', is a campaign set in 2334, at the time of the war between [[Terrans]] and [[Vasudans]].

==Development and Credits==
TBFIL.

'''Consulting:''' Nyctaeus, Goober5000, Mobius 
'''Testing:''' Colt, Goober5000, Nyctaeus, Envoybane, ShadowsOfLight, Fusion, Mobius 
'''Weapon effects:''' Inferno, Earth Defense, Blue Planet, Jessnec, with adjustments 
'''Weapon models:''' Inferno, MjnMixael, TheDagger, Earth Defense, FSPort 
'''Exclusive Music:''' ShadowsOfLight 
'''Skyboxes:''' Nyctaeus

==Story==
TBFIL.

==Releases==
===TSS1===
The first TSS campaign was released on March 24th, 2025.

===TSS2===
Part 2 is currently under development.

==Player comments==
TBFIL

==Related Links==
[[The Sixth Seal Intelligence Entries]] 
[https://www.hard-light.net/forums/index.php?topic=99578 '''Release Thread | Hard-Light Productions'''] 
[https://www.moddb.com/mods/the-sixth-seal '''Official Profile | ModDB''']

[[Category: User-made Campaigns]]

The Sixth Seal Intelligence Entries

2025-04-06T22:36:10Z

Mobius: Created page with "{{non-canon}} A list of The Sixth Seal intelligence entries follows. These were not present in the first release of the project, as they were introduced by updates. Thes..."

{{non-canon}}

A list of [[The Sixth Seal]] intelligence entries follows. These were not present in the first release of the project, as they were introduced by updates.

These entries do not feature '''spoilers'''.

==TSS1==
===Terran defections to the PVE===
The following information is classified level Tau.

Years into the open war with the Vasudan Empire, a question has been puzzling tacticians and senior officers: why would, under any circumstance, a Terran defect to the PVE and provide the enemy with crucial data that could be exploited against the human race, possibly leading to the ultimate extinction of Terrans? Defections and surrenders have always been a factor in conflicts, yet the occurrence of these events in an unprecedented circumstance - a space war with another species - invalidates any comparison with past warfare on Earth.

After a detailed evaluation of reports, the tactical branch of the GTN has concluded that defections do not normally occur as a last resort for survival in situations where death would be certain. Instead, they seem to follow a well-defined pattern, with the defectors planning their moves even months prior to the event.

Terran defectors have a multitude of - questionable - reasons. Some see in treason a form of protest against GTA policies and laws affecting their colonies. Others believe that the Terrans are more genocidal in nature than the Vasudans would ever be and are therefore willing to side with the enemy to prevent its annihilation. Many others are apparently affected by a form of 'Exoxenophilia', defined by specialists as a cultural attraction towards the aliens. The betrayal of the human species is not perceived as a crime due to the supposed balance of the conflict, as the GTA and PVE are not deemed capable of destroying each other due to matching technologies and overall military capabilities. Defectors therefore tend to assume that war would culminate in a stalemate at most, with no credible threat to the survival of humanity.

These findings have allowed GTN to optimize the psychological screening of its personnel and ensure that possible defectors would serve reasonably far from the front lines.

===Vasudan defections to the GTA===
The following information is classified level Tau.

The topic of Terran defectors to the PVE has troubled officers for years now, but it comes second to its Vasudan counterpart. The enemy is characterized by a strong sense of duty and an extremely articulated culture, one that would, for all intents and purposes, make the existence of defectors virtually impossible. However, Vasudan defections to the GTA have been a factor in the war ever since 2322, when the entire crew of the PVC Kheti, in a non-critical tactical situation, surrendered to the GTC Archer following a short fire exchange in Antares.

The motives behind Vasudan defectors are far more rooted than those of their Terran counterparts. For instance, defectors are not rooted by the fear of genocidal intention towards the Terrans, as such an intention is formally excluded by leading rules of engagement in the PVN. Although the Vasudans have been under a single political entity far longer than the Terrans, old wounds from regional conflicts preceding the age of space exploration remain latent in the present-day Vasudan Empire and can spark a variety of clashes at any time. An evaluation of defections has demonstrated that they most likely occur in crews with a heritage linked to the central equatorial regions of Vasuda Prime, where the harsh conditions experienced by their ancestors resulted in deep cultural and economic differences with other Vasudans.

It is worth mentioning that a non-negligible number of defections are religious in nature, with minor cults and fanatics within PVN ranks foreseeing catastrophes based on questionable interpretations of millennia-old scrolls and prophecies. The PVE formally rejects these ideals, thus leading multiple defectors to see in Terrans and their supposed lack of strong ideals a potential audience for these messages. To this date, PVE efforts meant to mitigate possible defections are unknown, and some wonder whether they actually exist.

==TSS2==
The campaign i currently under development.

Various Terms

2025-04-04T14:04:37Z

Mobius: Leaving only the key terms in bold

This article lists down the '''various terms, abbreviations, and other jargon''' used by official FreeSpace sources as well as the FreeSpace community.

==Official Terminology==
===General===
* '''[[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.
* '''[[Portal:FreeSpace 2|FS2]]''' - FreeSpace 2. The second game of the series.

===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 Pack files

===In-game 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.
*'''TSM''' - Training Simulator Module

====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_''' - [[Shivans|Shivan]]

====Designation Suffixes====
* '''_A''' - [[Advanced Warning And Control System|AWACS]]
* '''_B''' - Bomber
* '''_C''' - Cruiser
* '''_Cv''' - Corvette
* '''_D''' - [[Destroyer]]
* '''_Dr''' - Drone
* '''_EP''' - Escape Pod
* '''_F''' - Fighter
* '''_Fr''' - Freighter
* '''_G''' - Gas Miner
* '''_I''' - Installation
* '''_J''' - [[Juggernaut]]
* '''_M''' - Medical Ship or Missile
* '''_NB''' - Navigation Buoy
* '''_S''' - Support Ship
* '''_SC''' - Science Cruiser
* '''_SG''' - Sentry Gun
* '''_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 labels are also sometimes used for groups of larger and similar vessels.
*'''Squadron''' - Refers to an organized group of pilots. The [[242nd Suicide Kings]] and [[203rd Scorpions]] are two examples.
*'''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.
* '''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.
* '''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 classes canonically known are the [[GTI Arcadia|Arcadia]] and [[GTI Ganymede|Ganymede]]. 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.

===Other Ship Types===
*'''Transport''' - Primarily used for transporting personnel. Sometimes used to transport marines in boarding a warship, as seen in the capture of a Shivan cruiser. However, it may also be used for repair purposes and evacuation. Transports are designed with minimal defenses and have to be escorted at all times to ensure survival.
*'''Freighter''' - Freighters carry important cargo and usually mount a few anti-fighter turrets. The largest canonical freighter is the [[GTFr Triton]].
*'''Gas miner''' - Used primarily to retrieve and transport nebular gas. Because of their often volatile contents, gas miners have an explosion yield far larger than ships of comparable size. The [[GTG Zephyrus]], [[GVG Anuket]], and [[SSG Rahu]] are the only three examples of gas miners.
*'''AWACS''' - AWACS vessels are primarily used for the expansion of radar detection in systems. Secondary purposes including jamming communications and detecting ships that are invisible to normal sensors. The [[GTA Charybdis]] and [[GVA Setekh]] are the only two examples of this classification.
*'''Escape Pod''' - The [[GTEP Hermes]] and [[GVEP Ra]] carry out this role. Escape pods are primarily for escape purposes, and are deployed from capital ships on the verge of destruction to save its crew and officers.

===Unique Ship Types===
*'''Medical Ship''' - Only the [[GTM Hippocrates]] carries this role. Primarily used to house patients under medical care, it is also used to evacuate refugees.
*'''Science Cruiser''' - Only the [[GTSC Faustus]] carries out this role. The Faustus appears to be tasked as a civilian science research vessel, but is also used by the military in times of war for weapons research. Science cruisers mount very few defenses and are therefore vulnerable to any form of assault.

===Others found in ships.tbl that are not classified as ships===
*'''Cargo Container''' - Carried by freighters. Cargo containers are unarmed and vulnerable to even fighter attack, and can only move via freighters.
*'''Sentry Gun''' - A small, vulnerable structure mounting one or more primary weapons. The largest of these is the [[GTSG Mjolnir]], which mounts a beam cannon. Oddly, Shivan sentry guns are rarely encountered in the FreeSpace 2 campaign.
*'''Knossos''' - The Knossos is an enormous subspace portal which, with its rotating components help stabilize a nearly-collapsed jump node.
*'''Meson Bomb''' - The [[TC-Meson Bomb]] is a remote detonation device which blasts about in a massive shockwave. The only canonical situations wherein these were deployed was in the destruction of the Knossos portal and the sealing off of the Capella jump nodes.
*'''Asteroid''' - Asteroids are of natural phenomenon. They are basically huge rocks in space that are harmful to even large capital ships as demonstrated in [[Rebels and Renegades]]. Asteroids may collide with capital ships and deal a severe amount of damage, but can be neutralized by primary weapons easily.
*'''Unknown Shivan rotating device''' - Known as the [[Shivan Comm Node]] in the editor, there has been no canonical description of the device as information regarding it is classified Level Omega. However, its name implies that it may be a kind of communication device of the Shivans.

===Special objects found in ships.tbl===
*'''SpaceHunk''' - The [[SpaceHunk]] is never used in the main FS2 campaign. It appears to be a large piece of debris from an [[SJ Sathanas]] juggernaut.
*'''SJD Sathanas''' - The [[SJD Sathanas]] is a small, triangular object that is used to represent a distant Sathanas juggernaut in [[Into the Lion's Den]] and all missions from [[Dunkerque]] onwards.
*'''Volition Bravos''' - The [[Volition Bravos]] is an easter egg that can be summoned onto the field using a cheat. It resembles a pirate ship manned by members of the Volition, Inc. staff. Although the Volition Bravos mounts nothing more than a few flak cannons and turret lasers, it is nearly impossible to destroy due to its incredibly high hitpoint count of ten billion.

===Weapons===
*'''Aspect-seeking''' - A type of secondary that must acquire a lock to track the target. See [[GTM Harpoon]].
*'''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.
*'''Turret laser''' - Primary weapons found on capital ships, transports, and freighters. An example would be the [[Terran Turret]]. See also '''blob turret'''.
*'''Anti-fighter beam''' - Small beam weapons on ships at least cruiser-sized. They are used to fire at enemy fighters and bombers, but can also provide fire support against small capital ships.
*'''Anti-capital beam''' - Beam weapons are the main armament of capital ships. They range from small such as the [[SGreen]], to large such as the [[BGreen]] and the juggernaut-scale [[BFGreen]].
*'''Slash beam''' - Beams which are used to sweep ships clean of subsystems. Only Terran and Vasudan warships arm these beam weapons.
*'''Swarm missile''' - Swarm missiles are secondary weapons that are fired in multiple numbers. See [[GTM Hornet]]

==Fan Terminology==
===In-game Terminology===
====Designation Prefixes====
* '''A_''' - [[Ancients|Ancient]]
* '''Ae_''' - [[Aesdherians]]
* '''EA_''' - [[Earth Alliance]]
* '''HL_''' - [[Hammer of Light]]
* '''N_''' - [[Nightmares]]
* '''OR_''' - Outer Rim Syndicate
* '''UE_''' - [[United Earth Federation]]

====Designation Suffixes====
* '''_BS''', '''_Bs''', '''BB''' - Battleship
* '''_Ca''' - Carrier
* '''_Dn''' - Dreadnaught
* '''_Fg''', '''_Ff''' - Frigate
* '''_Gs''' - Gunship
* '''_H''' - Hive
* '''_SD''' - Superdestroyer
* '''_SJ''' - Super Juggernaut
* '''_TB''' - Tactical Bomber

===Ship Types===
* '''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.
* '''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.

===General===
* '''162''' - The Phoenix sub-forum on the Hard Light Productions Forums.
* '''AAA''' - Anti-fighter beam cannon(s)
* '''AB''' - Afterburner(s)
* '''Blob turret''' - A primary weapon-based, warship-mounted turret. The [[Terran Turret]] is an example.
* '''CM''' - Countermeasure
* '''CB''' - Command Briefing
* '''CBAnim''' - Command Briefing animation
* '''Colly''' - The [[GTVA Colossus|GTVA ''Colossus'']]
* '''FA''' - FRED Academy
* '''F2S''' - FreeSpace 2 Sector
* '''[[Portal:FreeSpace 1|FS1]]''' - Descent: FreeSpace—The Great War. Also called Conflict: FreeSpace—The Great War in Europe. The first game of the series.
* '''FS.PL''' - Defunct polish freespace community '''Freespace.pl'''
* '''FS2_Open''' or '''FSO''' - The open source version of FreeSpace 2
* '''FS2NetD''' - FS2 Network Game Monitor; utility used to monitor FS2 network games being operated on the FS2Net servers.
* '''FS3''' - [[FreeSpace 3]], the theoretical sequel to FreeSpace 2
* '''GOG''' or '''GoG''' - Good Old Games. A digital distribution website that sells copies of FreeSpace 2. See [[Getting FreeSpace]].
* '''GW''' - Game-Warden
* '''Hattie''' - The [[GVD Hatshepsut|GVD ''Hatshepsut'']]
* '''HLP''' - Hard Light Productions
* '''HOTU''' - Home of the Underdogs. This website used to host a stripped-down version of FreeSpace 2.
* '''Lucy''' - The [[SD Lucifer|SD ''Lucifer'']]
* '''MediaVP''' or '''MVP''' - VP files with graphical enhancements for FreeSpace Open
* '''Peggy''' - The [[GTF Pegasus|GTF ''Pegasus'']]
* '''Pers''' - The [[GTF Perseus|GTF ''Perseus'']]
* '''Retail''' - The original version of FreeSpace 2, as released by Volition in 1999, plus the official patches. (=not FreeSpace Open). ''Retail'' may also be used to refer to an official campaign, depending on context.
* '''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.
* '''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.
* '''SG''' - Sectorgame. This website hosts the FreeSpace 2 Sector.
* '''ST''' - [[Silent Threat]]
* '''TC''' - Total Conversion. See [[Total conversions]]
* '''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.
* '''VW''' - Volition Watch, developer fansite covering the FreeSpace, Red Faction and Summoner series. Awaiting demolition.
* '''Zod''' - A term used to describe [[Vasudans]]. Derived from Zodiac because their fighter wings were designated based on them in FS1. The term has been coined by Eishtmo.

===Campaign Abbreviations===
:'''''This list is incomplete and not necessarily up-to-date. See also: [[Narwhal's Campaign List]]'''''
* '''158''' - The 158th Banshee Squadron
* '''AA''' - Aeos Affair
* '''AAB''' - Ascension and Beyond
* '''AG''' - [[Alcibiades' Gamble]]
* '''AHTW''' - All Hands to War
* '''AotD''' - Angels of the Damned
* '''[[ASW]]''' - The [[Ancient-Shivan War (campaign)|Ancient-Shivan War]]
* '''BP''' - [[Blue Planet]]
** '''BP:AoA''' or '''AoA''' - [[Blue Planet: Age of Aquarius]]
** '''BP:WiH''' or '''WiH''' - [[Blue Planet: War in Heaven]]
* '''BtA''' - [[Between the Ashes]]
* '''BtRL''' - [[Beyond the Red Line]]
* '''BWO''' - [[Blackwater Operations]]
* '''CoW''' - Casualties of War
* '''CoS''', '''Nukemod-CoS''' or '''Nukemod''' - [[Nukemod|Nukemod - Children of Shiva]]
* '''CtS''' - [[Crossing the Styx]]
* '''DEM''' - [[Deus Ex Machina]]
* '''DoS''' - [[Dawn of Sol]]
* '''DW''' - Dusk Wars
* '''ED''' - Earth Defence
* '''FSPort''' - [[FreeSpace Port]]
** '''ST:R''' - [[Silent Threat: Reborn]]
* '''FS3''' - Freespace 3 the search For bosch
**NOTE: This one also reffers to hypothetical, official sequel
* '''FSU''' - The FreeSpace Upgrade Project
* '''HGI''' - Hellgate: Ikeya
* '''INF''' - [[Inferno]]. This may refer to any Inferno mod.
** '''INFA''' or '''INFA1''' - [[Inferno: Alliance]]
** '''INFA2''' - The sequel to Inferno: Alliance
** '''INFR1''' - [[Inferno Release 1]]
** '''INFASA''' - Inferno: Alliance Standalone
** '''INF SCP''' - Inferno SCP
** '''INFN''', '''INFNostos''' - [[Inferno Nostos]]
* '''ITDoH''' - Into The Depths of Hell
* '''ITHOV''' - Into the Halls of Valhalla
* '''JAD''' - [[Just Another Day]]
** '''JAD2''' - [[Just Another Day 2: Electric Boogaloo]]
** '''JAD3''' - [[Just Another Day 3: Shivans on a Plane]]
* '''JtEP''' - The Journey to Epsilon Pegasi
* '''LM''' - The Lightning Marshal
* '''MT''' - Machina Terra
* '''MG''' - Mind Games
* '''NTV''' - [[Neo-Terra Victorious]]
* '''OCaD''' - Operation: Cloak and Dagger
* '''OTT''' - [[Over the Top]]
* '''PI''' - [[The Procyon Insurgency]]
* '''RR''' - Renegade Resurgence
* '''SA''', '''Scroll''' - The Scroll of Antankharzim
* '''SerRes''' - [[Series Resurrecta]]
* '''SG''' - Shadow Genesis
* '''SGWP2''' - [[The Second Great War Part II]]
* '''SoL''' - [[Shadows of Lylat]]
* '''SotGW''' - [[Shadows of the Great War]]
* '''SR''' - [[Series Resurrecta]]
* '''SS''' - Shattered Stars
* '''SWC''' - Star Wars Conversion
** '''FotG''' - [[Fate of the Galaxy]]
* '''TAP''' - [[The Apocalypse Project]]
* '''TBP''' - [[The Babylon Project]]
** '''TBP:RW''' or '''RW''' - [[Raider Wars]]
** '''TBP:FH''' or '''FH''' - [[Fortune Hunters]]
* '''TI''' - Twisted Infinities
* '''TotT''' or '''ToT''' - Teeth of the Tiger
* '''TS''' - Technological Superiority
* '''TSS''' - [[The Sixth Seal]]
* '''TTP''' - The Titan Project
* '''TVWP''' - [[Terran-Vasudan War Project]]
* '''VD''' - Vassago's Dirge
* '''WCS''' - [[Wing Commander Saga]]
* '''WoD''' - [[Wings of Dawn]]

===Multiplayer===
The following is a list of some terms commonly seen on multiplayer chat screens.
* '''AI''' - Artificial Intelligence. This refers to any computer-controlled ship.
* '''Coop''' - Cooperative game. All players are on the same side and work together to accomplish the mission objectives.
* '''Dogfight''' or '''DF''' - 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''' - Latency. This refers to the "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 mitigated 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.
* '''Lag loading''' or '''Tab loading''' - An exploit that allows a player to load their ship with weapons that it is unable to carry by default, such as the Helios on a Perseus. This is achieved by first selecting the weapon in question with the mouse button, keeping it selected while using the Tab key to switch to the Ship Selection screen, moving the cursor over the bank where the weapon is to be loaded, and finally pressing the Tab key one more time to change back to the Weapons Loadout screen and letting go of the mouse button just as the screen changes. The server will still think that you have your old ship selected, so its weapons permissions will not update in time to prevent you from loading something illegal. This is usually discouraged in multiplayer and considered cheating, but some multiplayer maps were actually made to accommodate this tactic. Lag loading is also possible in single-player. Contrary to popular belief, does not have anything to do with lag, nor is it harder to do in single player.
*'''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''' - Setting "Object Updates" in the Multiplayer tab of FreeSpace 2's options to "Low". This is the preferred setting for MP clients. The "Low" setting limits the connection bit rate between the MP host and the client in order to make the game run smoother for everyone.
* '''Quick jumping''' - A technique that involves all players in the Briefing menu to commit in order for the host to end the mission without needing to host again. It is usually used to give players not yet playing an opportunity to join the game instead of needing to wait for another match.
*'''TvT''' - Team versus Team game. The players are divided into two sides and fight for supremacy.

===Terms related to modelling===
*'''Greeble''' - Small piece of detail which serve no other purpose only to make a ship look better.
*'''[[HTL]]''' - Hardware Transformation & Lighting. This abbreviation has since mutated into shorthand for any user-created high-polygon ship, or generally any retail ship with extra details added by the community.
*'''LOD''' - Level of Detail. The further you get away from a ship, the less detailed it will be rendered.
*'''Multi-part turret''' - A multi-part turret is, in a word, a turret with one, two or three barrels.
*'''Single-part turret''' - A single-part turret, is, in a word, a turret without any barrels.
*'''TrueView''' - A plugin utility for [[trueSpace]]. Ideal for building hierarchy. However, not a must.

===Forum Terms===

*'''OP''' - Original Post / Original Poster: The first post in a thread.

*'''Stickies''' - Threads which remain at the top of the list and are highlighted, as they are always needed and relevant. Sometimes referred to as 'Pinned' threads in other forums.

*'''Splitting a thread''' - Sometimes a thread goes a little off-topic. When this happens it may be split. When a thread is split, the original thread remains, usually with most of its posts, and a new thread is created with the split posts.

[[Category:Lists]]
[[Category:Multiplayer]]

Tenderizer

2025-04-01T19:24:59Z

Mobius: /* Notes */

{|- cellpadding="8" style="background:#000000;" align="center"
| [[Where Eagles Dare|Previous Mission]]
| [[FreeSpace 1 Campaign Walkthrough#Main FreeSpace 1 Campaign|Campaign Walkthrough]]
| [[Shell Game|Next Mission]]
|-
|}

ACT 2 MISSION 5

Fighter squadron: 
Description:

----
==Background==
:''In order to protect Vasuda Prime, the GTD Galatea will be moving from Antares to Beta Aquilae.''
:''Alpha and Beta will provide support.''
:''The sentry guns surrounding the jump node were severely damaged in the recent Hammer of Light attack. Alpha wing will inspect sentry guns to determine if they are salvageable. Beta wing will provide cover.''
:''The Galatea will jump into Antares, reset its coordinates, then jump to Beta Aquilae. Lately, the Hammer of Light has been attacking all ships passing through the jump node. It is your responsibility to destroy all enemy ships that you encounter.''
:''After the Galatea jumps to Beta Aquilae, you will be contacted by the Detiula Installation in the Antares system. There you will receive your briefing and move on to your next mission. Intelligence has specifically requested you and your wing for these missions. Good luck, pilot.''

==Walkthrough==
Fly to the Watchdogs at mission start and open fire as soon as your scan begins, as they'll soon turn hostile. A few warmup wings of HoL redshirts will arrive. Next are a few bomber waves. The bombers are equipped with Stilettos and Synaptics and are trying to disable the ''Galatea'', and therefore aren't much of a threat to her, although there are several [[PVB Amun|Amuns]] thrown in. Their heavy turrets will make short work of your wingmen on higher difficulties, so either don't bother defending the ''Galatea'' (Stiletto hits won't really hurt her) or load your wing with the best-armored ships available (Herc and Medusa in this case).

Next are the kamikazes. The Anubises do 4000 damage and the Seths 6000, so try to go for the latter even if they are slightly more difficult to kill. However, the kamikazes really won't do ''that'' much damage; the only scary thing they send at you is the explosives-packed Aten (PVC ''Mauler'').

On lower difficulties, you can simply kill the cruiser, but a more efficient tactic is to disable it with Stiletto and then rearm as your wingmen finish it off. Remember that this is a red-alert, so try to keep some wingmen alive and watch out for your hull.

==Notes==
This is one of the few missions in the campaign that allows [[cheats|cheating]]. In this context "cheating" does not mean "send your wingmen away so that you will get all kills". It means "cheat code". If you want to use [[Shivan Super Laser]]s in this ''and'' the next mission, go right ahead.

For some, the Watchdogs are actually Cerberus, making them a bit more dangerous, but not by much.

==Notable ships present==
*GTD ''Galatea''
*PVC ''Mauler'' ([[Hammer of Light]])

==Videos==
===Petersaber===
 <videoflash>RzCB3gccEuY</videoflash> 

[[Category:Main FreeSpace 1 Campaign]]

GVF Nhu

2025-03-26T14:54:16Z

Mobius: References to SR

{{User-made Ships}}

[[Image:VF Nhu.jpg|thumb|right|650px|{{PAGENAME}}]]

==Description:==
===Tech Room Description===
Spess fighta.

===Series Resurrecta Description (PVF Nhu)===
A familiar foe to Terran-Vasudan War veterans, the Nhu had been the source of problems for the GTA right in the middle of the conflict. Introduced in early 2324, right before the Battle of Vega III, the Nhu was superior to most Terran counterparts of the time, forcing the rushed development of newer designs among GTA forces. Its main characteristic was the possibility of being easily loaded with explosives, making it ideal for kamikaze assaults. This flexible Vasudan fighter served in virtually every theater of operations since its introduction, but was rendered obsolete by the end of the 2320s with the introduction of its replacement, the smaller PVF Anubis. The Hammer of Light has seized control of many reserve wings of these fighters and retrofitted them with modern engines and weapons. As they can hardly compete with modern designs, the HoL deploy these fighters en masse to capitalize on their numbers.

===Credits List===
*Model by '''Oddgrim'''

==Performance:==
===Statistics===
{{Ship_box
|name = @VF Nhu
|type = Space Superiority
|manufacturer = Sahr Corporation
|yaw_pitch_roll = 3.3 - 3.3 - 3.5
|max_velocity = 60 (78)
|max_ab_velocity = 130.0
|max_ab_duration = 6.6
|hitpoints = 230
|shields = 270
|length = 18.91
|width = 12.37
|height = 5.89
|gun_bank_1 = 2
|gun_bank_2 = 2
|missile_bank_1 = 40
|missile_bank_2 = 25
|countermeasures = 20
}}

===Armaments===
*'''[[Technical_Terms_and_Definitions#Gun Mounts|Gun Mounts]]'''
{|{{Weapon bank box background}}
|-valign="top"
|
{{Pbank_box
|table_style =
|header_style =
|setting =Default
|pbank_1_guns =2
|pbank_1_default =Prometheus R
|pbank_2_guns =2
|pbank_2_default =Mekhu HL-7
|allowed_loadout =Mekhu HL-7, Akheton SDG, Morning Star, Prometheus S, Prometheus R, Circe, Lamprey
}}
|}

*'''[[Technical_Terms_and_Definitions#Missile Banks|Missile Banks]]'''
{|{{Weapon bank box background}}
|-valign="top"
|
{{Sbank_box
|table_style =
|header_style =
|setting =Default
|sbank_1_capacity =40
|sbank_1_default =Harpoon
|sbank_2_capacity =25
|sbank_2_default =Harpoon
|allowed_loadout =Rockeye, Tempest, Harpoon, Hornet, TAG-B, Tornado, Hornet#Weak, EMP Adv.
}}
|}

==Gallery==

<gallery>
Image: |
</gallery>

===Veteran Comments===
{{comment|}}

===Download link:===
*Release Thread:
**[http://www.hard-light.net/forums/index.php?topic=85233.0 Release thread | Hard-light forums]

*Download:
**[http://www.freespacemods.net/download.php?view.906 Download | FSMods.net]
*p3d model preview: [http://p3d.in/mOoRQ]

*[[Series Resurrecta]]:
**[https://fsnebula.org/mod/SeriesResurrecta Series Resurrecta on Knossos | FSNebula]

[[Category: User-made Ships]]
[[Category: Non-canon]]

PVF Seshat

2025-03-26T14:51:43Z

Mobius: /* Download Link */

{{User-made Ships|''PVF '''Seshat'''''}}

{{shipimage|image=[[Image:PVF_Seshat.png|650px]]|caption=PVF Seshat}}

==Description:==

===Twist of Fate Chapter 2 Tech Description===
The Seshat is a new Vasudan space superiority fighter. Weaker than our Eris but faster, the Seshat is the first truly balanced fighter the PVN has ever built. The Seshat carries an average weapon loadout and is compatible with a wide range of Vasudan weapons. Like the Terran Apollo and Eris, the Seshat's main strength is adaptability. It can't intercept as well as a Horus, wade into a thick firefight as well as a Seth, or dogfight with the deadly grace of a Thoth, but it can do those things all at once, unlike other Vasudan fighters.

The Seshat is a class C threat.

===Series Resurrecta Tech Description===
The Seshat is a superb example of a design which can be adequately resurrected and adapted despite its troublesome initial development. The design was supposed to be introduced in late 2334 as a game changer to the Terran-Vasudan War, but faulty power grids and energy management systems caused so many accidents and inconveniences that the PVN had to abandon its plans to deploy it in combat against the GTA. These issues were, in fact, so common that the GTA found out about the existence of this prototype thanks to multiple reports on its accidents. The Shivan Incursion has quickly led the Seshat into oblivion as the Vasudans faced much tougher challenges with the near total destruction of their cities and administrative regions on Vasuda Prime. Mere days before the destruction of the Lucifer, however, tests performed on retrofitted Seshat prototypes have confirmed the possibility of turning the ship into an extremely versatile scout, with interiors adapted to host and support its pilot in missions potentially lasting over one month.

===Credits List===
{{shipimage|image=[[Image:PVFSeshat_Nyx.jpg|650px]]|caption=Alternate PVF Seshat}}
*Model by '''Aldo''', conversion by '''StratComm'''
*Alternate Model and textures by '''Nyctaeus''' and '''FreeSpaceKing'''

==Name Origin==
Seshat is the Egyptian goddess of wisdom and writing.

==Performance:==
===Statistics===
{|
|-
| style="width:200px" | '''[[Technical_Terms_and_Definitions#Type|Type]]'''
| style="width:200px" | Space Superiority
|-
| '''[[Technical_Terms_and_Definitions#Manufacturer|Manufacturer]]'''
| Akheton Corporation
|-
| '''[[Technical_Terms_and_Definitions#Maneuverablity|Maneuverability]]'''
| Good
|-
| '''[[Technical_Terms_and_Definitions#Max Velocity|Max Velocity]]'''
| 75.0 - 90.0 mps
|-
| '''[[Technical_Terms_and_Definitions#Max Afterburner Velocity|Max Afterburner Velocity]]'''
| 150.0 mps
|-
| '''[[Technical_Terms_and_Definitions#Armor|Armor]]'''
| Average
|-
| [[Technical_Terms_and_Definitions#Hitpoints|Hitpoints]]
| 290
|-
| [[Technical_Terms_and_Definitions#Shields|Shields]]
| 370
|-
| '''[[Technical_Terms_and_Definitions#Length|Length]]'''
| 25 m
|}

===Armaments===

*'''[[Technical_Terms_and_Definitions#Gun Mounts|Gun Mounts]]'''
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=3 style="background:#351515;"| '''Default Statistics'''
|- align="center"
| style="width:40px" |Bank
| style="width:60px" |Guns
| style="width:160px" |Standard Loadout
|- align="center"
| 1st
| 2
| Khopesh
|- align="center"
| 2nd
| 2
| [[Mekhu HL-7]]
|- align="center"
| colspan=3| Compatible Primaries
|-
| colspan=3| [[Vasudan Light Laser|VLL-9 Laser]], [[Avenger]], [[Mekhu HL-7]], Khopesh, [[GTW Akheton SDG|Akheton SDG]], Scimitar, [[GTW Flail|Flail]], Adze
|}

*'''[[Technical_Terms_and_Definitions#Missile Banks|Missile Banks]]'''
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=3 style="background:#351515;"| '''Default Statistics'''
|- align="center"
| style="width:40px" |Bank
| style="width:60px" |Capacity
| style="width:160px" |Standard Loadout
|- align="center"
| 1st
| 40
| [[GTM MX-64|Rockeye]]
|- align="center"
| 2nd
| 40
| [[GTM Interceptor|Interceptor]]
|- align="center"
| colspan=3| Compatible Secondaries
|-
| colspan=3| [[GTM MX-50|MX-50]], [[GTM Fury|Fury]], [[GTM MX-64|Rockeye]], [[GTM Hornet|Hornet]], [[GTM Interceptor|Interceptor]], [[GTM Harpoon|Harpoon]], [[GTM Phoenix V|Phoenix V]]
|}

==Gallery==
<gallery>
Image:FrontlinesSS006.jpg | A wing of Seshats as the [[PVF_Nefertum(Frontlines)|PVF Nefertum]], during the T-V War ([[Frontlines]]).
</gallery>

===Veteran Comments===

===Download Link===
*Stratcomm version:
**FreeSpace Mods (As the PVF Nefertum) - http://www.freespacemods.net/download.php?view.722

*Alternate version:
**[http://www.mediafire.com/file/ljkrqp01l0hy7t4/zodshit.7z/file Download | Mediafire]
**[https://drive.google.com/open?id=1N1ZBwNX7zjh2WHNwpGaneyu_XLQWc0xM Mirror | Google Drive]

*[[Series Resurrecta]]:
**[https://fsnebula.org/mod/SeriesResurrecta Series Resurrecta on Knossos | FSNebula]

PVF Ka

2025-03-26T14:51:18Z

Mobius: /* External links: */

{{User-made Ships|''{{PAGENAME}}''}}
[[Image:PVFKa.jpg|thumb|right|650px|{{PAGENAME}}]]
[[Image:PVFKa_HOL.jpg|thumb|right|650px|HoL Variant in Series Resurrecta]]
==Description:==
===Series Resurrecta Description===
Very limited information concerning this fighter is available at this time as most details remain classified. What is obvious, however, is that the Ka is a fighter entirely developed and manufactured by the Hammer of Light, used on rare occasions. Unconfirmed reports state that the most vital HoL strongholds may now be guarded by wings of Ka fighters. Pilots are advised to exercise caution when facing this threat to regional security.

===Credits===
*Original textures by '''Oddgrim'''
*Model / Texture by '''Nyctaeus'''

===Designer's Comments===

==Performance:==
===Statistics===
{{Ship_box
|name = PVF Ka
|yaw_pitch_roll = 4.2 - 4.2 - 4.2
|max_velocity = 60 (72)
|max_ab_velocity = 120.0
|max_ab_duration = 6.8
|hitpoints = 330
|shields = 600
|length = 20.51
|width = 19.49
|height = 4.68
|gun_bank_1 = 4
|gun_bank_2 = 2
|missile_bank_1 = 60
|missile_bank_2 = 80
|countermeasures = 40
}}

===Armaments===
*'''[[Technical_Terms_and_Definitions#Gun Mounts|Gun Mounts]]'''
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=4 style="background:#351515;"| '''Default Statistics'''
|- align="center"
| style="width:40px" |Bank
| style="width:60px" |Guns
| style="width:60px" |Capacity
| style="width:160px" |Standard Loadout
|- align="center"
| 1st
| 4
|
| Avenger
|- align="center"
| 2nd
| 2
|
| Avenger
|- align="center"
| colspan=4| Compatible Primaries
|-
| colspan=4| ML-16 Laser, VLL-9 Laser, Avenger, Flail, Prometheus, Prometheus A, Prometheus R, Banshee, S-Breaker, Leech Cannon
|}

*'''[[Technical_Terms_and_Definitions#Missile Banks|Missile Banks]]'''
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=3 style="background:#351515;"| '''Default Statistics'''
|- align="center"
| style="width:40px" |Bank
| style="width:60px" |Capacity
| style="width:160px" |Standard Loadout
|- align="center"
| 1st
| 60
| Interceptor
|- align="center"
| 2nd
| 80
| Interceptor
|- align="center"
| colspan=3| Compatible Secondaries
|-
| colspan=3| MX-50, Fury, Fang, Interceptor, Interceptor#Weak, Hornet, Hornet#Weak, Phoenix V, Havoc, EM Pulse
|}

==Gallery==
<gallery mode="packed-hover" heights="300px"></gallery>

==Modding Resources==
:$POF File: SerRes_Ka.pof
:Texture list: Glass-trans;KaHOL;TVckpt

===Veteran Comments===
{{comment|}}

==External links:==
*Unborn Legacy's Zod dump:
**[https://www.hard-light.net/forums/index.php?topic=96493.0 Release thread | Hard-light forums]
**[http://www.mediafire.com/file/ljkrqp01l0hy7t4/zodshit.7z/file Download | Mediafire]
**[https://drive.google.com/open?id=1N1ZBwNX7zjh2WHNwpGaneyu_XLQWc0xM Mirror | Google Drive]

*[[Series Resurrecta]]:
**[https://fsnebula.org/mod/SeriesResurrecta Series Resurrecta on Knossos | FSNebula]

PVF Seshat

2025-03-26T14:47:52Z

Mobius: SR's description added

{{User-made Ships|''PVF '''Seshat'''''}}

{{shipimage|image=[[Image:PVF_Seshat.png|650px]]|caption=PVF Seshat}}

==Description:==

===Twist of Fate Chapter 2 Tech Description===
The Seshat is a new Vasudan space superiority fighter. Weaker than our Eris but faster, the Seshat is the first truly balanced fighter the PVN has ever built. The Seshat carries an average weapon loadout and is compatible with a wide range of Vasudan weapons. Like the Terran Apollo and Eris, the Seshat's main strength is adaptability. It can't intercept as well as a Horus, wade into a thick firefight as well as a Seth, or dogfight with the deadly grace of a Thoth, but it can do those things all at once, unlike other Vasudan fighters.

The Seshat is a class C threat.

===Series Resurrecta Tech Description===
The Seshat is a superb example of a design which can be adequately resurrected and adapted despite its troublesome initial development. The design was supposed to be introduced in late 2334 as a game changer to the Terran-Vasudan War, but faulty power grids and energy management systems caused so many accidents and inconveniences that the PVN had to abandon its plans to deploy it in combat against the GTA. These issues were, in fact, so common that the GTA found out about the existence of this prototype thanks to multiple reports on its accidents. The Shivan Incursion has quickly led the Seshat into oblivion as the Vasudans faced much tougher challenges with the near total destruction of their cities and administrative regions on Vasuda Prime. Mere days before the destruction of the Lucifer, however, tests performed on retrofitted Seshat prototypes have confirmed the possibility of turning the ship into an extremely versatile scout, with interiors adapted to host and support its pilot in missions potentially lasting over one month.

===Credits List===
{{shipimage|image=[[Image:PVFSeshat_Nyx.jpg|650px]]|caption=Alternate PVF Seshat}}
*Model by '''Aldo''', conversion by '''StratComm'''
*Alternate Model and textures by '''Nyctaeus''' and '''FreeSpaceKing'''

==Name Origin==
Seshat is the Egyptian goddess of wisdom and writing.

==Performance:==
===Statistics===
{|
|-
| style="width:200px" | '''[[Technical_Terms_and_Definitions#Type|Type]]'''
| style="width:200px" | Space Superiority
|-
| '''[[Technical_Terms_and_Definitions#Manufacturer|Manufacturer]]'''
| Akheton Corporation
|-
| '''[[Technical_Terms_and_Definitions#Maneuverablity|Maneuverability]]'''
| Good
|-
| '''[[Technical_Terms_and_Definitions#Max Velocity|Max Velocity]]'''
| 75.0 - 90.0 mps
|-
| '''[[Technical_Terms_and_Definitions#Max Afterburner Velocity|Max Afterburner Velocity]]'''
| 150.0 mps
|-
| '''[[Technical_Terms_and_Definitions#Armor|Armor]]'''
| Average
|-
| [[Technical_Terms_and_Definitions#Hitpoints|Hitpoints]]
| 290
|-
| [[Technical_Terms_and_Definitions#Shields|Shields]]
| 370
|-
| '''[[Technical_Terms_and_Definitions#Length|Length]]'''
| 25 m
|}

===Armaments===

*'''[[Technical_Terms_and_Definitions#Gun Mounts|Gun Mounts]]'''
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=3 style="background:#351515;"| '''Default Statistics'''
|- align="center"
| style="width:40px" |Bank
| style="width:60px" |Guns
| style="width:160px" |Standard Loadout
|- align="center"
| 1st
| 2
| Khopesh
|- align="center"
| 2nd
| 2
| [[Mekhu HL-7]]
|- align="center"
| colspan=3| Compatible Primaries
|-
| colspan=3| [[Vasudan Light Laser|VLL-9 Laser]], [[Avenger]], [[Mekhu HL-7]], Khopesh, [[GTW Akheton SDG|Akheton SDG]], Scimitar, [[GTW Flail|Flail]], Adze
|}

*'''[[Technical_Terms_and_Definitions#Missile Banks|Missile Banks]]'''
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=3 style="background:#351515;"| '''Default Statistics'''
|- align="center"
| style="width:40px" |Bank
| style="width:60px" |Capacity
| style="width:160px" |Standard Loadout
|- align="center"
| 1st
| 40
| [[GTM MX-64|Rockeye]]
|- align="center"
| 2nd
| 40
| [[GTM Interceptor|Interceptor]]
|- align="center"
| colspan=3| Compatible Secondaries
|-
| colspan=3| [[GTM MX-50|MX-50]], [[GTM Fury|Fury]], [[GTM MX-64|Rockeye]], [[GTM Hornet|Hornet]], [[GTM Interceptor|Interceptor]], [[GTM Harpoon|Harpoon]], [[GTM Phoenix V|Phoenix V]]
|}

==Gallery==
<gallery>
Image:FrontlinesSS006.jpg | A wing of Seshats as the [[PVF_Nefertum(Frontlines)|PVF Nefertum]], during the T-V War ([[Frontlines]]).
</gallery>

===Veteran Comments===

===Download Link===
*Stratcomm version:
**FreeSpace Mods (As the PVF Nefertum) - http://www.freespacemods.net/download.php?view.722

*Alternate version:
**[http://www.mediafire.com/file/ljkrqp01l0hy7t4/zodshit.7z/file Download | Mediafire]
**[https://drive.google.com/open?id=1N1ZBwNX7zjh2WHNwpGaneyu_XLQWc0xM Mirror | Google Drive]

*Series Resurrecta:
**[https://fsnebula.org/mod/SeriesResurrecta Series Resurrecta on Knossos | FSNebula]

The Sixth Seal

2025-03-25T15:58:58Z

Mobius: ModDB link

[[Image:TheSixthSeal.png|center|650px]]

==General Info==
'''Author:''' Shiv 
'''Missions:''' 16 (part one) 
'''Release:''' March 24th, 2025 
'''Mods included:''' new music tracks 

'''The Sixth Seal,''' also referred to as '''TSS''', is a campaign set in 2334, at the time of the war between [[Terrans]] and [[Vasudans]].

==Development and Credits==
TBFIL.

'''Consulting:''' Nyctaeus, Goober5000, Mobius 
'''Testing:''' Colt, Goober5000, Nyctaeus, Envoybane, ShadowsOfLight, Fusion, Mobius 
'''Weapon effects:''' Inferno, Earth Defense, Blue Planet, Jessnec, with adjustments 
'''Weapon models:''' Inferno, MjnMixael, TheDagger, Earth Defense, FSPort 
'''Exclusive Music:''' ShadowsOfLight 
'''Skyboxes:''' Nyctaeus

==Story==
TBFIL.

==Releases==
===TSS1===
The first TSS campaign was released on March 24th, 2025.

===TSS2===
Part 2 is currently under development.

==Player comments==
TBFIL

==Related Links==
[https://www.hard-light.net/forums/index.php?topic=99578 '''Release Thread | Hard-Light Productions'''] 
[https://www.moddb.com/mods/the-sixth-seal '''Official Profile | ModDB''']

[[Category: User-made Campaigns]]

The Sixth Seal

2025-03-24T13:31:24Z

Mobius: /* Development and Credits */

[[Image:TheSixthSeal.png|center|650px]]

==General Info==
'''Author:''' Shiv 
'''Missions:''' 16 (part one) 
'''Release:''' March 24th, 2025 
'''Mods included:''' new music tracks 

'''The Sixth Seal,''' also referred to as '''TSS''', is a campaign set in 2334, at the time of the war between [[Terrans]] and [[Vasudans]].

==Development and Credits==
TBFIL.

'''Consulting:''' Nyctaeus, Goober5000, Mobius 
'''Testing:''' Colt, Goober5000, Nyctaeus, Envoybane, ShadowsOfLight, Fusion, Mobius 
'''Weapon effects:''' Inferno, Earth Defense, Blue Planet, Jessnec, with adjustments 
'''Weapon models:''' Inferno, MjnMixael, TheDagger, Earth Defense, FSPort 
'''Exclusive Music:''' ShadowsOfLight 
'''Skyboxes:''' Nyctaeus

==Story==
TBFIL.

==Releases==
===TSS1===
The first TSS campaign was released on March 24th, 2025.

===TSS2===
Part 2 is currently under development.

==Player comments==
TBFIL

==Related Links==
[https://www.hard-light.net/forums/index.php?topic=99578 '''Release Thread | Hard-Light Productions'''] 
[https://www.hard-light.net/forums/index.php?topic=99578 '''Official SerRes Profile | ModDB'''] (TBFIL)

[[Category: User-made Campaigns]]

The Sixth Seal

2025-03-24T13:28:26Z

Mobius: Created page with "650px ==General Info== '''Author:''' Shiv '''Missions:''' 16 (part one) '''Release:''' March 24th, 2025 '''Mods included:'''..."

[[Image:TheSixthSeal.png|center|650px]]

==General Info==
'''Author:''' Shiv 
'''Missions:''' 16 (part one) 
'''Release:''' March 24th, 2025 
'''Mods included:''' new music tracks 

'''The Sixth Seal,''' also referred to as '''TSS''', is a campaign set in 2334, at the time of the war between [[Terrans]] and [[Vasudans]].

==Development and Credits==
TBFIL.

'''Consulting:''' Nyctaeus, Goober5000, Mobius 
'''Testing:''' Colt, Goober5000, Nyctaeus, Envoybane, ShadowsOfLight, Fusion 
'''Weapon effects:''' Inferno, Earth Defense, Blue Planet, Jessnec, with adjustments 
'''Weapon models:''' Inferno, MjnMixael, TheDagger, Earth Defense, FSPort 
'''Exclusive Music:''' ShadowsOfLight 
'''Skyboxes:''' Nyctaeus

==Story==
TBFIL.

==Releases==
===TSS1===
The first TSS campaign was released on March 24th, 2025.

===TSS2===
Part 2 is currently under development.

==Player comments==
TBFIL

==Related Links==
[https://www.hard-light.net/forums/index.php?topic=99578 '''Release Thread | Hard-Light Productions'''] 
[https://www.hard-light.net/forums/index.php?topic=99578 '''Official SerRes Profile | ModDB'''] (TBFIL)

[[Category: User-made Campaigns]]

File:TheSixthSeal.png

2025-03-24T13:25:54Z

Mobius: The Sixth Seal logo by Nyctaeus.

== Summary ==
The Sixth Seal logo by Nyctaeus.

PVG Oasis

2025-03-24T13:22:16Z

Mobius:

{{User-made Ships|'''PVG''' '''Oasis'''}}

Pre-FS1-era unarmed Vasudan gas miner.

[[Image:PVG Oasis.jpg|thumb|right|650px|PVG Oasis]]
[[Image:HTLOasisWiki.png|thumb|right|650px|HTL Oasis as seen in [[The Sixth Seal]]]]

==Description:==
===Tech Room Description===
The largest unarmed ship in the Vasudan navy, the Oasis-class gas miner probably functions in a similar manner to our Bromios miners, extracting, refining, and storing fuel from gas giants for use in reactors. It is believed to have been designed prior to first contact with Terrans, to travel established and well-policed jump nodes for bulk fuel transport. They are rarely seen in contested systems, leading tacticians to believe the Vasudans refuel in secure locations.

===[[The Sixth Seal]] Tech Room Description===
Challenged by the harsh conditions of their home planet, the Vasudans learned very quickly to venture in the field of space exploration, and did so faster than the Terrans. Designated as a Resource Collector, the Oasis is a large and unarmed Vasudan design that is part of a long lineage of vessels, predating any other space faring vessel in circulation. What is now the Oasis is nothing but a heavily upgraded version of one of the first Vasudan ships ever capable of interplanetary travel and resource exploitation, well before the discovery of subspace drives.

These vessels have efficient, internal modular devices which can be easily adapted to gas or asteroid mining, depending on the environment. The three-stage deck structure of Oasis vessels allows for repeated resource processing and filtering, thus minimizing the loss of potentially valuable minerals or gases, as well as the need for further processing.

Oasis crews are older than average, as they're generally composed by both military and civilian officers nearing retirement and willing to contribute to the Empire with vital resource gathering. These ships have a relevant role in Vasudan culture, with plenty of proverbs, expressions, words and metaphors having their roots on Oasis operations. Generations of Vasudans who ended up serving on these ships and their predecessors have all but consolidated these expressions in culture. In fact, these sayings are present in Vasudan culture at all levels, ranging from colloquialisms to formal terms.

===Credits===
*Model by '''Galemp'''
*HTL by '''Nyctaeus''', based on texture by '''Oddgrim'''. TSS tech description by '''Mobius'''.

===Developer Notes===
Uses recolored HTL [[PVFr Bast|Bast]] texture, so maps of both are interchangeable. Use Texture Replacement in FRED2 to get get different color variants. Gas texture used on the rings is a recolor of Miner02vTile04 used by [[GVG Anuket|Anuket]], so this one can be swapped as well.

==Performance:==
===Statistics===
{{Ship_box
|name = PVG Oasis
|yaw_pitch_roll = 100 - 100 - 80
|max_velocity = 20 (35)
|hitpoints = 4000
|length = 360
|width = 174.41
|height = 175.12
}}

==Gallery==
<gallery mode="packed-hover" heights="300px">
Image:pvgoasis.jpg|PVG Oasis and [[TG Bromios]]
Image:FLOasis.jpg|Unreleased alternate HTL version from [[Frontlines]] by Black Wolf.
</gallery>

==Modding Resources==
:$POF File: oasis.pof
:Texture list: capital03-05;vascarg;miner02vtile04;vascarg2;capital03-02;vaseng3;cruisertile6;capital03-04;damage

===Veteran Comments===
{{comment|
}}

==External links:==
*[https://www.freespacemods.net/download_900.html Download | FSmods]
*[http://www.hard-light.net/forums/index.php?topic=84700.0 Release thread | Hard-light forums]
*HTL - [[The Sixth Seal]]:
**'''[https://www.hard-light.net/forums/index.php?topic=99578.0 Download | Hard-Light Productions]

GTF Antaeus

2025-03-24T13:21:23Z

Mobius:

{{Inferno Ships|''GTF '''Antaeus'''''}}

[[Image:gtfantaeus.jpg|thumb|right|470px| GTF Antaeus as seen in Inferno: Alliance.]]
[[Image:Antek2Wiki.png|thumb|right|470px| GTF Antaeus as seen in [[The Sixth Seal]].]]

==Description:==

===INFA Tech Room Description===
Though the Hercules class fighter was indeed a powerful craft, many pilots complained that it 'handled like a brick.' The Antaeus is an attempt to solve that problem, faster and more maneuverable than the Hercules but sacrifices little in armour and shielding. The only major drawback is the Anteaus has only one secondary bank and so carries far less missiles than the Hercules.

===The Sixth Seal Tech Room Description===
Developed by Han-Roland Corporation, the GTF Antaeus serves as the GTA fleet's standard assault fighter. Built for versatility, the Antaeus boasts a robust power supply capable of mounting heavy primary lasers, giving it a firepower advantage over the GTF Apollo. It also features a larger missile capacity, though the single secondary bank design requires pilots to carefully plan their loadouts to ensure mission effectiveness. The Antaeus is a reliable choice for missions requiring sustained combat capabilities.

===Credits List===
*Model by '''Woomeister'''
*Upgrade by '''Nyctaeus'''

===Name Origin===
Antaeus was a giant defeated by [[GTF Hercules|Hercules]].

==Performance:==
===Statistics===
{|
|-
| style="width:200px" | '''[[Technical_Terms_and_Definitions#Type|Type]]'''
| style="width:200px" | Assault Fighter
|-
| '''[[Technical_Terms_and_Definitions#Manufacturer|Manufacturer]]'''
| Han-Ronald Corp
|-
| '''[[Technical_Terms_and_Definitions#Maneuverablity|Maneuverability]]'''
| Average
|-
| '''[[Technical_Terms_and_Definitions#Max Velocity|Max Velocity]]'''
| 55.0 - 64.0 mps
|-
| '''[[Technical_Terms_and_Definitions#Max Afterburner Velocity|Max Afterburner Velocity]]'''
| 130.0 mps
|-
| '''[[Technical_Terms_and_Definitions#Armor|Armor]]'''
| Medium
|-
| [[Technical_Terms_and_Definitions#Hitpoints|Hitpoints]]
| 200
|-
| [[Technical_Terms_and_Definitions#Shields|Shields]]
| 500
|-
| '''[[Technical_Terms_and_Definitions#Length|Length]]'''
| 18 m
|}

===Armaments===

*'''[[Technical_Terms_and_Definitions#Gun Mounts|Gun Mounts]]'''
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=3 style="background:#351515;"| '''Default Statistics'''
|- align="center"
| style="width:40px" |Bank
| style="width:60px" |Guns
| style="width:160px" |Standard Loadout
|- align="center"
| 1st
| 2
| Shrieker
|- align="center"
| 2nd
| 4
| [[GTW Prometheus|Prometheus]]
|- align="center"
| colspan=3| Compatible Primaries
|-
| colspan=3| [[GTW Avenger|Avenger]], Avenger II, Shrieker, Mace, [[GTW Prometheus|Prometheus]], Banshee-R
|}

*'''[[Technical_Terms_and_Definitions#Missile Banks|Missile Banks]]'''
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=3 style="background:#351515;"| '''Default Statistics'''
|- align="center"
| style="width:40px" |Bank
| style="width:60px" |Capacity
| style="width:160px" |Standard Loadout
|- align="center"
| 1st
| 80
| [[GTM Interceptor|Interceptor]]
|- align="center"
| colspan=3| Compatible Secondaries
|-
| colspan=3| Hunter, [[GTM Fury|Fury]], [[GTM Hornet|Hornet]], [[GTM Interceptor|Interceptor]], [[GTM Phoenix V|Phoenix V]]
|}

===Veteran Comments===
{{comment|The Antaeus is the fighter of choice in Inferno Alliance. It has the six gunpoints of the original [[Hercules]], but only one missile bank. Armed with Prometheus cannons and/or Banshees the Antaeus could really rip apart any fighter in a dogfight, and its low secondary capacity is more than made up for with good enough maneuverability and speed. The Antaeus could be said to be the opposite of the [[GTF Hercules Mark II|Hercules Mark II]] in the way that while the Hercules Mark II focuses on missile capacity, the Antaeus focuses on primary firepower. All in all, however, the Hercules Mark II is probably the better fighter.}}

==Related Links==
*[[Inferno: Alliance]]:
**'''[http://www.freespacemods.net/download.php?view.94 Download | FreeSpaceMods.net]
*[[The Sixth Seal]]:
**'''[https://www.hard-light.net/forums/index.php?topic=99578.0 Download | Hard-Light Productions]

[[Category: User-made Ships]]

Apollo variants

2025-03-23T14:54:54Z

Mobius: Typos corrected

{{User-made Ships|''{{PAGENAME}}''}}
[[Image:Apollo_Bomber.jpg|thumb|right|650px|Bomber variant (AKA [[Famous persons#Lieutenant_Ash|Lt. Ash]]).]]
[[Image:Apollo_Proto.jpg|thumb|right|650px|Prototype variant.]]
[[Image:Apollo_MkII.jpg|thumb|right|650px|Mk II variant.]]

===Tech Room Description===
* Bomber variant
** The Apollo bomber variant has a turret, more primary guns that are powered by a stronger reactor, and can carry heavier secondary arms than its space superiority counterpart, while having similar acceleration and maneuverability. Overall, the GTB Apollo is a very versatile craft and can perform multiple roles, ranging from precision strikes on large capital ships' subsystems to assignments as assault fighter or bomber in attack runs on smaller craft, all the while doing well in Dogfights. Despite this, the higher production cost when compared to the standard issue Apollo, make the bomber variant a much more rare sight in the fleet, with only a few ships issued to specialized squadrons.

* Prototype variant
** The new Apollo fighter prototype is a perfect all-around ship, and a vast improvement over the aging Mustang Alpha in every aspect. It is more agile, has greater secondary loadout, better armour, and is faster. Field tests so far have yielded excellent results, although some pilots report slight instabilities at maximum speed and problems with low energy reserves for primaries in prolonged battles. All problems withstanding this impressive fighter will soon enter mass production, albeit maybe so with slight adjustments in place, to fix the remaining issues.

* MK II variant
** The Apollo Mark II is the attempt bring back old design that had been the backbone of the fleet during the Great War in a modernized form. This is achieved by on one hand combining the strong parts of the Apollo fighter and bomber variants in the old Apollo spaceframe, while adding all the latest tricks in fighter design. The MK II features twice as efficient gun controls as older GTVA ships, and at the same time a much higher secondary payload, than the older Apollo models. The MK II has much improved hull armour and especially shields as well. Chances are, the MK II will be to a new generations of pilots what the MK I had been to pilots for the longest part of the Great War: A versatile ship for every situation.

===Credits===
*'''Fightermedic'''

===Designer's Comments===

==Performance:==
===Statistics===
{{ship_box
|name =GTB Apollo
|type =Fighter-Bomber
|manufacturer =Han-Ronald Corp.
|max_velocity =58 - 85
|max_ab_velocity =140
|hitpoints =250
|shields =350
|length =21.35
|gun_bank_1 =3
|gun_bank_2 =3
|missile_bank_1 =6
|missile_bank_2 =6
|turrets =1
}}

{{ship_box
|name =TF Apollo XX
|type =Space-Superiority
|manufacturer =Han-Ronald Corp.
|max_velocity =70 - 82
|max_ab_velocity =140
|hitpoints =240
|shields =230
|length =21.35
|gun_bank_1 =2
|gun_bank_2 =2
|missile_bank_1 =12
|missile_bank_2 =12
}}

{{ship_box
|name =GTF Apollo Mk II
|type =All purpose
|manufacturer =Han-Ronald Corp.
|max_velocity =72 - 87
|max_ab_velocity =140
|hitpoints =400
|shields =600
|length =21.35
|gun_bank_1 =4
|gun_bank_2 =4
|missile_bank_1 =50
|missile_bank_2 =12
}}

==Gallery==
<gallery></gallery>

===Veteran Comments===
{{comment|
The 3 models only differ in the (modeled) primary and secondary weapon placements (plus second pilot cockpit and nose turret for the bomber) and glowpoint colors. The hull colors are achieved by team color maps and tables, and can therefore easily be altered to the modder's convenience.

The modelled primary and secondary mounts are actually separate subobjects that may be swapped around in PCS2 by an experienced modder to achieve any different configuration.
}}

==External links:==
*Download:
**[https://www.mediafire.com/?vpc2wv48otduf22 Download | Mediafire]
**[https://drive.google.com/open?id=16RCYGyBTmkPJKhVLfjrLIoAvRKp-L00y Mirror | Google Drive]
* Release thread
** [https://www.hard-light.net/forums/index.php?topic=92432.0 Apollo HTL and MK2, Prototype, Bomber variants]

GTB Apollo

2025-03-23T14:52:42Z

Mobius: Redirected page to Apollo variants

#REDIRECT: [[Apollo variants]]

Apollo versions

2025-03-23T14:51:42Z

Mobius: Redirected page to Apollo variants

#REDIRECT: [[Apollo variants]]

Inferno

2024-12-29T09:31:12Z

Mobius: Inferno continuities

Auriga

2024-11-17T15:40:22Z

Mobius:

{{non-canon}}
{{disambiguation}}
*[[MTD Auriga]], a [[GTD Orion|''Orion'']]-class destroyer used by [[Morgan Technologies]] in [[Derelict]]
*[[GTD Auriga]], an Orion-inspired light destroyer by '''Trashman'''
'''In various [[Inferno]] continuities'''
*[[Inferno: Alliance Ship Database#GTD Auriga|GTD ''Auriga'']], or MRD ''Auriga'', was an Orion-class destroyer that served as flagship of the Martian fleet in [[Inferno: Alliance]]
*[[EACa Auriga]], a class of carrier based on the GTD Orion

Lucifer invincibility

2024-09-08T08:05:38Z

Mobius: Redirected page to The Lucifer invincibility misconception

#REDIRECT [[The Lucifer invincibility misconception]]

Lucifer invulnerability

2024-09-08T08:05:12Z

Mobius: Redirected page to The Lucifer invincibility misconception

#REDIRECT [[The Lucifer invincibility misconception]]

Inferno

2024-08-29T11:21:05Z

Mobius: Article overhaul, additional changes required

:''For additional info regarding Inferno builds and their boosted limits, see [[Engine limitations]].''

{| border=0 cellpadding=4 cellspacing=0 style="margin: 0 auto 0 auto; background: #311; border: 2px #811 solid; border-collapse: collapse; font-size: 95%;"
|-
| align="center"| [[Image:INF.png]]
|-
|}

==General Info==
'''Current Team'''
*'''No Tea''' - Project Leader, FREDder, Writer
*'''Rampage''' - 3D Artist, FREDder
*'''Nyctaeus''' - 3D and 2D Artist
*'''Mobius''' - Advisor, FREDder, writer
*'''Colt''' - FREDder
*'''Admiral Nelson''' - FREDder, CBanim Artist
*'''Kitsune''' - FREDder
*'''Fusion''' - Writer, Bugtester

'''Semi-Active Members'''
*'''Rhymes''' - Writer
*'''MesoTroniK''' - Sound Artist
*'''Goober5000''' - SVN Host, Coding, Scripting

'''Legacy Members'''
*Woomeister (former project leader), Droid803, SadisticSid, Shiv, Freespaceking, Trivial Psychic, Jessnec, General Battuta, JSRNerdo, Moonred, TheDagger, BrotherBryon, Macielos4759, Hippo

'''Release dates and missions:''' 

'''INFR1:''' released in 2003, 14 missions 
'''INFA:''' released in 2006, 20 missions 
'''Nostos R1:''' first released in 2018, currently being upgraded with 22 missions (3 are part of a prologue) 
'''Nostos R2:''' release planned for 2024, 12 missions 
'''Nostos R3:''' under development 
'''INFASA/INFAR:''' c.a. 40 missions, now on hold 
'''INFA2:''' undefined 

'''Mods included:''' Complete modpacks 

===Story===
With over two decades of activity, Inferno (INF) is a mod of historical relevance for the FreeSpace community. Over the course of its development, Inferno experienced a total turnover of its team, which also resulted in major changes to the plots and concepts behind this project.

The core plots of Inferno show what happened years after the [[Second Shivan Incursion|Capella incident]] and the consequent [[List of Sol jump node devices|restoration]] of the [[Sol]] jump node in [[Delta Serpentis]]. In circa 2400, the [[GTVA]] finally managed to restore contact with the [[Terran]] home system, only to be faced by the [[Earth Alliance]], the new ruler of Sol which emerged from the fragmented ashes of the [[GTA]]. A war between the GTVA and the EA rages on, with the EA penetrating in GTVA territory. The [[Vasudans]] remain neutral in the conflict, a debated choice which caused relations between the two species in the GTVA to be somehow politically compromised. In such an intricate tactical and political scenario, the [[Shivans]] once again appear to threaten the existence of Terrans and Vasudans alike.

In addition to the main [[Post-Capella]] plot, Inferno covers the events that occurred in Sol following the destruction of the [[SD Lucifer]] in 2335. In these sister campaigns, new conflicts rage on in Sol between the key colonies of Earth, Mars, Jupiter and beyond, eventually culminating with the emergence of the Earth Alliance.

===General notes===
There are two distinct Inferno continuities - the so called '''old continuity,''' and the '''new continuity.''' [[Inferno Nostos]] (Nostos) is the only released campaign from new continuity, while [[Inferno Release 1]] (INFR1) and [[Inferno: Alliance]] (INFA) are the only two released mods of the old continuity. Nostos and INFR1 are set in circa 2400, while INFA is set in circa 2345. New continuity releases are all intended as upgrades of their old counterparts: Nostos is a significant upgrade over INFR1, and is also meant to go beyond the events described in the first mod, completing the main story; [[Inferno: Alliance Standalone]] (INFASA), now renamed as Inferno Alliance Reborn (INFAR), is meant to be a total replacement of the former INFA, focusing entirely on post [[Great War]] Sol. A campaign named [[INFA2]], meant to fill the gap between INFA and the main INF timeline, was also conceptualized but progress on it never actually started.

The growing number of acronyms and campaigns meant to replace their predecessors instead of further developing and completing the story have led to some criticism with respect to this project. In addition to that, the original INFR1 and INFA releases were affected by the presence of large and unused warships, plots generally regarded as poor by community members, and overpowered weapons. These represent the core issues that the new continuity is meant to address and ultimately solve in order to provide a single and consistent story.

It is worth noting that the original INFASA plans involved the release of small, independent minicampaigns meant to make use of the models and armaments not shown in the main INFASA campaign, which was set in Sol. These included Vasudan and Shivan fleets balanced for [[FreeSpace 1]] warfare. Several such minicampaigns were started but remained in hiatus for years; ultimately, they became part of a completely different project under the lead of team member Mobius, named [[Series Resurrecta]] (SR, SerRes). These campaigns retain various references to their INF origin.

The current plans are focused on Nostos, including the release of R2 and R3 which will complete the main Inferno timeline. INFAR is temporarily on hold.

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

Mostly known with the abbreviation INFR1, this is the first release of the Inferno project, dating back to 2003. INFR1 is compatible with FS Open thanks to a patch and additional support. A voice acted version of INFR1 was released on July 16th, 2023 for the 20th Anniversary of the mod.

Nostos has effectively replaced INFR1, which as of today retains mostly a historical value.

[[Inferno R1 Ship Database]]

====[[Inferno: Alliance]]====
'''Also known as: INFA, INF:A, INFA1'''

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. The campaign was focused on the war between Earth and Mars, which would have led later on to the foundation of the Earth Alliance.

INFASA, now INFAR, is meant to be the upgrade of the original INFA, but this project is currently on hold. Some of the satellite INFASA content however has found a new life in [[Series Resurrecta]].

[[Inferno: Alliance 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. The events INFR2 was initially meant to cover will be addressed in Nostos' R2 and R3, which are both nearing completion as of 2024.

===New Continuity===
====[[Inferno Nostos]]====
'''Also known as: INF SCP, INF Nostos'''

Inferno Nostos is a total overhaul of its predecessor (INFR1) and its supposed sequel INFR2. The first release of Nostos was in 2018 and a new version of Nostos R1, as well as the sequels R2 and R3 which will complete the main INF timeline, are both nearing completion as of 2024.

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

INFASA, now INFAR, is to INFA what Nostos is to INFR1: a complete upgrade of its predecessor. The main campaign is currently on hold and progress on it is supposed to resume following the release of Nostos R3. An episodic release of its c.a. 40 missions is considered.

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

The concept of INFA2 is meant to described the events that occurred in Sol between INFA and the main INF timeline. However, this project has never passed the conceptualization phase and a possible release, perhaps in a reduced form, after Nostos R3 is being considered.

==Related Links==
'''Websites'''
*[http://inferno.hard-light.net/ Official Inferno site | Hard-Light Productions.net]
*[http://inferno.hard-light.net/SOL Official Inferno: Alliance site | Hard-Light Productions.net]
*[https://www.moddb.com/games/infscp Inferno: Nostos page | ModDB.com]
*[http://www.moddb.com/games/inferno Inferno: Alliance Reborn page | ModDB.com]

'''Forums/Threads'''
*'''[https://www.hard-light.net/forums/index.php?board=20.0 Main Inferno board | Hard-Light Productions.net]'''
*[https://www.hard-light.net/forums/index.php?topic=94800.0 Inferno Nostos release thread | Hard-Light Productions.net]
*[https://www.hard-light.net/forums/index.php?topic=98869.0 INFR1 20th Anniversary Edition release thread | Hard-Light Productions.net]

'''Downloads'''
*'''[http://www.freespacemods.net/download.php?view.95 Inferno R1 | FreeSpaceMods.net]'''
*'''[http://www.freespacemods.net/download.php?view.353 SCP Patch for Inferno R1 | FreeSpaceMods.net]'''
*[http://www.freespacemods.net/download.php?view.94 Inferno: Alliance | FreeSpaceMods.net]

'''Videos'''
*[http://www.moddb.com/games/inferno/videos Inferno: Alliance Standalone videos | ModDB.com]

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

Amythaon

2024-08-27T11:20:22Z

Mobius: New article, please proofread

{{non-canon}}

===General Information===

*''Appeared in:'' [[Serendipity]] (mentioned)
*''In Mission(s):'' None, Intel entry
*''In System:'' [[Mirfak]]
*''Bitmap(s) used:'' None 

'''Amythaon''' is a planetoid orbiting Mirfak which is not native to the star system, as it was a rogue planet captured by Mirfak's gravity approximately 3 million years prior to the events described in FreeSpace. The planetoid, which has an anomalous orbit due to the gravitational capture, is also much older than the Mirfak star: detailed isotopic analysis has revealed Amythaon to have originated from the same cluster as [[Sol]], making its former parent star a so called stellar sibling of Sol. Amythaon, in addition to this peculiarity, has also revealed the presence of an extremely old leftover of a planetary bombardment. Christened '''Amythaon Planetary Thorn Structure''' (APTS) and dated at 447 million years ago, this is the oldest indirect evidence of advanced life ever found. Data concerning the APTS are subject to [[Coalition Watch]] monitoring and are consequently classified. The structure, now heavily faulted by tectonics and barely recognizable without advanced geophysical equipment, was initially 5 kilometers deep and 400 meters wide. Analyses have totally excluded a possible natural origin of the structure, and models attempting to compare it with [[Lucifer]] bombardments have yielded different results, meaning that the [[Shivans]], or at least the Lucifer, were not responsible for the APTS. No other evidence on Amythaon regarding possible past colonization has been found.

Just like many other celestial bodies in SR, Amythaon has been named after a [https://colonywars.fandom.com/wiki/Eos Colony Wars planet or satellite].

[[Category: Series Resurrecta Stars and Planets]]

Mirfak

2024-08-27T09:13:27Z

Mobius:

===Celestial Information===
*''Name, meaning and Constellation:'' Alpha Persei, Perseus. It comes from the Arabic word for ''Elbow'' from the Arabic Marfiķ al Thurayya,
*''Other name(s) and meaning:'' Mirphak, Marfak, Mirzac (all with the same meaning as Mirfak), Algenib, Algeneb, Elgenab, Gęnib, Chenib or Alchemb (all coming from the Arabic الجنب al-janb, or الجانب al-jānib, meaning ''the flank'' or ''side''), Hinali'i (Hawaiian name).

*''Distance from Sol:'' 600 ly, 184 pc
*''Type of System:'' Singular
*''Color:'' F-Yellow Supergiant
*''Right Ascension:'' 3h 24m 19s
*''Declination:'' +49° 51' 40"

===Important Events===
*To be filled in later.

===Jump Nodes===
*[[Epsilon Pegasi]]
*Unknown System

[[Category:Stars and Planets]]

Mirfak

2024-08-27T09:13:14Z

Mobius:

===Celestial Information===
*''Name, meaning and Constellation:'' Alpha Persei, Perseus. It comes from the Arabic word for ''Elbow'' from the Arabic Marfiķ al Thurayya,
*''Other name(s) and meaning:'' Mirphak, Marfak, Mirzac (all with the same meaning as Mirfak), Algenib, Algeneb, Elgenab, Gęnib, Chenib or Alchemb(all coming from the Arabic الجنب al-janb, or الجانب al-jānib, meaning ''the flank'' or ''side''), Hinali'i(Hawaiian name).

*''Distance from Sol:'' 600 ly, 184 pc
*''Type of System:'' Singular
*''Color:'' F-Yellow Supergiant
*''Right Ascension:'' 3h 24m 19s
*''Declination:'' +49° 51' 40"

===Important Events===
*To be filled in later.

===Jump Nodes===
*[[Epsilon Pegasi]]
*Unknown System

[[Category:Stars and Planets]]

Baldr

2024-08-14T08:11:40Z

Mobius: Created page with "{{non-canon}} ===General Information=== *''Appeared in:'' The Spirit of Ptah (mentioned) *''In Mission(s):'' None, Intel entry (Entanglement Edition only) *''In Sys..."

{{non-canon}}

===General Information===

*''Appeared in:'' [[The Spirit of Ptah]] (mentioned)
*''In Mission(s):'' None, Intel entry ([[Entanglement]] Edition only)
*''In System:'' [[Dubhe]]
*''Bitmap(s) used:'' None 

'''Baldr''' is a planetoid orbiting Dubhe, subject to research and exploitation after the [[Great War]]. Though little information is known about this planetoid as well as a similar celestial body in the same system, [[Hodr]], both of them provided evidence of an old civilization dating back to 35 million years prior to the events described in FreeSpace. Cross analysis of these findings, attributable to the secret project 9CT, and a general assessment on the evolution of the Dubhe star system, both provided evidence that these planetoids have been colonized by an interstellar species whose characteristics, motives and goals remain totally unknown. Dubhe's red giant phase, combined with active tectonics on both planetoids, have cancelled any tangible proof of this civilization from the surface, whose presence in the geologic record has so far been suspected only via isotopic excursions and other perturbations of the atmosphere compatible with industrial activities.

[https://en.wikipedia.org/wiki/Baldr Baldr] and his brother Hodr are characters from Germanic and Norse mythology.

[[Category: Series Resurrecta Stars and Planets]]

Hodr

2024-08-14T08:10:13Z

Mobius: Created page with "{{non-canon}} ===General Information=== *''Appeared in:'' The Spirit of Ptah (mentioned) *''In Mission(s):'' None, Intel entry (Entanglement Edition only) *''In Sys..."

{{non-canon}}

===General Information===

*''Appeared in:'' [[The Spirit of Ptah]] (mentioned)
*''In Mission(s):'' None, Intel entry ([[Entanglement]] Edition only)
*''In System:'' [[Dubhe]]
*''Bitmap(s) used:'' None 

'''Hodr''' is a planetoid orbiting Dubhe, subject to research and exploitation after the [[Great War]]. Though little information is known about this planetoid as well as a similar celestial body in the same system, [[Baldr]], both of them provided evidence of an old civilization dating back to 35 million years prior to the events described in FreeSpace. Cross analysis of these findings, attributable to the secret project 9CT, and a general assessment on the evolution of the Dubhe star system, both provided evidence that these planetoids have been colonized by an interstellar species whose characteristics, motives and goals remain totally unknown. Dubhe's red giant phase, combined with active tectonics on both planetoids, have cancelled any tangible proof of this civilization from the surface, whose presence in the geologic record has so far been suspected only via isotopic excursions and other perturbations of the atmosphere compatible with industrial activities.

[https://en.wikipedia.org/wiki/H%C3%B6%C3%B0r Hodr] and his brother Baldr are characters from Germanic and Norse mythology.

[[Category: Series Resurrecta Stars and Planets]]

Loacoon

2024-08-11T08:45:19Z

Mobius: Minor note on CW misspelling

{{non-canon}}

===General Information===

*''Appeared in:'' [[Serendipity]]
*''In Mission(s):'' TBFIL
*''In System:'' [[Epsilon Pegasi]]
*''Bitmap(s) used:'' TBFIL 

'''Loacoon''' is a [[Regulus Syndicate]] protectorate in the Epsilon Pegasi system, just like [[Erato]].

As most planets and planetoids in the Serendipity campaign, Loacoon is named after a planet featured in the [https://colonywars.fandom.com/wiki/Loacoon Colony Wars] series, which in turn was named after the mythological Trojan priest '''Laocoon''' who tried to warn his fellow citizens about the threat of the Trojan Horse. Please note that CW developers did not spell the name correctly, and this error was intentionally retained in [[SR]].

===Characteristics===
TBFIL

===Events===
TBFIL

[[Category: Series Resurrecta Stars and Planets]]

Blue Planet

2024-08-05T14:12:08Z

Mobius: Adding BP3 concept disclosed by The E. Its implementation here is merely temporary - it could be an article on its own.

[[File:BP-Banner.png|center|From our odyssey into Hell, we return with a gift...]]
'''Blue Planet''' is a series of campaigns set 18 years after the events of FreeSpace 2. With the Alliance in economic turmoil, Terran-Vasudan relations decaying, and the Security Council grappling with the ominous Contingency Morpheus, the GTVA's elite 14th Battlegroup spearheads the effort to re-establish contact with [[Earth]].

Blue Planet is very widely known throughout the Hard Light Productions (HLP) community as being one of the best user-made campaign projects of all-time, excelling in story concept, mission design, cutscene use and music selection.

==Story==
It is 2385, fifty years after the appearance of the [[Shivans]] at [[Ross 128]] and the beginning of the [[Great War]] and eighteen years following the [[Capella]] supernova and conclusion of the [[Second Shivan Incursion]]. Using [[Knossos]]-derived technology, the [[GTVA]] have finally completed the construction of a subspace portal, stabilising the subspace corridor linking [[Delta Serpentis]] to [[Sol]], the birthplace of the Terrans. After sending numerous probes through the portal, the GTVA decides that the node had indeed stabilised, and proceeds to send in the real ambassadors.

[[Blue Planet: Age of Aquarius]] (AoA), released in 2007, introduces the universe, and describes the struggles and adventures of the GTVA's 14th Battlegroup, an elite force of ships sent on a mission to re-establish contact with Earth. As they take a detour through a parallel reality where the Lucifer succeeded in wiping out Earth during the events of the original FreeSpace, one officer gains insight into the greater forces at work in the fabric of the multiverse.

The first part of [[Blue Planet: War in Heaven]] (WiH), released in August 2010, details the final weeks of a civil war between the government of Earth and the GTVA after contact was re-established. It focuses on the journey of a young woman torn between the ideals of her upbringing and the necessities of war. The GTVA, the UEF, and the other factions of the war struggle to shape the future of humanity and the Vasudan race as apocalypse looms.

[[Blue Planet: Chanticleer]], a spin-off campaign released in 2023, completes the arc of the GTVA-UEF civil war, as seen from the GTVA side. The story picks up where War in Heaven left off and is told from the perspective of a veteran GTVA pilot, following a single squadron through the end of the war.

==Missions==
===Age of Aquarius===
* 22-mission campaign

===War in Heaven===
* 23-mission campaign (released)
* Three single missions

===Chanticleer===
* 13-mission campaign

===Battle of Neptune===
* Two single missions

===Battle Captains===
* Two single missions

==Factions==

===Galactic Terran-Vasudan Alliance===
[[Image:GTD_Erebus.jpg|thumb|right|480px|The GTVA's most powerful vessel since the [[GTVA Colossus|''Colossus'']]—the GTD ''Erebus''.]]
[[Image:Gtfatalanta.jpg|thumb|right|480px|The Alliance's next-generation space superiority fighter—the GTF ''Atalanta''.]]
====Summary====
The Blue Planet continuity begins in 2385, only 18 years after the [[NTF Rebellion]] and [[Second Shivan Incursion]]. Following the GTVA's production doctrine employed between the Great War of 2335 and the NTF Rebellion of 2367, a number of FS2-era ships are still used, although most FS1-era ships, by contrast, have been phased out. Ships in active production are determined by their age, popularity among pilots, practicality and irreplaceableness. At the same time, in response to the massive losses sustained as a result of the [[Second Shivan Incursion]], the Alliance pushed forward the Threat Exigency Initiative, an extensive upgrading and redeployment project that spans the Terran arm of the GTVA. Lessons learned from the lack of proper logistical support in remote locations also prompted the introduction of a new "Logistics" class, non-combatant ships designed to serve as mobile installations.

The Threat Exigency Initiative, conceived as a more proper deterrent to the threat of future invasions, ushered in an age of new warships and battle doctrines inspired, ironically, by the [[Shivans]], fighters that can operate more independently, and weapons designed to be as versatile as possible. Products of the Threat Exigency Initiative include the [[GTD Erebus|GTD ''Erebus'']], a three-kilometre destroyer mounting [[HBlue|a powerful forward beam cannon]], warship-mounted heavy torpedo launchers, fast-firing pulse weapons that serve as secondary and tertiary warship armaments, the [[GTF Aurora|''Aurora'' heavy reconnaissance fighter]], and the [[Balor]], a rapid-firing, energy-efficient fighter-mounted particle blaster.

====Warships====
While many Capella-era warships remain in active production, most of the Great War-era warships have been phased out. The only remaining class of warship from the Great War that is still servicing the front lines is the [[GTD Orion|GTD ''Orion'']]. With the addition of the GTD ''Erebus'' into the ranks of the Terran fleet, the ''Orion'''s lengthy service to the Alliance has at last reached its final stages. Only a few ''Orion''-class destroyers remain in active service. The Capella-era warships are supplemented by warships designed and pushed into production as a result of the post-Capella Threat Exigency Initiative.

Virtually all Capella-era warships remain in active service, although some warship classes have been sorted into different sub-classes. For instance, the [[GTD Hecate|''Hecate''-class]], first commissioned as a destroyer during the [[NTF Rebellion]], has since been sub-classified as a carrier following a mediocre performance in the anti-warship field during the [[Second Shivan Incursion]]. The effectiveness of the [[GTC Aeolus|''Aeolus'' cruiser]] during the Second Shivan Incursion, combined with cheaper manufacturing techniques, meant that the Alliance resumed production for a cruiser class that originally had production lines cut after only twenty-four vessels were commissioned. Although still officially classified as a cruiser, the deployment of the ''Aeolus'' in the modern era is much closer to a tactical gunboat and warship escort. The [[GTCv Deimos|''Deimos''-class corvette]] now forms the core of Alliance corvette battlegroups, serving as an all-round warship.

The Threat Exigency Initiative introduced a new generation of warships that are generally faster and more agile than their Capella-era counterparts and are equipped with better-placed anti-fighter defenses, as well as secondary and tertiary anti-warship armaments such as anti-warship torpedoes and pulse cannons. The most powerful warship brought into service as a result of this project is the [[GTD Erebus|GTD ''Erebus'']], a three-kilometre destroyer fitted with the most advanced Alliance weapons and systems to effectively neutralise any threat. Other warships pushed into production include the [[GTD Titan|GTD ''Titan'']], a destroyer sporting a devastating frontal array of three [[BBlue|''Ice Queen'' heavy beam cannons]] and cavernous hangar, the [[GTCv Diomedes|GTCv ''Diomedes'']], a strike corvette mounting several [[TerSlashBlue|''Bull Frost'' tactical slashing beams]], and the [[GTL Anemoi|GTL ''Anemoi'']], a massive logistics vessel that can resupply and repair any ship ranging from fighter to destroyer and carry enough supplies and equipment to sustain a small fleet for months.

====Spacecraft====
Nearly all Great War-era spacecraft have been pulled from active service and sold off to third parties or used as training targets. The only two exceptions to this fate are the [[GTF Ulysses|''Ulysses'' fighter]] and [[GTB Ursa|''Ursa'' assault bomber]]. Of these two, the ''Ulysses'' remains in limited production and is no longer used in front-line operations, while the ''Ursa'', despite its incredibly lethargic speed and sluggish manoeuvrability, still retains its original role in the Alliance fleet, although no plans have been drawn up to create a new class of bombers taking after the design philosophies of the ''Ursa''.

By sharp contrast to the current deployment of all Capella-era warships, a number of Capella-era spacecraft have been slated to be pulled from active service. The two most prominent ship classes befalling this fate are the [[GTF Myrmidon|GTF ''Myrmidon'']], cited as being a powerful but excessively large fighter by many former Rebel pilots who have flown it, as well as the [[GTF Erinyes|GTF ''Erinyes'']], deemed to be too complicated to improve upon. At the opposite end of the spectrum are ship classes such as the [[GTB Artemis|GTB ''Artemis'']] and [[GTF Perseus|GTF ''Perseus'']], the former now mass-produced as the Alliance's main strike bomber, and the latter now reclassified and deployed as the Alliance's main space superiority fighter.

Four fighter classes and one bomber class have been brought into service as a result of the Threat Exigency Initiative: the [[GTF Aurora|''Aurora'' heavy reconnaissance fighter]], sporting enhanced sensors that can navigate the thickest nebula and detect stealth ships, all packaged in a decently armoured spaceframe; the [[GTF Draco|''Draco'' interceptor]], with an insanely high velocity rating allowing it to escort several warships at once; the [[GTF Atalanta|''Atalanta'' advanced space superiority fighter]], with its high speed and agility as well as excellent weapons compatibility; the [[GTF Nyx|GTF ''Nyx'']], a heavy fighter that blends the firepower of eight gun banks with a level of agility comparable to the ''Perseus''; and the [[GTB Rhea|GTB ''Rhea'']], a strike bomber with an asymmetrical weapons configuration that has been regarded as a statistical success among bomber squadrons.

====Weaponry====
Lessons learned during the [[Second Shivan Incursion]], at the cost of thousands of lives, prompted the GTVA to begin upgrading several warships in service after the Capella supernova, as well as to phase out older weapons that have been used for the past five decades and replace them with more modern weaponry. One of the Threat Exigency Initiative's primary goals is to produce better warship armaments and it has, to date, produced three different types of anti-warship weaponry. At the forefront of this are the range of new beam cannons installed on the GTVA's newest line of warships, such as the [[HBlue|''Winter King'' heavy beam]] mounted at the bow of the ''Erebus'' destroyer, and the [[TerSlashBlue|''Bull Frost'' tactical slashing beam]] mounted on the ''Diomedes'' corvette. The second type of anti-warship weapons developed are anti-warship torpedoes, serving as secondary weapons on the ''Erebus'' and ''Titan'' destroyers as well as friendly artillery. The third and final type of anti-warship weapons are pulse cannons, serving as battery weapons on heavier ships. Both the [[TerPulse|''Hellstar'']] and [[STerPulse|''Riptide'']] pulse cannons are recent developments of [[Morgan Technologies]], and have yet to be fully integrated into GTVA battle doctrine.

Much of the GTVA's fighter-mounted weaponry remains the same, although the [[Balor|Balor rapid-fire particle blaster]], so far the only fighter-mounted primary cannon developed by the Threat Exigency Initiative, adds a much-needed and fearsome complement to the standard-issue [[GTW Subach HL-7]]. The Balor was designed to serve and destroy everything short of a light cruiser, and it was designed to be far more versatile than nearly every other fighter-compatible primary gun in the GTVA arsenal. At the time of the Sol Gate's completion, the Balor was brand-new, and GTVA battle doctrine did not fully integrate it. By the time of the UEF-GTVA war, however, the Balor has seen widespread use in nearly every stage of the conflict.

While the [[GTM Trebuchet]] is now commonly used as a long-range heavy missile for destroying slower, heavier ships, the Alliance have also pushed a new missile into production lines—the [[GTM TAG-C]]. This, the third and final iteration of the Target Acquisition and Guidance line of missiles, not only retains the painting beacon of the [[GTM TAG-A]] and aspect-seeking technology of the [[GTM TAG-B]], but combines both with a highly sophisticated targeting beacon that will, on impact, transmit authorisation codes to a local friendly warship. Any large vessel unlucky enough to be hit by a TAG-C will have to deal with the barrage of anti-warship torpedoes that emerge from subspace. The TAG-C enables even fighters to deliver the same warship-shattering punch as an assault bomber.

===United Earth Federation===
[[Image:UEDSolaris.png|thumb|right|480px|The be-all and end-all of the UEF's military might—the UED ''Solaris''.]]
[[Image:NuKent.jpg|thumb|right|480px|The fastest ship in the UEF fleet on afterburners—the UEF ''Kentauroi''.]]
====Summary====
In the fifty years following the collapse of the Sol-Delta Serpentis jump node, the [[Galactic Terran Alliance]] was reorganised into the [[United Earth Federation]], or UEF, headed by the Global Ubuntu Party.

The Ubuntu Party placed emphasis on economic recovery and political stability, rather than military strength. What was left of the old GTA military was scrapped and slimmed down to suit the need of only being able to maintain order throughout much of an entire star system. Standard military doctrine in the UEF places emphasis on frigates that can serve as mobile carriers and operate in remote locations for lengthy periods, as well as versatile fighters that can be reassigned to numerous roles in a single operation. The main base of operations for each of the UEF's three fleets is a [[UED Solaris|''Solaris''-class destroyer]], a formidable carrier and command vessel that is never deployed on the front lines unless absolutely necessary.

====Warships====
The UEF only has three destroyers in active service, all of them [[UED Solaris|''Solaris''-class destroyers]]. Each of these destroyers serve as a base of operations to the Federation's three fleets, as well as their commanding officers. Originally considered "answers to a nonexistent problem", the ''Solaris'', ''Toutatis'' and ''Eris'' now serve at the very centre of the UEF's battle doctrine and, despite being designed to effectively neutralise an attack from any direction, are rarely seen on the front-lines. Instead, most military operations are carried out either by the fighter squadrons within these fleets or by smaller, faster frigates and cruisers assigned to each fleet.

Frigates and cruisers make up the Federation's primary attacking force. The two frigate classes currently in active service, the [[UEFg Karuna|''Karuna'']] and [[UEFg Narayana|''Narayana'']], both sport a hangar capable of housing a small fighter squadron, and the sole cruiser class, the corvette-sized [[UEC Sanctus|''Sanctus'']], is used in almost the same manner as the GTVA deploys the ''Deimos''. Although every frigate and cruiser in the Federation is assigned to one of the three fleets, they are often deployed on their own, away from the ''Solaris''-class destroyer that serves as their fleet's home base.

====Spacecraft====
The Federation makes heavy use of high-performance spacecraft that are generally much more agile and versatile than their GTVA counterparts. Almost every fighter class is capable of reverse thrust, as well as reverse afterburn, adding to their overall versatility on the field. The Federation's main space superiority fighter is the [[UEF Uhlan|UEF ''Uhlan'']], an all-round ship capable of fulfilling any fighter role as the situation demands. Other common ships include the [[UEF Kentauroi|UEF ''Kentauroi'']], the Federation's cross between the GTVA's ''Nyx'' and ''Perseus'' fighters, the [[UEF Uriel|UEF ''Uriel'']], a heavy assault fighter sporting a long-range gauss cannon, and the [[UEB Durga|UEB ''Durga'']], an assault bomber with the firepower to level entire cities. The Federation also produces an additional class of spacecraft, the [[UEF Lao Tze|UEF ''Lao Tze'']], an extremely powerful but difficult to fly heavy fighter used primarily by the elite [[Knights of the White Brotherhood]].

====Weaponry====
While the GTVA have spent decades developing beam and energy-based weaponry, Federation anti-warship armaments, on the other hand, follow a more traditional kinetic-based principle. The primary stopping power of the UEF's two frigate classes, the ''Karuna'' and ''Narayana'', are a pair of powerful bow-mounted heavy mass drivers that are complemented by their own targeting system, allowing them to incapacitate crucial enemy subsystems or turrets at will. The ''Solaris'' destroyer's primary weapons, however, come in the form of twelve heavy torpedo launchers that can easily decimate anything short of a superdestroyer in a matter of minutes. Secondary armament on all ships are made up of a mixture of anti-fighter tracers, flak guns and smaller anti-subsystem torpedo launchers.

The technology that powers Federation fighter-mounted weaponry, although crude and slightly dated as compared to the much greater level of sophistication seen in Alliance weaponry, is nonetheless just as effective, if not more so. The standard-issue [[Vulcan|SCWS-1 Vulcan]] is a rapid-firing plasma cannon that can easily track torpedoes and even the fastest ships produced by the Alliance, while the slightly heavier [[Maul|SCWS-2 Maul]] sacrifices refire rate for even more damage per shot. In the many decades since the [[Great War]], the legendary [[GTW Prometheus]] has been remade into the [[Rapier|SCWS-6 Rapier]], the most powerful fighter-compatible plasma weapon available to the standard Federation pilot, capable of Swiss-cheesing even the heaviest fighters in the Alliance with a few shots. Federation gunships such as the ''Uriel''-class mount a third weapon: a long-range ammo-based mass driver, such as the [[Archer]] or [[Vajra]], designed to obliterate turrets and subsystems from beyond regular retaliation range.

The UEF sports a slightly wider variety of secondary weapons compared to the GTVA. In addition to the regular [[Hellfire Missile|Hellfire dumbfire missile]], [[Javelin|Javelin aspect-seeking dogfight missile]], [[Grimler|Grimler heavy missile]] and [[Paveway|Paveway anti-subsystem missile]], as well as three anti-warship torpedoes, the Federation also produces two fire-and-forget swarm missiles, called the [[Dirk]] and [[Dart]], as well as the dreaded [[Slammer|Slammer suppression missile]], an aspect-seeking cluster missile containing heat-seeking explosive charges. While the Dirk and Dart provide Federation pilots with a third tier of dogfight missiles to choose from, the Slammer, on the other hand, has gained a reputation among the GTVA for being a fighter- and bomber-killer, capable of destroying entire wings with one hit, and is the most feared weapon in the UEF's arsenal of missiles.

===Vishnans===
[[Image:Vishnanpreserver.jpg|thumb|right|480px|The embodiment of Vishnu—the Vishnan Preserver.]]
[[Image:Vishnanmissionary.jpg|thumb|right|480px|The first known Vishnan ship ever encountered—the Vishnan Missionary.]]
:''See also: [[Vishnans]]''
====Summary====
The [[Vishnans]] are a new species introduced in Blue Planet. They describe themselves as Great Preservers and counterparts of the [[Shivans]], though initial contact with their species was possibly violent. What little is known about the Vishnans is sketchy and fairly inaccurate at best. The full capabilities of the Vishnans are, like the Shivans, unknown to the Terrans or Vasudans. What ''is'' established is that the Vishnans are arguably the only race capable of matching the Shivans.

All Vishnan ships are unmanned, piloted by instanced sub-sets of the species' superordinate consciousness nested in a hierarchical dependency of cognitive structure. They have not been encountered in the same universe as the GTVA and UEF, although it is hinted that they do exist.

====Warships====
Only four classes of Vishnan warships have been encountered so far, the largest simply designated the [[Vishnan Preserver]]. The Preserver appears to be a superjuggernaut with enormous tactical and strategic capabilities, including the modification of jump nodes. It may be unique.

The Vishnans' main warship is a massive squid-like vessel designated the [[Vishnan Sacred Keeper]]. While classified as a destroyer, the Keeper is able to go toe-to-toe with a Shivan [[SJ Sathanas|''Sathanas''-class juggernaut]], and its hull rating is well within superdestroyer levels. With a large beam emitter built into its underside, the Keeper is usually heavily guarded by a number of cruiser-class [[Vishnan Arbiter]]s and gunship-class [[Vishnan Protector]]s. The Keeper is the core of its entire fleet and is integral to their ability to communicate with their superconsciousness.

The Keeper's escorts, the Arbiter and Protector, are smaller, faster vessels armed with lighter beam cannons. They do not usually undertake and complete tasks on their own, but instead provide fire support for Vishnan strikecraft and, in return, require escort from enemy fighters and bombers on occasion due to their sub-par defences.

====Spacecraft====
To date, the Vishnans are known to possess two fighter classes and two bomber classes. Vishnan spacecraft vastly outperform their Shivan equivalents, with their fighters capable of flying circles around even the extremely agile Shivan [[SF Dragon|''Dragon''-class fighter]], and their bombers manoeuvrable enough to defend themselves and not compromise on secondary weapons. All Vishnan spacecraft are made of a crystalline compound that repairs itself over time. On the downside, Vishnan spacecraft number a lot less than their Shivan counterparts. Most Vishnan wings hardly ever exceed three ships, while Shivan ships by contrast are usually deployed in wings exceeding four ships.

The most commonly seen Vishnan spacecraft is designated the [[Vishnan Missionary]]. Agile and fast, the Missionary is an interceptor, reconnaissance vessel and space superiority fighter all in one. It was the first known Vishnan spacecraft ever encountered by the Alliance. The other Vishnan fighter, the [[Vishnan Preacher]], sacrifices speed and secondary weapon capacity for additional durability and an impressive combined primary firepower of ten guns.

The Vishnans' main bomber, designated the [[Vishnan Seeker]], is a medium strike bomber that can carry approximately the same amount of ordnance as the [[GTB Ursa|GTB ''Ursa'']]. The other bomber class is the massive [[Vishnan Inquisitor]], capable of carrying torpedoes that can easily level anything smaller than a superdestroyer with a few hits.

====Weaponry====
:''See also: [[Vishnan Beam Weapons]]''
The Vishnans are the second species ever encountered by the Terrans and Vasudans to already demonstrate beam capability. The two most powerful of these beams are mounted only on the Preserver and Sacred Keeper, while the lighter, smaller beams are mounted onto the Arbiters and Protectors. Vishnan beam weapons out-range and out-damage Shivan beams by a significant margin, but do not recharge as quickly.

Fighter-mounted Vishnan weaponry lack diversity as compared to Terran, Vasudan and even Shivan weaponry. Only one kind of primary weapon is used across all Vishnan fighters and bombers to date. The [[Vishnan Primary]] is a medium-firing heavy cannon that can double up as an anti-subsystem weapon.

Three classes of Vishnan secondary weapons are known to date. The [[Vishnan Missile]] is an aspect-seeking missile that can also be used as a light anti-subsystem missile, while the [[Vishnan Megabomb]] is used in the same manner as the GTVA's [[GTM Cyclops|''Cyclops'' torpedo]], although it is far more powerful. The third class of Vishnan missile, the [[Vishnan Ultrabomb]], is a torpedo containing a subspace device that, on impact, transfers a devastating warhead from within a nearby Keeper onto the target.

==Development==
===Original Concept===
:"Wow." 
::''—excerpt of Reply #60 of the original Age of Aquarius release thread, by Jeff Vader'' [http://www.hard-light.net/forums/index.php?topic=49876.msg1009465#msg1009465]

Blue Planet started off as a one-man project by Darius, much akin to how [[The Procyon Insurgency]] was created. When Age of Aquarius was released, several members of the community pointed out numerous errors and problems with the campaign, including crashes, missing effects, and empty tech room descriptions. As a consolation, these members also added praise to the portions of Age of Aquarius that did play out as planned, adding special mention to the harder missions, such as [[Keepers of Hell]], and the music used in other missions, such as [[Forced Entry]]. The numerous errors, glitches and issues prompted Darius to release a patch only two days after it was first released. Almost immediately after the patch was released, comments on the campaign shifted from its issues and praise to praise only. Much of the initial praise was targeted at three aspects of the campaign:

* mission design and difficulty;
* background music; and
* storyline.

Age of Aquarius also came in for special praise as it made extensive use of FS2_Open's cutscene feature, which was relatively new and unused at the time.

===The Team===
:"Very funny, Goob." 
::''—the first post on the Blue Planet board, by NGTM-1R'' [http://www.hard-light.net/forums/index.php?topic=55706.msg1125921#msg1125921]

Blue Planet as a project team, however, did not take off until about ten months later, when Age of Aquarius began to be relayed to newcomers as a recommended FS2_Open campaign, alongside stalwarts such as [[Derelict]] and [[Warzone]]. The formation of the Blue Planet board on the Hard Light Productions Forum's Hosted Projects section—reserved only for the most active hosted projects on HLP—was initially viewed as a joke, but ultimately became the catalyst needed for the formation of the project team as it is today. Over the course of the next few months, the size of the Blue Planet team grew rapidly. Initially comprising only Darius, as of August 2010, the Blue Planet team is made up of sixteen core members and six beta-testers.

===War in Heaven===
Not too long after the release of Age of Aquarius, Darius had finished conceiving a storyline for War in Heaven. However, he chose to wait until enough positive feedback was received from members of HLP before attempting to work on it. The development cycle of WiH was accelerated by rapid expansion of the project team from 2009 to early 2010, as well as the use of subversion, enabling all members of the team to work on the same version of the project.

===Chanticleer===
[[Chanticleer]] was written as a solo project by Jake "qweqwe321" Berman in 2022 and 2023, with the support of Blue Planet team members Darius and The_E, and beta testing by Fusion and LawBroSteve.

===Spinoff Campaigns===
* Battle of Neptune, by BP team member Dilmah G, covering the First Battle of Neptune.
* Battle Captains, by Lepanto, covering capital ship combat under Admirals Severanti and Lopez.

===BP3 concept===
''Though the project is currently in hibernation, a 2010 concept on BP3's plot [https://gist.github.com/The-E/ac1ea185c803314db59fd891418498d0 was disclosed] by team member The_E on August 4th, 2024:''

Mission 0: Something awesome and fear-inducing. Using the Capella node farm/supernode, the Shivans have opened entry points into multiple systems all around the Alliance. All pregnancies have miscarried and madness is rampant among the Nagari-sensitive. The Shivan apocalypse is underway and billions of Terrans are trying to flee to Sol, where, rumor has it, the enlightened will be spared. If only they knew the truth!

Mission 1: You are the Vasudan Jester Nabirasul, combination visionary and hard-ass Dirty Harry warfighter. Angst is beneath you. Flying alongside trusty sidekick Asenath, warrior-heir-possible-future-empress-lady, you fight alongside your fellow Medjai and the Terrans to hold the line in the darkest places of the war. Shivan behavior is explosively weird, entire squadrons vanish every day, and tens of millions are dying to systematic orbital bombardment. Locate the survivors of a planet-based militia squadron (lots of Kulases) and finish up their recon in force, glimpsing horrifying aspects of the new Shivan threat. (Location? Vega? Elsewhere?)

Mission 2: There ain't no time for 'gradual buildup' here. A trio of Sathanas juggernaughts have moved into (location), and they seem intent on using their subspace weapons to seal the system's nodes so they can wipe out the trapped GTVA forces. With the full might of the system's SSM defense arrays unleashed, blow a gap through the juggernaught's screens so the 14th Battlegroup, under Admiral Thea Carey, can make the kind of attack they've been drilling for eighteen years. Two Sathanases go down; the third manifests some really weird behavior (maybe starts firing huge missiles) and the attack is aborted in favor of the use of a precious meson bomb.

Mission 3: With the campaign in [system] sinking under the weight of escalating Shivan numbers and ferocity, hold the line as civilians and military assets alike make it out. Choose between saving defenseless civilians or preserving vital warfighting ability. Inevitably the defense crumbles; you are the last out before the meson bombs jump in from the other side. The node is sealed, but the Shivans will have it back online in less than a week, and their incursions are proceeding from other systems.

Mission 4: Emperor Khonsu II requisitions you for a special mission. In company with Samuel Bei, the not-yet-executed Noemi Laporte, Admiral Steele, the sleeper ship Sanctuary, and the UEF's Admiral Netreba, you will travel through the Knossos in N362 and locate our universe's Vishnans to petition them for assistance. Make transit through the Knossos as a Shivan battle group rumored to be led by the Dante and other nightmares breaks through GTVA lines and pursues you.

Mission 5: The Vishnans are located by Samuel Bei's scout wings, and a Keeper is sighted. But attempts to make contact are met with force, and even Bei's pleas cannot stir the Vishnans. It becomes clear that they support the Shivan cull. (Alternatively, Bei's pleas move them, but then -) Admiral Steele reveals the Security Council's MORPHEUS contingency includes a plan to capture a Vishnan Keeper and use it to seize control of a local Vishnan battle group - but a powerful Sensitive will be required. The Vishnans attack the task force and seem ready to overwhelm them when suddenly they go dead. Something has happened to the Keeper - the Dante and a group of Shivans have approached and disabled it.

Mission 6: It becomes apparent that the Vishnan Great Psyche has been murdered by the Shivans, as Laporte foresaw. Cut off from Alliance space and with no hope of Vishnan assistance, the task force flees deeper into the space beyond the Knossos, pursued by Shivans. Here they discover a derelict Vishnan Preserver. They use it to modify a node for long-range travel back to what they hope is Alliance space. After a heartbreaking farewell to Eriana, Sam Bei remains behind with a task force to study the Preserver and hopefully enact Steele's plan. The rest of the task force jumps through the modified node, but the Jester sabotages the calculations, and instead they find themselves in a distant and eerie universe.

Mission 7: A derelict spacecraft of enormous age and unknown design is located, drifting and apparently dead. Plumbing its systems, the Jester learns of the rise and fall of the Great Creators. But his attempts to understand the purpose of the Shivans are cut off by survey data indicating that 90% of the stars in the sky are surrounded by Shivan habitats - this universe is nothing but Shivan, through and through. Swarms of bizarre Shivans attack the task force and the groups are scattered in a series of panicked jumps: Laporte and the Federation contingent one way, Nabirasul and the Emperor another, and Steele and the Terrans a third.

Mission 8: Laporte's group stumbles on a cluster of Shivan comm nodes. By use of her Nagari talent and Fedayeen data, Laporte gathers information from these nodes on Shivan history, motives, and goals while the Eris holds off mighty Shivan attacks. Laporte realizes that the attacks on GTVA space have only been the reflex action of the Shivan algorithmic response, and that the true offensive is on its way - an invincible armada of star-burning, impregnably defended Shivan worldships. In a staggering moment of existential terror she witnesses the scope of the universe - nay, universes - under Shivan dominion, and realizes that mankind has no hope of defeating them. Netreba and the Eris are lost, leaving Laporte, Simms and the Indus to flee towards a distant signal.

Mission 9: Admiral Steele and his air wing discover a route back home - it's a modified node used for interdimensional transit, and hitting it at the right trajectory should lead to Capella. Fly as a ducttape-loving pilot of the 212th Silver Scythes as Steele goes on the attack, rolling in on what seems to be a Shivan rally point to buy time for the rest of the task force to regroup on the supernode. Now if only those damn Feds and Vasudans would show up before you're overwhelmed...

Mission 10: The Emperor and Nabirasul find themselves in what seems to be a blend or merger between universes, as if worlds have begun to interface without connecting nodes. Analysis of the microwave background reveals that they have entered a vast, artificial cosmos which was once a fertile womb for intelligence - in turn only a cell of something greater. Now it is dead, haunted by ancient ghosts and eerie whispers. The truth of the Brahmans' cancerous, malignant end is revealed as the task group stumbles upon a grim storehouse of doomsday devices: apoptotic weapons, meant to destroy universes before they are subverted by some hideous threat that might very well be what the Brahman became. Nabirasul speaks the grim truth: the Shivans are a way to prevent this from ever happening again. The Emperor considers abandoning all hope and surrendering to the Hammer of Light's prophecies, but Nabirasul rouses the emperor with a desperate plan. Suddenly the ancient debris comes alive with a warning: a threat is approaching. Shivans flood the area but seem to ignore the Vasudans, rushing to some unknown purpose. (?) The Vasudans grab one of the apoptotic weapons and blast their way through the Shivans towards Steele's distant signal as madness chases them; if the player doesn't make it out in time we need to make truly awful things happen.

Mission 10--1: An interlude of sad music and unexpected behavior. The player is Samuel Bei, alone in a spacesuit outside the great mass of the Vishnan Preserver. He records a fond farewell to Eriana, and then opens his suit to vacuum.

Mission 11: Synthesizing Laporte's Shivan data and the Jester's apoptotic weapon, a desperate plan comes into focus, but it'll require the surviving strength of the GTVA to work. Someone needs to make a run through the supernode, into Capella, through the grip of the black hole, into one of the nodes there and finally to Alliance space, killing every Shivan that gets in the way and discussing the desperate plan with the Alliance. The odds of survival are low, and a destroyer can't be risked. But there's one ship in the task force that's had experience with crazed sequential jumps under extreme conditions: the heavily retrofitted GTC Duke. With escort from two crack pilots, Corey and Taylor, make the run through hell and come out the other side to deliver a warning and a plan of action to the GTVA.

Mission 12: The GTVA has a proud tradition of stealing knowledge from ancient races to defend against unstoppable Shivan onslaughts. Laporte's Shivan data (hint that it was pushed her way by Ken) indicates that the center of Shivan strength in this universe lies well past the binary star system from Into the Lions Den, but that there is a single weak link in the chain that could be sealed to hold those Shivans back. The main Shivan thrust, however, is coming through the Capella supernode, directly from an adjacent universe that is a massive Shivan hub. Stopping them will require a two-pronged offensive. The Shambhala can seal the node past the Binary Star; the Emperor's recovered apoptotic weapon can be brought through the supernode and deployed in the neighboring universe where the worldship armada is gathering. But this plan requires the GTVA to launch an attack into Capella and open a gap for both the Shambhala and the Emperor to make their runs. Fly as the aging, unspeaking Wing Commander Snipes as the attack begins, but bogs down in fierce Shivan resistance - until Samuel Bei arrives in the body of a Vishnan Keeper, leading a subverted Vishnan battle group to assist. The tortured Sam has finally realized the meaning of his vision from AoA: he passed into the Great Psyche's memory storage when his body was dead, but now, with the Psyche dead, only by completely destroying his physical form can he render the transfer complete. Now he is a surrogate Great Psyche, struggling to give purpose to the remaining Vishnans for one last death ride.

Mission 13: Steele, the Emperor, and Laporte make the transit through their node into Capella as the GTVA push also breaks through. Juggernauts and worse are waiting for them, but the distraction gives the two offensive task groups time. Fly as Laporte as Steele forms up with the Shambhala and heads for Gamma Draconis, then the nebula, and then the binary star system beyond in a running battle. Meanwhile, the Emperor leads his Medjai on a dive into the singularity proper, leading them into the adjacent Shivan Hell universe.

Mission 14: Sam's last stand. Hop between Vishnan fighters as you, the consciousness that Sam has become, throw yourself into an all-out struggle with the Shivans as the surviving GTVA fleet withdraws back into friendly space (where they must survive for the plan to work). One of the Dantes or some appropriate big-bad monstrosity guns for your Preserver, but Eriana rams the Sanctuary, loaded with meson ordnance, into it and destroys it. Eventually you die in some awesome fashion.

Mission 15: Fly as Laporte (or Admiral Chiwetel Steele?) as you escort the Shambhala through the Knossos in the binary system and find yourself, at last, in the center of Shivan power in this galaxy - an enormous gate installation at the galactic core, guarded by a fleet so huge it's mostly skybox. With the Shambhala destroyed by the Shivans, enact your own contingency plan and fly yourself (or the Atreus?) in to take out the gate's stationkeeping drive. Optionally, if you're really good, survive an attack by (something scary) and make it back to the node alive. With this gate destroyed, the Shivans in this galaxy will be cut off from their superintelligence and it will take their local structure some time to reorganize. Except, of course, it's all meaningless if this backwater universe is still connected to the greater Shivan menace -

Mission 16: Fly alongside your Emperor as you emerge in Shivan Hell: a parallel universe swarming with Shivan manufacturing and thought. Legions of Shivan worldships represented on the skybox are headed for the supernode to transition into Capella. Fly suicidal defense as the Emperor brings the apoptotic weapon online and wipes out the whole universe, leaving our own reality isolated (for the moment), and the Shivans of our galaxy cut off from neighboring groups in Andromeda as well as their greater pan-universal brethren (and thus disorganized, a la post-Lucifer).

Mission 17: An epilogue. Years of bloody struggle to reclaim lost worlds, rebuild lost lives and purge the Shivans from the local node group lie ahead of the Alliance. 65% of the human race and 75% of Vasudans were killed, but the great hub of Earth remains to build new warships and new lives, and the Vasudans have always been resilient. With their Emperor and their greatest hero gone, they are a people leaderless, but a people birthed in sorrow, die in sorrow: they are used to it and prepared to move on.

Something Else?: Perhaps something tying in to the unresolved Bosch/Ken arc, a hint at Bosch persisting in the great totality of the Shivan organism, glimpsing an eternal past and future for the Shivans and understanding that while the Terran-Vasudan Alliance will perhaps carve out its own niche, this may be what the Shivans desired all along - because who can grasp the fearsome intellect of this worlds-spanning mind?

Also Laporte and Simms might be alive at the end? We could fix that.

Biggest problem with this may be the need for any sort of new assets. Mostly skyboxes.

MAP OF UNIVERSES

DEAD EARTH
| 
| 
| 
OURS ----------------- SHIVAN HELL
| 
| 
| 
TOMB UNIVERSE

==Releases==
''Age of Aquarius'' was first released on October 3, 2007, and the first patch for it was released two days later on October 5. In February 2010, AoA was rereleased with voice acting, reorganized modpack, and new assets.

The first part of ''War in Heaven'', consisting of the first two acts (15 missions) was released on August 7, 2010. The third act was released on January 7, 2013.

''Chanticleer'' was released in September 2023.

==Developers==
===Age of Aquarius and War in Heaven Project Staff===
*'''Darius''' — ''Project lead''

*'''Axem''' — ''Just another FREDder''
*'''Belisarius''' — ''Music composer''
*'''blowfish''' — ''Modeller''
*'''Cobra''' — ''Voice acting management assistance''
*'''Daddy Warhol''' — ''Music composer''
*'''Dilmah G''' — ''Mission designer, Military advisor''
*'''Dragon''' — ''Texture artist''
*'''Esarai''' — ''Modeller''
*'''Fury''' — ''Tabler, AI lead''
*'''General Battuta''' — ''Writer, Mission designer''
*'''HerraTohtori''' — ''Skybox artist''
*'''Nighteyes''' — ''Effects artist''
*'''Rian''' — ''Script content redundancy axe-man, Character writer''
*'''Steve O''' — ''Model contributor, Paternal figure''
*'''The E''' — ''Codework, Mission work, Model work, Writer''
*'''Wanderer''' — ''Effects artist''
*'''Zacam''' — ''Testing, Mod pack management, SVN manager''

===Chanticleer Project Staff===
*'''qweqwe321''' — Project Lead

===Beta Testers===
* [[User:Androgeos Exeunt|Androgeos]] [[User_talk:Androgeos_Exeunt|Exeunt]]
* MatthTheGeek
* QuantumDelta
* Snail
* Spoon
* ubiquitous
* Fusion
* Lawbrosteve

==See Also==
* [[Blue Planet: Age of Aquarius]]
* [[Blue Planet: Age of Aquarius Campaign Walkthrough]]
* [[Blue Planet: War in Heaven]]
* [[Blue Planet: War in Heaven Campaign Walkthrough]]
* [[Blue Planet: Chanticleer]]
* [[Blue Planet: Chanticleer Campaign Walkthrough]]
* [[Blue Planet Extras Portal]]
* [[Blue Planet ship database]]
* [[:Category:Blue Planet]]

==Related Links==
*[http://blueplanet.hard-light.net Blue Planet Website | Hard-Light Productions.net]
*[http://www.hard-light.net/forums/index.php/board,169.0.html Blue Planet board | Hard-Light Productions.net]
*[http://www.moddb.com/mods/blue-planet-war-in-heaven Blue Planet at ModDB]
*[http://www.imdb.com/title/tt3566260/ Blue Planet: War in Heaven at IMDB]

[[Category:User-made_Campaigns]]
[[Category:Blue Planet|*]]

FreeSpace 2 Shivan Ship Database

2024-08-04T11:16:16Z

Mobius: Number 17 trivia

[[FreeSpace_2_Ship_Database|FreeSpace 2 Ship Database]]

====SFr ''Baraqel''====
*[[SFr Dis]] class freighter
*Emerged from [[Knossos]] portal in [[A Lion at the Door]] (sm1-04) and attempted to drop off a cargo container
**Cargo: Sentry Guns
*Initially docked with an [[SAC 3]] cargo unit, which contained Missiles
*Destroyed by [[107th Ravens]] squadron

====SFr ''Maul''====
*[[SFr Mephisto]] class transport
*Attempted to drop off a cargo container near [[Knossos]] portal in [[A Lion at the Door]] (sm1-04)
**Cargo: Sentry Guns
*Initially docked with an [[SC 5]] cargo unit, which contained Propulsion Units
*Destroyed by [[107th Ravens]] squadron

====SFr ''Neqael''====
*[[SFr Asmodeus]] class freighter
*Emerged from [[Knossos]] portal in [[A Lion at the Door]] (sm1-04) and attempted to drop off a cargo container
**Cargo: Sentry Guns
*Initially docked with an [[SAC 2]] cargo unit, which contained Sensor Arrays
*Destroyed by [[107th Ravens]] squadron

====ST ''Semyaza''====
*[[ST Azrael]] class transport
*Waited near [[Knossos]] in [[A Lion at the Door]] (sm1-04)
**Cargo: Shivan Personnel
*Destroyed by [[107th Ravens]] squadron

====SC ''Urobach''====
*Does not appear in any missions
*Attacked and disabled [[FreeSpace_2_Terran_Ship_Database#GTD Aquitaine|GTD ''Aquitaine'']] just before [[Argonautica]] (sm3-05)
*Destroyed by [[FreeSpace_2_Terran_Ship_Database#GTD Aquitaine|GTD ''Aquitaine'']]

====SC ''Armaros''====
* [[SC Rakshasa]] class cruiser
* Attacked GTVI convoy in [[Crisis in Capella]]
* Destroyed by GTC ''Adamant''

====SC ''Asuras''====
*[[SC Cain]] class cruiser
*Discovered in [[Nebula System|nebula]] right before [[The Great Hunt (FS2)|The Great Hunt]] (sm1-06)
*Destroyed by [[FreeSpace_2_Terran_Ship_Database#GTCv Actium|GTCv ''Actium'']] and [[FreeSpace_2_Terran_Ship_Database#GTCv Lysander|GTCv ''Lysander'']] in [[The Great Hunt (FS2)|The Great Hunt]] (sm1-06)

====SC ''Azmedaj''====
*[[SC Cain]] class cruiser
*Destroyed by [[203rd Scorpions]] squadron in [[Return to Babel]] (sm3-03)

====SC ''Baal''====
*[[SC Cain]] class cruiser
*Destroyed by [[FreeSpace_2_Vasudan_Ship_Database#GVCv Khepri|GVCv ''Khepri'']], [[FreeSpace_2_Vasudan_Ship_Database#GVC Heket|GVC ''Heket'']], [[FreeSpace_2_Terran_Ship_Database#GTC Stalwart|GTC ''Stalwart'']] and [[70th Blue Lions]] squadron in [[Their Finest Hour]] (sm3-08)

====SC ''Bane''====
*[[SC Cain]] class cruiser
*Attacked [[GTVA]] forces retreating to [[Vega]] in sm3-10
* Destroyed by ''[[FreeSpace_2_Terran_Ship_Database#GTCv Lemnos|GTCv Lemnos]]'', ''[[FreeSpace_2_Terran_Ship_Database#GTC Sparta|GTC Sparta]]'', ''[[FreeSpace_2_Terran_Ship_Database#GTC Malta|GTC Malta]]'', ''[[FreeSpace_2_Terran_Ship_Database#GTC Ertanax|GTC Ertanax]]'', ''[[FreeSpace_2_Terran_Ship_Database#GTC Templar|GTC Templar]]'', ''[[FreeSpace_2_Vasudan_Ship_Database#GVC Ptah-Nu|GVC Ptah-Nu]]'' and [[70th Blue Lions]] squadron

====SC ''Behemoth''====
*[[SC Rakshasa]] class cruiser
*Emerged from [[Knossos]] portal in [[Gamma Draconis]] right before [[A Lion at the Door]] (sm1-04)
*Destroyed by [[107th Ravens]] squadron in [[A Lion at the Door]] (sm1-04)

====SC ''Belphegor''====
*[[SC Rakshasa]] class cruiser
*Attempted to hold a [[Shivan]] position in [[Gamma Draconis]] during M-05
*Destroyed by 77th Deadly Sevens squadron

====SC ''Dahaka''====
*[[SC Cain]] class cruiser
*Detected near second [[Knossos]] portal in [[Nebula System|nebula]] by [[203rd Scorpions]] squadron in [[Straight, No Chaser]] (sm3-04)
*Destroyed by [[203rd Scorpions]] squadron

====SC ''Demogorgon''====
*[[SC Cain]] class cruiser
*Destroyed by [[FreeSpace_2_Vasudan_Ship_Database#GVCv Khepri|GVCv ''Khepri'']],[[FreeSpace_2_Vasudan_Ship_Database#GVC Heket|GVC ''Heket'']], [[FreeSpace_2_Terran_Ship_Database#GTC Stalwart|GTC ''Stalwart'']] and [[70th Blue Lions]] squadron in [[Their Finest Hour]] (sm3-08)

====SC ''Gibborim''====
*[[SC Cain]] class cruiser
*Arrived through [[Epsilon Pegasi]] to intercept a civilian convoy in [[Exodus (FS2)|Exodus]] (sm3-06)
*Destroyed by [[70th Blue Lions]] squadron

====SC ''Goliath''====
*[[SC Cain]] class cruiser
*Emerged from [[Knossos]] portal in [[Gamma Draconis]] in [[A Lion at the Door]] (sm1-04)
*Destroyed by [[FreeSpace_2_Terran_Ship_Database#GTD Carthage|GTD ''Carthage'']]

====SC ''Iblis''====
*[[SC Rakshasa]] class cruiser
*Discovered in [[Nebula System|nebula]] right before [[The Great Hunt (FS2)|The Great Hunt]] (sm1-06)
*Destroyed by [[FreeSpace_2_Terran_Ship_Database#GTCv Actium|GTCv ''Actium'']] and [[FreeSpace_2_Terran_Ship_Database#GTCv Lysander|GTCv ''Lysander'']] in [[The Great Hunt (FS2)|The Great Hunt]] (sm1-06)

====SC ''Karnatoth''====
*[[SC Cain]] class cruiser - simulated
*Destroyed by a wing of GTVA fighters in the G-Shi simulation

====SC ''Malor''====
*[[SC Cain]] class cruiser
*Attempted to attack [[FreeSpace_2_Terran_Ship_Database#GTA Lucidity|GTA ''Lucidity'']], [[FreeSpace_2_Terran_Ship_Database#GTFr Erinpura|GTFr ''Erinpura'']] and [[FreeSpace_2_Terran_Ship_Database#GTFr Vauban|GTFr ''Vauban'']] in [[Battle of the Wilderness]] (sm2-01)
*Destroyed by [[134th Barracudas]] squadron

====SC ''Melchom''====
*[[SC Cain]] class cruiser
*Attacked [[GTVA]] forces retreating to [[Vega]] in [[Apocalypse]] (sm3-10)
*Destroyed by [[FreeSpace_2_Terran_Ship_Database#GTCv Lemnos|GTCv ''Lemnos'']], [[FreeSpace_2_Terran_Ship_Database#GTC Sparta|GTC ''Sparta'']], [[FreeSpace_2_Terran_Ship_Database#GTC Malta|GTC ''Malta'']], [[FreeSpace_2_Terran_Ship_Database#GTC Ertanax|GTC ''Ertanax'']], [[FreeSpace_2_Terran_Ship_Database#GTC Templar|GTC ''Templar'']], [[FreeSpace_2_Vasudan_Ship_Database#GVC Ptah-Nu|GVC ''Ptah-Nu'']] and [[70th Blue Lions]] squadron

====SC ''Orcus''====
*[[SC Rakshasa]] class cruiser
*Destroyed by [[FreeSpace_2_Vasudan_Ship_Database#GVCv Khepri|GVCv ''Khepri'']], [[FreeSpace_2_Vasudan_Ship_Database#GVC Heket|GVC ''Heket'']] and [[FreeSpace_2_Terran_Ship_Database#GTC Stalwart|GTC ''Stalwart'']] and [[70th Blue Lions]] squadron in [[Their Finest Hour]] (sm3-08)

====SC ''Rakshasa''====
*'''NOTE: inconsistency: invalid name'''
*[[SC Rakshasa]] class cruiser
*Attacked [[FreeSpace_2_Terran_Ship_Database#GTCv Bretagne|GTCv ''Bretagne'']] as it was trying to escape from the [[Nebula System|nebula]] in m-06
*Destroyed by [[FreeSpace_2_Terran_Ship_Database#GTCv Bretagne|GTCv ''Bretagne'']] and two fighter wings

====SC ''Rakshasa 17''====
*'''NOTE: inconsistency: invalid name'''
*[[SC Rakshasa]] class cruiser
*Destroyed by [[99th Skulls]] squadron in [[Into the Lion's Den]] (loop2-2)

====SC ''Rakshasa 19''====
*'''NOTE: inconsistency: invalid name'''
*[[SC Rakshasa]] class cruiser
*Destroyed by [[99th Skulls]] squadron in [[Into the Lion's Den]] (loop2-2)

====SC ''Rakshasa 45''====
*'''NOTE: inconsistency: invalid name'''
*[[SC Rakshasa]] class cruiser
*Arrived from [[Nebula System|nebula]] system in [[Into the Lion's Den]] (loop2-2)
*Destroyed by [[99th Skulls]] squadron

====SC ''Ramakara''====
*[[SC Rakshasa]] class cruiser (simulated)
*Destroyed by a wing of [[GTVA]] fighters in the G-Shi simulation

====SC ''Rephaim''====
*[[SC Rakshasa]] class cruiser
*Sighted in the [[Nebula System|nebula]] just before [[Speaking in Tongues]] (sm2-09)
*Exchanged unidentified (at the time) transmissions with the [[FreeSpace_2_Rebel_Ship_Database#NTF Iceni|NTF ''Iceni'']] using [[ETAK]] technology
*Destroyed by [[203rd Scorpions]] squadron

====SC ''Sammael''====
*[[SC Rakshasa]] class cruiser
*Destroyed by [[203rd Scorpions]] squadron in [[Return to Babel]] (sm3-03)

====SC ''Sathariel''====
*[[SC Rakshasa]] class cruiser
*Sent in along with the [[FreeSpace_2_Shivan_Ship_Database#SD Barqu|SD ''Barqu'']] to reinforce [[Shivan]] positions in [[Gamma Draconis]] after the [[FreeSpace_2_Shivan_Ship_Database#SCv Nosferatu|SCv ''Nosferatu'']] was destroyed in M-01b
*Destroyed by two wings of [[GTVA]] fighters in M-01b

====SC ''Sephiroth''====
*[[SC Rakshasa]] class cruiser
*Detected near second [[Knossos]] portal in [[Nebula System|nebula]] by [[203rd Scorpions]] squadron in [[Straight, No Chaser]] (sm3-04)
*Destroyed by [[203rd Scorpions]] squadron

====SC ''Thanatos''====
*[[SC Rakshasa]] class cruiser
*Attacked [[GTVA]] forces retreating to [[Vega]] in [[Apocalypse]] (sm3-10)
*Destroyed by [[FreeSpace_2_Terran_Ship_Database#GTCv Lemnos|GTCv ''Lemnos'']], [[FreeSpace_2_Terran_Ship_Database#GTC Sparta|GTC ''Sparta'']], [[FreeSpace_2_Terran_Ship_Database#GTC Malta|GTC ''Malta'']], [[FreeSpace_2_Terran_Ship_Database#GTC Ertanax|GTC ''Ertanax'']], [[FreeSpace_2_Terran_Ship_Database#GTC Templar|GTC ''Templar'']], [[FreeSpace_2_Vasudan_Ship_Database#GVC Ptah-Nu|GVC ''Ptah-Nu'']] and [[70th Blue Lions]] squadron

====SC ''Hela''====
*[[SC Lilith]] class cruiser
*Destroyed by [[FreeSpace_2_Vasudan_Ship_Database#GVCv Khepri|GVCv ''Khepri'']], [[FreeSpace_2_Vasudan_Ship_Database#GVC Heket|GVC ''Heket'']] and [[FreeSpace_2_Terran_Ship_Database#GTC Stalwart|GTC ''Stalwart'']] and [[70th Blue Lions]] squadron in [[Their Finest Hour]] (sm3-08)

====SCv ''Abaddon''====
*[[SCv Moloch]] class corvette
*Attacked [[FreeSpace_2_Terran_Ship_Database#GTD Aquitaine|GTD ''Aquitaine'']] in [[Argonautica]] (sm3-05) as it was retreating to [[Gamma Draconis]] through the [[Nebula System|nebula]]
*Destroyed by [[FreeSpace_2_Terran_Ship_Database#GTD Aquitaine|GTD ''Aquitaine'']] and [[203rd Scorpions]] squadron

====SCv ''Abraxis''====
*[[SCv Moloch]] class corvette
*Attacked [[FreeSpace_2_Vasudan_Ship_Database#GVCv Nebtuu|GVCv ''Nebtuu'']] just before [[Exodus (FS2)|Exodus]] (sm3-06)
*Destroyed [[FreeSpace_2_Vasudan_Ship_Database#GVCv Nebtuu|GVCv ''Nebtuu'']] with help from Shivan small craft
*Destroyed by [[FreeSpace_2_Vasudan_Ship_Database#GVCv Nebtuu|GVCv ''Nebtuu'']] and/or [[70th Blue Lions]] squadron

====SCv ''Balam'' ====
* [[SCv Moloch]] class corvette
* Attacked GTVI convoy in [[Crisis in Capella]]
* Attacked by GTC ''Adamant''
* Destroyed GTC ''Adamant''
* Destroyed by [[GVD Psamtik|GVD ''Psamtik'']]

====SCv ''Chamos''====
*[[SCv Moloch]] class corvette
*Deployed to take control of the [[Epsilon Pegasi]] jump node in [[Capella]] in M-02b
*Destroyed by [[FreeSpace_2_Vasudan_Ship_Database#GVD Zednanreh|GVD ''Zednanreh'']] and two fighter wings

====SCv ''Golab''====
*[[SCv Moloch]] class corvette
*Attacked [[FreeSpace_2_Vasudan_Ship_Database#GVCv Thutmose|GVCv ''Thutmose'']] in [[Speaking in Tongues]] (sm2-09)
*Destroyed by [[FreeSpace_2_Vasudan_Ship_Database#GVCv Thutmose|GVCv ''Thutmose'']] and [[203rd Scorpions]] squadron

====SCv ''Nosferatu''====
*[[SCv Moloch]] class corvette
*Aborted an intended subspace jump from [[Capella]] to [[Gamma Draconis]] due to a hardware failure just before M-01b
*Attacked and destroyed by [[GTVA]] fighter and bomber wings in M-01b
*[[FreeSpace_2_Shivan_Ship_Database#SD Barqu|SD ''Barqu'']] and [[FreeSpace_2_Shivan_Ship_Database#SC Sathariel|SC ''Sathariel'']] were sent to reinforce the position shortly after

====SCv ''Rahab''====
*[[SCv Moloch]] class corvette
*Deployed to take control of the [[Epsilon Pegasi]] jump node in [[Capella]] in M-02b
*Destroyed by [[FreeSpace_2_Vasudan_Ship_Database#GVD Zednanreh|GVD ''Zednanreh'']] and two fighter wings

====SCv ''Sargatanas''====
*[[SCv Moloch]] class corvette
*Attacked [[FreeSpace_2_Terran_Ship_Database#GTCv Bretagne|GTCv ''Bretagne'']] as it was trying to escape from the [[Nebula System|nebula]] in M-06
*Destroyed by [[FreeSpace_2_Terran_Ship_Database#GTCv Bretagne|GTCv ''Bretagne'']] and two fighter wings

====SCv ''Tiamat''====
*[[SCv Moloch]] class corvette
*Attacked [[FreeSpace_2_Terran_Ship_Database#GTD Aquitaine|GTD ''Aquitaine'']] in [[Proving Grounds]] (sm2-03)
*Destroyed by [[FreeSpace_2_Terran_Ship_Database#GTD Aquitaine|GTD ''Aquitaine'']] and [[134th Barracudas]] squadron

====SCv ''Tumael''====
*[[SCv Moloch]] class corvette
*Attempted to reinforce a [[Shivan]] position in [[Gamma Draconis]] when the [[FreeSpace_2_Shivan_Ship_Database#SC Belphegor|SC ''Belphegor'']] was critically damaged in M-05
*Attacked and destroyed by [[FreeSpace_2_Vasudan_Ship_Database#GVCv Pstotle|GVCv ''Pstotle'']] and two wings of the 77th Deadly Sevens squadron

====SD ''Barqu''====
*[[SD Demon]] class destroyer
*Sent in along with the [[FreeSpace_2_Shivan_Ship_Database#SC Sathariel|SC ''Sathariel'']] to reinforce [[Shivan]] positions in [[Gamma Draconis]] after the [[FreeSpace_2_Shivan_Ship_Database#SCv Nosferatu|SCv ''Nosferatu'']] was destroyed in M-01b
*Destroyed by two wings of [[GTVA]] fighters

====SD ''Beleth''====
*[[SD Demon]] class destroyer
*Attempted to follow [[FreeSpace_2_Shivan_Ship_Database#SJ Sathanas 01|SJ ''Sathanas'']] into [[Capella]] in [[Bearbaiting]] (sm3-01)
*Destroyed by [[FreeSpace_2_Vasudan_Ship_Database#GVCv Thebes|GVCv ''Thebes'']] and [[203rd Scorpions]] squadron

====SD ''Beast''====
*[[SD Ravana]] class destroyer
*Attacked [[FreeSpace_2_Terran_Ship_Database#GTVA Colossus|GTVA ''Colossus'']] in [[Capella]] in [[Their Finest Hour]] (sm3-08)
*Destroyed by [[FreeSpace_2_Terran_Ship_Database#GTVA Colossus|GTVA ''Colossus'']]
*The Devil is often called "Beast"

====SD ''Chemosh''====
*[[SD Ravana]] class destroyer
*Deployed to take control of the [[Epsilon Pegasi]] jump node in [[Capella]] in M-02b
*Destroyed by [[FreeSpace_2_Vasudan_Ship_Database#GVD Zednanreh|GVD ''Zednanreh'']] and two fighter wings
*Inflicted moderate damage upon the [[FreeSpace_2_Vasudan_Ship_Database#GVD Zednanreh|GVD ''Zednanreh'']] before going down

====SD ''Nebiros''====
*[[SD Ravana]] class destroyer
*First sighted by a wing of SOC fighters beyond the second [[Knossos]] portal
*Led the attack on [[FreeSpace_2_Terran_Ship_Database#GTI 3rd Fleet HQ|GTI ''3rd Fleet HQ'']] before and during [[Dunkerque]] (sm3-07)

====SD ''Ravana''====
*[[SD Ravana]] class destroyer
*First sighted in [[Nebula System|nebula]] in [[The Great Hunt (FS2)|The Great Hunt]] (sm1-06)
*Destroyed [[FreeSpace_2_Terran_Ship_Database#GTCv Lysander|GTCv ''Lysander'']] and quickly departed
*Destroyed [[FreeSpace_2_Terran_Ship_Database#GTD Delacroix|GTD ''Delacroix'']] between [[The Great Hunt (FS2)|The Great Hunt]] (sm1-06) and [[Slaying Ravana]] (sm1-07)
*Destroyed by [[FreeSpace_2_Vasudan_Ship_Database#GVCv Khenmu|GVCv ''Khenmu'']], [[FreeSpace_2_Terran_Ship_Database#GTCv Yakiba|GTCv ''Yakiba'']], [[FreeSpace_2_Terran_Ship_Database#GTC Heisenberg|GTC ''Heisenberg'']], [[FreeSpace_2_Vasudan_Ship_Database#GVC Somtus|GVC ''Somtus'']] and [[107th Ravens]] squadron in [[Slaying Ravana]] (sm1-07)

====SJ ''Sathanas 01''====
*[[SJ Sathanas]] class juggernaut
*First sighted in the [[Nebula System|nebula]] in [[The Fog of War]] (sm2-07)
*Destroyed [[FreeSpace_2_Vasudan_Ship_Database#GVCv Tatenen|GVCv ''Tatenen'']] and immediately departed
*Sighted again in [[A Monster in the Mist]] (sm2-08)
*Attacked by [[FreeSpace_2_Vasudan_Ship_Database#GVCv Maahes|GVCv ''Maahes'']]
*Subsystems scanned by [[Alpha 1]] from the [[203rd Scorpions]] squadron (player)
*Detected near the jump node to [[Gamma Draconis]] in the [[Nebula System|nebula]] during [[Speaking in Tongues]] (sm2-09)
*Evaded [[GTVA]] destroyers at the [[Gamma Draconis]] jump node*
*Arrived in [[Gamma Draconis]] despite the destruction of the [[Knossos]] portal in [[A Flaming Sword]] (sm2-10)
*Destroyed most of the [[GTVA]] fleet at the [[Capella]] jump node in [[Gamma Draconis]] between [[A Flaming Sword]] (sm2-10) and [[Bearbaiting]] (sm3-01)
*Destroyed or severely damaged [[FreeSpace_2_Terran_Ship_Database#GTD Phoenicia|GTD ''Phoenicia'']] in [[Bearbaiting]] (sm3-01)
*Front beam cannons were disabled by [[203rd Scorpions]] squadron
*Entered the [[Capella]] jump node
*Arrived in [[Capella]] through [[Gamma Draconis]] jump node between [[Bearbaiting]] (sm3-01) and [[High Noon]] (sm3-02)
*Destroyed [[GTVA]] forces at [[Gamma Draconis]] jump node
*Engaged [[FreeSpace_2_Terran_Ship_Database#GTVA Colossus|GTVA ''Colossus'']] in [[Capella]] in [[High Noon]] (sm3-02)
*Destroyed by [[FreeSpace_2_Terran_Ship_Database#GTVA Colossus|GTVA ''Colossus'']]

====SJ ''Sathanas 02''====
*[[SJ Sathanas]] class juggernaut
*Arrived from [[Knossos]] portal in the [[Nebula System|nebula]] in [[Straight, No Chaser]] (sm3-04)
*Destroyed [[FreeSpace_2_Vasudan_Ship_Database#GVD Psamtik|GVD ''Psamtik'']]

====SJ ''Sathanas 03''====
*[[SJ Sathanas]] class juggernaut
*Jumped out in the path of an [[SOC]] wing at the start of [[Into the Lion's Den]] (loop2-2)

====SJ ''Sathanas 04'' - ''09''====
*[[SJ Sathanas]] class juggernauts
*All spotted by an [[SOC]] wing while coming through [[Knossos]] 3 in [[Into the Lion's Den]] (loop2-2)

====SJ ''Sathanas 17''====
*[[SJ Sathanas]] class juggernaut
*Departed from [[Capella]] star and made an intrasystem jump near [[FreeSpace_2_Terran_Ship_Database#GTVA Colossus|GTVA ''Colossus'']] in [[Their Finest Hour]] (sm3-08)
*Destroyed [[FreeSpace_2_Terran_Ship_Database#GTVA Colossus|GTVA ''Colossus'']]
*In Ancient Rome and present-day Italy, the number 17 is linked to bad luck

[[FreeSpace_2_Ship_Database|FreeSpace 2 Ship Database]]
[[Category:Ship]]

Their Finest Hour

2024-08-04T10:34:21Z

Mobius: More trivia on 17

{{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 70th Blue Lions participate in a feint at the Gamma Draconis jump node.

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

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

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.

If Beta wing gets destroyed, the ''Colossus'' will send out Gamma and Delta wing. Gamma comprises four [[GTF Perseus|''Perseus'' interceptor]]s by default, while Delta wing consists of four [[GTB Boanerges|''Boanerges'' bombers]]. If Gamma is destroyed, the ''Colossus'' will deploy Kappa wing, comprising four [[GTF Myrmidon|''Myrmidon'' fighters]]. Should Delta be destroyed, the ''Colossus'' will send out Iota wing, consisting of four ''Boanerges'' bombers.

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 ''Colossus'', however, defies Command's 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; all surviving Alliance fighters and warships will also jump out automatically at this point.

==Objectives==

''(Objectives are viewable by pressing F4 and going to the Objectives tab)''

* Primary Objectives:
** Destroy targets of opportunity *
** <s>Defend allied warships</s>
* Secondary Objectives:
** Neutralize enemy fighters that enter the field of engagement *

* = Not marked as complete by the end of mission

==Notes==
===Allied Warships===
The event that allows the Allied fleet to fire its beam cannons triggers ''before'' the bulk of the fleet arrives. 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. However, modding the mission itself or using cheats to send a support ship to "repair" the ''Colossus'' will cause it to go on its programmed waypoints, but won't save it from the ''Sathanas'' as the latter has a simple ai-chase goal to attack the ''Colossus''.

===SJ ''Sathanas''===
The number that is sometimes associated with the SJ ''Sathanas'' that destroys the GTVA ''Colossus''—17—is taken from events logged by the game's Event Viewer (F4, Events tab). At around the same time the SD ''Beast'' is destroyed, the Event Viewer logs [[SJD Sathanas|SJD ''Sathanas'']] ''17'', one of the many Sathanas juggernauts at the Capella sun, departing. Moments later, an actual ''Sathanas'' juggernaut jumps in near the Colossus and proceeds to destroy it. This ''Sathanas'' is hence occasionally referred to as ''Sathanas 17'', even though it is only named ''Sathanas'' in the player's escort list.

The number 17 chosen by campaign developers for this Sathanas may not be a coincidence. In fact, in Ancient Rome and present-day Italy, 17 as a number is linked to bad luck and superstition (it's the equivalent of 13 for English-speaking countries). The leading explanation for this is that in Roman numbers, 17 is written as XVII, and the anagram of XVII is "VIXI" which literally means "I lived" (I'm now dead). Another common interpretation refers to the universal flood in the Old Testament, which supposedly started on the [https://www.biblegateway.com/passage/?search=Genesis+7%3A11&version=KJV 17th day of the second month]. The fear of the number 17, which is an actual phobia in greco-latin countries, is called [https://en.wikipedia.org/wiki/Heptadecaphobia Heptadecaphobia].

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

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

==Technical information==
{{MissionInfo|SM3-08.fs2|82.0 KB|James Agay|56 (+11 waypoints)|10|48|27|2: Exodus|Brief2}}

==Videos==
===QuantumDelta===
 <videoflash>9ftWQlXi-ao</videoflash> 
===TheOneTrueRenairen===
 <videoflash>zJBDr7G5LxU</videoflash> 

[[Category:Main FreeSpace 2 Campaign]]

Their Finest Hour

2024-08-04T10:12:42Z

Mobius: Some trivia on the number 17

{{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 70th Blue Lions participate in a feint at the Gamma Draconis jump node.

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

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

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.

If Beta wing gets destroyed, the ''Colossus'' will send out Gamma and Delta wing. Gamma comprises four [[GTF Perseus|''Perseus'' interceptor]]s by default, while Delta wing consists of four [[GTB Boanerges|''Boanerges'' bombers]]. If Gamma is destroyed, the ''Colossus'' will deploy Kappa wing, comprising four [[GTF Myrmidon|''Myrmidon'' fighters]]. Should Delta be destroyed, the ''Colossus'' will send out Iota wing, consisting of four ''Boanerges'' bombers.

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 ''Colossus'', however, defies Command's 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; all surviving Alliance fighters and warships will also jump out automatically at this point.

==Objectives==

''(Objectives are viewable by pressing F4 and going to the Objectives tab)''

* Primary Objectives:
** Destroy targets of opportunity *
** <s>Defend allied warships</s>
* Secondary Objectives:
** Neutralize enemy fighters that enter the field of engagement *

* = Not marked as complete by the end of mission

==Notes==
===Allied Warships===
The event that allows the Allied fleet to fire its beam cannons triggers ''before'' the bulk of the fleet arrives. 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. However, modding the mission itself or using cheats to send a support ship to "repair" the ''Colossus'' will cause it to go on its programmed waypoints, but won't save it from the ''Sathanas'' as the latter has a simple ai-chase goal to attack the ''Colossus''.

===SJ ''Sathanas''===
The number that is sometimes associated with the SJ ''Sathanas'' that destroys the GTVA ''Colossus''—17—is taken from events logged by the game's Event Viewer (F4, Events tab). At around the same time the SD ''Beast'' is destroyed, the Event Viewer logs [[SJD Sathanas|SJD ''Sathanas'']] ''17'', one of the many Sathanas juggernauts at the Capella sun, departing. Moments later, an actual ''Sathanas'' juggernaut jumps in near the Colossus and proceeds to destroy it. This ''Sathanas'' is hence occasionally referred to as ''Sathanas 17'', even though it is only named ''Sathanas'' in the player's escort list.

The number 17 chosen by campaign developers for this Sathanas may not be a coincidence. In fact, in Ancient Rome and present-day Italy, 17 as a number is linked to bad luck and superstition (it's the equivalent of 13 for English-speaking countries). The leading explanation for this is that in Roman numbers, 17 is written as XVII. The anagram of XVII is "VIXI", which literally means "I lived" (I'm now dead).

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

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

==Technical information==
{{MissionInfo|SM3-08.fs2|82.0 KB|James Agay|56 (+11 waypoints)|10|48|27|2: Exodus|Brief2}}

==Videos==
===QuantumDelta===
 <videoflash>9ftWQlXi-ao</videoflash> 
===TheOneTrueRenairen===
 <videoflash>zJBDr7G5LxU</videoflash> 

[[Category:Main FreeSpace 2 Campaign]]

Cold Element

2024-08-03T13:18:57Z

Mobius: More general details. It's still a stub that has to be expanded.

'''''Cold Element''''' is the name of the over-arching continuity covering the campaigns ''[[Aftermath (CE)|Aftermath]]'', ''[[Derelict]]'', ''[[Warzone]]'', ''[[Twilight]]'', and ''[[Blackwater Operations]]''.

Aftermath, Derelict, Warzone and Twilight are fully released campaigns, frequently subject to upgrades, bugfixes and improvements by various members of the community. Some of the upgrades included voice acting.

Blackwater Operations remained in a limbo phase for years, up until the unofficial release of a dump pack.

==External Links==
*[http://ce.hard-light.net/ Cold Element website]

{{stub}}

[[Category:Cold Element|*]]
[[Category:User-made Campaigns]]

Cold Element

2024-07-30T08:38:39Z

Mobius:

'''''Cold Element''''' is the name of the over-arching continuity covering the campaigns ''[[Aftermath (CE)|Aftermath]]'', ''[[Derelict]]'', ''[[Warzone]]'', ''[[Twilight]]'', and ''[[Blackwater Operations]]''.

==External Links==
*[http://ce.hard-light.net/ Cold Element website]

{{stub}}

[[Category:Cold Element|*]]
[[Category:User-made Campaigns]]

Ai profiles.tbl

2024-07-29T08:17:05Z

Mobius: Typo

{{SCP_table}}
{{TableVersionGit|2020-10-09|465af93dc}}
{{Tables}}
The '''ai_profiles.tbl''' allows the creation and management of different patterns of AI behavior, called profiles. Profiles consist of various statistics and flags that provide some control over AI behavior. All options within a profile are optional; if an option is not specified it will follow the original FreeSpace 2 retail behavior. Different missions can specify different profiles.

The default ai_profiles.tbl is hardcoded into the FSO executable, and defines the "FS2 RETAIL" AI profile. It's usually recommended not to modify this profile, but to create a new AI profile in a modular table instead, which will then inherit its defaults from the FS2 RETAIL profile.

{{Table232| This table can also be called '''mission_profiles.tbl'''}}

This table is one of the [[Modular Tables]] and can be extended with xxx-aip.tbm
{{Table232| Can also be extended with '''xxx-msp.tbm'''}}

If the version targeted in [[game_settings.tbl]] is equal to or later than these listed, the following options are enabled by default:
{{Table3610|
*'''reset last_hit_target_time for player hits'''}}
{{Table372|
*'''fix ramming stationary targets bug'''}}
{{Table202|
*'''huge turret weapons ignore bombs'''
*'''fix linked primary weapon decision bug'''
*'''prevent turrets targeting too distant bombs'''
*'''fix heat seekers homing on stealth ships bug'''
*'''allow vertical dodge'''
*'''fix ai class bug'''
*'''ai guards specific ship in wing'''
*'''fix ai path order bug'''
*'''aspect bomb invulnerability fix'''
*'''use actual primary range'''
*'''fighters/bombers with no shields can manage ETS'''}}
{{Table214|
*'''fixed ship-weapon collisions'''}}
{{Table220|
*'''fighterbay arrivals use carrier orientation'''
*'''prevent negative turret ammo'''
*'''fix keep-safe-distance'''}}
{{Table224|
*'''fix good-rearm-time bug'''
*'''no continuous turn on attack'''
*'''remove-goal properly removes play-dead order'''}}
{{Table232|
*'''ships playing dead don't manage ETS'''}}
{{Table234|
*'''hud squad messages use tactical disarm/disable'''}}
{{Table242|
*'''debris damage respects 'big damage' flag'''}}

==General Format==
'''#AI Profiles'''

'''$Default Profile:''' ''a profile name''

''Up to 9 different AI profiles''

'''#End'''

==#AI Profiles==
*Indicates to the parser that this is an ai_profiles table file.

===$Default Profile:===
*Defines the profile that each mission will use if no profile is specified in FRED. In addition, this profile will be selected automatically in FRED when you create a new mission. If this line is not specified, the default profile will be '''FS2 Retail''', the FreeSpace 2 retail behavior.

===$Profile Name:===
*The name of the profile, naturally.

----

The following entries accept '''float list''' of five comma-separated values. One value for each of the difficulty levels (Very Easy, Easy, Medium, Hard, Insane).

===$Player Afterburner Recharge Scale:===
{{Table3610|
*Sets the speed of afterburner recharge
*Syntax: '''Float list'''
**Default: 5, 3, 2, 1.5, 1}}

===$Max Beam Friendly Fire Damage:===
{{Table3610|
*Defines the maximum damage inflicted by friendly beam fire
*Syntax: '''Float list'''
**Default: 0, 5, 10, 20, 30}}

===$Player Countermeasure Life Scale:===
{{Table3610|
*Sets the factor applied to player launched countermeasure lifetime
*Syntax: '''Float list'''
**Default: 3, 2, 1.5, 1.25, 1}}

===$AI Countermeasure Firing Chance:===
{{Table3610|
*Defines the chance a countermeasure will be fired by an AI-controlled ship (this is scaled by ai_class)
*Syntax: '''Float list'''
**Default: 0.2, 0.3, 0.5, 0.9, 1.1}}

===$AI In Range Time:===
{{Table3610|
*The delay (in seconds) for the AI to fire its weapons after getting in range.
*Syntax: '''Float list'''
**Default: 2, 1.4, 0.75, 0, -1}}

===$AI Always Links Ammo Weapons:===
{{Table3610|
*AI ships will link ballistic primaries if ammo levels are greater than these percents.
*Syntax: '''Float list'''
**Default: 95, 80, 60, 40, 20}}

===$AI Maybe Links Ammo Weapons:===
{{Table3610|
*Defines the same as '''$AI Always Links Ammo Weapons:''' but in situations when its hull is below 33 % of maximum hitpoints.
*Syntax: '''Float list'''
**Default: 90, 60, 40, 20, 10}}

===$Primary Ammo Burst Multiplier:===
{{Table3611|
*Allows the AI to fire primary weapons in bursts. How long the bursts are (and how much time between them) is a function of ammo remaining, distance to target, angle to target, and this multiplier. A value of 0 turns this feature off (AI fires normally, without bursts). A value < 1 will make for shorter bursts with larger gaps, and a value > 1 will give longer bursts with shorter gaps.
*Syntax: '''Float list'''
**Default: 0, 0, 0, 0, 0}}

===$AI Always Links Energy Weapons:===
{{Table3610|
*AI ships will link energy primaries if energy levels are greater than these percents.
*Syntax: '''Float list'''
**Default: 100, 80, 60, 40, 20}}

===$AI Maybe Links Energy Weapons:===
{{Table3610|
*Defines the same as '''$AI Always Links Energy Weapons:''' but in situations when its hull is below 33 % of maximum hitpoints.
*Syntax: '''Float list'''
**Default: 90, 60, 40, 20, 10}}

===$Max Missiles Locked on Player:===
{{Table3610|
*Defines the maximum number of missiles allowed to be homing in on a player at any given time
*Note: Single-player only, no restriction in multiplayer
*Note: The alternative spelling "Missles" is also accepted for backwards compatibility reasons.
*Syntax: '''Integer list'''
**Default: 2, 3, 4, 7, 99}}

===$Max Player Attackers:===
{{Table3610|
*Sets the maximum number of ships allowed to be attacking the player at any given time
*This number is also checked when a ship checks for a new target, such as using the goal attack-any.
*Syntax: '''Integer list'''
**Default: 2, 3, 4, 5, 99}}

===$Max Incoming Asteroids:===
{{Table3610|
*Sets the maximum number of active (i.e. "thrown") asteroids that can be heading toward a friendly ship at any given time
*Syntax: '''Integer list'''
**Default: 3, 4, 5, 7, 10}}

===$Player Damage Factor: or $AI Damage Reduction to Player Hull:===
{{Table3610|
*Defines the factor applied to damage suffered by the player
*Syntax: '''Float list'''
**Default: 0.25, 0.5, 0.65, 0.85, 1}}

===$Player Subsys Damage Factor: or $AI Damage Reduction to Player Subsys:===
{{Table3610|
*Sets the factor applied to subsystem damage suffered by the player. This is in addition to the '''$Player Damage Factor:'''
*Syntax: '''Float list'''
**Default: 0.2, 0.4, 0.6, 0.8, 1}}

===$Predict Position Delay:===
{{Table3610|
*Sets the time after which the AI will recalculate the position of its target.
*It does not apply to the AI's aim, it only applies to things like avoiding collisions and maneuvering at close range. Generally, anything other than a 0 just allows the AI to do monumentally stupid things like try to turn to avoid ramming where it thought you were 2 seconds ago.
*Syntax: '''Float list''', seconds
**Default: 2, 1.5, 1.333, 0.5, 0}}

===$AI Shield Manage Delay:===
{{Table3610|
*Also '''$AI Shield Manage Delays:'''
*Sets the time in seconds between each instance of an AI ship managing its shields
*Syntax: '''Float list'''
**Default: 5, 4, 2.5, 1.2, 0.1}}

===$Friendly AI Fire Delay Scale:===
{{Table3610|
*Sets the factor applied to "fire wait" for friendly ships
*Syntax: '''Float list'''
**Default: 2, 1.4, 1.25, 1.1, 1}}

===$Hostile AI Fire Delay Scale:===
{{Table3610|
*Sets the factor applied to "fire wait" for hostile ships
*Syntax: '''Float list'''
**Default: 4, 2.5, 1.75, 1.25, 1}}

===$Friendly AI Secondary Fire Delay Scale:===
{{Table3614|
*Sets the factor applied to "fire wait" for friendly ships
*Syntax: '''Float list'''
**Default: 0.4, 0.6, 0.8, 1.0, 1.2}}

===$Hostile AI Secondary Fire Delay Scale:===
{{Table3614|
*Sets the factor applied to "fire wait" for hostile ships
*Syntax: '''Float list'''
**Default: 1.4, 1.2, 1.0, 0.8, 0.6}}

===$AI Turn Time Scale:===
{{Table3610|
*Defines the factor applied to time it takes for enemy ships to turn. A value of 1.0 means the ship turns at normal speed, 2.0 means half speed (takes twice as long), etc. Note that this value ONLY affects ships hostile to the player (always 1.0 for friendly ships).
*Syntax: '''Float list'''
**Default: 3, 2.2, 1.6, 1.3, 1}}

===$Glide Attack Percent:===
{{Table3611|
*How often the AI will use the "glide attack" move when it has the opportunity. Glide attack means using glide to maintain course while aiming and firing at the current target. Only affects ships capable of glide.
*Syntax: '''Float list'''
**Default: 0, 0, 0, 0, 0}}

===$Circle Strafe Percent:===
{{Table3611|
*How often the AI will use the "circle strafe" move when it has the opportunity. Circle strafe means that the ship will attempt "Descent-like" combat, trying to maintain distance while circling around the target using sidethrusters. Ships will only attempt this when sidethrust top speed is at least 2/3 of target's current velocity.
*Syntax: '''Float list'''
**Default: 0, 0, 0, 0, 0}}

===$Glide Strafe Percent:===
{{Table3611|
*How often the AI will use the "glide strafe" move when it has the opportunity. Glide strafe means using glide to attack capships by flying past and shooting at them. Only affects ships capable of glide.
*Syntax: '''Float list'''
**Default: 0, 0, 0, 0, 0}}

===$Random Sidethrust Percent:===
{{Table3611|
*Percentage of the time where AI ships will randomly sidethrust in a dogfight.
*Syntax: '''Float list'''
**Default: 0, 0, 0, 0, 0}}

===$Stalemate Time Threshold:===
{{Table3611|
*The minimum amount of time required for the AI to detect a "stalemate" situation. If a ship and its target have been within a certain distance of each other (defined by ''$Stalemate Distance Threshold'') for this amount of time without either of them scoring a hit on the other, the AI will do something to break the stalemate. Only applies to small ships. If this value is 0 or less, no stalemate detection is performed.
*Syntax: '''Float list'''
**Default: 0, 0, 0, 0, 0}}

===$Stalemate Distance Threshold:===
{{Table3611|
*The maximum distance that an AI ship must remain from its target for a "stalemate" to occur (see ''$Stalemate Time Threshold'').
*Syntax: '''Float list'''
**Default: 0, 0, 0, 0, 0}}

===$Player Shield Recharge Scale:===
{{Table3610|
*Defines the factor applied to the speed at which the player's shields recharge
*Syntax: '''Float list'''
**Default: 4, 2, 1.5, 1.25, 1}}

===$Player Weapon Recharge Scale:===
{{Table3610|
*Defines the factor applied to the speed at which the player's weapons recharge
*Syntax: '''Float list'''
**Default: 10, 4, 2.5, 2, 1.5}}

===$Max Turret Target Ownage:===
{{Table3610|
*Sets the maximum number of turrets on a particular ship allowed to be attacking the same target at any given time
*Syntax: '''Integer list'''
**Default: 3, 4, 7, 12, 19}}

===$Max Turret Player Ownage:===
{{Table3610|
*Sets the maximum number of turrets on a particular ship allowed to be attacking the player at any given time
*Syntax: '''Integer list'''
**Default: 3, 4, 7, 12, 19}}

===$Percentage Required For Kill Scale:===
{{Table3610|
*Sets the minimum percentage of the total assessed damage a player must inflict in order to be awarded a kill (3.6.10 and on)
*Syntax: '''Float list'''
**Default: 0.30, 0.30, 0.30, 0.30, 0.30}}

===$Percentage Required For Assist Scale:===
{{Table3610|
*Sets the minimum percentage of the total assessed damage a player must inflict in order to be awarded an assist (3.6.10 and on)
*Syntax: '''Float list'''
**Default: 0.15, 0.15, 0.15, 0.15, 0.15}}

===$Percentage Awarded For Capship Assist:===
{{Table3610|
*In TvT and Coop missions all teammates will be granted this percentage of the capships score when someone scores a kill (3.6.10 and on)
*Syntax: '''Float list'''
**Default: 0.5, 0.5, 0.5, 0.5, 0.5}}

===$Repair Penalty:===
{{Table3611|
*The amount to subtract from the player's score if they are repaired by a support ship
*Syntax: '''Integer list'''
**Default: 10, 20, 35, 50, 60}}

===$Delay Before Allowing Bombs to Be Shot Down:===
{{Table3611|
*Time after bombs are fired during which the bombs are invulnerable to weapon hits
*Syntax: '''Float list'''
**Default: 1.5, 1.5, 1.5, 1.5, 1.5}}

===$Chance AI Has to Fire Missiles at Player:===
{{Table3611|
* Chance for an AI to hesitate about firing a secondary or homing turret weapon at the player. Values range from 0-6, at 0 they will frequently hesitate, at 6 they will never hesitate.
*Syntax: '''Integer list'''
**Default: 0, 1, 2, 3, 4
* Mechanic details: AIs are only allowed to fire homing secondaries or turrets with homing weapons at the player in a limited window of time. The window starts every ten seconds, and lasts ('''value''' + 1) 7ths of that ten second cycle. Each ship has it's own cycle, so their windows are not all synchronized.
* Example: a value of 1 becomes 2/7ths, so ships can fire homing weapons at the player for roughly 2.85 seconds at a time, then are unable to fire them for 7.15 seconds.
}}

===$Max Aim Update Delay:===
{{Table3611|
*Maximum amount of delay allowed before the AI will update its aim. Until the next update, the AI will project the target forward based on last checked position and velocity. Applies to small ships vs small ships (dogfights). The actual delay is randomly selected between 0 and the maximum (so setting a value of 2 will result in an average of 1 second delay).
*Syntax: '''Float list'''
**Default: 0, 0, 0, 0, 0}}

===$Turret Max Aim Update Delay:===
{{Table3611|
*As $Max Aim Update Delay, but affecting turrets instead
*Syntax: '''Float list'''
**Default: 0, 0, 0, 0, 0}}

===$Player Autoaim FOV:===
{{Table3613|
*Gives the player autoaim within the specified number of degrees from the target (FOV).
*Unlike the ships.tbl settings for autoaim, this only affects the player (and, of course, only if there is a nonzero value for the difficulty level.)
*Syntax: '''Float list'''
**Default: 0, 0, 0, 0, 0}}

===$Detail Distance Multiplier:===
{{Table3613|
*Affects how the "model detail level" setting in Options switches between LOD levels.
*This number acts as a multiplier on the LOD distances specified in ships.tbl.
*NOTE THAT THIS IS PER DETAIL LEVEL, NOT PER DIFFICULTY LEVEL.
*Syntax: '''Float list'''
**Default: 0.125, 0.25, 1.0, 4.0, 8.0}}
----

The following entries are boolean flags. They can be set to ''YES'' or ''NO'', ''TRUE'' or ''FALSE'', ''OUI'' or ''NON'', ''HIja′'' or ''ghobe′'', etc. The default is ''NO''.

===$big ships can attack beam turrets on untargeted ships:===
{{Table3610|
*If set, big ships can attack a beam turret that's firing on them from a ship that they don't currently have targeted.}}

===$smart primary weapon selection:===
{{Table3610|
*If set, enables the new primary weapon selection method}}

===$smart secondary weapon selection:===
{{Table3610|
*If set, enables the new secondary weapon selection method (including proper use of bomber+ missiles)}}

===$smart shield management:===
{{Table3610|
*If set, shields will devote all their charging energy to the weakest quadrant(s) and not waste energy on fully-charged quadrants (previously was -smart_shields on the command line)}}

===$smart afterburner management:===
{{Table3610|
*If set, the AI will properly use brief pulses of afterburner power instead of afterburning until fuel is exhausted}}

===$free afterburner use:===
{{Table382|
*If set, the AI will use afterburners in more situations.}}

===$allow rapid secondary dumbfire:===
{{Table3610|
*If set, allows an AI ship to switch to rapid fire for dumbfire missiles}}

===$huge turret weapons ignore bombs:===
{{Table3610|
*If set, causes huge turret weapons (including anti-capship beams) to not target bombs}}

===$don't insert random turret fire delay:===
{{Table3610|
*If set, removes the random turret fire delay (from .1 to .9 seconds) inserted in addition to AI Fire Delay Scale}}

===$hack improve non-homing swarm turret fire accuracy:===
{{Table3610|
*If set, triggers a hack to improves the accuracy of non-homing swarm missiles by firing them along the turret's last fire direction rather than the direction it currently faces
*Also disables swarm weapons ability to fire only on the 'turrets barrel line'.}}

===$shockwaves damage small ship subsystems:===
{{Table3610|
*If set, shockwaves will cause damage to small ship subsystems (like in FS1)}}

===$navigation subsystem governs warpout capability:===
{{Table3610|
*If set, ships will not be able to warp out if their navigation subsystem is destroyed or low in strength}}

===$check communications for non-player ships:===
{{Table202|
*When set, every ship will have the same communications subsystem restrictions as the player, including minimum strength to send messages and EMP scramble status.
*Off by default.
*Syntax: '''''Boolean'''''}}

===$ignore lower bound for minimum speed of docked ship:===
{{Table3610|
*If set, there will be no lower bound for the speed at which docked ships move (like in FS1).
*When a ship is towing another ship or ships, the towing ship will be slowed down to a degree depending on the total mass of all docked ships. In FS1, the ships could slow down to an arbitrarily slow speed, even a fraction of a m/s above zero. In FS2, there is a lower bound on this behavior so that all ships are guaranteed to move at a minimum docked speed. When set, this flag removes the lower bound and restores FS1 behavior.}}

===$disable linked fire penalty:===
{{Table3610|
*If set, there will be no penalty for linking primaries. Normally, the rate of fire is *1 for a single bank, *0.66 for two banks and *0.5 for three banks (the fire delay is increased according to the formula 1+([nb of banks]-1)*0.5 ).}}

===$disable player secondary doublefire:===
{{Table202|
*If set, players are not allowed to dual-fire their secondaries.}}

===$disable ai secondary doublefire:===
{{Table202|
*If set, AIs are not allowed to dual-fire their secondaries.}}

===$disable weapon damage scaling:===
{{Table3610|
*If set, weapons will do the same damage to a ship regardless of "big damage", "supercap", etc. ship types.}}

===$use additive weapon velocity:===
{{Table3610|
*If set, weapons will inherit their firing ship's velocity. A ship traveling quickly will fire weapons faster than a ship traveling slowly. This also improves the accuracy of weapons fired while gliding.}}

===$use newtonian dampening:===
{{Table3610|
*Newtonian Dampening changes turning and acceleration behavior. By default, there's quite a bit of slide when you turn, and when combined with high damp values (such as in BtRL), you can actually push your speed up beyond the max. Newtonian Dampening is the more realistic turns, where too much turning will lower your speed. Forward momentum is also affected. Backslash can explain it in more detail. [http://www.hard-light.net/forums/index.php/topic,50870.msg1029741.html#msg1029741] }}

===$include beams for kills and assists:===
{{Table3610|
*If set, beam damage is counted when calculating kills and assists.}}

===$score kills based on damage caused:===
{{Table3610|
*If set, kills gain score based on the percentage damage the killer inflicted on the dead ship.}}

===$score assists based on damage caused:===
{{Table3610|
*If set, kills gain score based on the percentage damage the player gaining the assist inflicted on the dead ship.}}

===$allow event and goal scoring in multiplayer:===
{{Table3610|
*If set, players (rather than just their team) can gain score from events in multiplayer.}}

===$fix linked primary weapon decision bug:===
{{Table3610|
*If set, the AI will properly link primaries according to specified percentages of energy levels instead of retail behavior where it mistakenly linked according to absolute energy levels.}}

===$fix ramming stationary targets bug:===
{{Table202|
*When set, AI ships will try not to crash into stationary targets. See [http://scp.indiegames.us/mantis/view.php?id=3147 Mantis #3147].
*Off by default.
*Syntax: '''''Boolean'''''}}

===$prevent turrets targeting too distant bombs:===
{{Table3610|
*If set, prevents turrets from targeting bombs beyond maximum range of the weapons of the turret.}}

===$smart subsystem targeting for turrets:===
{{Table3610|
*If set, prevents turrets from trying to target subsystems beyond their fov limits, also keeps the turret subsystem targeting preference order intact regardless of the angle to the target.}}

===$fix heat seekers homing on stealth ships bug:===
{{Table3610|
*If set, heat-seeking missiles will not home in on stealth ships (this mirrors the established behavior where heat-seeking missiles do not home in on ships that are hidden from sensors).}}

===$multi allow empty primaries:===
{{Table3610|
*If set, allows a player to commit into a multiplayer game without primaries.}}

===$multi allow empty secondaries:===
{{Table3610|
*If set, allows a player to commit into a multiplayer game without secondaries.}}

===$allow turrets target weapons freely:===
{{Table3611|
*If set, allows turrets to target any weapons instead of just targeting bombs, to be used in conjunction with target priorities setup.}}

===$use only single fov for turrets:===
{{Table3611|
*If set, allows turrets to fire outside some hardcoded FOV set for certain missile types limits, and rely only on the user defined FOV.}}

===$allow vertical dodge:===
{{Table3611|
*If set, allows ships to dodge weapons fire vertically as well as horizontally.}}

===$force beam turrets to use normal fov:===
{{Table3611|
*If set makes beam turrets use same FOV rules as other weapons do. Prevents beam from a turret from following the target beyond the turret's FOV}}

===$fix AI class bug:===
{{Table3611|
*Fixes a bug where AI class attributes are not set properly on ships if the AI class is set in the mission to something other than the default for the ship type. Set this to YES if you want attributes in [[Ai.tbl]] to mean anything at all.}}

===$turrets ignore targets radius in range checks:===
{{Table3611|
*TBD.}}

===$no extra collision avoidance vs player:===
{{Table3611|
*Disables the extra collision avoidance that AI normally uses against the player. Makes the AI more aggressive vs the player at close range (same treatment as vs other AI), although ship-ship collisions are slightly more likely.}}

===$perform fewer checks for death screams:===
{{Table3614|
*If set, ships that are on different teams and ships that are outside the player's squadron will be allowed to send death screams. Additionally, the game will no longer cap a maximum number of screams per mission. (This flag originated as a customization of message behavior for the Wing Commander Saga mod.)
Prior to revision 9119, this was "$perform less checks for death screams:", but the old version will still parse correctly.}}

===$advanced turret fov edge checks:===
{{Table3614|
*Forces all turrets to use [[Subsystem#.22fov_edge_checks.22|"fov edge checks"]].}}

===$require turrets to have target in fov:===
{{Table3614|
*Forces all turrets to use [[Subsystem#.22target_requires_fov.22|"target requires fov"]].}}

===$all ships manage shields:===
{{Table3613|
*Allows AI to manage shields on big ships}}

===$ai aims from ship center:===
{{Table3613|
*AI aims weapons using the center of the ship instead of the first gunpoint. If a convergence offset is specified for this ship in ships.tbl, AI aims using that as a reference point.}}

===$allow primary link at mission start:===
{{Table37|
*Normally, no ships will link primaries for the first 30 seconds of a mission. In addition, ships will randomly not link for the first two minutes of a mission. Set this flag to YES to get rid of this often-problematic retail behavior. (Prior to revision 9119, this was called $allow primary link delay and defaulted to YES; to get rid of retail behavior you would specify NO. The old method is still supported for compatibility.)}}

===$allow beams to damage bombs:===
{{Table3613|
* Default: NO.
* When no, when any secondary encounters any beam it is instantly destroyed regardless of if it is marked as interceptable, has a health value, or any other circumstance that would normally apply to interception by other weapons.
* When true, damage and health values are respected in these circumstances. Secondaries without hitpoints are still destroyed, however.
}}

===$disable weapon damage scaling for player:===
{{Table3613|
*When set, Player weapon damage will no longer be scaled down when firing a non-huge primary against a ship with the "big damage" flag. Use with caution, as this may severely impact mission balance.}}

===$countermeasures affect aspect seekers:===
{{Table3613|
*By default, an aspect seeker that's been decoyed by a CM just flies straight forward, while a heatseeker in the same position will actively home in on the CM. This flag makes aspect seekers match heatseeker behavior in this regard.}}

===$ai guards specific ship in wing:===
{{Table3615|
*If ordered to guard a ship in a wing (of which it is not a member), the AI will guard that specific ship instead of the entire wing (resulting in guarding the wing leader).}}

===$support don't add primaries:===
{{Table382|
*When set, the support ship will not equip a new primary weapon into an empty bank.
*Off by default.
*Syntax: '''''Boolean'''''}}

===$fighterbay arrivals use carrier orientation:===
{{Table220|
*Causes all ships arriving via a ship's fighterbay to attempt to align their right vector with their carrier's right vector as they exit.
*Syntax: '''''Boolean'''''}}

===$fighterbay departures use carrier orientation:===
{{Table220|
*Causes all ships departing via a ship's fighterbay to attempt to align their right vector with their carrier's right vector as they enter.
*Syntax: '''''Boolean'''''}}

===$debris damage respects 'big damage' flag:===
{{Table242|
*Causes damage inflicted by debris to be limited by the 'big damage' flag in the same way as damage inflicted by weapons.
*Syntax: '''''Boolean'''''}}

===$don't limit change in speed due to physics whack:===
{{Table242|
*With this flag, the speed change due to physics whacks (collision, shockwave, etc.) is unlimited. Without this flag, the speed change will be capped at 440 m/s if it exceeds 500 m/s.
*Syntax: '''''Boolean'''''}}

===$ai path mode:===
{{Table3613|
*Possible options are "normal" and "alt1". The alt1 mode differs from the normal behaviour in the following ways:
**1. No path shortcutting. Normal pathing AI will skip forward along a path to the furthest point it can reach. This is sometimes desirable, but makes it a lot harder to predict how the AI is going to behave at various points along a path. Turning this off also allows us to force the AI to straighten out, by giving it several waypoints in a more-or-less straight line. This is useful for such things as lining up a landing.
**2. No sliding when following paths. Docking still works, but there is some code that causes the AI to lose its mind if it just misses a point: it turns towards the point in big, looping circles. This is apparently caused by passing a slide_vec value into ai_turn_towards_vector, which doesn't even seem to do what you'd expect it to do. Passing a null value instead turns off the stupid. (The behavior is fixed in alt1).
**3. Momentum taken into account when following paths. Path points will trigger sooner, proportional to the ship's speed and momentum. This prevents the AI from massively overshooting a waypoint, especially with high-damp ships.
**4. AI tries to follow the line between waypoints. Instead of just pointing at the next waypoint, the AI will fly a bit towards the line. This helps keep the AI actually on the path it claims to be following. See picture:[[Image:Altpaths.png]]
Blue is what happens with regular pathing. Red is the modified pathing: as you can see, it actively moves back towards the line.
**5. AI will respect "cap-waypoint-speed" when following paths (such as when docking or departing via bay).}}

===$default weapon select effect:===
{{Table3613|
*This specifies which effect to use for weapon select animations when no .ani can be found, or the -weapon_choice_3d commandline flag is active. This will default to the FS2 effect.
*Possible options are "FS1" and "off"}}
{{Table3615|
*This flag has been moved to [[Game_settings.tbl]]}}

===$default ship select effect:===
{{Table3613|
*This specifies which effect to use for ship select animations when no .ani can be found, or the -ship_choice_3d commandline flag is active. This will default to the FS2 effect.
*Possible options are "FS1" and "off"}}
{{Table3615|
*This flag has been moved to [[Game_settings.tbl]]}}

===$no warp camera:===
{{Table3615|
*When set, prevents the view from switching to the external camera when the player warps out.
*Note: this flag is deprecated and may get moved to another table without further notice.}}

===$fix ai path order bug:===
{{Table3615|
*When set, ship will follow its own waypoint path unless the wingleader has the same waypoint path and order.
*Off by default.
*Syntax: '''''Boolean'''''}}

===$strict turret-tagged-only targeting:===
{{Table372|
*When set, newer turret-tagged-only behavior will be enabled. See [http://scp.indiegames.us/mantis/view.php?id=3114 Mantis #3114].
*Off by default.
*Syntax: '''''Boolean'''''}}

===$aspect bomb invulnerability fix:===
{{Table373|
*When set, the code that makes bombs invulnerable for the first 1.5 seconds of life will use the correct lifetime calculation for aspect bombs. Without this fix, the invulnerability time will be extended by 20% of the total lifetime of the bomb.
*Off by default.
*Syntax: '''''Boolean'''''}}

===$glide decay requires thrust:===
{{Table373|
*When set, gliding ships will maintain their current speed without decay as long as they aren't actively thrusting.
*Off by default.
*Syntax: '''''Boolean'''''}}

===$ai can slow down when attacking big ships:===
{{Table38|
*When set, fighters attacking big ships will slow down depending on how long they've been attacking (80% speed after 5 seconds, 60% after 8 seconds, 40% after 10 seconds, and 20% after 15 seconds), how long it's been since they were last shot (full throttle if it was within the past 6 seconds), and how close they are (full throttle if the target is more than 1200 meters away).
*Off by default.
*Syntax: '''''Boolean'''''}}

===$use actual primary range:===
{{Table382|
*When set, fighters will no longer fire primary weapons at targets outside their range just because weapon travel time would be sufficiently short.
*Off by default.
*Syntax: '''''Boolean'''''}}

===$override radius for subsystem path points:===
{{Table202|
*When set, this value overrides the default distance for determining if a ship had reached a point in a model subsystem path. Useful to allow ships with high damp values to navigate subsystem paths when attacking a subsystem. Must be greater than or equal to 1. If '''''$use POF radius for subsystem path points:''''' is set than this override value will only be used if the point in the subsystem path is less than 1 or invalid.
*5 by default.
*Syntax: '''''Integer'''''}}

===$use POF radius for subsystem path points:===
{{Table202|
*When set, the distance for determining if a ship had reached a point in a model subsystem path will be the radius of that path point, not the default distance of 5.
*Off by default. If this is set to YES and ''''''$override radius for subsystem path points:''''' is set to greater than or equal to 1, then the path point radius will be used. If the path point radius cannot be found or is less than 1 then override radius will be used if it is set to greater than or equal to 1.
*Syntax: '''''Boolean'''''}}

===$bay arrive speed multiplier:===
{{Table373|
*Causes all AI ships arriving from fighterbays (following a fighterbay path) to gradually accelerate, instead of immediately attempting to attain maximum speed. This can be used to prevent fighters from overshooting the fighterbay paths. The initial target speed is the maximum speed multiplied by the given value, with the multiplier gradually approaching 1.0 as the distance to the end of the path decreases.
**Syntax: '''''Float''''' (defaults to 1.0)
{{Note|Will be overridden by path-specific multipliers, see [[Ships.tbl#.2Barrive_speed_multiplier:]].}}
}}

===$bay depart speed multiplier:===
{{Table373|
*Same as above, except for departures into fighterbays. The initial target speed is the maximum speed, with the target speed gradually approaching maximum speed multiplied by the given value as the distance to the fighterbay decreases.
**Syntax: '''''Float''''' (defaults to 1.0)
{{Note|Will be overridden by path-specific multipliers, see [[Ships.tbl#.2Bdepart_speed_multiplier:]].}}
}}

===$lead indicator second-order prediction factor:===
{{Table202|
*This is a 0 to 1 multiplier of a factor to adjust the lead indicator to take into account a ship's rotational velocity as well as its velocity. This will directly affect autoaim, making it more accurate for turning enemies.
*This ''will'' make the lead indicator slightly jitterier in general, and does not properly take into account gliding. It is recommended to adjust the value to fit your situation.
**Syntax: '''''Float''''' (defaults to 0.0)}}

===$no directional bias for missile and ship turning:===
{{Table202|
*When enabled, this will cause ships and missiles to take direct turning paths to point at their target. This does not directly affect their turning time, but in many situations will result in more efficient paths and a better time-to-target.
*Syntax: '''''Boolean'''''}}

===$respect ship axial turnrate differences:===
{{Table202|
*Normally AI ships will use the average of their pitch and heading turn times for their turn time on all axes. If this is enabled the ship will actually use the tabled values for each axis.
*'''''NOTE''''':The AI will '''''NOT''''' take this into account when turning, it will always turn directly towards its target, even if it could bank and use a faster axis instead. Use this flag carefully, and make sure that their your ships have exactly the turn times you want for each axis.
*Syntax: '''''Boolean'''''}}

===$any ship with no shields can manage ETS:===
{{Table202|
*Normally AI ships will not manage ETS if they do not have shields set to be on. When enabled, this flag allows the AI on any ship to manage ETS for weapons and engines even if they do not have shields set to on. Do note that in Vanilla FS2, some capital ships can go much faster with this enabled.
*Syntax: '''''Boolean'''''}}

===$fighters/bombers with no shields can manage ETS:===
{{Table202|
*Normally AI ships will not manage ETS if they do not have shields set to be on. When enabled, this flag allows the AI on fighters and bombers to manage ETS for weapons and engines even if they do have shields set to on.
*Syntax: '''''Boolean'''''}}

===$ships playing dead don't manage ETS:===
{{Table232|
*Prevents ships from managing their ETS is they are currently playing dead. Managing ETS could lead to unexpected speed changes in ship-maneuver.
*Syntax: '''''Boolean'''''}}

===$better combat collision avoidance for fightercraft:===
{{Table202|
*If set will cause small ships to be much better at avoiding colliding with large ships while fighting, and will not spend as long recovering from a collision if one does occur.
*Syntax: '''''Boolean'''''}}

===$firing requires exact los:===
{{Table202|
*If set will cause turrets and AI weapons to only fire if they have a clear line of sight from their firing point to their target's ship's center.
*Syntax: '''''Boolean'''''}}

===$improved missile avoidance for fightercraft:===
{{Table212|
*Fighters/bombers will be much more effective at dodging missiles in general. Of note is that AI do not normally care about countermeasure effect range before dropping them (only distance less than 200m), with this flag, they will only drop them if within countermeasure range.
*Syntax: '''''Boolean'''''}}

===$friendly ships use AI profile countermeasure chance:===
{{Table212|
*Specifies Friendly ships to use their specific AI class profile countermeasure firing chance. By default Friendly ships always use the second value in '''$AI Countermeasure Firing Chance:''' from default AI profile.
*Syntax: '''''Boolean'''''}}

===$improved subsystem attack pathing:===
{{Table212|
*Fightercraft will use a somewhat more efficient and faster subsystem attack pathing method.
*Notably, this method ''does not'' use the path system. Using this flag, aside from docking and fighter bay paths, ''all other'' paths will be ignored and are no longer necessary.
*Syntax: '''''Boolean'''''}}

===$fixed ship-weapon collisions:===
{{Table214|
*Fixes an error in ship-weapon collisions which would occasionally cause them to not trigger when they should.
*Most obvious when projectiles would erroneously bypass a full shield quadrant and damage the hull.
*Syntax: '''''Boolean'''''}}

===$AI secondary range awareness:===
{{Table214|
*Controls if the AI considers weapon range at all when selecting a secondary weapon to attempt to use. Currently available options are:
*'RETAIL': The default. After performing filtering logic based on the target types and weapon flags, the AI will select the first valid secondary bank as its active one, regardless of range.
*'AWARE': As retail, except that if a weapon is out of range it the AI will keep looking down the list to see if it has a weapon that is in range, and use that instead if it does. All other weapon selection and restriction logic still applies.}}

===$no shield damage from ship collisions:===
{{Table214|
*Normally, the heavier ship in a collision will receive shield damage from the collision if it has one.
*This disables that, and causes all involved ships to only take hull damage.
*Syntax: '''''Boolean'''''}}

===$turret target recheck time:===
{{Table220|
*Defines the amount of time between target recalculation for turrets.
*Affects turret reaction time in all scenarios, acquiring a target from idle, re-affirming the current target, switching to a new target or even a new subsystem on the same target.
*Be aware setting this value too low can have an extreme performance impact. It is recommended to not set this below 30 ms.
*Syntax: '''''Float''''', milliseconds
*Default: 2000}}

===$prevent negative turret ammo:===
{{Table220|
*By default, turrets with ammo would end up firing one extra shot, resulting in a -1 ammo. This flag corrects that behavior, so the ammo count is properly used.
*Syntax: '''''Boolean'''''}}

===$fix keep-safe-distance:===
{{Table220|
*Allows any ship flying the keep-safe-distance behavior to turn toward its goal point. Without this flag, ships will fly into the distance in a straight line.
*Syntax: '''''Boolean'''''}}

===$AI ignores aspect lock for leading:===
{{Table222|
*When off, AI fighters follows retail behavior of aiming directly at a target when using aspect lock missiles. When on AIs ignore this consideration and always lead their targets when attempting to aim at them.
*Syntax: '''''Boolean'''''
*Default: on}}

===$fix good-rearm-time bug:===
{{Table224|
*Causes the "good rearm time" SEXP to correctly expire (revert to being a "bad rearm time") at the end of the specified time.
*Syntax: '''''Boolean'''''}}

===$no continuous turn on attack:===
{{Table224|
*Prevents an AI behavior where fighters/bombers will spin around for a second or two when they acquire a target.
*Syntax: '''''Boolean'''''}}

===$remove-goal properly removes play-dead order:===
{{Table224|
*Causes remove-goal to take the ship out of the play-dead AI mode when removing the play-dead goal.
*Syntax: '''''Boolean'''''}}

===$bay arrivals not time limited:===
{{Table224|
*Causes AI to always complete a bay arrival path, even if it takes longer than 10 seconds.
*Syntax: '''''Boolean'''''}}

===$use adjusted AI class autoscale:===
{{Table224|
*Causes autoscaled AI classes to scale only based on the collection of autoscaled AI classes, not all AI classes. This prevents autoscaled calculations from being skewed by the presence of non-autoscaled classes in the list.
*Syntax: '''''Boolean'''''}}

===$carry shield difficulty scaling bug:===
{{Table232|
*Enables an erroneous behavior where player damage difficulty scaling is applied twice to damage from area blasts and shockwaves, greatly changing the effective difficulty scaling. This is a ''bug'' that should not be enabled, unless the mod was balanced during the time between 3.6.14 and 23.1 (mods [[Game_settings.tbl#.24Target_Version:|targeting within those versions]] automatically have this flag enabled).
*Syntax: '''''Boolean'''''}}

===$debris affected by physics whacks:===
{{Table232|
*Allows debris to be affected by physics whacks from weapons.
*Syntax: '''''Boolean'''''}}

===$asteroids affected by physics whacks:===
{{Table232|
*Allows asteroids to be affected by physics whacks from weapons.
*Syntax: '''''Boolean'''''}}

===$dynamic goals afterburn hard:===
{{Table232|
*Will cause all dynamic goals (such as a fighter defending itself, or a fighter chasing an attacker as part of a guard order) to 'afterburn hard' as the optional argument on ai-goals do.
*Syntax: '''''Boolean'''''}}

===$player orders afterburn hard:===
{{Table242|
*Will cause all player orders to 'afterburn hard' as the optional argument on ai-goals do.
*Syntax: '''''Boolean'''''}}

===$hud squad messages use tactical disarm/disable:===
{{Table234|
*Will cause disarm or disable orders issued by the hud squadmsg menu (i.e. player orders) to be 'tactical' goals that do not cause the target to be protected from attack.
*Syntax: '''''Boolean'''''}}

===$align to target when guarding stationary ship:===
{{Table242|
*Will cause ships to match the target's orientation when following a guard order, rather than facing directly away from the target which is the normal behavior.
*Syntax: '''''Boolean'''''}}

===$rotation factor multiplier for player collisions:===
{{Table242|
*Allows modders to have players experience rotational effects from collisions. This value is multiplied by the value of [https://wiki.hard-light.net/index.php/Ships.tbl#.2BRotation_Factor: $Collision Physics: +Rotation Factor:] in the ships table (which is specified for the ship class).
**Syntax: '''''Float''''' (defaults to 0.0)}}

==Sample Entry==
*Retail FS2 behaviour

<pre>
#AI Profiles

$Default Profile: FS2 RETAIL

$Profile Name: FS2 RETAIL

$Player Afterburner Recharge Scale: 5, 3, 2, 1.5, 1
$Max Beam Friendly Fire Damage: 0, 5, 10, 20, 30
$Player Countermeasure Life Scale: 3, 2, 1.5, 1.25, 1
$AI Countermeasure Firing Chance: 0.2, 0.3, 0.5, 0.9, 1.1
$AI In Range Time: 2, 1.4, 0.75, 0, -1
$AI Always Links Ammo Weapons: 95, 80, 60, 40, 20
$AI Maybe Links Ammo Weapons: 90, 60, 40, 20, 10
$Primary Ammo Burst Multiplier: 0, 0, 0, 0, 0
$AI Always Links Energy Weapons: 100, 80, 60, 40, 20
$AI Maybe Links Energy Weapons: 90, 60, 40, 20, 10
$Max Missiles Locked on Player: 2, 3, 4, 7, 99
$Max Player Attackers: 2, 3, 4, 5, 99
$Max Incoming Asteroids: 3, 4, 5, 7, 10
$Player Damage Factor: 0.25, 0.5, 0.65, 0.85, 1
$Player Subsys Damage Factor: 0.2, 0.4, 0.6, 0.8, 1
$Predict Position Delay: 2, 1.5, 1.333,0.5, 0
$AI Shield Manage Delay: 5, 4, 2.5, 1.2, 0.1
$Friendly AI Fire Delay Scale: 2, 1.4, 1.25, 1.1, 1
$Hostile AI Fire Delay Scale: 4, 2.5, 1.75, 1.25, 1
$Friendly AI Secondary Fire Delay Scale: 0.4, 0.6, 0.8, 1.0, 1.2
$Hostile AI Secondary Fire Delay Scale: 1.4, 1.2, 1.0, 0.8, 0.6
$AI Turn Time Scale: 3, 2.2, 1.6, 1.3, 1
$Glide Attack Percent: 0, 0, 0, 0, 0
$Circle Strafe Percent: 0, 0, 0, 0, 0
$Glide Strafe Percent: 0, 0, 0, 0, 0
$Random Sidethrust Percent: 0, 0, 0, 0, 0
$Stalemate Time Threshold: 0, 0, 0, 0, 0
$Stalemate Distance Threshold: 0, 0, 0, 0, 0
$Player Shield Recharge Scale: 4, 2, 1.5, 1.25, 1
$Player Weapon Recharge Scale: 10, 4, 2.5, 2, 1.5
$Max Turret Target Ownage: 3, 4, 7, 12, 19
$Max Turret Player Ownage: 3, 4, 7, 12, 19
$Percentage Required For Kill Scale: 0.30, 0.30, 0.30, 0.30, 0.30
$Percentage Required For Assist Scale: 0.15, 0.15, 0.15, 0.15, 0.15
$Percentage Awarded For Capship Assist: 0.1, 0.2, 0.35, 0.5, 0.6
$Repair Penalty: 10, 20, 35, 50, 60
$Delay Before Allowing Bombs to Be Shot Down: 1.5, 1.5, 1.5, 1.5, 1.5
$Chance AI Has to Fire Missiles at Player: 0, 1, 2, 3, 4
$Max Aim Update Delay: 0, 0, 0, 0, 0
$Turret Max Aim Update Delay: 0, 0, 0, 0, 0
$Player Autoaim FOV: 0, 0, 0, 0, 0
$Detail Distance Multiplier: 0.125,0.25, 1.0, 4.0, 8.0

$big ships can attack beam turrets on untargeted ships: NO
$smart primary weapon selection: NO
$smart secondary weapon selection: NO
$smart shield management: NO
$smart afterburner management: NO
$allow rapid secondary dumbfire: NO
$huge turret weapons ignore bombs: NO
$don't insert random turret fire delay: NO
$hack improve non-homing swarm turret fire accuracy: NO
$shockwaves damage small ship subsystems: NO
$navigation subsystem governs warpout capability: NO
$ignore lower bound for minimum speed of docked ship: NO
$disable linked fire penalty: NO
$disable weapon damage scaling: NO
$use additive weapon velocity: NO
$use newtonian dampening: NO
$include beams for kills and assists: NO
$score kills based on damage caused: NO
$score assists based on damage caused: NO
$allow event and goal scoring in multiplayer: NO
$fix linked primary weapon decision bug: NO
$prevent turrets targeting too distant bombs: NO
$smart subsystem targeting for turrets: NO
$fix heat seekers homing on stealth ships bug: NO
$multi allow empty primaries: NO
$multi allow empty secondaries: NO
$allow turrets target weapons freely: NO
$use only single fov for turrets: NO
$allow vertical dodge: NO
$force beam turrets to use normal fov: NO
$fix AI class bug: NO
$turrets ignore targets radius in range checks: NO
$no extra collision avoidance vs player: NO
$perform fewer checks for death screams: NO
$advanced turret fov edge checks: NO
$require turrets to have target in fov: NO
$all ships manage shields: NO
$ai aims from ship center: NO
$allow primary link at mission start: NO
$allow beams to damage bombs: NO
$disable weapon damage scaling for player: NO
$countermeasures affect aspect seekers: NO
$ai path mode: normal
$no warp camera: NO

#End
</pre>

== References ==
# "[http://www.hard-light.net/forums/index.php/topic,50870.msg1029741.html#msg1029741 Re: New difficulty? - Feature request!]", ''Hard Light Productions Forums'', Hard Light Productions, 2007-12-15. Retrieved on [[December_27]], [[2007]].

[[Category:Tables]]

List of Sol jump node devices

2024-07-28T10:36:23Z

Mobius: Created page with "{{non-canon}} The reverse engineering of the Knossos portal, manufactured by the Ancients, is implied at the end of FreeSpace 2. A broad reference to the capacity..."

{{non-canon}}

The reverse engineering of the [[Knossos]] portal, manufactured by the [[Ancients]], is implied at the end of [[FreeSpace 2]]. A broad reference to the capacity to restore collapsed [[jump node|jump nodes]] is also present in [[FS1]]. Therefore, the concept of devices and installations capable of reopening the [[Sol]] jump node in [[Delta Serpentis]] after the [[Capella]] crisis has sparked many ideas among FS fans and campaign developers. The Sol-DS node [[Great War|collapsed on March 29th, 2335]], following the destruction of the [[SD Lucifer|SD ''Lucifer'']].

Several fan-made devices/installations have been designed and released, all fulfilling the exact same purpose. Please note that, due to the specific setting of each fan-made campaign, the dates of reopening may not be clearly specified, or differ substantially. The size of these devices also varies considerably between campaigns. References to such assets are hereby listed by order of release of their respective campaign(s):

[[Inferno]]
*[[GTI Melia|GTI ''Melia'']] ([[INFR1]]). Also known as Sol Gate. Node restored in circa June 2400.
*[[GTI Ishtar|GTI ''Ishtar'']] ([[Inferno Nostos|Nostos]]). Also known as Sol Gate. Node restored on March 30th, 2399, one day after the anniversary of its destruction.

[[Blue Planet]]
*[[Alliance Jump Gate]]. Node restored in TBFIL.

[[Cold Element]]
*[[GTI Charon|GTI ''Charon'']]. Node restored in TBFIL.

[[Category: User-made Ships]]

Alliance Jump Gate

2024-07-28T10:33:29Z

Mobius: Genering initial description

{{User-made Ships|''Alliance '''Jumpgate'''''}}

This device, lacking a proper name, is one of the many fan-made installations serving the purpose of [[List of Sol jump node devices|restoring Sol's jump node]] in [[Delta Serpentis]]. It became popular among fans after its use in the first [[Blue Planet]] campaign, [[Age of Aquarius]].

{{shipimage|image=[[Image:alliancejumpgate.jpg]]|caption=Alliance Jumpgate}}

==Description:==

===Tech Room Description===
The prototype Jump Gate using Knossos technology connects Delta Serpentis to Sol along the severed jump node. Requiring eight years of planning and a decade to build, the Sol Jump Gate is the largest project undertaken by the GTVA since the Colossus project.

===Credits===
*Model by '''Trashman'''

==Performance:==
===Statistics===
{|
|-
| style="width:200px" | '''[[Technical_Terms_and_Definitions#Type|Type]]'''
| style="width:200px" | Knossos
|-
| '''[[Technical_Terms_and_Definitions#Manufacturer|Manufacturer]]'''
| Unknown
|-
| '''[[Technical_Terms_and_Definitions#Maneuverablity|Maneuverability]]'''
| N/A
|-
| '''[[Technical_Terms_and_Definitions#Max Velocity|Max Velocity]]'''
| N/A
|-
| '''[[Technical_Terms_and_Definitions#Max Afterburner Velocity|Max Afterburner Velocity]]'''
| N/A
|-
| '''[[Technical_Terms_and_Definitions#Armor|Armor]]'''
| N/A
|-
| [[Technical_Terms_and_Definitions#Hitpoints|Hitpoints]]
| 1 000 000
|-
| [[Technical_Terms_and_Definitions#Shields|Shields]]
| N/A
|-
| '''[[Technical_Terms_and_Definitions#Width|Width]]'''
| 6717 m
|-
| '''[[Technical_Terms_and_Definitions#Height|Height]]'''
| 5616 m
|-
| '''[[Technical_Terms_and_Definitions#Length|Length]]'''
| 1948 m
|}

===Armaments===

*'''[[Technical_Terms_and_Definitions#Turrets|Turrets]]'''
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=2 style="background:#351515;"| '''Default Statistics'''
|- align="center"
| style="width:120px" |Turret Type
| style="width:60px" |Amount
|- align="center"
| [[AAAf]]
| 2
|- align="center"
| [[Standard Flak]]
| 5
|- align="center"
| [[Terran Turret]]
| 15
|}

===Veteran Comments===
{{comment|}}

==Download link:==
*Blue Planet: AoA: http://www.freespacemods.net/download.php?view.42
*http://www.freespacemods.net/download.php?view.270

[[Category:Installation]]

GTI Melia

2024-07-28T10:31:02Z

Mobius:

{{Inferno_Ships}}

[[Image:Ishtar.jpg|thumb|right|650px|The GTI Ishtar in Nostos]]
[[Image:Gtimelia.jpg|thumb|right|600px|The GTI Melia in INFR1]]

The ''Ishtar'' is the massive installation featured in [[Inferno: Nostos]] that enabled the [[GTVA]] to [[List of Sol jump node devices|reopen]] the [[Sol]] lump node in [[Delta Serpentis]]. Also known as Sol Gate, its designation in the original [[INFR1]] campaign was GTI ''Melia''.

==Description:==

===Inferno R1 Description===
More famously known as the Sol Gate, the Melia connects Delta Serpentis to the Sol system by stabilising the collapsed jump node to the extent that all Allied ships can once again travel back to the birthplace of humanity. The Earth Alliance stormed the huge structure shortly after the first GTVA ships passed through the revitalised node.

===Inferno: Nostos Description===
More famously known as the Sol Gate, the massive Ishtar installation connects Delta Serpentis to the Sol system by stabilising the collapsed jump node to the extent that all Allied ships can once again travel back to the birthplace of humanity. The events of the Great War also prompted the Ishtar's designers to heavily arm the Gate with a multitude of heavy weapons, allowing it to destroy virtually any hostile capital ship trying to get into (or out of) Sol. The Earth Alliance stormed the huge structure in a surprise attack shortly after the first GTVA diplomatic envoy ships passed through the revitalised node, and has held the station ever since.

===Credits===
*HTL model from Nostos by '''BrotherBryon'''
*Textures and turrets by '''Nyctaeus'''

==Performance:==
===Statistics===
*'''Nostos'''
{|
|-
| style="width:200px" | '''[[Technical_Terms_and_Definitions#Width|Width]]'''
| style="width:200px" | 22463 m
|-
| '''[[Technical_Terms_and_Definitions#Height|Height]]'''
| 133324 m
|-
| '''[[Technical_Terms_and_Definitions#Length|Length]]'''
| 9150 m
|-
| '''[[Technical_Terms_and_Definitions#Turrets|Turrets]]'''
| 190
|-
| '''Fighterbays'''
| 2
|}

===Armaments===

*'''Nostos'''
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=2 style="background:#351515;"| '''Default Statistics'''
|- align="center"
| style="width:120px" |Turret Type
| style="width:60px" |Amount
|- align="center"
| T-AF-Clus-A
| 27
|- align="center"
| T-AF-Mis-B
| 27
|- align="center"
| T-RL-Type-2
| 37
|- align="center"
| T-B-AAA
| 8
|- align="center"
| T-AW-Plas-LR-A
| 43
|- align="center"
| T-B-Huge
| 22
|- align="center"
| T-AF-Flak-B
| 26
|}

*'''INFR1'''
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=2 style="background:#351515;"| '''Inferno R1'''
|- align="center"
| style="width:120px" |Turret Type
| style="width:60px" |Amount
|- align="center"
| BFBlue
| 7
|- align="center"
| HBlue
| 15
|- align="center"
| GTVA Rapid Laser
| 22
|}

==Veteran Comments==
{{comment|}}

==External links:==
*[https://www.hard-light.net/forums/index.php?topic=94800.0 Inferno Nostos: Act 1 release thread]

[[Category:Inferno Ships]]
[[Category:User-made Ships]]
[[Category:Installation]]

Charon

2024-07-28T10:02:17Z

Mobius: Created page with "{{disambiguation}} '''FreeSpace 1''' *'''GTS ''Charon''''', a Centaur support ship that captures Arjuna 1 in Enter the D..."

{{disambiguation}}

'''FreeSpace 1'''
*[[FreeSpace 1 Terran Ship Database#GTS Charon|'''GTS ''Charon''''']], a [[Centaur]] support ship that captures Arjuna 1 in [[Enter the Dragon]]

'''[[Cold Element]]'''
*[[GTI Charon|'''''Charon''''']]-class installation, a [[List of Sol jump node devices|device capable of reopening]] the [[Sol]] jump node in [[Delta Serpentis]]

GTI Charon

2024-07-28T09:58:18Z

Mobius: This is a draft, please expand it

{{User-made Ships|''GTI '''Charon'''''}}
The '''GTI ''Charon''''', featured [[Blackwater Operations]] (a [[Cold Element]] campaign) is [[List of Sol jump node devices|an installation capable of reopening]] the [[Sol]] jump node in [[Delta Serpentis]].

[[Image:<>.jpg|thumb|right|650px|The GTI ''Charon'']]

==Description:==
===BWO Description===
TBFIL.

===Credits===
TBFIL.

===Name Origin===
TBFIL.

==Performance:==
===Statistics===
{{Ship_box
|name = GTI Charon
|yaw_pitch_roll = TBFIL
|max_velocity = TBFIL
|hitpoints = TBFIL
|length = TBFIL
|width = TBFIL
|height = TBFIL
|turrets = TBFIL
|fighterbays = TBFIL
}}

===Armaments===
*'''Blackwater Operations'''
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=2 style="background:#351515;"| '''Default Statistics'''
|- align="center"
| style="width:120px" |Turret Type
| style="width:60px" |Amount
|- align="center"
| TBFIL
| TBFIL
|- align="center"
| TBFIL
| TBFIL
|- align="center"
| TBFIL
| TBFIL
|- align="center"
| TBFIL
| TBFIL
|- align="center"
| TBFIL
| TBFIL
|}

===Veteran Comments===
{{Comment|''TBFIL''}}

==External links:==
*Leaked version
**[https://www.hard-light.net/forums/index.php?topic=99339.msg1920060#msg1920060 Hard-Light Productions]

[[Category: User-made Ships]]
[[Category: Cold Element]]

GTD Golgotha

2024-07-28T09:49:42Z

Mobius: Categorization

{{User-made Ships|''GTD '''Golgotha'''''}}
The '''GTD ''Golgotha''''' is an iconic fan-made destroyer featured in [[Blackwater Operations]], a [[Cold Element]] campaign.

[[Image:GTDGolgotha oldrender.jpg|thumb|right|650px|An old render of GTD ''Golgotha'']]

==Description:==
===BWO Description===
TBFIL.

===Credits===
TBFIL.

==Performance:==
===Statistics===
{{Ship_box
|name = GTD Golgotha
|yaw_pitch_roll = TBFIL
|max_velocity = TBFIL
|hitpoints = TBFIL
|length = TBFIL
|width = TBFIL
|height = TBFIL
|turrets = TBFIL
|fighterbays = TBFIL
}}

===Armaments===
*'''Blackwater Operations'''
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=2 style="background:#351515;"| '''Default Statistics'''
|- align="center"
| style="width:120px" |Turret Type
| style="width:60px" |Amount
|- align="center"
| TBFIL
| TBFIL
|- align="center"
| TBFIL
| TBFIL
|- align="center"
| TBFIL
| TBFIL
|- align="center"
| TBFIL
| TBFIL
|- align="center"
| TBFIL
| TBFIL
|}

===Veteran Comments===
{{Comment|''TBFIL''}}

==External links:==
*Leaked version
**[https://www.hard-light.net/forums/index.php?topic=99339.msg1920060#msg1920060 Hard-Light Productions]

[[Category: User-made Ships]]
[[Category: Cold Element]]