Sarna News: Bad 'Mechs - Icestorm

Editing Bronson's Horde

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 20: Line 20:
 
By 3068, the MRBC had officially declared Bronson's Horde a rogue unit and issued bounties for their capture or destruction.  Their wanted status was gained by their perpetration of a variety of offenses, including war crimes, attacks on civilian targets, and piracy.  According to the MRBC bulletin, they were last spotted on [[Epsilon Eridani]].<ref name="DotJp36">''Dawn of the Jihad'', p. 36, "MRBC ADVISORY: UPDATES TO ROGUE/WANTED LIST"</ref>  While contracted with the Word, the Horde  was stationed on Epsilon Eridani and Orestes before being deployed as a garrison unit on [[Tybalt]], where they trained both of the Protectorate Militia Divisions on planet, the [[1st Tybalt Protectorate Militia|First]] and the [[2nd Tybalt Protectorate Militia|Second Tybalt Protectorate Militia]].<ref name="JSTBDp110">''Jihad Secrets: The Blake Documents'', p. 110, "Word of Blake Mercenary Deployments"</ref>
 
By 3068, the MRBC had officially declared Bronson's Horde a rogue unit and issued bounties for their capture or destruction.  Their wanted status was gained by their perpetration of a variety of offenses, including war crimes, attacks on civilian targets, and piracy.  According to the MRBC bulletin, they were last spotted on [[Epsilon Eridani]].<ref name="DotJp36">''Dawn of the Jihad'', p. 36, "MRBC ADVISORY: UPDATES TO ROGUE/WANTED LIST"</ref>  While contracted with the Word, the Horde  was stationed on Epsilon Eridani and Orestes before being deployed as a garrison unit on [[Tybalt]], where they trained both of the Protectorate Militia Divisions on planet, the [[1st Tybalt Protectorate Militia|First]] and the [[2nd Tybalt Protectorate Militia|Second Tybalt Protectorate Militia]].<ref name="JSTBDp110">''Jihad Secrets: The Blake Documents'', p. 110, "Word of Blake Mercenary Deployments"</ref>
  
In [[3071]], Bronson's Horde was redeployed to [[New Avalon]] to assist the Word's forces in defensive operations there.  Though they had lost a majority of their experience and professional skills due to working in the Periphery for so long, the Horde managed to keep the defending Davion forces on their toes through a series of raids between the Second and Third Battles of New Avalon.<ref name=JTPNAp9>''Jihad Turning Points: New Avalon'', p. 9</ref>  They launched an abortive attack on the North Albion Observatory near Mount Mitre that was repulsed as soon as the [[First Davion Guards]] felled a single Horde 'Mech, but other raids succeeded in hampering the Guards' repair efforts.  Shortly thereafter, they supported another raid by the [[36th Division (Word of Blake)|Thirty-sixth Division]] that sought supplies in Hamilton City. The [[Fifth FedCom RCT]] repelled the Blakists but the Horde was able to escape with several hundred tons of supplies and repair equipment. <ref name=JTPNAp9/> Despite their initial success in their raids, the unit lost a great deal of their 'Mechs and material, and was tapped to accompany the [[44th Shadow Division|Forty-fourth Shadow Division]] when that unit landed to reinforce Blakist efforts during the Third Battle of New Avalon.  The heavy fighting they saw destroyed the mercenary command prior to the Word's eventual withdrawal from New Avalon. <ref name="jtpna7"/><ref name=MnM>''Masters and Minions: The StarCorps Dossiers'', p. 223, "Word of Blake Mercenary Employment"</ref>
+
In [[3071]], Bronson's Horde was redeployed to [[New Avalon]] to assist the Word's forces in defensive operations there.  Though they had lost a majority of their experience and professional skills due to working in the Periphery for so long, the Horde managed to keep the defending Davion forces on their toes through a series of raids between the Second and Third Battles of New Avalon.<ref name=JTPNAp9>''Jihad Turning Points: New Avalon'', p. 9</ref>  They launched an abortive attack on the North Albion Observatory near Mount Mitre that was repulsed as soon as the [[First Davion Guards]] felled a single Horde 'Mech, but other raids succeeded in hampering the Guards' repair efforts.  Shortly thereafter, they supported another raid by the [[36th Division (Word of Blake)|Thirty-sixth Division]] that sought supplies in Hamilton City. The [[Fifth FedCom RCT]] repelled the Blakists but the Horde was able to escape with several hundred tons of supplies and repair equipment. <ref name=JTPNAp9/> Despite their initial success in their raids, the unit lost a great deal of their 'Mechs and material, and was tapped to accompany the [[44th Shadow Division|Forty-fourth Shadow Division]] when that unit landed to reinforce Blakist efforts during the Third Battle of New Avalon.  The heavy fighting they saw destroyed the mercenary command prior to the Fourty-forth's eventual withdrawal from New Avalon. <ref name="jtpna7"/><ref name=MnM>''Masters and Minions: The StarCorps Dossiers'', p. 223, "Word of Blake Mercenary Employment"</ref>
  
 
==Officers==
 
==Officers==

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}}

Template used on this page: