FreeSpace Wiki - User contributions [en]

Briefing texts (Operation Templar)

2009-11-05T17:05:12Z

Eishtmo: Created page with 'The FreeSpace Universe Reference Project Back To Main Page Download Docume…'

The FreeSpace Universe Reference
Project

Back To Main Page

Download Document in Word Format

FREESPACE MISSION INFORMATION
PLEASE READ

FREESPACE 2 MISSION INFORMATION

COMPILED BY: QUINN LAZERUS (EISHTMO)

EMAIL: EISHTMO@PORTALOFEVIL.COM

OPERATION TEMPLAR CAMPAIGN BRIEFINGS - COMMAND, MISSION, DEBRIEFING

WARNING: CONTAINS SPOILERS!!!!

Start Templar-01.fsm

MISSION BRIEFING 1

Congratulations, pilot. Because of your excellent service record, you have been chosen to participate in Operation Templar. This is a joint Terran-Vasudan endeavor intended to eradicate the last remnants of the Vasudan fanatics who call themselves the $h Hammer $h of $h Light.

MISSION BRIEFING 2

At 2130 hours, $h Hammer $h of $h Light operatives infiltrated Vasudan ranks in an attempt to hijack the $f GVD $f Anhur, a Typhon-class destroyer in the Vasuda system. Security forces are now battling the rebels for control of the ship. Your mission is to provide cover for the marine transports that will dock with the $f Anhur and insert reinforcements.

MISSION BRIEFING 3

Supreme Admiral Khu and other high-ranking officers of the Admiralty were on board the $f Anhur for a demonstration of the Scarab stealth technology prototypes. Should the rebels attempt to seize the prototypes or take the Admiralty hostage, we will need to act decisively.

DEBRIEFING 1

This is a terrible loss. Your incompetence has resulted in the Hammer of Light escaping with the Anhur, high-level Vasudan hostages, and the stealth technology prototypes. We are sending in another team to track them down. You are dismissed.

DEBRIEFING 2

You prevented the Hammer of Light from escaping with the captured destroyer. They will be that much weaker when we meet them again. But that provides little comfort to those lost on the Anhur. We must somehow eliminate this scourge once and for all!

DEBRIEFING 3

Great work, pilot! The remnants of the Hammer of Light forces are on the run. We are currently pursuing them into the Alpha Centauri system.

DEBRIEFING 4

You did not have orders to return to base. By deserting your unit, you have jeopardized this mission. Consider yourself grounded until you can be court-martialed, pilot.

End Templar-01.fsm

Start Templar-02.fsm

MISSION BRIEFING 1

We arrived too late in Vasuda to prevent the $h HoL transport and freighters from escaping. We are now pursuing them to Alpha Centauri. The rebels demand the release of all $h HoL leaders in government custody in exchange for the safe return of the hostages. The Vasudans have agreed to negotiate to give us time to attempt a rescue.

MISSION BRIEFING 2

Vasudan intelligence believes the $h Hammer $h of $h Light has isolated Supreme Admiral Khu and is holding him on board the $h Isis transport. The other hostages were transferred to two $h Taurus freighters. The third $h Taurus contains the stealth technology prototypes.

MISSION BRIEFING 3

Your mission is to scan all three freighters and destroy the vessel containing the prototypes. Once you have completed this objective, stand by for further orders. Under no circumstances should you fire on the ships carrying hostages.

DEBRIEFING 1

The Taurus freighters are taking the hostages to Aldebaran, while Admiral Khu is being taken to Sirius. Your orders are to follow the freighters. Other assets will try to track Admiral Khu.

DEBRIEFING 2

You disobeyed a direct order, pilot. Your reckless and criminal behavior has endangered the lives of our allies, jeopardizing future cooperation between Terrans and Vasudans. You are confined to the brig pending a court-martial.

DEBRIEFING 3

You did not have orders to return to base. By deserting your unit, you have jeopardized this mission. Consider yourself grounded until you can be court-martialed, pilot.

End Templar-02.fsm

Start Templar-03.fsm

MISSION BRIEFING 1

The $h Hammer $h of $h Light freighters carrying the Vasudan hostages seem to be headed for a rendezvous with the $h Tanis, an $h HoL destroyer. The $h Tanis and the freighters are now in the Aldebaran system. Command anticipates the rebels will try to transfer the hostages to the destroyer.

MISSION BRIEFING 2

Your main task is to keep those freighters from docking with the $h Tanis. We need to get the hostages back and we won't be able to if they get them onto that destroyer. If you can prevent that rendezvous, we'll send in marines in troop transports to capture the freighters and rescue the hostages.

MISSION BRIEFING 3

Do whatever is necessary to ensure the hostages' safety. We don't know what other forces the $h HoL has in-system, but you must handle them. Once the hostages are out of danger, wipe out the remaining $h HoL vessels.

MISSION BRIEFING 4

We have been advised that our forces in the Sirius system are preparing to engage the last known $h Hammer $h of $h Light outpost. A decisive victory in both systems will mean the complete annihilation of the $h Hammer $h of $h Light. This is a historic moment, pilot. Command is confident you are up to the challenge.

DEBRIEFING 1

Because of your outstanding performance, the hostages were successfully recovered. Operation Templar was a total success. All loyal citizens of the GTVA are celebrating the eradication of the Hammer of Light. Excellent work, pilots!

DEBRIEFING 2

Against difficult odds, GTVA marines boarded the HoL freighters and recovered the Vasudan hostages. This rescue effort would not have succeeded without your efforts. Well done, pilots.

DEBRIEFING 3

The GTVA has issued a formal apology for our failure to rescue the hostages. The Vasudans have little choice but to comply with the rebels' demands and release Hammer of Light prisoners in exchange for the officers. Operation Templar was a total failure.

DEBRIEFING 4

We botched the rescue mission, and the hostages paid with their lives. The Vasudans have terminated Operation Templar and will deal with the Hammer of Light on their own. There's a garbage scow with your name on it. Dismissed.

DEBRIEFING 5

You did not have orders to return to base. By deserting your unit, you have jeopardized this mission. Consider yourself grounded until you can be court-martialed, pilot.

End Templar-03.fsm

Start Templar-04.fsm

MISSION BRIEFING 1

Welcome to Sirius, pilots. Vasudan forces have tracked the $h Isis transport to the remote $h Nagada outpost here. This installation was de-commissioned after the Great War, but the $h Hammer $h of $h Light has brought the facility back on-line. Intelligence suspects they have been operating in this sector for only a short time.

MISSION BRIEFING 2

The Vasudans are deploying a hostage rescue team to invade the $h Nagada outpost, neutralize the rebels, and extract Supreme Admiral Khu. Your mission is to provide cover for the rescue team's transports. Success in this endeavor is of the utmost importance.

MISSION BRIEFING 3

With our victory in Aldebaran, this is the last remaining stronghold of the $h Hammer $h of $h Light. A decisive victory here will mean the complete annihilation of the $h HoL. We believe you are the team to accomplish this historic task. Good luck, pilots!

DEBRIEFING 1

We rescued Supreme Admiral Khu and destroyed outpost Nagada, the last refuge of the Hammer of Light. The GTVA has declared Operation Templar a complete success. Excellent work, pilots!

DEBRIEFING 2

Allied Command has formally apologized to the Vasudan Emperor for our failure to rescue Supreme Admiral Khu. The Vasudans are left with little choice but to comply with the rebels' demands and release Hammer of Light prisoners in exchange for the admiral. Operation Templar has failed.

DEBRIEFING 3

You did not have orders to return to base. By deserting your unit, you have jeopardized this mission. Consider yourself grounded until you can be court-martialed, pilot.

DEBREIFING 4

Though the Hammer of Light's outpost was destroyed, we lost Supreme Admiral Khu. The GTVA has issued a formal apology for this failure. Future cooperative efforts with our Vasudan allies have been jeopardized.

DEBREIFING 5

After two attempts, we managed to rescue Supreme Admiral Khu. Unfortunately, outpost Nagada remains operational. We are deploying a strike force to eliminate the hostiles you failed to neutralize.

DEBRIEFING 6

Operation Templar has been declared a total failure. The Hammer of Light's outpost remains operational, and Supreme Admiral Khu was killed during the rescue attempt. The Vasudans have decided to resolve the situation without Terran involvement. You are grounded pending reassignment.

End Templar-04.fsm

Operation Templar

2009-11-05T17:04:08Z

Eishtmo:

'''Operation Templar''' was a series of missions in which the [[Hammer of Light]] was crushed. These missions were to be played in the multiplayer co-op option in FreeSpace 2 originally. The Game of the Year edition includes an unmodified, unbalanced single-player version.

If you want to play Operation Templar in singleplayer at its intended multiplayer difficulty level, start it as a network game with yourself as the only player, so you will get respawns.

[[Operation Templar Campaign Briefings]] are now available.

==Missions==
*[[Bringing The Hammer Down]]
*[[Chasing the Threat]]
*[[Tightening the Noose]]
*[[Final Outpost]]

[[Category:History]]

Briefing texts (ST)

2009-11-05T17:01:26Z

Eishtmo:

The FreeSpace Universe Reference
Project

Back To Main Page

Download Document in Word Format

FREESPACE MISSION INFORMATION
PLEASE READ

DESCENT: FREESPACE MISSION INFORMATION

COMPILED BY: QUINN LAZERUS (EISHTMO)

EMAIL: EISHTMO@PORTALOFEVIL.COM

SILENT THREAT CAMPAIGN BRIEFINGS - COMMAND, MISSION, DEBRIEFING

WARNING: CONTAINS SPOILERS!!!!

Start md-01.fsm

COMMAND BRIEFING 1

Welcome to the GTI

Congratulations, pilot. You have been selected for the Special Operations branch of Galactic Terran Intelligence. You passed GTI's rigorous medical and psychological examinations, and your record of service with Admiral Po and the GTD Intrepid has been exemplary. You are now assigned to the GTI's Special Ops destroyer, the Krios.

The primary mission of the GTI is to provide Terran Command with accurate and comprehensive information regarding the tactics, technologies, activities, and strategic objectives of our enemies, specifically the Shivans and the Vasudan insurgency, Hammer of Light.

As a pilot for Special Ops, your missions will involve intelligence gathering and containment. These assignments are covert and classified. Violation of classification protocol will result in court-martial and possible execution under the Counter-Intelligence and Espionage Act.

COMMAND BRIEFING 2

Sol

All efforts to restore contact with Earth have failed. As you know, the Sol jump node in Delta Serpentis collapsed shortly after allied forces tracked and destroyed the Lucifer during its subspace jump. We believe the explosion of the Lucifer's five reactors created a subspace cataclysm that closed the node, perhaps permanently.

We have no word on what became of the Terran pilots that destroyed the Lucifer, or how much of the attack force remains stranded on the Earth side of the node.

As Terran scientists work toward reestablishing contact with Earth and GTA HQ, an interim GTA Command center has been set up in the Delta Serpentis system.

COMMAND BRIEFING 3

State of the Treaty

Cultural and political differences have threatened to undermine the Terran-Vasudan treaty since its inception. After fourteen years of warfare, the relationship between the GTA and the PVN has been plagued with mutual distrust, misunderstanding, and a failure to comply with the treaty's mandate of full cooperation. Furthermore, incidents of violence between Terran and Vasudan military personnel have compounded an already precarious situation.

COMMAND BRIEFING 4

Overzealous Pilots

The GTA and the PVN are conducting joint operations in the Vega system. Though hostilities between allied forces in Vega have been confined to isolated episodes, tensions have now escalated to an all-out confrontation. During a recent Shivan attack, Terran pilots fired upon Vasudan ships with intent to kill. Terran Command fears that if the PVN learns of this incident, the treaty and our hopes of defeating the Shivans will soon collapse.

COMMAND BRIEFING 5

Mission Classified

This mission has been classified at the highest level. If you should be killed or captured while fulfilling your objectives, GTI will disavow any knowledge of you or your actions.

COMMAND BRIEFING 6

New Technology: Leech Cannon

The secondary mission of the GTI is the research and development of cutting-edge technologies. As a Special Ops officer, you will have access to advanced weapons and warship prototypes not yet available to GTA pilots. These systems have undergone extensive lab and field testing and should function as designed.

The Leech Cannon drains the power supply of enemy fighters. Use the Leech Cannon to disable afterburners, energy weapons, and shields. No subsystems targeting is required, just point and shoot. The Leech Cannon is an anti-fighter weapon with minimal effect against larger vessels.

MISSION BRIEFING 1

At approximately 1530 hours, Terran and Vasudan fighters repelled a Shivan assault against Outpost Fermi. During the skirmish, Terran pilots fired on our Vasudan allies with intent to kill.

MISSION BRIEFING 2

The motives of these pilots are unclear. We do not believe their actions represent a large-scale insurrection within Terran ranks, but the situation must be contained.

MISSION BRIEFING 3

Hostilities have escalated to an all-out confrontation between Terran and Vasudan forces in the area. A GTI communications terminal in the sector transmitted an encoded message advising command of the situation, which threatens to jeopardize our treaty with the Vasudans.

MISSION BRIEFING 4

Your objective will be to sanitize the area. Destroy everything but the GTI communications terminal. All voices must be silenced to preserve the Terran-Vasudan alliance.

MISSION BRIEFING 5

This mission has an operational window of five minutes. Get in. Do your job. Get out. Good luck, pilot.

DEBRIEFING 1

Well done, pilot. You executed a clean sweep of the area and contained a volatile incident. A single Vasudan ship escaped, but the GTI will soon eliminate this threat.

DEBRIEFING 2

You exceeded your operational window, pilot. This failure will give GTA sufficient evidence to reconstruct the incident. You have compromised the Terran-Vasudan alliance, and GTA has severed its support of our operations. You are grounded permanently.

DEBRIEFING 3

You failed to silence the Vasudan transport. You have compromised the Terran-Vasudan alliance, and GTA has severed its support of our operations. You are grounded until further notice.

DEBRIEFING 4

Two targets escaped. GTI tracked and silenced the first vessel, but the second evaded our forces and informed the Vasudans of our operation. Your failure has jeopardized our treaty with the Vasudans. You are grounded until further notice.

End md-01.fsm

Start md-02.fsm

MISSION BRIEFING 1

A Vasudan ship, designated Aries 2, escaped our containment operation. GTI has tracked the vessel to a Vasudan-controlled supply zone.

MISSION BRIEFING 2

Aries 2 has communicated our objectives to Vasudan forces in that sector. We are jamming all local transmissions, but we must achieve absolute containment.

MISSION BRIEFING 3

Your mission will be to destroy all vessels in the supply zone. Ignore the cargo. Preliminary reconnaissance indicates a garrison of two Aten cruisers with fighter escort.

MISSION BRIEFING 4

The loss of innocent lives is regrettable but necessary to preserve the Terran-Vasudan alliance and defeat the Shivans. You must not fail.

DEBRIEFING 1

Excellent work. You defeated superior forces that intelligence failed to anticipate. The science vessel's escape pods survived the assault, but GTI will track and eliminate them. Analysis indicates you had no choice but to avoid the shock wave of the blast. You exercised good judgment under fire, pilot.

DEBRIEFING 2

Aborting a mission without orders is insubordination, pilot. You will have an opportunity to explain these actions at your court martial tomorrow, at 0800 hours.

End md-02.fsm

Start md-03.fsm

MISSION BRIEFING 1

GTI has located the Einstein's escape pods in the Beta Aquilae sector.

MISSION BRIEFING 2

Command has issued a new directive. Your mission will be to secure the area and guard the pods. A retrieval ship will recover the survivors for interrogation.

MISSION BRIEFING 3

We will deploy the retrieval ship as soon as possible. Defend those pods until you are relieved of duty. You will receive further orders in Beta Aquilae.

DEBRIEFING 1

The incident at Beta Aquilae has us puzzled. Command acknowledges you had no means of confirming the authorization status of the destroyer. Under these circumstances, you did excellent work ensuring the recovery of an escape pod.

DEBRIEFING 2

You are grounded until further notice, pilot. With none of the survivors in our custody, our intelligence efforts are futile.

DEBRIEFING 3

You aborted your mission before completion. You will be required to provide full testimony before a court martial. Dismissed.

End md-03.fsm

Start md-04.fsm

COMMAND BRIEFING 1

Unknown Fighters

A preliminary analysis of the incident at Beta Aquilae suggests the fighters you engaged possessed advanced stealth technologies. The origin and intent of this force remain unknown, and Terran Command has ordered a full investigation. You will be informed of the progress of this inquiry on a need-to-know basis. Until further notice, you have been reassigned to other GTI operations.

COMMAND BRIEFING 2

New Technology: Zeus Bomber

GTI research and development has completed field testing of the Zeus-class strike bomber. Like the Athena, its predecessor, the Zeus offers excellent speed and maneuverability. However, more efficient design enables the Zeus to carry Tsunami space bombs in its arsenal. These features will make the Zeus a versatile and effective weapon against Shivan capital ships.

COMMAND BRIEFING 3

New Technology: Cluster Bomb

A second-generation Synaptic bomb, GTI's cluster warhead has been designed for attacks against groups or wings of enemy ships. Upon reaching its target, the primary warhead fragments into multiple secondary warheads that explode within a split second. The detonations produce a field of energy blasts, making the cluster bomb most effective against fighter formations.

MISSION BRIEFING 1

A Shivan offensive has decimated our forces in the Ikeya system. The enemy annihilated our installations and eighty percent of the fleet garrisoned in that sector. The survivors are now retreating to secure Terran positions.

MISSION BRIEFING 2

Fortunately, the science cruiser Ratna survived the engagement. Scientists on board this vessel are spearheading the Eumenides Project and have developed cutting-edge weapon prototypes vital to the war effort.

MISSION BRIEFING 3

The Shivans disabled the Ratna, so the vessel has neither propulsion nor warp capability. We must retrieve our ship, its scientists, and their prototypes. Command anticipates Shivan reinforcements will soon resume their offensive.

MISSION BRIEFING 4

Under these circumstances, we must execute a high-risk maneuver to recover the Ratna. Vasudan transport Gemini will dock with the vessel and tow it away from the Shivan attack point. The docking seal may not hold, but we have no other viable options.

MISSION BRIEFING 5

Command will deploy additional Terran transports to evacuate the scientists. We cannot extract the prototypes from the Ratna, so the entire vessel must be recovered.

MISSION BRIEFING 6

Your mission: protect the Ratna. Repel the Shivan attack so repair crews can get the engines back on line. The future of this war is in your hands, pilot.

DEBRIEFING 1

You held off the enemy so our transports could evacuate the scientists. We need their expertise to win this war, pilot. Good work.

DEBRIEFING 2

Because of your outstanding performance, we recovered the Ratna and its prototypes. You should be very proud, pilot. You saved not only the Eumenides Project but possibly the lives of millions.

DEBRIEFING 3

You failed to provide our transports with adequate fighter cover. As a result, we could neither evacuate the scientists nor retrieve the prototypes. Technology will win this war, not mediocrity. Knowledge is power, pilot, and you're flying unarmed. Dismissed.

DEBRIEFING 4

We evacuated our scientists. However, without the prototypes, Command has terminated the Eumenides Project. There are no commendations for mediocrity, pilot. Dismissed.

End md-04.fsm

Start md-05.fsm

MISSION BRIEFING 1

Reconnaissance has observed a small Shivan cruiser group, designated Hellfire, en route to the Delta Serpentis jump node. If Hellfire reaches its destination, it will be reunited with the primary Shivan fleet.

MISSION BRIEFING 2

Hellfire consists of four cruisers, both Cain and Lilith class, with a fighter escort of ten to fifteen ships.

MISSION BRIEFING 3

Your squad will intercept and destroy as much of the Shivan force as possible. Beta and Delta will engage the cruisers. Alpha and Gamma will defend the bomber wings and neutralize the fighter threat.

DEBRIEFING 1

Well done, pilot. Because the Shivan cruisers failed to reach the Delta Serpentis jump node, we anticipate a decisive victory for our forces in that sector.

DEBRIEFING 2

You successfully destroyed Hellfire's fighter escort.

DEBRIEFING 3

We're at war pilot. This is no training mission. Hellfire reached the Delta Serpentis jump node and reinforced the primary Shivan fleet. Your failure cost us lives and resources we could not afford to lose.

End md-05.fsm

Start md-06.fsm

MISSION BRIEFING 1

Hammer of Light commandos have seized the Giordano, a science station located in the Deneb system. Sensitive GTI data will be compromised if we fail to recapture the Giordano immediately.

MISSION BRIEFING 2

Intelligence indicates the Vasudan destroyer Ptah now guards the science station.

MISSION BRIEFING 3

Your objective will be to protect transport Epsilon 1. The transport will dock with the Giordano and warp to a secure position. Delta wing will escort Epsilon 1 into the Deneb system and assist you with your mission.

MISSION BRIEFING 4

Should Epsilon 1 fail to accomplish its objective, we will deploy Epsilon 2. If neither transport succeeds in recovering the Giordano, your orders are to destroy the station and return to base.

DEBRIEFING 1

Excellent work. We recovered the Giordano and its data with only minimal losses.

DEBRIEFING 2

Your mission was a success. We lost Epsilon 1, but recovered the Giordano and its data.

DEBRIEFING 3

Your efforts have prevented a critical breach in GTI security. However, we regret the loss of the Giordano.

DEBRIEFING 4

The transports failed to recover the Giordano. The Hammer of Light now has access to data that will compromise GTI operations. Your gross incompetence has forced command to abort several key missions. Dismissed, pilot.

End md-06.fsm

Start md-07.fsm

COMMAND BRIEFING 1

Unknown Fighters

During recovery of the Einstein's escape pods in Beta Aquilae, unidentified fighters attacked your wing. The results of our inquiry are puzzling-the vessels are Loki-class fighters, GTI design and manufacture.

GTI research and development created the Loki-class fighter at a top-secret installation, location undisclosed. The prototype of a stealth fighter project, the Loki is designed to elude detection by all known sensor arrays.

COMMAND BRIEFING 2

Unknown Fighters

Analysis of the Beta Aquilae attack has enabled our engineers to exploit a structural weakness in the Loki, thus rendering its stealth technology useless. We have shared this information with our Vasudan allies, and we anticipate the Shivans will also have the expertise to uncloak the fighter.

The incident does signal an even more disturbing development, however: the emergence of a rogue element within the GTI. We suspect an insurgent cell has appropriated the Loki for unknown purposes. However, the secrecy surrounding the stealth project has impeded further inquiry.

COMMAND BRIEFING 3

The Einstein

The appearance of the Einstein in the Vega System is also troubling.

According to service logs, the Einstein was destroyed during the initial Shivan encounter at Ross 128, in which the enemy annihilated all Terran ships and installations. The Einstein had entered the system to conduct a routine geological survey three days prior to the attack.

Obviously, the Einstein's presence in Vega during our recent operation contradicts the official record.

COMMAND BRIEFING 4

Ross 128

Furthermore, evidence suggests the Einstein may have been a rogue GTI ship. A high-ranking GTI operative, Captain Ezra Tycho, commanded the science vessel. Though its official duties were limited to low-level planetary studies, the Einstein may have been involved in covert operations and weapons research. Analyzing the data we have gathered so far, we believe rogue elements within the GTI may have known about the existence of the Shivan threat prior to the attack on Ross 128.

COMMAND BRIEFING 5

Rogue Elements

Therefore, we suspect the Loki-class fighters were engaged in a GTI cover-up. The attack on your wing in the Beta Aquilae system may have been a botched attempt to destroy evidence of the Einstein's existence.
The extent of the cover-up and the objectives of the conspiracy remain unknown. You are advised to exercise caution during your next sorties.

COMMAND BRIEFING 6

New Technology: Loki Fighter

The latest prototype developed by the GTI stealth project, the Loki features high maximum velocity and excellent maneuverability. Because of a minor structural weakness, the Loki's stealth capability has been compromised. Nevertheless, the Loki is the most versatile fighter in our arsenal.

COMMAND BRIEFING 7

New Technology: S-Breaker

Developed as an anti-Shivan weapon, the Shield Breaker inflicts massive damage to enemy defensive systems. This weapon causes no structural damage, but coupling it with an anti-hull cannon will be effective against larger Shivan bombers such as the Seraphim.

Use it well.

MISSION BREIFING 1

Pirates have attacked the Talus Mining Facility. Because this installation processes materials critical to our warhead production, control of Talus is of the utmost strategic importance.

MISSION BREIFING 2

The facility's garrison repelled the pirate attack but sustained ninety percent casualties. Certain volatile materials breached containment during the engagement, and the resulting explosion annihilated the pirate force. However, the blast also severely compromised the structural integrity of the installation.

MISSION BRIEFING 3

Your primary objective will be to escort our transports while they recover the remaining warhead materials.

MISSION BRIEFING 4

Be advised the explosion released an ionized gas that will render small vessels invisible to sensors. This will make missile lock impossible on targets within the ionized zone.

MISSION BRIEFING 5

Once the operation has commenced, the facility will begin its evacuation. However, the cargo must be your first priority. Only after the materials have been recovered should you protect the escape pods. We regret any casualties that may result, but the strategic value of the warhead materials necessitates this decision.

MISSION BRIEFING 6

Command will deploy bombers to destroy the facility after all materials and survivors have been recovered.

MISSION BRIEFING 7

Because of heavy subspace activity in the area, we should anticipate a Shivan attack against our operation.

DEBRIEFING 1

Well done, pilot. You ensured the retrieval of all warhead materials and saved the lives of facility personnel.

DEBRIEFING 2

Good work, pilot. You ensured the retrieval of all warhead materials from the Talus Mining Facility.

DEBRIEFING 3

You had strict orders, pilot. Your actions may have seemed humane, but many more lives will be lost without those warhead materials. Command has no use for pilots who disregard its directives.

DEBRIEFING 4

Because of your ineptitude, the pirates now possess critical warhead materials and weapon prototypes. Furthermore, this catastrophe has bolstered the enemy's morale. Command anticipates their attacks against our positions will intensify.

DEBRIEFING 5

You skillfully thwarted the pirate assault. you did well to monitor the status of the transports to prevent materials from falling into enemy hands. Analysis suggests the pirates no longer pose any viable threat to our military ships and installations.

DEBRIEFING 6

Without those materials and prototypes, our capacity to wage war against the Shivans has been compromised. What happened out there, pilot? Was it incompetence...or treason?

End md-07.fsm

Start md-08.fsm

MISSION BRIEFING 1

Iota wing is en route to a GTI safe zone, located within an asteroid field. We have positioned Watchdog sentries near the zone to neutralize incoming projectiles.

MISSION BRIEFING 2

Iota's cargo is classified at the highest level, as are the coordinates of the safe zone. Your orders are to rendezvous with Iota and follow them to their destination.

DEBRIEFING 1

Well done. Iota wing arrived at the safe zone and sustained minimal casualties. You accomplished a mission of the utmost importance to GTI security.

DEBRIEFING 2

Whose side are you on, pilot? Iota was pulverized out there. I am not authorized to discuss the consequences of this debacle, but Hammer of Light just named a cruiser after you.

DEBRIEFING 3

We suffered heavy losses, but the survivors of Iota wing owe you their lives.

End md-08.fsm

Start md-09.fsm

MISSION BRIEFING 1

GTI fighters have disabled the Krios! Vital systems going critical! Return to base pronto!

DEBRIEFING 1

Well done. The evacuation could have been a massacre, but you got those pods to the jump node safely.

DEBRIEFING 2

All escape pods were destroyed. We are deeply saddened by the loss of this brave crew.

DEBRIEFING 3

A handful of escape pods survived the engagement. We regret that more could not be recovered.

End md-09.fsm

Start md-10.fsm

COMMAND BRIEFING 1

The Fate of the Krios

To obliterate data gathered about its activities in the Ross 128 system, Galactic Terran Intelligence destroyed the Krios. Effectively immediately, all surviving personnel are to be reassigned to the GTD Soyakaze.

COMMAND BRIEFING 2

The GTI

The conspiracy is not confined to a rogue element within the GTI, but involves officers in the highest echelon of the intelligence directorate. Although their objectives remain unclear, Command believes the conspirators intend to overthrow the GTA government and dissolve the Terran-Vasudan Treaty.

Galatic Terran Intelligence-its ships, installations, and personnel-are now hostile targets. Because of the technology and sensitive information within its grasp, the GTI poses a significant threat to the stability and security of the GTA, the PVN, and all allied worlds. Our actions must be swift and decisive.

The Soyakaze's primary objective is to locate and destroy the GTI's base of operations.

COMMAND BRIEFING 3

Ross 128

The Soyakaze has set course for the Ross 128 system. Information recovered from the Krios indicates GTI operations are concentrated around the site of the initial Shivan attack. Our first task will be to investigate this activity.

COMMAND BRIEFING 4

Admiral Scott

I will now take this opportunity to honor the late Admiral Scott, commander of the GTD Krios, who died in the line of duty.

Admiral Scott devoted many years of service to the GTI and dedicated himself to its mission: to provide the GTA and its allies with accurate and comprehensive information regarding the tactics, technologies, activities, and strategic objectives of its enemies.

His superiors, to whom he had given his trust and loyalty, betrayed Admiral Scott when they abandoned that mission to pursue their corrupt ambitions and designs. GTI is now the enemy.

Let us never forget the integrity and sacrifice of this fine officer.

COMMAND BRIEFING 5

New Technology: EM Pulse Missile

Without the technology and expertise of GTI's research and development branch, we will lack our enemy's cutting-edge weapon systems and ship prototypes. However, we do have a new addition to the arsenal: the EM Pulse missile.

Upon impact, the EM Pulse disables the electronics systems of the target ship. The weapon has numerous tactical applications. For example, a direct hit with an EM Pulse missile will prevent bombers from launching aspect-seeking warheads for several seconds. Once the EMP field has worn off, they must also reacquire their target's signature lock.

MISSION BRIEFING 1

We have set course for Ross 128, the site of the first Shivan contact. GTI operatives have been active in this system, and we must investigate. Your mission will be to inspect the wreckage from the original Shivan assault.

MISSION BRIEFING 2

Ross 128 is currently under Shivan control. There are no other Terran forces in this system. You will need to complete your mission quickly. Scan the wreckage and return to base.

DEBRIEFING 1

Your wing annihilated all GTI vessels. Fine work. We suspect the GTI already salvaged the wreckage at Ross 128. Their objectives in this sector remain unknown.

DEBRIEFING 2

We made no strategic gains at Ross 128, but your assault decimated the Shivan garrison. Nice work.

DEBRIEFING 3

Elements of the Shivan force escaped. I should not have to remind you that destroying all hostiles is a high priority. Winning the battle means nothing if we lose the war.

End md-10.fsm

Start md-11.fsm

MISSION BRIEFING 1

Reconnaissance reports heavy Shivan traffic through the Beta Aquilae jump node. Our mission: shut them down.

MISSION BRIEFING 2

Your wing will patrol this area and engage any hostiles. Seek and destroy.

DEBRIEFING 1

You had orders not to destroy the cargo, pilot. Either you're a slow learner or you're shooting for demotion. Intelligence needed that cargo for analysis.

DEBRIEFING 2

The Shivans escaped with their cargo. Apparently their freighters were too fast and maneuverable for you, pilot. Command is unimpressed with your lack of results.

DEBRIEFING 3

Our freighters retrieved the Shivan cargo. Well done. Intelligence has begun its analysis, and we hope to learn much about Shivan strategy in this sector.

DEBRIEFING 4

We failed to recover all the cargo, but we have sufficient evidence to uncover the Shivan's objective in this sector.

End md-11.fsm

Start md-12.fsm

COMMAND BRIEFING 1

GTI Headquarters

We have located the GTI's base of operations- the Jotunheim installation in the Beta Aquilae system.

The full extent of their activities in Beta Aquilae remain unknown. However, we believe the GTI has been studying Shivan culture and technology at Jotunheim since the massacre at Ross 128.

COMMAND BRIEFING 2

GTI Plans

Reconnaissance also has evidence of a large-scale prototype construction involving Shivan technology, but no data regarding the configuration and capability of this vessel could be gathered.

COMMAND BRIEFING 3

GTI Technology

GTI forces have access to Shivan armaments as well as the systems created by its research and development branch, so be advised your foe will possess superior technology. You will have to fly smarter and fight harder to win this battle.

Command suspects the GTI may also have Shivan captives at Jotunheim for the purposes of biological research and the development of viral weapons.

COMMAND BRIEFING 4

Hades

Terran Command intercepted a GTI transmission and technical readout relating to a Jotunheim operation with the codename Project Hades. Cryptographers are in the process of deciphering the transmission, and engineers are analyzing the technical readout. Although we have nothing conclusive, we must act now.

COMMAND BRIEFING 5

Our Mission

The rogue Galactic Terran Intelligence group must be crushed. These traitors threaten the security of the GTA, the stability of the Terran-Vasudan Alliance, and our future victory over the Shivans. Report for your mission briefing, pilot.

MISSION BRIEFING 1

Reconnaissance has uncovered the location of GTI's primary base of operations, the Jotunheim. Details concerning the strength of the garrison remain sketchy. GTA will launch an immediate, all-out offensive and deploy reinforcements as soon as possible.

MISSION BRIEFING 2

Failure is not an option. The GTI conducts weapons research on the Jotunheim, so be prepared to engage exotic prototypes with unknown capabilities.

DEBRIEFING 1

Your cowardice jeopardized our best opportunity to eliminate the GTI threat. Once operational, the Shivan-Terran hybrid will be invincible. Dismissed, pilot.

DEBRIEFING 2

Excellent work! Our initiative caught the GTI off guard. Preliminary scans indicate the GTI possessed Shivan defensive technologies. If that juggernaut had gone on line, GTI would be writing the history books.

End md-11.fsm

Briefing texts (ST)

2009-11-05T16:58:27Z

Eishtmo: Created page with 'The FreeSpace Universe Reference Project Back To Main Page Download Docume…'

The FreeSpace Universe Reference
Project

Back To Main Page

Download Document in Word Format

FREESPACE MISSION INFORMATION
PLEASE READ
=========================================================================

DESCENT: FREESPACE MISSION INFORMATION

COMPILED BY: QUINN LAZERUS (EISHTMO)

EMAIL: EISHTMO@PORTALOFEVIL.COM

=========================================================================

SILENT THREAT CAMPAIGN BRIEFINGS - COMMAND, MISSION, DEBRIEFING

=========================================================================

WARNING: CONTAINS SPOILERS!!!!

=========================================================================

Start md-01.fsm

=========================================================================

COMMAND BRIEFING 1

Welcome to the GTI

Congratulations, pilot. You have been selected for the Special Operations branch of Galactic Terran Intelligence. You passed GTI's rigorous medical and psychological examinations, and your record of service with Admiral Po and the GTD Intrepid has been exemplary. You are now assigned to the GTI's Special Ops destroyer, the Krios.

The primary mission of the GTI is to provide Terran Command with accurate and comprehensive information regarding the tactics, technologies, activities, and strategic objectives of our enemies, specifically the Shivans and the Vasudan insurgency, Hammer of Light.

As a pilot for Special Ops, your missions will involve intelligence gathering and containment. These assignments are covert and classified. Violation of classification protocol will result in court-martial and possible execution under the Counter-Intelligence and Espionage Act.

COMMAND BRIEFING 2

Sol

All efforts to restore contact with Earth have failed. As you know, the Sol jump node in Delta Serpentis collapsed shortly after allied forces tracked and destroyed the Lucifer during its subspace jump. We believe the explosion of the Lucifer's five reactors created a subspace cataclysm that closed the node, perhaps permanently.

We have no word on what became of the Terran pilots that destroyed the Lucifer, or how much of the attack force remains stranded on the Earth side of the node.

As Terran scientists work toward reestablishing contact with Earth and GTA HQ, an interim GTA Command center has been set up in the Delta Serpentis system.

COMMAND BRIEFING 3

State of the Treaty

Cultural and political differences have threatened to undermine the Terran-Vasudan treaty since its inception. After fourteen years of warfare, the relationship between the GTA and the PVN has been plagued with mutual distrust, misunderstanding, and a failure to comply with the treaty's mandate of full cooperation. Furthermore, incidents of violence between Terran and Vasudan military personnel have compounded an already precarious situation.

COMMAND BRIEFING 4

Overzealous Pilots

The GTA and the PVN are conducting joint operations in the Vega system. Though hostilities between allied forces in Vega have been confined to isolated episodes, tensions have now escalated to an all-out confrontation. During a recent Shivan attack, Terran pilots fired upon Vasudan ships with intent to kill. Terran Command fears that if the PVN learns of this incident, the treaty and our hopes of defeating the Shivans will soon collapse.

COMMAND BRIEFING 5

Mission Classified

This mission has been classified at the highest level. If you should be killed or captured while fulfilling your objectives, GTI will disavow any knowledge of you or your actions.

COMMAND BRIEFING 6

New Technology: Leech Cannon

The secondary mission of the GTI is the research and development of cutting-edge technologies. As a Special Ops officer, you will have access to advanced weapons and warship prototypes not yet available to GTA pilots. These systems have undergone extensive lab and field testing and should function as designed.

The Leech Cannon drains the power supply of enemy fighters. Use the Leech Cannon to disable afterburners, energy weapons, and shields. No subsystems targeting is required, just point and shoot. The Leech Cannon is an anti-fighter weapon with minimal effect against larger vessels.

MISSION BRIEFING 1

At approximately 1530 hours, Terran and Vasudan fighters repelled a Shivan assault against Outpost Fermi. During the skirmish, Terran pilots fired on our Vasudan allies with intent to kill.

MISSION BRIEFING 2

The motives of these pilots are unclear. We do not believe their actions represent a large-scale insurrection within Terran ranks, but the situation must be contained.

MISSION BRIEFING 3

Hostilities have escalated to an all-out confrontation between Terran and Vasudan forces in the area. A GTI communications terminal in the sector transmitted an encoded message advising command of the situation, which threatens to jeopardize our treaty with the Vasudans.

MISSION BRIEFING 4

Your objective will be to sanitize the area. Destroy everything but the GTI communications terminal. All voices must be silenced to preserve the Terran-Vasudan alliance.

MISSION BRIEFING 5

This mission has an operational window of five minutes. Get in. Do your job. Get out. Good luck, pilot.

DEBRIEFING 1

Well done, pilot. You executed a clean sweep of the area and contained a volatile incident. A single Vasudan ship escaped, but the GTI will soon eliminate this threat.

DEBRIEFING 2

You exceeded your operational window, pilot. This failure will give GTA sufficient evidence to reconstruct the incident. You have compromised the Terran-Vasudan alliance, and GTA has severed its support of our operations. You are grounded permanently.

DEBRIEFING 3

You failed to silence the Vasudan transport. You have compromised the Terran-Vasudan alliance, and GTA has severed its support of our operations. You are grounded until further notice.

DEBRIEFING 4

Two targets escaped. GTI tracked and silenced the first vessel, but the second evaded our forces and informed the Vasudans of our operation. Your failure has jeopardized our treaty with the Vasudans. You are grounded until further notice.

=========================================================================

End md-01.fsm

=========================================================================

Start md-02.fsm

=========================================================================

MISSION BRIEFING 1

A Vasudan ship, designated Aries 2, escaped our containment operation. GTI has tracked the vessel to a Vasudan-controlled supply zone.

MISSION BRIEFING 2

Aries 2 has communicated our objectives to Vasudan forces in that sector. We are jamming all local transmissions, but we must achieve absolute containment.

MISSION BRIEFING 3

Your mission will be to destroy all vessels in the supply zone. Ignore the cargo. Preliminary reconnaissance indicates a garrison of two Aten cruisers with fighter escort.

MISSION BRIEFING 4

The loss of innocent lives is regrettable but necessary to preserve the Terran-Vasudan alliance and defeat the Shivans. You must not fail.

DEBRIEFING 1

Excellent work. You defeated superior forces that intelligence failed to anticipate. The science vessel's escape pods survived the assault, but GTI will track and eliminate them. Analysis indicates you had no choice but to avoid the shock wave of the blast. You exercised good judgment under fire, pilot.

DEBRIEFING 2

Aborting a mission without orders is insubordination, pilot. You will have an opportunity to explain these actions at your court martial tomorrow, at 0800 hours.

=========================================================================

End md-02.fsm

=========================================================================

Start md-03.fsm

=========================================================================

MISSION BRIEFING 1

GTI has located the Einstein's escape pods in the Beta Aquilae sector.

MISSION BRIEFING 2

Command has issued a new directive. Your mission will be to secure the area and guard the pods. A retrieval ship will recover the survivors for interrogation.

MISSION BRIEFING 3

We will deploy the retrieval ship as soon as possible. Defend those pods until you are relieved of duty. You will receive further orders in Beta Aquilae.

DEBRIEFING 1

The incident at Beta Aquilae has us puzzled. Command acknowledges you had no means of confirming the authorization status of the destroyer. Under these circumstances, you did excellent work ensuring the recovery of an escape pod.

DEBRIEFING 2

You are grounded until further notice, pilot. With none of the survivors in our custody, our intelligence efforts are futile.

DEBRIEFING 3

You aborted your mission before completion. You will be required to provide full testimony before a court martial. Dismissed.

=========================================================================

End md-03.fsm

=========================================================================

Start md-04.fsm

=========================================================================

COMMAND BRIEFING 1

Unknown Fighters

A preliminary analysis of the incident at Beta Aquilae suggests the fighters you engaged possessed advanced stealth technologies. The origin and intent of this force remain unknown, and Terran Command has ordered a full investigation. You will be informed of the progress of this inquiry on a need-to-know basis. Until further notice, you have been reassigned to other GTI operations.

COMMAND BRIEFING 2

New Technology: Zeus Bomber

GTI research and development has completed field testing of the Zeus-class strike bomber. Like the Athena, its predecessor, the Zeus offers excellent speed and maneuverability. However, more efficient design enables the Zeus to carry Tsunami space bombs in its arsenal. These features will make the Zeus a versatile and effective weapon against Shivan capital ships.

COMMAND BRIEFING 3

New Technology: Cluster Bomb

A second-generation Synaptic bomb, GTI's cluster warhead has been designed for attacks against groups or wings of enemy ships. Upon reaching its target, the primary warhead fragments into multiple secondary warheads that explode within a split second. The detonations produce a field of energy blasts, making the cluster bomb most effective against fighter formations.

MISSION BRIEFING 1

A Shivan offensive has decimated our forces in the Ikeya system. The enemy annihilated our installations and eighty percent of the fleet garrisoned in that sector. The survivors are now retreating to secure Terran positions.

MISSION BRIEFING 2

Fortunately, the science cruiser Ratna survived the engagement. Scientists on board this vessel are spearheading the Eumenides Project and have developed cutting-edge weapon prototypes vital to the war effort.

MISSION BRIEFING 3

The Shivans disabled the Ratna, so the vessel has neither propulsion nor warp capability. We must retrieve our ship, its scientists, and their prototypes. Command anticipates Shivan reinforcements will soon resume their offensive.

MISSION BRIEFING 4

Under these circumstances, we must execute a high-risk maneuver to recover the Ratna. Vasudan transport Gemini will dock with the vessel and tow it away from the Shivan attack point. The docking seal may not hold, but we have no other viable options.

MISSION BRIEFING 5

Command will deploy additional Terran transports to evacuate the scientists. We cannot extract the prototypes from the Ratna, so the entire vessel must be recovered.

MISSION BRIEFING 6

Your mission: protect the Ratna. Repel the Shivan attack so repair crews can get the engines back on line. The future of this war is in your hands, pilot.

DEBRIEFING 1

You held off the enemy so our transports could evacuate the scientists. We need their expertise to win this war, pilot. Good work.

DEBRIEFING 2

Because of your outstanding performance, we recovered the Ratna and its prototypes. You should be very proud, pilot. You saved not only the Eumenides Project but possibly the lives of millions.

DEBRIEFING 3

You failed to provide our transports with adequate fighter cover. As a result, we could neither evacuate the scientists nor retrieve the prototypes. Technology will win this war, not mediocrity. Knowledge is power, pilot, and you're flying unarmed. Dismissed.

DEBRIEFING 4

We evacuated our scientists. However, without the prototypes, Command has terminated the Eumenides Project. There are no commendations for mediocrity, pilot. Dismissed.

=========================================================================

End md-04.fsm

=========================================================================

Start md-05.fsm

=========================================================================

MISSION BRIEFING 1

Reconnaissance has observed a small Shivan cruiser group, designated Hellfire, en route to the Delta Serpentis jump node. If Hellfire reaches its destination, it will be reunited with the primary Shivan fleet.

MISSION BRIEFING 2

Hellfire consists of four cruisers, both Cain and Lilith class, with a fighter escort of ten to fifteen ships.

MISSION BRIEFING 3

Your squad will intercept and destroy as much of the Shivan force as possible. Beta and Delta will engage the cruisers. Alpha and Gamma will defend the bomber wings and neutralize the fighter threat.

DEBRIEFING 1

Well done, pilot. Because the Shivan cruisers failed to reach the Delta Serpentis jump node, we anticipate a decisive victory for our forces in that sector.

DEBRIEFING 2

You successfully destroyed Hellfire's fighter escort.

DEBRIEFING 3

We're at war pilot. This is no training mission. Hellfire reached the Delta Serpentis jump node and reinforced the primary Shivan fleet. Your failure cost us lives and resources we could not afford to lose.

=========================================================================

End md-05.fsm

=========================================================================

Start md-06.fsm

=========================================================================

MISSION BRIEFING 1

Hammer of Light commandos have seized the Giordano, a science station located in the Deneb system. Sensitive GTI data will be compromised if we fail to recapture the Giordano immediately.

MISSION BRIEFING 2

Intelligence indicates the Vasudan destroyer Ptah now guards the science station.

MISSION BRIEFING 3

Your objective will be to protect transport Epsilon 1. The transport will dock with the Giordano and warp to a secure position. Delta wing will escort Epsilon 1 into the Deneb system and assist you with your mission.

MISSION BRIEFING 4

Should Epsilon 1 fail to accomplish its objective, we will deploy Epsilon 2. If neither transport succeeds in recovering the Giordano, your orders are to destroy the station and return to base.

DEBRIEFING 1

Excellent work. We recovered the Giordano and its data with only minimal losses.

DEBRIEFING 2

Your mission was a success. We lost Epsilon 1, but recovered the Giordano and its data.

DEBRIEFING 3

Your efforts have prevented a critical breach in GTI security. However, we regret the loss of the Giordano.

DEBRIEFING 4

The transports failed to recover the Giordano. The Hammer of Light now has access to data that will compromise GTI operations. Your gross incompetence has forced command to abort several key missions. Dismissed, pilot.

=========================================================================

End md-06.fsm

=========================================================================

Start md-07.fsm

=========================================================================

COMMAND BRIEFING 1

Unknown Fighters

During recovery of the Einstein's escape pods in Beta Aquilae, unidentified fighters attacked your wing. The results of our inquiry are puzzling-the vessels are Loki-class fighters, GTI design and manufacture.

GTI research and development created the Loki-class fighter at a top-secret installation, location undisclosed. The prototype of a stealth fighter project, the Loki is designed to elude detection by all known sensor arrays.

COMMAND BRIEFING 2

Unknown Fighters

Analysis of the Beta Aquilae attack has enabled our engineers to exploit a structural weakness in the Loki, thus rendering its stealth technology useless. We have shared this information with our Vasudan allies, and we anticipate the Shivans will also have the expertise to uncloak the fighter.

The incident does signal an even more disturbing development, however: the emergence of a rogue element within the GTI. We suspect an insurgent cell has appropriated the Loki for unknown purposes. However, the secrecy surrounding the stealth project has impeded further inquiry.

COMMAND BRIEFING 3

The Einstein

The appearance of the Einstein in the Vega System is also troubling.

According to service logs, the Einstein was destroyed during the initial Shivan encounter at Ross 128, in which the enemy annihilated all Terran ships and installations. The Einstein had entered the system to conduct a routine geological survey three days prior to the attack.

Obviously, the Einstein's presence in Vega during our recent operation contradicts the official record.

COMMAND BRIEFING 4

Ross 128

Furthermore, evidence suggests the Einstein may have been a rogue GTI ship. A high-ranking GTI operative, Captain Ezra Tycho, commanded the science vessel. Though its official duties were limited to low-level planetary studies, the Einstein may have been involved in covert operations and weapons research. Analyzing the data we have gathered so far, we believe rogue elements within the GTI may have known about the existence of the Shivan threat prior to the attack on Ross 128.

COMMAND BRIEFING 5

Rogue Elements

Therefore, we suspect the Loki-class fighters were engaged in a GTI cover-up. The attack on your wing in the Beta Aquilae system may have been a botched attempt to destroy evidence of the Einstein's existence.
The extent of the cover-up and the objectives of the conspiracy remain unknown. You are advised to exercise caution during your next sorties.

COMMAND BRIEFING 6

New Technology: Loki Fighter

The latest prototype developed by the GTI stealth project, the Loki features high maximum velocity and excellent maneuverability. Because of a minor structural weakness, the Loki's stealth capability has been compromised. Nevertheless, the Loki is the most versatile fighter in our arsenal.

COMMAND BRIEFING 7

New Technology: S-Breaker

Developed as an anti-Shivan weapon, the Shield Breaker inflicts massive damage to enemy defensive systems. This weapon causes no structural damage, but coupling it with an anti-hull cannon will be effective against larger Shivan bombers such as the Seraphim.

Use it well.

MISSION BREIFING 1

Pirates have attacked the Talus Mining Facility. Because this installation processes materials critical to our warhead production, control of Talus is of the utmost strategic importance.

MISSION BREIFING 2

The facility's garrison repelled the pirate attack but sustained ninety percent casualties. Certain volatile materials breached containment during the engagement, and the resulting explosion annihilated the pirate force. However, the blast also severely compromised the structural integrity of the installation.

MISSION BRIEFING 3

Your primary objective will be to escort our transports while they recover the remaining warhead materials.

MISSION BRIEFING 4

Be advised the explosion released an ionized gas that will render small vessels invisible to sensors. This will make missile lock impossible on targets within the ionized zone.

MISSION BRIEFING 5

Once the operation has commenced, the facility will begin its evacuation. However, the cargo must be your first priority. Only after the materials have been recovered should you protect the escape pods. We regret any casualties that may result, but the strategic value of the warhead materials necessitates this decision.

MISSION BRIEFING 6

Command will deploy bombers to destroy the facility after all materials and survivors have been recovered.

MISSION BRIEFING 7

Because of heavy subspace activity in the area, we should anticipate a Shivan attack against our operation.

DEBRIEFING 1

Well done, pilot. You ensured the retrieval of all warhead materials and saved the lives of facility personnel.

DEBRIEFING 2

Good work, pilot. You ensured the retrieval of all warhead materials from the Talus Mining Facility.

DEBRIEFING 3

You had strict orders, pilot. Your actions may have seemed humane, but many more lives will be lost without those warhead materials. Command has no use for pilots who disregard its directives.

DEBRIEFING 4

Because of your ineptitude, the pirates now possess critical warhead materials and weapon prototypes. Furthermore, this catastrophe has bolstered the enemy's morale. Command anticipates their attacks against our positions will intensify.

DEBRIEFING 5

You skillfully thwarted the pirate assault. you did well to monitor the status of the transports to prevent materials from falling into enemy hands. Analysis suggests the pirates no longer pose any viable threat to our military ships and installations.

DEBRIEFING 6

Without those materials and prototypes, our capacity to wage war against the Shivans has been compromised. What happened out there, pilot? Was it incompetence...or treason?

=========================================================================

End md-07.fsm

=========================================================================

Start md-08.fsm

=========================================================================

MISSION BRIEFING 1

Iota wing is en route to a GTI safe zone, located within an asteroid field. We have positioned Watchdog sentries near the zone to neutralize incoming projectiles.

MISSION BRIEFING 2

Iota's cargo is classified at the highest level, as are the coordinates of the safe zone. Your orders are to rendezvous with Iota and follow them to their destination.

DEBRIEFING 1

Well done. Iota wing arrived at the safe zone and sustained minimal casualties. You accomplished a mission of the utmost importance to GTI security.

DEBRIEFING 2

Whose side are you on, pilot? Iota was pulverized out there. I am not authorized to discuss the consequences of this debacle, but Hammer of Light just named a cruiser after you.

DEBRIEFING 3

We suffered heavy losses, but the survivors of Iota wing owe you their lives.

=========================================================================

End md-08.fsm

=========================================================================

Start md-09.fsm

=========================================================================

MISSION BRIEFING 1

GTI fighters have disabled the Krios! Vital systems going critical! Return to base pronto!

DEBRIEFING 1

Well done. The evacuation could have been a massacre, but you got those pods to the jump node safely.

DEBRIEFING 2

All escape pods were destroyed. We are deeply saddened by the loss of this brave crew.

DEBRIEFING 3

A handful of escape pods survived the engagement. We regret that more could not be recovered.

=========================================================================

End md-09.fsm

=========================================================================

Start md-10.fsm

=========================================================================

COMMAND BRIEFING 1

The Fate of the Krios

To obliterate data gathered about its activities in the Ross 128 system, Galactic Terran Intelligence destroyed the Krios. Effectively immediately, all surviving personnel are to be reassigned to the GTD Soyakaze.

COMMAND BRIEFING 2

The GTI

The conspiracy is not confined to a rogue element within the GTI, but involves officers in the highest echelon of the intelligence directorate. Although their objectives remain unclear, Command believes the conspirators intend to overthrow the GTA government and dissolve the Terran-Vasudan Treaty.

Galatic Terran Intelligence-its ships, installations, and personnel-are now hostile targets. Because of the technology and sensitive information within its grasp, the GTI poses a significant threat to the stability and security of the GTA, the PVN, and all allied worlds. Our actions must be swift and decisive.

The Soyakaze's primary objective is to locate and destroy the GTI's base of operations.

COMMAND BRIEFING 3

Ross 128

The Soyakaze has set course for the Ross 128 system. Information recovered from the Krios indicates GTI operations are concentrated around the site of the initial Shivan attack. Our first task will be to investigate this activity.

COMMAND BRIEFING 4

Admiral Scott

I will now take this opportunity to honor the late Admiral Scott, commander of the GTD Krios, who died in the line of duty.

Admiral Scott devoted many years of service to the GTI and dedicated himself to its mission: to provide the GTA and its allies with accurate and comprehensive information regarding the tactics, technologies, activities, and strategic objectives of its enemies.

His superiors, to whom he had given his trust and loyalty, betrayed Admiral Scott when they abandoned that mission to pursue their corrupt ambitions and designs. GTI is now the enemy.

Let us never forget the integrity and sacrifice of this fine officer.

COMMAND BRIEFING 5

New Technology: EM Pulse Missile

Without the technology and expertise of GTI's research and development branch, we will lack our enemy's cutting-edge weapon systems and ship prototypes. However, we do have a new addition to the arsenal: the EM Pulse missile.

Upon impact, the EM Pulse disables the electronics systems of the target ship. The weapon has numerous tactical applications. For example, a direct hit with an EM Pulse missile will prevent bombers from launching aspect-seeking warheads for several seconds. Once the EMP field has worn off, they must also reacquire their target's signature lock.

MISSION BRIEFING 1

We have set course for Ross 128, the site of the first Shivan contact. GTI operatives have been active in this system, and we must investigate. Your mission will be to inspect the wreckage from the original Shivan assault.

MISSION BRIEFING 2

Ross 128 is currently under Shivan control. There are no other Terran forces in this system. You will need to complete your mission quickly. Scan the wreckage and return to base.

DEBRIEFING 1

Your wing annihilated all GTI vessels. Fine work. We suspect the GTI already salvaged the wreckage at Ross 128. Their objectives in this sector remain unknown.

DEBRIEFING 2

We made no strategic gains at Ross 128, but your assault decimated the Shivan garrison. Nice work.

DEBRIEFING 3

Elements of the Shivan force escaped. I should not have to remind you that destroying all hostiles is a high priority. Winning the battle means nothing if we lose the war.

=========================================================================

End md-10.fsm

=========================================================================

Start md-11.fsm

=========================================================================

MISSION BRIEFING 1

Reconnaissance reports heavy Shivan traffic through the Beta Aquilae jump node. Our mission: shut them down.

MISSION BRIEFING 2

Your wing will patrol this area and engage any hostiles. Seek and destroy.

DEBRIEFING 1

You had orders not to destroy the cargo, pilot. Either you're a slow learner or you're shooting for demotion. Intelligence needed that cargo for analysis.

DEBRIEFING 2

The Shivans escaped with their cargo. Apparently their freighters were too fast and maneuverable for you, pilot. Command is unimpressed with your lack of results.

DEBRIEFING 3

Our freighters retrieved the Shivan cargo. Well done. Intelligence has begun its analysis, and we hope to learn much about Shivan strategy in this sector.

DEBRIEFING 4

We failed to recover all the cargo, but we have sufficient evidence to uncover the Shivan's objective in this sector.

=========================================================================

End md-11.fsm

=========================================================================

Start md-12.fsm

=========================================================================

COMMAND BRIEFING 1

GTI Headquarters

We have located the GTI's base of operations- the Jotunheim installation in the Beta Aquilae system.

The full extent of their activities in Beta Aquilae remain unknown. However, we believe the GTI has been studying Shivan culture and technology at Jotunheim since the massacre at Ross 128.

COMMAND BRIEFING 2

GTI Plans

Reconnaissance also has evidence of a large-scale prototype construction involving Shivan technology, but no data regarding the configuration and capability of this vessel could be gathered.

COMMAND BRIEFING 3

GTI Technology

GTI forces have access to Shivan armaments as well as the systems created by its research and development branch, so be advised your foe will possess superior technology. You will have to fly smarter and fight harder to win this battle.

Command suspects the GTI may also have Shivan captives at Jotunheim for the purposes of biological research and the development of viral weapons.

COMMAND BRIEFING 4

Hades

Terran Command intercepted a GTI transmission and technical readout relating to a Jotunheim operation with the codename Project Hades. Cryptographers are in the process of deciphering the transmission, and engineers are analyzing the technical readout. Although we have nothing conclusive, we must act now.

COMMAND BRIEFING 5

Our Mission

The rogue Galactic Terran Intelligence group must be crushed. These traitors threaten the security of the GTA, the stability of the Terran-Vasudan Alliance, and our future victory over the Shivans. Report for your mission briefing, pilot.

MISSION BRIEFING 1

Reconnaissance has uncovered the location of GTI's primary base of operations, the Jotunheim. Details concerning the strength of the garrison remain sketchy. GTA will launch an immediate, all-out offensive and deploy reinforcements as soon as possible.

MISSION BRIEFING 2

Failure is not an option. The GTI conducts weapons research on the Jotunheim, so be prepared to engage exotic prototypes with unknown capabilities.

DEBRIEFING 1

Your cowardice jeopardized our best opportunity to eliminate the GTI threat. Once operational, the Shivan-Terran hybrid will be invincible. Dismissed, pilot.

DEBRIEFING 2

Excellent work! Our initiative caught the GTI off guard. Preliminary scans indicate the GTI possessed Shivan defensive technologies. If that juggernaut had gone on line, GTI would be writing the history books.

=========================================================================

End md-11.fsm

=========================================================================

Silent Threat

2009-11-05T16:57:38Z

Eishtmo:

'''''Silent Threat''''' is an official expansion pack for [[Portal:FreeSpace 1|FreeSpace 1]]. Its major component is a new campaign documenting the [[Hades Rebellion]], which introduces several new ships and weapons as well as new command briefings. It is also notable in that it includes dozens of fan-created missions. ''Silent Threat'' was released on the second of October, 1998.

==Official Description==
"As the Great War rages on, you've been commissioned by the GTI (Galactic Terran Intelligence) for special intelligence operations. In a matter of National Security, you've been asked to go behind enemy lines in order to preserve the fragile space treaty. Is the GTI setting you up or are the Shivans spreading their evil rage?"
*Over 40 new missions created by both the developer and fans.
*2 new playable ships join your squadron of 40 stunningly realistic, richly detailed craft.
*2 new primary weapons and 2 new secondary weapons are now at your disposal to trash the sky with enemy debris.
*A new enemy capital ship has emerged and is poised to challenge the greatest fighters in space.
*The multiplayer chaos continues with up to 12 players over the Internet."

==New Ships and Weapons==
===Player-Flyable Ships===
*[[GTF Loki|GTF ''Loki'']] - Reconnaisance fighter used by the GTI.
*[[GTB Zeus|GTB ''Zeus'']] - New strike bomber to replace the [[GTB Athena|GTB ''Athena'']].
===Non Player-Flyable Ships===
*[[GTD Hades|GTD ''Hades'']] - Flagship of the GTI Fleet, developed with technology from the [[SD Lucifer|SD ''Lucifer'']].
*[[SB Seraphim|SB ''Seraphim'']] - Extremely powerful Shivan bomber.
===Weapons===
*[[GTW Leech Cannon|GTW-43 Leech Cannon]] - Energy draining primary weapon.
*[[GTW Shield Breaker|GTW-51 Shield Breaker]] - Primary weapon designed solely to defeat shields.
*[[GTM Cluster Bomb|GTM-86 Cluster Bomb]] - Second-generation cluster missile.
*[[GTM EM Pulse|GTM-11 EM Pulse]] - Electronic warfare missile capable of temporarily disabling enemy fighters and bombers.

==Campaign/Mission Briefings==
*Compiled by Eishtmo, [[Silent Threat Campaign Breifings]]

==Fan-Created Missions==
Over half of the missions included with ''Silent Threat'' were created by fans who participated in the Silent Threat Mission Design Contest. A list of the missions chosen for ''Silent Threat'' and their respsective designers follows:
*Asteroid Onslaught - Danny Craig Defrancis
*Black Knight - Michael M. Solyom
*Crippler - Christopher Douglas Haskett
*Cutting the Supply Line - Peter Drake
*Dead in the Water - Christopher James Bagwell
*Deception - Brian Wheeler
*[[The Destiny of Peace]] 1-7 - Justin Mills
*Fortress - Christopher Douglas Haskett
*Full T-V Battle - Jason Attard
*The Great Escape - Adam Rorabaugh
*The GTI Shadow - Justin Raynard
*Hunted - Dan J. Raymond
*Into the Fire - Colin "IceFire" Czerneda
*Loner - Rob Munro
*The Manhattan Project - Justin Mills
*The Master of Illusion - Ryan Glasnapp
*Order of the Eye - Peter Drake
*Powerball Arena - Victor "DrDooM" Shin
*Red Herring - Matt Sparling
*Roadkill - Matt Finnerty
*The Sands of Normandy - Nathan "Dynamo" Hoying
*Shadows - Brad Crawford
*Supplies! Supplies! - Jeff Montgomery
*Surprise - Eser Guven
*Survivors - Colin "IceFire" Czerneda
*Test of Honor - Brad Crawford
*Virginia's Run - Christopher Vann Cox

==Other Resources==
Since the main ''Silent Threat'' campaign received relatively extensive criticism and is ostensibly somewhat weak—in both storyline and execution—,a fan-created extension of the main campaign was released: ''[[Silent Threat: Reborn]]''. The campaign is an attempt to create a campaign without the shortcomings of the official one, namely plotholes and badly-scripted missions. This campaign is already available.

==Comments==
Much has been said about the campaign's defects. Yes, there is an Orion simply called "GTD" here (and it's furthermore referred to as a "cruiser"). Yes, there are no return to base directives anywhere, and all the targets are stationary and spew out an unlimited number of enemy fighters. Yes, there's not much dialog in the campaign, but there's something wonderful in the way the original ST is done: Playing on a sufficiently low difficulty level, there's nothing you need to worry about. ST requires no precognitive abilities to complete its missions, unlike its fan-made remade: There will be no EMP shockwaves that will render you incapacited because you did not jump out in a window of 5 seconds after killing everything. There will be no 15-minute-long missions that you will likely lose in the 14th minute. It's all about blowing up everything that gets in your way, sometimes while protecting something. These escort missions are just okay: there will be no single Zeus bomber that jumps in 8 kilometers away from you and, in 30 seconds, destroy the superpowerful space station you have been so ardently defending from an overwhelming enemy force. You will score a lot of kills in this campaign, and you may even single-handedly take on cruisers while your wingmen draw away hostile fighters' fire. Yes, the last mission is what it is: garbage, but then again, just play on a relaxing difficulty level, and you won't have a problem. - [[User:TopAce|TopAce]] 16:15, 4 September 2009 (UTC)

[[Category:The games]]
[[Category:Silent Threat Campaign|*]]

FreeSpace Trivia

2009-07-08T00:12:43Z

Eishtmo: /* Cutscene quirks */

==Quirks==
===Mission-related Quirks===
* In [[The Place of Chariots]], the mission where you encounter the [[NTF Boadicea]], Volition used the facing-waypoint SEXP to ensure that the Boadicea never appears when the player is looking directly at it. If the player turns toward the area where the Boadicea appears and never turns away, the mission will never progress.
* The mission name 'Exodus' appears in all three Volition single-player campaigns (The Main FreeSpace Campaign, Silent Threat, and FreeSpace 2).
* The mission names 'The Great Hunt' and 'Clash of the Titans' (with/without II on the end) appear in both FS1 and FS2.
* [[As Lightning Fall]] is the only FreeSpace 2 mission with no beams mounted on any ship.
* In FRED, ships are autonamed by assigning a number to their ship class (for example, GTC Leviathan 5). However, if a ship already has the name about to be assigned by the autonamer, the name will be (humorously) shown as "U.R.A. Moron".
* [[The Place of Chariots]] and [[The Romans Blunder]] appear to have been designed as a linked pair of missions. The Freighters in the first mission appear in the second one and have been set to carry cargo containing the same things. Both freighters and cargo have been set to red alert.
* Rather bizarrely the [[Sathanas]] is set to red-alert in [[High Noon]]. We cannot be entirely sure what that means. It could be a simple mistake or it could be an indication that the Sathanas was meant to accumulate damage from a mission proceeding it (There is a systematic error in the Volition missions where they set red-alert-carry on both the mission proceeding the red alert and the red alert itself).
* The [[Azrael]] that carries off [[Bosch]] in [[Return to Babel]] is also set to red-alert.
* Most interestingly of all, Alpha wing in [[Their Finest Hour]] is set up to red-alert. This can indicate that the last three missions of the campaign were all meant to be played in sequence. This probably proved too difficult, so the first mission was turned into a stand alone.

===Ship-related Quirks===
* The Aten destroyed before the mission in La Ruota Della Fortuna is designated ''HLC Maltusa''.
* The SCv Moloch's fighterbay was never used in the main campaign. However, it was used in a multiplayer mission.
* The TTC 1 tech container does not appear at all in either the FS1 or Silent Threat campaigns. A few of them appear in [[...But Hate the Traitor]], during the FS2 campaign. It also appears in the FS2 cutscene "Colossus" (albeit slightly enlarged).
* The ship name Andromeda was used for three Vasudan ships and one Terran ship: the PVFR Andromeda in [[The Hammer and the Anvil]], the PVC Andromeda in [[The Pursuit]], the GTSC Andromeda in [[On the Run]], and the GVC Andromeda in a command briefing in [[Surrender, Belisarius|Surrender, Belisarius!]].
* The [[PVS Scarab|Scarab]] and the [[GVEP Ra|Ra]] have FreeSpace's only "in-game" depiction of a Vasudan, Shivan, or Terran. The "unmanned" Scarab has a dead Vasudan in its debris, while the Ra's story is somewhat more [[Find the MOON Challenge Results|interesting]].
* The Hermes, Centaur, Scarab, Nephythys, and Hygeia all have untargetable engine subsystems and can be disabled by a properly placed Harpoon shot. The Centaur in [[Enter the Dragon]] is ocasionally disabled by the ''Shakti's'' blob turrets, for example. The Ra has an engine subsystem as well, but for whatever reason, it cannot be disabled.
* In the second training mission of FS2, there is an installation named the Kos. It appears to serve no purpose in the mission.
* All GTVA warships in [[Their Finest Hour]] are beam-freed by SEXP. They are beam-freed at the start of the mission, before most of them warp in, so only one Sobek is able to fire its beams.
* The Vasudans have no equivalent to the massive [[GTT Argo|Argo]] or [[SFr Asmodeus|Asmodeus]]. To get around this, in [[Return to Babel]] the Vasudans actually use an Argo transport named the GTT ''Qeb''. There is Volition concept art for the GVT ''Qeb'' class, which was apparently never made.
* The [[FreeSpace 1 Vasudan Ship Database#HLD Prophecy|HLD ''Prophecy'']] in [[The Great Hunt]] is "Neutral". Most Hammer of Light ships are set this way in missions that also feature Shivans, to allow the two to engage each other.
* The [[GTD Hecate|''Hecate'']] model is apparently based off of the [[GTD Hades|''Hades'']] model. The bow, rear engine arrangment, and "vertical" superstructures are similar.
* Neither the [[SF Mara (Terrans)|Terran Mara]] nor the [[GVB Bakha|Bakha]] are ever "given" to the player using an allow-ship SEXP; they're only used in "scramble" missions. Nor is the [[GVB Sekhmet|Sekhmet]] "given" to the player; this ship is the only Terran or Vasudan fighter/bomber in FS2 that the player never has a chance to fly in the main single-player campaign. Note that you have a chance to fly the [[GTF Pegasus|Pegasus]] only once, in [[Endgame]].
* Viewed from the side, the [[GTI Arcadia|Arcadia]] resembles the [[GTA]] logo.
* The gas-miners [[GTG Zephyrus]] and the [[GVG Anuket]] have dockpoints named 'blahblah'.
* Almost all the freighters and transports of FreeSpace 1 have unused shield meshes. (The [[Elysium]], [[Chronos]], [[Poseidon]], [[Isis]], [[Bast]], [[Ma'at]], [[Satis]], [[Azrael]], [[Mephisto]] and [[Asmodeus]] are all included in this group). The shield meshes can easily be re-activated by editing the [[ships.tbl]]. None of the new freighters or transports included with FreeSpace 2 share this trait.

===Weapon-related Quirks===
* The BFGreen is only used once in the game (during [[Endgame]] and only on one of the Colossus' turrets).
* The LRBGreen was only used once, in [[High Noon]].
* You can target your own bomb using the target-object-in-reticle key as well as the proximity target key. If you have previously acquired an aspect lock on a target, your target display will show a video from the bomb's seeker. If you have not acquired an aspect lock yet, it will show the regular display.
* The player is granted the Cyclops#short before [[Slaying Ravana]]. The player actually uses Cyclops#shorts until the [[The King's Gambit]]; he is never granted the "real" [[GTM Cyclops|Cyclops]], but uses it anyway for [[The King's Gambit]].
* The [[Harbinger]] missile model is reused as the tip of the [[Stiletto]] missile model.
* The amount of damage that a beam can inflict on a friendly is limited. On Very Easy, Easy, Medium, Hard, and Insane, the limits are 0, 5, 10, 20, and 30 damage, respectively (per every ~.2 seconds).
* A [[FreeSpace Reference Bible]] command brief states that the Terrans or Vasudans "tried three different missile prototypes, with no luck whatsoever" against the Lucifer as it attacked "the Vasudan outpost in the Diones system".

===Other Quirks===
* There are only three canon references to ground warfare in FreeSpace. If the player wins [[Surrender, Belisarius|the first mission]] in FS2, he is told that 600,000 ground troops are sent to invade Cygnus Prime. Also, there is an FS1 multi mission where the player attacks an HoL marine convoy. Finally, the FS2 multi mission Rebel Intercept has the player intercepting NTF reinforcements headed to reinforce a ground battle in [[Sirius]].
* FS1 command brief and tech room .anis normally had readable text. Almost all FS2 .anis, however, have some kind of nonsense text. The Colossus cutscene has several blocks of text, all of them starting with "Math is cool." The Meson Bomb command brief animation reads like an advertisement (Guaranteed to blow anything up...).
* Almost every radio message in FS2, other than training messages, is accompanied by a head animation. Several radio messages in FS1, however, don't have a head animation. None of the freighter's messages in FS1 have one, and there are two instances of "Command" not having an animation. In [[Eve of Destruction]], if the Orff is destroyed, Command speaks without a head .ani. Also, in [[Paving the Way]], Admiral Wolf's messages have no head .ani. In the FS2 mission [[Mystery of the Trinity]], when the Trinity reaches critical damage, a pilot speaks without a head .ani. This is due to a bug with the personas.
* The only squadron leader or admiral that the player ever sees is Admiral Wolf. Admiral Wolf (Alpha 1's commander on the Galatea) appears once, in a cutscene (and also a few times in-mission with the normal command head .ani).
* The FS2 techroom animation for Sol shows the Earth facing "backwards" and rotating the wrong way.
* The FS1 Vasudan persona is not fully voice-acted.
* In [[ships.tbl]] in both FS1 and FS2, ship names beginning with an "@" indicate a ship that was present in the demo.
* FreeSpace contains many [[Node Inconsistencies|node inconsistencies]]. For example various FS1 command brief ANIs show 3 different nodes connecting Sol to other systems (but not all at once).
* Right-clicking in the mainhall allows you to cycle through interface choices.
* Mission sm3-05 in FS1 makes reference to an enigmatic "[[Ysusi]] System". In the mission briefing dispaly, there is a node labeled "Ysusi System" placed outside the view area.

==Bugs==

Software, mission design, and similar bugs.

* Exclusive to ''Descent: FreeSpace''; if a support ship is ordered to dock with the player through AI orders and not by player command, the player's ship will be thrown out of the game area at high velocity in an intense spin. Leaving the game area by warping is subsequently impossible due to the spin.
* The FreeSpace engine's solution to complicated collision problems is to fling one of the offending objects far out of the game area, in the order of 500,000 units. It was once a minor pastime of the FreeSpace community to see how far one could be "flung" after messing around with the Orion's fighterbay.
* In [[Love the Treason...]], the jump node to [[Regulus]] is named "Regulas".
* If you fire bombs into certain fighterbays, such as the [[GTI Arcadia|Arcadia]]'s, your bombs will fly in circles until they run out of fuel and explode.
* If you name an object "planet" in FRED, and you go near the object in-game, a message will appear saying "Too close to planet. Taking damage!"
* In the command briefing animation for [[The King's Gambit]], the strategy is described in "Stage One" followed by "Stage 2".
* Sentry 04 in 'Place of Chariots' is assigned the cargo "Unable To Scan".
* The TC-TRI cargo containers carried by Capricorn wing in "The Romans Blunder" are friendly.
* The GTI Ganymede is never used in the main FS2 campaign, although it appears in a multiplayer dogfight.
* The SCv Moloch's figherbay "paths" are misplaced. It also has an incorrect turret normal on one of its bottom laser turrets that allows the Moloch to fire through itself. This is a common problem with Volition FreeSpace models. For example, the GTFr Chronos can fire straight through itself.
* The Myrmidon fighter is able to carry Helios anti-matter bombs, but not Cyclops or other heavy weaponry. This never has a chance to be noticed in the main campaign, as the player only uses Helios in scramble missions. This is widely believed to be either a data entry error or some kind of joke.
* During asteroid escort missions, note that the game only "hurls" asteroids at ships on your escort list. Therefore, you can make these missions easier by removing all friendly vessels from your escort list. It is not known if the same rule applies for hostile ships as well. This may not work at all in FS1, as ships marked as "escort ship" in FRED cannot be removed from your list. FSPort players face no such restriction.
*The "big damage", "huge", etc. flags are not fully implemented in FS1; it's possible to kill the Lucifer with an ML-16. They are implemented in FS2, however.

==Design Changes==

This category includes both early development decisions that were later changed, game engine changes between FS1 and FS2.

* Act I of FreeSpace 1 (consisting of the missions up to [[First Strike]]) was originally released as ''Descent: FreeSpace: Darkness Rising''.
* Volition released a [[FreeSpace Alpha]] version to several reviewers before the release of FS1. The Alpha contained a stripped-down, incomplete version of FS1, with the two FS1 demo missions plus an original mission featuring a Fenris/Leviathan cruiser named GTC ''Juggernath''. The mission was dropped before the official demo shipped.
* According to a table file in FS2, [[Silent Threat]] had another weapon known as the "GTM-84 Corkscrew Missile", and was "deemed too wacky for final release."
* Despite what the training missions say, support ships never run out of secondary weapons.
* The SC Cain and SC Lilith cruiser originally had a different hull design, with two fin-like appendages protruding from the lower hull. These can clearly be seen in [[FreeSpace Alpha|alpha/beta]] screenshots.
* The Prometheus was originally introduced at much earlier time (sometime around [[The Big Bang]]).
* The mission First Strike originally had an asteroid field.
* The special-issue DVD release of Descent: FreeSpace used planet bitmaps as backgrounds like in FS2, as well as afterburner trails. These additional effects were also apparently included in the demo, although they are missing in the main release.
* If you export the Artemis/Ares/Nephtys/Ptah/Sekhmet POF to COB, you can see that the main object is called "herca", suggesting that they were either based on or were early concepts for the Hercules Mk II.
* The Bakha bomber was originally a fighter.
* Shivan ships were originally green in color.
* The [[SD Demon]] increased in hull strength 60% between FS1 and FS2, from 100,000 to 160,000 hitpoints. This may be meant to compensate for its weaker broadside relative to the Orion (otherwise the Shivans would have no decent destroyer except Sathanas).
* The Volition website [http://www.freespace2.com/bfod.cfm] states that FS1 had a 50 point penalty for rearming (62.5 points on Insane). This feature was removed in FS2.
* In the mission [[Into the Maelstrom]], there are 2 Elysium transports named Hauler 1 and Hauler 2. They have no purpose in the mission.
* [[Clash of the Titans]] had a Fenris class cruiser designated the Gladiator. Its arrival cue was set to [[false]], however.
* In [[Their Finest Hour]], the Colossus has a complicated waypoint path, implying that it was originally meant to have a complicated and dramatic battle with the Sathanas. In the final version, the waypoints are not used and the Colossus is disabled. Command orders the Colossus to warp out even though its engines aren't working.
* The FS1 voice VP contains some "alternate" voice acting for several missions. For example, the freighter and transport dialogue during [[First Strike]] was apparently first voiced by a woman.
* The command briefing for [[Enter the Dragon]] refers to "your investigation of [[SD Lucifer|Lucifer]] at [[Antares]]". [[Alpha 1]] had not even encountered the Lucifer at that point in the campaign.
* FRED1 (the mission editor for FS1) originally had a feature known as TBL info. It is now present in FRED2_OPEN.
* The [[SD Lucifer|Lucifer]] tech description in FS1 states that it has 3 "flux" cannons. However, it only has 2. The third beam (perhaps the one used for bombarding planets) was probably meant to be mounted on the bow of the ship. (Development notes specify that a beam is to be located on each set of three red circles.)
*The high-res Lucifer model that Volition used for cutscenes has two "antennae" that are not present in the in-game model. They were probably removed for aesthetic reasons, but the non-canon HTL Lucifer re-incorporated them. Also, the high-res Lucifer has several green lights along with its red lighting which are clearly visible in the endgame cutscene. Note that Shivan ships were originally intended to be green.
* Originally the first mission in Descent: FreeSpace had the player cast as part of the Orff's crew, not the Galatea's. This can be verified through briefing screenshots taken from the [[FreeSpace Alpha|alpha/beta]] releases.
* The [[FreeSpace Reference Bible]] seems to imply that groups ships jumping in from subspace were originally intended to all come through the same "hole", rather than each ship having an individual hole. (''The pilot is soon within sight of the Terran installation. As the pilot struggles to relay his story and keep his bomber from disintegrating, many subspace holes open up in front of him, out of which streams of Shivan fighters pour.'')
* There is a sound file in the FS1 VPs called "Approach.wav" that sounds like a fighter coming in to land on its carrier. This implies that Volition initially intended there to be a landing cutscene at the end of each mission, like Wing Commander. The file might also be a leftover from an earlier design choice with every mission ending with the player entering a docking bay. This was scrapped early on, due to it severely changing the way missions were played.
* The FS2 voice VP, stu_fs2.vp, contains voiceacting for an unreleased mission, M09. More information can be found on the [http://www.hard-light.net/forums/index.php/topic,42231.0.html Hard Light thread] on the subject.
*The reason why FreeSpace is called FreeSpace is because it actually is referring to subspace. Inside the reference bible, the following quote is found "''When scientists discovered what used to be called “FreeSpace” (now referred to as “subspace”)''"

==Renamings==

Most of these renamings were noticed in pre-release screenshots, model file names, or in FRED by looking at internal names used in the missions themselves.

* Hostile Vasudan wings were originally called "Steel", "Brass", "Iron", etc.
* Shivan wings were originally called "Cobra", "Viper", "Hornet", etc.
* The Cyclops bomb was originally named Belial.
* The Harpoon missile was originally named Crossbow. The name for the missile can clearly be seen in the FreeSpace 2 trailer.
* The Subach HL-7 laser was originally named Subach HL-33.
* The Subach HL-7 laser and Mekhu HL-7 laser were originally named Sidearm. The name SD-4 Sidearm can clearly be seen in the FreeSpace 2 trailer. Moreover, in the retail version of FreeSpace 2 the icon and animation files for the weapons are still called iconSD4 and SD4, respectively.
* The Akheton SDG laser was originally named DR-2 Scalpel. At some point during the development phase it was also known as Akheton DR-2.
* The Interceptor was originally called the Shrike. At one point it was also called the Mega.
* The Avenger laser was originally named Phalanx.
* The ML-16 laser was originally named Light Laser.
* The Harbinger was originally called the Mag-Pulse.
* The Prometheus was originally called the Flux.
* The Phoenix V was originally called the Angelfire.
* The Synaptic was originally called the Cluster.
* The MX-50 was originally called the Rockeye. The name is still present in the FreeSpace 1 demo.
* The Rockeye was originally called the Wasp.
* The GTW-83 Lamprey was originally called the Shrieker, and was later changed to GTW-83 Light Laser, before finally settling on the present name.
* The Hornet was originally called the Swarm.
* The GTW-66 Maxim Cannon was originally called the GTW-66 Newton Cannon.
* The Morning Star was originally called the Mace. Later in development the name was changed to Flail II. Ultimately, though, it was renamed Morning Star.
* The Hornet was originally called the Bombardier.
* NTF wings were originally called "Corsair", etc.
* Admiral Khafre's name was originally Admiral Hepsut ([[Surrender, Belisarius]])
* The GTD ''Aquitaine'' was originally named the GTD ''Intrepid''.
* The GTD ''Galatea'', was originally named the ITA ''Repulse'' ([[FreeSpace Reference Bible]]).
* The SJ ''Sathanas'' was originally named ''Apocalypse''. If you look at your event log after completing [[A Monster in the Mist]], you can still see a goal named "Scan Apocalypse Subsystems".
* The GTFr ''Chronos'' was originally named ''Boar''.
* The GVF ''Tauret'' was originally named ''Crab''.
* The SF ''Dragon'' was originally named ''Mosquito''.
* The Avenger Prototype was originally named Mass Driver Prototype.
* Shivan wings were also originally named "Scab Alpha", "Scab Beta", etc.
* For a long time the Apollo fighter was called ''SF-XX Generic Fighter''.
* In the [[FreeSpace_Alpha|Alpha]] version, the Fury Missile still used the graphics of the left-out G-13 Medium Laser. The laser weapon disappeared completely before the original FreeSpace 1 demo, and was unique to the Alpha version. (It also looks a lot like the Tsunami colored grey.)

==Cutscene quirks==

Allegedly, Volition contracted another company to make the FreeSpace cutscenes. They have several canon inconsistencies.

'''FreeSpace 1 Intro'''
* The "Apollo" pictured in the FS1 introduction cutscene is actually a modified version of the in-game Apollo. According to the FS1 reference bible, the Apollo in the intro cutscene is a "Terran bomber". Its gun mounts are slightly different and off-center, among other changes. Perhaps [[Volition]] placed the Apollo's gun mounts closer to the centerline for the sake of playability. The Manticore, too, has different fire points (mounted on the twin "booms" instead of centered like they are in the game).
* If you look carefully, you can see a (apparently dead) copilot in the front seat of the intro's Apollo-bomber. He is visible for less than a second. The [[FreeSpace Reference Bible]] refers to this copilot as the "gunner".
* [[GTF Hercules|Hercules]] and [[GTB Medusa|Medusa]] icons are shown on Riviera Station's radar display (although no Hercs or Medusas are visible in the cutscene).

'''Hallfight'''
* The captured Shivan vessel is called "Freighter", but it's actually an Azrael transport.

'''FreeSpace 2 Intro'''
* Many community members claim that the destroyer holed in the intro is the [[GTD Legion|GTD ''Legion'']]. However, FreeSpace 1 command briefs claim that the ''Bastion'' and ''Galatea'' are guarding Deneb, and makes no reference to any other Terran destroyers guarding the system. [[Volition]] stated that this ship was not the ''Galatea'', and the Bastion does not bite the bullet until nearly the end of FS2.
* The name [[GTD Legion|GTD ''Legion'']] is the result of a campaign designer asking if he could call the destroyer "Legion" for the campaign. Dave B. said the designer could because the ship did not have a name. This is the closest to an actual name that Orion will ever have.
* A Shivan [[Demon|''Demon'']]-class destroyer appears after the destruction of the ''Legion'', even though the only Shivan destroyer (other than the ''Lucifer'') in the system, the [[SD Eva|''Eva'']], was already destroyed in [[Evangelist]].
* The [[Ursa]] is shown even though it was not finished with R&D until after [[Running the Gauntlet]].
* None of the [[Fenris]] cruisers had their missile launchers shown.
* A Hercules is shown crashing into the planet after getting shot down. It sits on the planet surface, relatively undamaged. In reality, an object in uncontrolled descent from orbit with the mass of a FreeSpace 2 fighter (which is hardly budged by "mutli-kiloton" missiles) would leave a deep crater in the ground. The pilot would experience extreme g-force upon impact and would not be alive to climb out of the cockpit as he apparently does in the cutscene.
* The Hades is shown as a wreck on the surface of the Deneb planet. Silent Threat command briefings indicate that the Hades was destroyed in [[Beta Aquilae]].

'''Colossus cutscene'''
* The Ganymede in the cutscene is several times bigger than normal.
* The ''Lucifer'' is smaller than normal.
* The Chronos freighters have two turrets (as opposed to the usual one), and the turrets look different.
* The Chronos freighters were either much smaller or the TTC 1 cargo much bigger.
* Mirfak is named Mirfax.
* The Galatea appears in the Colossus fleet.

=="Real Life"==

This category includes mainly business decisions, but also interesting connections between FreeSpace and RL.

* FreeSpace 1 was officially distributed as "Conflict: FreeSpace - The Great War" in Europe and "Descent: FreeSpace - The Great War" in the United States.
* The [[GTM Infyrno]] is a deliberate misspelling of Inferno, for copyright reasons.
* It's FreeSpace, not Freespace (notice the capitalization of the S).
* FreeSpace 1 is called Descent: FreeSpace in the US due to copyright issues with the disk compression utility FreeSpace.
* ''FreeSpace 2'' was originally named ''FreeSpace 2: Colossus'' (for the demo). Even before that, it was named ''FreeSpace 2: Exodus''.
* In Greek, the plural of Knossos is Knossoi, and the plural of Sathanas is Sathanai (ancient Greek) or Sathanes (modern Greek). These are loose translations; Sathanas is simply the Greek representation of the Hebrew word for Satan. Volition always circumvented the plural by using phrases such as "Sathanas juggernauts".

==Canon inconsistencies: Retail FS2 box==

Several [[canon]] inconsistencies are present on the retail FS2 box (although these inconsistencies are not generally accepted as canon themselves): [[Image:Freespacebox-1a.JPG|thumb|'''The front side of the European box edition.''']]
[[Image:Freespacebox-2a.JPG|thumb|'''The back side of the European box edition.''']]

* The Deimos is listed as an AWACS ship (on the backside of the box there is written "GTA Deimos"). However, the following text specifies that the ship class is "corvette". (Can be seen in the back side of the box)
* The Deimos has side-mounted multipart turrets that are not present in the game, or even possible under the game engine. (Can be seen in the ftont side of the box)
* The Deimos's turrets are not firing Terran Turrets. Instead they are firing Kayser-like lasers. (Can be seen in the front side of the box)
* Only the Perseus in front of the Deimos has engine thrusters. (Can be seen in the front side of the box)
* On the European version of the box, the ''Lucifer'' is visible just at the right of the first Deimos's top turret. (Can be seen in the front side of the box)
* On the European version of the box, the Deimos is a destroyer (the nameplate on the corvette says "..D Deimos"). (Can be seen in the front side of the box)
*In the back side of the box, the text below the rightmost screenshot says: "Encounter 'beam weapons' that can penetrate and utterly carve gigantic capital ships in half." However, beams in the game cannot cleave anything in half.
*In the introduction (back side), the last paragraph says: "Your nemesis has arrived... and they are wondering what happened to their scouting party." This statement is ambiguous, because it can refer to the Shivan force that attacked in 2335 (FreeSpace 1) or the scouting part that destroyed the GTC ''Vigiliant''.
* The Italian version of the box says that beam weapons can be used also by fighters, according to the blurb on the back ("Imparate a usare le armi a raggi...", "Learn to use beam weapons...") (Not shown in the thumbnails provided below)

[[Category:The games|Trivia]]

Talk:Timeline

2005-11-21T19:18:21Z

Eishtmo:

Hello? Is this thing working? If you're reading this, say something silly.

Timeline

2005-11-15T06:32:47Z

Eishtmo:

Please note that the Unification War and 14-Year War timelines are non-canon, developed by Eishtmo for the TVWP campaign. For the sake of consitency and due to the lack of anything official, they are being included here for completeness.

*2300-2320: [[Unification]] - Not Canon
*2320-2335: [[The 14-Year War]] - Data within may not be canon
*----2335--- : [[The Great War]]
*2335-2366: [[Reconstruction]] - Data within may not be canon
*2366-2367: [[The NTF Rebellion]]
*----2367--- : [[The Second Shivan Incursion]]
*2367-2400: [[Post-Capella]] - Not Canon

The above is being left in place as A)I'm curious where the author got the dates for the NTF and Shivan Incursion stuff and B) some of it is actually pretty correct. The Unification and 14 Year War sections are NOT canon and are background information for the Terran-Vasudan War Project. Below is the closest to a canon timeline, sans the game time lines, that can be compiled. - Eishtmo

~8000 BC: Dynasty of 10,000 Years established on Vasuda Prime

~6000 BC: Ancients Civilization destroyed by Shivans

2313: Subspace discovered by Terrans

?: Galactic Terran Alliance formed

~2317: Ma'at transport enters service

2321: Terran-Vasudan War (14 Year War) begins

?: Leviathan construction ordered 
Probably "a few months" after start of war

2323: Battle of Rexis 4 
GTD Goliath destroyed 
Anubis fighter confirmed 
First use of Anubis as kamikaze fighters

?: Battle of Gulnara 
Victory for Terrans 
Leviathan production halted

?: Battle of Talania System 
Terran Defeat 
Leviathan production restarted

?: Aldebaran Encounter 
Satis freighter enters service

~2327: Elysium transport enters service 
*Contradiction: FS1 says since colonization began* 
Thoth fighter production begun 
*Contradiction: FS1 says built with Ulysses fighter, 2335* 
107th Ravens Founded 

2333: Vega Engagement 
Typhon class destroyer appears 
GTD Eisenhower and 4th fleet destroyed

2335: 14 Year War ends 
Great War begins in Jan, ends Dec 
Lucifer destroyed in March 
GTA Provisional Government established in Delta Serpentis 
Hades Rebellion 

?: Terrans divide into four groups: 
Adhara Coalition 
Antares Federation 
Regulus Syndicate 
Luyten New Alliance 

2339: Emperor Khonsu II dissolves Vasudan Parliament

2345: Galactic Terran-Vasudan Alliance established

2347: GTVA Colossus construction started 
Bes freighter enters service

2352: GTSC Erikson visits Gamma Draconis 
~Cyclops bomb enters service

?: Operation Templar

~2353: Hecate class destroyer commissioned

2358: Beta Aquilae Convention 
Formal dismantling of Terran blocs 
Formation of General Assembly, Security Counsel and Vasudan Imperium

2360: Hatshepsut class destroyer commissioned

2365: Neo-Terran Front Rebellion begins 
Aeolus class cruiser production halted

2366: Lieutenant Commander Christopher Snipes 'defects' to the NTF

2367: Second Shivan Incursion