FreeSpace Wiki - User contributions [en]

Alexander McCarthy

2006-02-16T04:26:42Z

204.145.242.1: /* Justification */

==General==
Nothing is known about the biography or service to the [[GTA]] prior to his appearance in FreeSpace: The Great War.

==Betrayal of the GTA==
:''Main Article:'' [[Heist of the Avenger Prototype]]

Lieutenant Alexander McCarthy stole the prototype of the [[GTW Avenger]] Laser cannon on the 15th January of 2335 while [[Galactic Terran Alliance|GTA]] forces were raiding the Vasudan cargo depot the prototypes were stored. He used a hijacked transport, designated as the GTT Omega to carry out his plans. After the mission, [[Galactic Terran Intelligence]] found proof that the GTT Omega did not follow its orders. Capturing McCarthy and retrieving the stolen plans became a primary objective for the [[Galactic Terran Alliance|GTA]] to complete.

The adamant traitor was tracked down and captured while he was transfering the [[GTW Avenger]] technology to his Vasudan contact, the PVFr Rasputin. During the fight, Terran pilots disabled his transport's engines, disallowing McCarthy from escaping. All of McCarthy's loyalist pilots were killed by the [[GTA]] and McCarthy himself was captured.

No canon information is known about the future of McCarthy, other than the fact that his trials were highly publicized. See [[Heist of the Avenger Prototype]] for details.

==Associates==
McCarthy tried to carry out his betrayal with the following force: 
Based on what is displayed in the game
*GTT Omega, crew wholly loyal to McCarthy. [[GTT Elysium|Elysium-class]] transport
*8 [[GTF Apollo|Apollo-class fighters]]
*PVFr Rasputin, [[GVT Isis|Isis-class]] transport

==Justification==

At the time of his theft, the existence of the [[Shivans]] was not common knowledge amongst the Terran population, but McCarthy alluded to them when he claimed "the Vasudans are the least of our worries." It is probable that he hoped to strengthen the Vasudans so that they would be better able to face the Shivans.

==Knowledge==

Given his knowledge of the truth behind the Ross 128 attack, his knowledge of the existence of the Avenger prototype, and his ability to carry out his theft of the plans from the depot at just the right time, it is quite likely (though not explicitly canon) that McCarthy had connections with high-ranking military authorities, perhaps even in Terran Intelligence.

==Misc notes==
In FreeSpace 2, McCarthy was implied in the Command briefing of the [[The Sixth Wonder|Sixth Wonder]] mission. It was clarified that the [[242nd Suicide Kings]] were responsible for his capture and the fact that it was their first combat assignment.

Alexander McCarthy

2006-02-16T04:22:12Z

204.145.242.1: /* Betrayal of the GTA */ no evidence of this

==General==
Nothing is known about the biography or service to the [[GTA]] prior to his appearance in FreeSpace: The Great War.

==Betrayal of the GTA==
:''Main Article:'' [[Heist of the Avenger Prototype]]

Lieutenant Alexander McCarthy stole the prototype of the [[GTW Avenger]] Laser cannon on the 15th January of 2335 while [[Galactic Terran Alliance|GTA]] forces were raiding the Vasudan cargo depot the prototypes were stored. He used a hijacked transport, designated as the GTT Omega to carry out his plans. After the mission, [[Galactic Terran Intelligence]] found proof that the GTT Omega did not follow its orders. Capturing McCarthy and retrieving the stolen plans became a primary objective for the [[Galactic Terran Alliance|GTA]] to complete.

The adamant traitor was tracked down and captured while he was transfering the [[GTW Avenger]] technology to his Vasudan contact, the PVFr Rasputin. During the fight, Terran pilots disabled his transport's engines, disallowing McCarthy from escaping. All of McCarthy's loyalist pilots were killed by the [[GTA]] and McCarthy himself was captured.

No canon information is known about the future of McCarthy, other than the fact that his trials were highly publicized. See [[Heist of the Avenger Prototype]] for details.

==Associates==
McCarthy tried to carry out his betrayal with the following force: 
Based on what is displayed in the game
*GTT Omega, crew wholly loyal to McCarthy. [[GTT Elysium|Elysium-class]] transport
*8 [[GTF Apollo|Apollo-class fighters]]
*PVFr Rasputin, [[GVT Isis|Isis-class]] transport

==Justification==

At the time of his theft, the existence of the [[Shivans]] was not common knowledge amongst the Terran population, but McCarthy claimed to be doing it to strengthen the Vasudans so that they could both face a far greater foe, now recognized to have been the Shivans, which were indeed a much more dangerous enemy than the Vasudans had ever been. Though history likely exonerated McCarthy,, in light of his motivations and the eventual alliance with the Vasudans, it is unlikely he was prematurely released as a result.

==Misc notes==
In FreeSpace 2, McCarthy was implied in the Command briefing of the [[The Sixth Wonder|Sixth Wonder]] mission. It was clarified that the [[242nd Suicide Kings]] were responsible for his capture and the fact that it was their first combat assignment.

Heist of the Avenger Prototype

2006-02-16T04:19:07Z

204.145.242.1:

{{spoiler}}
*FreeSpace 1

There were at least three "heists" of the Avenger, all part of the same overall historical event: the defection of Lieutenant [[Alexander McCarthy]] to the Vasudans in 2335.

===Acquisition of the plans by the Vasudan cargo depot in Antares===

Somehow plans for the Avenger prototype cannon were transferred to the depot. It is likely that McCarthy arranged this in preparation for the delivery of the plans to Vasudan Command (because the easiest way for security breaches to happen is through an inside man) - Scenario A, but it is also possible that the Vasudans managed to acquire the plans on their own - Scenario B.

===Removal of the plans from the depot by the GTT Omega===

Terran Intelligence detected unusual activity at the depot and the Galatea was assigned to capture it. (Although Intelligence may not have known that the depot was storing the prototypes, they suspected the depot was militarily significant.) During the mission, the GTT Omega removed the plans from the depot before the GTA could completely secure the area. It is not known whether McCarthy was actually aboard the Omega, but it is known that he arranged this heist.

Interpretation of this heist follows from the first. If Scenario A is true, then McCarthy's removal of the plans was simply ensuring that his arrangement did not fall apart and that delivery of the plans to Vasudan Command was still possible. If Scenario B is true, then McCarthy seized the opportunity provided by the commotion at the depot to steal the plans.

Whatever the case, arranging for the GTT Omega to steal the plans right out from under the noses of the GTA during a GTA capture operation was a risky move, and if the GTA did not know about McCarthy's objectives before then, they would certainly have known at that time. If Scenario A is true and if the GTA had not conducted the capture operation, then it is entirely plausible for McCarthy to have gotten away with it.

===Recovery of the plans by the GTA===

Intelligence became aware of McCarthy's plot and was able to capture one of McCarthy's accomplices. Between this and the information gathered from Vasudan agents under Terran control, Intelligence was able to learn a great deal about McCarthy's plans. The Galatea was assigned to lead an attack on McCarthy's forces and was successful in capturing McCarthy, his Vasudan contact, and the stolen Avenger prototype.

===McCarthy's motives===

McCarthy's motives were apparently more than simply financial; he knew that the attack on Ross 128 was far more of a concern than the war against the Vasudans. Perhaps he hoped that delivering the Avenger to the Vasudans would to fight on an equal playing field with the Terrans would improve their odds against the Shivans.

It is likely that history exonerated McCarthy's actions, especially considering that the GTA eventually shared the Avenger with the PVN anyway. We know from FS2 that the McCarthy trials were well-publicized, so it is likely that the trials took place after or during the Great War and were quite dramatic. There were probably a great many questions raised about loyalty to the GTA vs. acting in the best interests of the Terran and Vasudan species.

[[Category:History]]

High Noon

2006-02-16T03:22:00Z

204.145.242.1: /* Walkthrough */

{|- cellpadding="8" style="background:#000000;" align="center"
| [[Bearbaiting|Previous Mission]]
| [[Campaign Walkthrough]]
| [[Return to Babel|Next Mission]]
|-
|}

ACT 3, MISSION 2

Fighter squadron: 
Description:

----
==Background==

==Walkthrough==

This can be the easiest mission in the whole game if you performed well in the previous mission. If not, you still have work to do because the Sathanas can take out the Colossus even with one beam turret operational. Fortunately, due to differences in timing, FPS, maneuvering, etc., the Colossus is usually safe once you're down to one turret. If the flak guns are still operational you may want to order your wingmen to take them out for you.

The Basilisks can be really annoying, but you can usually take several out with Trebuchets at long range before you engage the Sathanas. Fortunately, there are only eight of them, as opposed to the multitude in Bearbaiting, so when the second wave arrives, just order your wingmen to cover you. If you've gotten all four turrets, of course, feel free to take them out yourself to get credit for the extra kills.

You can ensure you get the kill for the Sathanas by making sure you inflict more damage on it than any of your wingmen. If your wingmen are busy with the Basilisks or if you've ordered them to depart, this should be pretty easy. After a 10 minute exchange of beam fire, the Sathanas throws in the sponge.

==Notable ships present==

The Fog of War

2006-02-16T03:07:40Z

204.145.242.1: /* Walkthrough */

{|- cellpadding="8" style="background:#000000;" align="center"
| [[Endgame|Previous Mission]]
| [[Campaign Walkthrough]]
| [[A Monster in the Mist|Next Mission]]
|-
|}

ACT 2, MISSION 7

Fighter squadron: 
Description:

----
==Background==

==Walkthrough==

You have to cruise the nebula searching for gas miners ([[SSG Rahu]]-class) and sentries. The miners are the primary goal to take out. I cannot give you any useful advice here, you have to find the miners on your own. All I can suggest you here is to use the [[GTW Maxim]] against the miners and the [[GTM Harpoon]]s against the fighters (if you encounter some of them by chance). You can achieve a secondary goal by destroying the sentries. 
The Vasudan AWACS ([[GVA Setekh]]-class) can provide you long range sensors. You can take advantage of this, and destroy the miners. After you accomplish the primary goal, the Vasudan [[GVCv Sobek]]-class corvette (GVCv Tatenen) falls under attack by [[Shivan]] bombers. Rush back to get some kills and when a large Shivan vessel jumps in, hit your thrusters and get out of the firing range of it. You have no chance to defend the Tatenen. Jump out after the Vasudan corvette goes down.

==Notable ships present==

==New equipment==
*[[Freespace_2_Era_Craft#Fighters_2|Vasudan fighters]] (most of them)
*[[GTW Mekhu HL-7]]
*[[GTW Maxim]]

The Sicilian Defense

2006-02-16T03:06:46Z

204.145.242.1: /* Walkthrough */

{|- cellpadding="8" style="background:#000000;" align="center"
| [[The King's Gambit|Previous Mission]]
| [[Campaign Walkthrough]]
| [[Endgame|Next Mission]]
|-
|}

ACT 2, MISSION 5

Fighter squadron: 
Description:

----
==Background==

==Walkthrough==

This is also a bombing run mission. I find it more difficult than the previous one. Your ability of survival is better tested in here than in the previous one. The NTD Vindicator ([[GTD Orion]]-class) is directly ahead of you. Target its beam cannons, and take them out. I belive destroying the Vindicator won't mean much trouble. But the thing that happens after this! More [[NTF]] warships jump in and attack you. 
The Vasudans send in a [[GVCv Sobek]]-class corvette (GVCv Hyksos) to assist you. You have to defend this vessel. Losing the corvette is a serious decrease in your chances. Taking down the anti-fighter beam turrets on the hostile warships is the key to survive. Or, you can head against their weapon subsystems to decrease their accuracy. The fighters can also mean trouble here, head against them after you have taken down the dangerous turrets of the warships. Losing every single of your wingmen also decreases your chances.

==Tips==

As with [[Slaying Ravana]], the Sobek offers excellent flak and beam cover, though in this mission there are too many threats to simply sit back and watch. The problem here is that the Hyksos stands a serious chance of being destroyed by the Vindicator. To prevent this, take out some of the Vindicator's portside heavy beam turrets.

==Notable ships present==

==New equipment==
*[[GTM Piranha]]

The Sixth Wonder

2006-02-16T03:00:20Z

204.145.242.1: /* Walkthrough */

{|- cellpadding="8" style="background:#000000;" align="center"
| [[Slaying Ravana|Previous Mission]]
| [[Campaign Walkthrough]]
| [[Into the Maelstrom|Next Mission]]
|-
|}

ACT 1, MISSION 8

Fighter squadron: 
Description:

----
==Background==

==Walkthrough==

I suggest you use the [[GTW Subach HL-7]] in both of your primary banks. Do have no need for the [[GTW Prometheus R]] in this mission. Also, arm yourself with a bank of [[GTM Harpoon]] and a bank of [[GTM Tempest]]. The mission is to save the [[GTI Arcadia]]-class installation (GTI Enif Station). You begin a few clicks away from the installation. Start approaching on it, and target the [[GTF Hercules]] fighters, who mean danger to the escaping civilian freighters. If you fail to take them out quickly, you lose a civilian freighter, and you fail to accomplish the secondary goal. 
A [[GTC Leviathan]]-class cruiser (NTC Cato) is attacking the station with its beam cannon. You should take that main beam cannon down to prevent the hostile cruiser from attacking the station dangerously. The [[GTM Tempest]] missile has a good use here. Fire at will while the beam cannon is in your reticle, and once the beam cannon is down, you should get as far from the cruiser as possible. It is too dangerous for you with 4 anti-fighter beam cannons. Even if you disarm the cruiser from all of its beam cannons, you won't have time to destroy it because enemy bombers jump in and attack the station. You should divert all your power to engines and approach on the bombers. 
With the agility of the [[GTF Perseus]], you can easily reach the [[GTB Zeus]]-class hostile bombers before they could fire their warheads onto the station. Even if they do so, you can destroy the bomb by hitting it. Press 'B' to target the nearest hostile bomb. Several waves of hostile bombers and fighters jump in, but they do not mean much danger for you. Concentrate on the bombers. While you are fighting the bombers, an additional [[GTCv Deimos|hostile corvette]] (NTCv Hawkwood) jumps in, but you do not have to do special efforts against it. A huge GTVA warship ([[GTVA Colossus]]) jumps in to assist the station. After the Colossus arrives, you only have to watch as she takes down the hostile corvette with a single shot.

==Tips==

Don't order any of your wingmen to ignore the corvette, or else the Colossus will ignore it too when she jumps in (making the mission impossible to complete). This is due to a bug in Freespace. If your wingmen keep attacking the corvette, distract them with other orders, such as attacking the Cato or the bombers.

==Notable ships present==

==New equipment==
*[[GTF Perseus]]

The Romans Blunder

2006-02-16T02:57:10Z

204.145.242.1: /* Walkthrough */

{|- cellpadding="8" style="background:#000000;" align="center"
| [[The Place of Chariots|Previous Mission]]
| [[Campaign Walkthrough]]
| [[A Lion at the Door|Next Mission]]
|-
|}

ACT 1, MISSION 3

Fighter squadron: 
Description:

----
==Background==

==Walkthrough==

This is a more difficult mission. You seem to have no chance of catching the [[NTF Iceni]], and it leaves the area. After a small conversation between the pilots and Command, two enemy freighters jump in with cargo, who are escorted by some fighters. Prioritize the fighters. Once they are gone, destroy the freighters. Do not splurge much effort at the containers, they are always destroyed by the shockwave of the explosion of the freighter carrying it. 
After the freighters and the fighters are down, two [[NTF]] cruisers (NTC Glorious, NTC Imporvious) jump in and make your day difficult. They have fighter assistance as well. Try to lure them away by pulling back at the time they begin approaching on you. Without the assistance of the cruisers, they do not stand much long against you and your wingmen. Attack the cruisers after the fighters. The Glorious is the weaker one, target the anti-fighter beam(s) on it, and attack it with the [[GTM Tempest]]s. Fire at will with your rockets to destroy the cruiser. 
The Impervious is tougher ([[GTC Leviathan]]-class), the [[GVD Psamtik]] jumps in and will destroy it on her own. After these cruisers have been destroyed, you can leave the area. The mission is more difficult to survive than completing its mission goals. Disarm the cruisers of their anti-fighter beam turrets first.

==Tips==

The Psamtik won't arrive until you take out the cruisers' fighter cover, so make sure you do that first.

==Notable ships present==
[[NTF Iceni]] 
[[GVD Psamtik]]

Surrender, Belisarius!

2006-02-16T02:53:07Z

204.145.242.1: /* Walkthrough */

{|- cellpadding="8" style="background:#000000;" align="center"
| Previous Mission
| [[Campaign Walkthrough]]
| [[The Place of Chariots|Next Mission]]
|-
|}

ACT 1, MISSION 1

Fighter squadron: [[53rd Hammerheads]] 
Description: The 53rd Hammerheads, GTD Aquitaine, must defend a convoy of Vasudan transports escaping Cygnus Prime.

----
==Background==
The GTVA are evacuating Cygnus Prime. Vasudan refugees are leaving the system in transport. The Aquitaine launches the Hammerheads to reinforce a fleeing Vasudan convoy.

==Walkthrough==

This is an easy mission, quite good as a warm-up to the game. You have to defend a convoy of Vasudan transports, designated Kappa wing. Not many [[NTF]] forces attack them, just a few [[GTF Hercules]]-class fighters. In this mission, you can learn how to put the [[GTM MX-64]] Rockeye FnF (Fire & Forget) missile to good use. Most pilots underestimate these missiles, and prefer the [[GTM Tempest]] dumbfire rockets. 
You can lose at maximum of one Vasudan transport. However, keeping them both alive is preferred, of course. This is an easy standard to attain, just fire continually and accurately, and both transports will survive. Once the transports reach their destination waypoint, a [[ GVD Hatshepsut]]-class Vasudan destroyer, the [[GVD Psamtik]], jumps in. 
After her arrival, an enemy warship, the [[GTCv Deimos]]-class NTCv Belisarius, also jumps in. Hit the Belisarius at least once before the Psamtik slashes her in half, and you will get the whole score for that kill (note: some older versions of FSO did not do this because of a bug). You can make your approach while the Psamtik is trying to convince the captain of the Belisarius to surrender. If your hull strentgh is low, do not risk this trick, as the Belisarius is well-armed with anti-fighter defenses.

==Notable ships present==
*[[GVD Psamtik]]
*NTCv Belisarius

==New equipment==
*[[GTF Myrmidon]]
*[[GTW Subach HL-7]]
*[[GTM MX-64]]
*[[GTM Tempest]]

Slaying Ravana

2006-02-16T02:51:13Z

204.145.242.1:

{|- cellpadding="8" style="background:#000000;" align="center"
| [[The Great Hunt(FS2)|Previous Mission]]
| [[Campaign Walkthrough]]
| [[The Sixth Wonder|Next Mission]]
|-
|}

ACT 1, MISSION 7

Fighter squadron: 
Description:

----
==Background==

==Walkthrough==

This mission tests your abilities in bombing runs. This one is quite difficult for the first run, so pay attention at anything you are doing. You have to choose a bomber all the way, I suggest you the [[GTB Medusa]], because it has the best survival chance, and it is able to carry a quite good amount of [[GTM Cyclops]] warheads. Arm yourself full of Cyclops. Hit your burners, but do not attack the [[SD Ravana]] right at the beginning. There are [[SF Basilisk]]-class fighters coming in front of you. Take them out with your lasers. After they are gone, go against the Ravana. 
Order you wingmen to disarm her. Have a bank of [[GTM Cyclops]] selected, target one of the closest subsystems of the Ravana. Wait until your computer acquires a lock, and shoot out your bombs. Making sure your warhead won't be hit by the lasers of the Ravana, you have to destroy the Weapons subsystem of this ship. It makes it far more inaccurate. If she fires at you with her anti-fighter beams, press R and hopefully, your attacker will be targeted. Head against it and fire the next salvo of [[GTM Cyclops]] at it. Change to another bank as soon as you fired a pair of bombs from another one. You only have to target the ship again without waiting for the 15 penalty seconds of the same bank. It is the mania of the game to prevent you from shooting powerful bombs quickly after each other. By changing the secondary bank, you can avoid this penalty.

==Tips==

I played this mission countless times using the "brute force" method of fire your bombs, lean on your afterburner, and hope you don't get shot at before I realized how much easier the mission can be if you think intelligently. Just use the Sobek! It provides excellent flak and beam cover for you to recharge and rearm between bombing runs. You can even just park there and wait for the Sobek to take out the Ravana itself, if that's your thing - just be sure to take out any beam turrets or fighters targeting it.

==Notable ships present==

==New equipment==
*[[GTB Boanerges]]
*[[GTM Cyclops]]

SD Demon

2006-02-04T00:28:06Z

204.145.242.1: /* Veteran Comments */

{{FS12_Ships}}
{{shipimage|image=http://www.descent-freespace.com/goodies/gallery/ships/tn_sddemon_tga.jpg|caption=The SD Demon}}

==Description:==

===FS1 Tech Room Description===
While the Demon-class Destroyer is easily one of the most massive ships we have yet seen, it is not the biggest or most powerful in the Shivan armada. However, it is still quite dangerous, with a plethora of missile turrets and two full squadrons of fighters. It is suggested that these capital ships be destroyed by bombers, as all cruisers that have attempted to engage a Demon have been destroyed. 
The Demon is a Class A threat in any allied system.

===FS2 Tech Room Description===
The SD Demon class of Shivan destroyers is much smaller than the Lucifer class but very heavily armed and extremely dangerous. Demons are known to carry numerous wings of fighters and bombers.

===Developer Notes===
None

===Veteran Comments===
''The sheer number of missile batteries on a Demon can make it very annoying indeed in FS1. In FS2 these missiles are less of a threat, and the posistioning of the Demon's flak guns and AAA beams makes it possible to knock out one weapon and leave much of that side of the ship defenseless. Unlike the Ravana, however, expect the Demon to take some severe punishment before it goes down. Also expect those main battery turrets to take severe punishment before being knocked out.''

''Surprisingly, the Demon's hull strength increases sixty percent between FS1 and FS2. This inadvertent bug undoubtedly made a few FSPort missions much harder. Now that the Port team knows of the problem, it will be fixed in the next release. :)''

==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/160 000
|-
| [[Technical_Terms_and_Definitions#Shields|Shields]]
| N/A
|-
| '''[[Technical_Terms_and_Definitions#Length|Length]]'''
| 2139 m
|}

===Armaments===

*'''[[Technical_Terms_and_Definitions#Turrets|Turrets]]'''
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=2 style="background:#351515;"| '''Freespace 1'''
| colspan=2 style="background:#300505;"| '''Freespace 2'''
|- align="center"
| style="width:120px" |Turret Type
| style="width:60px" |Amount
| style="width:120px" |Turret Type
| style="width:60px" |Amount
|- align="center"
| Shivan Turret Laser
| 18
| Shivan Turret Laser
| 10
|- align="center"
| Shivan Megafunk Turret
| 3
| Shivan Megafunk Turret
| 2
|- align="center"
| FighterKiller
| 5
| FighterKiller
| 5
|- align="center"
|
|
| Standard Flak
| 4
|- align="center"
|
|
| Antifighter Beam
| 2
|- align="center"
|
|
| Small Red Beam
| 1
|- align="center"
|
|
| Large Red Beam
| 2
|}

GTB Zeus

2006-02-04T00:08:49Z

204.145.242.1: /* Veteran Comments */

{{FS12_Ships}}
{{shipimage|No Picture|caption=The GTB Zeus}}

==Description:==

===FS1 Tech Room Description===
Another product of GTI R&D, the Zeus strike bomber is a worthy successor to the Athena. It's balanced design and increased reactor capacity give it remarkable speed for a bomber, yet still remains capable of carrying the powerful Tsunami bombs. These features will make the Zeus a versatile and effective weapon against capital ships.

===FS2 Tech Room Description===
The GTB Zeus is the fastest of all currently active GTVA bombers. It replaced the fleet's old Athena bombers as they were mothballed during the years following the Great War. Though slightly slower than the Athena, the Zeus's heavier armor and armament give it a much better battlezone survivability rate. Many of the Zeus wings in the GTVA fleet defected to the NTF during the initial stages of the rebellion.

===Developer Notes===
Excellent for hit-and-run bombing. Can carry Tsunamis. Good afterburner supply.

===Veteran Comments===

''The Zeus just can't hack it. The decrease in speed, shields, and manuverablity, and the increase in its thickness and hence target profile are all apparently minor, but they all magnify each other. In the end, it turns out that the Zeus is significantly less survivable then the Athena. If you really want a bomber and don't need too much muscle, you're probably going to be safer in a Medusa. (By the time FS2 rolls around, just plain forget the Zeus exists and grab that Artemis. It's godly in comparison.) If you're an Athena veteran and used to flying it as if it were a fighter, don't get a Zeus.'' 
''The Zeus offers good maneuverability, relatively high speed and four primary weapons which make it ideal against fighters if you do not need a large amount of bombs. Its warhead capacity is the lowest of all [[Second Great War]]-era craft, but as compensation, aiming with its laser guns is easy and the ability to take Tempests and Harpoons make it even more effective. Against flak fire, it does not hold out for long. The Zeus is practically a tactical bomber, which can defend itself until it releases all its Trebuchets or Stilettoes, eliminating turrets on hostile warships and pave the way for heavier bombers to deliver their heavy bombs.'' 
''As for compability, the Zeus is a good choice as well: The Prometheus S and the UD-8 can be chosen as well as anti-fighter warheads, Trebuchets, Stilettoes and Infyrnos.'' 
''I very much disagree with the first commenter: the Zeus is excellent for what it was designed for. It's a strike bomber, which means that it's used for tactical as opposed to destructive bombing. If you need to take out a few capships, obviously the Medusa or Ursa would be a better choice. But if you need to knock out subsystems or you need to be able to dogfight as well as drop a few bombs here and there, the Zeus is the way to go. Summary: The Medusa is better for destroying lots of ships, but you wouldn't want to dogfight in it. The Athena is better for dogfighting, but it can't carry the Tsunami. Ergo the Zeus fills an important vacancy in the FS1 bomber lineup.

==Performance:==
===Statistics===
{|
|-
| style="width:200px" | '''[[Technical_Terms_and_Definitions#Type|Type]]'''
| style="width:200px" | Stealth Bomber/Strike Bomber (FS1/FS2)
|-
| '''[[Technical_Terms_and_Definitions#Manufacturer|Manufacturer]]'''
| Dynamic Metamer
|-
| '''[[Technical_Terms_and_Definitions#Manuverablity|Manuverability]]'''
| Poor/Average
|-
| '''[[Technical_Terms_and_Definitions#Max Velocity|Max Velocity]]'''
| 55.0 - 75.0 mps
|-
| '''[[Technical_Terms_and_Definitions#Max Afterburner Velocity|Max Afterburner Velocity]]'''
| 110.0 mps
|-
| '''[[Technical_Terms_and_Definitions#Armor|Armor]]'''
| High/Medium
|-
| [[Technical_Terms_and_Definitions#Hitpoints|Hitpoints]]
| 200
|-
| [[Technical_Terms_and_Definitions#Shields|Shields]]
| 450
|-
| '''[[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'''
| style="background:#300505;"| '''Freespace 2'''
|- align="center"
| style="width:40px" |Bank
| style="width:60px" |Guns
| style="width:160px" |Standard Loadout
| style="width:240px" |Standard Loadout
|- align="center"
| 1st
| 2
| [[GTW Avenger|Avenger]]
| [[GTW Prometheus R|Prometheus R]]
|- align="center"
| 2nd
| 2
| [[GTW Flail|Flail]]
| [[GTW Prometheus R|Prometheus R]]
|- align="center"
| colspan=3| Compatible Primaries
| Compatible Primaries
|-
| colspan=3| [[GTW ML-16|ML-16 Laser]], [[GTW Disruptor|Disruptor]], [[GTW Avenger|Avenger]], [[GTW Flail|Flail]], [[GTW Prometheus|Prometheus]], [[GTW Leech Cannon|Leech Cannon]], [[GTW Shield Breaker|S-Breaker]]
| [[GTW Subach HL-7|Subach HL-7]], [[GTW Akheton SDG|Akheton SDG]], [[GTW Prometheus R|Prometheus R]], [[GTW Prometheus S|Prometheus S]], [[GTW Morning Star|Morning Star]], [[GTW Circe|Circe]], [[GTW Lamprey|Lamprey]], [[GTW Maxim|Maxim]]
|}
*'''[[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'''
| style="background:#300505;"| '''Freespace 2'''
|- align="center"
| style="width:40px" |Bank
| style="width:60px" |Capacity
| style="width:160px" |Standard Loadout
| style="width:240px" |Standard Loadout
|- align="center"
| 1st
| 40
| [[GTM Phoenix V|Phoenix V]]
| [[GTM Trebuchet|Trebuchet]]
|- align="center"
| 2nd
| 40
| [[GTM Stiletto|Stiletto]]
| [[GTM Stiletto II|Stiletto II]]
|- align="center"
| 3rd
| 40
| [[GTM Synaptic|Synaptic]]
| [[GTM Piranha|Piranha]]
|- align="center"
| colspan=3| Compatible Secondaries
| Compatible Secondaries
|-
| colspan=3| [[GTM D-Missile|D-Missile]], [[GTM Fury|Fury]], [[GTM Hornet|Hornet]], [[GTM Interceptor|Interceptor]], [[GTM Phoenix V|Phoenix V]], [[GTM Synaptic|Synaptic]], [[GTM Stiletto|Stiletto]], [[GTM Tsunami|Tsunami]], [[GTM EM Pulse|EM Pulse]], [[GTM Cluster Bomb|Cluster Bomb]]
| [[GTM EMP. Adv|Emp. Adv]], [[GTM Tempest|Tempest]], [[GTM Hornet|Hornet]], [[GTM Harpoon|Harpoon]], [[GTM Trebuchet|Trebuchet]], [[GTM Piranha|Piranha]], [[GTM Stiletto II|Stiletto II]], [[GTM Infyrno|Infyrno]], [[GTM Cyclops|Cyclops]]
|}

Talk:Node Inconsistencies

2006-02-03T23:47:36Z

204.145.242.1:

===Talania===

Further study into the topic has provided enough evidence that Talania was NEVER a canon star system. There is, at the very least, no evidence for it, the lack of a node map containing it being the biggest bit. At best, Talania as a star system is a concoction of various campaign builders and an overactive imagination. I apologize for making a big deal out of this. -- Eishtmo

There is indeed evidence for it - see the Leviathan FS1 tech entry: "...production was started up again after the defeat at the Talania system..." At the very least, we know it exists. Unfortunately we have no further information on what or where it is. -- Goober5000

A nodemap created for the campaign series Cardinal Spear and Cardinal Spear: Vega (1999) was designed to match the appearance of the Volition nodechart. However, the notion that the Talania system exists in the same sense as the Jovian system is an idea that has become more accepted. This would mean that Talania would be a planet in a system at the front of the V-T war, either Beta Aquilae, Antares, or Vega. -- Ace

"More accepted"? I don't think so; I don't think the majority of people care one way or the other. We seem to be the only three people with any more than a passing interest in finding out more about it. ;) Regardless, nowhere in Freespace is the term "system" used to refer to a planet with moons; it's always used to refer to a star with planets. Therefore if Talania exists, it's a star system, not a planet. -- Goober5000

Node Inconsistencies

2006-02-03T23:42:22Z

204.145.242.1: /* Apocryphal Validity */

Those continuation flaws that occur regarding jump nodes between FreeSpace: The Great War and FreeSpace 2 are called '''node inconsistencies'''.

There are a number of jump node connections that are used in [[Portal:Freespace_1|Freespace]] but are not illustrated on the [[Official Volition Node Map]]. They are listed below, along with their references and how valid you should consider them. [[Volition]] says that the [[Official Volition Node Map|node map]] should overrule other references.

==Pseudocanon Validity==

These connections are used in-game and would be considered canon if it weren't for the official map.

===[[Beta Cygni]] - [[Ikeya]] (probably a mistake; see description)===
Used in First Strike (SM1-10). [[Famous Persons|Admiral Wolf]] says that the [[SC Taranis|Taranis]] has been chased from the [[Beta Cygni]] system back to the [[Ikeya]] system, and the [[SC Taranis|Taranis]] is fleeing to the [[Beta Cygni]] node during the mission itself. It is very likely, however, that this is a mistake. The cutscene immediately preceding this mission (not to mention the official node map itself) shows that the only subspace node out of [[Ikeya]] leads to [[Ribos]]. Additionally, during the mission, Freighter Halkins tows the cruiser to Tombaugh Installation, which is located in [[Ribos]]. It is probable that the mission designer just confused [[Ribos]] with [[Beta Cygni]].

===[[Beta Cygni]] - [[Ribos]]===
Used by the shield prototype convoy in The Hammer and the Anvil (SM1-08). The shield prototypes are escorted from the Cygni Installation in [[Beta Cygni]] to the [[Ribos]] node.

===[[Deneb]] - [[Altair]]===
Used by the player's squadron and Omega wing. The node is seen in Reaching the Zenith (SM3-04) and used in Running the Gauntlet (SM3-05) and Black Omega (SM3-06). Xenolinguists are transported to [[Altair]] to retrieve the ancient records and back to [[Deneb]] to rejoin the Terran fleet.

===[[Sirius]] - [[Delta Serpentis]]===
Used by the [[GTD Bastion]] in Clash of the Titans (SM3-07). The Bastion tries to intercept the [[SD Lucifer]] before it can reach [[Sol]]. Also seen in CB_starmap13 and CB_starmap14.

==Apocryphal Validity==

Although the [[Talania]] system is referenced in the FS1 ship database, no reference to it appears on the [[Official Volition Node Map]]. According to Eishtmo, however, Volition released a rudimentary node map around the time FS1 came out that had this system illustrated on it. This node map has unfortunately disappeared and has yet to resurface.

===[[Talania]] - [[Beta Aquilae]]===
===[[Talania]] - [[Vega]]===

(For comments on this system, see the discussion page.)

==Command Briefing Animation Validity==

These connections are shown in the animations that accompany the FS1 command briefings. 

===Jump Nodes===

====[[Beta Aquilae]] - [[Sol]]====
Seen in CB_starmap06 and in CB_starmap08

====[[Ribos]] - [[Betelgeuse]]====
Seen in CB_starmap06, although Betelgeuse isn't labeled

====[[Ribos]] - [[Vega]]====
Seen in CB_starmap08, although the jump line isn't explicitly drawn

====[[Sol]] - [[Deneb]]====
Seen in CB_starmap08

====[[Vega]] - [[Antares]]====
Seen in CB_starmap04, although the jump line isn't explicitly drawn 

===Animation Usage===

====CB_starmap04====
Is seen in La Ruotta della Fortuna (SM2-03), showing ships being attacked in Vega and subsequently jumping to Deneb and Antares. Admiral Wolf says that the Vasudan fleet is retreating after having been decimated by the [[Hammer of Light]].

====CB_starmap06====
Is seen in Tenderizer (SM2-05), showing several possible jumps from Ribos through the surrounding systems. Admiral Wolf says that although there are dozens of star systems accessible from Ribos, the GTA can't afford to give up one more inch to the Shivans.

====CB_starmap08====
Is seen in Enter the Dragon (SM2-07) and in Playing Judas (SM2-08), showing the Lucifer jumping from Ribos to Vega and the Galatea jumping from Beta Aquilae to Sol to Deneb. In Enter the Dragon, Admiral Wolf says that fighter patrols have detected advance ships from the Lucifer fleet approaching Vasuda Prime. In Playing Judas, Admiral Wolf says that the Galatea has entered Deneb to guard the system against the Deneb prong of the Shivan attack on Vasuda. 

==Hearsay Validity==

These connections are mentioned in the FS1 briefings but are not shown visually.

===[[Betelgeuse]] - [[Antares]]===
Mentioned in The Field of Battle (SM1-02). Admiral Wolf says that Vasudans have been conducting strikes on Terran convoys en route to the Betelgeuse-Antares jump point. This jump corridor may also be alluded to in Paving the Way (SM1-06) when Admiral Wolf says that standard procedure would have the Galatea circumvent the Antares-Beta Cygni jump corridor and make two jumps. Jumping from Antares to Betelgeuse to Beta Cygni would satisfy this requirement. (But so would Antares to Ribos to Beta Cygni, through the pseudocanon Ribos-Beta Cygni corridor.)

==Implied Validity==

These connections are only implied, not described or illustrated.

===[[Beta Aquilae]] - [[Vasuda]]===
Implied in Tenderizer (SM2-05). Admiral Wolf says that the Galatea will be moving to Beta Aquilae in case the Shivans decide to attack Vasuda Prime through there. This implies that there is a jump corridor from Beta Aquilae to Vasuda. The shortest alternate route, starting from Beta Aquilae, involves three jumps: Vega to Deneb to Vasuda, or Sol to Deneb to Vasuda. (Of course, since they start in Antares, the Shivans could simply pulverize the Terran blockade and jump directly to Vasuda, but for whatever reason they don't decide to do that.)

Node Inconsistencies

2006-02-03T23:40:09Z

204.145.242.1: /* Beta Cygni - Ikeya (probably a mistake) */

Those continuation flaws that occur regarding jump nodes between FreeSpace: The Great War and FreeSpace 2 are called '''node inconsistencies'''.

There are a number of jump node connections that are used in [[Portal:Freespace_1|Freespace]] but are not illustrated on the [[Official Volition Node Map]]. They are listed below, along with their references and how valid you should consider them. [[Volition]] says that the [[Official Volition Node Map|node map]] should overrule other references.

==Pseudocanon Validity==

These connections are used in-game and would be considered canon if it weren't for the official map.

===[[Beta Cygni]] - [[Ikeya]] (probably a mistake; see description)===
Used in First Strike (SM1-10). [[Famous Persons|Admiral Wolf]] says that the [[SC Taranis|Taranis]] has been chased from the [[Beta Cygni]] system back to the [[Ikeya]] system, and the [[SC Taranis|Taranis]] is fleeing to the [[Beta Cygni]] node during the mission itself. It is very likely, however, that this is a mistake. The cutscene immediately preceding this mission (not to mention the official node map itself) shows that the only subspace node out of [[Ikeya]] leads to [[Ribos]]. Additionally, during the mission, Freighter Halkins tows the cruiser to Tombaugh Installation, which is located in [[Ribos]]. It is probable that the mission designer just confused [[Ribos]] with [[Beta Cygni]].

===[[Beta Cygni]] - [[Ribos]]===
Used by the shield prototype convoy in The Hammer and the Anvil (SM1-08). The shield prototypes are escorted from the Cygni Installation in [[Beta Cygni]] to the [[Ribos]] node.

===[[Deneb]] - [[Altair]]===
Used by the player's squadron and Omega wing. The node is seen in Reaching the Zenith (SM3-04) and used in Running the Gauntlet (SM3-05) and Black Omega (SM3-06). Xenolinguists are transported to [[Altair]] to retrieve the ancient records and back to [[Deneb]] to rejoin the Terran fleet.

===[[Sirius]] - [[Delta Serpentis]]===
Used by the [[GTD Bastion]] in Clash of the Titans (SM3-07). The Bastion tries to intercept the [[SD Lucifer]] before it can reach [[Sol]]. Also seen in CB_starmap13 and CB_starmap14.

==Apocryphal Validity==

Although the [[Talania]] system is referenced in the FS1 ship database, no reference to it appears on the [[Official Volition Node Map]]. According to Eishtmo, however, Volition released a rudimentary node map around the time FS1 came out that had this system illustrated on it. This node map has unfortunately disappeared and has yet to resurface.

===[[Talania]] - [[Beta Aquilae]]===
===[[Talania]] - [[Vega]]===

===Comments===
Eishtmo: ''Further study into the topic has provided enough evidence that Talania was NEVER a canon star system. There is, at the very least, no evidence for it, the lack of a node map containing it being the biggest bit. At best, Talania as a star system is a concoction of various campaign builders and an overactive imagination. I apologize for making a big deal out of this.'' 
Goober 5000: ''There is indeed evidence for it - see the Leviathan FS1 tech entry: "...production was started up again after the defeat at the Talania system..." At the very least, we know it exists. Unfortunately we have no further information on what or where it is.'' 
Ace: ''A nodemap created for the campaign series Cardinal Spear and Cardinal Spear: Vega (1999) was designed to match the appearance of the Volition nodechart. However, the notion that the Talania system exists in the same sense as the Jovian system is an idea that has become more accepted. This would mean that Talania would be a planet in a system at the front of the V-T war, either Beta Aquilae, Antares, or Vega.''

==Command Briefing Animation Validity==

These connections are shown in the animations that accompany the FS1 command briefings. 

===Jump Nodes===

====[[Beta Aquilae]] - [[Sol]]====
Seen in CB_starmap06 and in CB_starmap08

====[[Ribos]] - [[Betelgeuse]]====
Seen in CB_starmap06, although Betelgeuse isn't labeled

====[[Ribos]] - [[Vega]]====
Seen in CB_starmap08, although the jump line isn't explicitly drawn

====[[Sol]] - [[Deneb]]====
Seen in CB_starmap08

====[[Vega]] - [[Antares]]====
Seen in CB_starmap04, although the jump line isn't explicitly drawn 

===Animation Usage===

====CB_starmap04====
Is seen in La Ruotta della Fortuna (SM2-03), showing ships being attacked in Vega and subsequently jumping to Deneb and Antares. Admiral Wolf says that the Vasudan fleet is retreating after having been decimated by the [[Hammer of Light]].

====CB_starmap06====
Is seen in Tenderizer (SM2-05), showing several possible jumps from Ribos through the surrounding systems. Admiral Wolf says that although there are dozens of star systems accessible from Ribos, the GTA can't afford to give up one more inch to the Shivans.

====CB_starmap08====
Is seen in Enter the Dragon (SM2-07) and in Playing Judas (SM2-08), showing the Lucifer jumping from Ribos to Vega and the Galatea jumping from Beta Aquilae to Sol to Deneb. In Enter the Dragon, Admiral Wolf says that fighter patrols have detected advance ships from the Lucifer fleet approaching Vasuda Prime. In Playing Judas, Admiral Wolf says that the Galatea has entered Deneb to guard the system against the Deneb prong of the Shivan attack on Vasuda. 

==Hearsay Validity==

These connections are mentioned in the FS1 briefings but are not shown visually.

===[[Betelgeuse]] - [[Antares]]===
Mentioned in The Field of Battle (SM1-02). Admiral Wolf says that Vasudans have been conducting strikes on Terran convoys en route to the Betelgeuse-Antares jump point. This jump corridor may also be alluded to in Paving the Way (SM1-06) when Admiral Wolf says that standard procedure would have the Galatea circumvent the Antares-Beta Cygni jump corridor and make two jumps. Jumping from Antares to Betelgeuse to Beta Cygni would satisfy this requirement. (But so would Antares to Ribos to Beta Cygni, through the pseudocanon Ribos-Beta Cygni corridor.)

==Implied Validity==

These connections are only implied, not described or illustrated.

===[[Beta Aquilae]] - [[Vasuda]]===
Implied in Tenderizer (SM2-05). Admiral Wolf says that the Galatea will be moving to Beta Aquilae in case the Shivans decide to attack Vasuda Prime through there. This implies that there is a jump corridor from Beta Aquilae to Vasuda. The shortest alternate route, starting from Beta Aquilae, involves three jumps: Vega to Deneb to Vasuda, or Sol to Deneb to Vasuda. (Of course, since they start in Antares, the Shivans could simply pulverize the Terran blockade and jump directly to Vasuda, but for whatever reason they don't decide to do that.)

Node Inconsistencies

2006-02-03T23:39:35Z

204.145.242.1: /* Beta Cygni - Ikeya (sort of) */

Those continuation flaws that occur regarding jump nodes between FreeSpace: The Great War and FreeSpace 2 are called '''node inconsistencies'''.

There are a number of jump node connections that are used in [[Portal:Freespace_1|Freespace]] but are not illustrated on the [[Official Volition Node Map]]. They are listed below, along with their references and how valid you should consider them. [[Volition]] says that the [[Official Volition Node Map|node map]] should overrule other references.

==Pseudocanon Validity==

These connections are used in-game and would be considered canon if it weren't for the official map.

===[[Beta Cygni]] - [[Ikeya]] (probably a mistake)===
Used in First Strike (SM1-10). [[Famous Persons|Admiral Wolf]] says that the [[SC Taranis|Taranis]] has been chased from the [[Beta Cygni]] system back to the [[Ikeya]] system, and the [[SC Taranis|Taranis]] is fleeing to the [[Beta Cygni]] node during the mission itself. It is very likely, however, that this is a mistake. The cutscene immediately preceding this mission (not to mention the official node map itself) shows that the only subspace node out of [[Ikeya]] leads to [[Ribos]]. Additionally, during the mission, Freighter Halkins tows the cruiser to Tombaugh Installation, which is located in [[Ribos]]. It is probable that the mission designer just confused [[Ribos]] with [[Beta Cygni]].

===[[Beta Cygni]] - [[Ribos]]===
Used by the shield prototype convoy in The Hammer and the Anvil (SM1-08). The shield prototypes are escorted from the Cygni Installation in [[Beta Cygni]] to the [[Ribos]] node.

===[[Deneb]] - [[Altair]]===
Used by the player's squadron and Omega wing. The node is seen in Reaching the Zenith (SM3-04) and used in Running the Gauntlet (SM3-05) and Black Omega (SM3-06). Xenolinguists are transported to [[Altair]] to retrieve the ancient records and back to [[Deneb]] to rejoin the Terran fleet.

===[[Sirius]] - [[Delta Serpentis]]===
Used by the [[GTD Bastion]] in Clash of the Titans (SM3-07). The Bastion tries to intercept the [[SD Lucifer]] before it can reach [[Sol]]. Also seen in CB_starmap13 and CB_starmap14.

==Apocryphal Validity==

Although the [[Talania]] system is referenced in the FS1 ship database, no reference to it appears on the [[Official Volition Node Map]]. According to Eishtmo, however, Volition released a rudimentary node map around the time FS1 came out that had this system illustrated on it. This node map has unfortunately disappeared and has yet to resurface.

===[[Talania]] - [[Beta Aquilae]]===
===[[Talania]] - [[Vega]]===

===Comments===
Eishtmo: ''Further study into the topic has provided enough evidence that Talania was NEVER a canon star system. There is, at the very least, no evidence for it, the lack of a node map containing it being the biggest bit. At best, Talania as a star system is a concoction of various campaign builders and an overactive imagination. I apologize for making a big deal out of this.'' 
Goober 5000: ''There is indeed evidence for it - see the Leviathan FS1 tech entry: "...production was started up again after the defeat at the Talania system..." At the very least, we know it exists. Unfortunately we have no further information on what or where it is.'' 
Ace: ''A nodemap created for the campaign series Cardinal Spear and Cardinal Spear: Vega (1999) was designed to match the appearance of the Volition nodechart. However, the notion that the Talania system exists in the same sense as the Jovian system is an idea that has become more accepted. This would mean that Talania would be a planet in a system at the front of the V-T war, either Beta Aquilae, Antares, or Vega.''

==Command Briefing Animation Validity==

These connections are shown in the animations that accompany the FS1 command briefings. 

===Jump Nodes===

====[[Beta Aquilae]] - [[Sol]]====
Seen in CB_starmap06 and in CB_starmap08

====[[Ribos]] - [[Betelgeuse]]====
Seen in CB_starmap06, although Betelgeuse isn't labeled

====[[Ribos]] - [[Vega]]====
Seen in CB_starmap08, although the jump line isn't explicitly drawn

====[[Sol]] - [[Deneb]]====
Seen in CB_starmap08

====[[Vega]] - [[Antares]]====
Seen in CB_starmap04, although the jump line isn't explicitly drawn 

===Animation Usage===

====CB_starmap04====
Is seen in La Ruotta della Fortuna (SM2-03), showing ships being attacked in Vega and subsequently jumping to Deneb and Antares. Admiral Wolf says that the Vasudan fleet is retreating after having been decimated by the [[Hammer of Light]].

====CB_starmap06====
Is seen in Tenderizer (SM2-05), showing several possible jumps from Ribos through the surrounding systems. Admiral Wolf says that although there are dozens of star systems accessible from Ribos, the GTA can't afford to give up one more inch to the Shivans.

====CB_starmap08====
Is seen in Enter the Dragon (SM2-07) and in Playing Judas (SM2-08), showing the Lucifer jumping from Ribos to Vega and the Galatea jumping from Beta Aquilae to Sol to Deneb. In Enter the Dragon, Admiral Wolf says that fighter patrols have detected advance ships from the Lucifer fleet approaching Vasuda Prime. In Playing Judas, Admiral Wolf says that the Galatea has entered Deneb to guard the system against the Deneb prong of the Shivan attack on Vasuda. 

==Hearsay Validity==

These connections are mentioned in the FS1 briefings but are not shown visually.

===[[Betelgeuse]] - [[Antares]]===
Mentioned in The Field of Battle (SM1-02). Admiral Wolf says that Vasudans have been conducting strikes on Terran convoys en route to the Betelgeuse-Antares jump point. This jump corridor may also be alluded to in Paving the Way (SM1-06) when Admiral Wolf says that standard procedure would have the Galatea circumvent the Antares-Beta Cygni jump corridor and make two jumps. Jumping from Antares to Betelgeuse to Beta Cygni would satisfy this requirement. (But so would Antares to Ribos to Beta Cygni, through the pseudocanon Ribos-Beta Cygni corridor.)

==Implied Validity==

These connections are only implied, not described or illustrated.

===[[Beta Aquilae]] - [[Vasuda]]===
Implied in Tenderizer (SM2-05). Admiral Wolf says that the Galatea will be moving to Beta Aquilae in case the Shivans decide to attack Vasuda Prime through there. This implies that there is a jump corridor from Beta Aquilae to Vasuda. The shortest alternate route, starting from Beta Aquilae, involves three jumps: Vega to Deneb to Vasuda, or Sol to Deneb to Vasuda. (Of course, since they start in Antares, the Shivans could simply pulverize the Terran blockade and jump directly to Vasuda, but for whatever reason they don't decide to do that.)

Node Inconsistencies

2006-02-03T23:39:10Z

204.145.242.1: /* Beta Cygni - Ikeya */

Those continuation flaws that occur regarding jump nodes between FreeSpace: The Great War and FreeSpace 2 are called '''node inconsistencies'''.

There are a number of jump node connections that are used in [[Portal:Freespace_1|Freespace]] but are not illustrated on the [[Official Volition Node Map]]. They are listed below, along with their references and how valid you should consider them. [[Volition]] says that the [[Official Volition Node Map|node map]] should overrule other references.

==Pseudocanon Validity==

These connections are used in-game and would be considered canon if it weren't for the official map.

===[[Beta Cygni]] - [[Ikeya]] (sort of)===
Used in First Strike (SM1-10). [[Famous Persons|Admiral Wolf]] says that the [[SC Taranis|Taranis]] has been chased from the [[Beta Cygni]] system back to the [[Ikeya]] system, and the [[SC Taranis|Taranis]] is fleeing to the [[Beta Cygni]] node during the mission itself. It is very likely, however, that this is a mistake. The cutscene immediately preceding this mission (not to mention the official node map itself) shows that the only subspace node out of [[Ikeya]] leads to [[Ribos]]. Additionally, during the mission, Freighter Halkins tows the cruiser to Tombaugh Installation, which is located in [[Ribos]]. It is probable that the mission designer just confused [[Ribos]] with [[Beta Cygni]].

===[[Beta Cygni]] - [[Ribos]]===
Used by the shield prototype convoy in The Hammer and the Anvil (SM1-08). The shield prototypes are escorted from the Cygni Installation in [[Beta Cygni]] to the [[Ribos]] node.

===[[Deneb]] - [[Altair]]===
Used by the player's squadron and Omega wing. The node is seen in Reaching the Zenith (SM3-04) and used in Running the Gauntlet (SM3-05) and Black Omega (SM3-06). Xenolinguists are transported to [[Altair]] to retrieve the ancient records and back to [[Deneb]] to rejoin the Terran fleet.

===[[Sirius]] - [[Delta Serpentis]]===
Used by the [[GTD Bastion]] in Clash of the Titans (SM3-07). The Bastion tries to intercept the [[SD Lucifer]] before it can reach [[Sol]]. Also seen in CB_starmap13 and CB_starmap14.

==Apocryphal Validity==

Although the [[Talania]] system is referenced in the FS1 ship database, no reference to it appears on the [[Official Volition Node Map]]. According to Eishtmo, however, Volition released a rudimentary node map around the time FS1 came out that had this system illustrated on it. This node map has unfortunately disappeared and has yet to resurface.

===[[Talania]] - [[Beta Aquilae]]===
===[[Talania]] - [[Vega]]===

===Comments===
Eishtmo: ''Further study into the topic has provided enough evidence that Talania was NEVER a canon star system. There is, at the very least, no evidence for it, the lack of a node map containing it being the biggest bit. At best, Talania as a star system is a concoction of various campaign builders and an overactive imagination. I apologize for making a big deal out of this.'' 
Goober 5000: ''There is indeed evidence for it - see the Leviathan FS1 tech entry: "...production was started up again after the defeat at the Talania system..." At the very least, we know it exists. Unfortunately we have no further information on what or where it is.'' 
Ace: ''A nodemap created for the campaign series Cardinal Spear and Cardinal Spear: Vega (1999) was designed to match the appearance of the Volition nodechart. However, the notion that the Talania system exists in the same sense as the Jovian system is an idea that has become more accepted. This would mean that Talania would be a planet in a system at the front of the V-T war, either Beta Aquilae, Antares, or Vega.''

==Command Briefing Animation Validity==

These connections are shown in the animations that accompany the FS1 command briefings. 

===Jump Nodes===

====[[Beta Aquilae]] - [[Sol]]====
Seen in CB_starmap06 and in CB_starmap08

====[[Ribos]] - [[Betelgeuse]]====
Seen in CB_starmap06, although Betelgeuse isn't labeled

====[[Ribos]] - [[Vega]]====
Seen in CB_starmap08, although the jump line isn't explicitly drawn

====[[Sol]] - [[Deneb]]====
Seen in CB_starmap08

====[[Vega]] - [[Antares]]====
Seen in CB_starmap04, although the jump line isn't explicitly drawn 

===Animation Usage===

====CB_starmap04====
Is seen in La Ruotta della Fortuna (SM2-03), showing ships being attacked in Vega and subsequently jumping to Deneb and Antares. Admiral Wolf says that the Vasudan fleet is retreating after having been decimated by the [[Hammer of Light]].

====CB_starmap06====
Is seen in Tenderizer (SM2-05), showing several possible jumps from Ribos through the surrounding systems. Admiral Wolf says that although there are dozens of star systems accessible from Ribos, the GTA can't afford to give up one more inch to the Shivans.

====CB_starmap08====
Is seen in Enter the Dragon (SM2-07) and in Playing Judas (SM2-08), showing the Lucifer jumping from Ribos to Vega and the Galatea jumping from Beta Aquilae to Sol to Deneb. In Enter the Dragon, Admiral Wolf says that fighter patrols have detected advance ships from the Lucifer fleet approaching Vasuda Prime. In Playing Judas, Admiral Wolf says that the Galatea has entered Deneb to guard the system against the Deneb prong of the Shivan attack on Vasuda. 

==Hearsay Validity==

These connections are mentioned in the FS1 briefings but are not shown visually.

===[[Betelgeuse]] - [[Antares]]===
Mentioned in The Field of Battle (SM1-02). Admiral Wolf says that Vasudans have been conducting strikes on Terran convoys en route to the Betelgeuse-Antares jump point. This jump corridor may also be alluded to in Paving the Way (SM1-06) when Admiral Wolf says that standard procedure would have the Galatea circumvent the Antares-Beta Cygni jump corridor and make two jumps. Jumping from Antares to Betelgeuse to Beta Cygni would satisfy this requirement. (But so would Antares to Ribos to Beta Cygni, through the pseudocanon Ribos-Beta Cygni corridor.)

==Implied Validity==

These connections are only implied, not described or illustrated.

===[[Beta Aquilae]] - [[Vasuda]]===
Implied in Tenderizer (SM2-05). Admiral Wolf says that the Galatea will be moving to Beta Aquilae in case the Shivans decide to attack Vasuda Prime through there. This implies that there is a jump corridor from Beta Aquilae to Vasuda. The shortest alternate route, starting from Beta Aquilae, involves three jumps: Vega to Deneb to Vasuda, or Sol to Deneb to Vasuda. (Of course, since they start in Antares, the Shivans could simply pulverize the Terran blockade and jump directly to Vasuda, but for whatever reason they don't decide to do that.)

User-made standalone missions

2006-02-03T23:36:19Z

204.145.242.1: /* Great War-era missions */

=Missions=
==Pre-Great War-era missions==
==Great War-era missions==
[[Ross 128 (Mission)|Ross 128]] by Goober5000, FreeSpace

==Reconstruction-era missions==
==Second Great War-era missions==
[[Aken Bosch's Last Gleaming]] by Blaise Russel, FreeSpace 2 
[[Short Escape]] by TopAce, FreeSpace 2 
==Post-Second Great War-era missions==

=Notes to Wiki expanders=
Add your standalone missions into this list, following the sample below:

[[Sample standalone mission]] by Author, FreeSpace 2 
----
List mission in each category alphabetically, just to keep things in order. 
Should you have a mission that is named very generally, like Ross 128, add the (Mission) suffix to it, but do NOT separate the two words with a space.

Whether your mission is FreeSpace 2 Retail or FreeSpace Open should not be indicated here, see [[Sample standalone mission|Sample]]. If your mission needs the FreeSpace Port, also indicate it as FreeSpace 2.

Thank you.

[[Category:Lists]]