Difference between revisions of "Wounded Prey"
| (10 intermediate revisions by 5 users not shown) | |||
| 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 you, Taylor and Corey, pursuing. |
| + | |||
| + | During the transit, you write another entry into your 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. You also note power fluctuations from the ''Duke'', which you believe to be a symptom of imminent reactor failure. You begin to wonder if the crew of the ''Duke'' deserted out of insanity rather than insubordination and admit that you are now beginning to feel that the 14th Battlegroup is in the wrong universe. | ||
==Walkthrough== | ==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 you 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''' | ||
| − | + | ==Videos== | |
| − | + | ===QuantumDelta=== | |
| − | + | <br><videoflash>7zH4GTlEfKw</videoflash><br> | |
| − | + | Note: this mission starts at 10 mins 53 secs | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
[[Category: Blue Planet]] | [[Category: Blue Planet]] | ||
Latest revision as of 10:23, 6 December 2012
| 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 you, Taylor and Corey, pursuing.
During the transit, you write another entry into your 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. You also note power fluctuations from the Duke, which you believe to be a symptom of imminent reactor failure. You begin to wonder if the crew of the Duke deserted out of insanity rather than insubordination and admit that you are now beginning to feel that the 14th Battlegroup 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 you 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
Videos
QuantumDelta
Note: this mission starts at 10 mins 53 secs
