Version 2.3.2:



Started on July 28th, 2009 by Mobius. Completed on August 8th.



Issue: The GTC Arctius (Aeolus) doesn't have a proper nameplate - the one currently present in the modpack is "GTCvArctius".



Important change: The credits mission has been removed and the campaign file has been modified accordingly. I believe that mission should be used only for the voice acted version of Warzone.



Modpack: 



- Stars.tbl removed and replaced with Warzone-str.tbm.



- Warzone logo modified to show the FSCRP logo.



Generic changes, applied to all missions:



- Command briefing stages with "<default>" as animation have it changed to "default".



- In nebula missions, the minimum speed necessary to show trails has been set to 1 and the ambient light (RGB) has been set to 35.



- Very common wing names (such as Pisces, Cancer and Aries) have been changed when necessary. The changes are described below.





Episode 1 Mission 1:



- The player is no longer able to issue orders to transport Omega.



- "Okay Command" message text. "Orders recieved Command." ---> "Orders received, Command."



- Built-in arrival messages for Aries and Pisces wings' removed to prevent message conflicts.



- GTCv Odin replaced and rotated so that it can bring three turrets to bear on the Disen. A new event will make sue that the third beam is able to fire on the Disen, and the fire sequences have been delayed for more accuracy (beams are not precise of the Odin is still slowing down upon its arrival).



- Arrival of Zeta and Theta wings delayed by 3 seconds because the wings used to arrive when the Hatshepsut's speed was too high to make the launch look plausible.



- A new event effectively increases the rotating time of the Disen's solar panel to represent the damage sustained by the science cruiser.



- Two new events add the "Contact the Disen" and "Protect the Disen" directives. There were no directives refered to the Disen.





Episode 1 Mission 2:



- Briefing, Stage 5: The Valius icon has been flipped to face the prominent "Subspace Disturbances" icon.



- Scout wing Theta, mentioned during the briefing, has been renamed "Omicron". This change seemed necessary because the previous mission already featured a wing named Theta, and that name might lead the player to assume that the wing will be present during the mission (which doesn't happen).



- The Shivan freighters Delfta and Marach, as well as their cargo containers. have been beam-protected by default. Two new events will unprotect the freighters and the cargo several seconds after their arrival. This prevents the Valius and Gaudua from firing on these assets as soon as they jump in, thus eliminating them very quickly.



- Arrival order of the Shivan freighters mentioned above reverted. The Marach, which is docked to Container 01, used to arrive after the Delfta (which is docked to Container 02).



- A new event will prevent the Valius from firing its BGreen on the SD Revial. The beam causes considerable damage, and in later appeareances of the Shivan destroyer its hull integrity is at maximum levels.



- Another, new event will deactivate all beams on the Valius if the destroyer has taken immense damage from the Revial and is about to go down. This prevent the Valius from damaging the Revial (which is at full strength later in the campaign) until the final explosion.



- Event "d11" (showing the "Destroy Revial" directive) has been modified to remove the "[1]" part which used to appear in the previous version.



- Libra wing has been turned into Taurus.





Episode 1 Mission 3:



- Briefing, Stage 3: Camera position changed for variety purposes.



- The player is no longer able to issue orders to convoy ships.



- Built-in arrival messages for Scorpio and Cancer wing removed to prevent message conflicts.



- The event that makes calling support ships after the arrival or destruction of the Warlock has been checked and fixed.



- The orders which can be issued by the players to his wingmen have been checked and modified.



- Libra wing has been turned into Sagittarius.



- Cancer wing has been turned into Leo.





Episode 1 Mission 4:



- Briefing, Stage 4: The three Shivan depot icons have been merged into one.



- The event that reduces the Equinox's speed has been delayed to prevent the corvette from reducing its speed too early during the mission. Additionally, the corvette's average speed after the event has been increased by circa 2 mps (from 5-8 mps to 8-10 mps).



- The Abydos' arrival message, which is supposed to be sent by the cruiser's CO, used to be sent by Command. This has been changed.



- The Imra has been replaced to be closer to the main battle area.



- Aries wing has been turned into Aquarius.





Episode 1 Mission 5:



- Briefing, Stage 2-5: The Regulus node has been set as hostile.



- Briefing, Stage 5: Catharsis icon flipped to face the node and RBCs. Additionally, "Good luck pilot!" has been changed to "Good luck, pilot!".



- Libra wing's built-in arrival message has been removed to prevent message conflicts.



- Two additional fighters which are destroyed before the beginning of the mission have been added to Theta wing. Additionally, the wing's default orders have been changed so that the wing will either engage any hostiles or guard the player after the destruction of Mjolnir 2.



- A new event, triggered 3 seconds after the arrival of the warships Catharsis and Gibson, removes the Amerton from the escort list and adds the newly arrived warships.



- The RBCs' jamming effect has been improved even more by tagging the Mjolnirs before becoming undetectable. Accordingly, the Mjolnirs will be untagged should be Amerton be destroyed (a new event ensures that).



- Aries wing has been turned into Leo.





Episode 1 Mission 6:



- Briefing, Stage 1: All icons have been flipped to face the others properly. The "Shivan Attack Force" icon has been highlighted.



- Briefing, Stage 2-3: The "21st Vasudan BG" has been moved from stage 3 to stage 2 because the former did not mention it at all. Additionally, according to the briefing text, "21st" has been changed to "12th". The Revial icon in stage 3 has been highlighted.



- Briefing, Stage 5: Kappa wing icon highlighted.



- Briefing, Stage 6: Camera position and Britannia icon moved to make the corvette icon more visible.



- The Nheameai and its first waypoint path have been moved up to prevent the corvette from arriving too close to the Britannia. Additionally, the Moloch has been rotated to bring the beam weapons to bear and its average speed has been increased by 4 (from 8-11 to 12-15 mps).



- Two new events make sure that the warships Britannia and Eleris approach the Revial to attack it without actually ordering them to go berserk against the Ravana.



- Pisces wing has been turned into Sagittarius.





Episode 2 Mission 1:



- Briefing, Stage 2-4: Measia (GTM Hippocrates) icon changed from Freighter to Cruiser.



- Briefing, Stage 2: Measia and Theta icons replaced because they were partially covering each other.



- Briefing, Stage 3: Camera position and icons Alpha and Beta replaced.



- Briefing, Stage 4: All icons other than the Regulus Knossos and the Remehas have been removed because the stage is focused on the Moloch.



- The Equinox has been moved even more (Z: -135 meters) so that its departure message doesn't conflict with other messages.



- The player was able to issue orders to Theta 2 (GVFr Bes). This has been changed.



- "attacks?" message delayed by 5 additional seconds to prevent message conflicts.



- "Mayday!" message text. "Remehas is right behind us!" ---> "The Remehas is right behind us!".



- Destroying Gemini wing is now necessary to consider the area secure.



- "Terminated" message text. "Command, the Shivan warship has been eliminated." ---> "Command, the Shivan units have been eliminated."



- Aries wing's number of waves reduced from 3 to 2.



- The arrival of the Tatenen has been delayed by 5 additional seconds.



- Lambda wing now takes off from the Tatenen's fighterbay.



- Aries wing has been turned into Aquarius.



- Pisces wing has been turned into Sagittarius.



- Cancer wing has been turned into Capricorn.





Episode 2 Mission 2:



- Briefing, Stage 4: Hawkeye icon flipped to face the Warlock.



- A new event with a repeat count of 255 will make the Regulus node disappear in a progressive way as the player and the Hawkeye penetrate deeper in the nebula.



- Arrival sounds for the arrival of the debris have been removed.



- Alpha and Beta wings replaced so that they can start the mission from a position that makes their provenience (GTD Warlock's fighterbay) more evident.



- Aries wing has been turned into Scorpio.



- Cancer wing has been turned into Leo.



- Pisces wing has been turned into Virgo.



- Taurus wing has been turned into Aquarius.





Episode 2 Mission 3:



- Briefing, Stage 2: The Shivan depot icon is no longer highlighted (the stage is focused on Alpha wing). Additionally, the camera position has been moved for variety purposes.



- Zeta wing will not arrive if at the time of Aries' destruction the Kameth's integrity is at 14% or lower. It makes no sense to sortie the bombers only to inflict minimal damage.



- A new event will order Alpha wing to attack the sentry guns instead of remaining close to the player without doing anything.



- Tau 1's (Lt.Com. Niven) new orders are to stay close to the player without actually guarding him/her.





Episode 2 Mission 4:



- The event "Warlock 25" will become true only if the Miranda has docked safely. The message text's is a clear reference to the Miranda's repair teams so sending the message if the Argo hasn't docked yet made no sense.



- "Target Destroyed" message text. "Well done pilots!" ---> "Well done, pilots!".



- Just like the Sakatha, the Kalsa has also been beam-protected by default and is made targetable by beams 5 seconds after the Sakatha.



- Bonus goal and specific debriefing stage added. They will be used if the player and his wings manage to save the GTC Hawkins.



- Aries wing used to be launched by the Warlock. The arrival anchor has been set to Kebla now.



- Taurus wing's number of waves has been reduced from 2 to 1 because the wing is launched by the Kebla and its destruction is linked to the main mission goals. Taking down the Kebla too early meant preventing Taurus wing from being destroyed.



- Aries wing has been turned into Aquarius.



- Pisces wing has been turned into Sagittarius.



- Libra wing has been turned into Capricorn.





Episode 2 Mission 5:



- "Objective Achieved" message text. "Well done pilots!" ---> "Well done, pilots!".





Episode 2 Mission 6:



- Briefing, Stage 1-4: The "Mintaka" icon has been renamed "Kaus Borealis" and has also been set as hostile.



- Aries and Virgo wings' built-in arrival messages removed to prevent message conflicts.



- Alpha, Beta and Gamma will guard the Tatenen as soon as the destroyer arrives. These wings used to ignore the Hatshepsut's arrival.



- Time delays between the activation of the Tatenen's main beam cannons have been significantly reduced to give the destroyer a more concrete chance of eliminating the Lilith-class cruiser Remehya before it inflicts too much damage.



- The event linked to the "Remaya Beam destroyed" message has been modified so that it will become true after taking down the correct turret.



- Aries wing has been turned into Leo.



- Pisces wing has been turned into Gemini.



- Cancer wing has been turned into Aquarius.





Episode 3 Mission 1:



- Briefing, Stage 1-4: The Gienah Cygni icon has been set to hostile.



- All Tempests have been removed from Beta wing's default loadout. They have been replaced with Harpoons.



- "Demon Scramble" message text. "The Requelm is scrambling it's fighter wings!" ---> "The Requelm is scrambling its fighter wings!".



- Virgo wing's number of waves has been reduced from 2 to 1 because the wing is launched by the SD Requelm and its early destruction may prevent wave 2 from arriving.



- Aries and Virgo wings' built-in arrival messages removed to prevent message conflicts.



- The main wings' orders have reduced priority values now. This allows the player to issue orders the other wings can follow.



- Two Vasudan wings have been added to escort the Nethys and/or the Psama at the end of the mission.



- Aries wing has been turned into Scorpio.



- Virgo wing has been turned into Sagittarius.





Episode 3 Mission 2:



- "Accomplished" message text. "Alpha and Beta wings return to base.  Zeta wing, stand watch." ---> "Alpha and Beta wings, return to base.  Zeta wing, stand watch."



- Zeta wing's orders have been checked and changed so that the wing will effectively move to guard the Jauluun as soon as the area is clear.



- The combination break warp/fix warp (used to boost the jamming effect) has been replaced with never warp and allow warp.





Episode 3 Mission 3:



- Briefing, Stage 2: Kirosi icon highlighted.



- Aries wing's orders have been checked and changed so that the wing will move to attack the Casitgar without getting distracted by the player's squadron. The wing will depart from the field should the Casitgar be destroyed.



- Aries, Libra and Pisces wings' built-in arrival messages removed to prevent message conflicts.



- Two new events will clear Alpha and Beta wings' orders should the Kirosi arrive and then order them to attack any hostiles. This prevents Alpha and Beta from remaining close to the Casitgar even during the battle between the Warlock and the Kirosi.



- Aries wing has been turned into Gemini.



- Cancer wing has been turned into Leo.



- Virgo wing has been turned into Aquarius.



- Pisces wing has been turned into Scorpio.





Episode 3 Mission 4:



- Briefing, Stage 4: The "Cmd Niven" icon has been renamed "Lt. Com. Niven".



- Briefing, Stage 5: "Commander Niven" ---> "Lieutenant Commander Niven".



- Tempests removed from Alpha, Beta and Tau 1's loadout. They have been replaced with Trebuchets.



- The second message in the event "first conversation" has been delayed by 14 seconds so that Tau 1 (Niven) will send it after the arrival of the Vidar. The message, in fact, is a clear reference to the arrival of the explorer.



- Niven's initial waypoint speed has been set to 80-85. A new event will ensure that Niven will move near the Vidar in an apparent attempt to scan the ship as soon as the explorer arrives.



- Beta wing's departure cue, which was left blank, has been properly changed so that the wing will follow Alpha as it warps out.



- Stiletto II and Piranha warheads removed from the loadout because GTF Pegasus-class fighters can't be equipped with them.



- Pisces wing has been turned into Leo.





Episode 3 Mission 5:



- Briefing, Stage 1: "Commander Niven's" ---> "Lieutenant Commander Niven's".



- Briefing, Stage 2: Gemini icon moved up so that the Vidar's icon would not override Gemini's name.



- Briefing, Stage 3: The distance between Alpha and Beta icons increased because the icons' highlight effects were partially covering each other.



- The Themnos and Liberty's average starting speed has been set to 5-8 mps. Higher speeds prevent the Liberty from eliminating the Themnos in time.



- A new event will guardian the Liberty's beam turrets (11, 12, 23 and 24) to prevent the Themnos from destroying them.



- The Liberty's departure has been delayed by 10 seconds to prevent message conflicts.



- Full stops removed from the goal texts.



- Cancer wing has been turned into Sagittarius.





Episode 3 Mission 6:



- Briefing, Stage 3: The distance between the Mjolnir icons has been increased so that the icons' highlight effects won't cover each other.



- Briefing, Stage 4: "Good luck 636th!" ---> "Good luck, 636th!".



- "Wont't Be" message text. "Keep an eye out pilot." ---> "Keep an eye out, pilot."



- Aries wing's arrival message removed to prevent message conflicts.



- "planeta1" and "p_terran1" planet bitmaps rotated to face the most prominent star properly.



- "Accomplished" message text. "Mission accomplished pilots!" ---> "Mission accomplished, pilots!".



- The Coventry group's arrival has been delayed by 7 more seconds to prevent the warships from firing on the Nox's debris upon jumping in.



- Thanks to a new event and four new waypoint paths, the Coventry's group will not remain immobile upon arrival. It will move into position ahead of the node at reduced speed (5 mps).



- Virgo wing's delay between waves values have been significantly reduced.



- Four new wings have been added to escort the Coventry's group.



- Aries wing has been turned into Gemini.



- Virgo wing has been turned into Aquarius.



- Pisces wing has been turned into Capricorn.





Episode 3 Mission 7:



- Capricorn and Aries wing's built-in arrival messages removed to prevent message conflicts.



- The event "daskha down" has been delayed by 4 seconds to prevent possible message conflicts with the event "Daskha 5". Both events may have become true pretty much in the same moment.



- The event that made jumps possible if the Warlock is lost has been checked and fixed so that it can work properly.



- The Odin's arrival has been delayed by 12 additional seconds to prevent message conflicts and make it appear in a 'calm' moment of the mission.



- The event "MBS - Save wingmen" has been removed because it protected too many wingmen. Also, the random wingman protection events were already taking care of possible balance issues, ergo "Save wingmen" was unnecessary.



- The departure cue of all wings belonging to the Warlock have been changed so that these wings will land on the destroyer at the end of the mission. Four new events will order them to jump out if the Warlock is destroyed.



- The event "shiv talk" has been delayed by 7 seconds to prevent message conflicts.



- The event "friends" has been delayed by 24 seconds and the arrival delay of the cruisers Ragelam and Carcharot [Parvati] has been reduced accordingly. Now, the messages match in-game events properly.



- The Warlock used to be invulnerable when facing the cruisers Ragelam and Carcharoth [Parvati]. This has been changed so that the destroyer will sustain damage from the Rakshasa-class cruisers.







Version 2.3.1:



Started on June 30th, 2009 by Mobius. Completed on July 16th.



Modpack: "3056" value after the GTE Vidar's tech description set to -1 to prevent possible translation issues. All empty spaces in the modular table have been cleared.



Generic changes, applied to all missions:



- Squadron wings that are under the direct control of the player will depart if the mission is failed or accomplished.



- The player's starting speed will be at 100% - there's no point in being immobile upon jumping in.



- Delay between waves for all hostile wings checked.



- Squadron Reassign in Mission Specs section checked. In many missions of the campaign, the player was considered squadless and no squadron logos were used.



- Shivan secondaries checked. They appear to be unused in many missions, and many Shivan units aren't even equipped with the original weapons (same as the ones used by the GTVA).



- Delay between stages in most briefings changed - 500 and 1000 milliseconds weren't that much and influenced dynamic movements in a negative way.





Episode 1 Mission 1:



- Briefing, Stage 2-3-5: Disen (2), Alpha (3) and Tatenen (5) icons highlighted.



- "Repeat" message. "What is your status Disen?" ---> "What is your status, Disen?"



- Disen message. "GTSC Disen this is Alpha 2, 332nd Black Mantas, 7th Fleet." ---> "GTSC Disen, this is Alpha 2 from the 332nd Black Mantas, 7th Fleet."



- GVD Tatenen's arrival delayed by 8 seconds. It used to arrive and send messages while Command and Russik were still talking about the destruction of the Disen.



- Delay between waves of the following increased by the values between parentheses: Aries (3), Cancer (2), Libra (4-7), Pisces (1).



- The event "Tatenen clear" and the goal "Area Secured" will become true after 3 additional seconds.



- "planetb" bitmap rotated a bit to face the blue sun properly.



- Libra wing's orders changed so that the wing will actively attack whatever threatens it instead of going berserk against the Omega transport.



- Cancer wing's arrival location has been changed from a fixed point in space to a generic "Near Ship - Disen 3065" (thus increasing the average distance to the Disen by 500 meters). The wing is composed of two waves so watching the second wave jumping in exactly where the first one arrived was a bit weird.



- Pisces' wing arrival has been delayed by 6 seconds - the bombers used to jump in too early.



- The Odin's arrival and departure delays have been reduced by 14 and 2 seconds, respectively. This change was necessary so that the corvette's movements fit better in their respective contests (especially the arrival one).



- The event "omega departed" used to became true 12 seconds after the departure of Omega. The delay (connected to the above change) has been changed to 4.





Episode 1 Mission 2:



- Briefing, Stage 4: Valius icon flipped to face the Subspace Disturbance icon properly. The icon has also been highlighted due to its prominence. Additionally, Alpha and Beta icons in the same stage have been replaced to prevent them from covering the Valius' icon.



- The Valius has been slightly moved back to prevent the Revial's beam shots from missing the Orion and halt the mission.



- There are two wings named Kappa in the mission: one is a Vasudan scout wing mentioned in the briefing while the other is a Terran wing that is called as reinforcements. I've changed the former to "Theta".



- Delay between waves values for the following wings increased: Libra (2), Pisces (1), Scorpio (3), Aquarius (3), Gemini (2).



- Alt Name for the Knossos Portal edited so that it won't be visible in game. "Knossos Portal" and "Knossos" were a bit redundant. The name will appear as usual.



- Shivan cargo containers named following the "Container XX" naming convention.



- The Revial will arrive 9 seconds before. The wait was too long and wave the impression that the mission wasn't progressing.



- The Gaudua's departue cue has been changed so that the cruiser will depart 5 seconds after the destruction of the Valius. The previous cue left the cruiser immobile on the battlefield for a long while.



- Specific waypoint for the Revial added. The destroyer will fly it at reduced speed (random between 4 and 8 m/s).



- The "Destroy Revial" directive will become unvalid after the destruction of the Valius. There's no way to take the Ravana out at that point of the mission, and treating the "Destroy Revial" directive as an achievable one was not appropriate.



- Reinforcement wing Kappa will not be available to be called after the destruction of the Revial.



- The standard orders of the Shivan bomber wings (Scorpio, Gemini and Pisces) have been changed so that the bombers may choose to attack the Gaudua instead of concentrating their fire on the Valius. Gemini wing (SB Taurvi) will even prefer to go after the Gaudua, leaving the Valius to the better suited Nephilim and Nahema bombers.



- Kappa wing is now a squadron wing, meaning that it will appear in the list of wingmen.



- "Firepower" message head ani set to CM-5 because the message comes from the Valius.





Episode 1 Mission 3:



- Briefing, Stage 1-2: Transports and Hyperion icons replaced a bit to prevent overriding. Alpha wing's icon has been moved up a bit because it was partially covering the Sirius (jump node) icon.



- Briefing, Stage 4-5: Warlock icon highlighted (4) and flipped (4-5) to face the Sirius jump node.



- The cruiser Manasha will have an anti-spacecraft beam at its disposal. In order to prevent it from causing too much damage to civilian vessels, the beam will be activated 30 seconds after the arrival of the cruiser (15 seconds after the activation of the main beam weapon).



- The Warlock will jump before completing its waypoint path (distance < 1500 meters). For possible message-related issuess, the message "2000 meters" (to the node) has been turned into "3500 meters". Pretty much the same thing happened to the event "1000 meters", which has been turned into "2500 meters". The text of the messages have been changed according to the new settings.



- The source of a message which is supposed to be sent by the Warlock was "Command". This has been fixed.



- An event will ensure that all wings that remained in the system will move to protect Alpha 1 after the successful departure of the Warlock.



- The event "accomplished" used to become true if the goal "Warlock Depart" wasn't satisfied. The message sent by Command even orders all wings to jump out even if they're supposed to guard the node from possible Shivan attacks. Therefore, the text of the message has been changed from "Mission accomplished.  All wings, jump out now." to "The Warlock has departed safely.  Well done!"



- The event "Hold the node" has been delayed by 10 seconds to prevent message conflicts with the event "accomplished" and its modified message.



- A new event will ensure that all allied wings will escape to Sirius by using the jump node. There are no allied units available to recover the fighters in Regulus.



- If the GTM Callisto is destroyed, its escort wing (Kappa) will remain in system to assist the other GTVA assets. The wing's orders have been edited accordingly.



- The player is now uncapable of ordering other allied wings to depart. They will depart automatically at the end of the mission.



- Because there's no place in the system to jump to, the player's subspace drive will be active only in close proximity of the jump node.



- Arrival of Aries (and, consequently, Virgo) wing(s) delayed by 7 seconds because they used to jump in too early in the mission.



- For gameplay reasons, the Warlock has been replaced so that it will take a bit more to use the node. This change is intended to balance the effect of another change listed above, which leads the Warlock to engage its subspace drive well before completing its waypoint path.



- Two events will ensure that support ships will arrive from/land to the Warlock's fighterbay if the ship is present. If the Warlock is destroyed or departed, support ships will no longer be available. Before the arrival of the destroyer, support ships will enter the area from subspace (as usual).



- Wings Kappa and Phi set as squadron wings for better monitoring of their status.





Episode 1 Mission 4:



- Briefing, Stage 2: Shivan fighter wing icons moved a bit - they were partially covering both a planet and corvette icon.



- Briefing, Stage 3: All icons other than those representing the Shivan depot moved. They were partially covering it.



- Briefing, Stage 4: Shivan corvette icon moved a bit because it was partially covering the depot. The camera has been slightly replaced to put an emphasis on the possible presence of Shivan reinforcements.



- Briefing, Stage 5: Camera position changed for variety purposes.



- The Equinox's orders have been changed. The corvette is now ordered to follow waypoints during the whole mission instead of alternating waypoint paths with pure chases. A new waypoint path has been added to boost the effect.



- A new event will ensure that the Equinox's speed is reduced as soon as the corvette gets in close proximity of the cargo depot. Thanks to this, the corvette will be able to bring its beam weapons to bear in the upcoming warship encounters.



- The Shivan corvettes Imra and Ahalya has been moved behind so that they won't risk to collide with GTVA units upon jumping in. This change should also help with the management of the upcoming warship encounter.



- Both corvettes will be slowed down upon jumping to manage the encounter in a more accurate way. Specific waypoints for both assets have also been created.



- The event "Molochs here" was linked to the arrival of the Keseu and Jaual, which are two Shivan freighters that don't jump in during the mission (they are already on the field of engagement). The event has been edited so that it will be linked to the arrival of the Shivan corvettes Imra and Ahalhya.



- The Abydos has been replaced and has also been ordered to follow a new waypoint path at reduced speed



- The Hellion cruisers will follow a waypoint path at reduced speed instead of attacking the Equinox. The previous setting used to cause certain collisions. The distance between the two cruisers has also been increased by several hundred meters.



- All Shivan cargo containers have been renamed following the "Container XX" naming convention.



- Cancer wing's delay between waves values have been increased by 3 seconds.



- Beta wing now has the default order to attack the Hellion cruisers (priority 100) any hostile ship in the area (priority 50). The wing used to stay immobile upon arrival.



- Hellion wing (2 Rakshasa-class cruisers) has been disbanded. The cruisers have been renamed Hellion 1 and Hellion 2, and will keep the same orders as before.



- Alpha wing has the default order of guarding Alpha 1 now (the rest of Alpha wing used to remain immobile at the beginning of the mission). Delta wing's new orders are to guard Alpha wing (and not only Alpha 1) with a priotity of 100. Delta also has the new default order of attacking any hostile ship (priority 50).



- "Beta Late" message head ani, which was missing, has been set to TP-4. Same thing for "Abydos Destroyed", whose ani has been set to CM-2.





Episode 1 Mission 5:



- Briefing, Stage 4-5: Alpha wing icon removed because it was out of place. Stage 4 focuses on the network of RBCs while stage 5 focuses on the Sobek corvette Catharsis (whose icon has been highlighted and moved a bit for better visibility and prominence).



- The Mjolnir RBCs will become undetectable in a progressive way, whose timings depend on the distance of each RBC to the AWACS Amerton.



- The warships Catharsis and Gibson will arrive after the destruction of Libra wing. They used to arrive if the wing was still on the field, and messages reported that the area was secured. Additionally, achieving the goal "Node Blockade" is also a necessary condition to make the warships arrive and consider the mission a success.



- "Delta Wing" message persona changed. Delta is a wing of Sekhmet bombers and the message showed a TP-7 head animation. The ani has been changed to VP-2.



- A new event will make the Regulus node red. The system has been conquered by the Shivans and is therefore hostile.



- Theta wing is now a squadron wing. A new event will randomly damage the wing's subsystems at the beginning of the mission (the fighters have already partecipated to an engagement before). Also, Theta 1's hull integrity has been changed to 57 (it used to be 35, just like Theta 2's, which is strange).



- Aries wing's arrival has been delayed by 6 seconds to prevent message conflicts.





Episode 1 Mission 6:



- Briefing, Stage 3: The stage should be about a Vasudan battlegroup, for some strange reason the icon was misplaced and not visible ingame. The camera position has been changed to show the Vasudan icon, which has also been highlighted due to its importance.



- Briefing, Stage 5: Kappa and Britannia icons replaced. Kappa wing's icon was partially covering that of the Revial while the Britannia's icon was barely visible.



- The arrival of the Eleris has been delayed by 8 seconds to prevent message conflicts.



- An event will ensure that the Cain-class cruisers Chaitanya and Draupadi will not go berserk against the Britannia. They will rather follow new waypoint paths at reduced speed.



- Arrival of Virgo wing delayed by 4 seconds. Virgo's delay between waves has been increased by 10 - the wing, which jumps in front of the player, used to respawn quickly and attack the player immediately. This may have caused issues due to the fact that this is a bombing mission and the player is exposed to enemy fire.



- The Nheameai will follow a new waypoint at reduced speed instead of going berserk against the Britannia and the Eleris. The corvette has also been replaced for a better looking warship encounter.



- The destroyer Revial will follow its own waypoint path at reduced speed. The change is primarily intended to give a concrete chance of victory to the player and his wings.



- The Revial will become invulnerable if the Britannia and the Eleris are destroyed by its beam cannons. The destroyer will also depart from the field soon afterwards, effectively preventing the player from destroying it and turning the mission into a success even if two important GTVA assets (whose destruction causes the mission to fail) are lost.



- Recommendation text for losing the Eleris during the mission has been changed from "Destroy all Shivan targets in the combat zone." to "Destroy all Shivan targets in the combat zone, but don't forget to take a look at the hull integrity of important GTVA assets in the sector."



- The Hecate destroyer Leonov has been added to the escort list. Although the player's objectives have nothing to do with that warship, its arrival on the battlefield may be barely noticeable following the chaos caused by the Revial (and lead the player to think that the message coming from the destroyer makes use of a special source). Adding the Leonov to the escort list should make the arrival of that Hecate a bit more noticeable.



- Head animations for the following messages set as specified: "Zone is Hot" (TP-1), "What is that?" (TP-2), "That's It?" (TP-3), "Odd2" (TP-1), "What?" (TP-5), "New Signature! (TP-3 - sender set to <any wingman>), "Eleris Hurt" (CM-5), "Fleet Reporting" (CM-4), "Two Cruisers" (CM-4), "Powering Weapons" (CM-4), "Britannia Damage" (CM-4), "Weapons 2" (CM-4).



- "Odd3" message text. "It's possible pilots." ---> "It's possible, pilots."





Episode 2 Mission 1:



- Briefing, Stage 3: Alpha, Beta and Queth icons replaced because they were partially covering other icons. Beta wing's icon has been highlighted.



- Briefing, Stage 4: Remehas icon and camera position replaced to face the scenario from a more generic point of view. Furthermore, Alpha wing's icon is no longer highlighted.



- The Equinox has been replaced so that its departure message will not conflict with other messages. The changed distance is very difficult to notice during the mission.



- Virgo wing's delay between waves values increased by 3.



- Seraphim-class bombers and Manticore-class fighters were mixed in the same wing, Taurus. The Manticores have been removed from the wing and now form a wing on their own, Gemini. A specific directive for Gemini wing has also been added.



- The event "more shvs" and "eat it" are now linked to the arrival and the destruction of Gemini wing, respectively.



- Alt Name of Regulus Knossos edited so that the word "Knossos" won't appear twice when targeting the portal.



- The arrival of the Nicolas has been delayed by 6 seconds. That of the Remehas has been delayed by 9 seconds to give the player more time to approach the Nicolas.



- The arrival of the Tatenen has been delayed by 12 seconds. The destroyer has also been replaced for beam targeting purposes.



- Delay between waves of the following wings increased: Cancer (4), Pisces (2), Scorpio (3), Aries (3), Leo (6-9).



- Leo wing's number of waves has been reduced from 3 to 2: it is quite impossible for a Moloch to carry so many spacecraft, and directives may not get satisfied if the last wave hasn't taken off yet at the time of the Remehas' destruction.



- The player is no longer able to issue orders to Lambda wing.



- Cancer and Libra wings' built-in arrival messages have been deactivated to prevent message conflicts.



- All allied ships except the Tatenen (Equinox, Theta 1, Theta 2, Queth, Measia and Nicolas) could receive orders from the player. This has been changed for obvious reasons.



- Destroying the Shivan corvette Remehas is now a necessary condition to consider the mission a success. This change prevents message conflicts and also makes the whole situation look more plausible.



- The Remehas has been replaced so that it won't jump in too close to the Nicolas.



- Head animations for the following messages set as specified: "Nice Quiet Patrol?" (TP-3), "Eat it!" (TP-6).





Episode 2 Mission 2:



- Command Briefing, Stage 1: "long before the it was expected to perish" ---> "long before than it was expected to perish".



- Briefing, Stage 1-3: Jump node (1), Warlock (2) and Hawkeye (3) icons highlighted.



- Briefing, Stage 4: Camera position changed for variety purposes (without considering the text, stages 3 and 4 were basically the same).



- AWACS radius reduced from 8000 meters to 5500 meters. The default nebula range has been reduced from 7000 meters to 3500 meters.



- Libra wing will jump 3300 meters from the player. Its previous arrival target, Capricorn 1, caused the wing to jump in where it was placed in FRED after the destruction of Capricorn 1. Furthermore, the wing's delay between waves values have been changed from 0-0 to 6-9.



- A new event will generate randomized warnings if the player gets too far from the Hawkeye. There are five randomized messages and the event will send one of them every 12 seconds if the player hasn't returned back (or if the status of the mission doesn't lead the player to stay close to the AWACS).



- The directive "Escort the Hawkeye" will become true only after the successful end of the reconnaissance mission. It used to become true after the destruction of the last Shivan wings, which is not plausible giving the fact that the GTVA don't know how and when the Shivan attack ends.



- The Space Hunks will arrive if the distance between the Hawkeye and its designated waypoints is less than 3000 meters (and not 1500).



- Unknown 1 and 2's names will be hidden. Only the alt names, "Unknown Debris", will be readable.



- The event "accomplished" will become true after 10 additional seconds to prevent message conflicts.



- The AWACS Mar-herah is no longer AI protected by default. The Shivans will be able to damage it a bit and an event will protect and guardian both the hull and the engines of the AWACS only if it's sustained considerable damage.



- The player's starting position has been replaced (Y: -100 meters) to prevent possible collisions with Alpha 2 and/or Alpha 3 at the very beginning of the mission.



- Thanks to a new event, Sigma wing's subsystem integrities randomized because the wing was previously involved in a fight.



- Pisces wing's orders expanded so that the Shivan fighters would engage the Hawkeye's fighter escort if necessary.



- A new event will make the Regulus jump node invisible 5 minutes after the beginning of the mission. The player is supposed to venture deeper in the nebula and lose both visual and sensor contact with the Warlock, but the node was still visible at high distances.



- There were two AWOL debriefing stages in this mission, and even with bogus conditions set for them. Those stages have been merged into one with a more logical condition. Also, the second stage had a "Your failed your objective" which has been changed with "You've failed your objective".



- Because it was strange to have all attacking Shivan wings jumping in near the Hawkeye during the mission, wings composed of just one wave will arrive without the jump effect. Furthermore, they will be hidden from sensors for a few seconds (2-4) before the Hawkeye reveals their position. This should give the impression that those wings were patrolling the area and then found GTVA units.



- All Shivan wings except Cancer and Libra have their distance to target (arrival location) value increased by about 1300 meters. Those wings used to jump in too close to the Hawkeye (about 2000 meters). This change should make things more realistic and should also improve the change mentioned above (patrolling wings).



- Pisces wing's minimum delay between waves values have been increased by 4 seconds.



- "Sending Another Team" message text. "Roger that Hawkeye." ---> "Roger that, Hawkeye."



- The AWACS Hawkeye will depart as ordered by Command - the Charybdis used to remain immobile on the field after that order.



- Rho wing, which had no default orders, has been ordered to guard the Hawkeye. The wing will also depart from the field at the end of the mission (instead of remaining immobile).



- The message "Sathana Debris", which was sent by the Warlock, is now sent by the Hawkeye. The message's head ani has been changed from CM-5 (which wasn't even appropriate for the Warlock) to CM-3 (that of the Hawkeye).



- The Sathanas debris will be hidden from sensors until the Hawkeye processes the data (7 seconds after the "going over schematics" event). A new event has been created for this purpose.



- Thanks to a new event, the Sathanas debris will have their glowmaps deactivated - having them active was pointless at that point.



- Head animations in the following messages set as specified: "I knew it!" (TP-8), "What?" (TP-4), "Nebula!" (TP-8), "Roger" (TP-5), "Running Scared?!?" (TP-6).





Episode 2 Mission 3:



- Briefing, Stage 1: Three Shivan cargo container icons (one of which was highlighted) have been replaced with a single "Cargo Wing" icon, which is also highlighted.



- Briefing, Stage 2: The Shivan Depot icon is no longer highlighted and two unnecessary cargo container icons have been removed.



- Zeta wing's arrival cue has been modified so that the bombers will not jump in if the cruiser Kameth is destroyed. The departure cue has also been edited in a way that will lead Zeta to jump out 4 seconds after the destruction of the Shivan cruiser.



- The event "cargo depot" now has the "Move to Investigate" directive text linked to it.



- Cancer wing's arrival has been delayed by 5 seconds: the wing's appeareance was too innatural for its originary purpose.



- Gemini wing will arrive 7 seconds (instead of 0) after the freighter Troy. Taurus wing will arrive 4 seconds (instead of 0) after Gemini.



- The GTF Pegasus named "LCDR Niven" has been renamed "Tau 1". The fighter's callsign has been set to "Lt. Com. Niven" so that the original intent of the campaign creator will be represented properly.



- A new event will show a training message reporting that the data transfer from Tau 1 (Niven) to Alpha 1 is complete. The transfer used to be mentioned by one of Niven's messages, only.



- The "jump now" event will become true 2 seconds after the departure of Tau 1 (Niven) and not 16 seconds after the arrival of Niven himself.



- The Shivan cruiser Kameth used to appear on the escort list at the very beginning of the mission, even if the cruiser was well out of sensor range. A new event has been created to add the cruiser to the escort list only if a friendly unit gets sufficiently close to it.



- Aries wing had high delay between waves values, which caused the cruiser Kameth to remain defenseless for a long period and get destroyed. Because the destruction of Aries is linked to the arrival of Zeta wing (GTB Zeus), which otherwise would never enter the field of engagement, the value has been diminished to 5-7. For safety reasons, however, the "zeta deploy" event will not become true should the Kameth be destroyed before Aries wing.



- Delta wing's default orders have been modified so that the wing would move to guard Alpha wing if no hostiles are in the area (situation that occurs later, when the freighters depart with their valuable and mysterious cargo).



- "Shivan Fighters" message text. Commands asks to protect a transport, but there's a Triton-class freighter on the field at that point. Therefore, "transport" has been changed to "freighter".





Episode 2 Mission 4:



- Briefing, Stage 3: All icons have been replaced because they were partially covering each other.



- Briefing, Stage 4: The Tatenen's icon has been moved a bit because it was partially covering that of the Kebla. Both mentioned icons have been highlighted.



- In order to prevent the early destruction of the Shivan cruiser Sakatha, the warship has been beam-protected. An event will unprotect it 18 seconds after the beginning of the mission.



- The Rakshasa-class cruisers Parvati and Jagganath will be beam-freed after 15 and 22 additional seconds, respectively.



- The Miranda's cargo has been set to "Repair Teams" because of the text of critical messages. Thanks to a new event, its cargo will be transferred to the Warlock.



- Second part of the "Miranda Destroyed" message changed from "We cannot repair the Warlock,  All fighters, abort mission!" to "We cannot repair the Warlock...  All fighters, abort the mission!"



- Delay between waves values of the following wings increased: Virgo (4), Cancer (3), Pisces (4), Taurus (6-10).



- Zeta wing is now a squadron wing.



- Theta (GTB Boanerges) will no longer be able to receive orders from the player. The wing will also move to land on the Warlock as soon as the Kebla is destroyed (if the Warlock is destroyer, it will jump into subspace).



- All allied wings (except Theta) now have the default orders to attack any targets of opportunity and guard the Warlock. The priorities are the same, so the wings will behave depending on their own situations.



- "Here She Is" message text. "Do it now pilots!" ---> "Do it now, pilots!".



- "No Dynamic Goals" option selected for Taurus and Leo wings (SB Taurvi), so that they will go berserk against the Warlock. Their priority to attack the Hecate has been raised from 50 to 100 to prevent the bombers from getting distracted during their run.



- The event "Miranda Repairs" was linked to the destruction of the Kebla and not to the docking procedure of the transport, meaning that the Warlock's engines were likely to be reported as partially repaired even if the transport was still away. This has been changed for the sake of plausibility with a delay of 25 seconds after the dock (combined with a delay of 15 seconds after the destruction of the Kebla). Additionally, the "Miranda Repairs" event will not become true if the Warlock is destroyed, and the warship will become invulnerable to prevent it from getting destroyed by the Kebla's debris.



- In order to match the change mentioned above, the Kirosi's arrival cue has been edited so that the arrival of the destroyer will also be linked to the Warlock's repair operation and not to only the destruction of the Kebla.



- A new event will progressively repair the Warlock's engine subsystems by 1% every 21 seconds. The repair will commence 43 seconds after "Miranda Repairs".



- Just like Theta, Epsilon and Kappa wing will either land on the Warlock or jump out depending on the outcome of the mission. In order to boost the effect, Kappa wing will arrive from the Warlock's fighterbay instead than coming from subspace.



- Head animations in the following messages set as specified: "Changing Mission" (VP-1), "Warlock Destroyed" (CM-2), "Miranda Destroyed" (CM-2).





Episode 2 Mission 5:



- Briefing, Stage 3: Alpha wing icon moved a bit because it was partially covering the name of the icon "Shivan Depot Location Marker".



- Briefing, Stage 3: Shivan gas miner icon, waypoint icon and camera position moved a bit to have a better view on all icons.



- Briefing, Stage 4: "Unknown" icon highlighted and Alpha wing icon replaced. Camera position also changed for a better view.



- "All Ships Beam-Freed By Default" mission flag selected so that all Shivan warships on the battlefield will fire their anti-spacecraft beams on incoming GTVA units.



- Four waypoint paths (with 3-4 waypoints each) have been added for the specific purpose of having the all major assets (Rahu miners, Taour cruiser and Mar-herah AWACS) moving during the mission. An event will effectively slow down those assets.



- The "depot destroyed" event will become true after 6 seconds to prevent message conflicts.



- Maximum AWACS sensor radius set to 7000 meters (instead of 12000).



- The Vidar's name will remain hidden while its alt name will appear as usual. The event that changes the Vidar's alt name from "Unknown Vessel" to "GTE Vidar" will become true 6 seconds later than before.



- The event "return to base" will become true after 5 additional seconds for messaging purposes.



- The Vasudan AWACS Mar-herah will depart at the end of the mission.



- The number of Tempests in the loadout has been significantly raised so that the player's wingmen can also make use of that weapon.



- All allied wings now have the default order of attacking any hostiles (priority 100) and guard Alpha 1 (priority 89).



- "return to base" event delayed by 13 additional seconds to prevent message conflicts with Russik's messages.



- "Accomplished" message text. "Mission accomplished pilots." ---> "Mission accomplished, pilots."



- The Vidar's arrival has been delayed by 14 additional seconds to prevent message conflicts. The event "depot destroyed" has also been delayed by several seconds for the same reason.



- Reinforcement wing Epsilon will no longer be available to be called at the end of the mission.



- The Pharos nav buoy will disappear following the achievement of the "Depot Destroy" mission goal.





Episode 2 Mission 6:



- Briefing, Stage 1: Mintaka jump node icon highlighted.



- Briefing, Stage 4: The Tatenen icon used to become the Vidar's icon in stage 4 - this has been changed by creating a separate icon for the Vidar and moving the original Tatenen icon at the center of the jump node. The Vidar's icon type has also been changed from "corvette" to "cruiser" to match the style used in the other missions of the campaign.



- The first message sent by a random wingman showed the VC head ani. The message has been edited so that it will show a normal VP1 head animation.



- Gamma and Libra wings' built-in arrival message deactivated to prevent message conflicts.



- "p_deadp1" background bitmap increased to X/Y: 3.2 to make it more prominent (without showing the bitmap's detail glitches). "p_lava1" bitmap set to X/Y: 0.5 because having two big planets was not plausible.



- Because the mission takes place in a previously unexplored system and the player's base (Tatenen) appears during the mission, the player will be able to jump out only if: a) he's sufficiently close to the jump node (waypoint created to check the distance) or b) the Tatenen has jumped out and the player is ordered to return back to the destroyer. In any other circumstance, jump drives will not be operative. Furthermore, the player will not be able to order his wingmen to warp out (they'll do it by themselves when needed).



- Two events have been added to show the "Wait for Expeditionary Force" directive and send several messages that were not linked to any mission events. The messages coming from random wingmen didn't have a head ani, which has been set to VP-1. The RTB directive has also been delayed accordingly.



- Text of the "Accomplished" message changed from "Mission accomplishedm pilots.  All units, return to base." to "Mission accomplished, pilots.  Russik's expeditionary force will take it from there.  You may jump to the Tatenen."



- If the Tatenen is destroyed, all wings will use the Mintaka jump node to get back to GTVA space. All departure cues have been edited accordingly.



- Thanks to a new event and the modification of the "Tatenen here" event, support ships will not be available to be called in until the destroyer has entered the system (and they will arrive from the Hatshepsut's fighterbay). After the Tatenen's departure, support ships will arrive from subspace as usual.



- Pisces wing's delay between waves values increased by 2 seconds. The wing's arrival location has been changed from a static position in space to a more generic "near - any friendly - 2750 meters".



- Four new events have been created to ensure that the Tatenen will not fire 2-3 BVas beams at the Lilith class cruiser Remehya. The events will activate the main beams in a progressive way.



- Head animation for the message "Tatenen Down" has been set to CM-2.



- Asuras wing has been renamed Sagittarius. The name Asuras does not appear anywhere else in the campaign, so it seemed appropriate to stick with the classic naming convention.





Episode 3 Mission 1:



- Briefing, Stage 4: Alpha and Basil icons replaced. The Basil's icon has been renamed to a generic "Shivan Warships?" and its icon have been changed from "Cruiser" to "Cruiser Wing". The GTVA doesn't know what kind of Shiva units will emerge from the node, so this change seemed appropriate. Also, Alpha wing's icon will no longer be highlighted - the highlight flag has been assigned to "Shivan Warships?".



- The arrival of all Shivan convoy ships been delayed by 9 seconds: they used to arrive too early.



- Azrael 01's cargo changed from "Personell" to "Personnel".



- Gamma wing's built-in arrival message removed to prevent message conflicts.



- "Allow Daisy-chained Docking" mission flag activated and 9 more Shivan cargo containers (their names follow the "Container XX" naming convention) have been added. All of them have a specific cargo and several name changes were necessary so that the numbers could match the order of arrival of the Shivan freighters/transports that carry the containers.



- The Shivan cruisers Demoth and Basil will arrive after 6 additional seconds. They used to arrive too early (2 seconds after the destruction of the convoy).



- The Nethys will fly through its waypoints at a lower (randomized) speed for a better use of beam weapons.



- Destroying Aries and Taurus wings is now a necessary condition to accomplish the mission: the area cannot be considered secured if there are several hostiles left on the battlefield.



- Reinforcement wing Zeta will no longer be available to be called in if the mission is accomplished or failed.



- Default orders of all allied wings modified so that they will either engage the enemy or guard Alpha 1. This way, wings will not remain immobile during the mission. Specific orders, such as attacking the Requelm or protecting the Psama, have been kept.



- The Gienah system is hostile, so thanks to a new event the jump node that leads to that system is red now.



- The message "Demon Here", whose text is "Command, Demon class destroyer entering engagement area!", used to be sent by Command (CM-2 ani). The source has been changed to <any wingman> and the head ani to VP-2.



- The "Accomplished" message, sent by Command, had no animation. It's been obviously set to CM-2.





Episode 3 Mission 2:



- Briefing, Stage 2: Alpha and Beta wing icons moved a bit because they were covering each other. Those icons have also been highlighted.



- Briefing, Stage 3: Camera position changed for variety purposes (it was the same as stage 2's and nothing changed between the two stages).



- "p_deadp1" bitmap replaced, rotated and set to X/Y: 1.5. "p_lava1" bitmap set to X/Y: 0.45.



- Taurus and Gemini wings will be ordered to guard the AWACS Cortez via an event and not via starting orders. This will prevent an error warning (the Cortez changes IFF during the mission so FRED considers guarding it as an error) from popping up. Also, the default orders of those wings have been edited so that they will attack any hostile ship in range if the Cortez is destroyed.



- An event will represent the jamming effect coming from the Cortez at regular intervals. Support ships will not be available to be called and messages will be scrambled. The intensity of the jamming effect depends on the distance between the player and the radar domes of the Cortez. Furthermore, all subspace drives will be broken as long as the jamming will continue. Everything will be brought back to normality as soon as the jamming will be interrupted.



- Contact with Command will be restablished even if the player and his wings manage to take out the radar domes of the Cortez without actually destroying the AWACS. The message saying "The Cortez is down! Command, do you read?" has been split in two. The first part is used for the "Destroy Cortez" directive, while the other will be used for the "cortez down" event, which will become true if the radar domes are destroyed.



- The Vasudan corvette Jauluun has been slightly moved backwards. It used to jump in too close to (if not well inside) the main area of operations.



- The event "persue?" [sic] has been delayed by 3 seconds: it would be impossible for the Jauluun's CO to know what the tactical situation is like a mere 0 seconds after the arrival of its ship.



- "All Ships Beam-Freed By Default" flag activated: hostile beams used to be activated only after the arrival of the Jauluun and not when Russik went rogue.



- Destroying the AWACS Cortez is now necessary to accomplish the mission. This change is primarily due to the fact that the jamming source can be stopped without destroying the AWACS.



- Zeta wing's orders have been changed so that the fighters will attempt to secure the area before moving to escort the GVCv Jauluun.



- "Command!" message text. "Admiral Russik is ignoring us Command." ---> "Admiral Russik is ignoring us, Command!".



- Vasudan head anis selected for the messages coming from the player's wingmen.





Episode 3 Mission 3:



- Briefing, Stage 2-3: Cut to next (2)/previous (3) stage option set. In stage 3, "Stilleto" ---> "Stiletto".



- Briefing, Stage 4: Alpha and Beta icons higlighted.



- Briefing, Stage 5: Casitgar icon's IFF set to unknown (the warship will be disabled, but not friendly). Kirosi and Vidar icons highlighted and moved to prevent them from covering other icons. Vidar icon flipped to face the other units. Alpha, Beta and Casitgar icons replaced. Warlock icon created, highlighted and flipped.



- "p_deadp3" increased to X/Y: 3.0.



- A new event using the good-secondary-time SEXP has been added. Thanks to this event, wingmen should try to disrupt the Casitgar's subsystems instead of damaging the warship's hull.



- The event "no longer hostile" will become true after 3 additional seconds to prevent message conflicts.



- A new event will ensure that the cruiser Casitgar will use its anti-spacecraft beams against the player and his wingmen.



- The event "Casitgar friendly iff" has been delayed by 3 seconds so that its effects match Command's message in the most accurate way.



- The event "lock turrets" has been modified so that the Casitgar's beams will also be deactivated following the redesignation of the warship's IFF.



- The "No Such Thing" message used to come from Command even if it was fairly obvious that the message's true source is the Kirosi. The source has been edited.



- Command's message that marked the successful outcome of the operation (destruction of the destroyer Kirosi) was sent as soon as the Casitgar was disabled. This has been changed.



- The Casitgar's persona was missing, so it's been set to CM5 (female).



- Aries wing's (GTB Medusa) arrival has been delayed by 12 seconds: the bombers used to arrive in a very innatural as soon as the Casitgar was disabled. The increased delay should make things look a bit more realistic. The wing's payload has been changed so that the bombers will use thee Cyclops and not the Cyclops#short. The wing will finally move to attack the Casitgar as it should thanks to a couple of SEXPs and the "No Dynamic Goals" flag.



- The Kirosi's arrival cue was "and  -  is-goal-true-delay Comm Out 120   -   is-goal-true-delay Engine Out 0". It's been changed to "is-destroyed-delay 10 Aries" to prevent an innatural and premature arrival of the destroyer itself.



- "Kirosi Launches Bombers" message text. The final word, "Warlock", has been changed to "Warlock."



- The player will no longer be able to issue orders to Zeta wing because the bombers' task may be disrupted by player orders such as "Cover me", "Protect my Target" or "Engage the enemy" (which, giving the noticeable presence of enemy fighters and bombers, are to be taken into serious account).



- The Casitgar's orders will be cleared as soon as the warship is disabled. This prevents "Waypoints - Time to: Unknown" from being displayed after the IFF change.



- The Escape Pod's cargo has been changed from "Admiral Russik" to "Nothing. "Admiral Russik" has been set as callsign. The Hermes' arrival has been delayed by 11 seconds to prevent message conflicts.



- Two events will make sure that the player and his wings will not be able to jump out if the Warlock is on the battlefield.



- Minimum delay between waves values for the following wings increased: Libra (2), Aries (5-8), Pisces (4-7).



- All fighters in Alpha and Beta wings (except Alpha 1) will be locked so that the player won't be able to change their loadout in the briefing. This is a necessary change because two subsystems on the Casitgar need to be destroyed (comms and engines) and changing the loadout may result in odd situations, like destroying the cruiser instead of capturing it. The player will be able to customize his own loadout, so the lock is not a real problem.



- "Engine Out" goal text. "Disable Casitgar's  Engines" ---> "Disable Casitgar's Engines".



- Thanks to a new event, Alpha and Beta will move to guard the Casitgar as soon as the cruiser's IFF is changed to friendly.



- Upsilon transport's arrival has been delayed by 12 additional seconds to prevent message conflicts.



- Capricorn wing's (GTB Artemis) orders have been changed so that the bombers will move to attack the Warlock instead of getting distracted. The effect has been boosted thanks to the "No Dynamic Goals" flag.



- A new, chained event has been created to show the RTB directive after the departure of the Warlock.



- Head anis for the following messages set as specified: "2 Mins Comm No Engine" (CM-2), "2 Mins No Comm Engine" (CM-2), "1 Mins Comm No Engine" (CM-2), "1 Mins No Comm Engine" (CM-2).





Episode 3 Mission 4:



- Briefing, Stage 2-3: "Unknown" (2) and Alpha (3) icons highlighted.



- Briefing, Stage 4: "Alpha 4" icon has been renamed "Alpha" because it marks the whole wing.



- Briefing, Stage 5: Cmd Niven icon no longer highlighted. Without considering the text, stage 5 is the same as stage 4 so highlighting a single icon twice serves no purpose. In order to add more variety, the camera's position has been changed.



- The Pegasus "Cmd Niven" has been renamed "Tau 1". "Lt. Com. Niven" has been set as Tau 1's callsign. The briefing mentions him both as a Commander and Lt. Commander, so it's unclear which rank is the correct one. In the previous mission in which he appeared, his status was Lt. Commander - that status has been kept in this mission as well.



- The Vidar's arrival has been delayed by 15 additional seconds. The ship used to jump in only 4 seconds after the beginning of the mission, which was a very short timespan. Also, the Vidar has been slowed down and will not approach the Shivans at full speed.



- The Vidar's departure cue has been edited so that the ship will depart as soon as the Shivan Comm Node is destroyed or if it's sufficiently close to its waypoint path.



- Cancer wing's orders have been modified so that the wing will actively engage the player and his wingmen instead of moving on a defensive patrol around the Comm Node.



- "Area secure" message text. The final word, "base", has been changed to "base."



- Cancer wing's minimum delay between waves values increased by 2.



- The first message displayed by the event "Jammer Destroyed" is the same as the one sent by Niven at the beginning of the mission. The source has been changed back to "Command".



- There are two RTB directives whose appeareance depends on wheter or not the jammer is destroyed before the rest of the Shivan forces. In order to prevent both directives from appearing (because it's possible to destroy both the jammer and the other Shivan units) a single RTB directive has been set. It will appear following the achievement of any of the required objectives.



- Just like in E3M2, an event will represent the jamming effect caused by the Shivan Comm Node. This time, however, messages won't be scrambled and the EMP intensity will be minimal - the messages sent before the destruction of the Jammer are the way too important to be unreadable. The delay between disturbances is also significant (13 seconds).



- Mission flags edited so that only Command's built-in messages will be disabled during the mission. Command will be able to send built-in messages after the destruction of the Jammer.



- "Forces Destroye [sic] First" event changed so that it will become true as it should (Shivan forces eliminated before the destruction of the Jammer). The attached message, "Defenses Destroyed", will be sent by a random wingman and not by Command (it's impossible for Command to send that message). The message's ani has been changed to TP-4 (instead of CM-2).



- "All Ships Beam-Freed By Default" option turned on so that the cruiser Samat may fire its SAAA on GTVA fighters if possible. The Vidar is beam-protected, so there are no risks.



- "Clear the Area" message delayed by 4 seconds to prevent conflicts. CM-2 head ani set because the message comes from Command.



- TP-6 ani used in message "Blast!". CM-2 ani used in "Area Secure".



- Shivan wings' orders changed so that the fighters will not remain immobile at some point of the mission. They will either guard the Jammer, the Samat or attack any GTVA units.



- Tau 1 (Niven) will be randomly slowed down at the beginning of the mission so that he won't fly his waypoints quickly and then sit to wait for the Vidar's departure.





Episode 3 Mission 5:



<Please note that many other changes to this mission have been made only a few days before I started version 2.3 - you may wish to check those changes to know more about the current status of this mission. They're listed below.>



[



- Mission edited via Notepad to remove all ";; FSO 3.6.10;;" entries within the file. Those entries cause the instant corruption of the mission file upon saving.



- Leo, Aquarius and Libra are now ordered to attack the Vidar thanks to an event. This prevents FRED from considering their initial orders as an error (the Vidar is hostile at the beginning of the mission).



- Planet A bitmap rotated to face the star as it should.



- The Themnos and the Liberty both used to fly through their waypoints at maximum speed - I added an event to slow down those warships and preventing them from performing a flying circus.



- Transport Omega is now ordered to dock to the Vidar.



- Two wings of Perseus-class fighters, Theta and Iota, have been added. The wings are ordered to guard the Vidar.



]



- Briefing: Vidar icon's type changed from corvette to cruiser.



- Briefing, Stage 1-2: Vidar (1) and Gemini 1 (2) icons highlighted.



- Briefing, Stage 4: Beta wing is no longer highlighted. Also, the "GTCV" designation for the corvette Liberty has been changed to "GTCv" and "[...] available.  Your [...]" has been changed to "[...] available. Your [...]" by removing the unnecessary space.



- Briefing, Stage 5: Camera position moved and cut option selected (from stage 4 to 5 and vice versa). The Liberty's icon has been removed because it was out of place.



- Capricorn 1 and 2's cargo has been set to "Shivans". Although generic, it works fine for Azrael-class transports.



- "On the ready" event delayed by 2 seconds. It used to become true and display a tense warning message as soon as the mission started.



- Virgo wing is supposed to be near the Vidar at the beginning of the mission, but its arrival cue is set in a way that will make the Shivan wing jump in 3 seconds after the beginning of the mission. That value has been set to 0.



- Wings Pisces and Virgo will progressively move to attack the player and his wings should they get too close to the Vidar. Those wings were previously ordered to protect the Vidar, but they did almost nothing until before the player could deplete its secondary banks.



- Aries wing's arrival has been delayed by 3 seconds. The wing used to arrive in a strange way as soon as Aquarius jumped in.



- The corvettes Liberty and Themnos have been slowed down even more to have a better looking warship encounter. The Liberty has been replaced to have a better chance of firing its frontal turrets.



- The Themnos' first waypoint has been replaced in way that will allow the Shivan corvette to fire at least one of its beam cannons on the Vidar.



- Debriefing, Stage 6 (Failure - Vidar Destroyed): "Admiral Russiks" ---> "Admiral Russik's".



- Delay between waves values of the following wings changed: Leo (+3,-4), Aquarius (4).



- A new event will make the Naos node red. The system is hostile and that's where Russik is heading to.



- Thanks to a new event, Alpha and Beta wings will move to guard the Vidar as soon as the ship's IFF is changed to friendly.



- Coriana's persona changed from CM-1 (same as Russik's) to CM-5 for variety purposes.



- Destroying Leo wing is now a necessary condition for the Coriana to arrive, as the destruction of the Themnos is not related to the player's efforts in repelling the Shivans.



- Omega transport replaced to prevent it from colliding with the Philosties.



- Wings Theta and Iota will split to guard the Vidar, Coriana, Philosties and Omega. The wings will arrive after 2 additional seconds so that the ships they need to protect will already be on the field.





Episode 3 Mission 6:



- Briefing, Stage 2: Maya, Nox and Nagas icons highlighted and replaced because they were too close. The camera's position has been changed as well for variety purposes.



- Briefing, Stage 3: Alpha wing icon replaced because it was partially covering the RBC network. All Mjolnir icons have been highlighted.



- Briefing, Stage 4: Alpha wing's icon highlighted.



- Beta wing's arrival has been delayed by 6 seconds to prevent message conflicts.



- Destroying Aries and Virgo wings is now a necessary condition to consider the mission a success and leave the area.



- The GTCv Coventry's persona has been changed from CM2 to CM3. It was the same as the one used by Command. Also, the message that is supposed to come from the Coventry was sent by Command - the source has been edited accordingly.



- Shivan cargo containers "Cargo 1" and "Cargo 2" have been renamed "Container 01" and "Container 02", respectively.



- A new event will change the color of the Kaus Borealis jump node to red.



- The arrival of both the first Shivan group and Virgo wing has been delayed by 6 seconds to prevent possible message conflicts and make it look more natural.



- "First Wave" message sender. The content of the message is "We've got the first wave of the attack force arriving now, Command!" and the message used to be sent by Command (which didn't make sense). The sender has been changed to <any wingman>.



- "Incoming Fighters" sender fixed. The ani was TP-1, but the sender was Command - it's been changed to <any wingman>. Same thing for the "Ravana Down" message, with the difference that the head ani is TP-2.



- The arrival of the Coventry's group has been delayed by 5 seconds so that the ships will not fire on the remaining debris of the destroyer Nox upon arrival.



- Virgo wing's number of waves has been reduced from 4 to 3 for possible balance and RTB issues (the wing has high delay between waves values so the player might be forced to wait for the last wave at the end of the mission even if the other hostiles have been eliminated long before).





Episode 3 Mission 7:



- Briefing, Stage 1-2: Daskha (1) and Warlock (2) icons highlighted. Camera position changed (2) for variety purposes.



- Briefing, Stage 3: Alpha, Beta and Gamma icons added and highlighted. Camera position changed for the same reason posted above.



- Briefing, Stage 4: Warlock, Alpha, Beta and Gamma icons moved around Gemini 1 (which has been highlighted). The camera's position has been changed as well. Gemini 1 has been renamed "Gemini 1 - Admiral Russik".



- Pisces wing (composed of SF Dragon-class fighters) takes off from the GTD Warlock's fighterbay. This has been fixed so that the wing will take off from the SD Daskha.



- Scorpio wing's minimum delay between waves value increased by 6.



- No arrival message flag set for Cancer wing. The built-in message was in conflict with much more important messages.



- Alpha wing hasbeen moved away (1,5 clicks) for balance purposes. If the player chooses to fly a slow spacecraft, like the Ares, he will never manage to disarm the Daskha's beams in time.



- Arrival of the Rakshasa-class cruisers Parvati and Ragelam delayed by 23 seconds. The early arrival of those cruisers forced the player on the defensive, making a strike against the Comm Node impossible. Because of that, the Liliths were likely to arrive and turn the mission into a failure.



- The event "MBS - Alpha-Gamma-Beta Orders" will become true after 6 additional seconds to prevent conflicts between messages.



- "Shiv talk" event delayed by 4 seconds to prevent other conflicts and help with balance (the event is connected to the Daskha's actions).



- "Beam-free Rakshasas" event edited so that the Parvati and the Ragelam will begin firing their beam weapons after 15 additional seconds. Additionally, the weapons mounted on turrets 03 and 04 on both warships have been changed from "SRed" to "Shivan Turret Laser".



- Two events will ensure that Russik's transport, Gemini 1, will disappear from the escort list as soon as the Rakshasas arrive. It will reappear if the Comm Node and the cruisers are destroyed.



- The "Daskha Path" waypoint has been replaced (X: +600.0 meters, Y: +550.0 meters) to prevent the Warlock and the Daskha itself from being about to collide during the last part of the capship battle. In order to boost the effect, an event will effectively slow down the Daskha if the destroyers get too close. Even if the destroyers don't collide, anyway, they will slow down.



- The "Daskha Beams Offline" event will shut down anti-warship beams, only. Anti-spacecraft beams will continue to fire as usual.



- The Rakshasa-class cruiser "Parvati" has been renamed "Carcharoth". There was another Rakshasa with that name earlier in the campaign, so a change seemed appropriate.



- Both primary banks of Alpha and Gamma wings have been equipped with Kaysers for balance purposes.



- "Second Wave" and "More bombers" messages. The sender was Command even if the head ani was TP-1. Sender changed to <any wingman>.



- "Entering firing range", "Warlock 5" and "Launching Reinforcements" head anis changed from CM-2 to CM-4 because the messages come from the Warlock.



- "Two Ships" message ani changed from TP-4 to CM-2 because the message comes from Command. Same thing for the message "The Warlock Is Doomed", with the difference that the original ani was CM-1.



- "Alpha to Node" head ani missing and set to CM-4 because the message comes from the Warlock.



- Missing head anis in the following messages set to: CM-2 ("RTB Success" and "Node Later"), CM-4 ("Hurry to Node" and "Daskha Beams Fire").



- Taurus wing's built-in arrival message has been removed to prevent message conflicts.



- "Destroy node" event delayed by 6 seconds to prevent message conflicts. Iota wing's arrival, connected to this event, has been delayed by 4 seconds.



- "Warlock beam-free" event delayed by 13 additional seconds because the Warlock used to fire two BGreen beams in a timespan of 10 seconds, with unbelievable recharge rates.



- "friends" event delayed by 10 seconds to prevent possible message conflicts. The second message of the event list has been delayed by 20 seconds, and the arrival cue of the cruisers Ragelam and Carcharoth has been delayed accordingly. These changes seemed necessary for balance purposes.



- The GTCv Odin's arrival has been delayed by 8 seconds - the corvette used to jump in early, when the self destruction of Russik's transport was still going.



- The player will not be able to order the other wings to jump out nor he will be able to jump out with his own fighter unless the Warlock is destroyed. The only way to end the mission is to land on the Warlock, and the RTB directive have been edited accordingly. The "rtb" event has been edited to trigger a fade out effect (3000 milliseconds) instead of causing the mission to end instantly. Another message, which becomes true 3 seconds after rtb, will end the mission.



- Random wingman protection now used for Alpha, Beta and Gamma wings. This was necessary for obvious balance issues and messaging purposes.





CreditsWarzone



- RGB values reduced to 150 because they were too high (255).



- Leviticus music soundtrack selected to have some music during the cutscene. There used to be no music.