Difference between revisions of "Journey of a Thousand Miles"

From FreeSpace Wiki
Jump to: navigation, search
m (Background: Consistency check...)
m (Background: Some minor corrections...)
Line 9: Line 9:
 
----
 
----
 
==Background==
 
==Background==
The ''Duke'' was deployed back to Delta Serpentis in order to re-establish contact with Command. As foreshadowed earlier in the campaign, the 14th Battlegroup has been cut off from the GTVA since its arrival in Sol. This previously minor technical problem now appears to be a symptom of something more. With the ''Duke'' now heading towards [[Ross 128]] and unresponsive to hails, it and its crew as considered to have gone rogue.
+
The ''Duke'' was deployed back to Delta Serpentis in order to re-establish contact with Command. As mentioned earlier in the campaign, the 14th Battlegroup has been cut off from the GTVA since its arrival in Sol. This previously minor technical problem now appears to be a symptom of something more. With the ''Duke'' now heading towards [[Ross 128]] and unresponsive to hails, it and its crew are considered to have gone rogue.
  
You, Taylor and Corey are now tasked with apprehending the ''Duke'', or following it into Ross 128 if they fail to do so before it jumps.
+
You, Taylor and Corey are now tasked with apprehending the ''Duke'', or following it into Ross 128 if you fail to do so before it jumps.
  
 
==Walkthrough==
 
==Walkthrough==

Revision as of 07:13, 29 August 2011

Previous Mission


Campaign Walkthrough Next Mission



MISSION 5

Fighter squadron: 222nd Nightwolves

Description: Samuel Bei and Alpha wing pursue the GTC Duke.


Background

The Duke was deployed back to Delta Serpentis in order to re-establish contact with Command. As mentioned earlier in the campaign, the 14th Battlegroup has been cut off from the GTVA since its arrival in Sol. This previously minor technical problem now appears to be a symptom of something more. With the Duke now heading towards Ross 128 and unresponsive to hails, it and its crew are considered to have gone rogue.

You, Taylor and Corey are now tasked with apprehending the Duke, or following it into Ross 128 if you fail to do so before it jumps.

Walkthrough

You start off in this mission several kilometres away from the Duke, which is nearing the Ross 128 jump node. As you order the Duke to cut engine power and stand down, the Duke sends out a garbled and unintelligible transmission before turning hostile. Orestes control gives the order to destroy the Duke's engines. However, Shivan fighters will jump in and attempt to distract you from taking out the Duke's engines. Eventually, the Duke will reach the jump node and jump out though the node. Follow it through.

Notes

  • You cannot jump out unless you are within 500 metres of the Ross 128 jump node. If you are already within 500 metres of the jump node, you will not be able to jump out if you are more than 700 metres away from it.
  • The Duke will always jump out, and a scripted mission event will force the Duke to activate its jump drives when its engine subsystem falls below 36% integrity.

Total number of forces

Forces involved
Belligerents
  • GTC Duke
Ships
Strikecraft
  • 3 GTF Aurora (*)
    • Alpha 1
      • Bei
    • Alpha 2
      • Corey
    • Alpha 3
      • Taylor
Casualties

(*) May be replaced with the GTF Hercules Mark II, GTF Perseus and/or GTF Myrmidon