View Thread
|
Taste of Mayhem - AAR
|
|
| zenprime |
Posted on 11-10-2005 13:25
|
|
Posts: 105 Joined: September 02 2005 |
Game Settings PDS: Version 7.0 release 1 Map: Dust to Naught LAN Game, 2 vs. 2 HGN TF56 (Human, Positions 1 and 2) VGR TF22 (Standard AI, Positions 3 and 4) AAR Background HGN TF 56 deployed under operational command of the Hiigaran Navy?s 7th Fleet to the edge of confirmed Cush territory for patrol and training exercises. The Fereration of Cush?s borders have been largerly unguarded since the Invasion and it is the objective of the 7th Fleet to establish a strong Hiigaran military presence and confirmed hold of these contested systems. TF 56 was divided into two separate forces for exercises, the Blue team under the command of Commander W. Joc?kim Reliuus, the Red team under the command of Vice Admiral Mune Asam. Each based around respective shipyards. The Focus of this AAR is the efforts of Vice Admiral Asam?s forces. AAR Forward Blue scouts identified a large Vaygr resourcing operation insystem encroaching on the Federation of Cush?s boarders. Red forces prepared a small MCG to defend farthest outbound resourceing operations, designated point Kappa, and stepped up production on heavy combants. Blue forces already had a strike force within range of the enemy and began a strike against the Vaygr resourcers. Vaygr super-capital class signatures were detected under heavy ECM by a to be proceeding to point Kappa, and a second taskforce based around the Supermoniter, Red Star and the auxiliary escort carrier, Gawl-Gaju, were dispatched to the projected engagement zone. Prior to reaching point Kappa, the Vaygr forces stopped their advance and began to set up operations. Long range scouts discovered that the Vaygr forces were not composed of warships but two carriers and a second shipyard with light escorts. Further analysis revealed one of the carriers to be a light battle carrier. The MCG was launched to tie up the carrier and light battle carrier while Red Star and Gawl-Gaju dispatched the second shipyard. An advance unit from the first Vaygr shipyard intercepted the MCG before it could close with the Carriers and followed it into the theater of engagement of the light battle carrier. Blue forces were summarily engaged at this time. Do to the increased Vaygr presence and being unable to withdraw from the battle, Red Star and Gawl-Gaju altered course to flank the forces occupying the MCG. Gawl-Gaju and her escorts consisting of two Cazadors, one Lavi flight and one Gladius-A flight moved up the Vaygr force's port side, while Red Star began shelling at long range. Red Forces? Shipyard began full production of Fleet Cruisers to supplement Red Star?s dwindling escort forces. Red Star pressed deeper into the engagement, passing Gawl-Gaju who swung around to cover the Supermoniter?s aft flank. With reserves from the second enemy shipyard, the MCG and Red Star?s taskforce were quickly encircled. This effort great reduced the maneuvering ability of all ships in theater, though their proximity to the enemy allowed them to contain the Vaygr forward rescourcing. Gawl-Gaju attempted a tactical withdrawal from the field, but was destroyed by fresh Vaygr reinforcements. Unbeknown at the time, Gawl-Gaju?s withdraw was not precipitated by damage, but the results of a Vaygr strike-virus which had locked out the crew and begun to spread through NCW links. Gawl-Gaju?s crew shut down all transmitters though unfortunately the strike-virus was transmitted to command through the emergency final log dump and shortly began infection of all Red systems. Higher links to Blue Forces were shut down, and orders were issued before all ships switched to autistic mode to prevent further spread and remain combat worthy while command rebuilt the battle net. (Read: zenprime had to go walk his dogs.) Eight minutes thirty seconds later, command reestablished the Red Forces Battle net and spread antiviral packages to all ships. Red Star and the majority of the MCG were lost during the blackout, though the battle had progressed to such a point were victory was a Vaygr improbability. Shipyard production continued under autistic mode and completed a complement of Fleet Cruisers and a second escort carrier, Honor of Gawl. The vast majority of the second enemy shipyard?s forces were out of action but still functioning. In theater assets were regrouped and reorganized under the command of a Linebacker Flotilla Leader and were tasked with the destruction of the shipyard. Fleet Cruisers were sent to destroy remaining Vaygr capital-class assets, forming a wedge against fire from strike craft. A second LirrHra Light Cruiser was procured by way of hyperspace and directed to fly high escort for the Fleet Cruiser strikegroup. Resourcing operations during the command blackout resulted in a vast excess, expediting the construction of a Deliverance class Battle Carrier, Lavinia. She was ordered to proceed to the site of the second Vaygr carrier and take command of operations while constructing a wing of Khopesh II for escort. Second Light Cruiser was pinned between enemy shipyard and carriers. Vaygr reinforcements from the first shipyard occupied the forces of the Linebacker group. The Light Cruiser was a loss, but with Vaygr weapons trained on her, Fleet Cruisers were able to strike targets with impunity. Second Shipyard and Carriers lost structural integrity quickly and were destroyed. Honor of Gawl and her escorts procceded to aid Blue forces in destruction of the first shipyard. She arrived on the scene in time to watch the first shipyard explode and assist in mop-up op. Lavinia?s escort wing discovered a Vaygr carrier at the edge of the system, preparing for escape. Khopeshes moved in to disable the enemy carrier?s engines while Lavinia diverted to aid in the destruction of a Vaygr Sorceress III. All insystem Vaygr were assets destroyed. ![]() ![]() Bring it on. I've mastered multiple forms of Pink! [small]Zenprime is dead. Well no |
|
|
|
| Jump to Forum |











