Difference between revisions of "Wounded Prey"
m |
(JEEEEEEEEEEEEEEEEEEEEEEGS) |
||
| Line 3: | Line 3: | ||
'''MISSION 7''' | '''MISSION 7''' | ||
| − | '''Fighter squadron:''' [[222nd Nightwolves]] | + | '''Fighter squadron:''' [[222nd Nightwolves]] |
| − | '''Description: | + | '''Description:''' The pursuit of the GTC Duke reaches its conclusion. |
---- | ---- | ||
==Background== | ==Background== | ||
| − | The ''Duke'' | + | The GTC ''Duke'' entered the [[Laramis]] jump node and fetched up in the N362 system, with Alpha Wing of the 222nd Nightwolves, comprising Bei, Taylor and Corey, pursuing. |
| + | |||
| + | During the transit, Bei writes another entry into his personal log, questioning the ''Duke'''s motives for entering N362 and reflecting once again on the absence of GTVA Command as well as the strangeness of seeing the GTD ''Minnow'' and Shivans in star systems where they should not be. Bei also notes power fluctuations from the ''Duke'', which he believes to be a symptom of imminent reactor failure. He begins to wonder if the crew of the ''Duke'' deserted out of insanity rather than insubordination and admits that he is now beginning to feel that the 14th Battle Group is in the wrong universe. | ||
==Walkthrough== | ==Walkthrough== | ||
| − | Approach the ''Duke'' and press Alt-A. If this keypress does nothing, check your key bindings under Options, and simply press whatever is bound to the 'Autopilot' command. | + | This is a Red Alert mission, so your missile count and any damage incurred from the previous mission will carry over. |
| + | |||
| + | The ''Duke'' strained its jump drives to the limit in its mad dash through [[Delta Serpentis]], [[Ross 128]], and [[Laramis]]. The ship now lies disabled. The jump into N362 scattered Alpha wing, however, leaving Samuel Bei with the unpleasant duty of boarding the ship alone and ascertaining the status of its crew. | ||
| + | |||
| + | Approach the ''Duke'' and press Alt-A. If this keypress does nothing, check your key bindings under Options, and simply press whatever is bound to the 'Autopilot' command. The only other way to move further into the campaign is to kill yourself five times. | ||
==Notes== | ==Notes== | ||
| − | Many Blue Planet players entered this mission with alternate key bindings and found themselves briefly stymied by the directive to 'press Alt-A' to board the Duke | + | * Many Blue Planet players entered this mission with alternate key bindings and found themselves briefly stymied by the directive to 'press Alt-A' to board the Duke. |
| − | |||
| − | |||
==Total number of forces== | ==Total number of forces== | ||
| + | {{total_numbers_2 | ||
| + | |belligerent_1 =[[Galactic Terran-Vasudan Alliance|GTVA]] | ||
| + | |belligerent_2 =GTC ''Duke'' | ||
| + | |ship_1 = | ||
| + | |ship_2 = | ||
| + | * 1 [[GTC Hyperion|GTC ''Hyperion'']] | ||
| + | ** ''Duke'' | ||
| + | |strikecraft_1 = | ||
| + | * 1 [[GTF Perseus|GTF ''Perseus'']] (*)(#) | ||
| + | ** ''Alpha 1'' | ||
| − | + | * 1 [[Spacesuit]] | |
| − | + | ** ''Spacesuit 2'' | |
| − | + | |strikecraft_2 = | |
| − | + | |casualties_1 = | |
| − | + | |casualties_2 = | |
| − | + | }} | |
| − | + | (*) '''Actual ship type is based on previous mission selection'''<br> | |
| − | + | (#) '''Ship ordnance and damage values are carried over from previous mission''' | |
| − | |||
| − | |||
| − | | | ||
| − | | | ||
| − | | | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
[[Category: Blue Planet]] | [[Category: Blue Planet]] | ||
Revision as of 10:03, 14 August 2010
| Previous Mission
|
Campaign Walkthrough | Next Mission
|
MISSION 7
Fighter squadron: 222nd Nightwolves
Description: The pursuit of the GTC Duke reaches its conclusion.
Background
The GTC Duke entered the Laramis jump node and fetched up in the N362 system, with Alpha Wing of the 222nd Nightwolves, comprising Bei, Taylor and Corey, pursuing.
During the transit, Bei writes another entry into his personal log, questioning the Duke's motives for entering N362 and reflecting once again on the absence of GTVA Command as well as the strangeness of seeing the GTD Minnow and Shivans in star systems where they should not be. Bei also notes power fluctuations from the Duke, which he believes to be a symptom of imminent reactor failure. He begins to wonder if the crew of the Duke deserted out of insanity rather than insubordination and admits that he is now beginning to feel that the 14th Battle Group is in the wrong universe.
Walkthrough
This is a Red Alert mission, so your missile count and any damage incurred from the previous mission will carry over.
The Duke strained its jump drives to the limit in its mad dash through Delta Serpentis, Ross 128, and Laramis. The ship now lies disabled. The jump into N362 scattered Alpha wing, however, leaving Samuel Bei with the unpleasant duty of boarding the ship alone and ascertaining the status of its crew.
Approach the Duke and press Alt-A. If this keypress does nothing, check your key bindings under Options, and simply press whatever is bound to the 'Autopilot' command. The only other way to move further into the campaign is to kill yourself five times.
Notes
- Many Blue Planet players entered this mission with alternate key bindings and found themselves briefly stymied by the directive to 'press Alt-A' to board the Duke.
Total number of forces
| Forces involved | |
| Belligerents | |
| |
| Ships | |
| |
| Strikecraft | |
|
|
(*) Actual ship type is based on previous mission selection
(#) Ship ordnance and damage values are carried over from previous mission
