FreeSpace Wiki - User contributions [en]

Ancient-Shivan War

2008-12-07T13:59:09Z

Stormkeeper: Creating the first version of the Wiki entry for ASW

'''''Ancient-Shivan War''''' is a mod for FreeSpace 2 Open that attempts to replicate the battles between the Shivans and the Ancients.

==Plot==
The '''''Ancient-Shivan War''''' takes place in the distant past, putting the player in the role of one of the many Ancients as they fight desperately, and ultimately futilely, to save their empire and home from the Shivans. The player will have the opportunity to pilot numerous Ancient ships as he takes part in their struggle for survival.

==ASW Team==
*ShadowGorrath - Mod Leader, Tabling, Packaging, General Modder
*Droid803 - FREDder, General Modder
*FreeSpaceFreak - Effects, Planets, Mission backgrounds, other graphical stuff
*FreeSpaceKing - Maps and UV Mapping
*Stormkeeper - FREDder, Websites

==External Links==
* [http://www.sectorgame.com/ASW Website]
* [http://www.sectorgame.com/forums/viewforum.php?f=54&sid=0a0de80d7241420478a827c1ab3b86b3 Forum]
* [http://www.hard-light.net/forums/index.php/topic,53686.0.html Old ASW discussion on HLP]

134th Barracudas

2008-08-23T00:45:05Z

Stormkeeper: Corrected grammatical errors and spelling.

==General==
Squadron type: Combat evaluation unit 
Craft used the most: [[GTF Perseus|GTF ''Perseus'']] 
Stationed on-board: [[GTD Aquitaine|GTD ''Aquitaine'']] 
Squadron leader: Commander Vincey 

==Actions==
The '''134th Barracudas''' squadron, being an evaluation unit, tests weapons and reports their efficiency to superiors, often subjectively. When the NTF forces were withdrawing from [[Polaris]] and [[Regulus]], the Barracudas squadron was assigned to the nebular theater to test the new [[GTM TAG-A|Target Acquisition and Guidance missiles]] and the [[GTF Pegasus|''Pegasus''-class stealth fighter]].

The Barracudas faced some Shivan resistance while escorting the convoy which was carrying the prototypes. The convoy ships suffered no casualties and the test could commence as planned. The pilots who were assigned to test the TAG-A missiles soon faced a horde of Shivan fighters, and were outnumbered and outgunned. With the assistance of the GTCv ''Warspite'' and arriving reinforcements, the pilots survived the engagement.

The next step was to test the [[GTF Pegasus|Pegasus fighter]] which also did not proceed exactly as planned. The [[GTD Aquitaine|GTD ''Aquitaine'']] was ordered to withdrawn and pilots from the Barracudas escorted the destroyer until she made it back to jump node to [[Gamma Draconis]].

----

==Speculative, non-canon==
It seems clear the Barracudas assisted with testing the [[AWACS]] ship, the [[GTA Charybdis|GTA ''Charybdis'']], on its "official" OpEval period, however it was already in service with the SOC before this date. It is, however, fairly certain the Barracudas did not test the [[GTF Erinyes|GTF ''Erinyes'']] or the [[GTW UD-8 Kayser|UD-8 Kayser]] in combat; these were rushed direct from SOC testing to "in-service" status, likely due to the second Sathanas.

[[Category:Squadrons]]

FS Short Hand

2008-08-04T05:02:23Z

Stormkeeper: Bolded the terms for easier reading

'''Ingame Terminology'''
----

'''Wing''' - A unit of fightercraft, varying in size from one to six ships. The normal number is four. Ships of a wing are labelled by their wing name and a number (i.e. Alpha 1, Alpha 2, and so on). The GTVA uses the Greek alphabet for its wings and the signs of the zodiac for hostile wings. In FS1, Shivan wings were named after Hindu gods.

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

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

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

'''Superdestroyer''' - Bigger, meaner, and tougher than a destroyer, yet too small for the juggernaut classification; first applied well before the juggernaut classification came into existence. Only the [[GTD Hades|''Hades'']] and [[SD Lucifer|''Lucifer'']] have canonically been given this classification.

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

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

{{non-canon}}

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

* [[EACa Telemus]]
* [[EACa Auriga]]
* [[GVCa Tanen]]
* [[SCa Shiamak]]

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

* [[SFg Damini]]

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

'''Planet Destroyer''': A Juggernaut-sized ship specificately tasked to destroy planets. It is equipped with shields, effectively used to protect the hull from the explosion of a planet.

* [[SPD Vinaashak]]

'''Super-Juggernaut''': Equivalent of an entire armada of ships, the Super-Juggernaut is an almost invincible weapon. They're armed with huge anti-fleet cannons and moderately defended against bomber attacks; their main defense is sheer size and damage-absorbative potentional. Ships of this size are often referred to as "plot tools" rather than actual ships, as a single fightercraft cannot reasonably be expected to do them noticible harm.

* [[TSJ Icanus]]
* [[SSJ Gigas]]

'''Hive''': Even larger than the Super-Juggernaut, the Hive is a massive Shivan ship.

* [[SH Gargant]]

NTF Iceni

2008-07-24T06:29:20Z

Stormkeeper: /* Veteran Comments */

The '''NTF ''Iceni''''' is the command frigate of the [[Neo-Terran Front]], built under Admiral Bosch's direction at the Freedom shipyards in [[Polaris]], captured by the Neo-Terran Front at the start of their [[The NTF Rebellion|rebellion]]. With over two dozen turrets and a sheath of ultra-dense depleted uranium shielding around its subsystems, the ''Iceni'' is an extremely tough nut to crack. With Bosch on board, providing tactical guidance, the ''Iceni'' is the equal of any GTVA battle group. Intelligence believes the ship was custom-designed for a secret NTF project.

----

{{FS12_Ships}}
{{shipimage|image=[[Image:Iceni320x240.jpg]]|caption=The NTF Iceni}}

==Description:==

===FS2 Tech Room Description===
The Iceni is the NTF command frigate, built under Admiral Bosch's direction at the Freedom shipyards in Polaris, captured by the Neo-Terran Front at the start of their rebellion. With over two dozen turrets and a sheath of ultra-dense depleted uranium shielding around its subsystems, the Iceni is an extremely tough nut to crack. With Bosch on board, providing tactical guidance, the Iceni is the equal of any GTVA battle group. Intelligence believes the ship was custom-designed for a secret NTF project.

===Developer Notes===
None

===Name Origin===
The Iceni were a tribe of Celtic people who lived in what is now the county of Norfolk in Great Britain. They rebelled against Roman rule under their queen, Boadicea.

==Performance:==
===Statistics===
{{Ship Stats|Frigate|Freedom Shipyards|N/A|35.0|N/A|N/A|90 000|N/A|998}}

===Armaments===

*'''[[Technical_Terms_and_Definitions#Turrets|Turrets]]'''
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=2 style="background:#351515;"| '''Freespace 2'''
|- align="center"
| style="width:120px" |Turret Type
| style="width:60px" |Amount
|- align="center"
| [[Terran Turret]]
| 9
|- align="center"
| [[Terran Huge Turret]]
| 7
|- align="center"
| [[Standard Flak]]
| 2
|- align="center"
| [[MX-52]]
| 2
|- align="center"
| [[GTM Piranha|Piranha]]
| 2
|- align="center"
| [[BGreen|Big Green Beam]]
| 3
|}

==Veteran Comments==
{{Comment|
''The Iceni has decidedly FS1-era anti-fighter armament, but if your capital ship approaches from the right side, prepare for a severe beatdown as it cuts loose with paired BGreens. The other side of it has a single version of this useful anti-capital beam. The Iceni is capable of tearing a Deimos or Sobek to shreds, so while it may be corvette-sized, it is destroyer-armed. Under the correct circumstances this ship is quite capable of going toe-to-toe with any GTVA destroyer, or even an [[SD Demon]].''

''The Iceni is in a class of its own. It has slightly better armour than any other corvette, nearing that of a destroyer, and is a very speedy for a vessel its size. It has massive primary firepower in the form of 3 BGreens, but lacks an anti-fighter capability. And despite its three beam cannons, an Orion would have it for lunch. The main reason why this vessel was built IMO was to quickly reach the nebula and fend off most threats blocking the way. It was designed to be able to get to jump nodes ASAP and with minimal damage, and redundant engine subsystems help accomplish that.''

''However, its anti-fighter capability is noticeably less than that of the [[GTCv Deimos]] or even the [[GVCv Sobek]]''

''While one would say from the Table files that the Iceni has FS1 anti-fighter arnament, in the SOC-loop mission "Rebels and Renegades", the Iceni is seen using both Flak and Anti-fighter beams.''

''Its notable that the Iceni's anti-capital armament isn't distributed evenly, as mentioned above, approaching from the right is a far more dangerous proposition. The Iceni seen in-game is non-standard as it appears on the tables, mounting a few anti-fighter beams in the place to Terran Turrets.''
}}
[[Category:Unique ships|Iceni]]
[[Category:Ship]]

The Babylon Project

2008-07-21T03:17:42Z

Stormkeeper: Corrected Release link, previous one pointed to internal forum

{{TBP}}

'''''The Babylon Project''''' (TBP) is a stand-alone total conversion based on the Babylon 5 universe created by J. Michael Straczynski. It features large amount of ship and different species from the Babylon 5 universe.

The Babylon Station is a dream given form. It is a 5 mile long space station built in neutral territory orbiting the planet of Epsilon 3. A place for commerce and diplomacy where diverse populations can gather calmly without the threat of war and discuss their differences with the hope of understanding each other and settling their disagreeements peacefully. But not all disputes can be solved peacefully...

The Babylon Project features over 120 Ships of over 11 species or factions including the Earth Alliance Omega Class Destroyer, the Centauri Primus Class Battle Cruiser or the Vorlon Star Dreadnought. It also features the latest effects from the Source Code Project (high detailed textures and graphics and the "Glide-Mode" for some fighters).
High quality soundeffects and the original soundtrack from the famous TV-show are also included.

A increasing number of fan-made campaigns and dozens of single player missions are available for download.

 
'''Release Info:'''
:[http://www.hard-light.net/forums/index.php/topic,51780.0.html The Babylon Project 3.4 beta patch (4th April 2007)]

'''Homepage:'''
:[http://babylon.hard-light.net/ Link to TBP homepage]

'''Mods:'''
:[[TBP shiplist]]

[[Category:Total Conversions]]

Talk:References

2008-07-21T03:09:04Z

Stormkeeper:

These are obsolete, yes? - [[User:Snail|Snail]] 13:06, 20 July 2008 (CDT)

:Should be merged with something, if no one has done that already. - [[User:TopAce|TopAce]] 15:18, 20 July 2008 (CDT)

:The weapon data is reproduced almost identically on the [[Weapon Comparison (FS2)|weapon comparison tables]]. There's no such table on the wiki for the ships (that I know of), but all of the information is in the table files, so with or without these links, the data would be easy to cobble back together. -- [[User:BlueFlames|BlueFlames]] 16:07, 20 July 2008 (CDT)

::Maybe we could create a page for the ships references? [[User:Stormkeeper|Stormkeeper]] 22:09, 20 July 2008 (CDT)

GTD Orion

2008-07-17T14:42:21Z

Stormkeeper: /* Veteran Comments */

{{FS12_Ships}}
{{shipimage|image=[[Image:orion320x240.jpg]]|caption=The GTD Orion}}
The '''GTD ''Orion''''' was a standard Terran destroyer mainly used during the [[The Great War|Great War]]. After the appearance of [[beam weapons]] and the development of the [[GTD Hecate|GTD ''Hecate'']], Orions somehow lost their previous esteem and were gradually replaced by more advanced warships.

==Description:==

===FS1 Tech Room Description===
The Orion is the capital ship of the GTA. Measuring a frightening 2.1 kilometers in length, the cost to build one of these far outweighs the cost of paying the crew of this ship for 3 years. There is no more important symbol of Terran Pride than a ship like the Galatea or the Intrepid cruising past a colonized planet, patrolling the system and ensuring safety. In the course of the 14 year war, very few of these have ever been lost, making the destruction of an Orion a truly horrible defeat.

===FS2 Tech Room Description===
For over 30 years, the GTD Orion class was the largest ship in the Terran-Vasudan armada. Over two kilometers in length, bristling with dozens of death-dealing turrets, the Orion is as awesome in repose as it is in battle. All GTVA Orions have been retrofitted with the latest anti-warship beam weapons, as well as flak and AAA turrets for dealing with fighters and bombers. The Orion's cavernous hanger bays easily accommodate more than two dozen fighter or bomber wings.

===Developer Notes===
None

===Canon Orions===

''Note: The Orions that have actually appeared in-mission are bolded. At least one of the FreeSpace 1 ships may not be an Orion, but some other class of GTA destroyer. However, all of the NTF Orions have either appeared in-game or have been shown in a Command Briefing to be an Orion-class, with the exception of the ''[[NTD Jacobus|Jacobus]].

''[[GTA]]/[[GTVA]]:''

*[[GTD Amadeus|GTD ''Amadeus'']]
*'''[[GTD Bastion|GTD ''Bastion'']]'''
*'''[[FreeSpace 2 Terran Ship Database#GTD Carthage|GTD ''Carthage'']]'''
*'''[[GTD Galatea|GTD ''Galatea'']]'''
*'''[[GTD Intrepid|GTD ''Intrepid'']]'''
*'''[[GTD Krios|GTD ''Krios'']]'''
*'''[[FreeSpace 2 Terran Ship Database#GTD Messana|GTD ''Messana'']] '''
*[[GTD Minnow|GTD ''Minnow'']]
*[[GTD Nereid|GTD ''Nereid'']]
*[[GTD Soyakaze|GTD ''Soyakaze'']]

''[[Neo Terran Front]]:''

*[[FreeSpace 2 Rebel Ship Database#NTD Andronicus|NTD ''Andronicus'']]
*[[FreeSpace 2 Rebel Ship Database#NTD Cyrene|NTD ''Cyrene'']]
*[[NTD Jacobus|NTD ''Jacobus'']]
*[[FreeSpace 2 Rebel Ship Database#NTD Normandy|NTD ''Normandy'']]
*'''[[NTD Repulse|NTD ''Repulse'']]'''
*'''[[NTD Uhuru|NTD ''Uhuru'']]'''
*[[FreeSpace 2 Rebel Ship Database#NTD Vasa|NTD ''Vasa'']]
*'''[[NTD Vindicator|NTD ''Vindicator'']]'''

===Name origin===
In Greek mythology, Orion was a notorious hunter. There are numerous stories about his life.

Orion is also one of the many known large constellations. The constellation is also referred to as "The Hunter."

==Performance:==
===Statistics===
{{Ship Stats|Destroyer|Unknown|N/A|15.0|N/A|N/A|100 000|N/A|2023}}{|-
| style="width:200px"|'''[[Technical_Terms_and_Definitions#Fighter Complement|Fighter Complement]]'''
| style="width:200px"|96 - 120 (estimate)
|}

===Armaments===

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

==Veteran Comments==
{{Comment|
''Despite the introduction of the new Hecate class of destroyers, the aging Orion still remains a vital part of the GTVA arsenal. With the Hecate designed with an emphasis on protection from fighter and bomber attacks, the Orion remains the king of capital ship combat - With heavy beam emplacements capable of laying down devastating fire in nearly all directions, it is a true terror to any capital ship that strays into its firing range.''

''However, its age does show in one area. Being designed in an era where fighter and bomber ordnance was far inferior to today's weaponry and where shields were nonexistent, it carries very few dedicated anti-fighter turrets, making it an easy target for bomber wings should it ever be left without fighter escort.''

''The Orion only carries eight squadrons of fighters to the [[GTD Hecate|Hecate's]] twelve, but has massively more firepower, arranged better on its hull. The [[GTD Bastion]], however, canonically lists ten squadrons, it must be assumed that these are not full squadrons (twelve fighters per full squadron) or that the Bastion is not a typical Orion.''

''Great at eliminating capital ships. Those 6 anti-warship beams are nothing to laugh at. Rather vulnerable to enemy fighter craft but not as badly as people give it credit for. However, if you needed proof all warships over cruiser size need flak cannons, this would be it. The laser turrets cover long-range bomb destruction fairly well, but without flak, bombers could simply go closer and then let loose''

''It is worth noting that not all the canonical Orions in Freespace II mount standard weaponry, at least one (the NTD Uhuru) mounts [[Standard Flak|Flak Guns]] on its upper turrets.''

''If you're looking for a true descendant of ''HMS Dreadnaught ''in FS, put the Orion at the top of the list. Under ideal conditions it can bring two BGreens and two TerSlash to bear on a target; the heaviest broadside any GTVA destroyer can muster.''

''One thing worth noting is that the tech description is a bald-faced lie: the Orion does not have "dozens" of turrets. The fact is that it barely has a single dozen of them.''

''To be exact, the Orion has a dozen and one third turrets. This lack of turrets does not, however, compromise its ability against capital ships. Though the same cannot be said against a fighter assault.''}}

[[Category:Ship]]

Talk:GTD Hecate

2008-07-17T05:29:09Z

Stormkeeper:

Weird how the Hecate has a Terran Huge Turret in the middle of nowhere. I think it was meant to be a Terran Turret. Shouldn't it be fixed and made default? - [[User:Stormkeeper|Stormkeeper]] 06:50, 16 July 2008 (CDT)

No. It's a canon ship, so that is not for us to decide. - [[User:Shade|Shade]] 10:12, 16 July 2008 (CDT)

Talk:GTC Aeolus

2008-07-17T05:21:16Z

Stormkeeper:

Go into FRED.

Set up a mission with 4 Artemis attacking an Aeolus.

Watch the Aeolus die while inflicting barely any damage on the attacking bombers.

Make another mission. Send 4 Artemis to kill a Leviathan.

The Leviathan will die, but bring half of the bombers down with it.

Although the Aeolus has a lot of flak, this stuff is very bad at shooting down bombs. Blob turrets seem much better at that. Plus, it only has two anti-fighter beams, which are what really kills fighters and bombers. The Leviathan has ''four''. Why does this article claim that the Aeolus is such a great ship? Mind if I edit it? Mustang19 Apr 17 2007

:'''Ngtm1r'''... People are entitled to have their opinions. Calling them liers isnt going to help at all. So if you really have any opinions or comments about this please post those but leave the flaming elsewhere.
:'''Mustang19''', as for the actual article.. i think some of the more 'outrageous' comments are in the tech descriptions and those are '''''NOT''''' to be edited. However you may add your comments to the 'veteran comments' section. - [[User:Wanderer|Wanderer]] 00:54, 23 April 2007 (CDT)

I just realized something. If you count up all the Aeolus cruisers in the canon FS2 named ship list, it adds up to 23 already, meaning that any campaign that is using more than one Aeolus not on the list should actually explain why there are more. Unless, of course, you dismiss the 24 Aeolus limit as non canon.
Vigilant, Warwick, Agrippa, Stalwart, Templar, Malta, Ertanax, Sparta, Ascendant, Ashaton, Zanthar (11 - GTVA)
Camisard, Alexandria, Liberty, Epigoni, Loyola, Mylae, Hellespont, Saharan, Retribution, Righteous, Vindication, Vengeance (12 - NTF)
- [[User:Droid803|Droid803]]

:I know. I was counting too. - [[User:Stormkeeper|Stormkeeper]] 12:45, 16 July 2008 (CDT)

::Bear in mind that three of those appear in multiplayer missions that are described as simulations, so you can argue that there are four available, without the need to write in additional production. -- [[User:BlueFlames|BlueFlames]] 13:33, 16 July 2008 (CDT)

:::Still, 4 surviving cruisers spread through out the entire GTVA territory is abit stretching it. Which means the Fenris and Leviathans pick more than their far share of the slack. [[User:Stormkeeper|Stormkeeper]] 00:21, 17 July 2008 (CDT)

Talk:GTC Aeolus

2008-07-16T17:45:06Z

Stormkeeper:

Go into FRED.

Set up a mission with 4 Artemis attacking an Aeolus.

Watch the Aeolus die while inflicting barely any damage on the attacking bombers.

Make another mission. Send 4 Artemis to kill a Leviathan.

The Leviathan will die, but bring half of the bombers down with it.

Although the Aeolus has a lot of flak, this stuff is very bad at shooting down bombs. Blob turrets seem much better at that. Plus, it only has two anti-fighter beams, which are what really kills fighters and bombers. The Leviathan has ''four''. Why does this article claim that the Aeolus is such a great ship? Mind if I edit it? Mustang19 Apr 17 2007

:'''Ngtm1r'''... People are entitled to have their opinions. Calling them liers isnt going to help at all. So if you really have any opinions or comments about this please post those but leave the flaming elsewhere.
:'''Mustang19''', as for the actual article.. i think some of the more 'outrageous' comments are in the tech descriptions and those are '''''NOT''''' to be edited. However you may add your comments to the 'veteran comments' section. - [[User:Wanderer|Wanderer]] 00:54, 23 April 2007 (CDT)

I just realized something. If you count up all the Aeolus cruisers in the canon FS2 named ship list, it adds up to 23 already, meaning that any campaign that is using more than one Aeolus not on the list should actually explain why there are more. Unless, of course, you dismiss the 24 Aeolus limit as non canon.
Vigilant, Warwick, Agrippa, Stalwart, Templar, Malta, Ertanax, Sparta, Ascendant, Ashaton, Zanthar (11 - GTVA)
Camisard, Alexandria, Liberty, Epigoni, Loyola, Mylae, Hellespont, Saharan, Retribution, Righteous, Vindication, Vengeance (12 - NTF)
- [[User:Droid803|Droid803]]

I know. I was counting too. - [[User:Stormkeeper|Stormkeeper]] 12:45, 16 July 2008 (CDT)

Talk:GTD Hecate

2008-07-16T11:50:32Z

Stormkeeper: New page: Weird how the Hecate has a Terran Huge Turret in the middle of nowhere. I think it was meant to be a Terran Turret. Shouldn't it be fixed and made default?~~~~

Weird how the Hecate has a Terran Huge Turret in the middle of nowhere. I think it was meant to be a Terran Turret. Shouldn't it be fixed and made default?[[User:Stormkeeper|Stormkeeper]] 06:50, 16 July 2008 (CDT)

FreeSpace 2 game information

2008-07-15T08:33:01Z

Stormkeeper: /* Features */

=FreeSpace 2=
Released: October, 1999 
Developed by: Volition Inc. 
Published by: Interplay 

No age restrictions

Sequel of the award-winning FreeSpace: The Great War

==Story==
Thirty-two years have passed since the end of the Great War, we are now in the year of 2367. Ten years after the destruction of the [[SD Lucifer]] in the [[Sol]] system, the Terran and Vasudan species forged a new alliance, called the [[Galactic Terran-Vasudan Alliance]]. The [[Reconstruction]] period began in the galaxy as both races prepare their civilisations for the return of the [[Shivans]].

Even though, not everything goes very well: Admiral Aken Bosch formed the [[Neo-Terra Front]], a true alliance of an ideal considered hostile by the [[Galactic Terran-Vasudan Alliance]]. Both sides have been at war with each other for eighteen months now. [[Deneb]], [[Alpha Centauri]] and [[Epsilon Pegasi]] are the focus points in this war. 
Admiral Bosch's rebellion seems to be winning.

==Features==
*Enhanced graphics
*A completely new and alien environment: The nebula fog
*Be assigned to up to six fighter squadrons, from the Vasudan 203rd Scorpions to the elite 70th Blue Lions!
*Fly for the SOC, [[Special Operations Command]].
*Over 20 weapons of mass destruction
*A thirty-mission single player campaign and even more multiplayer missions!
*Encounter deadly new capital ship weapons: the Flak guns and Beam cannons
*Attack up to 8 players via LAN or TCP/IP
*Over 70 new ships, ranging from Super Capital ships to stealth fighters
*FRED, the easy-to-use mission editor
*Reasonable moddability

==System requirements==
===Minimum===
*Pentium 200MHz
*Windows 95/98/NT with DirectX 6.0 or newer
*32 MBytes of RAM
*400 MB Hard Disk space
*8x CD-ROM
*DirectSound certified video card
*Hardware accelerated card

===Optimum===
*Pentium 266MHz
*64 MBytes RAM
*8 MBytes Video memory
*3D Sound card with EAX or A3D

==Reviews==
===Home of the Underdogs Description (By Karajorma)===
Undoubtedly one of the best 3D space combat games ever made, Freespace 2 by Volition is a superb space opera of epic proportions. The strong emphasis on plot development combined with spectacular graphics and story-based missions make Freespace 2 a worthy contender to Origin's more well-known Wing Commander games. In fact, in my humble opinion the fun factor of Freespace 2 far surpasses that of Prophecy Gold, the last Wing Commander game, by a considerable margin.
The game begins with an alliance of humans and alien Vasudans attempting to rebuild their armies 32 years after the end of 'The Great War,' the battles of which were the subject of Freespace. You play a member of the GTVA, a Human-Vasudan alliance which is fighting a group of human rebels who call themselves the NTF.

Freespace 2 improves upon the excellent Freespace in every respect. Pre-mission elements such as the briefing session and ship configuration are superbly presented, with a lot of details and options to choose from. Frequent cutscenes made with rendered graphics are captivating, especially because outstanding voice acting makes them as absorbing to watch as real-life actors in Origin's Wing Commander IV (the cutscenes, except for the endings, are unfortunately missing in this CD-rip, but fortunately they are not necessary to your knowledge of the plot, since you can tell how the storyline is unfolding during briefing and de-briefing scenes). The game's emphasis on the plot is not just window-dressing, either: as in Wing Commander, your choices as well as mission successes and failures determine how the plot will develop, and ultimately what ending you will see. Even during the missions themselves, your objectives may suddenly change when new backstory-related developments take place. Being able to think "at the seat of the pants" to quickly adapt to changing circumstances is the key to winning in Freespace 2.

In terms of gameplay, Freespace 2 is basically a 'bigger and better' Freespace. Capital ships now have awe-inspiring proportions and are able to fight each other. This makes for many a memorable scene when you are caught like a tiny fly in the middle of capital-ships-only combat with cannons and turrets and huge beam weapons that are wider than your spacecraft. The game universe is much larger than in Freespace. Volition also adds a lot of nice graphical details, such as the cool-looking (and appropriately opaque) nebula, on top of much prettier 3D graphics. There are many new ships in the game in addition to all the ships from Freespace, more varied and more powerful weapons, and more diverse missions. The strategic aspect has also been much improved: your success in some missions depend as much on your strategic choices as your joystick expertise. Should you send a couple of wingmen ahead to recon enemy ships, or have them protect vulnerable ships? Should you take out the enemy bombers first, or the agile fighters? In-game choices such as these can spell the difference between life and death.

In addition to the superb single-player campaign, Freespace 2 includes full multiplayer support: up to 12 players via LAN or the Internet (PXO and SquadWars.com), or head-to-head via modem. In any of these modes, you can choose to fly co-op, team-based, or free-for-all dogfight, with many different missions to choose from. And to add even more bang for the buck, the game includes FRED2, a full-featured editor that you can use to create your own missions and campaigns. With an epic-sized space operaic plot, gorgeous graphics, top-notch space combat action, optional missions and multiple endings, and virtually unlimited replayability, Freespace 2 is a must-have for all armchair space pilots... and a worthy entrant into our Hall of Belated Fame.

The Apocalypse Project

2008-07-15T08:22:38Z

Stormkeeper: /* Homeworld */

{{Template:TAP}}

==General Info==
'''Project Leader:'''
, pecenipicek, shiv_pl 
'''Project Members :'''
*pecenipicek ~ Project leader, Head 3D Modeler
*nubbles526 ~ writer,wiki maintainer
*PyroMX ~ 2D artist, web site designer, advertiser
*Sarafan ~ head writer
*shiv_pl ~ Second in command, main organizer of stuff, FREDer, tabler, partially effect artist
*Grug ~ Effects, occasional table tweaks
*Alkan Rena ~ Concept arist and cutscene drawer
*freespaceking ~ texture artist

==Places Open/Applying==

The Apocalypse Project is looking for the following people with talents to join the project:

* FREDder: Open
* Table Editor: Open
* Storyline Writer: Full
* Modeler: Open
* Texture Map Maker: Open
* Wiki Maintainer: Full
* Sound effects arist: Open
* Music composer: Open
 

'''If you wish to join the project, please contact shiv_pl or pecenipicek.'''

==Content (Demo Version)==

'''Mods included:''' Non Yet 

==Content (Full Version)==

'''Mods included:''' Non Yet 

==Overview==

''(Note: The actual story is still in writing. This paragraph is just a story to be based upon, and the final piece may not match the paragraph''

The Apocalypse project is a FreeSpace mod based on Homeworld. Homeworld is a massivly popular award winning space-sim game. The mod is divided into three sections: Homeworld, Homeworld: Cataclysm and Homeworld 2. Homeworld would act as a "demo" to give the player a feel about the main character (Iifrit Tambuura) and it's surroundings. Cataclysm woudld just be a "expansion" to where Homeworld had left off, and show the struggle of Tamubuura when he and his clan are trying to prepare themselves for the attack on Hiigara. Lastly, Homeworld 2 (or Era 2 for some people) would describe how a group of Kiith of an elite recon unit make it's way into the siege of Hiigara.

==Homeworld==

Kharak. A hostile, desert world, where the only arable land lie in the polar regions. The Kiithid have called it home since time immemorable. Near the end of the Heresy Wars, Kiith Naabal emerged from their hidden polar region, sallying forth to stop the Heresy Wars, and establishing the Time of Reason. During the ToR, advances in biological and chemical sciences revealed a disturbing lack of commonality between the kiith and most Kharakid life. Except for a small variety of bacteria and a single species of small forager, the kiith were aliens to the world.

In 1105, a radar satellite malfunctioned, and scanned the surface of the planet. A strong return where there should have been non revealed to be an ancient city, now known as Khar Toba, built around the skeletal chassis of an advanced vessel. Beneath the surface, in a shielded chamber, lay the remains of the ancient ship's power plant. Attached to it was a small, nondescript module. This small module was revealed to be a solid state hyperspace induction module. With this, the Kiith were ready to take their first steps into the galaxy, but it was not until 1135, did they know how far they would have to go.

At Khar Toba, a team of dedicated archaeologist continued to work on the ancient city under some of the harshest Kharakid conditions. Mevath Sagald, leader of the expedition, single handly found and explored the mythic Observertory Temple of Khar Toba after accidents left her working on her own. There, she found a single black stone, weathered by the elements till its markings were near indistinguishable... the Guidestone. On its surface was etched a simple map of the galaxy, and a single gouged line leading from a point of the rim to one deep in the galactic center. Adjacent to the rim spot was a string of numbers giving Kharak's actual position. At the other end, was a single word, ancient but common to all dialects. Hiigara ... Home.

This single discovery sparked off the largest construction project ever known. The entire planet was devoted to the construction of the Mothership. Part carrier, part survey ship, part factory complex and temporary home for millions of people in cyrogenic sleep. Over a period of 35 years, the Mothership took form within the massive Scaffold, which itself took 20 years to build. Now the Mothership and the Kiith are ready to begin the journey to their Hiigara ... to their Homeworld.

==Homeworld: Cataclysm==

Coming soon...

==Homeworld 2==

Coming soon...

==Related Links==
[http://tap.hard-light.net/| The Apocalypse Website] 
[http://www.hard-light.net/forums/index.php/board,155.0.html| The Forum of The Apocalypse Project]

''This article is currently updated by Nubbles. If you have any concerns or critisism about a few things I wrote above, please feel free to edit the article and make the necessery changes, or PM me through Hard-Light.''

[[Category:Total Conversions]]

The King's Gambit

2008-07-15T05:57:44Z

Stormkeeper: /* Walkthrough */ Corrected minor spelling errors.

{{Mission|next=The Sicilian Defense|previous=Proving Grounds|campaign=Campaign Walkthrough}}

'''ACT 2, MISSION 4'''

'''Fighter squadron: [[64th Raptors]]'''

'''Description: The 64th attempts to cripple the [[NTF]] as they come through the node.'''

----
==Background==
[[Admiral Bosch]] sends his forces on a banzai charge to the [[Knossos]] subspace portal. The 3rd Terran fleet and 11th Vasudan Battle Group attempt to hold him off.

==Walkthrough==

This is also a bombing run mission. You have to destroy as many hostile capital ships as you can. The [[GTB Artemis]] with the primary bank of [[GTW Prometheus S]], and all three banks of [[GTM Cyclops]] is the most ideal for this mission. The Artemis is the most maneuverable [[GTVA]] bomber you can use. It is also the lightest, but you have chance to survive only in the Artemis. A Vasudan [[GVD Typhon]]-class destroyer and several [[GTSG Mjolnir]] cannons are assisting you with their firepower.

Alternately, you can choose a fighter from another wing and let your allies run the bombing missions. With good instructions, the beam turrets, the Typhon and your allied wings can destroy the [[NTF]] ships without difficulty. Hunt down fighters if you choose this path, and be sure to bring [[GTM Harpoon]]s with you.
The first [[NTF]] ship that arrives in the NTD Uhuru ([[GTD Orion]]-class). You have to fire a few Cyclops at it to ensure its destruction. With the Uhuru, [[GTF Hercules]] fighters jump in and they head after the Mjolnir sentry guns. Your fighter assistance can handle them most of the times, but I suggest you move against the fighters after you delivered a few bombs at the Uhuru. Losing the Mjolnir cannons or the Vasudan destroyer can mean as serious loss of firepower as you won't have the firepower to neutralize enemy warships which jump in. So head against the fighters, as well.

Order your squadron to attack the next series of warships which jump in. Since the AI in Freespace are quite forgetting, you would better remind them they are not only there as spectators. Target one of the warships you consider the most serious threats, and hit C, 2, 1, 1. This orders your squadron to attack your target. You have to take down at least 50% of the incoming warships.

Damaging the engines of the warships immediately gains you more time before they jump out. If you manage to disable one of the warships, it won't be able to escape at all. Acquiring quick lock on a moving target with Cyclops requires time, if you practice more, and understand the targeting engine of Freespace, you can gain advantage. Shoot, shoot, shoot, kill, kill, kill. These are the rules.

''KR's Notes :'' Most people can't even kill the Uhuru before it jumps out... Because when it jumps in, it slides at a speed of over 150m/s, reaching its waypoint faster than the other ships. The best way to take down this guy is to target its engines as soon as it jumps in, lob a few cyclops and follow it. The Uhuru's jump in speed is so great that it actually reaches your start point.

"MrMitten's" Notes :" Never have I once had to throw a single glance at the Uhuru; even on insane. Just order everyone to kill it a couple times while command is giving its Uhuru speech. The bombs of your wingmen combined with the Cap-ship-raping power of the Mjolnirs should shoot it out of the sky quite handily. Save your bombs for the other ships.

==Notable ships present==
*GVD Hedetet
*NTD Uhuru
*GTCv York
*NTCv Pax
*NTCv Perseverance
*GTC Warwick
*NTC Liberty
*NTC Undaunted
*GVC Unut
*NTT Inspiration

==New equipment==
*[[GTB Artemis]]
*[[GTW Prometheus S]]

==Confirmed Glitches==
At times, the ship selection will offer the Artemis D.H. Although this seems like a potential advantage, the weapon selection screen also does '''not''' offer bombs of any type. This will be the first major problem you will encounter, other minor problems you should have noticed by now: odd readouts for secondary weapons, no simulated voice in techroom. These problems are caused by having a player file which was used with FS2_Open 3.7 or older, and having upgraded to FS2_Open 3.9 or newer. Unfortunately, the only known fix is to either downgrade your FS_Open version or create a new pilot (yes, sadly, losing all progress). Of course, you could also attempt to complete the missions using the Rockeyes which replace the unavailable Cyclopses. Or you could switch to available Hornets and EMPs. Otherwise, you are pretty much sunk.

Please also note that retail has no reproducable problems of this kind.

[[Category:Main Freespace 2 Campaign]]

Battle of the Wilderness

2008-07-15T05:49:44Z

Stormkeeper: Corrected broken links, misspelled "Charybdis". My bad.

{|- cellpadding="8" style="background:#000000;" align="center"
| [[Feint! Parry! Riposte!|Previous Mission]] or [[...But Hate the Traitor|SOC Loop 1]]
| [[Campaign Walkthrough]]
| [[A Game of TAG|Next Mission]]
|-
|}

ACT 2, MISSION 1

Fighter squadron: [[134th Barracudas]] 
Description: The 134th protects a convoy carrying a prototype version of the [[GTM TAG-A]] missile and tests the functionality of the [[GTA Charybdis]] in the nebula.

----
==Background==
As a CEU or combat evaluation unit, the 134th guards a convoy of expimental [[GTM TAG-A|TAG-A]] (Target Acquisition and Guidance) missiles while the [[GTA Charybdis|Lucidity]] provides [[AWACS]].

==Walkthrough==

This is a long and boring mission. The swirling gases of the nebula make combat difficult, so pick your shots. Don't be afraid to use your secondaries here; I suggest a double bank of [[GTM Harpoon]]s to supplement your primaries.
 
The convoy you are tasked to defend consists of two freighters and their cargo. The freighters must survive in order to complete the mission. Due to a 'bug', you can allow the cargo to be lost, as the game won't recognise that it was lost. It is unlikely that the cargo will be destroyed since the [[Shivans]] target the freighter directly. The [[Shivans]] will use fighters and a few bombers to attack the convoy. As always prioritise bombs and bombers before fighters.
 
The SC Malor, an [[SC Cain]] class cruiser will also attack the convoy. The Cain class is the weakest of all Shivan cruisers, so you won't find it difficult to destroy. However, you should destroy the main beam cannon below its nose to render her powerless against the freighters. You can also try to destroy the anti-fighter beam on the lower aft part of the ship to give you and your wingmen an easier time of taking her out. Once the two Alliance ships have reached the [[GTCv Deimos|GTCv Warspite]], the mission is complete and you may return to base.
 
If things get too hot, a wing of Medusa bombers are at your disposal. Call them in if the freighters are in danger of being destroyed by the Malor, which is unlikely if you act fast enough.

==Notable ships present==
*[[GTCv Deimos|GTCv Warspite]]
*[[SC Cain|SC Malor]]
*[[GTA Charybdis|GTA Lucidity]]
==New equipment==
*[[GTM TAG-A]]

[[Category:Main Freespace 2 Campaign]]

Battle of the Wilderness

2008-07-15T05:47:41Z

Stormkeeper: Correct grammar and spelling errors, modified walkthrough slightly.

{|- cellpadding="8" style="background:#000000;" align="center"
| [[Feint! Parry! Riposte!|Previous Mission]] or [[...But Hate the Traitor|SOC Loop 1]]
| [[Campaign Walkthrough]]
| [[A Game of TAG|Next Mission]]
|-
|}

ACT 2, MISSION 1

Fighter squadron: [[134th Barracudas]] 
Description: The 134th protects a convoy carrying a prototype version of the [[GTM TAG-A]] missile and tests the functionality of the [[GTA Charybodis]] in the nebula.

----
==Background==
As a CEU or combat evaluation unit, the 134th guards a convoy of expimental [[GTM TAG-A|TAG-A]] (Target Acquisition and Guidance) missiles while the [[GTA Charybodis|Lucidity]] provides [[AWACS]].

==Walkthrough==

This is a long and boring mission. The swirling gases of the nebula make combat difficult, so pick your shots. Don't be afraid to use your secondaries here; I suggest a double bank of [[GTM Harpoon]]s to supplement your primaries.
 
The convoy you are tasked to defend consists of two freighters and their cargo. The freighters must survive in order to complete the mission. Due to a 'bug', you can allow the cargo to be lost, as the game won't recognise that it was lost. It is unlikely that the cargo will be destroyed since the [[Shivans]] target the freighter directly. The [[Shivans]] will use fighters and a few bombers to attack the convoy. As always prioritise bombs and bombers before fighters.
 
The SC Malor, an [[SC Cain]] class cruiser will also attack the convoy. The Cain class is the weakest of all Shivan cruisers, so you won't find it difficult to destroy. However, you should destroy the main beam cannon below its nose to render her powerless against the freighters. You can also try to destroy the anti-fighter beam on the lower aft part of the ship to give you and your wingmen an easier time of taking her out. Once the two Alliance ships have reached the [[GTCv Deimos|GTCv Warspite]], the mission is complete and you may return to base.
 
If things get too hot, a wing of Medusa bombers are at your disposal. Call them in if the freighters are in danger of being destroyed by the Malor, which is unlikely if you act fast enough.

==Notable ships present==
*[[GTCv Deimos|GTCv Warspite]]
*[[SC Cain|SC Malor]]
*[[GTA Charybodis|GTA Lucidity]]
==New equipment==
*[[GTM TAG-A]]

[[Category:Main Freespace 2 Campaign]]

The Apocalypse Project

2008-07-14T01:50:30Z

Stormkeeper: /* Homeworld */

{{Template:TAP}}

==General Info==
'''Project Leader:'''
, pecenipicek, shiv_pl 
'''Project Members :'''
*pecenipicek ~ Project leader, Head 3D Modeler
*nubbles526 ~ writer,wiki maintainer
*PyroMX ~ 2D artist, web site designer, advertiser
*Sarafan ~ head writer
*shiv_pl ~ Second in command, main organizer of stuff, FREDer, tabler, partially effect artist
*Grug ~ Effects, occasional table tweaks
*Alkan Rena ~ Concept arist and cutscene drawer
*freespaceking ~ texture artist

==Places Open/Applying==

The Apocalypse Project is looking for the following people with talents to join the project:

* FREDder: Open
* Table Editor: Open
* Storyline Writer: Full
* Modeler: Open
* Texture Map Maker: Open
* Wiki Maintainer: Full
* Sound effects arist: Open
* Music composer: Open
 

'''If you wish to join the project, please contact shiv_pl or pecenipicek.'''

==Content (Demo Version)==

'''Mods included:''' Non Yet 

==Content (Full Version)==

'''Mods included:''' Non Yet 

==Overview==

''(Note: The actual story is still in writing. This paragraph is just a story to be based upon, and the final piece may not match the paragraph''

The Apocalypse project is a FreeSpace mod based on Homeworld. Homeworld is a massivly popular award winning space-sim game. The mod is divided into three sections: Homeworld, Homeworld: Cataclysm and Homeworld 2. Homeworld would act as a "demo" to give the player a feel about the main character (Iifrit Tambuura) and it's surroundings. Cataclysm woudld just be a "expansion" to where Homeworld had left off, and show the struggle of Tamubuura when he and his clan are trying to prepare themselves for the attack on Hiigara. Lastly, Homeworld 2 (or Era 2 for some people) would describe how a group of Kiith of an elite recon unit make it's way into the siege of Hiigara.

==Homeworld==

Kharak. A hostile, desert world, where the only arable land lie in the polar regions. The Kiithid have called it home since time immemorable. Near the end of the Heresy Wars, Kiith Naabal emerged from their hidden polar region, sallying forth to stop the Heresy Wars, and establishing the Time of Reason. During the ToR, advances in biological and chemical sciences revealed a disturbing lack of commonality between the kiith and most Kharakid life. Except for a small variety of bacteria and a single species of small forager, the kiith were aliens to the world.

In 1105, a radar satellite malfunctioned, and scanned the surface of the planet. A strong return where there should have been non revealed to be an ancient city, now known as Khar Toba, built around the skeletal chassis of an advanced vessel. Beneath the surface, in a shielded chamber, lay the remains of the ancient ship's power plant. Attached to it was a small, nondescript module. This small module was revealed to be a solid state hyperspace induction module. With this, the Kiith were ready to take their first steps into the galaxy, but it was not until 1135, did they know how far they would have to go.

At Khar Toba, a team of dedicated archaeologist continued to work on the ancient city under some of the harshest Kharakid conditions. Mevath Sagald, leader of the expedition, found and explored the mythic Observertory Temple of Khar Toba. There, she found a single black stone. It was the Guidestone. On its surface was etched a simple map of the galaxy, and a single gouged line leading from a point of the rim to one deep in the galactic center. Adjacent to the rim spot was a string of numbers giving Kharak's actual position. At the other end, was a single word, ancient but common to all dialects. Hiigara ... Home.

This single discovery sparked off the largest construction project ever known. The entire planet was devoted to the construction of the Mothership. Part carrier, part survey ship, part factory complex and temporary home for millions of people in cyrogenic sleep. Over a period of 55 years, the Mothership took form. Now the Mothership is ready to begin the journey to Hiigara ... to home.

==Homeworld: Cataclysm==

Coming soon...

==Homeworld 2==

Coming soon...

==Related Links==
[http://tap.hard-light.net/| The Apocalypse Website] 
[http://www.hard-light.net/forums/index.php/board,155.0.html| The Forum of The Apocalypse Project]

''This article is currently updated by Nubbles. If you have any concerns or critisism about a few things I wrote above, please feel free to edit the article and make the necessery changes, or PM me through Hard-Light.''

[[Category:Total Conversions]]

Playing Judas

2008-07-14T01:08:37Z

Stormkeeper: /* Notes */

{|- cellpadding="8" style="background:#000000;" align="center"
| [[Enter the Dragon|Previous Mission]]
| [[Freespace 1 Campaign Walkthroughs#Main Freespace 1 Campaign|Campaign Walkthrough]]
| [[Evangelist|Next Mission]]
|-
|}

ACT 2 MISSION 8

Fighter squadron: 
Description:

----
==Background==
:''In this mission we will be using the captured Shivan Dragon-class fighter on a scouting mission in the Deneb system.''
:''The Shivans seem to be bringing in a large number of vessels into the Deneb system through the Vega Jump Node. We believe this is in preparation for a preliminary assault on Vasuda Prime.''
:''Because the Shivans have tight control over the Vega-Deneb jump node, we cannot send in a Terran scout. By flying the Shivan Dragon, we believe you will be able to slip in undetected.''
:''There are four Shivan fighters in the area, maintaining tight patrol. If you come into close contact with these fighters, they will certainly scan your ship, detect your presence, and open fire. Avoid contact with any of the Arjuna fighters.''
:''Arjuna seems to be maintaining consistent patterns in their patrol.''
:''On arrival, observe their flight pattern and plan your course to avoid contact.''
:''In the event that you are engaged by Arjuna wing, return to base immediately.''
:''Your primary objective is to conduct a close scan of all ships that pass through the Vega-Deneb Jump Node. This includes warships, freighters, and transports. Try to determine the contents of any cargo in the area, as well.''
:''We have reason to believe that a Shivan Demon-class Destroyer, the Eva, will be passing through the area. If it does, it is imperative that you scan it. Remember that your fighter is only partially functional, and it's flight systems will behave unpredictably. Be careful. Command out.''

==Walkthrough==
Don't shoot anything. Fly toward cargo 1 and 2. Scan them. Scan the Kali freighters that have by now warped in. Next quickly scan cargo 3 and 4. Bang! Bonus objective. More freighters. Scan them. A brief pause. Monitor Arjuna 1-3 to make sure you are far away. Last group of freighters. Scan them. 
More pause. Repeat monitoring Arjuna. Warp drives die. Eva jumps in. Scan it. Pause. Repeat monitoring Arjuna. Lucifer jumps in. 
Scan it. Put your shield level up. Scroll through the Lucifer's subsystems until you see Fighterbay 1. Fly by it. Don't go in it. Rama will detect you. Fly around in random directions or attack the fighters until your jump drives have come back online. Jump out fast.
==Notes==
It is possible to play this mission "broken", i.e. eliminate Arjuna wing at the beginning and then play from there, but given how weak the Dragon you fly is, this is not recommended.

==Notable ships present==
*[[SD Demon|SD Eva]]
*[[SD Lucifer|SD Lucifer]]
[[Category:Main Freespace 1 Campaign]]

Modular Tables

2008-07-13T12:15:52Z

Stormkeeper: /* Important Notes. Loading Order */

==Introduction==
Modular tables are SCP addition to the standard FreeSpace table system. Each tabular table (.tbm extension) adds or modify data from its related base table (.tbl extension). So there's no more need to edit the 'parent' table.

The base table each modular table modifies depends on the ending three letters of its name. See [[Modular Tables#Supported Modular Tables|the list of supported modular tables]] below.

==Important Notes. Loading Order==
* Modular table files should use the 'parent table' sections. They should also keep their entry order.
* Completely new entries and also complete rewrites of entries in parent table file are always possible.
* '''Loading order:'''
** The base table (.tbl) is loaded first despite its location priority, (see [[Command-Line_Reference#-mod|-mod flag help]] for more info about priority places). Of course, if there are several versions of the same base table in several vps or /data/tables folders, only the highest priority one will be loaded.
** Then, ALL its related tbms are loaded, even if they are in a lower priority place than the base tbl table. I.e, '''tbms are always applied'''. If there are several versions of the same file you can imagine what happens.
** When they are loaded, tbms start being applied in reverse priority order; ie, tbms are applied from the lowest priority place to the highest priority place.
** The former rule makes that, if there are conflictive entries in several tables, '''the highest priority ones will override the rest''' because they will be the last applied changes. '''EXTREMELY IMPORTANT NOTE:''' Because of a bug, '''fs_open versions till 3.6.9. (included)''' apply tbms in direct priority order, from the highest priority to the lowest one. In this way, '''the lowest priority entries override the rest'''. As example, this issue makes impossible overriding mediavps tbm settings from any tbm inside a main mod which uses this art enhancement as a secondary mod. The only way you have is overriding the whole table as explained below. '''WARNING: Never use conflictive tbms inside the same priority location''', (vp or /data/tables folder). For example, do not put aaa-shp.tbm and bbb-shp.tbm inside the same vp if they have conflictive entries. Due technical design there is no easy way to know their loading order. For the final user, finally applied entries will seem randomly selected. Alphabetical sorting is not applied here. Only vps are alphabetically ordered when loaded; individual files, (like tbms), aren't, it doesn't matter if they are obtained either from hard disk folders or from inside a vp archive. Nevertheless, this is a pretty strange mod design: why should you put conflictive versions of any class of modular table in the same location?, just edit and merge them deleting undesired entries. But this warning can be also understood in the following way: Be careful '''if you split one tbm in several ones''' due to any reason, (tracking changes, management of different groups of parameters or whatever), '''always check that they all are fully complementary with no conflictive entries'''. 
** Derived from priority and tbm handling, the only two ways to override the settings of AnExistingTable-xxx.tbm are:
*** Adding another AnExistingTable-xxx.tbm in a higher priority place so it gets loaded instead of the original version.
*** Overriding every single AnExistingTable-xxx.tbm entry, using one or several other -xxx.tbm tables located in higher priority places.

==eXtendable Modular Tables==
In addition, some modular tables are XMTs (or eXtentable Modular Tables). They offer capability to add new partial entries or make partial editing to each entry. Within XMT tbms:
* All fields are optional. But toplevel entries, of course, because you ''do need'' to specify which item you want to modify ;-) .
* Toplevel entries can replace part of other existing toplevel entries. Only changed parameters should be specified.
* Addition of the '''+nocreate''' parameter. This parameter should be entered right after entry name and prevents possible creation of partially undefined entry. For example, if the parent table file lacked the entry that was included to the as a partial entry to the modular table file then the creation of partially undefined entry is possible which could cause problems with the game.
**Example:

$Name: @Subach HL-7
+nocreate

==Supported Modular Tables==
The list of supported tbms is:

*[[ai_profiles.tbl]] can be extended with '''xxx-aip.tbm''' (XMT)
*[[armor.tbl]] can be extended with '''xxx-amr.tbm''' (non-XMT)
*[[hud_gauges.tbl]] can be extended with '''xxx-hdg.tbm''' (non-XMT)
*[[mflash.tbl]] can be extended with '''xxx-mfl.tbm''' (non-XMT)
*[[music.tbl]] can be extended with '''xxx-mus.tbm''' (non-XMT)
*[[objecttypes.tbl]] can be extended with '''xxx-obt.tbm''' (XMT)
*[[scripting.tbl]] can be extended with '''xxx-sct.tbm'''
*[[ships.tbl]] can be extended with '''xxx-shp.tbm''' (XMT)
*[[species_defs.tbl]] can be extended with '''xxx-sdf.tbm''' (XMT)
*[[stars.tbl]] can be extended with '''xxx-str.tbm''' (non-XMT)
*[[strings.tbl]] can be extended with '''xxx-lcl.tbm''' (???)
*[[weapons.tbl]] can be extended with '''xxx-wep.tbm''' (XMT)
*[[weapon_expl.tbl]] can be extended with '''xxx-wxp.tbm''' (non-XMT)

Other special modular tables are:

*[[fireball.tbl]] can be '''''edited''''' with '''xxx-fbl.tbm''' file ([[fireball.tbl#Modular Fireball Table|special]])

==Sample - Alpha-wep.tbm==
*Changes the speed of the ''Subach HL-7'' and also adds a faint grey trail to it.
*To create it make a text file using a text editor and save the file as '''''Alpha-wep.tbm''''' with the following contents to the proper folder (.../data/tables).

#Primary Weapons
$Name: @Subach HL-7
+nocreate
$Velocity: 650.0
$Trail:
+Start Width: 0.4
+End Width: 0.0
+Start Alpha: 0.35
+End Alpha: 0.0
+Max Life: 0.2
+Bitmap: Contrail
#End

[[Category:Tables]]

The Apocalypse Project

2008-07-13T11:16:23Z

Stormkeeper: Corrected a few spelling/grammar errors.

{{Template:TAP}}

==General Info==
'''Project Leader:'''
, pecenipicek, shiv_pl 
'''Project Members :'''
*pecenipicek ~ Project leader, Head 3D Modeler
*nubbles526 ~ writer,wiki maintainer
*PyroMX ~ 2D artist, web site designer, advertiser
*Sarafan ~ head writer
*shiv_pl ~ Second in command, main organizer of stuff, FREDer, tabler, partially effect artist
*Grug ~ Effects, occasional table tweaks
*Alkan Rena ~ Concept arist and cutscene drawer
*freespaceking ~ texture artist

==Places Open/Applying==

The Apocalypse Project is looking for the following people with talents to join the project:

* FREDder: Open
* Table Editor: Open
* Storyline Writer: Full
* Modeler: Open
* Texture Map Maker: Open
* Wiki Maintainer: Full
* Sound effects arist: Open
* Music composer: Open
 

'''If you wish to join the project, please contact shiv_pl or pecenipicek.'''

==Content (Demo Version)==

'''Mods included:''' Non Yet 

==Content (Full Version)==

'''Mods included:''' Non Yet 

==Overview==

''(Note: The actual story is still in writing. This paragraph is just a story to be based upon, and the final piece may not match the paragraph''

The Apocalypse project is a FreeSpace mod based on Homeworld. Homeworld is a massivly popular award winning space-sim game. The mod is divided into three sections: Homeworld, Homeworld: Cataclysm and Homeworld 2. Homeworld would act as a "demo" to give the player a feel about the main character (Iifrit Tambuura) and it's surroundings. Cataclysm woudld just be a "expansion" to where Homeworld had left off, and show the struggle of Tamubuura when he and his clan are trying to prepare themselves for the attack on Hiigara. Lastly, Homeworld 2 (or Era 2 for some people) would describe how a group of Kiith of an elite recon unit make it's way into the siege of Hiigara.

==Homeworld==

Kharak, a planet that is reaching the end of its abilty to support life. The inhabitants, who named themselves Kiiths, are finding it harder to find arable land and to shelter themselves. However, one day, a few archeologists have uncovered the ruins of an anicient city. What they standing in front of was the home of their ancestors. The archeologists also found a stone with some writing on it. When the stone was taken back for examination, it has revealed that the Kiith are actually not from Kharak.
The Kiith were excited to learn this information, and construction on a ship has begun. The Kiith had in mind that it should be big, powerful and fast. Their answer was the Mothership. The Mothership is able to carry up to 10,000 Kiithid into deep space. However, such big ship also need sacrifices. Three generations of Kiith witnessed the construction of the Mothersip. However, once this pride has been completed, they are finally able to return to where they came from...their Homeworld.

==Homeworld: Cataclysm==

Coming soon...

==Homeworld 2==

Coming soon...

==Related Links==
[http://tap.hard-light.net/| The Apocalypse Website] 
[http://www.hard-light.net/forums/index.php/board,155.0.html| The Forum of The Apocalypse Project]

''This article is currently updated by Nubbles. If you have any concerns or critisism about a few things I wrote above, please feel free to edit the article and make the necessery changes, or PM me through Hard-Light.''

[[Category:Total Conversions]]

Post-Capella-era campaign ideas

2008-07-13T11:07:19Z

Stormkeeper: /* Flying Shotgun with the Shivan Defence Force */

These are concept campaigns for the Reconstruction era and, due to stupid error, for everything after: Add yours at the bottom of the list.

==Flying Shotgun with the Shivan Defence Force==
I haven't seen any campaign you play sa the Shivans on, and it would also shed light on the motives of the Shivans.
It might be a big mod because I'm sure the Shivans have all sorts of weapons, ships, etc that we haven't seen, and a modder would need to seriously flesh out the Shvan arsenal (would you take a shivan loadout screen seriously if it had Shivan Mega Laser on it?).

''Lightspeed's Shivan weapons pack would cover that problem I think. Alternatively one might want to try and restart the Hidden Terror campaign currently languishing on Sectorgame.-ngtm1r''

''Flaming Sword just released his Shivan mod. Its still a work in progress though, but it looks quite promising. - Storm''

==Reconquest of Earth==
Description: Exploration parties have found a new way to Sol (through the Shivan nebula?). Unfortunately, the Terrans there are not willing to become part of the GTVA (reason to be established in campaign). 
The GTVA and Terranovan Confederation (or whatever else you want to call it) duke it out (possible multiplayer head-to-head campaign). Possibly, if the route is through part of the Shivan Nebula, have a three-power war between the GTVA, TNC, and Shivans. 

Modding: Do not make this campaign unless you like modding or you don't care about plot holes. To avoid plot holes, you need to either plagarise a lot of FS1 craft & weapons or do a lot of modding. 
Neccessary: 
Make an Orion with Shivan beam weapons (they got them by REing the Lucifer debris) (Terran beam weapons weren't invented until after Sol was cut off, so GTBWs on a TNC Orion would be a plot hole); if it gives them a serious advantage, make weaker versions, because leaving the Confederation's Orions without beams would give the GTVA a major advantage. 
Either Resurrect the Athena and Valkyrie at a minimum or make new fighters solely for Confederation Pilots; make the selection good enough for until the Confeds RE GTVA fighters. 
Do the same for a decent selection of guns and missiles (beam weapons can be copied from the Shivans). 
Optional: 
Make a new race called the Terranovans (Latin, literal: New Earth; figurative: New Chance). 
Give the Terranovans some sort of signature technology, eg a fighter with AWACS technology or support-ship capability, or give them some Shivan technology (eg better drives). 
Balancing: 
If you have a three-power war in the Shivan Nebula and the Shivans overpower the Confeds easily on easy or very easy, either ask yourself whether you need the Shivans to have as much firepower, or give the Confederation a shield-penetrator (my conception of the campaign was that the Shivans still attacked Earth evenn after the Lucifer was destroyed and the Terranovans are angry no effort was seemingly made to protect them; they developed the shield-penetrator as an anti-Shivan weapon); if this doesn't help, rethink the mission(s) in question; if the GTVA is almost as badly outmatched, have them RE the penetrator. 

=="what happened to bosch" campaigns?==

I think it would be interesting to expand on the bosch mystery: I know only of one campaign: technical superiority (unfortunately aborted) who tried to cover the problem, and it left me longing for more. Will bosch return? what did he find out about the shivans? will he be able to warn us?

''There's more than one campaign about Bosch's fate. Gai Daigoji's Utopia and Deep Blood talked about the return of Bosch, if I remember well.'' - [[User:Mobius|Mobius]]

Talk:Playing Judas

2008-07-13T11:04:25Z

Stormkeeper: Undo revision 16928 by Stormkeeper (Talk)

The notes suggest to open fire at the beginning of the mission. Does that make the mission fail immediately? - Mobius

*Well, if you fire, the Arjunas would come and kill you. But it does not make you fail the mission.[[User:Nubbles|Nubbles]] 13:50, 10 February 2008 (CST)

Then this should be mentioned as superb example of bad FREDding. - Mobius

*Dude if you open fire it is LIKE failing because the Eva, the Lucifer, Rama, Arjuna, Vishnu, Durga, Savitri, Jugganath, Parvati,Pochi, Tama, James, Steve Ballmer, Chuck Norris AND Derek Smart start attacking you. [[User:Snail|Snail]] 16:38, 15 February 2008 (CST)
Nooooo....!! Not mr Smart!!! Nooo...!! (By the by; the mission really is a text book example of lousy FREDding.) [[User:Selectah|Selectah]] 08:03, 13 March 2008 (CST)
I got fed up and just failed 5 times in a row to skip it.

Talk:Playing Judas

2008-07-13T11:04:07Z

Stormkeeper:

Talk:Playing Judas

2008-07-13T11:03:38Z

Stormkeeper:

Playing Judas

2008-07-13T11:02:36Z

Stormkeeper: /* Notable ships present */

{|- cellpadding="8" style="background:#000000;" align="center"
| [[Enter the Dragon|Previous Mission]]
| [[Freespace 1 Campaign Walkthroughs#Main Freespace 1 Campaign|Campaign Walkthrough]]
| [[Evangelist|Next Mission]]
|-
|}

ACT 2 MISSION 8

Fighter squadron: 
Description:

----
==Background==
:''In this mission we will be using the captured Shivan Dragon-class fighter on a scouting mission in the Deneb system.''
:''The Shivans seem to be bringing in a large number of vessels into the Deneb system through the Vega Jump Node. We believe this is in preparation for a preliminary assault on Vasuda Prime.''
:''Because the Shivans have tight control over the Vega-Deneb jump node, we cannot send in a Terran scout. By flying the Shivan Dragon, we believe you will be able to slip in undetected.''
:''There are four Shivan fighters in the area, maintaining tight patrol. If you come into close contact with these fighters, they will certainly scan your ship, detect your presence, and open fire. Avoid contact with any of the Arjuna fighters.''
:''Arjuna seems to be maintaining consistent patterns in their patrol.''
:''On arrival, observe their flight pattern and plan your course to avoid contact.''
:''In the event that you are engaged by Arjuna wing, return to base immediately.''
:''Your primary objective is to conduct a close scan of all ships that pass through the Vega-Deneb Jump Node. This includes warships, freighters, and transports. Try to determine the contents of any cargo in the area, as well.''
:''We have reason to believe that a Shivan Demon-class Destroyer, the Eva, will be passing through the area. If it does, it is imperative that you scan it. Remember that your fighter is only partially functional, and it's flight systems will behave unpredictably. Be careful. Command out.''

==Walkthrough==
Don't shoot anything. Fly toward cargo 1 and 2. Scan them. Scan the Kali freighters that have by now warped in. Next quickly scan cargo 3 and 4. Bang! Bonus objective. More freighters. Scan them. A brief pause. Monitor Arjuna 1-3 to make sure you are far away. Last group of freighters. Scan them. 
More pause. Repeat monitoring Arjuna. Warp drives die. Eva jumps in. Scan it. Pause. Repeat monitoring Arjuna. Lucifer jumps in. 
Scan it. Put your shield level up. Scroll through the Lucifer's subsystems until you see Fighterbay 1. Fly by it. Don't go in it. Rama will detect you. Fly around in random directions or attack the fighters until your jump drives have come back online. Jump out fast.
==Notes==
Arjuna wing is not ''that'' big a threat, really. If you want to make the mission a little bit more interesting -- in its' intended form it's really, really boring -- fire your primaries or secondaries upon entry. Arjuna will home in on you immediately. Keep following directives and eliminate Arjuna whilst doing so. They're not really that hard to dispose of. With them gone, the rest of the mission can easily be played at X2 speed. 

Please be adviced that this mission is dung. It is a complete mystery why it was even released in the first place. The mission doesn't require ''any'' skill, nor does it provide ''any'' entertainment. When a complete novice -- one who hasn't even ''played'' FreeSpace, ever -- FREDs for the first time, the results are better in magnitude than this substandard piece of manure. It has been long suspected that this mission was left in by mistake.

==Notable ships present==
*[[SD Demon|SD Eva]]
*[[SD Lucifer|SD Lucifer]]
[[Category:Main Freespace 1 Campaign]]

ULTRA Anti-Fighter Beam

2008-07-13T10:58:21Z

Stormkeeper: /* Veteran Comments */

'''ULTRA Anti-Fighter Beam''' is beam used in the [[Portal:Freespace 2|Freespace 2]] to defend capital ships against fighters

{{FS12_Weapons}}
==Description==
Anti-fighter beam weapon

==Performance==
===Statistics===
{{Beam|4 000|2.2|2.5|Anti fighter|3|165|413 (total)}}

==Notes==

===Veteran Comments===
{{Comment|'''Very''' deadly AAA beam, more effective then the [[AAAf]] or [[AAAh]], not usually used, and never by default. Powerful enough to destroy most fighters in one pulse. In the main FS2 campaign, it is used by the [[Freespace_2_Terran_Ship_Database#GTCv_Warspite|GTCv Warspite]] in "A Game of TAG" to balance the player's lack of any proper missiles.

Also used by the [[Colossus]] in [[High Noon]].

Unlike other beam weapons, this appears to be the only one that does not need to recharge in between shots. Once, I replaced all the [[AAAf]]s on the Colossus with this in a user-made level; I could hear them firing over and over again like nobody's business.

Replaced all the anti-fighter beams on an [[Aeolus]] with this baby and no fighter got within 2 klicks of it. Bottom line ? Use sparingly in your own campaigns. This weapon more or less means death for most if not all fighters and boombers.}}

[[Category:Weapon]]

Argonautica

2008-07-13T10:45:45Z

Stormkeeper: /* Notable ships present */ Fixed broken links.

{|- cellpadding="8" style="background:#000000;" align="center"
| [[Straight, No Chaser|Previous Mission]]
| [[Campaign Walkthrough]]
| [[Exodus (FS2)|Next Mission]] or [[As Lightning Fall|SOC Loop 2]]
|-
|}

'''ACT 3, MISSION 5'''

'''Fighter squadron:'''

'''Description:'''
----
==Background==
While on the run from the Sathanas, the Aquitaine is disabled by a Shivan warship, just shy of the Gamma Draconis node in the nebula. Fighters are scrambled to defend the destroyer from further Shivan attack while repair teams and components are delivered.

==Walkthrough==
This is a fairly standard nebula bomber-intercept mission. Just make sure you prioritize your targets appropriately and don't get stuck on the wrong side of the Aquitaine. The ship is two kilometers long, so if you are racing from one side to the other, without completely clearing either, you are wasting precious time that could be spent wasting bombers.

If you clear the area of bombers, even for just a few moments, pull alongside the SCv Abaddon. Even though you can do little more than grind through its turrets, maintaining proximity to the Shivan corvette will allow the Aquitaine to bombard it.

==Notable ships present==

*[[GTD Aquitaine|GTD ''Aquitaine'']]
*[[SCv Moloch|SCv ''Abaddon'']]
*[[GTT Argo|GTT ''Argo'']]
*[[GTC Aeolus|GTC ''Agrippa'']]

==Name origin==
''Argonautica'' is an epic poem that describes the events of a ship named ''Argo''. ''Argo'' was sent on a mission to retrieve a sacred object called the Golden Fleece.

[[Category:Main Freespace 2 Campaign]]

Straight, No Chaser

2008-07-13T10:43:22Z

Stormkeeper: Corrected a few errors I missed previously.

{{Mission|next=Argonautica|previous=Return to Babel|campaign=Campaign Walkthrough}}

'''ACT 3, MISSION 4'''

'''Fighter squadron:''' 203rd Scorpians

'''Description:''' Your squadron has been dispatched into the nebula to find Admiral Bosch.

----
==Background==
After the transport carrying Admiral Bosch escaped, your squadron is sent to look for it.

==Walkthrough==
Recommended load out: [[GVF Serapis]], 1 [[GTW Maxim]], 1 [[GTW Prometheus S]], 1 bank of [[GTM Tornado]] and 1 bank of [[GTM Harpoon]]

At the beginning, you will not see any hostiles. Keep flying forward, and engage the enemy fighters you encounter. Command and wingmen will talk, and then someone mentions he saw another Knossos portal. Your new objective is to clear the area, and Command annouces that there was no Azarel. Soon, a Cain-class cruiser, Sephiroth will jump in. Using your Maxims and Tornados, you should be able to take the Sephiroth fast, as well as the Dahaka. Soon, the Psamtik will jump in, 9000 meters from the Knossos. Order your wingmen to guard the Psamtik; head to the Psamtik yourself. Shivan fighters will jump in; destroy them. After you have destroyed the Shivans, a Sathanas will jump in and immediatly destroy the Psamtik. Jump out once you Command tells you to.

==Notable ships present==
[[SC Rakshasa|SC Dahaka]] 
[[GVD Hatshepsut|GVD Psamtik]] 
[[SC Cain|SC Sephiroth]] 
[[SJ Sathanas]]
[[Category:Main Freespace 2 Campaign]]

Straight, No Chaser

2008-07-13T10:41:42Z

Stormkeeper: Corrected grammar errors, re structured walkthrough

{{Mission|next=Argonautica|previous=Return to Babel|campaign=Campaign Walkthrough}}

'''ACT 3, MISSION 4'''

'''Fighter squadron:''' 203rd Scorpians

'''Description:''' Your team has been sent into the Nebalae to find the Azarel transport.

----
==Background==
After the transport carrying Admiral Bosch escaped, your team is sent to look for it.

==Walkthrough==
Recommended load out: [[GVF Serapis]], 1 [[GTW Maxim]], 1 [[GTW Prometheus S]], 1 bank of [[GTM Tornado]] and 1 bank of [[GTM Harpoon]]

At the beginning, you will not see any hostiles. Keep flying forward, and engage the enemy fighters you encounter. Command and wingmen will talk, and then someone mentions he saw another Knossos portal. Your new objective is to clear the area, and Command annouces that there was no Azarel. Soon, a Cain-class cruiser, Sephiroth will jump in. Using your Maxims and Tornados, you should be able to take the Sephiroth fast, as well as the Dahaka. Soon, the Psamtik will jump in, 9000 meters from the Knossos. Order your wingmen to guard the Psamtik; head to the Psamtik yourself. Shivan fighters will jump in; destroy them. After you have destroyed the Shivans, a Sathanas will jump in and immediatly destroy the Psamtik. Jump out once you Command tells you to.

==Notable ships present==
[[SC Rakshasa|SC Dahaka]] 
[[GVD Hatshepsut|GVD Psamtik]] 
[[SC Cain|SC Sephiroth]] 
[[SJ Sathanas]]
[[Category:Main Freespace 2 Campaign]]

The Romans Blunder

2008-07-10T16:32:16Z

Stormkeeper: /* Walkthrough */ Corrected spelling Imporvious -> Impervious

{{Mission|next=A Lion at the Door|previous=The Place of Chariots|campaign=Campaign Walkthrough}}

'''ACT 1, MISSION 3'''

'''Fighter squadron:''' [[53rd Hammerheads]]'''
'''Description:''' You have been ordered to intercept the Iceni.

----
==Background==
The 53rd is scrambled to intercept the [[NTF Iceni|Iceni]], before it reaches Sirius, but somone high up made a mistake... if it was a mistake.

==Walkthrough==

This is a more difficult mission. You seem to have no chance of catching the [[NTF Iceni]], and it leaves the area. After a small conversation between the pilots and Command, two enemy freighters jump in with cargo, who are escorted by some fighters. Prioritize the fighters. Once they are gone, destroy the freighters. Do not splurge much effort at the containers, they are always destroyed by the shockwave of the explosion of the freighter carrying it.

After the freighters and the fighters are down, two [[NTF]] cruisers (NTC Glorious, NTC Impervious) jump in and make your day difficult. They have fighter assistance as well. Try to lure them away by pulling back at the time they begin approaching on you. Without the assistance of the cruisers, they do not stand much long against you and your wingmen. Attack the cruisers after the fighters. The Glorious is the weaker one, target the anti-fighter beam(s) on it, and attack it with the [[GTM Tempest]]s. Fire at will with your rockets to destroy the cruiser.

The Impervious is tougher ([[GTC Leviathan]]-class), the [[GVD Psamtik]] jumps in and will destroy it on her own. After these cruisers have been destroyed, you can leave the area. The mission is more difficult to survive than completing its mission goals. Disarm the cruisers of their anti-fighter beam turrets first.

==Tips==

The Psamtik won't arrive until you take out the cruisers' fighter cover, so make sure you do that first. Despite what command says, the cruiser's anti-fighter beam cannons will not fire at you.

As usual, your teammate's AI is lacking. it may be difficult to keep them alive in this mission.

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

[[GVD Psamtik]]

==Notable quote==

This mission is quite well known for the opening dialogue in the mission.

Command: Engage full burners and intercept the Iceni. They are two kilometers from the Sirius jump node.

Alpha 2: Command, we're five clicks from that corvette! Those coordinates you gave us were bogus! We don't stand a chance of catching that ship!

Command: You have your orders, pilot.

Alpha2: Command, where's the blockade? Why isn't the Alliance guarding this node?

Command: Our line of defense has been reprioritized for engagements elsewhere in the system.

Iceni Jumps
Enemy Leader: I regret your efforts to intercept us have failed, pilots. You would be well advised to question the wisdom of your leaders. Helm, engage subspace drive.

Beta1: The Iceni has jumped! I repeat. The Iceni has jumped!

Command: Acknowledged, pilot.

Alpha2: Request a status brief, Command! What the hell is going on here?

Command: You're out of line, pilot!

Alpha2: Out of line? I don't think so. We're risking our lives out here! We deserve a straight answer!

Command: You can discuss this at your debriefing. We now have reports that rebel vessels are heading for the jump node. Stand by for mission update. Command out.

Alpha2: Damn it! Command let Bosch escape!

Alpha3: What are you talking about?

Alpha2: They pulled the blockade. They gave us the wrong coordinates. There's no other explanation.

Alpha3: Why? Why would they let him go?

Alpha2: You tell me, pilot. I'm informed on a need-to-know basis.

Alpha3: Stand down. We're on your side here.

Alpha2: Why did we attack the Iceni? Why did we destroy that cargo? I can live with being a pawn if the game makes sense.
[[Category:Main Freespace 2 Campaign]]

User:Stormkeeper

2008-07-10T15:33:27Z

Stormkeeper: New page: I'm Stormkeeper. And this page is still under construction. I'm a long time HLP member, but just recently started helping around on the Wiki. I dislike bad English. I'm also in the proc...

I'm Stormkeeper.

And this page is still under construction.

I'm a long time HLP member, but just recently started helping around on the Wiki. I dislike bad English. I'm also in the process of creating weapons, mostly for capital ships, and a single player campaign, as yet unnamed.

A Game of TAG

2008-07-09T15:29:05Z

Stormkeeper: Revised the walkthrough, fixed minor formatting errors, corrected description.

{{Mission|next=Proving Grounds|previous=Battle of the Wilderness|campaign=Campaign Walkthrough}}

'''ACT 2, MISSION 2'''

'''Fighter squadron: [[134th Barracudas]]'''

'''Description: Combat Evaluation of the [[GTM TAG-A]]'''

----
==Background==
The 134th Barracudas are called to test the experimental TAG system, which the [[GTVA]] hopes will give them an advantage against the [[Shivans]].

==Walkthrough==

This mission is easier than it looks. You have to fly a [[GTF Ulysses]] with one [[GTW Subach HL-7]] and one [[GTW Prometheus R]]. You also have a new kind of missile in your secondary bank. It is the [[GTM TAG-A]] missile, which is used to paint hostile fighters so a nearby warship can open fire at it from a longer distance, and with higher accuracy. Coupled with the [[ULTRA Anti-Fighter Beam|ULTRA AAF beam]] on the Warspite, this mission can be quite easy.

The first squadron of fighters you encounter are [[SF Basilisk]] fighters. They are easy to hit, but a squadron of [[SF Mara|SF Maras]] come next. These fighters are far more maneuverable and much smaller than the Basilisks and present a greater challenge. TAG them all the way. Try to get as close to them as possible to greatly increase your chance of hitting. There's no easy way to do this, either TAG them all, or take them down yourself. Its much easier to just TAG them though.

Next, the [[GTCv Deimos|GTCv Warspite]] is attacked by Shivan bombers and fighters. You're not properly armed to face those fighters, but you're Alpha 1 so it doesn't matter. As always target bombs and bombers first. Simply TAG the bombers and fighters and hunt down the bombs. Note that unless you're fantastically accurate with the TAGs, you'll probably need to re-arm midway.

Keep your eye on the GTA Lucidity as well. The AWACS goes down pretty fast, especially under hails of Hornet fire.

Sometime after, Kappa 3 will jump in, screaming for Command to pull the fleet from the nebula and to shut the [[Knossos| subspace portal]]. Shortly after he finishes screaming, he gets jumped by Shivan fighters. Finish off the Shivan fighters to win the mission.

==Notable ships present==
*GTCv Warspite
*GTA Lucidity
*Kappa 3 (From the Vanished kappa wing)

==New equipment==
*[[GTM TAG-A]]

[[Category:Main Freespace 2 Campaign]]

Teeth of the Tiger

2008-07-08T16:38:05Z

Stormkeeper: Minor grammar, spelling changes.

==General Info==

'''Project Lead:''' BengalTiger

'''Other Members:''' Hellstryker, Retsof, 0rph3u5, blowfish, Titan, shiv, Colonol Dekker

'''Missions:''' Mission count for final release is unknown, 3 will be included in the demo

'''Mods included:'''

Numerous, including:

*1 entirely new species, plus several more to discover along the way
*Numerous new GTVA ships (in later chapters)
*Many new Shivan ships
*And more!

'''Required:'''

* Lightspeed's Nebulae
* MediaVPs (3.6.8z recommended)
* FreeSpace Open 3.6.9 or later.

==Description==

'''Teeth of the Tiger: Intro'''
''3 missions''

The demo of Teeth of the Tiger takes place 5 weeks after the Capella Incident. GTVA Command had decided to explore the numerous unidentified nodes leading out of allied systems. Regulus was first in line, with Command deciding to explore the Struve AB system. Soon after entering the node, a Shivan ship was sighted, and Command decided to use Meson warheads to close the node. Their actions that day set in motion a chain of events that would decide the very fate of humanity.

==Links==

[http://freespacemods.net/forum/viewforum.php?f=505 Official TotT forums on Freespacemods.net]

Eishtmo's Terran-Vasudan War timeline

2008-07-08T09:28:38Z

Stormkeeper: /* January: */

{{NotAllCanon}}

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

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

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

===2320:===

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


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

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

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

===2321:===

=====January:=====
Prince Mihos killed during drug gang battle. Vasudan politicians blame [[GTA]] outright.

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

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

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

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


===2322:===

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

===2323:===

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

===2324:===

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

===2326:===

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

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


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

===2327===

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

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


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

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

===2328:===

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

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

===2329:===

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

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

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

===2330:===

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

===2331:===

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

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

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

===2332:===

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

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

====2333:====

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

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

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

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

=====June:=====

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

====2334:====

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

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


====2335:====

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


=====January 15th:=====
The Shivans attack Vasudan and Terran forces near the Antares-Ribos node. The loss of the PVC ''Taurus'' and GTSC ''Plato'' leads toward a cease-fire proposal on the 18th by the Vasudans.

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

[[Unification]]''' :PREVIOUS | NEXT: '''[[The Great War]]

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

Technical Terms and Definitions

2008-07-08T08:48:47Z

Stormkeeper: /* Missile Banks */

==Craft Statistics==
===Type===
Text data which appears as 'Craft type' in the ship selection screen.
===Manufacturer===
Text data which appears as 'Manufacturer' in the ship selection screen.
===Maneuverability===
Text data (descriptive) which appears as 'Maneuveribility' in the ship selection screen.

===Max Velocity===
Velocity to reach when your engine recharge is at default rate and you have full speed. The second number is the maximum velocity with engine recharge at maximum rate.
===Armor===
Text data (descriptive) of the strength of the vessel.
====Hitpoints====
The number of hitpoints the craft has. A hit decreases this value, in regard of the damage value * armor factor.
====Shields====
The number of shield hitpoints the craft has. A hit decreases this value, in regard of the damage value * shield factor.

===Length===
Lenght of the ship or object
===Compatible Containers===
List of containers that are designed for the ship (usually freighter) in question. 

==Craft Armaments==
===Gun Mounts===
*Describes the non-turretted primary weapons banks mounted on the ship.
*'''Bank'''
**Number of the primary weapon bank
*'''Guns'''
**Lists the number of primary weapons (=guns) in the bank in question.
*'''Standard Loadout'''
**The default weapons for the primary weapon bank.
*'''Compatible Primaries'''
**The primary weapons that can be mounted to the ship
*Detailed data for different weapons mounted in the turrets can be found from [[Weapon Comparison (FS1)#Standard Primaries|FS 1 Weapon Comparison Table]] and from [[Weapon Comparison (FS2)#Standard Primaries|FS 2 Weapon Comparison Table]]

===Missile Banks===
*Describes the non-turretted secondary weapon (missiles) banks mounted on the ship
*'''Bank'''
**Number of the secondary weapon bank
*'''Capacity'''
**Number of [[GTM Hornet|Hornet]] sized missiles that can be fitted to the secondary weapon bank.
*'''Standard Loadout'''
**The default loadout for the secondary weapon bank.
*'''Compatible Secondaries'''
**The secondary weapons that can be mounted to the ship
*Detailed data for different weapons mounted in the secondary banks can be found from [[Weapon Comparison (FS1)#Standard Secondaries|FS 1 Weapon Comparison Table]] and from [[Weapon Comparison (FS2)#Standard Secondaries|FS 2 Weapon Comparison Table]]

===Turrets===
*Describes the all the turretted weapons mounted on the ship
*'''Turret Type'''
**The type of the turret. In other word the default turret loadout
*'''Amount'''
**The number of the particular type of turret mounted on the ship.
*Detailed data for different weapons mounted in the turrets can be found from [[Weapon Comparison (FS1)|FS 1 Weapon Comparison Table]] and from [[Weapon Comparison (FS2)|FS 2 Weapon Comparison Table]]

[[Category:Tables]]
[[Category:Lists]]

SD Demon

2008-07-08T08:29:18Z

Stormkeeper:

{{FS12_Ships}}
{{shipimage|image=[[Image:demon320x240.jpg]]|caption=The SD Demon}}

==Description:==

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

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

===Developer Notes===
None

==Performance:==
===Statistics===
{|
|-
| style="width:200px" | '''[[Technical_Terms_and_Definitions#Type|Type]]'''
| style="width:200px" | Destroyer
|-
| '''[[Technical_Terms_and_Definitions#Manufacturer|Manufacturer]]'''
| Unknown
|-
| '''[[Technical_Terms_and_Definitions#Maneuverablity|Maneuverability]]'''
| N/A
|-
| '''[[Technical_Terms_and_Definitions#Max Velocity|Max Velocity]]'''
| 20.0 mps
|-
| '''[[Technical_Terms_and_Definitions#Max Afterburner Velocity|Max Afterburner Velocity]]'''
| N/A
|-
| '''[[Technical_Terms_and_Definitions#Armor|Armor]]'''
| N/A
|-
| [[Technical_Terms_and_Definitions#Hitpoints|Hitpoints]]
| (FS1)100 000/(FS2)160 000
|-
| [[Technical_Terms_and_Definitions#Shields|Shields]]
| N/A
|-
| '''[[Technical_Terms_and_Definitions#Length|Length]]'''
| 2139 m
|}

===Armaments===

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

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

The Demon's hull strength increases sixty percent between FS1 and FS2. The ship's beam weaponry is relatively weak (two [[LRed]] and one [[SRed]]), so apparently [V] increased the Demon's hit points at the last minute to make it superior to the [[GTD Hecate|Hecate]] and [[GVD Hatshepsut|Hatshepsut]].

This ship is slightly less capable at taking out fighters than the [[GTD Hecate|Hecate]] and [[GVD Hatshepsut|Hatshepsut]] due to its less numerous anti-fighter turrets, but it is more capable in an anti-capital ship role than any GTVA destroyer if properly positioned.

The Demon appears to be more of a defensive destroyer, given that it's main guns, the two [[LRed|LReds]], are not forward-facing. An easy target if attacked from the front.

Do not underestimate the firepower of this destroyer. If its front beams aren't disabled quickly, even a [[GVCv Sobek|Sobek-class]] corvette won't survive for very long in its sights. Trust me, I saw what happened to the [[FreeSpace_2_Vasudan_Ship_Database#GVCv_Thebes|Thebes]] when I failed to blow them up fast enough on the lowest difficulty level. The Demon may only have one [[SAAA]] on either side of it, but they have a full field of fire to the front and sides. Furthermore, you don't even know where they are until they hit you...and then, it may be too late. Also note that Demon-class warships tend to get disabled fairly easily because of their large and relatively weak engine subsystem, which can be neutralized by just one and a half Helios.

The Demon actually has more firepower than the Lucifer in FS2, which only has 2 SReds.

In FS1 there's a big undefended blindspot inside the "tentacles", leaving the weapons subsystem unguarded by blob turret fire. This just happens to be right next to the fighter bays, however, so be careful. In FS2 the flak batteries provide at least some cover to this area.}}

[[Category:Ship]]

High Noon

2008-07-08T08:21:04Z

Stormkeeper: /* Walkthrough */

{{Mission|next=Return to Babel|previous=Bearbaiting|campaign=Campaign Walkthrough}}

'''ACT 3, MISSION 2'''

'''Fighter squadron:''' [[203rd Scorpions]]

'''Description:''' Help destroy the Santhanas

----
==Background==

Following Alpha's disarming of at least two of the Sathanas' main guns, the Sathanas entered Capella to be confronted by the [[GTVA Colossus]]. If the Sathanas still has at least one main turret operational after [[Bearbaiting]], the Sathanas also decimated an allied fleet near the Capella node.

==Walkthrough==
[[Image:Screen005.jpg|thumb|The Death of the Sathanas]]

(Can't chose weapon loadout or ship selection)

Default: [[GVB Bakha]], 1 [[GTW Mekhu HL-7]], 1 [[GTW Akheton SDG]], 1 bank of [[GTM Helios]], 1 bank of [[GTM Trebuchet]]

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

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

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

''KR's Notes :'' This mission gives you buttwhooping 10K points if you manage to get the Sathanas kill. I found that for some reason, if you order your wingmen to ignore the sathanas, so will the Colossus... So don't do that... just tell them to engage enemy (C-3-9). Your gonna have to do alot of Shift-R to get the kill. I found that the best spot to kill it is the fighterbay... But for some reason, the fighter bay did some small explosion, as if it were disabled, and then the basilisks stopped popping... But couldn't complete objectives because of that... In any other case, just disable flaks and AAA turrets so they don't annoy you, and start camping at the subsystems aronund the ship. Oh , don't stay near the engines, the engine washes are gonna annoy you big time.

==Notable ships present==
[[SJ Sathanas]]

[[GTVA Colossus]]

[[Category:Main Freespace 2 Campaign]]

SSG Belial

2008-07-08T08:19:46Z

Stormkeeper: /* Name origin */ Corrected spelling and grammar issues

{{FS12_Ships}}
{{shipimage|image=[[Image:belial320x240.jpg]]|caption=The SSG Belial}}

==Description:==

===FS2 Tech Room Description===
The SSG Belial sentry gun platform appears to be a radical redesign of the Trident platform that was first encountered during the Great War. Pilots who have encountered both report that the Belial is harder to kill. It is reliably known that the Belial has twice as many laser turrets as the Trident sentry gun. Both types are used to guard storage depots, gas miners, and other Shivan installations.

===Developer Notes===
None

===Name origin===
Belial is an evil being in Jewish apocrypha. His name means "worthless" in Hebrew.
Belial is supposedly the father of Lucifer, and also the one who goaded him into evil and into fighting the war against heaven.

==Performance:==
===Statistics===
{|
|-
| style="width:200px" | '''[[Technical_Terms_and_Definitions#Type|Type]]'''
| style="width:200px" | Sentry Gun
|-
| '''[[Technical_Terms_and_Definitions#Manufacturer|Manufacturer]]'''
| Unknown
|-
| '''[[Technical_Terms_and_Definitions#Maneuverablity|Maneuverability]]'''
| N/A
|-
| '''[[Technical_Terms_and_Definitions#Max Velocity|Max Velocity]]'''
| N/A
|-
| '''[[Technical_Terms_and_Definitions#Max Afterburner Velocity|Max Afterburner Velocity]]'''
| N/A
|-
| '''[[Technical_Terms_and_Definitions#Armor|Armor]]'''
| N/A
|-
| [[Technical_Terms_and_Definitions#Hitpoints|Hitpoints]]
| 160
|-
| [[Technical_Terms_and_Definitions#Shields|Shields]]
| N/A
|-
| '''[[Technical_Terms_and_Definitions#Length|Length]]'''
| 22 m
|}

===Armaments===

*'''[[Technical_Terms_and_Definitions#Turrets|Turrets]]'''
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=2 style="background:#300505;"| '''Freespace 2'''
|- align="center"
| style="width:120px" |Turret Type
| style="width:60px" |Amount
|- align="center"
| [[Shivan Heavy Laser]]
| 4
|}
===Veteran Comments===
{{comment|''The Belial is the only sentry gun you should fear. Four turrets give it firepower commensurate to a fighter from any angle, and while easily dispatched with secondary weapons, as with all sentries you must get rather close to the Belial hit it with primaries. This can be a problem when taking accurate and sustained fire from four Shivan Heavy Lasers.'' 
''All sentry guns are hard to hit at distance, but this is the hardest.'' }}

[[Category:Ship]]

ULTRA Anti-Fighter Beam

2008-07-08T08:16:43Z

Stormkeeper: /* Veteran Comments */

ULTRA Anti-Fighter Beam

2008-07-08T08:16:20Z

Stormkeeper: /* Veteran Comments */

SD Ravana

2008-07-08T08:02:03Z

Stormkeeper: /* Veteran Comments */ Re-directed The Great Hunt link to appropriate mission

The '''SD ''Ravana''''' class of destroyers was first spotted in the [[Nebula System|nebula]] beyond [[Gamma Draconis]], discovered by the GTCv ''Lysander'' and the GTCv ''Actium.''

This class is probably the most powerful Shivan capital vessel, second only to the [[SJ Sathanas|SJ ''Sathanas'']] and maybe the [[SD Lucifer|SD ''Lucifer'']]. In possesion of 4 forward-facing beam cannons, it can rip through the hull of a [[GTD Hecate|GTD ''Hecate'']] or an [[GTD Orion|''Orion'']]-class destroyer in under a minute, and take out smaller vessels within seconds. Its anti-capital ship weaponry make it a threat to any vessel, even one the size of the [[GTVA Colossus|GTVA ''Colossus'']].

But the anti-capital beams come at a price. The ''Ravana''-class is more vulnerable to fighter and bomber attacks than its brother, the [[SD Demon|''Demon'']]-class. Still, it would take a large number of squadrons to take out such a target.

----

{{FS12_Ships}}
{{shipimage|image=[[Image:HTLRavana640x480.jpg|320px]]|caption=The SD Ravana}}

==Description:==

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

===Developer Notes===
None

===Name origin===
In Hindu tradition, Ravana is the antagonist of Rama, legendary king of ancient India. According to the epic poem ''Ramayana'', Ravana is the king of the [[SC Rakshasa|rakshasa]]s.

Ravana is a hindu deity famous in the ramayana for his legendary angers. His name means "he with the mighty roar".

==Performance:==
===Statistics===
{|
|-
| style="width:200px" | '''[[Technical_Terms_and_Definitions#Type|Type]]'''
| style="width:200px" | Destroyer
|-
| '''[[Technical_Terms_and_Definitions#Manufacturer|Manufacturer]]'''
| Unknown
|-
| '''[[Technical_Terms_and_Definitions#Maneuverablity|Maneuverability]]'''
| N/A
|-
| '''[[Technical_Terms_and_Definitions#Max Velocity|Max Velocity]]'''
| 20.0 mps
|-
| '''[[Technical_Terms_and_Definitions#Max Afterburner Velocity|Max Afterburner Velocity]]'''
| N/A
|-
| '''[[Technical_Terms_and_Definitions#Armor|Armor]]'''
| N/A
|-
| [[Technical_Terms_and_Definitions#Hitpoints|Hitpoints]]
| 100 000
|-
| [[Technical_Terms_and_Definitions#Shields|Shields]]
| N/A
|-
| '''[[Technical_Terms_and_Definitions#Length|Length]]'''
| 2346 m
|}

===Armaments===

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

===Veteran Comments===
{{comment|''The Ravana is scary-looking, but it's not tough. Weaker in terms of hull strength, and MUCH weaker in terms of turret strength then the Demon, the Ravana pays for its attack-oriented design with weak defenses. Indeed, fighters and bombers can range over the front three-quarters of Ravana's upper surfaces with near-impunity, and the lower-spine-mounted SAAA beam is placed too far back to defend the Ravana's main guns. It has a flak turret and another SAAA for anyone who comes up behind it, however. A capital ship behind a Ravana, on the other hand, is the Shivan destroyer's death sentence, as its engine subsystems are not strong and cover nearly the whole rear surface of the destroyer. Paired Trebuchets to the main beams the moment one of these enters the mission, then ignore it unless directed otherwise.''

''In [[The Great Hunt (FS2)|The Great Hunt]] I was actually able to destroy the Ravana's main beam cannons before it fired on the [[GTCv Deimos|Deimos corvettes]], that's how weak they are. (Didn't make a difference, the corvette is destroyed by a [[SEXP]]). However, the Ravana, if used in its intended offensive role, can easily decimate a destroyer before being destroyed.''

''In a nutshell, the Ravana is useless if it is engaged from behind, and a light threat if side to side with another destroyer. This destroyer's saving grace is in its raw firepower facing foward. When deployed in a strategic position, or jumping in behind another destroyer, this beast will be your worst nightmare. Since most destroyers have their main beams facing forward and the odd ligher beam mounted aft (in the Hecate's case, two), it can dish out enough firepower to level the destroyer, and only take moderate damage. but this is only the case when the Hecate is alone. Roughly two wings of fighters, of any class, can knock out any anti-cap beam the Ravana wields & keep fighter cover on a friendly vessel. Just keep an eye on its beam cannons & you should get out all right. As stated before, the Ravana is no Demon, so it can't take as much punishment.''

''Ah yes, the Ravana is a fearsome sight, and it does have some fearsome weapons to suit...only that they're all pointing forwards. That single [[SAAA]] on its rear may be an annoyance to bombers, but that's all it has for rear fighter-bomber cover. Destroy it and get a corvette to jump in behind it, and the Ravana's finished.''

''The Ravana is one of the most powerful destroyers in FS2 (in terms of anti-warship firepower), and can beat out even an Orion in a duel. Its anti-fighter defenses are somewhat mediocre, however, and its main beams have weak armor in addition to its anti-fighter defenses being positioned poorly to defend them. You should be able to take out its main beams in a matter of seconds with your primaries without being bothered by any of its defenses.''

''We see three warships of this class in the main FS2 campaign and we don't know if they're widely present in the Shivan fleet. In custom campaigns the Ravana is without any doubt the most common Shivan capital ship. The player is usually tasked to destroy its main beam cannons in deja-vu missions which are an outrage to this warship. If you consider the presence of a Ravana in your custom campaign, try to avoid typos like the one mentioned above and don't make it a sitting duck easy to defeat. Don't forget that the first Ravana encountered by GTVA forces easily destroyed a corvette and a destroyer and damaged many other ships: it really is a considerable threat and the using the fire-beam SEXP to maximize firepower isn't forbidden.''}}

[[Category:Ship]]