In many of the missions, the FS2 design team created a certain event with a particular name (event names are not displayed in-game), built up the mission, and then had to change the ship that that event referred to. But the event sometimes retained the original name, revealing interesting tidbits about how the mission was originally planned...
Mission | Discrepancy |
A Lion at the Door (SM1-04.FS2) |
This is the first mission with Shivans in FS2, where you attack a Shivan cargo depot near the Knossos in Gamma Draconis. There is an event named "Destroy Moloch" that actually refers to Leo wing, composed of Shivan Astaroth fighters. |
The Great Hunt (SM1-06.FS2) |
First encounter with the Ravana-class destroyer here. The mistake is almost the exact same as the one above, just with the "Moloch" reference now referring to a wing of Mara's, Pisces. |
Slaying Ravana (SM1-07.FS2) |
The Ravana is destroyed in this mission. Again, same "Moloch" mistake here with Leo, a wing of Basilisk fighters. |
Proving Grounds (SM2-03.FS2) |
Just a note: What with all the Moloch mix-ups, I think it's safe to say that the original plan was to introduce the Moloch-class corvettes earlier on in the game. However, this is the first mission where one is encountered (testing of the Pegasus-class stealth fighters). The problem is that the Moloch-class corvette encountered here is not introduced by Command as a new, never been encountered Shivan warship. The message displayed upon it's arrival is: "The Shivans have sortied a Moloch-class corvette, designation Tiamat." Also in this mission is an misnamed event (again); Delta wing has an event labeled for Beta wing. One last thing about this mission: If you don't destroy the Moloch, then in the debriefing recommendations it says that "In order to destroy the Moloch-class corvette, you must keep it within sensor range. You are providing sensor support for the Aquitaine." I can't find any kind of event in the mission that would cause this dependancy of the destroyer on a fighter's sensors. Is this something built-in to the engine for nebula missions or is it just a bunch of hot-air? |
Feint! Parry! Riposte! (SM1-10.FS2) |
This is the mission where rebel Admiral Koths' destroyer, the Orion-class NTD Repulse tries to ram the GTVA Colossus and is destroyed. The event name which frees the Repulse beam turrets to fire is called "Iceni Armed"... |
A Game of TAG (SM2-02.FS2) |
Testing the TAG missiles in the nebula in this mission. It's kinda out of sensor range and you never really fly closer to it, but in FRED2 you can see that there is a jump node labeled "Capella" about 10-15 klicks away from the action. There is no jump corridor between Capella and the nebula. |
The Fog of War (SM2-07.FS2) |
The Sathanas is first encountered in this nebula mission. The events in the mission that occur after the juggernaught arrives are called "Apoc arrives" and "Apoc arrives 2" - SJ Apocalypse, anyone? |
A Monster in the Mist (SM2-08.FS2) |
This is the mission where you fly as a Vasudan stealth fighter to scan the Sathanas' subsystems. The beam-free event for the Sathanas is called "Beam Free All Apoc" in this one as well. |
Speaking in Tongues (SM2-09.FS2) |
In this mission you're supposed to lure the Sathanas in by attacking a Shivan cruiser. You discover that the Iceni is in the area trying to communicate with the Shivans. In the briefing it states that "The GVCv Sopedu will provide fire support for this operation." That's all fine and dandy, but in the mission the corvette's name is the GVCv Thutmose... My guess as to the reason for the change is that the name "Sopedu" sounded too stupid when they did the voice acting. :) |
Bearbaiting (SM3-01.FS2) |
You're supposed to take out the Sathanas' forward beam turrets in this mission. Another event name mix-up here: "Beta Wing down" refers to the destruction of Delta wing. |
High Noon (SM3-02.FS2) |
This was that mission we all waited for - the GTVA Colossus vs. the SJ Sathanas. The thing to note for this mission is not a mistake, but it still shows something about what would have been. The Sathanas has the "Red Alert Carry Status" box checked. This does not mean that the Sathanas was supposed to be carried over from the previous mission (in "Bearbaiting", above, the Sathanas does not have the "Red Alert Carry Status" checked), but that this mission was originally designed to end with a Red Alert, and that the next mission would have the same Sathanas... |
Straight, No Chaser (SM3-03.FS2) |
Supposed to capture the Shivan transport carrying Bosch, but it's not in the area. The Psamtik is destroyed by a 2nd Sathanas at the 2nd Knossos <sniffle>. Another reference to the Sathanas as an "Apoc" in an event. |
Argonautica (SM3-05.FS2) |
The mission is to defend the disabled GTD Aquitaine until an Argo-class transport (the Argo, actually - appearently the first of it's class) boards with a damage control team. The interesting thing is that there is a debriefing section that has the usage formula of "false"; it will never appear in the mission. The unused text reads: "Your sighting of the Shivan juggernaut has provided Intelligence with valuable information regarding the potential strength and movements of the enemy fleet." Hmmmm.... |
As Lightning Fall (LOOP2-1.FS2) |
This is the one where you rescue Lt. Cmdr. Snipes. The Argo-class transport that jumps in to dock with Snipes' transport, Lambda 1, has some event names that refer to it as the GTT Teloron. Another thing is that this mission, which is near impossible to complete without getting lost a few times, is essentially 2D. There is almost no Y-axis (up/down) positioning. Just imagine how hard it could be... :) Tip/Cheat: If you simply can't get to the end of the nav buoy maze, try this. From the first nav buoy head straight towards the second one (it helps to close in on the second one first so it doesn't jiggle around in your radar). Make sure you're aligned exactly, 1st to 2nd, then start cruising. After around 9000 meters from the 2nd nav bouy, the Grall should come into view. :) |
Exodus (SM3-06.FS2) |
In this mission you escort a convoy of Capellan refugees to the Epsilon Pegasai node. The Cain-class Gibborim is refered to as the Psoloc by some event names. The Argo-class Lambda 1 was Scipio, and Lambda 2 was Severius. The Hippocrates-class Vesalius was the Sachan. Probably all were changed so they wouldn't sound so dumb. |
Clash of the Titans II (SM3-09.FS2) |
The next to the last mission of the campaign, where you escort the GTD Bastion, loaded with Meson bombs, to the Capella-Epsilon Pagasai node. The event that occurs when the Bastion's hull is critical is named "Colossus Hurt".... |
Apocalypse (SM3-10.FS2) |
The last mission of the campaign has you protecting the ships fleeing to the Vega node (until the nice supernova, that is...). The following cargoes are spread in ships and containers throughout the fleet: Machine tool parts, Taxation Census Reports, Parker's Boots, Dravis' diary, Abbot Laurent's Journal, Medical Supplies, Foodstuffs and Orenian koi. That last one sounds like a great name for space crack. :) Interesting priorities the GTVA has... The usual mix-ups in event names are rampant here, but I get the feeling that this time it's not all accidental...: GTT Notus is called Omega in the message text and the voice-over; GTFr Io's escape/destroyed events are named "Deanna Safe/ Deanna down"; the GTFr Miranda's events use the name "DC Ward"; GTCv Lemnos = "Overlord "; GTC Zollner and GTC Sparta (Leviathan and Aeolus, respectively) = "La Rochelle" and "Resolve"; the GTM's Sydenham, Herophilus & Boerhaave = "Immac", "Munif" & "Repr" and the GVG Hez-Ur = "Immo". Bizzare, no? BTW, those last four, the medical ships and the gas miner, may be just shortened nicknames for their original full names. I say this because the Overlord was referred to a couple of times as the "OVR", the La Rochelle as the "Roch", etc. But I couldn't find any remaining full names that matched the last four. |