Editing 1001st Adder Sentinels (Clan Star Adder)

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 1: Line 1:
{{infoBoxMilitaryCommand
+
{{infoBoxStateUnit
| image = [[Image:Clan Star Adder.jpg|190px]]
+
| image   = [[Image:Clan Star Adder.jpg|190px]]
| Designation = 1001st Adder Sentinels
+
| nickname = None
| Formed =
+
| parent formation = [[Mu Provisional Galaxy (Clan Star Adder)|Mu Provisional Galaxy]]
| Disbanded =
+
| formed  = 3059
| Previous Designation =
+
| year    = 3067
| Nickname =
+
| unitname = 1001st Adder Sentinels
| Affiliation = [[Clan Star Adder]]
 
| Parent Command = [[Mu Provisional Galaxy (Clan Star Adder)|Mu Provisional Galaxy]]
 
| Sub-Command =  
 
 
}}
 
}}
  
Line 14: Line 11:
 
In [[3059]] the '''1001st Adder Sentinels''' was formed using personnel that were former [[Clan Burrock]] warriors. This Cluster was then assigned to Mu Galaxy to bolster losses incurred in the Burrock Absorption. It was first stationed on [[Brim]] alongside the [[152nd Adder Sentinels (Clan Star Adder)|152nd Sentinels]]. The rest of Mu Galaxy made a concerted effort to incorporate the new cluster into the Clan. <ref name=FM:CrCp128>''Field Manual: Crusader Clans'', p. 128, "1001st Adder Sentinels"</ref>
 
In [[3059]] the '''1001st Adder Sentinels''' was formed using personnel that were former [[Clan Burrock]] warriors. This Cluster was then assigned to Mu Galaxy to bolster losses incurred in the Burrock Absorption. It was first stationed on [[Brim]] alongside the [[152nd Adder Sentinels (Clan Star Adder)|152nd Sentinels]]. The rest of Mu Galaxy made a concerted effort to incorporate the new cluster into the Clan. <ref name=FM:CrCp128>''Field Manual: Crusader Clans'', p. 128, "1001st Adder Sentinels"</ref>
  
By [[3067]] the Sentinels had relocated to a garrison post on [[Dagda (Clan System)|Dagda]].<ref name=FM:Up74>''Field Manual: Updated'', p. 74, "Crusader Clans TO&E"</ref> The warriors of the Cluster had become uneasy over the years as the customs and traditions of their former Clan were seemingly erased, but the provisional of new [[Burrock (BattleMech)|Burrock]] BattleMechs in 3066 helped ease this tension. <ref name=FM:Up51>''Field Manual: Updated'', p. 51</ref>
+
By [[3067]] the Sentinels had relocated to a garrison post on [[Dagda (Clan)|Dagda]].<ref name=FM:Up74>''Field Manual: Updated'', p. 74, "Crusader Clans TO&E"</ref> The warriors of the Cluster had become uneasy over the years as the customs and traditions of their former Clan were seemingly erased, however the provisional of new [[Burrock]] BattleMechs in 3066 help ease this tension. <ref name=FM:Up51>''Field Manual: Updated'', p. 51</ref>
  
 
==Officers==
 
==Officers==
Line 51: Line 48:
 
'''1001st Adder Sentinels''' (Green) at 30% full strength <ref name=WoR169/>
 
'''1001st Adder Sentinels''' (Green) at 30% full strength <ref name=WoR169/>
 
* CO: Star Colonel Ivan Earle
 
* CO: Star Colonel Ivan Earle
 
 
==References==
 
==References==
 
<references />
 
<references />

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: