Editing Baron (WarShip 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 25:
Line 25: * 8x [[NAC/10]] * 8x [[NAC/10]] * 6x [[White Shark]] Launcher * 6x [[White Shark]] Launcher − | Armor = 256 tons [[Improved Ferro-Aluminum]] + | Armor = 256 tons of [[Improved Ferro-Aluminum]] | DropShip Capacity = 0 | DropShip Capacity = 0 | Crew = 233<ref name="TRO:3057Rp200"/> | Crew = 233<ref name="TRO:3057Rp200"/> Line 37:
Line 37: | Grav Decks = 1 x 65 meters diameter | Grav Decks = 1 x 65 meters diameter | Escape Pods/Life Boats = 38/13 | Escape Pods/Life Boats = 38/13 − | Heat Sinks = 1,100 [[Heat Sink|single]] + | Heat Sinks = 1,100 (single) | BV (1.0) = 34,661<ref name="TRO:3057Rp200"/> | BV (1.0) = 34,661<ref name="TRO:3057Rp200"/> | BV (2.0) = 27,692<ref name=JTPL-15>''Jihad Turning Points: Luthien'', p. 15: "''Baron'' [Destroyer]"</ref> | BV (2.0) = 27,692<ref name=JTPL-15>''Jihad Turning Points: Luthien'', p. 15: "''Baron'' [Destroyer]"</ref> Line 45:
Line 45: The '''''Baron'''''-class destroyer was a moderately effective design that suffered due to protracted development and construction.<ref name="TRO:3057Rp200">''Technical Readout: 3057 Revised'', p. 200: "Baron (Destroyer)"</ref> The '''''Baron'''''-class destroyer was a moderately effective design that suffered due to protracted development and construction.<ref name="TRO:3057Rp200">''Technical Readout: 3057 Revised'', p. 200: "Baron (Destroyer)"</ref> − With initial construction beginning in [[2515]] in the midst of a massive arms race intended to allow the [[Terran Hegemony]] to maintain its edge against the [[Great Houses]], flaws were discovered with the then-revolutionary [[Palenkov-Reese]] [[Interplanetary Drive System|interplanetary engines]] used by the ''Baron''. While the fault was correctable, it took two years and greatly reduced their performance, by which point naval design had marched steadily onward and the ''Baron''-class was considered out of date before the first ship had slipped its moorings in [[2520]]. In [[2582]] the [[Star League]] presented over half the constructed ''Barons'' to Star League member states; the remainder were retained by the [[Star League Defense Force]] and though it would see action in the [[Reunification War]], their performance was considered lackluster.<ref name="TRO:3057Rp200"/> The [[Federated Suns]] had five ''Barons'' lost or destroyed to the [[Taurian Concordat]] during the [[Case Amber|Case AMBER]] ambush at [[Tentativa]] alone.<ref name="H:RWp69">''Historical: Reunification War'', p. 69: "Battle for Tentativa"</ref> + With initial construction beginning in [[2515]] in the midst of a massive arms race intended to allow the [[Terran Hegemony]] to maintain its edge against the [[Great Houses]], flaws were discovered with the then-revolutionary [[Palenkov-Reese]] interplanetary engines used by the ''Baron''. While the fault was correctable, it took two years and greatly reduced their performance, by which point naval design had marched steadily onward and the ''Baron''-class was considered out of date before the first ship had slipped its moorings in [[2520]]. In [[2582]] the [[Star League]] presented over half the constructed ''Barons'' to Star League member states; the remainder were retained by the [[Star League Defense Force]] and though it would see action in the [[Reunification War]], their performance was considered lackluster.<ref name="TRO:3057Rp200"/> The [[Federated Suns]] had five ''Barons'' lost or destroyed to the [[Taurian Concordat]] during the [[Case Amber|Case AMBER]] ambush at [[Tentativa]] alone.<ref name="H:RWp69">''Historical: Reunification War'', p. 69: "Battle for Tentativa"</ref> The design's sole saving graces were its generously sized fuel bunkers and accommodations for thirty extra passengers, which caused many high-ranking Star League diplomats to select ships of the ''Baron''-class as heavily armed transports into high-risk areas, including the [[Periphery]]. However, by [[2720]], the [[SLDF]] had decommissioned and sold off the remaining ''Barons'' to the Great Houses;<ref name="TRO:3057Rp200"/> the [[Capellan Confederation]] kept three ''Barons'' in their active fleet until at least [[2765]]<ref name="FR:2765CCAFp5">''Field Report 2765: CCAF'', p. 5: "Guarding the Vault of Heaven"</ref> while the [[Draconis Combine]] was operating five<ref>[http://bg.battletech.com/forums/index.php/topic,35369.msg855464.html#msg855464 Official Errata Thread]</ref> the [[Federated Suns]] three<ref>''Field Report 2765: AFFS'', p. 6: "Naval Defense Doctrine"</ref> and the [[Lyran Commonwealth]] one at the same point in time.<ref name="FR2765:LCAFp5">''Field Report 2765: LCAF'', p. 5: "The Vacuum Fleet"</ref> The design's sole saving graces were its generously sized fuel bunkers and accommodations for thirty extra passengers, which caused many high-ranking Star League diplomats to select ships of the ''Baron''-class as heavily armed transports into high-risk areas, including the [[Periphery]]. However, by [[2720]], the [[SLDF]] had decommissioned and sold off the remaining ''Barons'' to the Great Houses;<ref name="TRO:3057Rp200"/> the [[Capellan Confederation]] kept three ''Barons'' in their active fleet until at least [[2765]]<ref name="FR:2765CCAFp5">''Field Report 2765: CCAF'', p. 5: "Guarding the Vault of Heaven"</ref> while the [[Draconis Combine]] was operating five<ref>[http://bg.battletech.com/forums/index.php/topic,35369.msg855464.html#msg855464 Official Errata Thread]</ref> the [[Federated Suns]] three<ref>''Field Report 2765: AFFS'', p. 6: "Naval Defense Doctrine"</ref> and the [[Lyran Commonwealth]] one at the same point in time.<ref name="FR2765:LCAFp5">''Field Report 2765: LCAF'', p. 5: "The Vacuum Fleet"</ref> − The [[Succession Wars (History)|Succession Wars]] would see even mothballed ''Barons'' restored to combat status; the last active ''Baron'' in the [[Inner Sphere]] was believed to have been the [[Draconis Combine]] destroyer DCS ''[[Yedo]]'' restored to active service and destroyed in [[2853]] in battle over [[Hesperus II]],<ref name="TRO:3057Rp200"/><ref>''Tactics of Desperation'', Part 1</ref> but at least one ''Baron'' would survive in a [[Clan]] naval cache until the [[Wars of Reaving]].<ref>''The Wars of Reaving'', pp. 112–113: "Constriction"</ref> In the buildup to the [[Jihad]], the [[Word of Blake]] would restore three ''Barons'' to working order, subsequently deploying them in various battles around the Inner Sphere, with the last being destroyed in [[3077]].<ref name="J:FRp128">''Jihad: Final Reckoning'', p. 128: "Word of Blake Naval Assets"</ref> + The [[Succession Wars (History)|Succession Wars]] would see even mothballed ''Barons'' restored to combat status; the last active ''Baron'' in the [[Inner Sphere]] was believed to have been the [[Draconis Combine]] destroyer DCS ''[[Yedo]]'' restored to active service and destroyed in [[2853]] in battle over [[Hesperus II]],<ref name="TRO:3057Rp200"/><ref>''Tactics of Desperation'', Part 1</ref> but at least one ''Baron'' would survive in a [[Clan]] naval cache until the [[Wars of Reaving]].<ref>''The Wars of Reaving'', pp. 112–113: "Constriction"</ref> In the buildup to the [[Jihad]] the [[Word of Blake]] would restore three ''Barons'' to working order, subsequently deploying them in various battles around the Inner Sphere, with the last being destroyed in [[3077]].<ref name="J:FRp128">''Jihad: Final Reckoning'', p. 128: "Word of Blake Naval Assets"</ref> ==Armament== ==Armament== − Mounting a large array of [[NL35]] capital Lasers, the ''Baron'' boasts impressive endurance on longer patrols, with six mounted in the nose, ten carried in each broadside with a further three directly aft. A mix of capital-grade [[autocannons]] and missile launchers provide support, with two [[NAC/10|NAC/10s]] and [[White Shark]] missile launchers in each forward angle, two more NAC/10s on each rear angle and two White Shark tubes directly rearward.<ref name="TRO:3057Rp200"/> + Mounting a large array of [[NL35]] capital Lasers, the ''Baron'' boasts impressive endurance on longer patrols, with six mounted in the nose, ten carried in each broadside with a further three directly aft. A mix of capital-grade [[autocannon]]s and missile launchers provide support, with two [[NAC/10]]s and [[White Shark]] missile launchers in each forward angle, two more NAC/10s on each rear angle and two White Shark tubes directly rearward.<ref name="TRO:3057Rp200"/> ==Cargo== ==Cargo==
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 25: | Line 25: | ||
* 8x [[NAC/10]] | * 8x [[NAC/10]] | ||
* 6x [[White Shark]] Launcher | * 6x [[White Shark]] Launcher | ||
| − | | Armor = 256 tons [[Improved Ferro-Aluminum]] | + | | Armor = 256 tons of [[Improved Ferro-Aluminum]] |
| DropShip Capacity = 0 | | DropShip Capacity = 0 | ||
| Crew = 233<ref name="TRO:3057Rp200"/> | | Crew = 233<ref name="TRO:3057Rp200"/> | ||
| Line 37: | Line 37: | ||
| Grav Decks = 1 x 65 meters diameter | | Grav Decks = 1 x 65 meters diameter | ||
| Escape Pods/Life Boats = 38/13 | | Escape Pods/Life Boats = 38/13 | ||
| − | | Heat Sinks = 1,100 | + | | Heat Sinks = 1,100 (single) |
| BV (1.0) = 34,661<ref name="TRO:3057Rp200"/> | | BV (1.0) = 34,661<ref name="TRO:3057Rp200"/> | ||
| BV (2.0) = 27,692<ref name=JTPL-15>''Jihad Turning Points: Luthien'', p. 15: "''Baron'' [Destroyer]"</ref> | | BV (2.0) = 27,692<ref name=JTPL-15>''Jihad Turning Points: Luthien'', p. 15: "''Baron'' [Destroyer]"</ref> | ||
| Line 45: | Line 45: | ||
The '''''Baron'''''-class destroyer was a moderately effective design that suffered due to protracted development and construction.<ref name="TRO:3057Rp200">''Technical Readout: 3057 Revised'', p. 200: "Baron (Destroyer)"</ref> | The '''''Baron'''''-class destroyer was a moderately effective design that suffered due to protracted development and construction.<ref name="TRO:3057Rp200">''Technical Readout: 3057 Revised'', p. 200: "Baron (Destroyer)"</ref> | ||
| − | With initial construction beginning in [[2515]] in the midst of a massive arms race intended to allow the [[Terran Hegemony]] to maintain its edge against the [[Great Houses]], flaws were discovered with the then-revolutionary [[Palenkov-Reese]] | + | With initial construction beginning in [[2515]] in the midst of a massive arms race intended to allow the [[Terran Hegemony]] to maintain its edge against the [[Great Houses]], flaws were discovered with the then-revolutionary [[Palenkov-Reese]] interplanetary engines used by the ''Baron''. While the fault was correctable, it took two years and greatly reduced their performance, by which point naval design had marched steadily onward and the ''Baron''-class was considered out of date before the first ship had slipped its moorings in [[2520]]. In [[2582]] the [[Star League]] presented over half the constructed ''Barons'' to Star League member states; the remainder were retained by the [[Star League Defense Force]] and though it would see action in the [[Reunification War]], their performance was considered lackluster.<ref name="TRO:3057Rp200"/> The [[Federated Suns]] had five ''Barons'' lost or destroyed to the [[Taurian Concordat]] during the [[Case Amber|Case AMBER]] ambush at [[Tentativa]] alone.<ref name="H:RWp69">''Historical: Reunification War'', p. 69: "Battle for Tentativa"</ref> |
The design's sole saving graces were its generously sized fuel bunkers and accommodations for thirty extra passengers, which caused many high-ranking Star League diplomats to select ships of the ''Baron''-class as heavily armed transports into high-risk areas, including the [[Periphery]]. However, by [[2720]], the [[SLDF]] had decommissioned and sold off the remaining ''Barons'' to the Great Houses;<ref name="TRO:3057Rp200"/> the [[Capellan Confederation]] kept three ''Barons'' in their active fleet until at least [[2765]]<ref name="FR:2765CCAFp5">''Field Report 2765: CCAF'', p. 5: "Guarding the Vault of Heaven"</ref> while the [[Draconis Combine]] was operating five<ref>[http://bg.battletech.com/forums/index.php/topic,35369.msg855464.html#msg855464 Official Errata Thread]</ref> the [[Federated Suns]] three<ref>''Field Report 2765: AFFS'', p. 6: "Naval Defense Doctrine"</ref> and the [[Lyran Commonwealth]] one at the same point in time.<ref name="FR2765:LCAFp5">''Field Report 2765: LCAF'', p. 5: "The Vacuum Fleet"</ref> | The design's sole saving graces were its generously sized fuel bunkers and accommodations for thirty extra passengers, which caused many high-ranking Star League diplomats to select ships of the ''Baron''-class as heavily armed transports into high-risk areas, including the [[Periphery]]. However, by [[2720]], the [[SLDF]] had decommissioned and sold off the remaining ''Barons'' to the Great Houses;<ref name="TRO:3057Rp200"/> the [[Capellan Confederation]] kept three ''Barons'' in their active fleet until at least [[2765]]<ref name="FR:2765CCAFp5">''Field Report 2765: CCAF'', p. 5: "Guarding the Vault of Heaven"</ref> while the [[Draconis Combine]] was operating five<ref>[http://bg.battletech.com/forums/index.php/topic,35369.msg855464.html#msg855464 Official Errata Thread]</ref> the [[Federated Suns]] three<ref>''Field Report 2765: AFFS'', p. 6: "Naval Defense Doctrine"</ref> and the [[Lyran Commonwealth]] one at the same point in time.<ref name="FR2765:LCAFp5">''Field Report 2765: LCAF'', p. 5: "The Vacuum Fleet"</ref> | ||
| − | The [[Succession Wars (History)|Succession Wars]] would see even mothballed ''Barons'' restored to combat status; the last active ''Baron'' in the [[Inner Sphere]] was believed to have been the [[Draconis Combine]] destroyer DCS ''[[Yedo]]'' restored to active service and destroyed in [[2853]] in battle over [[Hesperus II]],<ref name="TRO:3057Rp200"/><ref>''Tactics of Desperation'', Part 1</ref> but at least one ''Baron'' would survive in a [[Clan]] naval cache until the [[Wars of Reaving]].<ref>''The Wars of Reaving'', pp. 112–113: "Constriction"</ref> In the buildup to the [[Jihad]] | + | The [[Succession Wars (History)|Succession Wars]] would see even mothballed ''Barons'' restored to combat status; the last active ''Baron'' in the [[Inner Sphere]] was believed to have been the [[Draconis Combine]] destroyer DCS ''[[Yedo]]'' restored to active service and destroyed in [[2853]] in battle over [[Hesperus II]],<ref name="TRO:3057Rp200"/><ref>''Tactics of Desperation'', Part 1</ref> but at least one ''Baron'' would survive in a [[Clan]] naval cache until the [[Wars of Reaving]].<ref>''The Wars of Reaving'', pp. 112–113: "Constriction"</ref> In the buildup to the [[Jihad]] the [[Word of Blake]] would restore three ''Barons'' to working order, subsequently deploying them in various battles around the Inner Sphere, with the last being destroyed in [[3077]].<ref name="J:FRp128">''Jihad: Final Reckoning'', p. 128: "Word of Blake Naval Assets"</ref> |
==Armament== | ==Armament== | ||
| − | Mounting a large array of [[NL35]] capital Lasers, the ''Baron'' boasts impressive endurance on longer patrols, with six mounted in the nose, ten carried in each broadside with a further three directly aft. A mix of capital-grade [[ | + | Mounting a large array of [[NL35]] capital Lasers, the ''Baron'' boasts impressive endurance on longer patrols, with six mounted in the nose, ten carried in each broadside with a further three directly aft. A mix of capital-grade [[autocannon]]s and missile launchers provide support, with two [[NAC/10]]s and [[White Shark]] missile launchers in each forward angle, two more NAC/10s on each rear angle and two White Shark tubes directly rearward.<ref name="TRO:3057Rp200"/> |
==Cargo== | ==Cargo== | ||