Editing Mercer (DropShip class)

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.

Latest revision Your text
Line 37: Line 37:
  
 
==Description==
 
==Description==
[[Clan Steel Viper]] engineers developed the '''''Mercer'''''-class [[DropShip]] after their ejection from the [[Inner Sphere]] by [[Clan Jade Falcon]]. To show that they were still a force to be reckoned with, the Vipers planned an assault on their longtime enemies, [[Clan Snow Raven]]. Knowing the Ravens would challenge any landing attempts they made, the Viper Khans realized that they needed a heavily armed and well protected 'Mech transport. The Viper Khan's concern was simple: The massive naval forces of the Snow Ravens would rip through a standard fleet of ''[[Union-C]]'' DropShips, destroying 'Mech [[Trinary|Trinaries]] before they even hit the ground.<ref name=TRO3067-190>''Technical Readout: 3067,'' p. 190, "Mercer DropShip Profile"</ref>
+
[[Clan Steel Viper]] engineers developed the '''''Mercer'''''-class [[DropShip]] after their ejection from the [[Inner Sphere]] by [[Clan Jade Falcon]]. To show that they were still a force to be reckoned with, the Vipers planned an assault on their long-time enemies, [[Clan Snow Raven]]. Knowing the Ravens would challenge any landing attempts they made, the Viper Khans realized that they needed a heavily armed and well protected 'Mech transport. The Viper Khan's concern was simple: The massive naval forces of the Snow Ravens would rip through a standard fleet of ''[[Union-C]]'' DropShips, destroying 'Mech [[Trinary|Trinaries]] before they even hit the ground.<ref name=TRO3067-190>''Technical Readout: 3067,'' p. 190, "Mercer DropShip Profile"</ref>
  
 
With this in mind, the ''Mercer'' was developed to move a full Trinary into position{{cn}}, while maximizing the armament and protection mounted on the hull. Ultimately the 'Mech storage capacity was reduced to a single [[Binary]], but the armor protection mounted on the ''Mercer'' was maximized. In the Viper's attack on [[Lum]], the ''Mercer'' performed well, delivering its cargo of 'Mechs to the ground while still fighting off the Snow Raven forces. While ultimately unsuccessful, the assault on Lum disrupted production for nearly two months.<ref name=TRO3067-190/>  
 
With this in mind, the ''Mercer'' was developed to move a full Trinary into position{{cn}}, while maximizing the armament and protection mounted on the hull. Ultimately the 'Mech storage capacity was reduced to a single [[Binary]], but the armor protection mounted on the ''Mercer'' was maximized. In the Viper's attack on [[Lum]], the ''Mercer'' performed well, delivering its cargo of 'Mechs to the ground while still fighting off the Snow Raven forces. While ultimately unsuccessful, the assault on Lum disrupted production for nearly two months.<ref name=TRO3067-190/>  

Please note that all contributions to BattleTechWiki are considered to be released under the GNU FDL 1.2 (see BattleTechWiki:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

To edit this page, please answer the question that appears below (more info):

Cancel Editing help (opens in new window)

Advanced templates:

Editing: {{Merge}}   {{Moratorium}}   {{Otheruses| | | }}

Notices: {{NoEdit}}   {{Sign}}   {{Unsigned|name}}   {{Welcome}}

Administration: {{Essay}}   {{Policy}}   {{Procedure}}

This page is a member of 1 hidden category: