Difference between revisions of "Monitor (naval concept)"
m (→Existing Monitors: wording) |
Csdavis715 (talk | contribs) m |
||
(4 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
− | {{otheruses|the spacecraft design concept|other uses|Monitor | + | {{otheruses|the spacecraft design concept|other uses|Monitor}} |
==Overview== | ==Overview== | ||
In the context of [[BattleTech]] spacecraft, the term '''Monitor''', although not clearly defined, is usually used to describe the concept of a [[WarShip]] without a [[jump drive]] core. | In the context of [[BattleTech]] spacecraft, the term '''Monitor''', although not clearly defined, is usually used to describe the concept of a [[WarShip]] without a [[jump drive]] core. | ||
Line 6: | Line 6: | ||
==No Official Rules== | ==No Official Rules== | ||
− | No official rules exist for Monitors. The very concept breaks the aerospace construction rules, as WarShips (with their size limit of 2,500,000 tons) mount a jump drive by definition. Under Canon rules, | + | No official rules exist for Monitors. The very concept breaks the aerospace construction rules, as WarShips (with their size limit of 2,500,000 tons) mount a jump drive by definition. Under Canon rules, non–jump capable vessels must be built either as [[DropShip]]s (size limit of 100,000 tons) or even [[small craft]] (size limit of 200 tons). [[Space station]]s are immobile structures and cannot mount tactical maneuvering thrusters, giving them limited tactical value. |
− | [[Gerald Hall]] pioneered the Monitor concept in the [[MechForce]] magazine [[MechQuarterly]] (vol. 4, issue 2), an official but | + | [[Gerald Hall]] pioneered the Monitor concept in the [[MechForce]] magazine [[MechQuarterly]] (vol. 4, issue 2), an official but [[canon|noncanon]] BattleTech publication. His suggested construction rules for Monitors were incorporated into the official BattleTech design program, [[HeavyMetal Aero]], but are not canonical and violate legal construction rules. |
==XTRO:Boondoggles== | ==XTRO:Boondoggles== | ||
Line 28: | Line 28: | ||
:With the advent of the [[compact KF drive]], space became a much more dangerous place. No longer were warships limited to assault DropShips, but they could easily surpass a million tons. Yet, almost half of that mass was still tied up in the KF drive. During the latter part of the twenty-seventh century, a group of [[SLDF]] [[admiral]]s pushed to create a new breed of WarShip, dispensing with the KF drive with the goal of doubling the potential firepower such a vessel could bring to bear. After over a decade of campaigning, funding was finally allocated for project AMHITRITE and Blue Nose Clipperships won the bidding to provide construction for the prototype. | :With the advent of the [[compact KF drive]], space became a much more dangerous place. No longer were warships limited to assault DropShips, but they could easily surpass a million tons. Yet, almost half of that mass was still tied up in the KF drive. During the latter part of the twenty-seventh century, a group of [[SLDF]] [[admiral]]s pushed to create a new breed of WarShip, dispensing with the KF drive with the goal of doubling the potential firepower such a vessel could bring to bear. After over a decade of campaigning, funding was finally allocated for project AMHITRITE and Blue Nose Clipperships won the bidding to provide construction for the prototype. | ||
− | :Though the concept “monitor” was based on the proven hull of the venerable ''[[Avatar (WarShip)|Avatar]]'' class cruiser, almost immediately problems emerged when the KF drive was removed from the equation. Without the frame around the KF drive acting as the ship’s primary keel, stress analysis revealed that a great deal of additional structural reinforcement would be needed to avoid integrity failure under combat thrust. The design plans were hastily re-drawn and construction resumed, but the structure reinforcements ate away far more mass than originally expected. | + | :Though the concept “monitor” was based on the proven hull of the venerable ''[[Avatar (WarShip class)|Avatar]]'' class cruiser, almost immediately problems emerged when the KF drive was removed from the equation. Without the frame around the KF drive acting as the ship’s primary keel, stress analysis revealed that a great deal of additional structural reinforcement would be needed to avoid integrity failure under combat thrust. The design plans were hastily re-drawn and construction resumed, but the structure reinforcements ate away far more mass than originally expected. |
:As construction continued on three prototype hulls, the numerous setbacks and additional costs mounted, drawing greater scrutiny from a number of oversight committees. While these monitors had a potential military impact, the potential political impact of their possible failure was orders of magnitudes greater. Internal divisions, even among the Star League admiralty, quickly formed, with pro-monitor and anti-monitor camps ignoring any data that failed to agree with their positions. | :As construction continued on three prototype hulls, the numerous setbacks and additional costs mounted, drawing greater scrutiny from a number of oversight committees. While these monitors had a potential military impact, the potential political impact of their possible failure was orders of magnitudes greater. Internal divisions, even among the Star League admiralty, quickly formed, with pro-monitor and anti-monitor camps ignoring any data that failed to agree with their positions. | ||
Line 46: | Line 46: | ||
==Existing Monitors== | ==Existing Monitors== | ||
Although the Monitor concept at large was refuted, a few isolated cases exist in canon that could be regarded as Monitors: | Although the Monitor concept at large was refuted, a few isolated cases exist in canon that could be regarded as Monitors: | ||
− | *The ''[[Bonaventure]]''-class corvette ''[[Sheridan (Bonaventure)|Sheridan]]'', as of [[3067]], operates as a training ship in the [[Sol]] system. It has had its jump drive removed to make room for a full second crew and some training gear; however, it is unknown just how much of the jump drive was removed and how much room/mass the extra facilities take up.<ref>BattleCorps short story "The Last Full Measure"</ref> | + | *The ''[[Bonaventure (WarShip class)|Bonaventure]]''-class corvette ''[[Sheridan (Individual Bonaventure-class WarShip)|Sheridan]]'', as of [[3067]], operates as a training ship in the [[Sol]] system. It has had its jump drive removed to make room for a full second crew and some training gear; however, it is unknown just how much of the jump drive was removed and how much room/mass the extra facilities take up.<ref>BattleCorps short story "The Last Full Measure"</ref> |
− | *The [[Word of Blake]]'s converted ''[[Naga (WarShip class)|Naga]]''-class [[SDS]] control ships in the [[Sol]] system were effectively monitors.<ref>''Jihad Hot Spots: Terra'', pp. | + | *The [[Word of Blake]]'s converted ''[[Naga (WarShip class)|Naga]]''-class [[SDS]] control ships in the [[Sol]] system were effectively monitors.<ref>''Jihad Hot Spots: Terra'', pp. 178–180</ref> |
*[[Battlesat]] type space stations with (limited) thrust power could also arguably be described as monitors. It should be noted that they are legal under current construction rules, but have been rendered largely moot due to their limited movement. As a consequence, it is questionable if battlesats were deployed outside of the known canonical example in the [[Luthien]] system.<ref>As explained in [http://bg.battletech.com/forums/index.php/topic,28084.0.html this thread] on the official [[BattleTech forum]]</ref> | *[[Battlesat]] type space stations with (limited) thrust power could also arguably be described as monitors. It should be noted that they are legal under current construction rules, but have been rendered largely moot due to their limited movement. As a consequence, it is questionable if battlesats were deployed outside of the known canonical example in the [[Luthien]] system.<ref>As explained in [http://bg.battletech.com/forums/index.php/topic,28084.0.html this thread] on the official [[BattleTech forum]]</ref> | ||
*Despite its name, the ''[[Cockatrice]] Monitor Platform'' is technically a DropShip (its design in turn based on a [[Small Craft]], the [[K-1]] DropShuttle); while it could be described as a monitor in a functionality sense, it is not a Monitor in the design sense of being a WarShip without a jump drive core. | *Despite its name, the ''[[Cockatrice]] Monitor Platform'' is technically a DropShip (its design in turn based on a [[Small Craft]], the [[K-1]] DropShuttle); while it could be described as a monitor in a functionality sense, it is not a Monitor in the design sense of being a WarShip without a jump drive core. |
Latest revision as of 10:41, 14 October 2023
- This article is about the spacecraft design concept. For other uses, see Monitor.
Contents
Overview[edit]
In the context of BattleTech spacecraft, the term Monitor, although not clearly defined, is usually used to describe the concept of a WarShip without a jump drive core.
This drive core has no tactical value in combat but typically makes up 47.5% of a given WarShip's mass. The idea behind the Monitor concept is to free up this mass for weapons, armor, and other combat-relevant systems by forgoing the jump drive. Such Monitors would theoretically be vastly more powerful on a ton-per-ton basis compared to regular WarShips of the same mass.
No Official Rules[edit]
No official rules exist for Monitors. The very concept breaks the aerospace construction rules, as WarShips (with their size limit of 2,500,000 tons) mount a jump drive by definition. Under Canon rules, non–jump capable vessels must be built either as DropShips (size limit of 100,000 tons) or even small craft (size limit of 200 tons). Space stations are immobile structures and cannot mount tactical maneuvering thrusters, giving them limited tactical value.
Gerald Hall pioneered the Monitor concept in the MechForce magazine MechQuarterly (vol. 4, issue 2), an official but noncanon BattleTech publication. His suggested construction rules for Monitors were incorporated into the official BattleTech design program, HeavyMetal Aero, but are not canonical and violate legal construction rules.
XTRO:Boondoggles[edit]
BattleTech Line Developer Herbert A. Beas II has repeatedly[1] stated that Monitors, if they existed, would outperform WarShips to the point where they would threaten game balance, and that Monitors were therefore kept out of BattleTech for game balancing reasons. To put the issue to rest, he solicited an entry for Monitors in Experimental Technical Readout: Boondoggles to showcase that, and why, the concept was not viable in the BattleTech universe. However, within days of publication fans pointed out on the BattleTech Forum that the entry as written, which described a small number of Monitors to have been built and deployed before the project was scrapped, actually proved the Monitor concept to be viable to a degree. In response to this, an erratum was published that completely replaces the initial entry in what technically constitutes a retcon (in the sense of altering canon).
The following is a direct transcript of the official erratum posting, reproduced here verbatim with kind permission of the author, Herbert Beas:
“ | Hello,
The following errata applies to the entry titled "Monitors". Please replace ALL TEXT under this entry with the following:
We apologize for the inconvenience. Thank you, |
” |
— Herbert Beas |
Existing Monitors[edit]
Although the Monitor concept at large was refuted, a few isolated cases exist in canon that could be regarded as Monitors:
- The Bonaventure-class corvette Sheridan, as of 3067, operates as a training ship in the Sol system. It has had its jump drive removed to make room for a full second crew and some training gear; however, it is unknown just how much of the jump drive was removed and how much room/mass the extra facilities take up.[2]
- The Word of Blake's converted Naga-class SDS control ships in the Sol system were effectively monitors.[3]
- Battlesat type space stations with (limited) thrust power could also arguably be described as monitors. It should be noted that they are legal under current construction rules, but have been rendered largely moot due to their limited movement. As a consequence, it is questionable if battlesats were deployed outside of the known canonical example in the Luthien system.[4]
- Despite its name, the Cockatrice Monitor Platform is technically a DropShip (its design in turn based on a Small Craft, the K-1 DropShuttle); while it could be described as a monitor in a functionality sense, it is not a Monitor in the design sense of being a WarShip without a jump drive core.
References[edit]
- ↑ "Establishing that monitors never worked in the setting, however, was my intention.";
"We simply call those "broken" JumpShips and/or WarShips. Really, the point is that a "monitor" in BattleTech simply does not exist as a viable or in any way functional concept.";
"There never were any official monitor rules. That was the point of the entire exercise with XTR: Boondoggles; explaining why there never were any." - ↑ BattleCorps short story "The Last Full Measure"
- ↑ Jihad Hot Spots: Terra, pp. 178–180
- ↑ As explained in this thread on the official BattleTech forum
Bibliography[edit]
- Experimental Technical Readout: Boondoggles (mind the erratum published for the Monitor entry)
- Jihad Hot Spots: Terra
- "The Last Full Measure" (BattleCorps Story)
- MechQuarterly vol. 4, issue 2 (apocryphal)