FreeSpace Wiki - User contributions [en]

SD Ravana

2006-04-05T08:24:33Z

FireCrack: /* Veteran Comments */

The '''SD Ravana''' class of Destroyers was first spotted in the [[Shivan_Nebula|nebula]] beyond [[Gamma Draconis]], discovered by the GTCv Lysander and the GTCv Actium. 
This Class is probably the most powerful Shivan capital vessel, second only to the [[SJ Sathanas|Sathanas]] and maybe the Lucifer. In possesion of 4 forward facing beam cannons, it can rip through the hull of a [[GTD Hecate|Hecate]] or [[GTD Orion|Orion]] class destroyer in under a minute, and take out smaller vessels within seconds. It's anti-capital ship weaponry make it a threat to any vessel, even one the size of the Colossus. 
But the Anti-Capital beams come at a price. The Ravana Class is more vulnerable to fighter and bomber attacks than its brother, the [[SD Demon|Demon]] Class. Still, it would take a large number of squadrons to take out such a target. 

----

{{FS12_Ships}}
{{shipimage|No Picture|caption=The SD Ravana}}

==Description:==

===FS2 Tech Room Description===
The SD Ravana is a destroyer class GTVA forces have only recently encountered. It appears to be tasked with clearing out smaller foes, a mission for which it is well suited. It eagerly wipes out wings of fighters and bombers and also overwhelms cruisers and corvettes.

===Developer Notes===
None

===Veteran Comments===
''The Ravana is scary-looking, but it's not tough. Weaker in terms of hull strength, and MUCH weaker in terms of turret strength then the Demon, the Ravana pays for its attack-oriented design with weak defenses. Indeed, fighters and bombers can range over the front three-quarters of Ravana's upper surfaces with near-impunity, and the lower-spine-mounted SAAA beam is placed too far back to defend the Ravana's main guns. It has a flak turret and another SAAA for anyone who comes up behind it, however. A capital ship behind a Ravana, on the other hand, is the Shivan destroyer's death sentence, as its engine subsystems are not strong and cover nearly the whole rear surface of the destroyer. Notheless, it's forward batteries will cause massive damage to other capships if left unchecked.''

''In [[The Great Hunt]] I was actually able to destroy the Ravana's main beam cannons before it fired on the [[GTCv Deimos|Deimos corvettes]], that's how weak they are. (Didn't make a difference, the corvette is destroyed by a [[SEXP]]).''

==Performance:==
===Statistics===
{|
|-
| style="width:200px" | '''[[Technical_Terms_and_Definitions#Type|Type]]'''
| style="width:200px" | Destroyer
|-
| '''[[Technical_Terms_and_Definitions#Manufacturer|Manufacturer]]'''
| Unknown
|-
| '''[[Technical_Terms_and_Definitions#Manuverablity|Manuverability]]'''
| N/A
|-
| '''[[Technical_Terms_and_Definitions#Max Velocity|Max Velocity]]'''
| 20.0 mps
|-
| '''[[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]]
| 100 000
|-
| [[Technical_Terms_and_Definitions#Shields|Shields]]
| N/A
|-
| '''[[Technical_Terms_and_Definitions#Length|Length]]'''
| 2346 m
|}

===Armaments===

*'''[[Technical_Terms_and_Definitions#Turrets|Turrets]]'''
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=2 style="background:#300505;"| '''Freespace 2'''
|- align="center"
| style="width:120px" |Turret Type
| style="width:60px" |Amount
|- align="center"
| [[Shivan Turret Laser]]
| 17
|- align="center"
| [[Standard Flak]]
| 5
|- align="center"
| [[FighterKiller]]
| 1
|- align="center"
| [[Shivan Cluster]]
| 1
|- align="center"
| [[SAAA|Anti-Fighter Beam]]
| 2
|- align="center"
| [[SRed|Small Red Beam]]
| 2
|- align="center"
| [[LRed|Large Red Beam]]
| 2
|}

[[Category:Ship]]

GTB Athena

2005-11-23T02:14:47Z

FireCrack:

{{FS12_Ships}}
{{shipimage|image=http://www.volition-inc.com/fs/images/spacecraft/gtb-athena.jpg|caption=The GTB Athena}}

==Description:==

===Overview===
The '''GTB Athena''' was one of the oldest, most commonly used class of bomber during the [[14-Year War]]. When the [[Shivans]] arrived with their outpowering warships, the need arose for larger, more devastating bombs, which the Athena was enough small to be able to carry.

Being the lightest bomber of all known Terran bombers, the Athena provided a reasonable efficiency against incoming hostile fighters, while it was not worth a fighter-class.

===FS1 Tech Room Description===
The smallest bomber in the fleet, the Athena has oftentimes been mistaken for a fighter. However, one should not be fooled by its small size. The Athena can carry light bombs, and most missiles. It also has the ability to dogfight well. Its strong shielding and hull make it the favored "Lightning Bomber" of the GTA.

===Developer Notes===
Excellent for hit-and-run bombing. Good speed for its size, with a high capacity afterburner reserve.

===Veteran Comments===
''I always wanted to love the Athena, but it's lack of a any serious anti-cap ship capablity made it a non-choice when going against anything bigger than a transport.'' 
 
''The Athena is the ultimate tool for a fighter pilot. But not a bomber pilot. It has higher speed then the Hercules, good manuverabilty, and can haul an equal if not greater amount of ordance. It has a thin target profile from the the sides and front-back. Its gun setup is the best for dogfighting or bomb interception ever seen in a Freespace game, more then compensating for its inablity to carry the [[Prometheus]] or [[Banshee]]. If you want to carry real bombs, though, you'll have to get a Medusa.''

==Performance:==
===Statistics===
{|
|-
| style="width:200px" | '''[[Technical_Terms_and_Definitions#Type|Type]]'''
| style="width:200px" | Light Bomber
|-
| '''[[Technical_Terms_and_Definitions#Manufacturer|Manufacturer]]'''
| Dynamic Metamer
|-
| '''[[Technical_Terms_and_Definitions#Manuverablity|Manuverability]]'''
| Average
|-
| '''[[Technical_Terms_and_Definitions#Max Velocity|Max Velocity]]'''
| 60.0 - 75.0 mps
|-
| '''[[Technical_Terms_and_Definitions#Max Afterburner Velocity|Max Afterburner Velocity]]'''
| 120.0 mps
|-
| '''[[Technical_Terms_and_Definitions#Armor|Armor]]'''
| Medium
|-
| [[Technical_Terms_and_Definitions#Hitpoints|Hitpoints]]
| 250
|-
| [[Technical_Terms_and_Definitions#Shields|Shields]]
| 500
|-
| '''[[Technical_Terms_and_Definitions#Length|Length]]'''
| 20 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;"| '''Freespace 1'''
|- align="center"
| style="width:50px" |Bank
| style="width:50px" |Guns
| style="width:200px" |Standard Loadout
|- align="center"
| 1st
| 2
| [[GTW Avenger|Avenger]]
|- align="center"
| 2nd
| 2
| [[GTW Flail|Flail]]
|- align="center"
| colspan=3| Compatible Primaries
|-
| colspan=3| [[GTW ML-16|ML-16 Laser]], [[GTW Disruptor|Distruptor]], [[GTW Avenger|Avenger]], [[GTW Flail|Flail]], [[GTW Leech Cannon|Leech Cannon]], [[GTW Shield Breaker|S-Breaker]]
|}
*'''[[Technical_Terms_and_Definitions#Missile Banks|Missile Banks]]'''
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=3 style="background:#351515;"| '''Freespace 1'''
|- align="center"
| style="width:50px" |Bank
| style="width:50px" |Capacity
| style="width:200px" |Standard Loadout
|- align="center"
| 1st
| 80
| [[GTM Phoenix V|Phoenix V]]
|- align="center"
| 2nd
| 80
| [[GTW Synaptic|Synaptic]]
|- align="center"
| colspan=3| Compatible Secondaries
|-
| colspan=3| [[GTM D-Missile|D-Missile]], [[GTM Fury|Fury]], [[GTM Phoenix V|Phoenix V]], [[GTM Synaptic|Synaptic]], [[GTM Stiletto|Stiletto]], [[GTM Interceptor|Interceptor]], [[GTM EM Pulse|EM Pulse]], [[GTM Cluster Bomb|Cluster Bomb]]
|}

Template:Shipimage

2005-11-23T02:13:58Z

FireCrack:

{| border=0 align=right cellpadding=0 cellspacing=0 width=30% style="margin: 0 0 1em 1em; background: #101010; border: 2px
#CC0500 solid; border-collapse: collapse; font-size: 95%;"
! style="color: white; height: 30px; background: #1B0E0E; 70%;"| {{{image}}}
|-
! style="color: white; height: 30px; background: #404040; 70%; align:center"| {{{caption}}}
|}

Template:Shipimage

2005-11-23T02:11:10Z

FireCrack:

{| border=0 align=right cellpadding=0 cellspacing=0 width=30% style="margin: 0 0 1em 1em; background: #101010; border: 2px
#CC0500 solid; border-collapse: collapse; font-size: 95%;"
! style="color: white; height: 30px; background: #1B0E0E; 70%;"|img
|-
! style="color: white; height: 30px; background: #404040; 70%; align:center"| The GTB Athena
|}

Second Shivan Incursion

2005-11-22T04:51:28Z

FireCrack: /* 2367 */

{{NotAllCanon}}

The '''Second Shivan Incursion''' was the second invasion by the ruthless [[Shivans]] on Galactic Terran-Vasudan space.

Shortly after the discovery of the [[Knossos]] subspace portal, a Rakshasa-class Shivan cruiser emerged. A short-lived offensive against the Shivans in the nebula beyond the portal also saw the end of [[The NTF Rebellion]] with the deployment of the [[GTVA Colossus]]. Bosch, however, made contact with the Shivans and vanished into the nebula. Meanwhile, dozens of six-kilometer long Shivan Sathanas juggernauts began pouring from the portal, and started converging on the [[Capella]] star. A plan to collapse the jump nodes to Capella using [[Meson Bomb]]s was hatched and technically successful, but during the final stages of evacuation, the Sathanas juggernauts triggered a supernova in Capella. This timeline will give a battle-by-battle account of the offensive and defensive action against the Shivans.

==2367==

August 16th: Rakshasa class Shivan cruiser and several wings of Maras appear through the Knossos portal, destroying the GTC Vigilant. GTVA command deploys the GTD Carthage and the GVCv Dashor to neutralize the immediate threat.

August 20th: NTC Trinity discovered adrift in the nebula.

August 21st: GTCv Lysander destroyed by SD Ravana.

August 22nd: SD Ravana destroyed by bombers in the nebula.

August 28th: NTF launches a major offensive in Epsilon Pegasi. Rear Admiral Koth and the NTF 6th Fleet inflict 75% causalties to the GTVA forces. First Nebular Retreat.

August 29th: First combat deployment of the GTVA Colossus, at the Battle of Enif Station.

November 2nd: With Epsion Pegasi secured, the GTD Aquitaine spearheads the exploration of the nebula.

November 7th: Sirius falls to the GTVA. Bosch orders the rest of the NTF fleet to Gamma Draconis and the Nebula to make contact with the Shivans. End of the NTF rebellion.

November 11th: First appearance of the SJ Sathanas. Second Nebular Retreat.

November 14th: The Knossos portal is destroyed by Meson bombs, but the SJ Sathanas emerges in Gamma Draconis through the now-stabilized node.

November 15th: Sathanas main beams and the SD Beleth destroyed by Bakha bombers near the Gamma Draconis-Capella node. Destruction of the SJ Sathanas by the GTVA Colossus in Capella.

November 18th: Admiral Bosch and his immediate subordinates captured by the Shivans. GTVA recovers the schematics for the ETAK device. NTF Iceni self-destructs.

November 22nd: Discovery of the second Knossos portal by the GVD Psamtik. Multiple Sathanas juggernauts encountered in the nebula. GVD Psamtik destroyed by the second Sathanas. Third Nebular Retreat.

November 23rd: Terran SOC pilots, flying captured Mara fighters, scout the system beyond the second Knossos and encounter a third Knossos as well as several additional juggernauts.

November 24th: Massive evacuations of the densely-populated Capella system begin. Millions of refugees flood into Epsilon Pegasi and Vega.

November 29th: 90 Sathanas juggernauts surround the Capella sun and begin emitting quantum subspace pulses of increasing intensity. GTVA Colossus destroyed by Sathanas 17 while defending the Capella-Gamma Draconis node.

November 30th: GTD Nereid and GTD Bastion, packed with meson bombs, detonate inside the Vega-Capella and Epsilon Pegasi-Capella nodes. Sathanas juggernauts destabilize the Capella star. Capella goes supernova.

[[The NTF Rebellion]]''' :PREVIOUS | NEXT: '''[[Post-Capella]]

[[Category:History|Second Shivan Incursion]]

Second Shivan Incursion

2005-11-22T04:49:51Z

FireCrack: /* 2367 */

{{NotAllCanon}}

The '''Second Shivan Incursion''' was the second invasion by the ruthless [[Shivans]] on Galactic Terran-Vasudan space.

Shortly after the discovery of the [[Knossos]] subspace portal, a Rakshasa-class Shivan cruiser emerged. A short-lived offensive against the Shivans in the nebula beyond the portal also saw the end of [[The NTF Rebellion]] with the deployment of the [[GTVA Colossus]]. Bosch, however, made contact with the Shivans and vanished into the nebula. Meanwhile, dozens of six-kilometer long Shivan Sathanas juggernauts began pouring from the portal, and started converging on the [[Capella]] star. A plan to collapse the jump nodes to Capella using [[Meson Bomb]]s was hatched and technically successful, but during the final stages of evacuation, the Sathanas juggernauts triggered a supernova in Capella. This timeline will give a battle-by-battle account of the offensive and defensive action against the Shivans.

==2367==

August 16th: Rakshasa class Shivan cruiser and several wings of Maras appear through the Knossos portal, destroying the GTC Vigilant. GTVA command deploys the GTD Carthage and the GVCv Dashor to neutralize the immediate threat.

August 20th: NTC Trinity discovered adrift in the nebula.

August 21st: GTCv Lysander destroyed by SD Ravana.

August 22nd: SD Ravana destroyed by bombers in the nebula.

August 28th: NTF launches a major offensive in Epsilon Pegasi. Rear Admiral Koth and the NTF 6th Fleet inflict 75% causalties to the GTVA forces. First Nebular Retreat.

August 29th: First combat deployment of the GTVA Colossus, at the Battle of Enif Station.

November 2nd: With Epsion Pegasi secured, the GTD Aquitaine spearheads the exploration of the nebula.

November 7th: Sirius falls to the GTVA. Bosch orders the rest of the NTF fleet to Gamma Draconis and the Nebula to make contact with the Shivans. End of the NTF rebellion.

November 11th: First appearance of the SJ Sathanas. Second Nebular Retreat.

November 14th: The Knossos portal is destroyed by Meson bombs, but the SJ Sathanas emerges in Gamma Draconis through the now-stabilized node.

November 15th: Sathanas main beams and the SD Beleth destroyed by Bakha bombers near the Gamma Draconis-Capella node. Destruction of the SJ Sathanas by the GTVA Colossus in Capella.

November 18th: Admiral Bosch and his immediate subordinates captured by the Shivans. GTVA recovers the schematics for the ETAK device. NTF Iceni self-destructs.

November 22nd: Discovery of the second Knossos portal by the GVD Psamtik. Multiple Sathanas juggernauts encountered in the nebula. GVD Psamtik destroyed by the second Sathanas.

November 23rd: Terran SOC pilots, flying captured Mara fighters, scout the system beyond the second Knossos and encounter a third Knossos as well as several additional juggernauts. Third Nebular Retreat.

November 24th: Massive evacuations of the densely-populated Capella system begin. Millions of refugees flood into Epsilon Pegasi and Vega.

November 29th: 90 Sathanas juggernauts surround the Capella sun and begin emitting quantum subspace pulses of increasing intensity. GTVA Colossus destroyed by Sathanas 17 while defending the Capella-Gamma Draconis node.

November 30th: GTD Nereid and GTD Bastion, packed with meson bombs, detonate inside the Vega-Capella and Epsilon Pegasi-Capella nodes. Sathanas juggernauts destabilize the Capella star. Capella goes supernova.

[[The NTF Rebellion]]''' :PREVIOUS | NEXT: '''[[Post-Capella]]

[[Category:History|Second Shivan Incursion]]

GVD Hatshepsut

2005-11-22T02:47:50Z

FireCrack: /* Technical data */

==Official Description==
In 2360, Allied Command commissioned the first of the GVD Hatshepsut-class destroyers. The Vasudan contractor Akheton designed the Hatshepsut to efficiently integrate the new beam cannon. The process of retrofitting the older Typhon-class warships yielded vessels prone to system failures and reactor overloads. Though a handful of modified Typhons remain in service, the Hatshepsut has taken over as the primary Vasudan destroyer. With 24 turrets, 5 beam cannons, and 2 fighterbays, destroyers such as GVD Psamtik of Deneb's 13th Battle Group serve at the vanguard of the modern Vasudan fleet.

==Technical data==
Hull strength: 135,000 hitpoints 
Maximum velocity: 15 metres/second 
Length: approximately 2 kilometres 
Fighter complement: Unknown Might be around 15 wings. 
Scan time: 2,000 miliseconds 
Weaponry:
*1 SVas beam cannon
*3 BVas beam cannons
*5 Fusion Mortar warhead launchers
*6 Terran Huge turrets
*4 AAAf anti-fighter beams
*11 Standard flak guns
Other subsystems:
*Bridge
*Navigation
*Weapons
*Communication
*Sensors
*Fighter bay 01
*Fighter bay 02
*Reactor
*Engine 01
*Engine 02

==Ship names==
[[GVD Psamtik]] 
[[GVD Memphis]] 

==Wiki Comments==
The Hatshepsut is not as much effective against fighters than the [[GTD Hecate]]-class, but her BVas beams mean danger to anything larger than a bomber and can be targeted with beam cannons. It's a setback that the beam turrets are large, thereby easy to hit, and vulnerable.

There is a nice, glowmapped version for the Hatshepsut's textures in the SCP [[MediaVP]].

GVD Hatshepsut

2005-11-22T02:47:31Z

FireCrack: /* Technical data */

==Official Description==
In 2360, Allied Command commissioned the first of the GVD Hatshepsut-class destroyers. The Vasudan contractor Akheton designed the Hatshepsut to efficiently integrate the new beam cannon. The process of retrofitting the older Typhon-class warships yielded vessels prone to system failures and reactor overloads. Though a handful of modified Typhons remain in service, the Hatshepsut has taken over as the primary Vasudan destroyer. With 24 turrets, 5 beam cannons, and 2 fighterbays, destroyers such as GVD Psamtik of Deneb's 13th Battle Group serve at the vanguard of the modern Vasudan fleet.

==Technical data==
Hull strength: 135,000 hitpoints 
Maximal velocity: 15 metres/second 
Length: approximately 2 kilometres 
Fighter complement: Unknown Might be around 15 wings. 
Scan time: 2,000 miliseconds 
Weaponry:
*1 SVas beam cannon
*3 BVas beam cannons
*5 Fusion Mortar warhead launchers
*6 Terran Huge turrets
*4 AAAf anti-fighter beams
*11 Standard flak guns
Other subsystems:
*Bridge
*Navigation
*Weapons
*Communication
*Sensors
*Fighter bay 01
*Fighter bay 02
*Reactor
*Engine 01
*Engine 02

==Ship names==
[[GVD Psamtik]] 
[[GVD Memphis]] 

==Wiki Comments==
The Hatshepsut is not as much effective against fighters than the [[GTD Hecate]]-class, but her BVas beams mean danger to anything larger than a bomber and can be targeted with beam cannons. It's a setback that the beam turrets are large, thereby easy to hit, and vulnerable.

There is a nice, glowmapped version for the Hatshepsut's textures in the SCP [[MediaVP]].

FreeSpace 2 Tactical

2005-11-20T18:30:58Z

FireCrack: Cleaning up

[[#Basics|Basics]] | [[#Mission Types|Mission Types]] | [[#The HUD|The HUD]] | [[#Preferred GTVA Hardware|Ships]] | [[#Preferred Primary and Secondary Loadouts|Weapons]]

===Basics===

Alright pilot, lets get to the basics of space combat in FreeSpace 2. In the deep cold of space, nobody can hear you scream, so don't get yourself killed, that's the first rule in any handbook.

If you have the choice, you should make sure you check ever aspect of your ship and wing configuration. Going with the standard loadout may get you by, but there may be better or preferred weaponry out there.

When you hit space, first thing you should check is the nearby friendly ships, your current velocity, armed weapons and configurations, and if there is any immediate threats nearby.

===Mission Types===

====Guard Missions====

Protecting a friendly vessel can sometimes prove quite challenging, especially when the enemy forces outnumber you. Fortunately, you can use some things to your advantage. Order your wingmen to protect your escort target, or escort wing. The target being escorted usually has some defenses of its own, use those to your advantage. I've seen many a Basilisk splashed because escorting fighters drew the Shivan fighters into range of the bigger ships guns. If you have 2 wings to work with, this is even easier, you can usually assign one wing to escort while one engages the enemy ships at long range.

If you're helping fend off an opposing capital ship, remember to take out its main beams as soon as possible. When stripped of their beam weapons, capital ships lose much of their offensive firepower, and this can give you a critical advantage in battle. Once the main beam weapons are out, target the anti fighter beams, especially if you're defending a small ship like a cruiser.

====Assault Missions====

Assault missions usually come in a few flavors. If your attacking an enemy cap-ship, then you'll be wanting a bomber of some kind (usually Sekhmet or Boanerges) and a loadout of Cyclops or Helios. If your mission requires the escort of a bomber wing, then you better have a few Perseus with Harpoons at the ready.

When attacking enemy cap-ships, make sure you knock out some of the turrets or the weapons subsystem before letting loose with the space bombs. Anti fighter beams and Flak cannons are particularly good at eliminating incoming bombs, but even standard plasma turrets can find their marks on occasion.

====Stealth Missions====

Stealth missions can be among the most challenging to fly, requiring top notch reflexes and situational awareness. Remember to stay as far away as possible from patrolling fighters, and avoid firing your weapons at all costs.

===The HUD (Heads Up Display)===

The most important interface in the entire game is your Heads Up Display, or more commonly known as HUD. The HUD used in FreeSpace is robust, giving you many options on the brightness, color, and numerous displays designed to help you during the conflict.

====The Main Flight Controller====

The Main Flight Controller (MFC) is the cluster of instrumentation at the center of the screen, and contains an enormous number of extremely valuable tools. A majority portion of your time in your ship will be spent looking at the MFC since it serves as the focal point of your ship's weapons, flight path, and most critical readouts.

The center of the screen shows the targeting reticle, three small slashes in a triangular arrangement. This where your weapons are pointed. Note that this is the center of your ship's axis, straight ahead in other words. The ship's weapons will be mounted away from the center to varying degrees. For some craft, the distance between the weapon's actual muzzle and the targeting reticle is quite dramatic! It is only through experience and observation that you will be able to know where your weapon's shot is actually going to land relative to the reticle.

Directly below the reticle is a summary of your target's hull and shield strength. This is the same information as presented in the target information box, but here you can see it without taking your eyes off the target. Surrounding the numeric hull strength are four sectors showing shield power. If a quadrant is down, it's good to try hitting that part of the ship rather than chewing on other shield quadrants that are still active.

There are four types of indicators that orbit the edge of the MFC. They are:

1: The target directional indicator: A solid arrow will point the the direction to your current target if that target is not near the center of your view.

2: The aspect indicator: A small "T" shaped marker shows the current aspect, or facing, of the target relative to your ship. If the aspect indicator is in the upper half of its orbit, then the ship is facing toward you. Conversely, if the indicator is in the bottom half, then the target ship is facing away from you. 12 o'clock means the target is heading straight at you, 6 o'clock means you're staring up its engine exhaust. 3 and 9 o'clock indicate directions of travel that are roughly perpendicular to yours.

3: The attacking hostile indicator: One or more hollow red triangles point in the direction of hostiles that are currently attacking (targeting) you. These can be cycled through by using the "Next nearest attaker" key (default 'R').

4: The incoming missile indicator: One or more yellow triangles will point the direction of incoming guided missiles. The length of the line extending from the point of the triangle shows the missile's approximate distance. You will also hear a series of warning beeps that increase in frequency as the missiles near you. Be aware that no warning is shown for dumbfire or manually detonated missiles; you must learn to recognize these weapons by sight and sound alone.

On the left side of the MFC, are your throttle setting and afterburner gauge. Your engine's top speed is displayed; this number will change depending on how much power you have allocated to engines. Your current throttle setting is displayed as a hash mark on this scale. If your ship is set to automatically change speed to follow your target, you will see an "M" indicator next to your throttle setting. The afterburner gauge simply shows how much power is available to drive your ship's powerful afterburner boost feature.

On the right side of the MFC, are the two threat indicators and the weapon energy gauge. The thread indicators show you when an enemy is firing their primary guns at you (top icon), or is attempting missile lock (bottom icon). You will also receive an audible warning if the enemy is trying to missile-lock you. The weapon energy gauge simply shows how much power is available for the firing of your primary guns; keep an eye on this one, as if it reachs zero, you can't fire your guns until some power recharges. If the level gets very low, a percentage will be shown.

====Wingman Display====

This shows the current wings under your command. Each dot represents a fighter. All are organized into their respective wings (Alpha, Beta, Delta, Epsilon). There may be more wings under your command than shown here. An easy way to see what wings are under your command is to bring up the communications window (default 'C' key), and choose "Wings" ('2' key).

When one of the fighters is under fire and taking hits, their dot will flash briefly. Be sure to keep an eye on the status of vulnerable wings like bombers. A solid green dot is good; a solid red dot means that the fighter is badly damaged. If the dot turns to a hollow green circle, then the ship has left the combat area. If it's a hollow red circle, then the ship has been destroyed.

====Monitoring Display====

This display allows you to keep tabs on friendly or enemy craft that are vital to your mission objectives. It allows you to quickly target these ships with a single key press. The monitoring display shows the current hull strength of the target, and will also flash briefly if that ship is under fire. A "D" is shown next to the line if the ship is disabled and unable to move. Be aware that you have control to add or remove ships from this list via a menu shown when pressing te F4 key.

====Weapons Display====

The top of this display shows your primary weapons. The bottom shows all secondary weapons. Active weapons are marked with a single triangle. In the secondary display, missiles can be dual fired. When such an option is selected, a double triangle is used to mark the display.

====Energy Display====

This shows where your energy is being allotted to. When your craft is equipped with shields, this is broken into 3 bars, when there is no shields, this is shown with 2 bars. Each bar represents Guns, Shields, and Energy respectively.

====Target information box and targeting bracket====

When you select a target, it will be surrounded by a box so you can keep track of it easily. Its distance will be shown under the box. Note that this distance may vary from the one shown in the target information box, since one is showing distance to the target's center of mass, while the other is showing the distance to your currently selected turret or sub-system. To the right side of the box, you may see a number of colored dots. These dots indicate how many of your squadmates are currently assigned to the target. On an allied target, these dots indicate wingmates guarding the target ship. On a hostile target, dots indicate wingmates that are attacking this target.

In the lower-left of the screen is the Target Information Box. This gives you vital details on the stats of a targeted ship. This information includes:

- a visual representation of the target, showing its orientation relative to your ship.

- the ship's hull strength, shown both as a percentage and as a bar graph on the right side of the box.

- if the target has shields, then a diagram showing their shield quadrants and each one's relative strength will be displayed.

- the target ship's distance, and speed

- docking status, whether the target is attached to or hauling something else (for example, a cargo container or a transport).

If the target is an allied ship, then you will receive additional information, namely its current orders and estimated time to completion (if applicable). When you select a turret or sub-system of the target, then additional information is shown: the name of the selected subtarget and its strength.

In the case of both the target information box and the target bracket, your current subtarget will be shown as a second set of brackets. If the subtarget is visible to you, then its bracket will be a square. Otherwise, it will be a diamond with an X in it. Be aware that sometimes this may be innacurate. If it looks like the subtarget should be in view but the computer says it isn't, you may still hit it.

Talk:GTVA Colossus

2005-11-16T09:03:08Z

FireCrack:

Quotes might be inaccurate. I recalled them from heart. - TopAce

I added the sidebar, but the picture messed with it so i rearanged the article, i'm preety sure the pic sholdnt be where i put it so we need a wiki-god to make it nicely positioned.--[[User:FireCrack|FireCrack]] 10:03, 16 Nov 2005 (CET)

GTVA Colossus

2005-11-16T09:01:24Z

FireCrack:

{{FS12_Ships}}
==General==
http://www.freespace2.com/images/ship_colossus/smpic.jpg
===Description and History===
----
The largest space-faring warship ever constructed by [[Terrans]] or [[Vasudans]], the GTVA Colossus was the result of twenty years of joint effort from dozens of contractors from across the [[Galactic Terran-Vasudan Alliance]]. Logging in with a length of six-kilometres, this behemoth was equipped with over eighty weapon turrets, in addition to over 240 combat spacecraft.

With the offensive power that exceeded most GTVA battlegroups, the Colossus was designed to combat the [[Shivans]] upon their return to Allied territory. The prospective target was one or more Lucifer-class super-destroyers, and it was deemed that the Colossus would not only have the firepower not only to destroy such a foe, but also to survive multiple hits from a Lucifer's primary weapon system.

The first combat use of the Colossus was against the [[Neo-Terran Front]]. NTF forces proved to be no match for the Colossus and her battlegroup, and the rebels made every effort to avoid direct combat with the juggernaut. It can be truthfully said that it was the Colossus that was the ultimate factor in the NTF's collapse. With his fleet shattered, and the remnants being actively pursued and destroyed by the Colossus, Admiral Aken Bosch gave the order to flee GTVA space to the relative safety of the nebula beyond [[Gamma Draconis]].

With the NTF defeated, the Colossus was finally to fulfil the role her designers had envisioned for her: the defeat of a Shivan incursion. However, as it turned out, the challenge was not to be Lucifer-class super-destroyers, but rather a Sathanas-class juggernaut. Twenty-years of constant struggle finally culminated with the Colossus' destruction of the [[SJ Sathanas]], all at the cost of moderate damage to the Colossus.

All would have been well was it not for the [[Shivans]] possessing multiple juggernauts. In the closing stages of the Battle of [[Capella]], the Colossus was deployed to interdict Shivan traffic at the [[Gamma Draconis]] jump node in [[Capella]] to divert enemy forces and attention away from the GTD Bastion, which was en route to collapse the jump corridor to [[Epsilon Pegasi]]. The ploy succeeded, as the [[Shivans]] first deployed an [[SD Ravana]], then a Sathanas to engage the Colossus. In her weakened state, it was obvious that the Colossus would not survive an engagement with another Sathanas-class juggernaut, and Allied Command ordered the Colossus to withdraw.

However, with the success of the Bastion's critical mission in doubt, the Colossus disobeyed the direct order from Allied Command, and refused to disengage. Subsequently, the Colossus was destroyed with the loss of all hands. The thirty-thousand officers and crew of the Colossus willingly sacrificed themselves to ensure the continued survival of the billions of individuals making up the Terran and Vasudan species, and ultimately, the
[[Galactic Terran-Vasudan Alliance]]. They shall never be forgotten.
===Technical data===
----
Class: GTVA Colossus (Unique ship) 
Length: 6,116 metres 
Hull strength: 1,000,000 hitpoints 
Maximal velocity: 25 metres/second 
Number of turrets: 82 in description, 63 in-game
*18 Standard turrets
*12 Standard flak guns
*20 AAAf beam cannons
*7 Terran Slasher beams
*6 Big Green beams.
Fighter capacity: Sixty fighter and bomber wings 
Crew: around 30,000 
Scan time: 6,000 miliseconds 
Subsystems:
*6 Radar dishes (1% of total hull strength each)
*Communications (3% of total hull strength)
*Navigation (3% of total hull strength)
*Sensors (5% of total hull strength)
*Weapons (5% of total hull strength)
*Engine(Center) (7% of total hull strength)
*Engine(Front) (7% of total hull strength)
*Engine(Main) (7% of total hull strength)
*Engine Large 1 (Indestructible)
*Engine Large 2 (Indestructible)
*Engine Large 3 (Indestructible)
*Fighter bay (Indestructible)

==Victims of the Colossus==
*NTCv Hawkwood (Destroyed at Enif Station)
*NTD Repulse (Admiral Koth's flagship. Kamikaze attacked the Colossus)
*NTD Andronius (Reported destroyed in Command Briefing)
*NTC Camisard (Reported destroyed in Command Briefing)
*SJ Sathanas (First, High Noon mission)
*SD Beast (Destroyed shortly before the second Shivan juggernaut destroyed the Colossus)

==Quotes==
"This is the GTVA Colossus. Fighters, stand back of hostile warships. All batteries, fire at will!"

"This is the GTVA Colossus. Admiral Koth, you are ordered to power down your engines immidietely and surrender, the Polaris jump node is blockaded, there is no escape"

"You are sacrificing thousands of lifes for nothing!"

"If only Koth had surrendered rather than playing Martyr, his crew would still be alive"

"A Shivan juggernaut has jumped within range. What's the status of the Bastion?"

"We'll hold them back here. Just get the Baston through!"

==Colossus, the cutscene==
WORD BY WORD 
Narrator: The following is classified level Rho. Unauthorised access is punishable under the GTVA security act, Deneb convention, section 21.3.5. We vanquished the Shivans in the Great War but the hard questions remained. How would we confront the threat of future invasion? The Shivans might return at any time, any place, without warning. How would we fight the next threat to the very existence of our species?
In 2345, on the tenth anniversary of the Shivan attack on Ross 128, the Vasudan emperor Khonsu II addressed the newly formed GTVA general assembly. The emperor inaugurated an ambitious and unprecedented joint endeavour. The GTVA Colossus. 

Khonsu II: Together we built a civilisation on the ruins of the great war, and now we stand on the threshold of a new era of prosperity and harmony. Project Colossus the Vasudan people celebrate our shared covenant of peaceful coexistence and mutual defense of our Terran allies. 

Narrator: The Colossus is the most powerful space faring warship ever constructed. Spanning six kilometres from bow to stern the Colossus has taken over twenty years to complete. Twelve Lucifer class destroyers can fit within its massive hull. Its state of the art weaponry includes, forty-five laser turrets, fifteen flack guns, twelve missile batteries and twelve beam cannons. The Colossus wields more firepower than twelve Orion class destroyers combined. Sixty fighter and bomber wings are housed in its vast hanger, and its crew numbers over thirty thousand. Among its contractors are industry giants Triton Dynamics, Subach-Innes and the Akheton Corporation
The alliance now wages war on multiple fronts in Deneb, Alpha Centuri, Epsilon Pegasi and the mysterious nebula beyond Gamma Draconis. Once deployed the Colossus will end these conflicts swiftly and decisively. If ever the Shivans return to threaten our worlds we will be ready to face the challenge, securing peace for today and for generations to come.

GTVA Colossus

2005-11-16T09:00:41Z

FireCrack:

http://www.freespace2.com/images/ship_colossus/smpic.jpg
{{FS12_Ships}}
==General==
===Description and History===
----
The largest space-faring warship ever constructed by [[Terrans]] or [[Vasudans]], the GTVA Colossus was the result of twenty years of joint effort from dozens of contractors from across the [[Galactic Terran-Vasudan Alliance]]. Logging in with a length of six-kilometres, this behemoth was equipped with over eighty weapon turrets, in addition to over 240 combat spacecraft.

With the offensive power that exceeded most GTVA battlegroups, the Colossus was designed to combat the [[Shivans]] upon their return to Allied territory. The prospective target was one or more Lucifer-class super-destroyers, and it was deemed that the Colossus would not only have the firepower not only to destroy such a foe, but also to survive multiple hits from a Lucifer's primary weapon system.

The first combat use of the Colossus was against the [[Neo-Terran Front]]. NTF forces proved to be no match for the Colossus and her battlegroup, and the rebels made every effort to avoid direct combat with the juggernaut. It can be truthfully said that it was the Colossus that was the ultimate factor in the NTF's collapse. With his fleet shattered, and the remnants being actively pursued and destroyed by the Colossus, Admiral Aken Bosch gave the order to flee GTVA space to the relative safety of the nebula beyond [[Gamma Draconis]].

With the NTF defeated, the Colossus was finally to fulfil the role her designers had envisioned for her: the defeat of a Shivan incursion. However, as it turned out, the challenge was not to be Lucifer-class super-destroyers, but rather a Sathanas-class juggernaut. Twenty-years of constant struggle finally culminated with the Colossus' destruction of the [[SJ Sathanas]], all at the cost of moderate damage to the Colossus.

All would have been well was it not for the [[Shivans]] possessing multiple juggernauts. In the closing stages of the Battle of [[Capella]], the Colossus was deployed to interdict Shivan traffic at the [[Gamma Draconis]] jump node in [[Capella]] to divert enemy forces and attention away from the GTD Bastion, which was en route to collapse the jump corridor to [[Epsilon Pegasi]]. The ploy succeeded, as the [[Shivans]] first deployed an [[SD Ravana]], then a Sathanas to engage the Colossus. In her weakened state, it was obvious that the Colossus would not survive an engagement with another Sathanas-class juggernaut, and Allied Command ordered the Colossus to withdraw.

However, with the success of the Bastion's critical mission in doubt, the Colossus disobeyed the direct order from Allied Command, and refused to disengage. Subsequently, the Colossus was destroyed with the loss of all hands. The thirty-thousand officers and crew of the Colossus willingly sacrificed themselves to ensure the continued survival of the billions of individuals making up the Terran and Vasudan species, and ultimately, the
[[Galactic Terran-Vasudan Alliance]]. They shall never be forgotten.
===Technical data===
----
Class: GTVA Colossus (Unique ship) 
Length: 6,116 metres 
Hull strength: 1,000,000 hitpoints 
Maximal velocity: 25 metres/second 
Number of turrets: 82 in description, 63 in-game
*18 Standard turrets
*12 Standard flak guns
*20 AAAf beam cannons
*7 Terran Slasher beams
*6 Big Green beams.
Fighter capacity: Sixty fighter and bomber wings 
Crew: around 30,000 
Scan time: 6,000 miliseconds 
Subsystems:
*6 Radar dishes (1% of total hull strength each)
*Communications (3% of total hull strength)
*Navigation (3% of total hull strength)
*Sensors (5% of total hull strength)
*Weapons (5% of total hull strength)
*Engine(Center) (7% of total hull strength)
*Engine(Front) (7% of total hull strength)
*Engine(Main) (7% of total hull strength)
*Engine Large 1 (Indestructible)
*Engine Large 2 (Indestructible)
*Engine Large 3 (Indestructible)
*Fighter bay (Indestructible)

==Victims of the Colossus==
*NTCv Hawkwood (Destroyed at Enif Station)
*NTD Repulse (Admiral Koth's flagship. Kamikaze attacked the Colossus)
*NTD Andronius (Reported destroyed in Command Briefing)
*NTC Camisard (Reported destroyed in Command Briefing)
*SJ Sathanas (First, High Noon mission)
*SD Beast (Destroyed shortly before the second Shivan juggernaut destroyed the Colossus)

==Quotes==
"This is the GTVA Colossus. Fighters, stand back of hostile warships. All batteries, fire at will!"

"This is the GTVA Colossus. Admiral Koth, you are ordered to power down your engines immidietely and surrender, the Polaris jump node is blockaded, there is no escape"

"You are sacrificing thousands of lifes for nothing!"

"If only Koth had surrendered rather than playing Martyr, his crew would still be alive"

"A Shivan juggernaut has jumped within range. What's the status of the Bastion?"

"We'll hold them back here. Just get the Baston through!"

==Colossus, the cutscene==
WORD BY WORD 
Narrator: The following is classified level Rho. Unauthorised access is punishable under the GTVA security act, Deneb convention, section 21.3.5. We vanquished the Shivans in the Great War but the hard questions remained. How would we confront the threat of future invasion? The Shivans might return at any time, any place, without warning. How would we fight the next threat to the very existence of our species?
In 2345, on the tenth anniversary of the Shivan attack on Ross 128, the Vasudan emperor Khonsu II addressed the newly formed GTVA general assembly. The emperor inaugurated an ambitious and unprecedented joint endeavour. The GTVA Colossus. 

Khonsu II: Together we built a civilisation on the ruins of the great war, and now we stand on the threshold of a new era of prosperity and harmony. Project Colossus the Vasudan people celebrate our shared covenant of peaceful coexistence and mutual defense of our Terran allies. 

Narrator: The Colossus is the most powerful space faring warship ever constructed. Spanning six kilometres from bow to stern the Colossus has taken over twenty years to complete. Twelve Lucifer class destroyers can fit within its massive hull. Its state of the art weaponry includes, forty-five laser turrets, fifteen flack guns, twelve missile batteries and twelve beam cannons. The Colossus wields more firepower than twelve Orion class destroyers combined. Sixty fighter and bomber wings are housed in its vast hanger, and its crew numbers over thirty thousand. Among its contractors are industry giants Triton Dynamics, Subach-Innes and the Akheton Corporation
The alliance now wages war on multiple fronts in Deneb, Alpha Centuri, Epsilon Pegasi and the mysterious nebula beyond Gamma Draconis. Once deployed the Colossus will end these conflicts swiftly and decisively. If ever the Shivans return to threaten our worlds we will be ready to face the challenge, securing peace for today and for generations to come.

GTVA Colossus

2005-11-16T08:59:46Z

FireCrack:

{{FS12_Ships}}

http://www.freespace2.com/images/ship_colossus/smpic.jpg

==General==
===Description and History===
----
The largest space-faring warship ever constructed by [[Terrans]] or [[Vasudans]], the GTVA Colossus was the result of twenty years of joint effort from dozens of contractors from across the [[Galactic Terran-Vasudan Alliance]]. Logging in with a length of six-kilometres, this behemoth was equipped with over eighty weapon turrets, in addition to over 240 combat spacecraft.

With the offensive power that exceeded most GTVA battlegroups, the Colossus was designed to combat the [[Shivans]] upon their return to Allied territory. The prospective target was one or more Lucifer-class super-destroyers, and it was deemed that the Colossus would not only have the firepower not only to destroy such a foe, but also to survive multiple hits from a Lucifer's primary weapon system.

The first combat use of the Colossus was against the [[Neo-Terran Front]]. NTF forces proved to be no match for the Colossus and her battlegroup, and the rebels made every effort to avoid direct combat with the juggernaut. It can be truthfully said that it was the Colossus that was the ultimate factor in the NTF's collapse. With his fleet shattered, and the remnants being actively pursued and destroyed by the Colossus, Admiral Aken Bosch gave the order to flee GTVA space to the relative safety of the nebula beyond [[Gamma Draconis]].

With the NTF defeated, the Colossus was finally to fulfil the role her designers had envisioned for her: the defeat of a Shivan incursion. However, as it turned out, the challenge was not to be Lucifer-class super-destroyers, but rather a Sathanas-class juggernaut. Twenty-years of constant struggle finally culminated with the Colossus' destruction of the [[SJ Sathanas]], all at the cost of moderate damage to the Colossus.

All would have been well was it not for the [[Shivans]] possessing multiple juggernauts. In the closing stages of the Battle of [[Capella]], the Colossus was deployed to interdict Shivan traffic at the [[Gamma Draconis]] jump node in [[Capella]] to divert enemy forces and attention away from the GTD Bastion, which was en route to collapse the jump corridor to [[Epsilon Pegasi]]. The ploy succeeded, as the [[Shivans]] first deployed an [[SD Ravana]], then a Sathanas to engage the Colossus. In her weakened state, it was obvious that the Colossus would not survive an engagement with another Sathanas-class juggernaut, and Allied Command ordered the Colossus to withdraw.

However, with the success of the Bastion's critical mission in doubt, the Colossus disobeyed the direct order from Allied Command, and refused to disengage. Subsequently, the Colossus was destroyed with the loss of all hands. The thirty-thousand officers and crew of the Colossus willingly sacrificed themselves to ensure the continued survival of the billions of individuals making up the Terran and Vasudan species, and ultimately, the
[[Galactic Terran-Vasudan Alliance]]. They shall never be forgotten.
===Technical data===
----
Class: GTVA Colossus (Unique ship) 
Length: 6,116 metres 
Hull strength: 1,000,000 hitpoints 
Maximal velocity: 25 metres/second 
Number of turrets: 82 in description, 63 in-game
*18 Standard turrets
*12 Standard flak guns
*20 AAAf beam cannons
*7 Terran Slasher beams
*6 Big Green beams.
Fighter capacity: Sixty fighter and bomber wings 
Crew: around 30,000 
Scan time: 6,000 miliseconds 
Subsystems:
*6 Radar dishes (1% of total hull strength each)
*Communications (3% of total hull strength)
*Navigation (3% of total hull strength)
*Sensors (5% of total hull strength)
*Weapons (5% of total hull strength)
*Engine(Center) (7% of total hull strength)
*Engine(Front) (7% of total hull strength)
*Engine(Main) (7% of total hull strength)
*Engine Large 1 (Indestructible)
*Engine Large 2 (Indestructible)
*Engine Large 3 (Indestructible)
*Fighter bay (Indestructible)

==Victims of the Colossus==
*NTCv Hawkwood (Destroyed at Enif Station)
*NTD Repulse (Admiral Koth's flagship. Kamikaze attacked the Colossus)
*NTD Andronius (Reported destroyed in Command Briefing)
*NTC Camisard (Reported destroyed in Command Briefing)
*SJ Sathanas (First, High Noon mission)
*SD Beast (Destroyed shortly before the second Shivan juggernaut destroyed the Colossus)

==Quotes==
"This is the GTVA Colossus. Fighters, stand back of hostile warships. All batteries, fire at will!"

"This is the GTVA Colossus. Admiral Koth, you are ordered to power down your engines immidietely and surrender, the Polaris jump node is blockaded, there is no escape"

"You are sacrificing thousands of lifes for nothing!"

"If only Koth had surrendered rather than playing Martyr, his crew would still be alive"

"A Shivan juggernaut has jumped within range. What's the status of the Bastion?"

"We'll hold them back here. Just get the Baston through!"

==Colossus, the cutscene==
WORD BY WORD 
Narrator: The following is classified level Rho. Unauthorised access is punishable under the GTVA security act, Deneb convention, section 21.3.5. We vanquished the Shivans in the Great War but the hard questions remained. How would we confront the threat of future invasion? The Shivans might return at any time, any place, without warning. How would we fight the next threat to the very existence of our species?
In 2345, on the tenth anniversary of the Shivan attack on Ross 128, the Vasudan emperor Khonsu II addressed the newly formed GTVA general assembly. The emperor inaugurated an ambitious and unprecedented joint endeavour. The GTVA Colossus. 

Khonsu II: Together we built a civilisation on the ruins of the great war, and now we stand on the threshold of a new era of prosperity and harmony. Project Colossus the Vasudan people celebrate our shared covenant of peaceful coexistence and mutual defense of our Terran allies. 

Narrator: The Colossus is the most powerful space faring warship ever constructed. Spanning six kilometres from bow to stern the Colossus has taken over twenty years to complete. Twelve Lucifer class destroyers can fit within its massive hull. Its state of the art weaponry includes, forty-five laser turrets, fifteen flack guns, twelve missile batteries and twelve beam cannons. The Colossus wields more firepower than twelve Orion class destroyers combined. Sixty fighter and bomber wings are housed in its vast hanger, and its crew numbers over thirty thousand. Among its contractors are industry giants Triton Dynamics, Subach-Innes and the Akheton Corporation
The alliance now wages war on multiple fronts in Deneb, Alpha Centuri, Epsilon Pegasi and the mysterious nebula beyond Gamma Draconis. Once deployed the Colossus will end these conflicts swiftly and decisively. If ever the Shivans return to threaten our worlds we will be ready to face the challenge, securing peace for today and for generations to come.

SJ Sathanas

2005-11-16T08:59:05Z

FireCrack: Addes siedbar

{{FS12_Ships}}
==Overview==

The SJ Sathanas is the most powerful space-faring warship ever encountered by the [[Galactic Terran-Vasudan Alliance|GTVA]]. With four ultra-heavy beam cannons, a Sathanas outstrips even a [[GTVA Colossus|Colossus-class vessel]] in terms of raw firepower. Indeed, this was tragically demonstrated when a Sathanas juggernaut destroyed the [[GTVA Colossus]] in the [[Capella]] system. The only apparent weakness of the Shivan juggernaut is that the massive beam cannons are concentrated at the bow. Aside from a comparatively diminuative anti-warship beam cannon at the stern, the other flanks of the massive warship are covered only by point-defence weapons. However, a Sathanas is still more than able to defend itself and project offensive power via the many hundreds of fighters and bombers it carries in its cavernous flightbay. Thus, stopping a juggernaut is almost impossible. Even the 'expedient' of disabling the massive warship is hardly worth considering due to the numerous redundant engines found on the hull. In essence, any attack on a Sathanas-class juggernaut can be considered almost suicidal.

==History==

The first combat appearance of a Shivan Juggernaut was in the nebular theatre beyond the first [[Knossos]] portal in [[Gamma Draconis]] when the warship destroyed a Vasudan taskforce assaulting a Shivan gas-mining operation. The [[Galactic Terran-Vasudan Alliance|GTVA]] immediately began to withdraw from the nebula, and after numerous rearguard actions, the [[GTVA Colossus]] engaged and destroyed the juggernaut in the [[Capella]] system. After that victory, the GTVA returned to the nebula with the objective of locating and capturing Admiral Aken Bosch. However, that goal failed to be achieved as GTVA forces discovered that the _multiple_ Sathanas-class juggernauts were en route to GTVA space. [[Gamma Draconis]] was quickly overrun by the swift advance of the juggernaut fleet, which shortly entered [[Capella]]. In a desperate gamble, the GTVA fleet held the Shivans at bay while civilians were evacuated to [[Epsilon Pegasi]] and [[Vega]]. During the closing stages of the battle, the GTVA Colossus was destroyed in Capella by a Shivan juggernaut while providing a diversion for the GTD Bastion, which was tasked with collapsing the jump corridor to [[Epsilon Pegasi]]. In a final startling turn of events, the Shivan juggernauts instigated the super-nova of the [[Capella]] star as the jump corridor to [[Vega]] was destroyed.

==Conclusion==

The Shivan juggernaut fleet is the single, most serious threat to the survival of the Terran and Vasudan species. The GTVA barely managed to stop one Sathanas, and even then it was with warship that took two decades to construct. An encounter with any more Shivan juggernauts will only be able to be stopped with extreme difficulty. As a final note, all technical data concerning Sathanas-class juggernauts has been classified Level Upsilon.

GVD Psamtik

2005-11-14T18:07:32Z

FireCrack: /* Ship history */ Big cleanup, probably still needs work

==General==
*Ship class: [[GVD Hatshepsut]]
*In service: [[The Second Shivan Incursion]]
*Commander: Admiral Khaffe
*First appeared: Surrender, Bellisarius!
*Fate: Destroyed in the nebula by [[SJ Sathanas]]
*Fighter Squadrons: [[203rd Scorpions]]

==Ship history==
The Psamtik was the command ship of the 13th Vasudan Battle group, assigned to assist GTVA forces in the [[Deneb]] system against the [[Neo-Terra Front|NTF]]. The deployment of the Psamtik and the eventually caused the NTF to weaken at [[Deneb]]. The pilots of the Psamtik spotted the first [[SJ Sathanas]] and retreated back to [[Gamma Draconis]]. As Allied command ordered, the Psamtik's fighter wings oversaw the destruction of the [[Knossos]] subspace portal. After the shivan Juggernaut's intrusion into allied space it was the Psamtik that deployed fighters and bombers to destroy the main beam cannons on the Sathanas to assist [[GTVA Colossus]] in it's destruction. The Psamtik itself took part in none of these missions, only its fighters were present.

After this victory, the primary focus of the Psamtik was to locate Admiral Aken Bosch and his command frigate, the [[NTF Iceni]]. During this search, fighter wings from the Psamtik came across a second [[Knossos]] subspace portal. The Psamtik was called in to examine the portal, but moments after arriving, a second Sathanas Juggernaut came through the portal and destroyed the Psamptik, killing Admiral Khaffe and the entire crew.

Main Page

2005-11-14T17:58:02Z

FireCrack: Removed underscore from "User-made_Campaigns"

'''Welcome to the Freespace Wiki, the ultimate source for Freespace info on the web.'''


{| border=0 align=right cellpadding=4 cellspacing=0 width=30% style="margin: 0 0 1em 1em; background: #404040; border: 1px

#CC0500 solid; border-collapse: collapse; font-size: 95%;"
! style="color: white; height: 30px; background: #613030; 70%;"|''Retail Freespace''
|-
| [[Portal:Freespace 1|Freespace 1]]
|-
| [[Portal:Freespace 2|Freespace 2]]
|-
! style="color: white; height: 30px; background: #613030; 70%;"|''Freespace Source Code Project''
|-
| [[Getting Started(Main)|Getting Started]]
|-
| [[Multiplayer(Main)|Multiplayer]]
|-
| [[Command-Line_Reference|Command-Line Reference]]
|-
! style="color: white; height: 30px; background: #613030; 70%;"|''Modding Freespace''
|-
| [[Portal:Modding|General Modding]]
|-
| [[User-made_Campaigns|User-made Campaigns]]
|-
! style="color: white; height: 30px; background: #613030; 70%;"|''Freespace Universe''
|-
| [[Portal:FS Universe|The Universe]]
|-
! style="color: white; height: 30px; background: #613030; 70%;"|''Other''
|-
| [[Freespace Lingo]]
|-
| [[Freespace_Wiki:Community_Portal|Freespace Community]]
|-
| [[Getting Freespace]]
|-
| [[BitTorrent(Main)|BitTorrent]]
|}

The Freespace Wiki is designed to be a comprehensive source of data for the Freespace series of games, including information about the games themselves, the Freespace universe, and community activities, such as modding and the Source Code Project. It also contains help with some of the more common problems, such as setting up multiplayer and obtaining the freespace games, which can be quite difficult in stores.

Anyone can edit the Freespace Wiki, and we encourage you to do so, but please read our [[canon|Canon Policy]] for information on what sort of data should be submitted, and how to submit it, before you begin.

{| border=0 align=left cellpadding=4 cellspacing=0 width=65% style="margin: 0 0 1em 1em; background: #404040; border: 1px

#CC0500 solid; border-collapse: collapse; font-size: 95%;"
! style="color: white; height: 30px; background: #613030; 70%;"|''Featured Article of the Moment''
|-
|{{Featured Article}}
|}

Animation Code

2005-11-14T17:55:31Z

FireCrack: ReTweaked last edit to be more visible.

Known commonly as Bob's animation code as the code was written by Bobboau. Enables submodels defined in [[ships.tbl]] or in any related modular table to be animated in game. Animation code is included to the subsystem entry in similar manner as with [[Animation_Code#Setting_Turret_Angle|multipart turrets]]

==Animation Class==
*Animation classes are defined in submodels description
*Syntax: '''$animation=''' ''Class''
*'''Triggered'''
**Currently only supported animation class

===Animation Type===
*Animation type defines when the animation is used
*Currently supported animation types:
**'''"initial"'''
***Animation code is started when the mission begins
**'''"docking"'''
***Animation code is started when ship starts docking
**'''"docked"'''
***Animation code is started when ship is docked
**'''"primary bank"'''
***Animation code is started when a primary bank is fired
**'''"secondary bank"'''
***Animation code is started when a secondary bank is fired
**'''"door"'''
***Animation code starts when ship launches or retrives others through it's fighterbay.
*Syntax: '''$type=''' ''Type''

===Animation Sub-Type===
*Optional more accurate descriptor for the animation type
*For example used when defined primary bank is fired
*Syntax: '''+sub_type:''' ''Value'', (0 = 1st weapon bank, 1 = 2nd weapon bank, etc.)

===Animation Code===
*'''+delay:'''
**Defines how long til the trigger starts
**Syntax: ''Value'', (seconds)
*'''+reverse delay:'''
**
**Syntax: ''Value'', (seconds)
*'''+absolute angle:''' OR '''+relative angle:'''
**Defines the rotation degrees with three floats that give the x, y, and z. Absolute means in world terms; relative means relative to the ship. So a 90 degree angle on the ship would always be straight up in relative degrees; it would vary depending how the ship was rotated in absolute degrees.
**Syntax: ''Value,Value,Value'', (degrees)
*'''+velocity:'''
**Defines subobject rotation speed, in relative terms. Defined with x, y and z floats.
**Syntax: ''Value,Value,Value'', (meters)
*'''+acceleration:'''
**Defeines acceleration speed of subobject rotation. Defined with three floats, x, y and z
**Syntax: ''Value,Value,Value''
*'''+time:'''
**Defines time for object to rotate, move, whatever.
**Syntax: ''Value'', (seconds)
*'''$Sound:''' (Does not work with 'initial' animations)
**Defines sounds that are played with the animation
**'''+Start:'''
***Defines the sound that is played when animation starts
***Syntax: ????
**'''+Loop:'''
***Defines the sound that is played when animation is going on
***Syntax: ????
**'''+End:'''
***Defines the sound that is played when animation stops
***Syntax: ????
**'''+Radius:'''
***Defines the distance from the submodel where the sound is audible
***Syntax: ''Value'', (meters)

==Animation Examples==
===Setting Turret Angle===
*Animation code can be used to set multipart turrets barrel angle at the beginning of the mission
*'''Animation Class''' = triggered
**The only one available
*'''Animation Type''' = initial
**As we want the barrels to align themselves at the beginning of the mission
*'''Animation Code'''
**'''+relative_angle:''' is good for this purpose
**Notes about angles:
***First value is used to determine the turret's barrels deviation from the turrets normal. So barrel elevation in degrees is ( 90 - the first value ).
***Second value is used to determine the turret facing. With ''0'' the turret facing is in the normal setting and with ''180'' turn the turret completely around. Do note that turrets on the underside of the model normally face backwards so to get these turrets pointing to forward directin the second value has to be set to 180.

====Example====
$Subsystem: turret02,0.833,1.0
$Default PBanks: ( "Terran Turret" )
$animation=triggered
$type="inital"
+relative_angle: 90,180,0

[[Category:Tables]]

Animation Code

2005-11-14T17:54:18Z

FireCrack: Consolidated "initial" and "not initial"

Known commonly as Bob's animation code as the code was written by Bobboau. Enables submodels defined in [[ships.tbl]] or in any related modular table to be animated in game. Animation code is included to the subsystem entry in similar manner as with [[Animation_Code#Setting_Turret_Angle|multipart turrets]]

==Animation Class==
*Animation classes are defined in submodels description
*Syntax: '''$animation=''' ''Class''
*'''Triggered'''
**Currently only supported animation class

===Animation Type===
*Animation type defines when the animation is used
*Currently supported animation types:
**'''"initial"'''
***Animation code is started when the mission begins
**'''"docking"'''
***Animation code is started when ship starts docking
**'''"docked"'''
***Animation code is started when ship is docked
**'''"primary bank"'''
***Animation code is started when a primary bank is fired
**'''"secondary bank"'''
***Animation code is started when a secondary bank is fired
**'''"door"'''
***Animation code starts when ship launches or retrives others through it's fighterbay.
*Syntax: '''$type=''' ''Type''

===Animation Sub-Type===
*Optional more accurate descriptor for the animation type
*For example used when defined primary bank is fired
*Syntax: '''+sub_type:''' ''Value'', (0 = 1st weapon bank, 1 = 2nd weapon bank, etc.)

===Animation Code===
*'''+delay:'''
**Defines how long til the trigger starts
**Syntax: ''Value'', (seconds)
*'''+reverse delay:'''
**
**Syntax: ''Value'', (seconds)
*'''+absolute angle:''' OR '''+relative angle:'''
**Defines the rotation degrees with three floats that give the x, y, and z. Absolute means in world terms; relative means relative to the ship. So a 90 degree angle on the ship would always be straight up in relative degrees; it would vary depending how the ship was rotated in absolute degrees.
**Syntax: ''Value,Value,Value'', (degrees)
*'''+velocity:'''
**Defines subobject rotation speed, in relative terms. Defined with x, y and z floats.
**Syntax: ''Value,Value,Value'', (meters)
*'''+acceleration:'''
**Defeines acceleration speed of subobject rotation. Defined with three floats, x, y and z
**Syntax: ''Value,Value,Value''
*'''+time:'''
**Defines time for object to rotate, move, whatever.
**Syntax: ''Value'', (seconds)
*'''$Sound:'''
**Defines sounds that are played with the animation (Does not work with 'initial' animations)
**'''+Start:'''
***Defines the sound that is played when animation starts
***Syntax: ????
**'''+Loop:'''
***Defines the sound that is played when animation is going on
***Syntax: ????
**'''+End:'''
***Defines the sound that is played when animation stops
***Syntax: ????
**'''+Radius:'''
***Defines the distance from the submodel where the sound is audible
***Syntax: ''Value'', (meters)

==Animation Examples==
===Setting Turret Angle===
*Animation code can be used to set multipart turrets barrel angle at the beginning of the mission
*'''Animation Class''' = triggered
**The only one available
*'''Animation Type''' = initial
**As we want the barrels to align themselves at the beginning of the mission
*'''Animation Code'''
**'''+relative_angle:''' is good for this purpose
**Notes about angles:
***First value is used to determine the turret's barrels deviation from the turrets normal. So barrel elevation in degrees is ( 90 - the first value ).
***Second value is used to determine the turret facing. With ''0'' the turret facing is in the normal setting and with ''180'' turn the turret completely around. Do note that turrets on the underside of the model normally face backwards so to get these turrets pointing to forward directin the second value has to be set to 180.

====Example====
$Subsystem: turret02,0.833,1.0
$Default PBanks: ( "Terran Turret" )
$animation=triggered
$type="inital"
+relative_angle: 90,180,0

[[Category:Tables]]