Editing 1st Canopian Brigade
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 11:
Line 11: | Sub-Command = | Sub-Command = }} }} + + The '''1st Canopian Brigade''' is an independent BattleMech regiment, which was raised by colonists in the [[Magistracy of Canopus]]. The '''1st Canopian Brigade''' is an independent BattleMech regiment, which was raised by colonists in the [[Magistracy of Canopus]]. ==History== ==History== ===Formation=== ===Formation=== − The Brigade's origins can be traced to [[Addasar]], a colony world in the Magistracy of Canopus. The world was never a priority for the Magistracy's armed forces to permanently station a force on planet. The colony world, still in its settlement stages needed more protection than the MAF could provide. A local farmer [[Felicia Joppa]], advocated the colony hire lone MechWarriors to help form a protective unit on planet from raiders. This ad hoc unit of loners successfully repelled pirate raids, justifying Joppa's view of the situation. Thus began the unit's true formation on world, with word of other local colonies worlds raising their own homebrew units.<ref name=FMPp44>''Field Manual: Periphery'', p. 44: "1st Canopian Brigade Unit Profile"</ref> + The Brigade's origins can be traced to [[Addasar]], a colony world in the Magistracy of Canopus. The world was never a priority for the Magistracy's armed forces to permanently station a force on planet. The colony world, still in its settlement stages needed more protection than the MAF could provide. A local farmer [[Felicia Joppa]], advocated the colony hire lone MechWarriors to help form a protective unit on planet from raiders. This ad hoc unit of loners successfully repelled pirate raids, justifying Joppa's view of the situation. Thus began the unit's true formation on world, with word of other local colonies worlds raising their own homebrew units.<ref name=FMPp44>''Field Manual: Periphery'', p. 44, "1st Canopian Brigade Unit Profile"</ref> ===Survival and Recognition=== ===Survival and Recognition=== − As the unit became larger, Joppa became its commanding officer despite having no formal military training. The unit suffered growth problems, due from lack of discipline and death of several of its pilots. Joppa's personal charisma and forceful personality was all that held the unit together. The Magistracy government soon became aware of the young unit's existence and struggle to survive. Magestrix [[Emma Centrella]] and the MAF arranged a deal to build up the unit that was similar to arrangement with then then expanded [[Magistracy Cavaliers]]. Two of its battalions would be made available for use by the MAF, while a single battalion would always be retained on planet under world's control.<ref>''Field Manual: Periphery'', pp. 39, 41: "1st Canopian Brigade"</ref> + As the unit became larger, Joppa became its commanding officer despite having no formal military training. The unit suffered growth problems, due from lack of discipline and death of several of its pilots. Joppa's personal charisma and forceful personality was all that held the unit together. The Magistracy government soon became aware of the young unit's existence and struggle to survive. Magestrix [[Emma Centrella]] and the MAF arranged a deal to build up the unit that was similar to arrangement with then then expanded [[Magistracy Cavaliers]]. Two of its battalions would be made available for use by the MAF, while a single battalion would always be retained on planet under world's control.<ref>''Field Manual: Periphery'', pp. 39, 41, "1st Canopian Brigade"</ref> Despite it becoming a frontline unit by [[3064]], it is not considered reliable with exception of the units commanding officer. Equipment utilized by the unit was of Succession War grade, with little in way of upgraded technology. The MAF High Command is concerned with the unit's response if Colonel Joppa should be replaced. The MAF high Command has not released or assigned support units such as armor and aerospace fighters to Brigade.<ref name=FMPp44/> Despite it becoming a frontline unit by [[3064]], it is not considered reliable with exception of the units commanding officer. Equipment utilized by the unit was of Succession War grade, with little in way of upgraded technology. The MAF High Command is concerned with the unit's response if Colonel Joppa should be replaced. The MAF high Command has not released or assigned support units such as armor and aerospace fighters to Brigade.<ref name=FMPp44/> − By [[3067]], the MAF continued to cycle the Brigade's battalions off [[Addasar]], never leaving the same battalion for its garrison duty. The practice help stimulate and gave the regiment's elements more experience. The practice is viewed as a way to combat the regiment's earlier problems of discipline and lack of experience.<ref>''Field Manual: Updates'', p. 190: "Unaffiliated MAF Units"</ref> Two of the unit's battalions were to be deployed to [[Luxen]] for their forward deployment, while retaining one back on its homeworld.<ref name=FMUp201>''Field Manual: Updates'', p. 201: "MAF Deployment Table - 3067"</ref> + By [[3067]], the MAF continued to cycle the Brigade's battalions off [[Addasar]], never leaving the same battalion for its garrison duty. The practice help stimulate and gave the regiment's elements more experience. The practice is viewed as a way to combat the regiment's earlier problems of discipline and lack of experience.<ref>''Field Manual: Update'', p. 190, "Unaffiliated MAF Units"</ref> Two of the unit's battalions were to be deployed to [[Luxen]] for their forward deployment, while retaining one back on its homeworld.<ref name=FMUp201>''Field Manual: Updates'', p. 201, "MAF Deployment Table - 3067"</ref> === The Jihad === === The Jihad === Line 28:
Line 30: === The Dark Age === === The Dark Age === − The First Canopian Brigade was deployed to the anti-spinward regions of the Magistracy at the turn of the thirty-second century as a punishment for the lax command structure the Brigade operated under and the Brigade's general unwillingness to follow orders from further up the chain. However, what the high command viewed as a punishment came to be seen by the Brigade as a gift; stationed far from Canopus IV, the Brigade could operate as it saw fit, redeploying as needed without needing to wait for permission or approval from the high command.<ref name="FM:3145p191">''Field Manual: 3145'', p. 191: "Independent MAF Commands"</ref> + The First Canopian Brigade was deployed to the anti-spinward regions of the Magistracy at the turn of the thirty-second century as a punishment for the lax command structure the Brigade operated under and the Brigade's general unwillingness to follow orders from further up the chain. However, what the high command viewed as a punishment came to be seen by the Brigade as a gift; stationed far from Canopus IV, the Brigade could operate as it saw fit, redeploying as needed without needing to wait for permission or approval from the high command.<ref name="FM:3145p191">''Field Manual: 3145'', p. 191, "Independent MAF Commands"</ref> The Brigade attacked [[Tellman's Mistake]] in [[3146]]. When the [[5th Rim Commonality Guards]] arrived to liberate the world, the First engaged in an offensive campaign that drove the Fifth into a retreat. While repositioning, the Fifth lost several other stragglers. This quickly led both forces to a similar size, and the conflict dragged into a stalemate.<ref>''Shattered Fortress'', p. 20</ref> The Brigade attacked [[Tellman's Mistake]] in [[3146]]. When the [[5th Rim Commonality Guards]] arrived to liberate the world, the First engaged in an offensive campaign that drove the Fifth into a retreat. While repositioning, the Fifth lost several other stragglers. This quickly led both forces to a similar size, and the conflict dragged into a stalemate.<ref>''Shattered Fortress'', p. 20</ref> Line 45:
Line 47: | [[Colonel]]||[[Felicia Joppa]]||[[3064]] - [[3067]]<ref name=FMPp44/><ref name=FMUp201/> | [[Colonel]]||[[Felicia Joppa]]||[[3064]] - [[3067]]<ref name=FMPp44/><ref name=FMUp201/> |- |- − | Colonel||[[Rei Fujimoto]]||[[3085]]<ref name=FM3085p149>''Field Manual: 3085'', p. 149: "MAF Deployment Table - 3085"</ref> + | Colonel||[[Rei Fujimoto]]||[[3085]]<ref name=FM3085p149>''Field Manual: 3085'', p. 149, "MAF Deployment Table - 3085"</ref> |- |- − | Colonel||[[Ashley Gorman]]||[[3145]]<ref name=FM:3145p200>''Field Manual: 3145'', p. 200: "Unaffilated MAF Commands"</ref> + | Colonel||[[Ashley Gorman]]||[[3145]]<ref name=FM:3145p200>''Field Manual: 3145'', p. 200, "Unaffilated MAF Commands"</ref> |- |- |} |} Line 81:
Line 83: <div class="gamerules"> <div class="gamerules"> ===Game Notes=== ===Game Notes=== − While using Scenario rules, such as [[Force Specific Rules]] found in Field Manual: Periphery, the Brigade is given following abilities. + While using Scenario rules, such as [[Force Specific Rules]] found in Field Manual Periphery, the Brigade is given following abilities. − In a scenario, for each of the Brigade's BattleMechs not fielded on map, the controlling player receives cumulative +1 initiative bonus. Also, for every three 'Mechs not deployed, unit's to-hit modifier receives -1 to weapon attack rolls. These bonus only remain in effect as long as the reserve 'Mechs remain out of play.<ref>''Field Manual: Periphery'', p. 151: "Force-Specific Rules"</ref> + In a scenario, for each of the Brigade's BattleMechs not fielded on map, the controlling player receives cumulative +1 initiative bonus. Also, for every three 'Mechs not deployed, unit's to-hit modifier receives -1 to weapon attack rolls. These bonus only remain in effect as long as the reserve 'Mechs remain out of play.<ref>''Field Manual: Periphery'', p. 151, "Force-Specific Rules"</ref> </div> </div>
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 11: | Line 11: | ||
| Sub-Command = | | Sub-Command = | ||
}} | }} | ||
| + | |||
| + | |||
The '''1st Canopian Brigade''' is an independent BattleMech regiment, which was raised by colonists in the [[Magistracy of Canopus]]. | The '''1st Canopian Brigade''' is an independent BattleMech regiment, which was raised by colonists in the [[Magistracy of Canopus]]. | ||
==History== | ==History== | ||
===Formation=== | ===Formation=== | ||
| − | The Brigade's origins can be traced to [[Addasar]], a colony world in the Magistracy of Canopus. The world was never a priority for the Magistracy's armed forces to permanently station a force on planet. The colony world, still in its settlement stages needed more protection than the MAF could provide. A local farmer [[Felicia Joppa]], advocated the colony hire lone MechWarriors to help form a protective unit on planet from raiders. This ad hoc unit of loners successfully repelled pirate raids, justifying Joppa's view of the situation. Thus began the unit's true formation on world, with word of other local colonies worlds raising their own homebrew units.<ref name=FMPp44>''Field Manual: Periphery'', p. 44 | + | The Brigade's origins can be traced to [[Addasar]], a colony world in the Magistracy of Canopus. The world was never a priority for the Magistracy's armed forces to permanently station a force on planet. The colony world, still in its settlement stages needed more protection than the MAF could provide. A local farmer [[Felicia Joppa]], advocated the colony hire lone MechWarriors to help form a protective unit on planet from raiders. This ad hoc unit of loners successfully repelled pirate raids, justifying Joppa's view of the situation. Thus began the unit's true formation on world, with word of other local colonies worlds raising their own homebrew units.<ref name=FMPp44>''Field Manual: Periphery'', p. 44, "1st Canopian Brigade Unit Profile"</ref> |
===Survival and Recognition=== | ===Survival and Recognition=== | ||
| − | As the unit became larger, Joppa became its commanding officer despite having no formal military training. The unit suffered growth problems, due from lack of discipline and death of several of its pilots. Joppa's personal charisma and forceful personality was all that held the unit together. The Magistracy government soon became aware of the young unit's existence and struggle to survive. Magestrix [[Emma Centrella]] and the MAF arranged a deal to build up the unit that was similar to arrangement with then then expanded [[Magistracy Cavaliers]]. Two of its battalions would be made available for use by the MAF, while a single battalion would always be retained on planet under world's control.<ref>''Field Manual: Periphery'', pp. 39, 41 | + | As the unit became larger, Joppa became its commanding officer despite having no formal military training. The unit suffered growth problems, due from lack of discipline and death of several of its pilots. Joppa's personal charisma and forceful personality was all that held the unit together. The Magistracy government soon became aware of the young unit's existence and struggle to survive. Magestrix [[Emma Centrella]] and the MAF arranged a deal to build up the unit that was similar to arrangement with then then expanded [[Magistracy Cavaliers]]. Two of its battalions would be made available for use by the MAF, while a single battalion would always be retained on planet under world's control.<ref>''Field Manual: Periphery'', pp. 39, 41, "1st Canopian Brigade"</ref> |
Despite it becoming a frontline unit by [[3064]], it is not considered reliable with exception of the units commanding officer. Equipment utilized by the unit was of Succession War grade, with little in way of upgraded technology. The MAF High Command is concerned with the unit's response if Colonel Joppa should be replaced. The MAF high Command has not released or assigned support units such as armor and aerospace fighters to Brigade.<ref name=FMPp44/> | Despite it becoming a frontline unit by [[3064]], it is not considered reliable with exception of the units commanding officer. Equipment utilized by the unit was of Succession War grade, with little in way of upgraded technology. The MAF High Command is concerned with the unit's response if Colonel Joppa should be replaced. The MAF high Command has not released or assigned support units such as armor and aerospace fighters to Brigade.<ref name=FMPp44/> | ||
| − | By [[3067]], the MAF continued to cycle the Brigade's battalions off [[Addasar]], never leaving the same battalion for its garrison duty. The practice help stimulate and gave the regiment's elements more experience. The practice is viewed as a way to combat the regiment's earlier problems of discipline and lack of experience.<ref>''Field Manual: | + | By [[3067]], the MAF continued to cycle the Brigade's battalions off [[Addasar]], never leaving the same battalion for its garrison duty. The practice help stimulate and gave the regiment's elements more experience. The practice is viewed as a way to combat the regiment's earlier problems of discipline and lack of experience.<ref>''Field Manual: Update'', p. 190, "Unaffiliated MAF Units"</ref> Two of the unit's battalions were to be deployed to [[Luxen]] for their forward deployment, while retaining one back on its homeworld.<ref name=FMUp201>''Field Manual: Updates'', p. 201, "MAF Deployment Table - 3067"</ref> |
=== The Jihad === | === The Jihad === | ||
| Line 28: | Line 30: | ||
=== The Dark Age === | === The Dark Age === | ||
| − | The First Canopian Brigade was deployed to the anti-spinward regions of the Magistracy at the turn of the thirty-second century as a punishment for the lax command structure the Brigade operated under and the Brigade's general unwillingness to follow orders from further up the chain. However, what the high command viewed as a punishment came to be seen by the Brigade as a gift; stationed far from Canopus IV, the Brigade could operate as it saw fit, redeploying as needed without needing to wait for permission or approval from the high command.<ref name="FM:3145p191">''Field Manual: 3145'', p. 191 | + | The First Canopian Brigade was deployed to the anti-spinward regions of the Magistracy at the turn of the thirty-second century as a punishment for the lax command structure the Brigade operated under and the Brigade's general unwillingness to follow orders from further up the chain. However, what the high command viewed as a punishment came to be seen by the Brigade as a gift; stationed far from Canopus IV, the Brigade could operate as it saw fit, redeploying as needed without needing to wait for permission or approval from the high command.<ref name="FM:3145p191">''Field Manual: 3145'', p. 191, "Independent MAF Commands"</ref> |
The Brigade attacked [[Tellman's Mistake]] in [[3146]]. When the [[5th Rim Commonality Guards]] arrived to liberate the world, the First engaged in an offensive campaign that drove the Fifth into a retreat. While repositioning, the Fifth lost several other stragglers. This quickly led both forces to a similar size, and the conflict dragged into a stalemate.<ref>''Shattered Fortress'', p. 20</ref> | The Brigade attacked [[Tellman's Mistake]] in [[3146]]. When the [[5th Rim Commonality Guards]] arrived to liberate the world, the First engaged in an offensive campaign that drove the Fifth into a retreat. While repositioning, the Fifth lost several other stragglers. This quickly led both forces to a similar size, and the conflict dragged into a stalemate.<ref>''Shattered Fortress'', p. 20</ref> | ||
| Line 45: | Line 47: | ||
| [[Colonel]]||[[Felicia Joppa]]||[[3064]] - [[3067]]<ref name=FMPp44/><ref name=FMUp201/> | | [[Colonel]]||[[Felicia Joppa]]||[[3064]] - [[3067]]<ref name=FMPp44/><ref name=FMUp201/> | ||
|- | |- | ||
| − | | Colonel||[[Rei Fujimoto]]||[[3085]]<ref name=FM3085p149>''Field Manual: 3085'', p. 149 | + | | Colonel||[[Rei Fujimoto]]||[[3085]]<ref name=FM3085p149>''Field Manual: 3085'', p. 149, "MAF Deployment Table - 3085"</ref> |
|- | |- | ||
| − | | Colonel||[[Ashley Gorman]]||[[3145]]<ref name=FM:3145p200>''Field Manual: 3145'', p. 200 | + | | Colonel||[[Ashley Gorman]]||[[3145]]<ref name=FM:3145p200>''Field Manual: 3145'', p. 200, "Unaffilated MAF Commands"</ref> |
|- | |- | ||
|} | |} | ||
| Line 81: | Line 83: | ||
<div class="gamerules"> | <div class="gamerules"> | ||
===Game Notes=== | ===Game Notes=== | ||
| − | While using Scenario rules, such as [[Force Specific Rules]] found in Field Manual | + | While using Scenario rules, such as [[Force Specific Rules]] found in Field Manual Periphery, the Brigade is given following abilities. |
| − | In a scenario, for each of the Brigade's BattleMechs not fielded on map, the controlling player receives cumulative +1 initiative bonus. Also, for every three 'Mechs not deployed, unit's to-hit modifier receives -1 to weapon attack rolls. These bonus only remain in effect as long as the reserve 'Mechs remain out of play.<ref>''Field Manual: Periphery'', p. 151 | + | In a scenario, for each of the Brigade's BattleMechs not fielded on map, the controlling player receives cumulative +1 initiative bonus. Also, for every three 'Mechs not deployed, unit's to-hit modifier receives -1 to weapon attack rolls. These bonus only remain in effect as long as the reserve 'Mechs remain out of play.<ref>''Field Manual: Periphery'', p. 151, "Force-Specific Rules"</ref> |
</div> | </div> | ||