From 3cf576e201207795e4f979e26e9f763fe122a994 Mon Sep 17 00:00:00 2001 From: repligator Date: Mon, 22 Jul 2024 18:21:01 -0400 Subject: [PATCH] Spelling, typos, etc. Changed several Black Knight entries that were referencing other models. Rephrased a sentence that was uncomfortably close to being copy-pasted. All tests passed or ignored. --- megamek/data/mechfiles/fighters/ProtoTypes/Suzaku SU-14.blk | 2 +- .../data/mechfiles/fighters/TRO3039u/Chippewa CHP-W5.blk | 2 +- .../data/mechfiles/fighters/TRO3039u/Corsair CSR-V12.blk | 2 +- megamek/data/mechfiles/fighters/TRO3039u/Stuka STU-K10.blk | 2 +- megamek/data/mechfiles/fighters/TRO3039u/Stuka STU-K5.blk | 2 +- .../data/mechfiles/mechs/3039u/Black Knight BL-7-KNT-L.mtf | 2 +- .../data/mechfiles/mechs/3039u/Black Knight BL-7-KNT.mtf | 2 +- megamek/data/mechfiles/mechs/3039u/Blackjack BJ-1X.mtf | 2 +- megamek/data/mechfiles/mechs/3039u/Crockett CRK-5003-0.mtf | 4 ++-- megamek/data/mechfiles/mechs/3039u/Cyclops CP-10-HQ.mtf | 2 +- megamek/data/mechfiles/mechs/3039u/King Crab KGC-0000.mtf | 2 +- megamek/data/mechfiles/mechs/3039u/King Crab KGC-010.mtf | 2 +- megamek/data/mechfiles/mechs/3039u/Lancelot LNC25-02.mtf | 2 +- megamek/data/mechfiles/mechs/3039u/Ostroc OSR-2C.mtf | 2 +- megamek/data/mechfiles/mechs/3039u/Ostroc OSR-2L.mtf | 2 +- megamek/data/mechfiles/mechs/3039u/Ostroc OSR-2M.mtf | 2 +- megamek/data/mechfiles/mechs/3039u/Ostroc OSR-3C.mtf | 2 +- megamek/data/mechfiles/mechs/3039u/Ostsol OTL-4D.mtf | 2 +- megamek/data/mechfiles/mechs/3039u/Ostsol OTL-4F.mtf | 2 +- megamek/data/mechfiles/mechs/3039u/Thug THG-10E.mtf | 2 +- megamek/data/mechfiles/mechs/3039u/UrbanMech UM-R60.mtf | 2 +- megamek/data/mechfiles/mechs/3039u/UrbanMech UM-R60L.mtf | 2 +- megamek/data/mechfiles/mechs/3039u/Vulcan VL-2T.mtf | 2 +- megamek/data/mechfiles/mechs/3039u/Vulcan VL-5T.mtf | 2 +- megamek/data/mechfiles/mechs/3039u/Wasp WSP-1A.mtf | 4 ++-- megamek/data/mechfiles/mechs/3039u/Wasp WSP-1D.mtf | 2 +- megamek/data/mechfiles/mechs/3039u/Wasp WSP-1K.mtf | 2 +- megamek/data/mechfiles/mechs/3039u/Wasp WSP-1L.mtf | 2 +- megamek/data/mechfiles/mechs/3039u/Wasp WSP-1W.mtf | 2 +- .../data/mechfiles/mechs/3050U/Black Knight BL-12-KNT.mtf | 2 +- .../data/mechfiles/mechs/3050U/Black Knight BL6b-KNT.mtf | 2 +- megamek/data/mechfiles/mechs/3050U/Crab CRB-27.mtf | 2 +- megamek/data/mechfiles/mechs/3050U/Crockett CRK-5003-1.mtf | 2 +- megamek/data/mechfiles/mechs/3050U/Crockett CRK-5003-3.mtf | 2 +- megamek/data/mechfiles/mechs/3050U/Crockett CRK-5004-1.mtf | 2 +- megamek/data/mechfiles/mechs/3050U/Crockett CRK-5005-1.mtf | 2 +- megamek/data/mechfiles/mechs/3050U/Dragonfly (Viper) A.mtf | 2 +- megamek/data/mechfiles/mechs/3050U/Dragonfly (Viper) B.mtf | 2 +- megamek/data/mechfiles/mechs/3050U/Dragonfly (Viper) C.mtf | 2 +- megamek/data/mechfiles/mechs/3050U/Dragonfly (Viper) D.mtf | 2 +- megamek/data/mechfiles/mechs/3050U/Dragonfly (Viper) E.mtf | 2 +- megamek/data/mechfiles/mechs/3050U/Dragonfly (Viper) F.mtf | 2 +- megamek/data/mechfiles/mechs/3050U/Dragonfly (Viper) G.mtf | 2 +- megamek/data/mechfiles/mechs/3050U/Dragonfly (Viper) H.mtf | 2 +- megamek/data/mechfiles/mechs/3050U/Dragonfly (Viper) I.mtf | 2 +- .../data/mechfiles/mechs/3050U/Dragonfly (Viper) Prime.mtf | 2 +- megamek/data/mechfiles/mechs/3050U/Guillotine GLT-3N.mtf | 2 +- megamek/data/mechfiles/mechs/3050U/Hunchback HBK-5M.mtf | 2 +- megamek/data/mechfiles/mechs/3050U/King Crab KGC-000.mtf | 2 +- megamek/data/mechfiles/mechs/3050U/King Crab KGC-005.mtf | 2 +- megamek/data/mechfiles/mechs/3050U/King Crab KGC-008.mtf | 2 +- megamek/data/mechfiles/mechs/3050U/King Crab KGC-008B.mtf | 2 +- megamek/data/mechfiles/mechs/3050U/UrbanMech UM-R63.mtf | 2 +- megamek/data/mechfiles/mechs/3050U/UrbanMech UM-R68.mtf | 2 +- megamek/data/mechfiles/mechs/3050U/UrbanMech UM-R70.mtf | 2 +- megamek/data/mechfiles/mechs/3050U/Urbanmech UM-R69.mtf | 2 +- .../data/mechfiles/mechs/3055U/Hellhound (Conjurer) 3.mtf | 2 +- megamek/data/mechfiles/mechs/3058Uu/Kodiak 2.mtf | 2 +- megamek/data/mechfiles/mechs/3058Uu/Kodiak 3.mtf | 2 +- megamek/data/mechfiles/mechs/3058Uu/Kodiak 4.mtf | 2 +- megamek/data/mechfiles/mechs/3058Uu/Kodiak 5.mtf | 2 +- megamek/data/mechfiles/mechs/3058Uu/Kodiak.mtf | 2 +- megamek/data/mechfiles/mechs/3075/Ostroc OSR-2Cb.mtf | 2 +- megamek/data/mechfiles/mechs/3085u/ONN/Cyclops CP-11-B.mtf | 2 +- megamek/data/mechfiles/mechs/3085u/ONN/Cyclops CP-11-C2.mtf | 2 +- megamek/data/mechfiles/mechs/3085u/ONN/Cyclops CP-11-C3.mtf | 2 +- .../data/mechfiles/mechs/3085u/ONN/Dragonfly (Viper) U.mtf | 2 +- .../data/mechfiles/mechs/3085u/ONN/King Crab KGC-005r.mtf | 2 +- megamek/data/mechfiles/mechs/3085u/ONN/UrbanMech UM-AIV.mtf | 2 +- megamek/data/mechfiles/mechs/3085u/ONN/UrbanMech UM-R80.mtf | 2 +- .../data/mechfiles/mechs/3085u/Phoenix/Griffin GRF-5K.mtf | 2 +- .../data/mechfiles/mechs/3085u/Phoenix/Griffin GRF-6CS.mtf | 2 +- .../data/mechfiles/mechs/3085u/Phoenix/Griffin GRF-6S.mtf | 4 ++-- .../data/mechfiles/mechs/3085u/Phoenix/Ostroc OSR-4C.mtf | 2 +- .../data/mechfiles/mechs/3085u/Phoenix/Ostroc OSR-4K.mtf | 4 ++-- .../data/mechfiles/mechs/3085u/Phoenix/Ostroc OSR-4L.mtf | 2 +- .../data/mechfiles/mechs/3085u/Phoenix/Ostroc OSR-5C.mtf | 2 +- .../data/mechfiles/mechs/3085u/Phoenix/Ostroc OSR-5W.mtf | 6 +++--- .../mechfiles/mechs/3085u/Phoenix/Phoenix Hawk IIC 3.mtf | 2 +- .../mechfiles/mechs/3085u/Phoenix/Phoenix Hawk IIC 4.mtf | 2 +- .../mechfiles/mechs/3085u/Phoenix/Phoenix Hawk IIC 5.mtf | 2 +- .../mechfiles/mechs/3085u/Phoenix/Phoenix Hawk IIC 6.mtf | 2 +- .../mechfiles/mechs/3085u/Phoenix/Phoenix Hawk IIC 7.mtf | 2 +- .../mechfiles/mechs/3085u/Phoenix/Phoenix Hawk IIC 8.mtf | 2 +- megamek/data/mechfiles/mechs/3085u/Phoenix/Wasp WSP-3A.mtf | 2 +- megamek/data/mechfiles/mechs/3085u/Phoenix/Wasp WSP-3S.mtf | 2 +- .../data/mechfiles/mechs/3085u/Phoenix/Wasp WSP-7MAF.mtf | 2 +- megamek/data/mechfiles/mechs/3085u/Phoenix/Wasp WSP-8T.mtf | 2 +- .../data/mechfiles/mechs/3145/Davion/Atlas III AS7-D2.mtf | 2 +- .../data/mechfiles/mechs/3145/Davion/Atlas III AS7-D3.mtf | 2 +- .../data/mechfiles/mechs/3145/NTNU RS/Griffin GRF-6S2.mtf | 2 +- megamek/data/mechfiles/mechs/3145/NTNU RS/Wasp WSP-3K.mtf | 2 +- megamek/data/mechfiles/mechs/3145/NTNU RS/Wasp WSP-3P.mtf | 2 +- .../data/mechfiles/mechs/3145/Steiner/King Crab KGC-009.mtf | 2 +- megamek/data/mechfiles/mechs/3150/King Crab KGC-009C.mtf | 2 +- megamek/data/mechfiles/mechs/ER 2750/Crab CRB-27sl.mtf | 2 +- .../mechs/ForcePacks/UrbanMech/UrbanMech UM-R27.mtf | 2 +- .../mechfiles/mechs/ISP3/Reptar EPT-C-1 MilitiaMech.mtf | 2 +- .../mechs/Operation Klondike/Crockett CRK-5003-1b.mtf | 2 +- .../mechs/Rec Guides ilClan/Vol 15/Phoenix Hawk IIC 10.mtf | 2 +- .../mechs/Rec Guides ilClan/Vol 15/Phoenix Hawk IIC 2.mtf | 2 +- .../mechs/Rec Guides ilClan/Vol 15/Phoenix Hawk IIC 9.mtf | 2 +- .../mechs/Rec Guides ilClan/Vol 15/Phoenix Hawk IIC.mtf | 2 +- .../mechs/Rec Guides ilClan/Vol 2/UrbanMech UM-R96.mtf | 2 +- .../mechfiles/mechs/Rec Guides ilClan/Vol 21/Cyclops C.mtf | 2 +- .../mechfiles/mechs/Rec Guides ilClan/Vol 21/Kodiak 6.mtf | 2 +- .../mechs/Rec Guides ilClan/Vol 21/Ostroc OSR-2D.mtf | 2 +- .../mechs/Rec Guides ilClan/Vol 21/Ostroc OSR-3M.mtf | 2 +- .../mechs/Rec Guides ilClan/Vol 21/Ostroc OSR-6R.mtf | 2 +- .../mechs/Rec Guides ilClan/Vol 21/Ostroc OSR-9C.mtf | 2 +- .../mechfiles/mechs/Rec Guides ilClan/Vol 29/Charger C.mtf | 2 +- .../mechs/Rec Guides ilClan/Vol 31/Clint CLNT-3 4T.mtf | 2 +- .../mechfiles/mechs/Rec Guides ilClan/Vol 4/Wasp WSP-3W.mtf | 2 +- .../mechfiles/mechs/Rec Guides ilClan/Vol 4/Wasp WSP-4W.mtf | 2 +- .../Rec Guides ilClan/Vol 5/Hellhound (Conjurer) 7.mtf | 2 +- .../mechs/Rec Guides ilClan/Vol 5/Hellhound (Conjurer).mtf | 2 +- .../mechs/Rec Guides ilClan/Vol 5/King Crab KGC-011.mtf | 2 +- .../mechs/Rec Guides ilClan/Vol 8/Dragonfly (Viper) J.mtf | 2 +- .../mechs/Rec Guides ilClan/Vol 8/Dragonfly (Viper) K.mtf | 2 +- .../mechs/Rec Guides ilClan/Vol 8/Dragonfly (Viper) L.mtf | 2 +- .../mechs/Rec Guides ilClan/Vol 8/Dragonfly (Viper) M.mtf | 2 +- .../mechs/Rec Guides ilClan/Vol 8/Dragonfly (Viper) R.mtf | 2 +- .../mechs/Rec Guides ilClan/Vol 8/Dragonfly (Viper) T.mtf | 2 +- .../mechfiles/mechs/Shrapnel/Vol 4/SuburbanMech UM-R100.mtf | 2 +- .../mechfiles/mechs/Shrapnel/Vol 4/SuburbanMech UM-R90.mtf | 2 +- .../Black Knight BL-10-KNT Ross.mtf | 2 +- .../data/mechfiles/mechs/Tukayyid/Black Knight BL-9-KNT.mtf | 2 +- .../mechs/Turning Points/HTP Misery/Ostroc OSR-2C Michi.mtf | 2 +- .../mechs/Turning Points/JTP Dieron/Kodiak Cale.mtf | 2 +- .../mechs/WoR Supplemental/Dragonfly (Viper) Z.mtf | 2 +- .../mechs/Wolf and Blake/Griffin GRF-6S Francine II.mtf | 2 +- .../mechs/Wolf and Blake/Griffin GRF-6S Francine.mtf | 2 +- .../data/mechfiles/mechs/XTRs/Primitives II/Wasp WSP-1.mtf | 2 +- .../mechfiles/mechs/XTRs/Republic II/UrbanMech UM-R93.mtf | 2 +- .../mechs/XTRs/Succession Wars/Super Wasp WSP-2A-X.mtf | 2 +- .../data/mechfiles/vehicles/3075/Crow Scout Helicopter.blk | 2 +- megamek/data/mechfiles/vehicles/DarkAge/Shackleton AESV.blk | 2 +- 137 files changed, 143 insertions(+), 143 deletions(-) diff --git a/megamek/data/mechfiles/fighters/ProtoTypes/Suzaku SU-14.blk b/megamek/data/mechfiles/fighters/ProtoTypes/Suzaku SU-14.blk index ddb3a6e845e..7d8a0c8e714 100644 --- a/megamek/data/mechfiles/fighters/ProtoTypes/Suzaku SU-14.blk +++ b/megamek/data/mechfiles/fighters/ProtoTypes/Suzaku SU-14.blk @@ -140,7 +140,7 @@ Kajikazawa CHASSIS:Suzaku Sleek Assault ENGINE:Nissan 375 Extra Light ARMOR:New Samarkand Flying Dragon Heavy Ferro-Aluminum -COMMUNICATIONS:Duotech 250 +COMMUNICATIONS:Duoteck 250 TARGETING:Chichester ASR30 diff --git a/megamek/data/mechfiles/fighters/TRO3039u/Chippewa CHP-W5.blk b/megamek/data/mechfiles/fighters/TRO3039u/Chippewa CHP-W5.blk index 65c17ed946c..955d69862f1 100644 --- a/megamek/data/mechfiles/fighters/TRO3039u/Chippewa CHP-W5.blk +++ b/megamek/data/mechfiles/fighters/TRO3039u/Chippewa CHP-W5.blk @@ -125,7 +125,7 @@ Designed by the Star League, the heavy Chippewa isn't extremely fast, but it has -Short or long range, it is best to stay away from a Chippewa. With the Exostar LRM-15 and SRM-6 racks to the front, backed up by two Martell Medium Lasers in the nose and four McCorkel Large Lasers in the wings, the Chippewa can lay down a devastating first strike. For rear protection, two McCorkel Small Lasers are mounted in the tail. The Chippewa was the first SLDF fighter to mount specialized Laser Insulators. However, the technological know-how to produce this insulation was lost during the Succession Wars and later models were built without them. +Short or long range, it is best to stay away from a Chippewa. With the ExoStar LRM-15 and SRM-6 racks to the front, backed up by two Martell Medium Lasers in the nose and four McCorkel Large Lasers in the wings, the Chippewa can lay down a devastating first strike. For rear protection, two McCorkel Small Lasers are mounted in the tail. The Chippewa was the first SLDF fighter to mount specialized Laser Insulators. However, the technological know-how to produce this insulation was lost during the Succession Wars and later models were built without them. diff --git a/megamek/data/mechfiles/fighters/TRO3039u/Corsair CSR-V12.blk b/megamek/data/mechfiles/fighters/TRO3039u/Corsair CSR-V12.blk index ae105209a20..247bc18522a 100644 --- a/megamek/data/mechfiles/fighters/TRO3039u/Corsair CSR-V12.blk +++ b/megamek/data/mechfiles/fighters/TRO3039u/Corsair CSR-V12.blk @@ -121,7 +121,7 @@ The compact laser system and sleek design of the Corsair made it a superior aero -Geared towards short range combat, the Corsair carries a total of two Martell Medium Lasers and four Exostar Small Lasers, while two Exostar Large Lasers gives it some additional reach. Both medium lasers are located in each wing, with the large lasers and two of the small lasers filling the nose. For coverage to the stern, the remaining two small lasers are mounted to the rear and tied directly into the targeting systems, giving the pilot extreme accuracy in his rear field of fire. The compact laser systems are also well-suited for a ground-attack role, while the presence of sixteen heat sinks means the Corsair can continuously fire both large lasers and fire the medium and small lasers with negligible heat buildup. +Geared towards short range combat, the Corsair carries a total of two Martell Medium Lasers and four ExoStar Small Lasers, while two ExoStar Large Lasers gives it some additional reach. Both medium lasers are located in each wing, with the large lasers and two of the small lasers filling the nose. For coverage to the stern, the remaining two small lasers are mounted to the rear and tied directly into the targeting systems, giving the pilot extreme accuracy in his rear field of fire. The compact laser systems are also well-suited for a ground-attack role, while the presence of sixteen heat sinks means the Corsair can continuously fire both large lasers and fire the medium and small lasers with negligible heat buildup. diff --git a/megamek/data/mechfiles/fighters/TRO3039u/Stuka STU-K10.blk b/megamek/data/mechfiles/fighters/TRO3039u/Stuka STU-K10.blk index 257cb66453c..dcabc3d9463 100644 --- a/megamek/data/mechfiles/fighters/TRO3039u/Stuka STU-K10.blk +++ b/megamek/data/mechfiles/fighters/TRO3039u/Stuka STU-K10.blk @@ -126,7 +126,7 @@ First designed in 2530 for the Star League Defense Force, the Stuka is meant for -This variant replaced the three Medium Lasers with two extra Heat Sinks and four Exostar Small Lasers. This variant is mostly seen in the Draconis March Militia. +This variant replaced the three Medium Lasers with two extra Heat Sinks and four ExoStar Small Lasers. This variant is mostly seen in the Draconis March Militia. diff --git a/megamek/data/mechfiles/fighters/TRO3039u/Stuka STU-K5.blk b/megamek/data/mechfiles/fighters/TRO3039u/Stuka STU-K5.blk index 9b7901b3889..c72efe42e57 100644 --- a/megamek/data/mechfiles/fighters/TRO3039u/Stuka STU-K5.blk +++ b/megamek/data/mechfiles/fighters/TRO3039u/Stuka STU-K5.blk @@ -124,7 +124,7 @@ First designed in 2530 for the Star League Defense Force, the Stuka is meant for -The STU-K5 Stuka carries a mix of weaponry, a Simpson LRM-20 Rack, Holly SRM-4, and a Martell Medium Laser rounding out the payload in the nose. The wings mount two Exostar Large Lasers each, with the final two Medium Lasers facing to the rear. +The STU-K5 Stuka carries a mix of weaponry, a Simpson LRM-20 Rack, Holly SRM-4, and a Martell Medium Laser rounding out the payload in the nose. The wings mount two ExoStar Large Lasers each, with the final two Medium Lasers facing to the rear. diff --git a/megamek/data/mechfiles/mechs/3039u/Black Knight BL-7-KNT-L.mtf b/megamek/data/mechfiles/mechs/3039u/Black Knight BL-7-KNT-L.mtf index e25ee4ec8e6..1b8e7dbf894 100644 --- a/megamek/data/mechfiles/mechs/3039u/Black Knight BL-7-KNT-L.mtf +++ b/megamek/data/mechfiles/mechs/3039u/Black Knight BL-7-KNT-L.mtf @@ -160,7 +160,7 @@ Heat Sink overview:The Black Knight was introduced in 2578 both as a front-line combatant and as a command BattleMech at the company and battalion level for the Star League Defense Force. -capabilities:Thirteen tons of armor protection on an Endo Steel frame allows the Black Knight to withstand significant punishment. The biggest disadvantage of the design is its challenging heat curve, though the fact that it mounts twenty heat sinks ensures that the Black Knight can still disperse a significant amount of heat produced by its weapons. However, if the 'Mech is involved in a prolonged combat situation, a less experienced MechWarrior who is not competent at heat management may be in trouble. The Black Knight's superior communications equipment allowed it to readily coordinate a whole company of 'Mechs at the same time, as well as link together the command frequencies of an entire parent regiment and connect with orbital support satellites. Improved construction materials provided the Black Knight with a light but sturdy chassis capable of carrying more weaponry and armor for less weight. With the type and amount of weapons carried by the 'Mech, the only challenge the Black Knight faces is heat management. +capabilities:The biggest disadvantage of the design is its challenging heat curve, though the fact that it mounts twenty-two heat sinks ensures that the Black Knight can still disperse a significant amount of heat produced by its weapons. However, if the 'Mech is involved in a prolonged combat situation, a less experienced MechWarrior who is not competent at heat management may be in trouble. The Black Knight's superior communications equipment allowed it to readily coordinate a whole company of 'Mechs at the same time, as well as link together the command frequencies of an entire parent regiment and connect with orbital support satellites. Improved construction materials provided the Black Knight with a light but sturdy chassis capable of carrying more weaponry and armor for less weight. With the type and amount of weapons carried by the 'Mech, the only challenge the Black Knight faces is heat management. deployment:This is a field modification from the Free Worlds League during the Succession Wars. Because of the scarcity of PPCs within that realm, Black Knights with a damaged PPC would have that weapon replaced with a large laser, while the extra space and weight left over allowed for two additional heat sinks to be added. diff --git a/megamek/data/mechfiles/mechs/3039u/Black Knight BL-7-KNT.mtf b/megamek/data/mechfiles/mechs/3039u/Black Knight BL-7-KNT.mtf index 3335298bc29..fee3694ea25 100644 --- a/megamek/data/mechfiles/mechs/3039u/Black Knight BL-7-KNT.mtf +++ b/megamek/data/mechfiles/mechs/3039u/Black Knight BL-7-KNT.mtf @@ -160,7 +160,7 @@ Heat Sink overview:The Black Knight was introduced in 2578 both as a front-line combatant and as a command BattleMech at the company and battalion level for the Star League Defense Force. -capabilities:Thirteen tons of armor protection on an Endo Steel frame allows the Black Knight to withstand significant punishment. The biggest disadvantage of the design is its challenging heat curve, though the fact that it mounts twenty heat sinks ensures that the Black Knight can still disperse a significant amount of heat produced by its weapons. However, if the 'Mech is involved in a prolonged combat situation, a less experienced MechWarrior who is not competent at heat management may be in trouble. The Black Knight's superior communications equipment allowed it to readily coordinate a whole company of 'Mechs at the same time, as well as link together the command frequencies of an entire parent regiment and connect with orbital support satellites. Improved construction materials provided the Black Knight with a light but sturdy chassis capable of carrying more weaponry and armor for less weight. With the type and amount of weapons carried by the 'Mech, the only challenge the Black Knight faces is heat management. +capabilities:The biggest disadvantage of the design is its challenging heat curve, though the fact that it mounts twenty heat sinks ensures that the Black Knight can still disperse a significant amount of heat produced by its weapons. However, if the 'Mech is involved in a prolonged combat situation, a less experienced MechWarrior who is not competent at heat management may be in trouble. The Black Knight's superior communications equipment allowed it to readily coordinate a whole company of 'Mechs at the same time, as well as link together the command frequencies of an entire parent regiment and connect with orbital support satellites. Improved construction materials provided the Black Knight with a light but sturdy chassis capable of carrying more weaponry and armor for less weight. With the type and amount of weapons carried by the 'Mech, the only challenge the Black Knight faces is heat management. deployment:The BL-7 Black Knight is the downgraded version of the 'Mech produced during the Succession Wars following the destruction of Kong Interstellar Corporation's factories on Connaught in 2802. Production of the BL-7-KNT began in 2809 and continued until the CCAF destroyed the plant in 2820; thereafter many of the repairs made by the Great Houses to their own Black Knights in many ways mimicked Kong's version. The Endo Steel chassis was replaced with a Technicron Standard chassis which, while keeping the weapons payload and engine the same, required a reduction in overall armor protection by two tons. While the same weapon types were retained, the McCorkel, Maxell and Magna lasers were replaced with their respective Tronel III, II and I models. Kong Interstellar also replaced the communications system with the Tek BattleCom system and the targeting and tracking systems with a Tek Tru-Trak system. diff --git a/megamek/data/mechfiles/mechs/3039u/Blackjack BJ-1X.mtf b/megamek/data/mechfiles/mechs/3039u/Blackjack BJ-1X.mtf index 8448ef5f067..4748016f079 100644 --- a/megamek/data/mechfiles/mechs/3039u/Blackjack BJ-1X.mtf +++ b/megamek/data/mechfiles/mechs/3039u/Blackjack BJ-1X.mtf @@ -162,7 +162,7 @@ overview:The original contract between General Motors and the SLDF sought for "a capabilities:The Blackjack's original mission was to assist in suppressing insurgent groups (mostly in the Periphery) that defied Star League authority in the decades preceding its demise. The Blackjack is only a minor success in its secondary capacity as a fire support platform. The autocannons lacked the firepower to take on heavily defended targets. At close range, though, the combination of lasers poses a significantly bigger threat. The addition of jump jets came late in the design phase, but the Whitworth Jetlift units have proven to be a vital asset over the decades. The Blackjack's sole significant disadvantage was negative press, which stated that the entire project was a shambles because the 'Mech's basic architecture was defective and unstable. The 'Mech's tiny footpads were alleged to cause falls and hamper maneuverability, or that the StarGuard II armor was brittle and tended to break off. Despite the fact that none of these accusations were ever proven, the Blackjack went out of favor, and few grieved the loss of GM's production line. -deployment:Early Blackjack prototypes differed from the production model significantly. They were armed with twin GM Flashpoint flamers and additional heat sinks in place of each autocannon, and were powered by a VOX 225 power plant allowing for greater speed than the later models, but lacked the jump jets. +deployment:In contrast to the later production models, early prototype Blackjacks were armed with twin GM Flashpoint flamers and additional heat sinks in place of each autocannon, and were powered by a VOX 225 power plant allowing for greater speed than the later models, but lacked the jump jets. history:The Blackjack had limited use in the Star League, and manufacture was shortly discontinued. Relegated to service with Hegemony planetary militia or sold to League member nations, it can still be encountered on the battlefield today. The majority of them now fight for the Capellan Confederation and the Federated Suns. The Confederation has nothing but disdain for the design. The breakaway St. Ives Compact, on the other hand, could not be as picky, and the Blackjack serves in the St. Ives Lancers. The Federated Suns used the Blackjack in the March Militias until the myth of the Blackjack's inferiority was busted on Xhosa VII in 3022. The Crucis Lancers and Deneb Light Cavalry were re-interested in the 'Mech. diff --git a/megamek/data/mechfiles/mechs/3039u/Crockett CRK-5003-0.mtf b/megamek/data/mechfiles/mechs/3039u/Crockett CRK-5003-0.mtf index af4b93ff98e..e834eb73d30 100644 --- a/megamek/data/mechfiles/mechs/3039u/Crockett CRK-5003-0.mtf +++ b/megamek/data/mechfiles/mechs/3039u/Crockett CRK-5003-0.mtf @@ -163,9 +163,9 @@ overview:Introduced in 2735, the Crockett was originally designed and built for capabilities:Due to the fact that the Crockett was originally a training 'Mech, it carries a variety of weapons. In addition, the highly-advanced Scope 30 RNDST targeting-tracking system gave the large lasers superior range to any other laser system at the time of its introduction. The Crockett is also very well-protected thanks to sixteen and a half tons of armor. Finally it carries three jump jets, one in either leg and the rear torso, giving it a range of 90 meters. -deployment:The 5003-0 Crockett is a downgraded version of the 'Mech first spotted in 2881. The 'Mech retains the same overall feel of the 5003-1 but uses only technology available to the Great Houses during the Succession Wars. The ER Large Lasers have been replaced with Magna Mark III Large Lasers models and the LB-X autocannon has been downgraded to a standard Blakenberg AC/10. In addition, the double heat sinks that made the 'Mech capable of a very high rate of fire have been downgraded to single versions that can only dissipate half as much heat as those carried by the 5003-1 Crockett. Its electronics were also replaced with a GRPNTR Groundpainter 5 communications system and a Scope 30 RNDST targeting-tracking system. +deployment:The 5003-0 Crockett is a downgraded version of the 'Mech first spotted in 2881. The 'Mech retains the same overall feel of the 5003-1 but uses only technology available to the Great Houses during the Succession Wars. The ER Large Lasers have been replaced with Magna Mark III Large Lasers models and the LB-X autocannon has been downgraded to a standard Blankenburg AC/10. In addition, the double heat sinks that made the 'Mech capable of a very high rate of fire have been downgraded to single versions that can only dissipate half as much heat as those carried by the 5003-1 Crockett. Its electronics were also replaced with a GRPNTR Groundpainter 5 communications system and a Scope 30 RNDST targeting-tracking system. -history:Ten years after its introduction, however, Star League Defense Force commanders began to realize that Blankenburg Technologies had taken the "combat capability" requirement almost too seriously, and began to field the 'Mech on the front lines. Beyond its heavy weapons load-out, large number of heat sinks and use of jump jets, part of what made the Crockett successful was the enemy's unfamiliarity with this design, giving it an added advantage. Its cockpit systems, simplified for use as a trainer, allowed anyone to pilot the Crockett with only a minimal amount of familiarization training. The Crockett did not go without its growing pains, however. Once it was pressed into combat there was a flaw found in the cockpit's life support system that resulted in the death of three MechWarriors. This flaw was corrected in future production, with previously-issued machines recalled and refitted with the life support system upgrade. In service to the SLDF the hallmark tactic of the Crockett was to engage an enemy 'Mech at range and, before the enemy could accurately target it, jump behind them to attack their weaker rear. So effective was the Crockett that, following the dissolution of the Star League and start of the Succession Wars, many of the Great Houses removed the 'Mech from their training programs and used them to fight on the front lines. As many of the Crockett's components became lostech Blankenburg was forced to make do with inferior spare parts, reducing its capabilities with every year. Eventually the last few Crocketts were little more than a collection of salvaged parts, largely unrecognizable from their original design, until the 'Mech finally went extinct within the Inner Sphere. This changed starting in the thirty-first century, thanks to ComStar's secret stockpile of Star League-era 'Mechs. Original models of the Crockett were used to outfit the Com Guards while downgraded versions were gifted to the Draconis Combine as part of Operation Rosebud. With the Clan Invasion surviving models of the design were also seen among second-line Clan forces. As part of Precentor Martial Anastasius Focht's rearmament program the Blankenberg production line on Terra was reopened to start producing new Crocketts starting in 3054, although it would be only a few years until the Word of Blake conquered the planet and began supplying themselves and their Free Worlds League allies. In order to maintain their supply ComStar contracted Grumium Creations to begin producing Crocketts starting in 3062 and the 'Mech fought on both sides during the Jihad. +history:Ten years after its introduction, however, Star League Defense Force commanders began to realize that Blankenburg Technologies had taken the "combat capability" requirement almost too seriously, and began to field the 'Mech on the front lines. Beyond its heavy weapons load-out, large number of heat sinks and use of jump jets, part of what made the Crockett successful was the enemy's unfamiliarity with this design, giving it an added advantage. Its cockpit systems, simplified for use as a trainer, allowed anyone to pilot the Crockett with only a minimal amount of familiarization training. The Crockett did not go without its growing pains, however. Once it was pressed into combat there was a flaw found in the cockpit's life support system that resulted in the death of three MechWarriors. This flaw was corrected in future production, with previously-issued machines recalled and refitted with the life support system upgrade. In service to the SLDF the hallmark tactic of the Crockett was to engage an enemy 'Mech at range and, before the enemy could accurately target it, jump behind them to attack their weaker rear. So effective was the Crockett that, following the dissolution of the Star League and start of the Succession Wars, many of the Great Houses removed the 'Mech from their training programs and used them to fight on the front lines. As many of the Crockett's components became lostech Blankenburg was forced to make do with inferior spare parts, reducing its capabilities with every year. Eventually the last few Crocketts were little more than a collection of salvaged parts, largely unrecognizable from their original design, until the 'Mech finally went extinct within the Inner Sphere. This changed starting in the thirty-first century, thanks to ComStar's secret stockpile of Star League-era 'Mechs. Original models of the Crockett were used to outfit the Com Guards while downgraded versions were gifted to the Draconis Combine as part of Operation Rosebud. With the Clan Invasion surviving models of the design were also seen among second-line Clan forces. As part of Precentor Martial Anastasius Focht's rearmament program the Blankenburg production line on Terra was reopened to start producing new Crocketts starting in 3054, although it would be only a few years until the Word of Blake conquered the planet and began supplying themselves and their Free Worlds League allies. In order to maintain their supply ComStar contracted Grumium Creations to begin producing Crocketts starting in 3062 and the 'Mech fought on both sides during the Jihad. manufacturer:Refit primaryfactory:Various diff --git a/megamek/data/mechfiles/mechs/3039u/Cyclops CP-10-HQ.mtf b/megamek/data/mechfiles/mechs/3039u/Cyclops CP-10-HQ.mtf index c6ce4f4d3da..8d4c1f6eb89 100644 --- a/megamek/data/mechfiles/mechs/3039u/Cyclops CP-10-HQ.mtf +++ b/megamek/data/mechfiles/mechs/3039u/Cyclops CP-10-HQ.mtf @@ -157,7 +157,7 @@ Foot Actuator -Empty- overview:The Cyclops began production in 2710 as an assault BattleMech and headquarters unit for Star League Defense Force field commanders. -capabilities:A decent mix of weapons provided the Cyclops with both long- and short-range firepower and a sizable engine to keep up with mobile operations. But the centerpiece of the Cyclops is its sophisticated holographic battle computer, the Tacticon B-2000. When combined with the Omstead Olmstead 840 tight beam comm suite with SatNav module, the Cyclops can effectively command a brigade across the surface of an entire world. Unfortunately the Cyclops is poorly protected relative to other assault 'Mechs with only ten tons of armor, and while its normal load of twelve heat sinks allows it to stay cool in most cases, they can prove to be inadequate in especially heavy situations. +capabilities:A decent mix of weapons provided the Cyclops with both long- and short-range firepower and a sizable engine to keep up with mobile operations. But the centerpiece of the Cyclops is its sophisticated holographic battle computer, the Tacticon B-2000. When combined with the Olmstead 840 tight beam comm suite with SatNav module, the Cyclops can effectively command a brigade across the surface of an entire world. Unfortunately the Cyclops is poorly protected relative to other assault 'Mechs with only ten tons of armor, and while its normal load of twelve heat sinks allows it to stay cool in most cases, they can prove to be inadequate in especially heavy situations. deployment:The most notable of all Cyclops variants, introduced in 2750, fits the 'Mech with a Collapsible Command Module strapped to its rear torso, allowing a fully operational headquarters bunker to be set up in fifteen minutes. In order to make room for the module the Autocannon/20 and its ammunition was removed from this variant. Irreparable damages suffered during the Succession Wars means less than half of those Cyclopses with a working B-2000 have an operable command module. history:Unfortunately the Cyclops did not fare so well with the onset of the Amaris Civil War when the Rim Worlds Republic Military destroyed its primary factory on Caph in 2774. Spare parts for the machine quickly began to dry up, until by the end of the Succession Wars less than ten percent still had a working B-2000 computer. Lacking the critical part of being a command vehicle many Cyclopses were pressed into an assault role. Acting as the bodyguard or decoy for the real commanding officer, they proved to be swift if mediocre combat machines. As most enemies know about the vulnerable head and automatically target it in combat, many Cyclops pilots also began adding false head protectors to defend against impacts. A study by the NAIS after the Fourth Succession War would eventually find that these caused more harm than good by restricting vision and increasing shrapnel, ending the practice altogether. The rediscovery of the Helm Memory Core kick-started a number of attempts to replicate the B-2000 computer, however there were no successful attempts prior to the Clan Invasion. Also, the invention of the C3 Computer with its emphasis on small-scale networking, and a switch in doctrine to using DropShips as command posts, saw the Cyclops' command role decline. However Grumium Creations was eventually able to restart production of new variants of the 'Mech, and where it has participated a Cyclops with a working B-2000 has had noticeable effects. For this reason Cyclops 'Mechs with a working battle computer were reserved for high-ranking officers. manufacturer:Stormvanger Assemblies, Unlimited diff --git a/megamek/data/mechfiles/mechs/3039u/King Crab KGC-0000.mtf b/megamek/data/mechfiles/mechs/3039u/King Crab KGC-0000.mtf index f8fbbc23cc0..9d7bdecf536 100644 --- a/megamek/data/mechfiles/mechs/3039u/King Crab KGC-0000.mtf +++ b/megamek/data/mechfiles/mechs/3039u/King Crab KGC-0000.mtf @@ -166,6 +166,6 @@ manufacturer:Field Refit primaryfactory:Various systemmanufacturer:CHASSIS:Hollis Mark II systemmanufacturer:ENGINE:Vlar 300 -systemmanufacturer:ARMOR:Protec Tech 12 +systemmanufacturer:ARMOR:ProtecTech 12 systemmanufacturer:COMMUNICATIONS:Dalban's VirtuTalk systemmanufacturer:TARGETING:Dalban HiRez diff --git a/megamek/data/mechfiles/mechs/3039u/King Crab KGC-010.mtf b/megamek/data/mechfiles/mechs/3039u/King Crab KGC-010.mtf index 4c721fa5981..472dc9c0f1a 100644 --- a/megamek/data/mechfiles/mechs/3039u/King Crab KGC-010.mtf +++ b/megamek/data/mechfiles/mechs/3039u/King Crab KGC-010.mtf @@ -169,6 +169,6 @@ manufacturer:Cosara Weaponries,Cosara Weaponries primaryfactory:Mars,Northwind systemmanufacturer:CHASSIS:Hollis Mark II systemmanufacturer:ENGINE:Vlar 300 -systemmanufacturer:ARMOR:Protec Tech 12 +systemmanufacturer:ARMOR:ProtecTech 12 systemmanufacturer:COMMUNICATIONS:Dalban Commline systemmanufacturer:TARGETING:Dalban HiRez-B diff --git a/megamek/data/mechfiles/mechs/3039u/Lancelot LNC25-02.mtf b/megamek/data/mechfiles/mechs/3039u/Lancelot LNC25-02.mtf index 4aa5d863a7f..5844c43a558 100644 --- a/megamek/data/mechfiles/mechs/3039u/Lancelot LNC25-02.mtf +++ b/megamek/data/mechfiles/mechs/3039u/Lancelot LNC25-02.mtf @@ -160,7 +160,7 @@ overview:The Lancelot was originally conceived in response to a Star League Defe capabilities: Krupp Technologies attempted to combine the speed of a medium 'Mech with the survivability of a heavy 'Mech in the Lancelot. Despite the use of a lightweight Extralight engine, the production Lancelot ended up in the heavyweight class, but the SLDF was impressed enough with the unit's speed and firepower during its trial runs to make an initial order of 250 in 2581. -deployment:The Lancelot did not survive the loss of Star League technology as well as most of its older cousins. Manufactured by Luthien Armor Works from their huge plant on Luthien, the 02 retained the same weapons array though with different models: a Lord's Light PPC, two Sunglow Heavy Lasers, and a Victory 23R Medium Laser. This came at the expense however of a smaller Pitban 240 fusion engine and nineteen single heat sinks. With a new maximum speed of only 64.8 km/h the thin-skinned Lancelot made for an easy target for other 'Mechs of its weight class, and the less efficient heat dissipation system made it unable to unleash its full firepower safely and consistently; firing both large lasers and the PPC at the same time now entailed risking a shutdown from overheating. LAW also had to replace the Krupp electronics used in the Star League variants, installing a Sipher KIT-4 communications system and a Hawkeye B3 targeting and tracking system. +deployment:The Lancelot did not survive the loss of Star League technology as well as most of its older cousins. Manufactured by Luthien Armor Works from their huge plant on Luthien, the 02 retained the same weapons array though with different models: a Lord's Light PPC, two SunGlow Heavy Lasers, and a Victory 23R Medium Laser. This came at the expense however of a smaller Pitban 240 fusion engine and nineteen single heat sinks. With a new maximum speed of only 64.8 km/h the thin-skinned Lancelot made for an easy target for other 'Mechs of its weight class, and the less efficient heat dissipation system made it unable to unleash its full firepower safely and consistently; firing both large lasers and the PPC at the same time now entailed risking a shutdown from overheating. LAW also had to replace the Krupp electronics used in the Star League variants, installing a Sipher KIT-4 communications system and a Hawkeye B3 targeting and tracking system. history:An entirely energy-based armament allowed the Lancelot to operate away from friendly supply lines for extended periods, while the use of a Hermes 360XL engine not only made it faster than any other heavy 'Mech at the time but also allowed for thirteen double heat sinks to be installed. The use of only nine and a half tons of armor was considered light for its tonnage, however this was partially offset by the design's mobility and its subtle curves, presenting a narrower silhouette for the enemy to target. Its advanced Krupp KBC battle computer, long a standard in the industry, offered superior internal system monitoring, such as current armor status and skin temperature, without distracting the pilot during combat. The most exceptional part of the Lancelot was its KBC Starsight Model 3 T&T System, which could track and prioritize hundreds of targets and projectiles at once. This also made the Lancelot superior at shooting down enemy fighters, and by all indications it was replacing the Rifleman as the SLDF's standard anti-aircraft 'Mech before the Amaris Civil War put an end to that plan. Many Lancelots, along with Krupp's factory on Mars, were destroyed during the Civil War, and as the advanced systems which had gone into their construction became lostech these 'Mechs came to the brink of extinction. Luthien Armor Works obtained copies of the design and began production after the Second Succession War, but their LNC25-02 model was greatly reduced in capability, most significantly the loss of its mobility. With only average speed now and enough armor plating to withstand only a few solid hits, pilots derisively began referring to the 'Mech as "the Coffin." Whereas before the fall of the Star League the Lancelot could be found in almost all militaries, by the end of the Succession Wars less than a dozen still-functional original models were in service, many heavily modified due to battle damage, alongside a few hundred 02 models, most of which were in the hands of the Draconis Combine. In the wake of the Clan Invasion and the Battle of Tukayyid, Precentor Martial Anastasius Focht would rebuild the Krupp Stellar factory on Mars to restart production of original model Lancelots for the Com Guards along with other advanced variants. Examples of these 'Mechs would also be used by the Word of Blake in the prosecution of their Jihad. diff --git a/megamek/data/mechfiles/mechs/3039u/Ostroc OSR-2C.mtf b/megamek/data/mechfiles/mechs/3039u/Ostroc OSR-2C.mtf index 1db3c0a8564..fee185cb2c5 100644 --- a/megamek/data/mechfiles/mechs/3039u/Ostroc OSR-2C.mtf +++ b/megamek/data/mechfiles/mechs/3039u/Ostroc OSR-2C.mtf @@ -162,7 +162,7 @@ capabilities:Its unique walker/pod profile, later seen in the Stalker and Maraud deployment:The Ostroc carries as its primary weapons two Fuersturm-C Large Lasers in the left and right torsos. These give the Ostroc good medium to long range damage capabilities. The Ostroc's secondary weapons are two Fuersturm-b Medium Lasers also mounted in the side torsos and a Totschlagen SRM-4 launcher in the right torso for close-range combat, with one ton of reloads carried in the center torso. While the Ostroc's laser-heavy weapons payload allows it to operate well as a guerrilla fighter since it has limited dependency on supply lines, its short arms are a handicap in close combat, and the shocks of hand-to-hand fighting can easily damage the Fuersturm systems. The nineteen-ton Vlar 300 fusion engine propels the Ostroc to a cruising speed of 86.4 km/h, fast for its size, while fifteen heat sinks provide adequate heat management. Although nine tons of armor provide good protection for the 'Mech, very little is used to protect the arms, meaning the loss of one or both in battle is likely. -history:The best-known of Ostman Industries' Ost Class of 'Mechs, the Ostroc debuted in 2511 and proved so successful in this role production continued for approximately 200 years. While a quality 'Mech, the low production capacity of Ostman Industries made the Ostroc a rarity; indeed the company licensed their other Ost 'Mechs out to Kong Interstellar just to maintain their rate of production, and the majority of those produced were assigned garrison duties within the Terran Hegemony. Still, the 'Mech saw action in every major conflict of the Star League, especially towards the end in the civil war and subsequent First Succession War. The destruction of Ostman Industries meant an end to any new Ostrocs, although all sides of the Succession Wars continued to field these 'Mechs in combat, particularly the Draconis Combine. It was because of the small number and wide dispersal of surviving Ostrocs that the design was largely passed over while others were being updated after the Helm Memory Core discovery. A major revitalization of the design took place within the Capellan Confederation after the Clan Invasion. Having largely rebuilt their forces after the previous decades' setbacks, the Strategios wanted to update the ancient 'Mech, but rather than reverse-engineering the original they ordered all Capellan 'Mech manufacturers to submit bids for a replacement. Ceres Metals was the only one to send in a proposal which matched exactly what they wanted and won the contract, completing the first production run in January 3067. Versions of these new Ostrocs also started showing up in the Taurian Concordat and Circinus Federation, a result of espionage according to Capellan charges. +history:The best-known of Ostmann Industries' Ost Class of 'Mechs, the Ostroc debuted in 2511 and proved so successful in this role production continued for approximately 200 years. While a quality 'Mech, the low production capacity of Ostmann Industries made the Ostroc a rarity; indeed the company licensed their other Ost 'Mechs out to Kong Interstellar just to maintain their rate of production, and the majority of those produced were assigned garrison duties within the Terran Hegemony. Still, the 'Mech saw action in every major conflict of the Star League, especially towards the end in the civil war and subsequent First Succession War. The destruction of Ostmann Industries meant an end to any new Ostrocs, although all sides of the Succession Wars continued to field these 'Mechs in combat, particularly the Draconis Combine. It was because of the small number and wide dispersal of surviving Ostrocs that the design was largely passed over while others were being updated after the Helm Memory Core discovery. A major revitalization of the design took place within the Capellan Confederation after the Clan Invasion. Having largely rebuilt their forces after the previous decades' setbacks, the Strategios wanted to update the ancient 'Mech, but rather than reverse-engineering the original they ordered all Capellan 'Mech manufacturers to submit bids for a replacement. Ceres Metals was the only one to send in a proposal which matched exactly what they wanted and won the contract, completing the first production run in January 3067. Versions of these new Ostrocs also started showing up in the Taurian Concordat and Circinus Federation, a result of espionage according to Capellan charges. manufacturer:Diplass BattleMechs,Kong Interstellar Corporation,Kong Interstellar Corporation,Ostmann Industries primaryfactory:Apollo,Connaught,Loxley,Terra diff --git a/megamek/data/mechfiles/mechs/3039u/Ostroc OSR-2L.mtf b/megamek/data/mechfiles/mechs/3039u/Ostroc OSR-2L.mtf index bf885878420..cbfcbe397c9 100644 --- a/megamek/data/mechfiles/mechs/3039u/Ostroc OSR-2L.mtf +++ b/megamek/data/mechfiles/mechs/3039u/Ostroc OSR-2L.mtf @@ -162,7 +162,7 @@ capabilities:Its unique walker/pod profile, later seen in the Stalker and Maraud deployment:The 2L variant of the Ostroc introduced in 2884 is modified for long range combat. The SRM-4 launcher has been replaced with an LRM-5 launcher, increasing the 'Mechs long-range damage capabilities slightly by sacrificing some of its close range firepower. -history:The best-known of Ostman Industries' Ost Class of 'Mechs, the Ostroc debuted in 2511 and proved so successful in this role production continued for approximately 200 years. While a quality 'Mech, the low production capacity of Ostman Industries made the Ostroc a rarity; indeed the company licensed their other Ost 'Mechs out to Kong Interstellar just to maintain their rate of production, and the majority of those produced were assigned garrison duties within the Terran Hegemony. Still, the 'Mech saw action in every major conflict of the Star League, especially towards the end in the civil war and subsequent First Succession War. The destruction of Ostman Industries meant an end to any new Ostrocs, although all sides of the Succession Wars continued to field these 'Mechs in combat, particularly the Draconis Combine. It was because of the small number and wide dispersal of surviving Ostrocs that the design was largely passed over while others were being updated after the Helm Memory Core discovery. A major revitalization of the design took place within the Capellan Confederation after the Clan Invasion. Having largely rebuilt their forces after the previous decades' setbacks, the Strategios wanted to update the ancient 'Mech, but rather than reverse-engineering the original they ordered all Capellan 'Mech manufacturers to submit bids for a replacement. Ceres Metals was the only one to send in a proposal which matched exactly what they wanted and won the contract, completing the first production run in January 3067. Versions of these new Ostrocs also started showing up in the Taurian Concordat and Circinus Federation, a result of espionage according to Capellan charges. +history:The best-known of Ostmann Industries' Ost Class of 'Mechs, the Ostroc debuted in 2511 and proved so successful in this role production continued for approximately 200 years. While a quality 'Mech, the low production capacity of Ostmann Industries made the Ostroc a rarity; indeed the company licensed their other Ost 'Mechs out to Kong Interstellar just to maintain their rate of production, and the majority of those produced were assigned garrison duties within the Terran Hegemony. Still, the 'Mech saw action in every major conflict of the Star League, especially towards the end in the civil war and subsequent First Succession War. The destruction of Ostmann Industries meant an end to any new Ostrocs, although all sides of the Succession Wars continued to field these 'Mechs in combat, particularly the Draconis Combine. It was because of the small number and wide dispersal of surviving Ostrocs that the design was largely passed over while others were being updated after the Helm Memory Core discovery. A major revitalization of the design took place within the Capellan Confederation after the Clan Invasion. Having largely rebuilt their forces after the previous decades' setbacks, the Strategios wanted to update the ancient 'Mech, but rather than reverse-engineering the original they ordered all Capellan 'Mech manufacturers to submit bids for a replacement. Ceres Metals was the only one to send in a proposal which matched exactly what they wanted and won the contract, completing the first production run in January 3067. Versions of these new Ostrocs also started showing up in the Taurian Concordat and Circinus Federation, a result of espionage according to Capellan charges. manufacturer:Field Refit primaryfactory:Field Refit diff --git a/megamek/data/mechfiles/mechs/3039u/Ostroc OSR-2M.mtf b/megamek/data/mechfiles/mechs/3039u/Ostroc OSR-2M.mtf index 52ef747b4a1..5e9baacdfcf 100644 --- a/megamek/data/mechfiles/mechs/3039u/Ostroc OSR-2M.mtf +++ b/megamek/data/mechfiles/mechs/3039u/Ostroc OSR-2M.mtf @@ -159,7 +159,7 @@ capabilities:Its unique walker/pod profile, later seen in the Stalker and Maraud deployment:An experimental model produced by Kong Interstellar for the Free Worlds League in 2793, the 2M variant of the Ostroc focuses on the 'Mech's maneuverability. Five jump jets, two in each leg and one in the rear torso, have been added to the design, giving it a maximum jumping distance of one hundred and fifty meters. In order to make this change, the medium lasers and the SRM-4 launcher were removed. Relatively few of these were built between the League's annexation of Connaught and the factory's destruction. -history:The best-known of Ostman Industries' Ost Class of 'Mechs, the Ostroc debuted in 2511 and proved so successful in this role production continued for approximately 200 years. While a quality 'Mech, the low production capacity of Ostman Industries made the Ostroc a rarity; indeed the company licensed their other Ost 'Mechs out to Kong Interstellar just to maintain their rate of production, and the majority of those produced were assigned garrison duties within the Terran Hegemony. Still, the 'Mech saw action in every major conflict of the Star League, especially towards the end in the civil war and subsequent First Succession War. The destruction of Ostman Industries meant an end to any new Ostrocs, although all sides of the Succession Wars continued to field these 'Mechs in combat, particularly the Draconis Combine. It was because of the small number and wide dispersal of surviving Ostrocs that the design was largely passed over while others were being updated after the Helm Memory Core discovery. A major revitalization of the design took place within the Capellan Confederation after the Clan Invasion. Having largely rebuilt their forces after the previous decades' setbacks, the Strategios wanted to update the ancient 'Mech, but rather than reverse-engineering the original they ordered all Capellan 'Mech manufacturers to submit bids for a replacement. Ceres Metals was the only one to send in a proposal which matched exactly what they wanted and won the contract, completing the first production run in January 3067. Versions of these new Ostrocs also started showing up in the Taurian Concordat and Circinus Federation, a result of espionage according to Capellan charges. +history:The best-known of Ostmann Industries' Ost Class of 'Mechs, the Ostroc debuted in 2511 and proved so successful in this role production continued for approximately 200 years. While a quality 'Mech, the low production capacity of Ostmann Industries made the Ostroc a rarity; indeed the company licensed their other Ost 'Mechs out to Kong Interstellar just to maintain their rate of production, and the majority of those produced were assigned garrison duties within the Terran Hegemony. Still, the 'Mech saw action in every major conflict of the Star League, especially towards the end in the civil war and subsequent First Succession War. The destruction of Ostmann Industries meant an end to any new Ostrocs, although all sides of the Succession Wars continued to field these 'Mechs in combat, particularly the Draconis Combine. It was because of the small number and wide dispersal of surviving Ostrocs that the design was largely passed over while others were being updated after the Helm Memory Core discovery. A major revitalization of the design took place within the Capellan Confederation after the Clan Invasion. Having largely rebuilt their forces after the previous decades' setbacks, the Strategios wanted to update the ancient 'Mech, but rather than reverse-engineering the original they ordered all Capellan 'Mech manufacturers to submit bids for a replacement. Ceres Metals was the only one to send in a proposal which matched exactly what they wanted and won the contract, completing the first production run in January 3067. Versions of these new Ostrocs also started showing up in the Taurian Concordat and Circinus Federation, a result of espionage according to Capellan charges. manufacturer:Kong Interstellar Corporation primaryfactory:Connaught diff --git a/megamek/data/mechfiles/mechs/3039u/Ostroc OSR-3C.mtf b/megamek/data/mechfiles/mechs/3039u/Ostroc OSR-3C.mtf index 53fd9973a0e..eebf0371d2a 100644 --- a/megamek/data/mechfiles/mechs/3039u/Ostroc OSR-3C.mtf +++ b/megamek/data/mechfiles/mechs/3039u/Ostroc OSR-3C.mtf @@ -159,7 +159,7 @@ capabilities:Its unique walker/pod profile, later seen in the Stalker and Maraud deployment:The 3C variant looks to improve the long-range direct firepower of the Ostroc. Introduced in 2876, the two medium lasers and the SRM-4 have been removed in order to add a third large laser mounted in the right torso. -history:The best-known of Ostman Industries' Ost Class of 'Mechs, the Ostroc debuted in 2511 and proved so successful in this role production continued for approximately 200 years. While a quality 'Mech, the low production capacity of Ostman Industries made the Ostroc a rarity; indeed the company licensed their other Ost 'Mechs out to Kong Interstellar just to maintain their rate of production, and the majority of those produced were assigned garrison duties within the Terran Hegemony. Still, the 'Mech saw action in every major conflict of the Star League, especially towards the end in the civil war and subsequent First Succession War. The destruction of Ostman Industries meant an end to any new Ostrocs, although all sides of the Succession Wars continued to field these 'Mechs in combat, particularly the Draconis Combine. It was because of the small number and wide dispersal of surviving Ostrocs that the design was largely passed over while others were being updated after the Helm Memory Core discovery. A major revitalization of the design took place within the Capellan Confederation after the Clan Invasion. Having largely rebuilt their forces after the previous decades' setbacks, the Strategios wanted to update the ancient 'Mech, but rather than reverse-engineering the original they ordered all Capellan 'Mech manufacturers to submit bids for a replacement. Ceres Metals was the only one to send in a proposal which matched exactly what they wanted and won the contract, completing the first production run in January 3067. Versions of these new Ostrocs also started showing up in the Taurian Concordat and Circinus Federation, a result of espionage according to Capellan charges. +history:The best-known of Ostmann Industries' Ost Class of 'Mechs, the Ostroc debuted in 2511 and proved so successful in this role production continued for approximately 200 years. While a quality 'Mech, the low production capacity of Ostmann Industries made the Ostroc a rarity; indeed the company licensed their other Ost 'Mechs out to Kong Interstellar just to maintain their rate of production, and the majority of those produced were assigned garrison duties within the Terran Hegemony. Still, the 'Mech saw action in every major conflict of the Star League, especially towards the end in the civil war and subsequent First Succession War. The destruction of Ostmann Industries meant an end to any new Ostrocs, although all sides of the Succession Wars continued to field these 'Mechs in combat, particularly the Draconis Combine. It was because of the small number and wide dispersal of surviving Ostrocs that the design was largely passed over while others were being updated after the Helm Memory Core discovery. A major revitalization of the design took place within the Capellan Confederation after the Clan Invasion. Having largely rebuilt their forces after the previous decades' setbacks, the Strategios wanted to update the ancient 'Mech, but rather than reverse-engineering the original they ordered all Capellan 'Mech manufacturers to submit bids for a replacement. Ceres Metals was the only one to send in a proposal which matched exactly what they wanted and won the contract, completing the first production run in January 3067. Versions of these new Ostrocs also started showing up in the Taurian Concordat and Circinus Federation, a result of espionage according to Capellan charges. manufacturer:Field Refit primaryfactory:Field Refit diff --git a/megamek/data/mechfiles/mechs/3039u/Ostsol OTL-4D.mtf b/megamek/data/mechfiles/mechs/3039u/Ostsol OTL-4D.mtf index a20a7c2f75c..73c1c0a2df3 100644 --- a/megamek/data/mechfiles/mechs/3039u/Ostsol OTL-4D.mtf +++ b/megamek/data/mechfiles/mechs/3039u/Ostsol OTL-4D.mtf @@ -159,7 +159,7 @@ Heat Sink -Empty- -Overview: Ostmann Industries had built up a solid portfolio of BattleMechs by 2693, having drawn up and produced the successful Ostwar, Ostsol, and Ostscout designs. Their attempt at a new member of their line-up, a heavy cavalry BattleMech capable of independent operations, would lead to the development of the Ostsol. Their manufacturing lines, however, were already overloaded by demand for the popular Ostsol, leading Ostsmann to partner with Kong Interstellar to manufacture the design on Kong's lines on Connaught. The pact would be profitable for both companies, and the Ostsol became a popular staple in both House armies and SLDF forces. +Overview: Ostmann Industries had built up a solid portfolio of BattleMechs by 2693, having drawn up and produced the successful Ostwar, Ostsol, and Ostscout designs. Their attempt at a new member of their line-up, a heavy cavalry BattleMech capable of independent operations, would lead to the development of the Ostsol. Their manufacturing lines, however, were already overloaded by demand for the popular Ostsol, leading Ostmann to partner with Kong Interstellar to manufacture the design on Kong's lines on Connaught. The pact would be profitable for both companies, and the Ostsol became a popular staple in both House armies and SLDF forces. Capabilities: The Ostsol was created to fulfill a contract for a rapid heavy BattleMech with a fully energy-based armament. In this, Ostmann Industries was successful. The Ostsol has offered sterling service as a heavy cavalry design since its inception, and the shattered supply lines of the Succession Wars did little to reduce the 'Mech's effectiveness. The TRSS.2L3 sensors, reused after their outstanding use on the Ostscout, give the Ostsol excellent data gathering capabilities for a 'Mech of its role. However, just as with the earlier Ostroc, the Ostsol suffers from fragile arms and often loses them in combat. diff --git a/megamek/data/mechfiles/mechs/3039u/Ostsol OTL-4F.mtf b/megamek/data/mechfiles/mechs/3039u/Ostsol OTL-4F.mtf index b1b226ecca3..f173e722572 100644 --- a/megamek/data/mechfiles/mechs/3039u/Ostsol OTL-4F.mtf +++ b/megamek/data/mechfiles/mechs/3039u/Ostsol OTL-4F.mtf @@ -154,7 +154,7 @@ Heat Sink -Empty- -Overview: Ostmann Industries had built up a solid portfolio of BattleMechs by 2693, having drawn up and produced the successful Ostwar, Ostsol, and Ostscout designs. Their attempt at a new member of their line-up, a heavy cavalry BattleMech capable of independent operations, would lead to the development of the Ostsol. Their manufacturing lines, however, were already overloaded by demand for the popular Ostsol, leading Ostsmann to partner with Kong Interstellar to manufacture the design on Kong's lines on Connaught. The pact would be profitable for both companies, and the Ostsol became a popular staple in both House armies and SLDF forces. +Overview: Ostmann Industries had built up a solid portfolio of BattleMechs by 2693, having drawn up and produced the successful Ostwar, Ostsol, and Ostscout designs. Their attempt at a new member of their line-up, a heavy cavalry BattleMech capable of independent operations, would lead to the development of the Ostsol. Their manufacturing lines, however, were already overloaded by demand for the popular Ostsol, leading Ostmann to partner with Kong Interstellar to manufacture the design on Kong's lines on Connaught. The pact would be profitable for both companies, and the Ostsol became a popular staple in both House armies and SLDF forces. Capabilities: The Ostsol was created to fulfill a contract for a rapid heavy BattleMech with a fully energy-based armament. In this, Ostmann Industries was successful. The Ostsol has offered sterling service as a heavy cavalry design since its inception, and the shattered supply lines of the Succession Wars did little to reduce the 'Mech's effectiveness. The TRSS.2L3 sensors, reused after their outstanding use on the Ostscout, give the Ostsol excellent data gathering capabilities for a 'Mech of its role. However, just as with the earlier Ostroc, the Ostsol suffers from fragile arms and often loses them in combat. diff --git a/megamek/data/mechfiles/mechs/3039u/Thug THG-10E.mtf b/megamek/data/mechfiles/mechs/3039u/Thug THG-10E.mtf index 91d31726219..d4e317cb5ee 100644 --- a/megamek/data/mechfiles/mechs/3039u/Thug THG-10E.mtf +++ b/megamek/data/mechfiles/mechs/3039u/Thug THG-10E.mtf @@ -156,7 +156,7 @@ Foot Actuator overview:The Thug was designed by Maltex Corporation as a direct competitor to the popular Warhammer BattleMech. First seeing production in 2572. -capabilities:The armament on the Thug is a very simple, yet effective, combination. The 10E is a downgraded version of the 11E produced by Earthwerks Incorporated following the destruction of Maltex's facilities in 2835. The primary changes come from the loss of the double heat sinks, CASE, and the Endo Steel structure. To compensate for the weight needed for a standard structure, the SRMs have been downgraded from six tube launchers to Holly SRM-4s. In addition, the Thug lost one ton of ammunition. While this version can still compete with the Warhammer and boast superior armor protection, the replacement of its double heat sinks with single heat sinks takes away its greatest advantage. Its communications and targeting-tracking systems were also replaced with a Colmax-025 and Instatrack Mark XV. +capabilities:The armament on the Thug is a very simple, yet effective, combination. The 10E is a downgraded version of the 11E produced by Earthwerks Incorporated following the destruction of Maltex's facilities in 2835. The primary changes come from the loss of the double heat sinks, CASE, and the Endo Steel structure. To compensate for the weight needed for a standard structure, the SRMs have been downgraded from six tube launchers to Holly SRM-4s. In addition, the Thug lost one ton of ammunition. While this version can still compete with the Warhammer and boast superior armor protection, the replacement of its double heat sinks with single heat sinks takes away its greatest advantage. Its communications and targeting-tracking systems were also replaced with a Colmax-025 and Instatrac Mark XV. history:The Thug sought to directly address some of the challenges which faced the Warhammer, chief of which was to increase armor protection without sacrificing firepower. When compared side-by-side, the Thug has a great many advantages over the Warhammer, yet it never wholly replaced the venerable 'Mech. Still the Thug proved popular enough that Maltex Corporation was forced to contract Earthwerks Incorporated to produce the Thug on Keystone in order to meet demand. Although it has had its detractors, the Thug has proven itself for over five hundred years to be the quintessential "zombie 'Mech." Production of the Thug from Maltex's original factory on Errai ceased when it was destroyed in 2835, one of many causalities of the Succession Wars, leaving only Earthwerks to continue building new Thugs at a rate of twelve per year. Unfortunately the same terrible conflict resulted in the loss of much advanced knowledge and technology, threatening their ability to keep even this meager production rate up. In a twist of fate it was the Warhammer which helped keep the Thug production line alive: with the loss of their original PPC weaponry, Earthwerks instead reworked the design to make use of the extensive stockpile of Donal PPCs used by the Warhammer, allowing new Thugs to be built and repairs to be made more easily. Beyond the few still in service to the Great Houses the largest user of Thugs was ComStar, a fact confirmed upon the reveal of their Com Guards. Eventually the recovery of lostech would allow both Earthwerks and Maltex to restart production of original-model Thugs during the 3050s. These were supplanted by new variants which, following the formation of the Second Star League, were supplied to ComStar, the SLDF, the Draconis Combine and Federated Suns. New Thugs were also built for the Word of Blake and those forces of the Free Worlds League aligned with them during the Jihad. diff --git a/megamek/data/mechfiles/mechs/3039u/UrbanMech UM-R60.mtf b/megamek/data/mechfiles/mechs/3039u/UrbanMech UM-R60.mtf index 1b0f5fff641..5680a5da940 100644 --- a/megamek/data/mechfiles/mechs/3039u/UrbanMech UM-R60.mtf +++ b/megamek/data/mechfiles/mechs/3039u/UrbanMech UM-R60.mtf @@ -161,7 +161,7 @@ capabilities:This was achieved by starting with a cheap, easily-produced chassis deployment:The UrbanMech packs a powerful punch for its size. The standard version carries an Imperator-B Autocannon/10 in its right arm and as a backup weapon it carries a Harmon Light Small Laser in the left arm for suppressing infantry. With these two weapons the UrbanMech can constantly harass, or if piloted by an experienced enough MechWarrior, down 'Mechs up to twice its own size. A single ton of ammo for the autocannon, located in the right torso, leaves little endurance for a prolonged fight, though it fits in perfectly with the hit-and-run nature of the 'Mech; one way or another most observers agree the UrbanMech is good for about two minutes of combat. -history:Large numbers of UrbanMechs were produced by Orguss Industries from 2675 until the destruction of their assembly lines. The UrbanMech reentered production at the Betelgeuse facility of Hellespont Industrials during the Jihad, and continued to be manufactured up through 3149. As such, UrbanMechs could be found in all of the armies of the Successor States. However most military leaders saw the slow little 'Mech as a liability, confining their stockpiles to garrison duty or stripping them of parts. This dismissive attitude towards the UrbanMech saved it from the ravages of the Succession Wars and ensured its continued use into the thirty-first century. The Capellan Confederation remained the largest and only user of UrbanMechs to actually deploy them for front-line duty, a result of the devastation of the Fourth Succession War and their desperation for any 'Mech to replenish their losses. The Confederation Reserve Cavalry and Capellan Defense Force had the lion's share of UrbanMechs, followed by the Tikonov Republican Guard and St. Ives Armored Cavalry; outside the Confederation the Federated Suns' Capellan March Militia fielded the largest number of UrbanMechs due to the fact it was composed of large amounts of captured Capellan equipment. Its prominence within the Confederation meant the UrbanMech was among those 'Mechs within the CCAF to receive upgrades following the recovery of lostech; the other States followed suit with much less priority over improving other 'Mechs. Despite this the sheer costs necessary to replace the UrbanMech's engine and increase its top speed meant even the Confederation limited their refit packages to improving the weapons and armor only. A testament to the desperation of the Word of Blake Jihad, Hellespont Industrials would reactivate a shuttered production facility on Betelgeuse to produce the UrbanMech alongside primitive "retrotech" designs for material starved Capellan garrison forces. This plant would maintain production of the UrbanMech in a steadily increasing volume of configurations throughout the Dark Age Era as the CCAF secretly expanded before it waged war against the Republic of the Sphere. Rather than dramatic and expensive enhancements, Hellespont's new variants retain the venerable design's low ground speed urban combat focus and can be applied as refits as readily as new production. +history:Large numbers of UrbanMechs were produced by Orgus Industries from 2675 until the destruction of their assembly lines. The UrbanMech reentered production at the Betelgeuse facility of Hellespont Industrials during the Jihad, and continued to be manufactured up through 3149. As such, UrbanMechs could be found in all of the armies of the Successor States. However most military leaders saw the slow little 'Mech as a liability, confining their stockpiles to garrison duty or stripping them of parts. This dismissive attitude towards the UrbanMech saved it from the ravages of the Succession Wars and ensured its continued use into the thirty-first century. The Capellan Confederation remained the largest and only user of UrbanMechs to actually deploy them for front-line duty, a result of the devastation of the Fourth Succession War and their desperation for any 'Mech to replenish their losses. The Confederation Reserve Cavalry and Capellan Defense Force had the lion's share of UrbanMechs, followed by the Tikonov Republican Guard and St. Ives Armored Cavalry; outside the Confederation the Federated Suns' Capellan March Militia fielded the largest number of UrbanMechs due to the fact it was composed of large amounts of captured Capellan equipment. Its prominence within the Confederation meant the UrbanMech was among those 'Mechs within the CCAF to receive upgrades following the recovery of lostech; the other States followed suit with much less priority over improving other 'Mechs. Despite this the sheer costs necessary to replace the UrbanMech's engine and increase its top speed meant even the Confederation limited their refit packages to improving the weapons and armor only. A testament to the desperation of the Word of Blake Jihad, Hellespont Industrials would reactivate a shuttered production facility on Betelgeuse to produce the UrbanMech alongside primitive "retrotech" designs for material starved Capellan garrison forces. This plant would maintain production of the UrbanMech in a steadily increasing volume of configurations throughout the Dark Age Era as the CCAF secretly expanded before it waged war against the Republic of the Sphere. Rather than dramatic and expensive enhancements, Hellespont's new variants retain the venerable design's low ground speed urban combat focus and can be applied as refits as readily as new production. manufacturer:Orgus Industries primaryfactory:Marcus diff --git a/megamek/data/mechfiles/mechs/3039u/UrbanMech UM-R60L.mtf b/megamek/data/mechfiles/mechs/3039u/UrbanMech UM-R60L.mtf index 6f86aefc344..7a44c7642e1 100644 --- a/megamek/data/mechfiles/mechs/3039u/UrbanMech UM-R60L.mtf +++ b/megamek/data/mechfiles/mechs/3039u/UrbanMech UM-R60L.mtf @@ -160,7 +160,7 @@ capabilities:This was achieved by starting with a cheap, easily-produced chassis deployment:Generally associated with the Capellan Confederation, who have modified a few of their UrbanMechs in this fashion, the -R60L is an upgrade to make the UrbanMech twice as deadly as the -R60 version. The -R60L sacrifices two tons of armor, allowing it to replace the Imperator-B Autocannon/10 with an Imperator-Zeta Autocannon/20 that is capable of downing most light 'Mechs and severely damaging most medium 'Mechs in a single salvo. Besides the thinner armor this modification comes with a very limited ammunition supply, which makes it unpopular. -history:Large numbers of UrbanMechs were produced by Orguss Industries from 2675 until the destruction of their assembly lines. The UrbanMech reentered production at the Betelgeuse facility of Hellespont Industrials during the Jihad, and continued to be manufactured up through 3149. As such, UrbanMechs could be found in all of the armies of the Successor States. However most military leaders saw the slow little 'Mech as a liability, confining their stockpiles to garrison duty or stripping them of parts. This dismissive attitude towards the UrbanMech saved it from the ravages of the Succession Wars and ensured its continued use into the thirty-first century. The Capellan Confederation remained the largest and only user of UrbanMechs to actually deploy them for front-line duty, a result of the devastation of the Fourth Succession War and their desperation for any 'Mech to replenish their losses. The Confederation Reserve Cavalry and Capellan Defense Force had the lion's share of UrbanMechs, followed by the Tikonov Republican Guard and St. Ives Armored Cavalry; outside the Confederation the Federated Suns' Capellan March Militia fielded the largest number of UrbanMechs due to the fact it was composed of large amounts of captured Capellan equipment. Its prominence within the Confederation meant the UrbanMech was among those 'Mechs within the CCAF to receive upgrades following the recovery of lostech; the other States followed suit with much less priority over improving other 'Mechs. Despite this the sheer costs necessary to replace the UrbanMech's engine and increase its top speed meant even the Confederation limited their refit packages to improving the weapons and armor only. A testament to the desperation of the Word of Blake Jihad, Hellespont Industrials would reactivate a shuttered production facility on Betelgeuse to produce the UrbanMech alongside primitive "retrotech" designs for material starved Capellan garrison forces. This plant would maintain production of the UrbanMech in a steadily increasing volume of configurations throughout the Dark Age Era as the CCAF secretly expanded before it waged war against the Republic of the Sphere. Rather than dramatic and expensive enhancements, Hellespont's new variants retain the venerable design's low ground speed urban combat focus and can be applied as refits as readily as new production. +history:Large numbers of UrbanMechs were produced by Orgus Industries from 2675 until the destruction of their assembly lines. The UrbanMech reentered production at the Betelgeuse facility of Hellespont Industrials during the Jihad, and continued to be manufactured up through 3149. As such, UrbanMechs could be found in all of the armies of the Successor States. However most military leaders saw the slow little 'Mech as a liability, confining their stockpiles to garrison duty or stripping them of parts. This dismissive attitude towards the UrbanMech saved it from the ravages of the Succession Wars and ensured its continued use into the thirty-first century. The Capellan Confederation remained the largest and only user of UrbanMechs to actually deploy them for front-line duty, a result of the devastation of the Fourth Succession War and their desperation for any 'Mech to replenish their losses. The Confederation Reserve Cavalry and Capellan Defense Force had the lion's share of UrbanMechs, followed by the Tikonov Republican Guard and St. Ives Armored Cavalry; outside the Confederation the Federated Suns' Capellan March Militia fielded the largest number of UrbanMechs due to the fact it was composed of large amounts of captured Capellan equipment. Its prominence within the Confederation meant the UrbanMech was among those 'Mechs within the CCAF to receive upgrades following the recovery of lostech; the other States followed suit with much less priority over improving other 'Mechs. Despite this the sheer costs necessary to replace the UrbanMech's engine and increase its top speed meant even the Confederation limited their refit packages to improving the weapons and armor only. A testament to the desperation of the Word of Blake Jihad, Hellespont Industrials would reactivate a shuttered production facility on Betelgeuse to produce the UrbanMech alongside primitive "retrotech" designs for material starved Capellan garrison forces. This plant would maintain production of the UrbanMech in a steadily increasing volume of configurations throughout the Dark Age Era as the CCAF secretly expanded before it waged war against the Republic of the Sphere. Rather than dramatic and expensive enhancements, Hellespont's new variants retain the venerable design's low ground speed urban combat focus and can be applied as refits as readily as new production. manufacturer:Refit primaryfactory:Various diff --git a/megamek/data/mechfiles/mechs/3039u/Vulcan VL-2T.mtf b/megamek/data/mechfiles/mechs/3039u/Vulcan VL-2T.mtf index 6ef07bf9938..e1429f883a0 100644 --- a/megamek/data/mechfiles/mechs/3039u/Vulcan VL-2T.mtf +++ b/megamek/data/mechfiles/mechs/3039u/Vulcan VL-2T.mtf @@ -155,7 +155,7 @@ overview:The Vulcan was designed as an anti-infantry 'Mech in 2775 during the cl capabilities:The Vulcan is lightly armored at only five tons, though this is typically sufficient when facing infantry forces and its narrow profile makes it a harder target to hit. A cruising speed of 97.2 km/h is enhanced by six jump jets mounted in the rear of the Vulcan's torso, specially vented to reduce heat buildup, giving it a jumping range of 180 meters. deployment:The Vulcan's primary weapons are a Firestorm Flamer mounted in the right arm and a Sperry Browning Machine Gun in the left arm, fed by one ton of ammunition stored in the left torso. To give it some anti-'Mech firepower the Vulcan was given a reliable Armstrong Autocannon/2 with one ton of ammo, both mounted in the right torso, however it performed poorly in this regard and was most often employed as an anti-building weapon. A Randell medium laser in the left torso served as a backup weapon for the autocannon, while ten heat sinks are used to keep the 'Mech cool. Its one true deficiency was the lack of manipulative hands, limiting its ability to engage in close combat fighting with other 'Mechs. history:As the SLDF battled Republican troops in the streets and thoroughfares of the Terran Hegemony, many 'Mechs were destroyed by dug-in infantry during these urban battles. In response to this problem, MatherTechno Inc. designed the Vulcan to pack weaponry capable of taking out large numbers of enemy troops and capable of unparalleled mobility in an urban environment, though not intended to engage in all-out battles with larger 'Mechs. The Vulcan's distinct profile would eventually give rise to its nickname "Scarecrow." Production of the Vulcan began as soon as MatherTechno's factory on Northwind was liberated by the SLDF, with Aleksandr Kerensky himself specifically ordering their production lines converted to produce the Vulcan. The design's baptism of fire came during Operation Liberation, the final battle of the civil war to liberate Terra from Stefan Amaris, where it served as part of the Volunteer Regiments and earned its reputation as a tough city fighter. Each of the Great Houses had a sizable number of Vulcans at the start of the First Succession War when, just a few months into the conflict, MatherTechno's factory on Northwind was destroyed. Only the Lyran Commonwealth and Free Worlds League managed to acquire the design specifications for the Vulcan and keep it in limited production throughout the rest of the Succession Wars, with the League awarding the schematics to Nimakachi Fusion Products Limited and the Commonwealth giving theirs to Coventry Metal Works. Of the other Great Houses the Capellan Confederation had the fewest number of Vulcans as a result of the loss of Sappho, where the majority of their Vulcans were stationed, to House Marik during the Second Succession War. The Federated Suns kept their Vulcans going thanks to several spare part supply dumps located in their territory, and used the 'Mech extensively during the reconquest of Kentares IV. The majority of the Draconis Combine's Vulcan inventory was used during a raid on Dobson in 3020 where they decimated several key Davion aerospace fighter bases. Following the recovery of several lostech components Nimakachi was able to create a new variant, the VT-5M, and begin limited production in 3050, eventually increasing their lines to produce twenty a month. Coventry Metal Works produced their own upgraded variant around the same time, the VT-5S, which played a pivotal role during the FedCom Civil War as part of the Allied forces. The Word of Blake purchased a number of Vulcans in preparation for their seizure of Terra in 3058, codenamed Operation Odysseus. The Blakists would go on to seize more Vulcans after the start of the Jihad following their sacking of Nimakachi's Tematagi plant in 3069, with many transferred to the Protectorate Militia for policing duties. -manufacturer:Coventry Metal Works,MaltherTechno Inc.,Nimakachi Fusion Products Ltd., +manufacturer:Coventry Metal Works,MatherTechno Inc.,Nimakachi Fusion Products Ltd., primaryfactory:Coventry,Northwind,Tematagi systemmanufacturer:CHASSIS:Mather Tech 500 systemmanufacturer:ENGINE:Pitban 240 diff --git a/megamek/data/mechfiles/mechs/3039u/Vulcan VL-5T.mtf b/megamek/data/mechfiles/mechs/3039u/Vulcan VL-5T.mtf index fbf8c2d1191..33f1125ffe2 100644 --- a/megamek/data/mechfiles/mechs/3039u/Vulcan VL-5T.mtf +++ b/megamek/data/mechfiles/mechs/3039u/Vulcan VL-5T.mtf @@ -162,7 +162,7 @@ deployment:The Vulcan's primary weapons are a Firestorm Flamer mounted in the ri history:As the SLDF battled Republican troops in the streets and thoroughfares of the Terran Hegemony, many 'Mechs were destroyed by dug-in infantry during these urban battles. In response to this problem, MatherTechno Inc. designed the Vulcan to pack weaponry capable of taking out large numbers of enemy troops and capable of unparalleled mobility in an urban environment, though not intended to engage in all-out battles with larger 'Mechs. The Vulcan's distinct profile would eventually give rise to its nickname "Scarecrow." Production of the Vulcan began as soon as MatherTechno's factory on Northwind was liberated by the SLDF, with Aleksandr Kerensky himself specifically ordering their production lines converted to produce the Vulcan. The design's baptism of fire came during Operation Liberation, the final battle of the civil war to liberate Terra from Stefan Amaris, where it served as part of the Volunteer Regiments and earned its reputation as a tough city fighter. Each of the Great Houses had a sizable number of Vulcans at the start of the First Succession War when, just a few months into the conflict, MatherTechno's factory on Northwind was destroyed. Only the Lyran Commonwealth and Free Worlds League managed to acquire the design specifications for the Vulcan and keep it in limited production throughout the rest of the Succession Wars, with the League awarding the schematics to Nimakachi Fusion Products Limited and the Commonwealth giving theirs to Coventry Metal Works. Of the other Great Houses the Capellan Confederation had the fewest number of Vulcans as a result of the loss of Sappho, where the majority of their Vulcans were stationed, to House Marik during the Second Succession War. The Federated Suns kept their Vulcans going thanks to several spare part supply dumps located in their territory, and used the 'Mech extensively during the reconquest of Kentares IV. The majority of the Draconis Combine's Vulcan inventory was used during a raid on Dobson in 3020 where they decimated several key Davion aerospace fighter bases. Following the recovery of several lostech components Nimakachi was able to create a new variant, the VT-5M, and begin limited production in 3050, eventually increasing their lines to produce twenty a month. Coventry Metal Works produced their own upgraded variant around the same time, the VT-5S, which played a pivotal role during the FedCom Civil War as part of the Allied forces. The Word of Blake purchased a number of Vulcans in preparation for their seizure of Terra in 3058, codenamed Operation Odysseus. The Blakists would go on to seize more Vulcans after the start of the Jihad following their sacking of Nimakachi's Tematagi plant in 3069, with many transferred to the Protectorate Militia for policing duties. -manufacturer:MaltherTechno Inc. +manufacturer:MatherTechno Inc. primaryfactory:Northwind systemmanufacturer:CHASSIS:Mather Tech 500 systemmanufacturer:ENGINE:Pitban 240 diff --git a/megamek/data/mechfiles/mechs/3039u/Wasp WSP-1A.mtf b/megamek/data/mechfiles/mechs/3039u/Wasp WSP-1A.mtf index 9ba2bd35a80..1d4e0bff178 100644 --- a/megamek/data/mechfiles/mechs/3039u/Wasp WSP-1A.mtf +++ b/megamek/data/mechfiles/mechs/3039u/Wasp WSP-1A.mtf @@ -163,12 +163,12 @@ deployment:The primary weapon is a Diverse Optics Type 2 Medium Laser carried in history:The classic WSP-1A had a ground speed that could be considered lackluster when compared to many modern light 'Mechs, but this was offset by its jump capability. While carrying heavier weapons than 'Mechs like the Locust, the Wasp would generally only engage other light 'Mechs, using its jump capabilities to avoid conflicts with larger foes. The Wasp was also used in the role of raider because of its ability to hit and fade in rough terrain. Even after the sheer destruction of the Succession Wars, the Wasp still remained the most numerous 'Mech ahead of the Locust and Stinger; many thousands were in use by all of the Great Houses and in the Periphery while a hundred more were built each year from factories across known space. Nearly half of all newly-built Wasps came from IBMU's and Kali Yama's factories located in the Free Worlds League on Shiro III and Kalidasa respectively. Among other major Inner Sphere Wasp manufacturing sites were Defiance Industries' Furillo factory within the Lyran Commonwealth and Archenar BattleMechs on New Avalon within the Federated Suns. Many of the Great Houses had Wasp variants built specifically for them, as did Wolf's Dragoons. Out in the Periphery the Wasp was manufactured on Taurus, Perdition, Canopus IV and Alpheratz, making it equally common among the Periphery States. The reintroduction of Star League lostech was used to update the ancient design with modern improvements, starting first with the WSP-1S built by Defiance for the Federated Commonwealth. This was followed by the new WSP-3W built specifically for Wolf's Dragoons by Archenar, then the WSP-3M built by IBMU and Kali Yama. Another wave of updates came when Vicore Industries began to peddle their "Project Phoenix" program and found a willing buyer in Hellespont Industries. Requiring only minor changes to their production line, these new more mobile, more stealthy WSP-3Ls debuted in late July of 3067, and within the Capellan Confederation Armed Forces was used with new Raven and Phoenix Hawk models to form Shadow Lances. Taurus Territorial and Detroit Consolidated also began building these new Wasps under license from Hellespont, while Defiance designed their own updated version of the Wasp, the WSP-3S, which was then licensed to Archenar. -manufacturer:Alliance Defenders Limited,Bordello Military Goods Inc,Diplass BattleMechs,Majesty Metals and Manufacturing,King Dumount Defense Facility,Defiance Industries,Pride of Granada Industries,Kali Yama Weapons Industries Inc,Orguss Industries,General Mechanics,Achernar Battlemechs,Lyran 'Mech Corporation,Amalgamated Sword and Steel,Rim Motors,Pinard Protectorates Limited,Interstellar Arms,Irian BattleMechs Unlimited,Hellespont 'Mech Works,Taurus Territorial Industries, Majesty Metals and Manufacturing +manufacturer:Alliance Defenders Limited,Bordello Military Goods Inc,Diplass BattleMechs,Majesty Metals and Manufacturing,King Dumount Defense Facility,Defiance Industries,Pride of Granada Industries,Kali Yama Weapons Industries Inc,Orgus Industries,General Mechanics,Achernar Battlemechs,Lyran 'Mech Corporation,Amalgamated Sword and Steel,Rim Motors,Pinard Protectorates Limited,Interstellar Arms,Irian BattleMechs Unlimited,Hellespont 'Mech Works,Taurus Territorial Industries, Majesty Metals and Manufacturing primaryfactory:Alpheratz,Antwerp,Apollo,Canopus IV,Castile,Furillo,Granada,Kalidasa,Marcus,Mars,New Avalon,Nichol's Rest, Oldsmith,Otisberg,Perdition,Rockwellawan,Shiro III,Sian,Taurus,Tetski systemmanufacturer:CHASSIS:1A Type 3 systemmanufacturer:ENGINE:Hermes 120 systemmanufacturer:ARMOR:Durallex Light systemmanufacturer:JUMPJET:Rawlings 52 -systemmanufacturer:COMMUNICATIONS:Duotech 65 +systemmanufacturer:COMMUNICATIONS:Duoteck 65 systemmanufacturer:TARGETING:RadCom TXX diff --git a/megamek/data/mechfiles/mechs/3039u/Wasp WSP-1D.mtf b/megamek/data/mechfiles/mechs/3039u/Wasp WSP-1D.mtf index 039734b2a9b..65c4649c6a4 100644 --- a/megamek/data/mechfiles/mechs/3039u/Wasp WSP-1D.mtf +++ b/megamek/data/mechfiles/mechs/3039u/Wasp WSP-1D.mtf @@ -171,5 +171,5 @@ systemmanufacturer:CHASSIS:1A Type 3 systemmanufacturer:ENGINE:Hermes 120 systemmanufacturer:ARMOR:Durallex Light systemmanufacturer:JUMPJET:Rawlings 52 -systemmanufacturer:COMMUNICATIONS:Duotech 65 +systemmanufacturer:COMMUNICATIONS:Duoteck 65 systemmanufacturer:TARGETING:RadCom TXX diff --git a/megamek/data/mechfiles/mechs/3039u/Wasp WSP-1K.mtf b/megamek/data/mechfiles/mechs/3039u/Wasp WSP-1K.mtf index b9d2f5fce93..3fc0ab6f5ab 100644 --- a/megamek/data/mechfiles/mechs/3039u/Wasp WSP-1K.mtf +++ b/megamek/data/mechfiles/mechs/3039u/Wasp WSP-1K.mtf @@ -169,5 +169,5 @@ systemmanufacturer:CHASSIS:1A Type 3 systemmanufacturer:ENGINE:Hermes 120 systemmanufacturer:ARMOR:Durallex Light systemmanufacturer:JUMPJET:Rawlings 52 -systemmanufacturer:COMMUNICATIONS:Duotech 65 +systemmanufacturer:COMMUNICATIONS:Duoteck 65 systemmanufacturer:TARGETING:RadCom TXX diff --git a/megamek/data/mechfiles/mechs/3039u/Wasp WSP-1L.mtf b/megamek/data/mechfiles/mechs/3039u/Wasp WSP-1L.mtf index a6ea203c439..7da4fc28e74 100644 --- a/megamek/data/mechfiles/mechs/3039u/Wasp WSP-1L.mtf +++ b/megamek/data/mechfiles/mechs/3039u/Wasp WSP-1L.mtf @@ -168,5 +168,5 @@ systemmanufacturer:CHASSIS:1A Type 3 systemmanufacturer:ENGINE:Hermes 120 systemmanufacturer:ARMOR:Durallex Light systemmanufacturer:JUMPJET:Rawlings 52 -systemmanufacturer:COMMUNICATIONS:Duotech 65 +systemmanufacturer:COMMUNICATIONS:Duoteck 65 systemmanufacturer:TARGETING:RadCom TXX diff --git a/megamek/data/mechfiles/mechs/3039u/Wasp WSP-1W.mtf b/megamek/data/mechfiles/mechs/3039u/Wasp WSP-1W.mtf index c6ccef349ba..620e5efecd1 100644 --- a/megamek/data/mechfiles/mechs/3039u/Wasp WSP-1W.mtf +++ b/megamek/data/mechfiles/mechs/3039u/Wasp WSP-1W.mtf @@ -173,5 +173,5 @@ systemmanufacturer:CHASSIS:1A Type 3 systemmanufacturer:ENGINE:Hermes 120 systemmanufacturer:ARMOR:Durallex Light systemmanufacturer:JUMPJET:Rawlings 52 -systemmanufacturer:COMMUNICATIONS:Duotech 65 +systemmanufacturer:COMMUNICATIONS:Duoteck 65 systemmanufacturer:TARGETING:RadCom TXX diff --git a/megamek/data/mechfiles/mechs/3050U/Black Knight BL-12-KNT.mtf b/megamek/data/mechfiles/mechs/3050U/Black Knight BL-12-KNT.mtf index 0e69d660c93..db3a31c33ca 100644 --- a/megamek/data/mechfiles/mechs/3050U/Black Knight BL-12-KNT.mtf +++ b/megamek/data/mechfiles/mechs/3050U/Black Knight BL-12-KNT.mtf @@ -159,7 +159,7 @@ Endo-Steel overview:The Black Knight was introduced in 2578 both as a front-line combatant and as a command BattleMech at the company and battalion level for the Star League Defense Force. -capabilities:Thirteen tons of armor protection on an Endo Steel frame allows the Black Knight to withstand significant punishment. The biggest disadvantage of the design is its challenging heat curve, though the fact that it mounts twenty heat sinks ensures that the Black Knight can still disperse a significant amount of heat produced by its weapons. However, if the 'Mech is involved in a prolonged combat situation, a less experienced MechWarrior who is not competent at heat management may be in trouble. The Black Knight's superior communications equipment allowed it to readily coordinate a whole company of 'Mechs at the same time, as well as link together the command frequencies of an entire parent regiment and connect with orbital support satellites. Improved construction materials provided the Black Knight with a light but sturdy chassis capable of carrying more weaponry and armor for less weight. With the type and amount of weapons carried by the 'Mech, the only challenge the Black Knight faces is heat management. +capabilities:Thirteen tons of armor protection on an Endo Steel frame allows the Black Knight to withstand significant punishment. The biggest disadvantage of the design is its challenging heat curve, though the fact that it mounts sixteen double heat sinks ensures that the Black Knight can still disperse a significant amount of heat produced by its weapons. However, if the 'Mech is involved in a prolonged combat situation, a less experienced MechWarrior who is not competent at heat management may be in trouble. The Black Knight's superior communications equipment allowed it to readily coordinate a whole company of 'Mechs at the same time, as well as link together the command frequencies of an entire parent regiment and connect with orbital support satellites. Improved construction materials provided the Black Knight with a light but sturdy chassis capable of carrying more weaponry and armor for less weight. With the type and amount of weapons carried by the 'Mech, the only challenge the Black Knight faces is heat management. deployment:The BL-12 was probably the most technologically advanced version of the Black Knight leading up to the Jihad. While still based on the original BL-6 model, this design goes in a completely different direction from the BL-9. Introduced in 3063 the first thing that was done to the BL-12 was the upgrade of all of the medium lasers and the PPC to extended range versions, then its single heat sinks were upgraded to double strength versions, reducing the total number from twenty to sixteen. Finally, all of the weapons were mated to a Targeting Computer. diff --git a/megamek/data/mechfiles/mechs/3050U/Black Knight BL6b-KNT.mtf b/megamek/data/mechfiles/mechs/3050U/Black Knight BL6b-KNT.mtf index 2ab3d4a941f..e28f9fb5df0 100644 --- a/megamek/data/mechfiles/mechs/3050U/Black Knight BL6b-KNT.mtf +++ b/megamek/data/mechfiles/mechs/3050U/Black Knight BL6b-KNT.mtf @@ -161,7 +161,7 @@ Endo Steel overview:The Black Knight was introduced in 2578 both as a front-line combatant and as a command BattleMech at the company and battalion level for the Star League Defense Force. -capabilities:Thirteen tons of armor protection on an Endo Steel frame allows the Black Knight to withstand significant punishment. The biggest disadvantage of the design is its challenging heat curve, though the fact that it mounts twenty heat sinks ensures that the Black Knight can still disperse a significant amount of heat produced by its weapons. However, if the 'Mech is involved in a prolonged combat situation, a less experienced MechWarrior who is not competent at heat management may be in trouble. The Black Knight's superior communications equipment allowed it to readily coordinate a whole company of 'Mechs at the same time, as well as link together the command frequencies of an entire parent regiment and connect with orbital support satellites. Improved construction materials provided the Black Knight with a light but sturdy chassis capable of carrying more weaponry and armor for less weight. With the type and amount of weapons carried by the 'Mech, the only challenge the Black Knight faces is heat management. +capabilities:Thirteen tons of armor protection on an Endo Steel frame allows the Black Knight to withstand significant punishment. The biggest disadvantage of the design is its challenging heat curve, though the fact that it mounts sixteen double heat sinks ensures that the Black Knight can still disperse a significant amount of heat produced by its weapons. However, if the 'Mech is involved in a prolonged combat situation, a less experienced MechWarrior who is not competent at heat management may be in trouble. The Black Knight's superior communications equipment allowed it to readily coordinate a whole company of 'Mechs at the same time, as well as link together the command frequencies of an entire parent regiment and connect with orbital support satellites. Improved construction materials provided the Black Knight with a light but sturdy chassis capable of carrying more weaponry and armor for less weight. With the type and amount of weapons carried by the 'Mech, the only challenge the Black Knight faces is heat management. deployment:Used by the SLDF Royal BattleMech regiments, the 6b was introduced in 2751 and upgraded the heat dissipation system with double heat sinks. The tonnage saved was used to upgrade the large lasers to Raker-X Large Pulse Lasers and the PPC to an Kinslaughter ER PPC. diff --git a/megamek/data/mechfiles/mechs/3050U/Crab CRB-27.mtf b/megamek/data/mechfiles/mechs/3050U/Crab CRB-27.mtf index 4177245d86d..4a1a2a1b9d3 100644 --- a/megamek/data/mechfiles/mechs/3050U/Crab CRB-27.mtf +++ b/megamek/data/mechfiles/mechs/3050U/Crab CRB-27.mtf @@ -159,7 +159,7 @@ overview:Designed in 2719 during the last days of the Star League, the Crab was capabilities:Although lacking hand actuators or jump jets, it possessed good overland speed and its all-energy weapons payload was suitable for long-range missions without the prospect for resupply. The Crab also boasted a highly advanced communications system, the Dalban Series K, and was built mostly with proven parts easy to maintain. The term "Crab walk" soon became synonymous with easy duty, since technicians spent less than half the time maintaining the Crab than with other 'Mechs of the same weight class. -deployment:The Crab carries two RamTech 1200 Large Lasers, each housed in the claw and forearm of either arm. While excellent weapons they are quite delicate with the focusing mirrors liable to be knocked out of alignment if used in hand-to-hand combat; fixing them requires the pilot to leave their cockpit and stick their head up into each arm's elbow to make the necessary adjustments. Backing up the large lasers is a Ceres Arms Medium Laser in the center torso, well-protected from the fusion engine and with easy access to the sixteen heat sinks, and an Exostar Small Laser in the head, a last-resort weapon more suitable for fighting infantry and rioting citizens. Nine tons of Ferro-Fibrous Armor provides good protection for its size as even the weakest locations, the left and right torso, can each survive a shot from a PPC. Originally lacking hand actuators, Cosara later provided a refit kit to install one in either or both arms. +deployment:The Crab carries two RamTech 1200 Large Lasers, each housed in the claw and forearm of either arm. While excellent weapons they are quite delicate with the focusing mirrors liable to be knocked out of alignment if used in hand-to-hand combat; fixing them requires the pilot to leave their cockpit and stick their head up into each arm's elbow to make the necessary adjustments. Backing up the large lasers is a Ceres Arms Medium Laser in the center torso, well-protected from the fusion engine and with easy access to the sixteen heat sinks, and an ExoStar Small Laser in the head, a last-resort weapon more suitable for fighting infantry and rioting citizens. Nine tons of Ferro-Fibrous Armor provides good protection for its size as even the weakest locations, the left and right torso, can each survive a shot from a PPC. Originally lacking hand actuators, Cosara later provided a refit kit to install one in either or both arms. history:Less than a thousand Crabs had been produced when the Succession Wars began. So popular was the Crab that many believed it was likely to become the standard medium 'Mech of the SLDF. Unfortunately the Amaris Civil War and the dissolution of the Star League put an end to any future plans for the Crab. Cosara Weaponries' Crab factory on Northwind was practically destroyed in 2786, one of many strategic targets attacked in the opening salvos of the First Succession War. Although dedicated technicians were able to keep portions of the assembly line open, producing what spare parts they still could to rebuild damaged Crabs, the technology used for both the original's advanced armor plating and communications system became lost. Designated as CRB-20 models, these Crabs were only slightly inferior to the original: with the destruction of the military infrastructure necessary for the Dalban Series K's more advanced functions to work, its replacement by lesser systems ironically became less of an issue. By the end of the Fourth Succession War a hundred or so Crabs were still active in the Inner Sphere and all were CRB-20s. Unbeknownst to many, ComStar had secreted away massive stockpiles of Star League technology and 'Mechs, including the Crab. When it came time to form their own military original CRB-27 Crabs were used to outfit the Com Guards, while at the same time gifting downgraded CRB-20s to the Draconis Combine during the War of 3039 as part of Operation Rosebud. Concurrently the discovery of the Helm Memory Core allowed the refit line on Northwind to start upgrading the remaining downgraded Crabs to their original specification. Unknown to anyone in the Inner Sphere was the continued existence of the Crab in the arsenal of the Clans, although by the time of the Clan Invasion these had been relegated to second-line and garrison units. Eventually Cosara Weaponries was able to restart production of the original Crab in the 3050s and brand-new variants began turning up. Among these were new CRB-30s built by ComStar (later acquired by the Word of Blake) which made use of new C3 technology; it was also rumored ComStar sold these models to the rump Free Rasalhague Republic. During the Jihad the Word of Blake managed to capture the Northwind factory and begin producing their own radical variant known as the CRB-45. diff --git a/megamek/data/mechfiles/mechs/3050U/Crockett CRK-5003-1.mtf b/megamek/data/mechfiles/mechs/3050U/Crockett CRK-5003-1.mtf index b98ba787a98..be6b8611c64 100644 --- a/megamek/data/mechfiles/mechs/3050U/Crockett CRK-5003-1.mtf +++ b/megamek/data/mechfiles/mechs/3050U/Crockett CRK-5003-1.mtf @@ -165,7 +165,7 @@ capabilities:Due to the fact that the Crockett was originally a training 'Mech, deployment:The primary weapon is a Blankenburg LB-X Autocannon/10 that can use either standard High Explosive Armor Penetrating (HEAP) ammunition or a shotgun-like cluster round. It is fed by three tons of reloads, two in the right torso and one in the left. The autocannon is backed up by two Blankenburg 25 Extended Range Large Lasers in either arm for long range combat. When the Crockett closes with its enemies, it can bring into play its twin Holly-6 SRM-6 launchers, mounted in either side torso with two tons of reloads in the right, and two Dodd Small Lasers mounted in either arm. The Holly launchers were chosen in particular for their reliability, especially when the 'Mech lands after jumping through the air; less-proven launchers were shown to have one or more missiles knocked out of alignment after just a single jump. All of the heat from its weapons is offset by the use of fifteen double heat sinks. -history:Ten years after its introduction, however, Star League Defense Force commanders began to realize that Blankenburg Technologies had taken the "combat capability" requirement almost too seriously, and began to field the 'Mech on the front lines. Beyond its heavy weapons load-out, large number of heat sinks and use of jump jets, part of what made the Crockett successful was the enemy's unfamiliarity with this design, giving it an added advantage. Its cockpit systems, simplified for use as a trainer, allowed anyone to pilot the Crockett with only a minimal amount of familiarization training. The Crockett did not go without its growing pains, however. Once it was pressed into combat there was a flaw found in the cockpit's life support system that resulted in the death of three MechWarriors. This flaw was corrected in future production, with previously-issued machines recalled and refitted with the life support system upgrade. In service to the SLDF the hallmark tactic of the Crockett was to engage an enemy 'Mech at range and, before the enemy could accurately target it, jump behind them to attack their weaker rear. So effective was the Crockett that, following the dissolution of the Star League and start of the Succession Wars, many of the Great Houses removed the 'Mech from their training programs and used them to fight on the front lines. As many of the Crockett's components became lostech Blankenburg was forced to make do with inferior spare parts, reducing its capabilities with every year. Eventually the last few Crocketts were little more than a collection of salvaged parts, largely unrecognizable from their original design, until the 'Mech finally went extinct within the Inner Sphere. This changed starting in the thirty-first century, thanks to ComStar's secret stockpile of Star League-era 'Mechs. Original models of the Crockett were used to outfit the Com Guards while downgraded versions were gifted to the Draconis Combine as part of Operation Rosebud. With the Clan Invasion surviving models of the design were also seen among second-line Clan forces. As part of Precentor Martial Anastasius Focht's rearmament program the Blankenberg production line on Terra was reopened to start producing new Crocketts starting in 3054, although it would be only a few years until the Word of Blake conquered the planet and began supplying themselves and their Free Worlds League allies. In order to maintain their supply ComStar contracted Grumium Creations to begin producing Crocketts starting in 3062 and the 'Mech fought on both sides during the Jihad. +history:Ten years after its introduction, however, Star League Defense Force commanders began to realize that Blankenburg Technologies had taken the "combat capability" requirement almost too seriously, and began to field the 'Mech on the front lines. Beyond its heavy weapons load-out, large number of heat sinks and use of jump jets, part of what made the Crockett successful was the enemy's unfamiliarity with this design, giving it an added advantage. Its cockpit systems, simplified for use as a trainer, allowed anyone to pilot the Crockett with only a minimal amount of familiarization training. The Crockett did not go without its growing pains, however. Once it was pressed into combat there was a flaw found in the cockpit's life support system that resulted in the death of three MechWarriors. This flaw was corrected in future production, with previously-issued machines recalled and refitted with the life support system upgrade. In service to the SLDF the hallmark tactic of the Crockett was to engage an enemy 'Mech at range and, before the enemy could accurately target it, jump behind them to attack their weaker rear. So effective was the Crockett that, following the dissolution of the Star League and start of the Succession Wars, many of the Great Houses removed the 'Mech from their training programs and used them to fight on the front lines. As many of the Crockett's components became lostech Blankenburg was forced to make do with inferior spare parts, reducing its capabilities with every year. Eventually the last few Crocketts were little more than a collection of salvaged parts, largely unrecognizable from their original design, until the 'Mech finally went extinct within the Inner Sphere. This changed starting in the thirty-first century, thanks to ComStar's secret stockpile of Star League-era 'Mechs. Original models of the Crockett were used to outfit the Com Guards while downgraded versions were gifted to the Draconis Combine as part of Operation Rosebud. With the Clan Invasion surviving models of the design were also seen among second-line Clan forces. As part of Precentor Martial Anastasius Focht's rearmament program the Blankenburg production line on Terra was reopened to start producing new Crocketts starting in 3054, although it would be only a few years until the Word of Blake conquered the planet and began supplying themselves and their Free Worlds League allies. In order to maintain their supply ComStar contracted Grumium Creations to begin producing Crocketts starting in 3062 and the 'Mech fought on both sides during the Jihad. manufacturer:Blankenburg Technologies primaryfactory:Terra diff --git a/megamek/data/mechfiles/mechs/3050U/Crockett CRK-5003-3.mtf b/megamek/data/mechfiles/mechs/3050U/Crockett CRK-5003-3.mtf index 633e8339475..2b3ae1066e5 100644 --- a/megamek/data/mechfiles/mechs/3050U/Crockett CRK-5003-3.mtf +++ b/megamek/data/mechfiles/mechs/3050U/Crockett CRK-5003-3.mtf @@ -164,7 +164,7 @@ capabilities:Due to the fact that the Crockett was originally a training 'Mech, deployment:The 5003-3 was produced by Grumium Creations in 3062. The ammunition bins are reshuffled and a half-ton of armor is removed to make room for CASE. -history:Ten years after its introduction, however, Star League Defense Force commanders began to realize that Blankenburg Technologies had taken the "combat capability" requirement almost too seriously, and began to field the 'Mech on the front lines. Beyond its heavy weapons load-out, large number of heat sinks and use of jump jets, part of what made the Crockett successful was the enemy's unfamiliarity with this design, giving it an added advantage. Its cockpit systems, simplified for use as a trainer, allowed anyone to pilot the Crockett with only a minimal amount of familiarization training. The Crockett did not go without its growing pains, however. Once it was pressed into combat there was a flaw found in the cockpit's life support system that resulted in the death of three MechWarriors. This flaw was corrected in future production, with previously-issued machines recalled and refitted with the life support system upgrade. In service to the SLDF the hallmark tactic of the Crockett was to engage an enemy 'Mech at range and, before the enemy could accurately target it, jump behind them to attack their weaker rear. So effective was the Crockett that, following the dissolution of the Star League and start of the Succession Wars, many of the Great Houses removed the 'Mech from their training programs and used them to fight on the front lines. As many of the Crockett's components became lostech Blankenburg was forced to make do with inferior spare parts, reducing its capabilities with every year. Eventually the last few Crocketts were little more than a collection of salvaged parts, largely unrecognizable from their original design, until the 'Mech finally went extinct within the Inner Sphere. This changed starting in the thirty-first century, thanks to ComStar's secret stockpile of Star League-era 'Mechs. Original models of the Crockett were used to outfit the Com Guards while downgraded versions were gifted to the Draconis Combine as part of Operation Rosebud. With the Clan Invasion surviving models of the design were also seen among second-line Clan forces. As part of Precentor Martial Anastasius Focht's rearmament program the Blankenberg production line on Terra was reopened to start producing new Crocketts starting in 3054, although it would be only a few years until the Word of Blake conquered the planet and began supplying themselves and their Free Worlds League allies. In order to maintain their supply ComStar contracted Grumium Creations to begin producing Crocketts starting in 3062 and the 'Mech fought on both sides during the Jihad. +history:Ten years after its introduction, however, Star League Defense Force commanders began to realize that Blankenburg Technologies had taken the "combat capability" requirement almost too seriously, and began to field the 'Mech on the front lines. Beyond its heavy weapons load-out, large number of heat sinks and use of jump jets, part of what made the Crockett successful was the enemy's unfamiliarity with this design, giving it an added advantage. Its cockpit systems, simplified for use as a trainer, allowed anyone to pilot the Crockett with only a minimal amount of familiarization training. The Crockett did not go without its growing pains, however. Once it was pressed into combat there was a flaw found in the cockpit's life support system that resulted in the death of three MechWarriors. This flaw was corrected in future production, with previously-issued machines recalled and refitted with the life support system upgrade. In service to the SLDF the hallmark tactic of the Crockett was to engage an enemy 'Mech at range and, before the enemy could accurately target it, jump behind them to attack their weaker rear. So effective was the Crockett that, following the dissolution of the Star League and start of the Succession Wars, many of the Great Houses removed the 'Mech from their training programs and used them to fight on the front lines. As many of the Crockett's components became lostech Blankenburg was forced to make do with inferior spare parts, reducing its capabilities with every year. Eventually the last few Crocketts were little more than a collection of salvaged parts, largely unrecognizable from their original design, until the 'Mech finally went extinct within the Inner Sphere. This changed starting in the thirty-first century, thanks to ComStar's secret stockpile of Star League-era 'Mechs. Original models of the Crockett were used to outfit the Com Guards while downgraded versions were gifted to the Draconis Combine as part of Operation Rosebud. With the Clan Invasion surviving models of the design were also seen among second-line Clan forces. As part of Precentor Martial Anastasius Focht's rearmament program the Blankenburg production line on Terra was reopened to start producing new Crocketts starting in 3054, although it would be only a few years until the Word of Blake conquered the planet and began supplying themselves and their Free Worlds League allies. In order to maintain their supply ComStar contracted Grumium Creations to begin producing Crocketts starting in 3062 and the 'Mech fought on both sides during the Jihad. manufacturer:Grumium Creations primaryfactory:Grumium diff --git a/megamek/data/mechfiles/mechs/3050U/Crockett CRK-5004-1.mtf b/megamek/data/mechfiles/mechs/3050U/Crockett CRK-5004-1.mtf index 6a7b7ca2546..b5a625e7556 100644 --- a/megamek/data/mechfiles/mechs/3050U/Crockett CRK-5004-1.mtf +++ b/megamek/data/mechfiles/mechs/3050U/Crockett CRK-5004-1.mtf @@ -164,7 +164,7 @@ capabilities:Due to the fact that the Crockett was originally a training 'Mech, deployment:An upgrade of the 5003-3 introduced in 3063, the 5004-1 makes use of a C3i Computer to enable the Crockett to share targeting data with other members of its Level II. In order to free up room, a ton of autocannon ammunition has been removed and the missile launchers have been downgraded to SRM-4s. The remaining half-ton went to the addition of armor. Finally, all the lasers have been upgraded to extended range models. -history:Ten years after its introduction, however, Star League Defense Force commanders began to realize that Blankenburg Technologies had taken the "combat capability" requirement almost too seriously, and began to field the 'Mech on the front lines. Beyond its heavy weapons load-out, large number of heat sinks and use of jump jets, part of what made the Crockett successful was the enemy's unfamiliarity with this design, giving it an added advantage. Its cockpit systems, simplified for use as a trainer, allowed anyone to pilot the Crockett with only a minimal amount of familiarization training. The Crockett did not go without its growing pains, however. Once it was pressed into combat there was a flaw found in the cockpit's life support system that resulted in the death of three MechWarriors. This flaw was corrected in future production, with previously-issued machines recalled and refitted with the life support system upgrade. In service to the SLDF the hallmark tactic of the Crockett was to engage an enemy 'Mech at range and, before the enemy could accurately target it, jump behind them to attack their weaker rear. So effective was the Crockett that, following the dissolution of the Star League and start of the Succession Wars, many of the Great Houses removed the 'Mech from their training programs and used them to fight on the front lines. As many of the Crockett's components became lostech Blankenburg was forced to make do with inferior spare parts, reducing its capabilities with every year. Eventually the last few Crocketts were little more than a collection of salvaged parts, largely unrecognizable from their original design, until the 'Mech finally went extinct within the Inner Sphere. This changed starting in the thirty-first century, thanks to ComStar's secret stockpile of Star League-era 'Mechs. Original models of the Crockett were used to outfit the Com Guards while downgraded versions were gifted to the Draconis Combine as part of Operation Rosebud. With the Clan Invasion surviving models of the design were also seen among second-line Clan forces. As part of Precentor Martial Anastasius Focht's rearmament program the Blankenberg production line on Terra was reopened to start producing new Crocketts starting in 3054, although it would be only a few years until the Word of Blake conquered the planet and began supplying themselves and their Free Worlds League allies. In order to maintain their supply ComStar contracted Grumium Creations to begin producing Crocketts starting in 3062 and the 'Mech fought on both sides during the Jihad. +history:Ten years after its introduction, however, Star League Defense Force commanders began to realize that Blankenburg Technologies had taken the "combat capability" requirement almost too seriously, and began to field the 'Mech on the front lines. Beyond its heavy weapons load-out, large number of heat sinks and use of jump jets, part of what made the Crockett successful was the enemy's unfamiliarity with this design, giving it an added advantage. Its cockpit systems, simplified for use as a trainer, allowed anyone to pilot the Crockett with only a minimal amount of familiarization training. The Crockett did not go without its growing pains, however. Once it was pressed into combat there was a flaw found in the cockpit's life support system that resulted in the death of three MechWarriors. This flaw was corrected in future production, with previously-issued machines recalled and refitted with the life support system upgrade. In service to the SLDF the hallmark tactic of the Crockett was to engage an enemy 'Mech at range and, before the enemy could accurately target it, jump behind them to attack their weaker rear. So effective was the Crockett that, following the dissolution of the Star League and start of the Succession Wars, many of the Great Houses removed the 'Mech from their training programs and used them to fight on the front lines. As many of the Crockett's components became lostech Blankenburg was forced to make do with inferior spare parts, reducing its capabilities with every year. Eventually the last few Crocketts were little more than a collection of salvaged parts, largely unrecognizable from their original design, until the 'Mech finally went extinct within the Inner Sphere. This changed starting in the thirty-first century, thanks to ComStar's secret stockpile of Star League-era 'Mechs. Original models of the Crockett were used to outfit the Com Guards while downgraded versions were gifted to the Draconis Combine as part of Operation Rosebud. With the Clan Invasion surviving models of the design were also seen among second-line Clan forces. As part of Precentor Martial Anastasius Focht's rearmament program the Blankenburg production line on Terra was reopened to start producing new Crocketts starting in 3054, although it would be only a few years until the Word of Blake conquered the planet and began supplying themselves and their Free Worlds League allies. In order to maintain their supply ComStar contracted Grumium Creations to begin producing Crocketts starting in 3062 and the 'Mech fought on both sides during the Jihad. manufacturer:Grumium Creations primaryfactory:Grumium diff --git a/megamek/data/mechfiles/mechs/3050U/Crockett CRK-5005-1.mtf b/megamek/data/mechfiles/mechs/3050U/Crockett CRK-5005-1.mtf index 5a5b4689730..32420aca6f9 100644 --- a/megamek/data/mechfiles/mechs/3050U/Crockett CRK-5005-1.mtf +++ b/megamek/data/mechfiles/mechs/3050U/Crockett CRK-5005-1.mtf @@ -164,7 +164,7 @@ capabilities:Due to the fact that the Crockett was originally a training 'Mech, deployment:This model produced by Word of Blake in 3070 uses a Light Engine for power so that it can add improved jump jets that enable it to jump up to 150 meters. The small lasers of the 5004-1 have been removed and it utilizes a small cockpit, cementing its role as a front line unit rather than a training 'Mech. -history:Ten years after its introduction, however, Star League Defense Force commanders began to realize that Blankenburg Technologies had taken the "combat capability" requirement almost too seriously, and began to field the 'Mech on the front lines. Beyond its heavy weapons load-out, large number of heat sinks and use of jump jets, part of what made the Crockett successful was the enemy's unfamiliarity with this design, giving it an added advantage. Its cockpit systems, simplified for use as a trainer, allowed anyone to pilot the Crockett with only a minimal amount of familiarization training. The Crockett did not go without its growing pains, however. Once it was pressed into combat there was a flaw found in the cockpit's life support system that resulted in the death of three MechWarriors. This flaw was corrected in future production, with previously-issued machines recalled and refitted with the life support system upgrade. In service to the SLDF the hallmark tactic of the Crockett was to engage an enemy 'Mech at range and, before the enemy could accurately target it, jump behind them to attack their weaker rear. So effective was the Crockett that, following the dissolution of the Star League and start of the Succession Wars, many of the Great Houses removed the 'Mech from their training programs and used them to fight on the front lines. As many of the Crockett's components became lostech Blankenburg was forced to make do with inferior spare parts, reducing its capabilities with every year. Eventually the last few Crocketts were little more than a collection of salvaged parts, largely unrecognizable from their original design, until the 'Mech finally went extinct within the Inner Sphere. This changed starting in the thirty-first century, thanks to ComStar's secret stockpile of Star League-era 'Mechs. Original models of the Crockett were used to outfit the Com Guards while downgraded versions were gifted to the Draconis Combine as part of Operation Rosebud. With the Clan Invasion surviving models of the design were also seen among second-line Clan forces. As part of Precentor Martial Anastasius Focht's rearmament program the Blankenberg production line on Terra was reopened to start producing new Crocketts starting in 3054, although it would be only a few years until the Word of Blake conquered the planet and began supplying themselves and their Free Worlds League allies. In order to maintain their supply ComStar contracted Grumium Creations to begin producing Crocketts starting in 3062 and the 'Mech fought on both sides during the Jihad. +history:Ten years after its introduction, however, Star League Defense Force commanders began to realize that Blankenburg Technologies had taken the "combat capability" requirement almost too seriously, and began to field the 'Mech on the front lines. Beyond its heavy weapons load-out, large number of heat sinks and use of jump jets, part of what made the Crockett successful was the enemy's unfamiliarity with this design, giving it an added advantage. Its cockpit systems, simplified for use as a trainer, allowed anyone to pilot the Crockett with only a minimal amount of familiarization training. The Crockett did not go without its growing pains, however. Once it was pressed into combat there was a flaw found in the cockpit's life support system that resulted in the death of three MechWarriors. This flaw was corrected in future production, with previously-issued machines recalled and refitted with the life support system upgrade. In service to the SLDF the hallmark tactic of the Crockett was to engage an enemy 'Mech at range and, before the enemy could accurately target it, jump behind them to attack their weaker rear. So effective was the Crockett that, following the dissolution of the Star League and start of the Succession Wars, many of the Great Houses removed the 'Mech from their training programs and used them to fight on the front lines. As many of the Crockett's components became lostech Blankenburg was forced to make do with inferior spare parts, reducing its capabilities with every year. Eventually the last few Crocketts were little more than a collection of salvaged parts, largely unrecognizable from their original design, until the 'Mech finally went extinct within the Inner Sphere. This changed starting in the thirty-first century, thanks to ComStar's secret stockpile of Star League-era 'Mechs. Original models of the Crockett were used to outfit the Com Guards while downgraded versions were gifted to the Draconis Combine as part of Operation Rosebud. With the Clan Invasion surviving models of the design were also seen among second-line Clan forces. As part of Precentor Martial Anastasius Focht's rearmament program the Blankenburg production line on Terra was reopened to start producing new Crocketts starting in 3054, although it would be only a few years until the Word of Blake conquered the planet and began supplying themselves and their Free Worlds League allies. In order to maintain their supply ComStar contracted Grumium Creations to begin producing Crocketts starting in 3062 and the 'Mech fought on both sides during the Jihad. manufacturer:Blankenburg Technologies primaryfactory:Terra diff --git a/megamek/data/mechfiles/mechs/3050U/Dragonfly (Viper) A.mtf b/megamek/data/mechfiles/mechs/3050U/Dragonfly (Viper) A.mtf index 0c2030fe43e..eb126fb51d8 100644 --- a/megamek/data/mechfiles/mechs/3050U/Dragonfly (Viper) A.mtf +++ b/megamek/data/mechfiles/mechs/3050U/Dragonfly (Viper) A.mtf @@ -159,7 +159,7 @@ Jump Jet overview:The Viper is a fast, highly-maneuverable medium OmniMech originally designed by Clan Fire Mandrill on Shadow. Codenamed the Dragonfly by the Inner Sphere forces that first encountered this small but fierce OmniMech, the name stuck because of its ability to move swiftly over the battlefield. The Viper is fast and well-armored, but significantly under-gunned compared with other Clan OmniMechs massing 35-45 tons (including the Adder, Battle Cobra, Grendel, Shadow Cat, Pouncer, and Cougar). -capabilities:A close range harasser configuration, the Viper A is armed with an impressive five ER Medium Lasers for its main striking power and is backed up by an SRM-6 launcher with an Artemis IV fire control system that increases the launcher's accuracy. This powerful short range punch makes the Viper A a powerful foe in close combat situations, though an inexperienced MechWarrior may find him or herself quickly overcome by heat. The Viper is built on a lightweight Endo Steel chassis and powered by a weight saving 320 XL engine that propels the Viper to a top speed of 129.6 km/h. The Viper augments its impressive ground speed with eight jump jets that allow it to jump up to a distance of two hundred and forty meters. The Viper has seven tons of Ferro-Fibrous armor to absorb any damage from shots that are lucky enough to strike it and has eight and a half tons of podspace for its weapons payload. +capabilities:A close range harasser configuration, the Viper A is armed with an impressive five ER Medium Lasers for its main striking power and is backed up by an SRM-6 launcher with an Artemis IV fire control system that increases the launcher's accuracy. This powerful short range punch makes the Viper A a powerful foe in close combat situations, though an inexperienced MechWarrior may find him or herself quickly overcome by heat. The Viper is built on a lightweight Endo Steel chassis and powered by a weight saving 320 XL engine that propels the Viper to a top speed of 129.6 km/h. The Viper augments its impressive ground speed with eight jump jets that allow it to jump up to a distance of two hundred and forty meters. The Viper has seven tons of Ferro-Fibrous armor to absorb any damage from shots that are lucky enough to strike it and has eight and a half tons of pod space for its weapons payload. history:Clan Ghost Bear came into possession of the design in 3002 when they traded several production runs of Executioner OmniMechs for the design and production facilities on Shadow. Rather than trial for land rights to Shadow, and become embroiled in the internecine struggles of the Fire Mandrills, the Bears restructured the facility, making the lines modular, and relocated production to Strana Mechty - this modular technology proved very useful when the Ghost Bears migrated back to the Inner Sphere in the late 3050s. Surprisingly, the Bears left their first modular production facility on Strana Mechty. Production continued on Strana Mechty for Clan Ghost Bear until the mid-3060s when the Hell's Horses won the production rights and the facility (and then promptly lost the facility to Clan Ice Hellion in 3068). In addition to the manufacturing plant on Strana Mechty, at least one other planet in the Homeworlds was home to a manufacturing line producing Vipers; in 3071 Clan Goliath Scorpion captured a Viper factory from Clan Coyote on Delios, although it is unknown if the planet survived the Wars of Reaving, Goliath Scorpion Abjurement and the subsequent abandonment of the planet by the Coyotes and Cloud Cobras. manufacturer:Upsilon Plant 2J, Dominion Facility Kappa-5 diff --git a/megamek/data/mechfiles/mechs/3050U/Dragonfly (Viper) B.mtf b/megamek/data/mechfiles/mechs/3050U/Dragonfly (Viper) B.mtf index 169184846d5..ad4af9e8f79 100644 --- a/megamek/data/mechfiles/mechs/3050U/Dragonfly (Viper) B.mtf +++ b/megamek/data/mechfiles/mechs/3050U/Dragonfly (Viper) B.mtf @@ -157,7 +157,7 @@ Jump Jet overview:The Viper is a fast, highly-maneuverable medium OmniMech originally designed by Clan Fire Mandrill on Shadow. Codenamed the Dragonfly by the Inner Sphere forces that first encountered this small but fierce OmniMech, the name stuck because of its ability to move swiftly over the battlefield. The Viper is fast and well-armored, but significantly under-gunned compared with other Clan OmniMechs massing 35-45 tons (including the Adder, Battle Cobra, Grendel, Shadow Cat, Pouncer, and Cougar). -capabilities:Configured for long range sniping, the Viper B's primary weapon is a powerful ER PPC. To protect itself if an enemy closes to short range, the 'Mech has two highly accurate Small Pulse Lasers and a Flamer. The Viper is built on a lightweight Endo Steel chassis and powered by a weight saving 320 XL engine that propels the Viper to a top speed of 129.6 km/h. The Viper augments its impressive ground speed with eight jump jets that allow it to jump up to a distance of two hundred and forty meters. The Viper has seven tons of Ferro-Fibrous armor to absorb any damage from shots that are lucky enough to strike it and has eight and a half tons of podspace for its weapons payload. +capabilities:Configured for long range sniping, the Viper B's primary weapon is a powerful ER PPC. To protect itself if an enemy closes to short range, the 'Mech has two highly accurate Small Pulse Lasers and a Flamer. The Viper is built on a lightweight Endo Steel chassis and powered by a weight saving 320 XL engine that propels the Viper to a top speed of 129.6 km/h. The Viper augments its impressive ground speed with eight jump jets that allow it to jump up to a distance of two hundred and forty meters. The Viper has seven tons of Ferro-Fibrous armor to absorb any damage from shots that are lucky enough to strike it and has eight and a half tons of pod space for its weapons payload. history:Clan Ghost Bear came into possession of the design in 3002 when they traded several production runs of Executioner OmniMechs for the design and production facilities on Shadow. Rather than trial for land rights to Shadow, and become embroiled in the internecine struggles of the Fire Mandrills, the Bears restructured the facility, making the lines modular, and relocated production to Strana Mechty - this modular technology proved very useful when the Ghost Bears migrated back to the Inner Sphere in the late 3050s. Surprisingly, the Bears left their first modular production facility on Strana Mechty. Production continued on Strana Mechty for Clan Ghost Bear until the mid-3060s when the Hell's Horses won the production rights and the facility (and then promptly lost the facility to Clan Ice Hellion in 3068). In addition to the manufacturing plant on Strana Mechty, at least one other planet in the Homeworlds was home to a manufacturing line producing Vipers; in 3071 Clan Goliath Scorpion captured a Viper factory from Clan Coyote on Delios, although it is unknown if the planet survived the Wars of Reaving, Goliath Scorpion Abjurement and the subsequent abandonment of the planet by the Coyotes and Cloud Cobras. manufacturer:Upsilon Plant 2J, Dominion Facility Kappa-5 diff --git a/megamek/data/mechfiles/mechs/3050U/Dragonfly (Viper) C.mtf b/megamek/data/mechfiles/mechs/3050U/Dragonfly (Viper) C.mtf index f8bdcd66176..f44c4acbf0c 100644 --- a/megamek/data/mechfiles/mechs/3050U/Dragonfly (Viper) C.mtf +++ b/megamek/data/mechfiles/mechs/3050U/Dragonfly (Viper) C.mtf @@ -162,7 +162,7 @@ Jump Jet overview:The Viper is a fast, highly-maneuverable medium OmniMech originally designed by Clan Fire Mandrill on Shadow. Codenamed the Dragonfly by the Inner Sphere forces that first encountered this small but fierce OmniMech, the name stuck because of its ability to move swiftly over the battlefield. The Viper is fast and well-armored, but significantly under-gunned compared with other Clan OmniMechs massing 35-45 tons (including the Adder, Battle Cobra, Grendel, Shadow Cat, Pouncer, and Cougar). -capabilities:The Viper C carries an Active Probe to allow it to find hidden enemy units, usually in an urban environment where it can bring its four Machine Guns and three Flamers to bear on any infantry unfortunate enough to be found. To provide some combat capability against 'Mechs and vehicles, the C configuration has two ER Medium Lasers. The Viper is built on a lightweight Endo Steel chassis and powered by a weight saving 320 XL engine that propels the Viper to a top speed of 129.6 km/h. The Viper augments its impressive ground speed with eight jump jets that allow it to jump up to a distance of two hundred and forty meters. The Viper has seven tons of Ferro-Fibrous armor to absorb any damage from shots that are lucky enough to strike it and has eight and a half tons of podspace for its weapons payload. +capabilities:The Viper C carries an Active Probe to allow it to find hidden enemy units, usually in an urban environment where it can bring its four Machine Guns and three Flamers to bear on any infantry unfortunate enough to be found. To provide some combat capability against 'Mechs and vehicles, the C configuration has two ER Medium Lasers. The Viper is built on a lightweight Endo Steel chassis and powered by a weight saving 320 XL engine that propels the Viper to a top speed of 129.6 km/h. The Viper augments its impressive ground speed with eight jump jets that allow it to jump up to a distance of two hundred and forty meters. The Viper has seven tons of Ferro-Fibrous armor to absorb any damage from shots that are lucky enough to strike it and has eight and a half tons of pod space for its weapons payload. history:Clan Ghost Bear came into possession of the design in 3002 when they traded several production runs of Executioner OmniMechs for the design and production facilities on Shadow. Rather than trial for land rights to Shadow, and become embroiled in the internecine struggles of the Fire Mandrills, the Bears restructured the facility, making the lines modular, and relocated production to Strana Mechty - this modular technology proved very useful when the Ghost Bears migrated back to the Inner Sphere in the late 3050s. Surprisingly, the Bears left their first modular production facility on Strana Mechty. Production continued on Strana Mechty for Clan Ghost Bear until the mid-3060s when the Hell's Horses won the production rights and the facility (and then promptly lost the facility to Clan Ice Hellion in 3068). In addition to the manufacturing plant on Strana Mechty, at least one other planet in the Homeworlds was home to a manufacturing line producing Vipers; in 3071 Clan Goliath Scorpion captured a Viper factory from Clan Coyote on Delios, although it is unknown if the planet survived the Wars of Reaving, Goliath Scorpion Abjurement and the subsequent abandonment of the planet by the Coyotes and Cloud Cobras. manufacturer:Upsilon Plant 2J, Dominion Facility Kappa-5 diff --git a/megamek/data/mechfiles/mechs/3050U/Dragonfly (Viper) D.mtf b/megamek/data/mechfiles/mechs/3050U/Dragonfly (Viper) D.mtf index 0ef2f0ad963..457db8836d3 100644 --- a/megamek/data/mechfiles/mechs/3050U/Dragonfly (Viper) D.mtf +++ b/megamek/data/mechfiles/mechs/3050U/Dragonfly (Viper) D.mtf @@ -158,7 +158,7 @@ Jump Jet overview:The Viper is a fast, highly-maneuverable medium OmniMech originally designed by Clan Fire Mandrill on Shadow. Codenamed the Dragonfly by the Inner Sphere forces that first encountered this small but fierce OmniMech, the name stuck because of its ability to move swiftly over the battlefield. The Viper is fast and well-armored, but significantly under-gunned compared with other Clan OmniMechs massing 35-45 tons (including the Adder, Battle Cobra, Grendel, Shadow Cat, Pouncer, and Cougar). -capabilities:Capable of engaging an enemy at a variety of ranges, the Viper D has an LRM-5 that allows it to engage enemy units at long ranges. As the distance closes, the Viper D can bring its two ER Medium Lasers and Streak SRM-6 to bear on an enemy, with two ER Small Lasers for extremely close combat situations. The Viper is built on a lightweight Endo Steel chassis and powered by a weight saving 320 XL engine that propels the Viper to a top speed of 129.6 km/h. The Viper augments its impressive ground speed with eight jump jets that allow it to jump up to a distance of two hundred and forty meters. The Viper has seven tons of Ferro-Fibrous armor to absorb any damage from shots that are lucky enough to strike it and has eight and a half tons of podspace for its weapons payload. +capabilities:Capable of engaging an enemy at a variety of ranges, the Viper D has an LRM-5 that allows it to engage enemy units at long ranges. As the distance closes, the Viper D can bring its two ER Medium Lasers and Streak SRM-6 to bear on an enemy, with two ER Small Lasers for extremely close combat situations. The Viper is built on a lightweight Endo Steel chassis and powered by a weight saving 320 XL engine that propels the Viper to a top speed of 129.6 km/h. The Viper augments its impressive ground speed with eight jump jets that allow it to jump up to a distance of two hundred and forty meters. The Viper has seven tons of Ferro-Fibrous armor to absorb any damage from shots that are lucky enough to strike it and has eight and a half tons of pod space for its weapons payload. history:Clan Ghost Bear came into possession of the design in 3002 when they traded several production runs of Executioner OmniMechs for the design and production facilities on Shadow. Rather than trial for land rights to Shadow, and become embroiled in the internecine struggles of the Fire Mandrills, the Bears restructured the facility, making the lines modular, and relocated production to Strana Mechty - this modular technology proved very useful when the Ghost Bears migrated back to the Inner Sphere in the late 3050s. Surprisingly, the Bears left their first modular production facility on Strana Mechty. Production continued on Strana Mechty for Clan Ghost Bear until the mid-3060s when the Hell's Horses won the production rights and the facility (and then promptly lost the facility to Clan Ice Hellion in 3068). In addition to the manufacturing plant on Strana Mechty, at least one other planet in the Homeworlds was home to a manufacturing line producing Vipers; in 3071 Clan Goliath Scorpion captured a Viper factory from Clan Coyote on Delios, although it is unknown if the planet survived the Wars of Reaving, Goliath Scorpion Abjurement and the subsequent abandonment of the planet by the Coyotes and Cloud Cobras. manufacturer:Upsilon Plant 2J, Dominion Facility Kappa-5 diff --git a/megamek/data/mechfiles/mechs/3050U/Dragonfly (Viper) E.mtf b/megamek/data/mechfiles/mechs/3050U/Dragonfly (Viper) E.mtf index bd3c90e9df9..5e506b74697 100644 --- a/megamek/data/mechfiles/mechs/3050U/Dragonfly (Viper) E.mtf +++ b/megamek/data/mechfiles/mechs/3050U/Dragonfly (Viper) E.mtf @@ -157,7 +157,7 @@ Jump Jet overview:The Viper is a fast, highly-maneuverable medium OmniMech originally designed by Clan Fire Mandrill on Shadow. Codenamed the Dragonfly by the Inner Sphere forces that first encountered this small but fierce OmniMech, the name stuck because of its ability to move swiftly over the battlefield. The Viper is fast and well-armored, but significantly under-gunned compared with other Clan OmniMechs massing 35-45 tons (including the Adder, Battle Cobra, Grendel, Shadow Cat, Pouncer, and Cougar). -capabilities:Similar to the D configuration, the Viper E has an ATM-6 that is capable of filling the roles of the LRM and SRM launchers on the D configuration. The Viper E has an ER Medium Laser and two ER Small Lasers for close range direct firepower. The Viper is built on a lightweight Endo Steel chassis and powered by a weight saving 320 XL engine that propels the Viper to a top speed of 129.6 km/h. The Viper augments its impressive ground speed with eight jump jets that allow it to jump up to a distance of two hundred and forty meters. The Viper has seven tons of Ferro-Fibrous armor to absorb any damage from shots that are lucky enough to strike it and has eight and a half tons of podspace for its weapons payload. +capabilities:Similar to the D configuration, the Viper E has an ATM-6 that is capable of filling the roles of the LRM and SRM launchers on the D configuration. The Viper E has an ER Medium Laser and two ER Small Lasers for close range direct firepower. The Viper is built on a lightweight Endo Steel chassis and powered by a weight saving 320 XL engine that propels the Viper to a top speed of 129.6 km/h. The Viper augments its impressive ground speed with eight jump jets that allow it to jump up to a distance of two hundred and forty meters. The Viper has seven tons of Ferro-Fibrous armor to absorb any damage from shots that are lucky enough to strike it and has eight and a half tons of pod space for its weapons payload. history:Clan Ghost Bear came into possession of the design in 3002 when they traded several production runs of Executioner OmniMechs for the design and production facilities on Shadow. Rather than trial for land rights to Shadow, and become embroiled in the internecine struggles of the Fire Mandrills, the Bears restructured the facility, making the lines modular, and relocated production to Strana Mechty - this modular technology proved very useful when the Ghost Bears migrated back to the Inner Sphere in the late 3050s. Surprisingly, the Bears left their first modular production facility on Strana Mechty. Production continued on Strana Mechty for Clan Ghost Bear until the mid-3060s when the Hell's Horses won the production rights and the facility (and then promptly lost the facility to Clan Ice Hellion in 3068). In addition to the manufacturing plant on Strana Mechty, at least one other planet in the Homeworlds was home to a manufacturing line producing Vipers; in 3071 Clan Goliath Scorpion captured a Viper factory from Clan Coyote on Delios, although it is unknown if the planet survived the Wars of Reaving, Goliath Scorpion Abjurement and the subsequent abandonment of the planet by the Coyotes and Cloud Cobras. manufacturer:Upsilon Plant 2J, Dominion Facility Kappa-5 diff --git a/megamek/data/mechfiles/mechs/3050U/Dragonfly (Viper) F.mtf b/megamek/data/mechfiles/mechs/3050U/Dragonfly (Viper) F.mtf index 8c3c6f8066d..26a9d84f720 100644 --- a/megamek/data/mechfiles/mechs/3050U/Dragonfly (Viper) F.mtf +++ b/megamek/data/mechfiles/mechs/3050U/Dragonfly (Viper) F.mtf @@ -166,7 +166,7 @@ Jump Jet overview:The Viper is a fast, highly-maneuverable medium OmniMech originally designed by Clan Fire Mandrill on Shadow. Codenamed the Dragonfly by the Inner Sphere forces that first encountered this small but fierce OmniMech, the name stuck because of its ability to move swiftly over the battlefield. The Viper is fast and well-armored, but significantly under-gunned compared with other Clan OmniMechs massing 35-45 tons (including the Adder, Battle Cobra, Grendel, Shadow Cat, Pouncer, and Cougar). -capabilities:A close combat configuration, the Viper F is armed with eight Heavy Machine Guns which are all linked to a pair of Machine Gun Arrays, making it extremely deadly against infantry and other soft targets. For more well-armored foes, it carries three ER Medium Lasers. This mix makes the F configuration suitable for combating infantry with integrated light vehicle support elements. This configuration was developed by Clan Hell's Horses. The Viper is built on a lightweight Endo Steel chassis and powered by a weight saving 320 XL engine that propels the Viper to a top speed of 129.6 km/h. The Viper augments its impressive ground speed with eight jump jets that allow it to jump up to a distance of two hundred and forty meters. The Viper has seven tons of Ferro-Fibrous armor to absorb any damage from shots that are lucky enough to strike it and has eight and a half tons of podspace for its weapons payload. +capabilities:A close combat configuration, the Viper F is armed with eight Heavy Machine Guns which are all linked to a pair of Machine Gun Arrays, making it extremely deadly against infantry and other soft targets. For more well-armored foes, it carries three ER Medium Lasers. This mix makes the F configuration suitable for combating infantry with integrated light vehicle support elements. This configuration was developed by Clan Hell's Horses. The Viper is built on a lightweight Endo Steel chassis and powered by a weight saving 320 XL engine that propels the Viper to a top speed of 129.6 km/h. The Viper augments its impressive ground speed with eight jump jets that allow it to jump up to a distance of two hundred and forty meters. The Viper has seven tons of Ferro-Fibrous armor to absorb any damage from shots that are lucky enough to strike it and has eight and a half tons of pod space for its weapons payload. history:Clan Ghost Bear came into possession of the design in 3002 when they traded several production runs of Executioner OmniMechs for the design and production facilities on Shadow. Rather than trial for land rights to Shadow, and become embroiled in the internecine struggles of the Fire Mandrills, the Bears restructured the facility, making the lines modular, and relocated production to Strana Mechty - this modular technology proved very useful when the Ghost Bears migrated back to the Inner Sphere in the late 3050s. Surprisingly, the Bears left their first modular production facility on Strana Mechty. Production continued on Strana Mechty for Clan Ghost Bear until the mid-3060s when the Hell's Horses won the production rights and the facility (and then promptly lost the facility to Clan Ice Hellion in 3068). In addition to the manufacturing plant on Strana Mechty, at least one other planet in the Homeworlds was home to a manufacturing line producing Vipers; in 3071 Clan Goliath Scorpion captured a Viper factory from Clan Coyote on Delios, although it is unknown if the planet survived the Wars of Reaving, Goliath Scorpion Abjurement and the subsequent abandonment of the planet by the Coyotes and Cloud Cobras. manufacturer:Upsilon Plant 2J, Dominion Facility Kappa-5 diff --git a/megamek/data/mechfiles/mechs/3050U/Dragonfly (Viper) G.mtf b/megamek/data/mechfiles/mechs/3050U/Dragonfly (Viper) G.mtf index c1fc8455ce2..0a52df52495 100644 --- a/megamek/data/mechfiles/mechs/3050U/Dragonfly (Viper) G.mtf +++ b/megamek/data/mechfiles/mechs/3050U/Dragonfly (Viper) G.mtf @@ -159,7 +159,7 @@ Jump Jet overview:The Viper is a fast, highly-maneuverable medium OmniMech originally designed by Clan Fire Mandrill on Shadow. Codenamed the Dragonfly by the Inner Sphere forces that first encountered this small but fierce OmniMech, the name stuck because of its ability to move swiftly over the battlefield. The Viper is fast and well-armored, but significantly under-gunned compared with other Clan OmniMechs massing 35-45 tons (including the Adder, Battle Cobra, Grendel, Shadow Cat, Pouncer, and Cougar). -capabilities:Another configuration of the Viper that is intended to fight at close range, the G configuration carries as its primary weapon a Plasma Cannon. This is backed up with a Heavy Medium Laser and four Anti-Personnel Gauss Rifles for protection from infantry attacks. The Viper is built on a lightweight Endo Steel chassis and powered by a weight saving 320 XL engine that propels the Viper to a top speed of 129.6 km/h. The Viper augments its impressive ground speed with eight jump jets that allow it to jump up to a distance of two hundred and forty meters. The Viper has seven tons of Ferro-Fibrous armor to absorb any damage from shots that are lucky enough to strike it and has eight and a half tons of podspace for its weapons payload. +capabilities:Another configuration of the Viper that is intended to fight at close range, the G configuration carries as its primary weapon a Plasma Cannon. This is backed up with a Heavy Medium Laser and four Anti-Personnel Gauss Rifles for protection from infantry attacks. The Viper is built on a lightweight Endo Steel chassis and powered by a weight saving 320 XL engine that propels the Viper to a top speed of 129.6 km/h. The Viper augments its impressive ground speed with eight jump jets that allow it to jump up to a distance of two hundred and forty meters. The Viper has seven tons of Ferro-Fibrous armor to absorb any damage from shots that are lucky enough to strike it and has eight and a half tons of pod space for its weapons payload. history:Clan Ghost Bear came into possession of the design in 3002 when they traded several production runs of Executioner OmniMechs for the design and production facilities on Shadow. Rather than trial for land rights to Shadow, and become embroiled in the internecine struggles of the Fire Mandrills, the Bears restructured the facility, making the lines modular, and relocated production to Strana Mechty - this modular technology proved very useful when the Ghost Bears migrated back to the Inner Sphere in the late 3050s. Surprisingly, the Bears left their first modular production facility on Strana Mechty. Production continued on Strana Mechty for Clan Ghost Bear until the mid-3060s when the Hell's Horses won the production rights and the facility (and then promptly lost the facility to Clan Ice Hellion in 3068). In addition to the manufacturing plant on Strana Mechty, at least one other planet in the Homeworlds was home to a manufacturing line producing Vipers; in 3071 Clan Goliath Scorpion captured a Viper factory from Clan Coyote on Delios, although it is unknown if the planet survived the Wars of Reaving, Goliath Scorpion Abjurement and the subsequent abandonment of the planet by the Coyotes and Cloud Cobras. manufacturer:Upsilon Plant 2J, Dominion Facility Kappa-5 diff --git a/megamek/data/mechfiles/mechs/3050U/Dragonfly (Viper) H.mtf b/megamek/data/mechfiles/mechs/3050U/Dragonfly (Viper) H.mtf index 00ee5d5f70d..6492dfff323 100644 --- a/megamek/data/mechfiles/mechs/3050U/Dragonfly (Viper) H.mtf +++ b/megamek/data/mechfiles/mechs/3050U/Dragonfly (Viper) H.mtf @@ -160,7 +160,7 @@ Jump Jet overview:The Viper is a fast, highly-maneuverable medium OmniMech originally designed by Clan Fire Mandrill on Shadow. Codenamed the Dragonfly by the Inner Sphere forces that first encountered this small but fierce OmniMech, the name stuck because of its ability to move swiftly over the battlefield. The Viper is fast and well-armored, but significantly under-gunned compared with other Clan OmniMechs massing 35-45 tons (including the Adder, Battle Cobra, Grendel, Shadow Cat, Pouncer, and Cougar). -capabilities:Configured around the heavy laser system, the Viper H has two ER Medium Lasers which are backed up by two powerful Heavy Medium Lasers and two highly accurate Small Pulse Lasers. For added protection from missile fire, this configuration also has an Anti-Missile System. This configuration was put into production by the Ice Hellions after they gained control of the Upsilon Plant 2J on Strana Mechty in 3068. The Viper is built on a lightweight Endo Steel chassis and powered by a weight saving 320 XL engine that propels the Viper to a top speed of 129.6 km/h. The Viper augments its impressive ground speed with eight jump jets that allow it to jump up to a distance of two hundred and forty meters. The Viper has seven tons of Ferro-Fibrous armor to absorb any damage from shots that are lucky enough to strike it and has eight and a half tons of podspace for its weapons payload. +capabilities:Configured around the heavy laser system, the Viper H has two ER Medium Lasers which are backed up by two powerful Heavy Medium Lasers and two highly accurate Small Pulse Lasers. For added protection from missile fire, this configuration also has an Anti-Missile System. This configuration was put into production by the Ice Hellions after they gained control of the Upsilon Plant 2J on Strana Mechty in 3068. The Viper is built on a lightweight Endo Steel chassis and powered by a weight saving 320 XL engine that propels the Viper to a top speed of 129.6 km/h. The Viper augments its impressive ground speed with eight jump jets that allow it to jump up to a distance of two hundred and forty meters. The Viper has seven tons of Ferro-Fibrous armor to absorb any damage from shots that are lucky enough to strike it and has eight and a half tons of pod space for its weapons payload. history:Clan Ghost Bear came into possession of the design in 3002 when they traded several production runs of Executioner OmniMechs for the design and production facilities on Shadow. Rather than trial for land rights to Shadow, and become embroiled in the internecine struggles of the Fire Mandrills, the Bears restructured the facility, making the lines modular, and relocated production to Strana Mechty - this modular technology proved very useful when the Ghost Bears migrated back to the Inner Sphere in the late 3050s. Surprisingly, the Bears left their first modular production facility on Strana Mechty. Production continued on Strana Mechty for Clan Ghost Bear until the mid-3060s when the Hell's Horses won the production rights and the facility (and then promptly lost the facility to Clan Ice Hellion in 3068). In addition to the manufacturing plant on Strana Mechty, at least one other planet in the Homeworlds was home to a manufacturing line producing Vipers; in 3071 Clan Goliath Scorpion captured a Viper factory from Clan Coyote on Delios, although it is unknown if the planet survived the Wars of Reaving, Goliath Scorpion Abjurement and the subsequent abandonment of the planet by the Coyotes and Cloud Cobras. manufacturer:Upsilon Plant 2J, Dominion Facility Kappa-5 diff --git a/megamek/data/mechfiles/mechs/3050U/Dragonfly (Viper) I.mtf b/megamek/data/mechfiles/mechs/3050U/Dragonfly (Viper) I.mtf index 9e9e80854c6..add104c7194 100644 --- a/megamek/data/mechfiles/mechs/3050U/Dragonfly (Viper) I.mtf +++ b/megamek/data/mechfiles/mechs/3050U/Dragonfly (Viper) I.mtf @@ -158,7 +158,7 @@ Jump Jet overview:The Viper is a fast, highly-maneuverable medium OmniMech originally designed by Clan Fire Mandrill on Shadow. Codenamed the Dragonfly by the Inner Sphere forces that first encountered this small but fierce OmniMech, the name stuck because of its ability to move swiftly over the battlefield. The Viper is fast and well-armored, but significantly under-gunned compared with other Clan OmniMechs massing 35-45 tons (including the Adder, Battle Cobra, Grendel, Shadow Cat, Pouncer, and Cougar). -capabilities:Capable of engaging an enemy at any range, the I configuration carries an ATM-3 launcher which is capable of engaging at long, medium, and short ranges. This is supported at close range by a trio of Heavy Medium Lasers which are all linked to an advanced Targeting Computer. The 'Mech also carries a Light Active Probe to allow it to detect hidden enemy units and, for further protection, an Anti-Missile System is carried which helps protect the 'Mech from missile attacks. The Viper is built on a lightweight Endo Steel chassis and powered by a weight saving 320 XL engine that propels the Viper to a top speed of 129.6 km/h. The Viper augments its impressive ground speed with eight jump jets that allow it to jump up to a distance of two hundred and forty meters. The Viper has seven tons of Ferro-Fibrous armor to absorb any damage from shots that are lucky enough to strike it and has eight and a half tons of podspace for its weapons payload. +capabilities:Capable of engaging an enemy at any range, the I configuration carries an ATM-3 launcher which is capable of engaging at long, medium, and short ranges. This is supported at close range by a trio of Heavy Medium Lasers which are all linked to an advanced Targeting Computer. The 'Mech also carries a Light Active Probe to allow it to detect hidden enemy units and, for further protection, an Anti-Missile System is carried which helps protect the 'Mech from missile attacks. The Viper is built on a lightweight Endo Steel chassis and powered by a weight saving 320 XL engine that propels the Viper to a top speed of 129.6 km/h. The Viper augments its impressive ground speed with eight jump jets that allow it to jump up to a distance of two hundred and forty meters. The Viper has seven tons of Ferro-Fibrous armor to absorb any damage from shots that are lucky enough to strike it and has eight and a half tons of pod space for its weapons payload. history:Clan Ghost Bear came into possession of the design in 3002 when they traded several production runs of Executioner OmniMechs for the design and production facilities on Shadow. Rather than trial for land rights to Shadow, and become embroiled in the internecine struggles of the Fire Mandrills, the Bears restructured the facility, making the lines modular, and relocated production to Strana Mechty - this modular technology proved very useful when the Ghost Bears migrated back to the Inner Sphere in the late 3050s. Surprisingly, the Bears left their first modular production facility on Strana Mechty. Production continued on Strana Mechty for Clan Ghost Bear until the mid-3060s when the Hell's Horses won the production rights and the facility (and then promptly lost the facility to Clan Ice Hellion in 3068). In addition to the manufacturing plant on Strana Mechty, at least one other planet in the Homeworlds was home to a manufacturing line producing Vipers; in 3071 Clan Goliath Scorpion captured a Viper factory from Clan Coyote on Delios, although it is unknown if the planet survived the Wars of Reaving, Goliath Scorpion Abjurement and the subsequent abandonment of the planet by the Coyotes and Cloud Cobras. manufacturer:Upsilon Plant 2J, Dominion Facility Kappa-5 diff --git a/megamek/data/mechfiles/mechs/3050U/Dragonfly (Viper) Prime.mtf b/megamek/data/mechfiles/mechs/3050U/Dragonfly (Viper) Prime.mtf index 99288aca0a6..bc8c483ad58 100644 --- a/megamek/data/mechfiles/mechs/3050U/Dragonfly (Viper) Prime.mtf +++ b/megamek/data/mechfiles/mechs/3050U/Dragonfly (Viper) Prime.mtf @@ -160,7 +160,7 @@ Jump Jet overview:The Viper is a fast, highly-maneuverable medium OmniMech originally designed by Clan Fire Mandrill on Shadow. Codenamed the Dragonfly by the Inner Sphere forces that first encountered this small but fierce OmniMech, the name stuck because of its ability to move swiftly over the battlefield. The Viper is fast and well-armored, but significantly under-gunned compared with other Clan OmniMechs massing 35-45 tons (including the Adder, Battle Cobra, Grendel, Shadow Cat, Pouncer, and Cougar). -capabilities:In its primary weapons configuration, the Viper is configured to fill a variety of close combat roles. The Viper has an Anti-Missile System for added defense capabilities and has two Machine Guns for use against soft targets and anti-infantry work. The Viper's main guns are two Medium Pulse Lasers and an SRM-4 launcher that allow it to harass other 'Mechs and vehicles. The Viper is built on a lightweight Endo Steel chassis and powered by a weight saving 320 XL engine that propels the Viper to a top speed of 129.6 km/h. The Viper augments its impressive ground speed with eight jump jets that allow it to jump up to a distance of two hundred and forty meters. The Viper has seven tons of Ferro-Fibrous armor to absorb any damage from shots that are lucky enough to strike it and has eight and a half tons of podspace for its weapons payload. +capabilities:In its primary weapons configuration, the Viper is configured to fill a variety of close combat roles. The Viper has an Anti-Missile System for added defense capabilities and has two Machine Guns for use against soft targets and anti-infantry work. The Viper's main guns are two Medium Pulse Lasers and an SRM-4 launcher that allow it to harass other 'Mechs and vehicles. The Viper is built on a lightweight Endo Steel chassis and powered by a weight saving 320 XL engine that propels the Viper to a top speed of 129.6 km/h. The Viper augments its impressive ground speed with eight jump jets that allow it to jump up to a distance of two hundred and forty meters. The Viper has seven tons of Ferro-Fibrous armor to absorb any damage from shots that are lucky enough to strike it and has eight and a half tons of pod space for its weapons payload. history:Clan Ghost Bear came into possession of the design in 3002 when they traded several production runs of Executioner OmniMechs for the design and production facilities on Shadow. Rather than trial for land rights to Shadow, and become embroiled in the internecine struggles of the Fire Mandrills, the Bears restructured the facility, making the lines modular, and relocated production to Strana Mechty - this modular technology proved very useful when the Ghost Bears migrated back to the Inner Sphere in the late 3050s. Surprisingly, the Bears left their first modular production facility on Strana Mechty. Production continued on Strana Mechty for Clan Ghost Bear until the mid-3060s when the Hell's Horses won the production rights and the facility (and then promptly lost the facility to Clan Ice Hellion in 3068). In addition to the manufacturing plant on Strana Mechty, at least one other planet in the Homeworlds was home to a manufacturing line producing Vipers; in 3071 Clan Goliath Scorpion captured a Viper factory from Clan Coyote on Delios, although it is unknown if the planet survived the Wars of Reaving, Goliath Scorpion Abjurement and the subsequent abandonment of the planet by the Coyotes and Cloud Cobras. manufacturer:Upsilon Plant 2J, Dominion Facility Kappa-5 diff --git a/megamek/data/mechfiles/mechs/3050U/Guillotine GLT-3N.mtf b/megamek/data/mechfiles/mechs/3050U/Guillotine GLT-3N.mtf index 7fc680219de..d009eb280d7 100644 --- a/megamek/data/mechfiles/mechs/3050U/Guillotine GLT-3N.mtf +++ b/megamek/data/mechfiles/mechs/3050U/Guillotine GLT-3N.mtf @@ -161,7 +161,7 @@ overview:The Guillotine was originally designed in 2499 as a front-line BattleMe capabilities:While its weaponry was ample for its era, as time went by the march of technology allowed for the development of larger 'Mechs which were significantly better armed. However few of these new 'Mechs could match the Guillotine in maneuverability or staying power, and so the 'Mech simply transitioned from the front-line shock role to that of a heavy raider - a task it excels at thanks to its quick speed and use of jump jets. Its mobility also makes the 'Mech adept at fighting in difficult terrain such as jungle or mountainous regions. The only serious issue with the 'Mech ironically are its weapons, which have been plagued with various problems over the centuries. -deployment:The Guillotine carries a Sunglow Type 2 Large Laser in its left arm as the primary weapon. While the Sunglow laser is an excellent weapon, there are issues with the fiber optic power cabling, which runs from the power converter hidden deep within the 'Mech out to the emitter. Running near the surface of the underarm, it is all too easy for the cable to bind when the weapon is raised over the 'Mech's head. Experienced pilots know to lower the arm in this case, but for a MechWarrior unused to the Guillotine they may try to force the line and snap it, preventing use of the 'Mech's most powerful weapon. Replacing the power cabling is an extremely expensive and time consuming process requiring considerable effort. Back-up for the large laser are four ExoStar II Medium Lasers, two in the right arm and two split between the side torsos. Like the larger lasers the ExoStar IIs consist of a power supply well-hidden within the Guillotine connected to a firing mechanism by fiber optic cables, although the eight cables which power the medium lasers don't suffer from the Sunglow's snagging issue. The final weapon on the design is a single Coventry-6 SRM-6 with one ton of reloads in the right torso. Despite centuries of correcting other faults in the system, a stubborn and persistent problem with the SRM launcher is its occasional failure to arm missiles five and six. Not even a complete redesign of the system managed to solve this bug. The problem was eventually discovered to involve the CASE protecting the missile reloads, and only its removal caused the problem to desist. +deployment:The Guillotine carries a SunGlow Type 2 Large Laser in its left arm as the primary weapon. While the SunGlow laser is an excellent weapon, there are issues with the fiber optic power cabling, which runs from the power converter hidden deep within the 'Mech out to the emitter. Running near the surface of the underarm, it is all too easy for the cable to bind when the weapon is raised over the 'Mech's head. Experienced pilots know to lower the arm in this case, but for a MechWarrior unused to the Guillotine they may try to force the line and snap it, preventing use of the 'Mech's most powerful weapon. Replacing the power cabling is an extremely expensive and time consuming process requiring considerable effort. Back-up for the large laser are four ExoStar II Medium Lasers, two in the right arm and two split between the side torsos. Like the larger lasers the ExoStar IIs consist of a power supply well-hidden within the Guillotine connected to a firing mechanism by fiber optic cables, although the eight cables which power the medium lasers don't suffer from the SunGlow's snagging issue. The final weapon on the design is a single Coventry-6 SRM-6 with one ton of reloads in the right torso. Despite centuries of correcting other faults in the system, a stubborn and persistent problem with the SRM launcher is its occasional failure to arm missiles five and six. Not even a complete redesign of the system managed to solve this bug. The problem was eventually discovered to involve the CASE protecting the missile reloads, and only its removal caused the problem to desist. history:Newhart Industries built the Guillotine from their factory on New Earth, but this was destroyed during the Amaris Civil War in 2776 as part of a celebration put on by the 12th Republican Guard. At the same time Irian BattleMechs Unlimited was building Guillotines under contract from Newheart out of Irian and continued to do so for another half-century; Lycomb-Davion IntroTech had also been producing the Guillotine from their main manufacturing facility on Demeter, but this facility was destroyed by Capellan Confederation forces early in the First Succession War. The collapse of the Star League and exodus of the SLDF scattered Guillotines across all of the Great Houses, while ComStar succeeded in raiding New Earth in 2788 and acquiring a battalion's worth from former Newhart stockpiles. In the wake of the First Succession War a shortage of the advanced components necessary for the 'Mech forced IBMU to design a downgraded variant, the GLT-4L, which they continued to produce off and on for the next few centuries. The recovery of the Helm Memory Core inspired a number of old designs, the Guillotine included, to be upgraded with lostech. Using the refurbished Newhart factory Irian's new GLT-5M model not only restored the Guillotine to its former glory but improved upon it with better (and importantly more reliable) weaponry. Irian continued producing new Guillotines, which would go on to take part in the FedCom Civil War and the Jihad. diff --git a/megamek/data/mechfiles/mechs/3050U/Hunchback HBK-5M.mtf b/megamek/data/mechfiles/mechs/3050U/Hunchback HBK-5M.mtf index e1382649ab0..3ccc1261e93 100644 --- a/megamek/data/mechfiles/mechs/3050U/Hunchback HBK-5M.mtf +++ b/megamek/data/mechfiles/mechs/3050U/Hunchback HBK-5M.mtf @@ -159,7 +159,7 @@ overview:The Hunchback is a respected and feared Reunification War-era street fi capabilities:Built for urban combat and close range brawling, this BattleMech has the heavy armor and weaponry to stand up against any foe in the dense cover of a city environment. Its heavy armament does come at a cost: in terms of maneuverability and heat dissipation the Hunchback is merely average, while the lack of long-range weapons means the Hunchback is little more than a slow moving target in the open. In an attack the slow speed of the Hunchback forces it to participate as part of the second wave, exploiting any weaknesses in the enemy's armor after they've been softened up. -deployment:Utilizing locally produced components such as the Kali Yama Big Bore autocannon and Hellion-V medium lasers, the Kali Yama-produced 5M Hunchback is a simple upgrade of the original 4G model that first saw production in 3046. The most notable changes saw the heat sinks upgraded to double-strength models, while the small laser was upgraded to a Sunglow Prism-Optic Small Pulse Laser, and CASE was added to protect against ammunition explosions. The extra weight required to add the newer systems forced Kali Yama to reduce ammunition storage to a single ton of reloads, making it unpopular with MechWarriors and spawning the unofficial HBK-5N variant. +deployment:Utilizing locally produced components such as the Kali Yama Big Bore autocannon and Hellion-V medium lasers, the Kali Yama-produced 5M Hunchback is a simple upgrade of the original 4G model that first saw production in 3046. The most notable changes saw the heat sinks upgraded to double-strength models, while the small laser was upgraded to a SunGlow Prism-Optic Small Pulse Laser, and CASE was added to protect against ammunition explosions. The extra weight required to add the newer systems forced Kali Yama to reduce ammunition storage to a single ton of reloads, making it unpopular with MechWarriors and spawning the unofficial HBK-5N variant. history:The Hunchback was originally designed and produced by Komiyaba/Nissan General Industries and sold throughout the Inner Sphere and Periphery, often fielded as part of medium and assault lances. The company was destroyed in the Succession Wars, but the Hunchback continued to remain popular, especially in the arsenals of House Kurita and House Liao where it fit the dueling nature and all-or-nothing combat styles of the two Successor States. Eventually Kali Yama Weapons Industries bought the rights to the Hunchback and restarted production at their factory on Kalidasa to supply House Marik with large numbers of the 'Mech. Dwindling stockpiles of spare parts and personal preference led many owners to remove the Hunchbacks large signature autocannon and typically install smaller weapons in larger numbers in its stead, resulting in a variety of variants collectively known as "Swayback'" because of the significant change to the 'Mech's configuration and torso structure. The rediscovery of lost technology in the years prior to the Clan Invasion inspired a number of old designs to be upgraded, the Hunchback included. Under contract from the Free Worlds League Military, Kali Yama engineers designed a variant, the HBK-5M, which sought to improve upon the original while still maintaining the "soul" of the machine. While the new variant included several improvements, mostly involving extra protection against ammunition explosions and overheating, to the chagrin of many MechWarriors this came at the cost of reduced ammunition for the autocannon. Their objections ignored, production began in 3046. The new variant came into widespread use throughout the FWLM until Operation Guerrero, when this drawback was responsible for the failure of several advances. After this, Kali Yama finally produced a new variant–the HBK-6M–which addressed this concern. In the years since, Norse-Storm BattleMechs opened a refit line to produce new Hunchback variants and the 'Mech saw use on both sides in the Jihad. diff --git a/megamek/data/mechfiles/mechs/3050U/King Crab KGC-000.mtf b/megamek/data/mechfiles/mechs/3050U/King Crab KGC-000.mtf index 9757ada3055..ac4b15d0422 100644 --- a/megamek/data/mechfiles/mechs/3050U/King Crab KGC-000.mtf +++ b/megamek/data/mechfiles/mechs/3050U/King Crab KGC-000.mtf @@ -157,7 +157,7 @@ overview:The King Crab has been a horror on the battlefield since its introducti capabilities:While not the most heavily armored 'Mech, the King Crab is still tough to crack, with sixteen tons of ferro-fibrous armor and CASE protecting its ammunition stores; however, the arms are probably the most susceptible area to receive damage and an internal hit is likely to knock an autocannon out of the fight. The 'Mech is also slow, with a cruising speed of 32 km/h and top speed of 54 km/h, and has been described as a "notorious hangar queen". -deployment:The King Crab's primary weapons are two massive Deathgiver Autocannon/20s, among the most powerful BattleMech weapons ever created. Each arm carries one of these massive weapons, and they are fed by two tons of ammo split between the side torsos. The firepower of these weapons is enough to destroy a medium 'Mech in one salvo. To protect the autocannons in combat, engineers designed the King Crab with simple hand actuators. In appearance and movement, the actuators are very similar to pincers or claws found on real crabs, a contributing factor to the 'Mech's name. To back up the autocannons, and provide some long-range capabilities, the King Crab carries a Simpson-15 LRM-15 launcher, mounted in the left torso and fed by one ton of reloads in the same location, and an Exostar Large Laser in the right torso. +deployment:The King Crab's primary weapons are two massive Deathgiver Autocannon/20s, among the most powerful BattleMech weapons ever created. Each arm carries one of these massive weapons, and they are fed by two tons of ammo split between the side torsos. The firepower of these weapons is enough to destroy a medium 'Mech in one salvo. To protect the autocannons in combat, engineers designed the King Crab with simple hand actuators. In appearance and movement, the actuators are very similar to pincers or claws found on real crabs, a contributing factor to the 'Mech's name. To back up the autocannons, and provide some long-range capabilities, the King Crab carries a Simpson-15 LRM-15 launcher, mounted in the left torso and fed by one ton of reloads in the same location, and an ExoStar Large Laser in the right torso. history:The KGC-000, designed by Cosara Weaponries scientists under General Kerensky's directives, performed brilliantly in its specified mission, though it was nowhere near the command vehicle that Defiance Industries' later Atlas was. The majority of King Crabs joined Kerensky on his Exodus, including all surviving -010 platforms; those that remained were surreptitiously purchased by ComStar and mothballed on Terra. Upon the Clans' arrival and the Battle of Tukayyid, most Com Guard commanders discovered that the original Imperator-D autocannon design could not close quickly enough with Clan machines to cause considerable damage. After being approached by ComStar, Cosara Weaponries created the -001 variant; the additional range gave the King Crab some much-needed reach. ComStar, pleased with their performance, gave Cosara permission to mass-produce the enhanced King Crab for general market sale, with ComStar receiving a major portion of the yearly earnings. Northwind production ended after the Word of Blake blockaded the system, and scattered intelligence reports indicate that the Blakists took control the Cosara plant. After being shut down for some months, the plant reopened in late 3069, continuously producing and sending a newer King Crab variant to Protectorate forces. First Precentor Dow took an extraordinary action for the once-secret organization after losing a major weapons supply. ComStar was able to infiltrate the Cosara plant and grab the new engineering designs by hiring a tiny mercenary group that specialized in corporate espionage. ComStar then approached Starcorps Industries and gave the young company the opportunity to create a new King Crab variation, the KGC-007. StarCorps accepted, eager to expand their product line, and the first -007s are scheduled to roll off the Son Hoa line in late 3071. The first three production runs have already been purchased by the LAAF and AFFC. diff --git a/megamek/data/mechfiles/mechs/3050U/King Crab KGC-005.mtf b/megamek/data/mechfiles/mechs/3050U/King Crab KGC-005.mtf index 0cf579268d2..27bde45c846 100644 --- a/megamek/data/mechfiles/mechs/3050U/King Crab KGC-005.mtf +++ b/megamek/data/mechfiles/mechs/3050U/King Crab KGC-005.mtf @@ -167,6 +167,6 @@ manufacturer:Cosara Weaponries primaryfactory:Mars systemmanufacturer:CHASSIS:Hollis Mark IIe systemmanufacturer:ENGINE:Vlar 300 -systemmanufacturer:ARMOR:Protec Tech 12 +systemmanufacturer:ARMOR:ProtecTech 12 systemmanufacturer:COMMUNICATIONS:Dalban Commline systemmanufacturer:TARGETING:Dalban HiRez-B diff --git a/megamek/data/mechfiles/mechs/3050U/King Crab KGC-008.mtf b/megamek/data/mechfiles/mechs/3050U/King Crab KGC-008.mtf index dac2a0c9371..1e7cdeb29b3 100644 --- a/megamek/data/mechfiles/mechs/3050U/King Crab KGC-008.mtf +++ b/megamek/data/mechfiles/mechs/3050U/King Crab KGC-008.mtf @@ -154,6 +154,6 @@ manufacturer:Cosara Weaponries primaryfactory:Northwind systemmanufacturer:CHASSIS:Hollis Mark IIe systemmanufacturer:ENGINE:Vlar 300 -systemmanufacturer:ARMOR:Protec Tech 12 with CASE +systemmanufacturer:ARMOR:ProtecTech 12 with CASE systemmanufacturer:COMMUNICATIONS:Dalban Commline systemmanufacturer:TARGETING:Dalban HiRez-B diff --git a/megamek/data/mechfiles/mechs/3050U/King Crab KGC-008B.mtf b/megamek/data/mechfiles/mechs/3050U/King Crab KGC-008B.mtf index 3bacb0b3b1c..c5cb6451569 100644 --- a/megamek/data/mechfiles/mechs/3050U/King Crab KGC-008B.mtf +++ b/megamek/data/mechfiles/mechs/3050U/King Crab KGC-008B.mtf @@ -170,6 +170,6 @@ manufacturer:Cosara Weaponries,Cosara Weaponries primaryfactory:Mars,Northwind systemmanufacturer:CHASSIS:Hollis Mark IIe systemmanufacturer:ENGINE:Vlar 300 -systemmanufacturer:ARMOR:Protec Tech 12 with CASE +systemmanufacturer:ARMOR:ProtecTech 12 with CASE systemmanufacturer:COMMUNICATIONS:Dalban Commline systemmanufacturer:TARGETING:Dalban HiRez-B diff --git a/megamek/data/mechfiles/mechs/3050U/UrbanMech UM-R63.mtf b/megamek/data/mechfiles/mechs/3050U/UrbanMech UM-R63.mtf index 550d42c8525..82766999a8e 100644 --- a/megamek/data/mechfiles/mechs/3050U/UrbanMech UM-R63.mtf +++ b/megamek/data/mechfiles/mechs/3050U/UrbanMech UM-R63.mtf @@ -161,7 +161,7 @@ capabilities:This was achieved by starting with a cheap, easily-produced chassis deployment:This is the official upgrade kit for the Capellan Confederation's UrbanMechs, distributed for field modification since before 3050. It replaces the Autocannon/10 with a Mydron Excel LB-X Autocannon/10 version and retains the small laser, but adds a Magna 200P Small Pulse Laser. -history:Large numbers of UrbanMechs were produced by Orguss Industries from 2675 until the destruction of their assembly lines. The UrbanMech reentered production at the Betelgeuse facility of Hellespont Industrials during the Jihad, and continued to be manufactured up through 3149. As such, UrbanMechs could be found in all of the armies of the Successor States. However most military leaders saw the slow little 'Mech as a liability, confining their stockpiles to garrison duty or stripping them of parts. This dismissive attitude towards the UrbanMech saved it from the ravages of the Succession Wars and ensured its continued use into the thirty-first century. The Capellan Confederation remained the largest and only user of UrbanMechs to actually deploy them for front-line duty, a result of the devastation of the Fourth Succession War and their desperation for any 'Mech to replenish their losses. The Confederation Reserve Cavalry and Capellan Defense Force had the lion's share of UrbanMechs, followed by the Tikonov Republican Guard and St. Ives Armored Cavalry; outside the Confederation the Federated Suns' Capellan March Militia fielded the largest number of UrbanMechs due to the fact it was composed of large amounts of captured Capellan equipment. Its prominence within the Confederation meant the UrbanMech was among those 'Mechs within the CCAF to receive upgrades following the recovery of lostech; the other States followed suit with much less priority over improving other 'Mechs. Despite this the sheer costs necessary to replace the UrbanMech's engine and increase its top speed meant even the Confederation limited their refit packages to improving the weapons and armor only. A testament to the desperation of the Word of Blake Jihad, Hellespont Industrials would reactivate a shuttered production facility on Betelgeuse to produce the UrbanMech alongside primitive "retrotech" designs for material starved Capellan garrison forces. This plant would maintain production of the UrbanMech in a steadily increasing volume of configurations throughout the Dark Age Era as the CCAF secretly expanded before it waged war against the Republic of the Sphere. Rather than dramatic and expensive enhancements, Hellespont's new variants retain the venerable design's low ground speed urban combat focus and can be applied as refits as readily as new production. +history:Large numbers of UrbanMechs were produced by Orgus Industries from 2675 until the destruction of their assembly lines. The UrbanMech reentered production at the Betelgeuse facility of Hellespont Industrials during the Jihad, and continued to be manufactured up through 3149. As such, UrbanMechs could be found in all of the armies of the Successor States. However most military leaders saw the slow little 'Mech as a liability, confining their stockpiles to garrison duty or stripping them of parts. This dismissive attitude towards the UrbanMech saved it from the ravages of the Succession Wars and ensured its continued use into the thirty-first century. The Capellan Confederation remained the largest and only user of UrbanMechs to actually deploy them for front-line duty, a result of the devastation of the Fourth Succession War and their desperation for any 'Mech to replenish their losses. The Confederation Reserve Cavalry and Capellan Defense Force had the lion's share of UrbanMechs, followed by the Tikonov Republican Guard and St. Ives Armored Cavalry; outside the Confederation the Federated Suns' Capellan March Militia fielded the largest number of UrbanMechs due to the fact it was composed of large amounts of captured Capellan equipment. Its prominence within the Confederation meant the UrbanMech was among those 'Mechs within the CCAF to receive upgrades following the recovery of lostech; the other States followed suit with much less priority over improving other 'Mechs. Despite this the sheer costs necessary to replace the UrbanMech's engine and increase its top speed meant even the Confederation limited their refit packages to improving the weapons and armor only. A testament to the desperation of the Word of Blake Jihad, Hellespont Industrials would reactivate a shuttered production facility on Betelgeuse to produce the UrbanMech alongside primitive "retrotech" designs for material starved Capellan garrison forces. This plant would maintain production of the UrbanMech in a steadily increasing volume of configurations throughout the Dark Age Era as the CCAF secretly expanded before it waged war against the Republic of the Sphere. Rather than dramatic and expensive enhancements, Hellespont's new variants retain the venerable design's low ground speed urban combat focus and can be applied as refits as readily as new production. manufacturer:Refit primaryfactory:Various diff --git a/megamek/data/mechfiles/mechs/3050U/UrbanMech UM-R68.mtf b/megamek/data/mechfiles/mechs/3050U/UrbanMech UM-R68.mtf index 3e52d8f23f1..07ecb38eefd 100644 --- a/megamek/data/mechfiles/mechs/3050U/UrbanMech UM-R68.mtf +++ b/megamek/data/mechfiles/mechs/3050U/UrbanMech UM-R68.mtf @@ -161,7 +161,7 @@ capabilities:This was achieved by starting with a cheap, easily-produced chassis deployment:Eschewing the autocannon, this Draconis Combine variant carries an MRM-30 with two tons of ammo. The added damage potential proved a nasty surprise to Clan Ghost Bear during the Combine-Ghost Bear War. -history:Large numbers of UrbanMechs were produced by Orguss Industries from 2675 until the destruction of their assembly lines. The UrbanMech reentered production at the Betelgeuse facility of Hellespont Industrials during the Jihad, and continued to be manufactured up through 3149. As such, UrbanMechs could be found in all of the armies of the Successor States. However most military leaders saw the slow little 'Mech as a liability, confining their stockpiles to garrison duty or stripping them of parts. This dismissive attitude towards the UrbanMech saved it from the ravages of the Succession Wars and ensured its continued use into the thirty-first century. The Capellan Confederation remained the largest and only user of UrbanMechs to actually deploy them for front-line duty, a result of the devastation of the Fourth Succession War and their desperation for any 'Mech to replenish their losses. The Confederation Reserve Cavalry and Capellan Defense Force had the lion's share of UrbanMechs, followed by the Tikonov Republican Guard and St. Ives Armored Cavalry; outside the Confederation the Federated Suns' Capellan March Militia fielded the largest number of UrbanMechs due to the fact it was composed of large amounts of captured Capellan equipment. Its prominence within the Confederation meant the UrbanMech was among those 'Mechs within the CCAF to receive upgrades following the recovery of lostech; the other States followed suit with much less priority over improving other 'Mechs. Despite this the sheer costs necessary to replace the UrbanMech's engine and increase its top speed meant even the Confederation limited their refit packages to improving the weapons and armor only. A testament to the desperation of the Word of Blake Jihad, Hellespont Industrials would reactivate a shuttered production facility on Betelgeuse to produce the UrbanMech alongside primitive "retrotech" designs for material starved Capellan garrison forces. This plant would maintain production of the UrbanMech in a steadily increasing volume of configurations throughout the Dark Age Era as the CCAF secretly expanded before it waged war against the Republic of the Sphere. Rather than dramatic and expensive enhancements, Hellespont's new variants retain the venerable design's low ground speed urban combat focus and can be applied as refits as readily as new production. +history:Large numbers of UrbanMechs were produced by Orgus Industries from 2675 until the destruction of their assembly lines. The UrbanMech reentered production at the Betelgeuse facility of Hellespont Industrials during the Jihad, and continued to be manufactured up through 3149. As such, UrbanMechs could be found in all of the armies of the Successor States. However most military leaders saw the slow little 'Mech as a liability, confining their stockpiles to garrison duty or stripping them of parts. This dismissive attitude towards the UrbanMech saved it from the ravages of the Succession Wars and ensured its continued use into the thirty-first century. The Capellan Confederation remained the largest and only user of UrbanMechs to actually deploy them for front-line duty, a result of the devastation of the Fourth Succession War and their desperation for any 'Mech to replenish their losses. The Confederation Reserve Cavalry and Capellan Defense Force had the lion's share of UrbanMechs, followed by the Tikonov Republican Guard and St. Ives Armored Cavalry; outside the Confederation the Federated Suns' Capellan March Militia fielded the largest number of UrbanMechs due to the fact it was composed of large amounts of captured Capellan equipment. Its prominence within the Confederation meant the UrbanMech was among those 'Mechs within the CCAF to receive upgrades following the recovery of lostech; the other States followed suit with much less priority over improving other 'Mechs. Despite this the sheer costs necessary to replace the UrbanMech's engine and increase its top speed meant even the Confederation limited their refit packages to improving the weapons and armor only. A testament to the desperation of the Word of Blake Jihad, Hellespont Industrials would reactivate a shuttered production facility on Betelgeuse to produce the UrbanMech alongside primitive "retrotech" designs for material starved Capellan garrison forces. This plant would maintain production of the UrbanMech in a steadily increasing volume of configurations throughout the Dark Age Era as the CCAF secretly expanded before it waged war against the Republic of the Sphere. Rather than dramatic and expensive enhancements, Hellespont's new variants retain the venerable design's low ground speed urban combat focus and can be applied as refits as readily as new production. manufacturer:Refit primaryfactory:Various diff --git a/megamek/data/mechfiles/mechs/3050U/UrbanMech UM-R70.mtf b/megamek/data/mechfiles/mechs/3050U/UrbanMech UM-R70.mtf index 5879a8246d7..7c8b5b3e259 100644 --- a/megamek/data/mechfiles/mechs/3050U/UrbanMech UM-R70.mtf +++ b/megamek/data/mechfiles/mechs/3050U/UrbanMech UM-R70.mtf @@ -161,7 +161,7 @@ capabilities:This was achieved by starting with a cheap, easily-produced chassis deployment:The Federated Suns -70 model is an upgrade that has greater potential than the -R63. The -70 uses Ferro-Fibrous armor and mounts a Rotary Autocannon/5, which can fire up to six times the normal rate of fire, and carries two tons of ammunition. For backup weapons, it carries an Extended Range Medium Laser and Extended Range Small Laser. -history:Large numbers of UrbanMechs were produced by Orguss Industries from 2675 until the destruction of their assembly lines. The UrbanMech reentered production at the Betelgeuse facility of Hellespont Industrials during the Jihad, and continued to be manufactured up through 3149. As such, UrbanMechs could be found in all of the armies of the Successor States. However most military leaders saw the slow little 'Mech as a liability, confining their stockpiles to garrison duty or stripping them of parts. This dismissive attitude towards the UrbanMech saved it from the ravages of the Succession Wars and ensured its continued use into the thirty-first century. The Capellan Confederation remained the largest and only user of UrbanMechs to actually deploy them for front-line duty, a result of the devastation of the Fourth Succession War and their desperation for any 'Mech to replenish their losses. The Confederation Reserve Cavalry and Capellan Defense Force had the lion's share of UrbanMechs, followed by the Tikonov Republican Guard and St. Ives Armored Cavalry; outside the Confederation the Federated Suns' Capellan March Militia fielded the largest number of UrbanMechs due to the fact it was composed of large amounts of captured Capellan equipment. Its prominence within the Confederation meant the UrbanMech was among those 'Mechs within the CCAF to receive upgrades following the recovery of lostech; the other States followed suit with much less priority over improving other 'Mechs. Despite this the sheer costs necessary to replace the UrbanMech's engine and increase its top speed meant even the Confederation limited their refit packages to improving the weapons and armor only. A testament to the desperation of the Word of Blake Jihad, Hellespont Industrials would reactivate a shuttered production facility on Betelgeuse to produce the UrbanMech alongside primitive "retrotech" designs for material starved Capellan garrison forces. This plant would maintain production of the UrbanMech in a steadily increasing volume of configurations throughout the Dark Age Era as the CCAF secretly expanded before it waged war against the Republic of the Sphere. Rather than dramatic and expensive enhancements, Hellespont's new variants retain the venerable design's low ground speed urban combat focus and can be applied as refits as readily as new production. +history:Large numbers of UrbanMechs were produced by Orgus Industries from 2675 until the destruction of their assembly lines. The UrbanMech reentered production at the Betelgeuse facility of Hellespont Industrials during the Jihad, and continued to be manufactured up through 3149. As such, UrbanMechs could be found in all of the armies of the Successor States. However most military leaders saw the slow little 'Mech as a liability, confining their stockpiles to garrison duty or stripping them of parts. This dismissive attitude towards the UrbanMech saved it from the ravages of the Succession Wars and ensured its continued use into the thirty-first century. The Capellan Confederation remained the largest and only user of UrbanMechs to actually deploy them for front-line duty, a result of the devastation of the Fourth Succession War and their desperation for any 'Mech to replenish their losses. The Confederation Reserve Cavalry and Capellan Defense Force had the lion's share of UrbanMechs, followed by the Tikonov Republican Guard and St. Ives Armored Cavalry; outside the Confederation the Federated Suns' Capellan March Militia fielded the largest number of UrbanMechs due to the fact it was composed of large amounts of captured Capellan equipment. Its prominence within the Confederation meant the UrbanMech was among those 'Mechs within the CCAF to receive upgrades following the recovery of lostech; the other States followed suit with much less priority over improving other 'Mechs. Despite this the sheer costs necessary to replace the UrbanMech's engine and increase its top speed meant even the Confederation limited their refit packages to improving the weapons and armor only. A testament to the desperation of the Word of Blake Jihad, Hellespont Industrials would reactivate a shuttered production facility on Betelgeuse to produce the UrbanMech alongside primitive "retrotech" designs for material starved Capellan garrison forces. This plant would maintain production of the UrbanMech in a steadily increasing volume of configurations throughout the Dark Age Era as the CCAF secretly expanded before it waged war against the Republic of the Sphere. Rather than dramatic and expensive enhancements, Hellespont's new variants retain the venerable design's low ground speed urban combat focus and can be applied as refits as readily as new production. manufacturer:Refit primaryfactory:Various diff --git a/megamek/data/mechfiles/mechs/3050U/Urbanmech UM-R69.mtf b/megamek/data/mechfiles/mechs/3050U/Urbanmech UM-R69.mtf index 1e875a487ce..6bb2958ab3a 100644 --- a/megamek/data/mechfiles/mechs/3050U/Urbanmech UM-R69.mtf +++ b/megamek/data/mechfiles/mechs/3050U/Urbanmech UM-R69.mtf @@ -161,7 +161,7 @@ capabilities:This was achieved by starting with a cheap, easily-produced chassis deployment:This Free Worlds League variant upgrades the autocannon to an Ultra Autocannon/10 and the laser to an ER Small Laser. This is all made possible by the upgrade to five tons of Ferro-Fibrous armor and the removal of the eleventh heat sink. While the ultra-class autocannon provides superior firepower, it can also eat through the single ton of ammunition at an alarming rate. -history:Large numbers of UrbanMechs were produced by Orguss Industries from 2675 until the destruction of their assembly lines. The UrbanMech reentered production at the Betelgeuse facility of Hellespont Industrials during the Jihad, and continued to be manufactured up through 3149. As such, UrbanMechs could be found in all of the armies of the Successor States. However most military leaders saw the slow little 'Mech as a liability, confining their stockpiles to garrison duty or stripping them of parts. This dismissive attitude towards the UrbanMech saved it from the ravages of the Succession Wars and ensured its continued use into the thirty-first century. The Capellan Confederation remained the largest and only user of UrbanMechs to actually deploy them for front-line duty, a result of the devastation of the Fourth Succession War and their desperation for any 'Mech to replenish their losses. The Confederation Reserve Cavalry and Capellan Defense Force had the lion's share of UrbanMechs, followed by the Tikonov Republican Guard and St. Ives Armored Cavalry; outside the Confederation the Federated Suns' Capellan March Militia fielded the largest number of UrbanMechs due to the fact it was composed of large amounts of captured Capellan equipment. Its prominence within the Confederation meant the UrbanMech was among those 'Mechs within the CCAF to receive upgrades following the recovery of lostech; the other States followed suit with much less priority over improving other 'Mechs. Despite this the sheer costs necessary to replace the UrbanMech's engine and increase its top speed meant even the Confederation limited their refit packages to improving the weapons and armor only. A testament to the desperation of the Word of Blake Jihad, Hellespont Industrials would reactivate a shuttered production facility on Betelgeuse to produce the UrbanMech alongside primitive "retrotech" designs for material starved Capellan garrison forces. This plant would maintain production of the UrbanMech in a steadily increasing volume of configurations throughout the Dark Age Era as the CCAF secretly expanded before it waged war against the Republic of the Sphere. Rather than dramatic and expensive enhancements, Hellespont's new variants retain the venerable design's low ground speed urban combat focus and can be applied as refits as readily as new production. +history:Large numbers of UrbanMechs were produced by Orgus Industries from 2675 until the destruction of their assembly lines. The UrbanMech reentered production at the Betelgeuse facility of Hellespont Industrials during the Jihad, and continued to be manufactured up through 3149. As such, UrbanMechs could be found in all of the armies of the Successor States. However most military leaders saw the slow little 'Mech as a liability, confining their stockpiles to garrison duty or stripping them of parts. This dismissive attitude towards the UrbanMech saved it from the ravages of the Succession Wars and ensured its continued use into the thirty-first century. The Capellan Confederation remained the largest and only user of UrbanMechs to actually deploy them for front-line duty, a result of the devastation of the Fourth Succession War and their desperation for any 'Mech to replenish their losses. The Confederation Reserve Cavalry and Capellan Defense Force had the lion's share of UrbanMechs, followed by the Tikonov Republican Guard and St. Ives Armored Cavalry; outside the Confederation the Federated Suns' Capellan March Militia fielded the largest number of UrbanMechs due to the fact it was composed of large amounts of captured Capellan equipment. Its prominence within the Confederation meant the UrbanMech was among those 'Mechs within the CCAF to receive upgrades following the recovery of lostech; the other States followed suit with much less priority over improving other 'Mechs. Despite this the sheer costs necessary to replace the UrbanMech's engine and increase its top speed meant even the Confederation limited their refit packages to improving the weapons and armor only. A testament to the desperation of the Word of Blake Jihad, Hellespont Industrials would reactivate a shuttered production facility on Betelgeuse to produce the UrbanMech alongside primitive "retrotech" designs for material starved Capellan garrison forces. This plant would maintain production of the UrbanMech in a steadily increasing volume of configurations throughout the Dark Age Era as the CCAF secretly expanded before it waged war against the Republic of the Sphere. Rather than dramatic and expensive enhancements, Hellespont's new variants retain the venerable design's low ground speed urban combat focus and can be applied as refits as readily as new production. manufacturer:Refit primaryfactory:Various diff --git a/megamek/data/mechfiles/mechs/3055U/Hellhound (Conjurer) 3.mtf b/megamek/data/mechfiles/mechs/3055U/Hellhound (Conjurer) 3.mtf index bbbdf619576..85bda622bd2 100644 --- a/megamek/data/mechfiles/mechs/3055U/Hellhound (Conjurer) 3.mtf +++ b/megamek/data/mechfiles/mechs/3055U/Hellhound (Conjurer) 3.mtf @@ -163,7 +163,7 @@ history:Even with an established infrastructure, rebuilding a destroyed Touman f manufacturer:Irece Alpha primaryfactory:Irece systemmanufacturer:CHASSIS:Puma Type Medium Endo Steel -systemmanufacturer:ENGINE:Star League Standart 300 +systemmanufacturer:ENGINE:Star League Standard 300 systemmanufacturer:ARMOR:Alpha Plate Special Ferro-Fibrous systemmanufacturer:COMMUNICATIONS:JNE II Integrated systemmanufacturer:TARGETING:Build 4 CAT Advanced TTS diff --git a/megamek/data/mechfiles/mechs/3058Uu/Kodiak 2.mtf b/megamek/data/mechfiles/mechs/3058Uu/Kodiak 2.mtf index ad87a400cf2..b7743684e55 100644 --- a/megamek/data/mechfiles/mechs/3058Uu/Kodiak 2.mtf +++ b/megamek/data/mechfiles/mechs/3058Uu/Kodiak 2.mtf @@ -157,7 +157,7 @@ CLDoubleHeatSink -Empty- -Empty- -capabilities:Though not taken to the same extreme as other Clan Totem 'Mechs, the Kodiak does epitomize the Ghost Bears' method of warfare, combining an impressive defensive platform with surprising amounts of speed and firepower. Its massive 400-rated XL Engine propels the Kodiak to a maximum speed of 64.8 km/h, while seventeen and a half tons of Compound 12A2 gives it impressive armor protection. Though it mounts an incredible amount of firepower, even the use of twenty double heat sinks cannot prevent overheating problems when they are all fired simultaneously, though most MechWarriors learn to use their weapons sparingly and love the 'Mech's ability to deliver a massive knockout punch. The Kodiak incorporates the Garret L20 as its communications system, and uses the RCA Instatrack Mark IX for targeting, however the "claws" mounted on both of its arms are purely aesthetic. +capabilities:Though not taken to the same extreme as other Clan Totem 'Mechs, the Kodiak does epitomize the Ghost Bears' method of warfare, combining an impressive defensive platform with surprising amounts of speed and firepower. Its massive 400-rated XL Engine propels the Kodiak to a maximum speed of 64.8 km/h, while seventeen and a half tons of Compound 12A2 gives it impressive armor protection. Though it mounts an incredible amount of firepower, even the use of twenty double heat sinks cannot prevent overheating problems when they are all fired simultaneously, though most MechWarriors learn to use their weapons sparingly and love the 'Mech's ability to deliver a massive knockout punch. The Kodiak incorporates the Garret L20 as its communications system, and uses the RCA Instatrac Mark IX for targeting, however the "claws" mounted on both of its arms are purely aesthetic. deployment:A more mobile variant that first saw action during the Combine-Ghost Bear War on Richmond, the Kodiak 2 was an attempt to solve the original's heat problem and increase its mobility by mounting jump jets, enabling it to leap up to one hundred and twenty meters, in place of four medium lasers and one missile launcher. diff --git a/megamek/data/mechfiles/mechs/3058Uu/Kodiak 3.mtf b/megamek/data/mechfiles/mechs/3058Uu/Kodiak 3.mtf index 47057aaa2e6..770e8be54c7 100644 --- a/megamek/data/mechfiles/mechs/3058Uu/Kodiak 3.mtf +++ b/megamek/data/mechfiles/mechs/3058Uu/Kodiak 3.mtf @@ -156,7 +156,7 @@ Clan LB 20-X Cluster Ammo -Empty- -Empty- -capabilities:Though not taken to the same extreme as other Clan Totem 'Mechs, the Kodiak does epitomize the Ghost Bears' method of warfare, combining an impressive defensive platform with surprising amounts of speed and firepower. Its massive 400-rated XL Engine propels the Kodiak to a maximum speed of 64.8 km/h, while seventeen and a half tons of Compound 12A2 gives it impressive armor protection. Though it mounts an incredible amount of firepower, even the use of twenty double heat sinks cannot prevent overheating problems when they are all fired simultaneously, though most MechWarriors learn to use their weapons sparingly and love the 'Mech's ability to deliver a massive knockout punch. The Kodiak incorporates the Garret L20 as its communications system, and uses the RCA Instatrack Mark IX for targeting, however the "claws" mounted on both of its arms are purely aesthetic. +capabilities:Though not taken to the same extreme as other Clan Totem 'Mechs, the Kodiak does epitomize the Ghost Bears' method of warfare, combining an impressive defensive platform with surprising amounts of speed and firepower. Its massive 400-rated XL Engine propels the Kodiak to a maximum speed of 64.8 km/h, while seventeen and a half tons of Compound 12A2 gives it impressive armor protection. Though it mounts an incredible amount of firepower, even the use of twenty double heat sinks cannot prevent overheating problems when they are all fired simultaneously, though most MechWarriors learn to use their weapons sparingly and love the 'Mech's ability to deliver a massive knockout punch. The Kodiak incorporates the Garret L20 as its communications system, and uses the RCA Instatrac Mark IX for targeting, however the "claws" mounted on both of its arms are purely aesthetic. deployment:This variant created by Clan Snow Raven in the mid-3060s turns the Kodiak into an anti-aircraft platform. Removing all but four of the arm-mounted medium lasers and reducing the number of heat sinks to fourteen freed up room for a pair of LB-X Autocannon/20s, three tons of ammo each, and an advanced targeting computer. diff --git a/megamek/data/mechfiles/mechs/3058Uu/Kodiak 4.mtf b/megamek/data/mechfiles/mechs/3058Uu/Kodiak 4.mtf index b10539af43f..fff54227573 100644 --- a/megamek/data/mechfiles/mechs/3058Uu/Kodiak 4.mtf +++ b/megamek/data/mechfiles/mechs/3058Uu/Kodiak 4.mtf @@ -157,7 +157,7 @@ CLDoubleHeatSink -Empty- -Empty- -capabilities:Though not taken to the same extreme as other Clan Totem 'Mechs, the Kodiak does epitomize the Ghost Bears' method of warfare, combining an impressive defensive platform with surprising amounts of speed and firepower. Its massive 400-rated XL Engine propels the Kodiak to a maximum speed of 64.8 km/h, while seventeen and a half tons of Compound 12A2 gives it impressive armor protection. Though it mounts an incredible amount of firepower, even the use of twenty double heat sinks cannot prevent overheating problems when they are all fired simultaneously, though most MechWarriors learn to use their weapons sparingly and love the 'Mech's ability to deliver a massive knockout punch. The Kodiak incorporates the Garret L20 as its communications system, and uses the RCA Instatrack Mark IX for targeting, however the "claws" mounted on both of its arms are purely aesthetic. +capabilities:Though not taken to the same extreme as other Clan Totem 'Mechs, the Kodiak does epitomize the Ghost Bears' method of warfare, combining an impressive defensive platform with surprising amounts of speed and firepower. Its massive 400-rated XL Engine propels the Kodiak to a maximum speed of 64.8 km/h, while seventeen and a half tons of Compound 12A2 gives it impressive armor protection. Though it mounts an incredible amount of firepower, even the use of twenty double heat sinks cannot prevent overheating problems when they are all fired simultaneously, though most MechWarriors learn to use their weapons sparingly and love the 'Mech's ability to deliver a massive knockout punch. The Kodiak incorporates the Garret L20 as its communications system, and uses the RCA Instatrac Mark IX for targeting, however the "claws" mounted on both of its arms are purely aesthetic. deployment:This variant mounts an Artemis IV FCS enhanced LRM-20 and a pair of ER Medium Lasers in each arm. For additional short range firepower, an LB 20-X AC is carried in the right torso. diff --git a/megamek/data/mechfiles/mechs/3058Uu/Kodiak 5.mtf b/megamek/data/mechfiles/mechs/3058Uu/Kodiak 5.mtf index 478596d8981..752e2bbb3cd 100644 --- a/megamek/data/mechfiles/mechs/3058Uu/Kodiak 5.mtf +++ b/megamek/data/mechfiles/mechs/3058Uu/Kodiak 5.mtf @@ -162,7 +162,7 @@ CLDoubleHeatSink -Empty- -Empty- -capabilities:Though not taken to the same extreme as other Clan Totem 'Mechs, the Kodiak does epitomize the Ghost Bears' method of warfare, combining an impressive defensive platform with surprising amounts of speed and firepower. Its massive 400-rated XL Engine propels the Kodiak to a maximum speed of 64.8 km/h, while seventeen and a half tons of Compound 12A2 gives it impressive armor protection. Though it mounts an incredible amount of firepower, even the use of twenty double heat sinks cannot prevent overheating problems when they are all fired simultaneously, though most MechWarriors learn to use their weapons sparingly and love the 'Mech's ability to deliver a massive knockout punch. The Kodiak incorporates the Garret L20 as its communications system, and uses the RCA Instatrack Mark IX for targeting, however the "claws" mounted on both of its arms are purely aesthetic. +capabilities:Though not taken to the same extreme as other Clan Totem 'Mechs, the Kodiak does epitomize the Ghost Bears' method of warfare, combining an impressive defensive platform with surprising amounts of speed and firepower. Its massive 400-rated XL Engine propels the Kodiak to a maximum speed of 64.8 km/h, while seventeen and a half tons of Compound 12A2 gives it impressive armor protection. Though it mounts an incredible amount of firepower, even the use of twenty double heat sinks cannot prevent overheating problems when they are all fired simultaneously, though most MechWarriors learn to use their weapons sparingly and love the 'Mech's ability to deliver a massive knockout punch. The Kodiak incorporates the Garret L20 as its communications system, and uses the RCA Instatrac Mark IX for targeting, however the "claws" mounted on both of its arms are purely aesthetic. deployment:This variant is a dedicated close range brawler. Adding three more heat sinks helps keep it cool as it employs nine ER Medium Lasers and two ER Large Lasers. The Gauss Rifle remains in the right torso. diff --git a/megamek/data/mechfiles/mechs/3058Uu/Kodiak.mtf b/megamek/data/mechfiles/mechs/3058Uu/Kodiak.mtf index 8954d5118c9..3b4e10a81fc 100644 --- a/megamek/data/mechfiles/mechs/3058Uu/Kodiak.mtf +++ b/megamek/data/mechfiles/mechs/3058Uu/Kodiak.mtf @@ -165,7 +165,7 @@ CLDoubleHeatSink overview:The Kodiak is a fast Assault 'Mech designed by Clan Ghost Bear as a second-line counterpart to the Gladiator. -capabilities:Though not taken to the same extreme as other Clan Totem 'Mechs, the Kodiak does epitomize the Ghost Bears' method of warfare, combining an impressive defensive platform with surprising amounts of speed and firepower. Its massive 400-rated XL Engine propels the Kodiak to a maximum speed of 64.8 km/h, while seventeen and a half tons of Compound 12A2 gives it impressive armor protection. Though it mounts an incredible amount of firepower, even the use of twenty double heat sinks cannot prevent overheating problems when they are all fired simultaneously, though most MechWarriors learn to use their weapons sparingly and love the 'Mech's ability to deliver a massive knockout punch. The Kodiak incorporates the Garret L20 as its communications system, and uses the RCA Instatrack Mark IX for targeting, however the "claws" mounted on both of its arms are purely aesthetic. +capabilities:Though not taken to the same extreme as other Clan Totem 'Mechs, the Kodiak does epitomize the Ghost Bears' method of warfare, combining an impressive defensive platform with surprising amounts of speed and firepower. Its massive 400-rated XL Engine propels the Kodiak to a maximum speed of 64.8 km/h, while seventeen and a half tons of Compound 12A2 gives it impressive armor protection. Though it mounts an incredible amount of firepower, even the use of twenty double heat sinks cannot prevent overheating problems when they are all fired simultaneously, though most MechWarriors learn to use their weapons sparingly and love the 'Mech's ability to deliver a massive knockout punch. The Kodiak incorporates the Garret L20 as its communications system, and uses the RCA Instatrac Mark IX for targeting, however the "claws" mounted on both of its arms are purely aesthetic. deployment:The Kodiak's primary armament consists of devastating short-range weaponry; namely the single Series II Ultra AC/20 occupying its entire right torso, and twin Streak SRM-6s situated in the left torso. These powerful weapons enable the Kodiak to savage any foe, but care must be taken with the limited ammunition at the MechWarrior's disposal. The 'Mech supplements its primary weaponry with eight Series 2a ER Medium Lasers, four above each hand set into a claw-like array. The ER Medium Lasers, powered by the fusion power plant, provide hefty firepower long after the ammunition bays have run dry. While the Kodiak is a cruel opponent close up, it is far from defenseless at long-range; mounted directly beneath the engine is a Series 7k ER Large Laser, allowing it to soften up targets as it advances for the kill. diff --git a/megamek/data/mechfiles/mechs/3075/Ostroc OSR-2Cb.mtf b/megamek/data/mechfiles/mechs/3075/Ostroc OSR-2Cb.mtf index 6614884b6d7..cfa703cb104 100644 --- a/megamek/data/mechfiles/mechs/3075/Ostroc OSR-2Cb.mtf +++ b/megamek/data/mechfiles/mechs/3075/Ostroc OSR-2Cb.mtf @@ -162,7 +162,7 @@ capabilities:Its unique walker/pod profile, later seen in the Stalker and Maraud deployment:This upgrade of the 2C was used by the SLDF Royals starting in 2729. The large lasers are upgraded to ER Large Lasers, and the SRM-4 is replaced with a pair of Streak SRM-2s. Fourteen double heat sinks keep this 'Mech cool, while Ferro-Fibrous armor gives it additional protection. -history:The best-known of Ostman Industries' Ost Class of 'Mechs, the Ostroc debuted in 2511 and proved so successful in this role production continued for approximately 200 years. While a quality 'Mech, the low production capacity of Ostman Industries made the Ostroc a rarity; indeed the company licensed their other Ost 'Mechs out to Kong Interstellar just to maintain their rate of production, and the majority of those produced were assigned garrison duties within the Terran Hegemony. Still, the 'Mech saw action in every major conflict of the Star League, especially towards the end in the civil war and subsequent First Succession War. The destruction of Ostman Industries meant an end to any new Ostrocs, although all sides of the Succession Wars continued to field these 'Mechs in combat, particularly the Draconis Combine. It was because of the small number and wide dispersal of surviving Ostrocs that the design was largely passed over while others were being updated after the Helm Memory Core discovery. A major revitalization of the design took place within the Capellan Confederation after the Clan Invasion. Having largely rebuilt their forces after the previous decades' setbacks, the Strategios wanted to update the ancient 'Mech, but rather than reverse-engineering the original they ordered all Capellan 'Mech manufacturers to submit bids for a replacement. Ceres Metals was the only one to send in a proposal which matched exactly what they wanted and won the contract, completing the first production run in January 3067. Versions of these new Ostrocs also started showing up in the Taurian Concordat and Circinus Federation, a result of espionage according to Capellan charges. +history:The best-known of Ostmann Industries' Ost Class of 'Mechs, the Ostroc debuted in 2511 and proved so successful in this role production continued for approximately 200 years. While a quality 'Mech, the low production capacity of Ostmann Industries made the Ostroc a rarity; indeed the company licensed their other Ost 'Mechs out to Kong Interstellar just to maintain their rate of production, and the majority of those produced were assigned garrison duties within the Terran Hegemony. Still, the 'Mech saw action in every major conflict of the Star League, especially towards the end in the civil war and subsequent First Succession War. The destruction of Ostmann Industries meant an end to any new Ostrocs, although all sides of the Succession Wars continued to field these 'Mechs in combat, particularly the Draconis Combine. It was because of the small number and wide dispersal of surviving Ostrocs that the design was largely passed over while others were being updated after the Helm Memory Core discovery. A major revitalization of the design took place within the Capellan Confederation after the Clan Invasion. Having largely rebuilt their forces after the previous decades' setbacks, the Strategios wanted to update the ancient 'Mech, but rather than reverse-engineering the original they ordered all Capellan 'Mech manufacturers to submit bids for a replacement. Ceres Metals was the only one to send in a proposal which matched exactly what they wanted and won the contract, completing the first production run in January 3067. Versions of these new Ostrocs also started showing up in the Taurian Concordat and Circinus Federation, a result of espionage according to Capellan charges. manufacturer:Ostmann Industries,Field Refits primaryfactory:Terra,Various diff --git a/megamek/data/mechfiles/mechs/3085u/ONN/Cyclops CP-11-B.mtf b/megamek/data/mechfiles/mechs/3085u/ONN/Cyclops CP-11-B.mtf index fcd81679df8..17c353d8e7b 100644 --- a/megamek/data/mechfiles/mechs/3085u/ONN/Cyclops CP-11-B.mtf +++ b/megamek/data/mechfiles/mechs/3085u/ONN/Cyclops CP-11-B.mtf @@ -161,7 +161,7 @@ Ferro-Fibrous overview:The Cyclops began production in 2710 as an assault BattleMech and headquarters unit for Star League Defense Force field commanders. -capabilities:A decent mix of weapons provided the Cyclops with both long- and short-range firepower and a sizable engine to keep up with mobile operations. But the centerpiece of the Cyclops is its sophisticated holographic battle computer, the Tacticon B-2000. When combined with the Omstead Olmstead 840 tight beam comm suite with SatNav module, the Cyclops can effectively command a brigade across the surface of an entire world. Unfortunately the Cyclops is poorly protected relative to other assault 'Mechs with only ten tons of armor, and while its normal load of twelve heat sinks allows it to stay cool in most cases, they can prove to be inadequate in especially heavy situations. +capabilities:A decent mix of weapons provided the Cyclops with both long- and short-range firepower and a sizable engine to keep up with mobile operations. But the centerpiece of the Cyclops is its sophisticated holographic battle computer, the Tacticon B-2000. When combined with the Olmstead 840 tight beam comm suite with SatNav module, the Cyclops can effectively command a brigade across the surface of an entire world. Unfortunately the Cyclops is poorly protected relative to other assault 'Mechs with only ten tons of armor, and while its normal load of twelve heat sinks allows it to stay cool in most cases, they can prove to be inadequate in especially heavy situations. deployment:Introduced in 3071 this version of the Cyclops carries a second Gauss Rifle, thirteen and a half tons of Ferro-Fibrous armor and CASE. To make room for this equipment, engineers replaced the engine with a 270 rated model. Though this slows the Cyclops by 25%, the increased weaponry and armor protection compensates for the reduced speed. diff --git a/megamek/data/mechfiles/mechs/3085u/ONN/Cyclops CP-11-C2.mtf b/megamek/data/mechfiles/mechs/3085u/ONN/Cyclops CP-11-C2.mtf index e2b8c4be188..57cf5493d91 100644 --- a/megamek/data/mechfiles/mechs/3085u/ONN/Cyclops CP-11-C2.mtf +++ b/megamek/data/mechfiles/mechs/3085u/ONN/Cyclops CP-11-C2.mtf @@ -163,7 +163,7 @@ Foot Actuator overview:The Cyclops began production in 2710 as an assault BattleMech and headquarters unit for Star League Defense Force field commanders. -capabilities:A decent mix of weapons provided the Cyclops with both long- and short-range firepower and a sizable engine to keep up with mobile operations. But the centerpiece of the Cyclops is its sophisticated holographic battle computer, the Tacticon B-2000. When combined with the Omstead Olmstead 840 tight beam comm suite with SatNav module, the Cyclops can effectively command a brigade across the surface of an entire world. Unfortunately the Cyclops is poorly protected relative to other assault 'Mechs with only ten tons of armor, and while its normal load of twelve heat sinks allows it to stay cool in most cases, they can prove to be inadequate in especially heavy situations. +capabilities:A decent mix of weapons provided the Cyclops with both long- and short-range firepower and a sizable engine to keep up with mobile operations. But the centerpiece of the Cyclops is its sophisticated holographic battle computer, the Tacticon B-2000. When combined with the Olmstead 840 tight beam comm suite with SatNav module, the Cyclops can effectively command a brigade across the surface of an entire world. Unfortunately the Cyclops is poorly protected relative to other assault 'Mechs with only ten tons of armor, and while its normal load of twelve heat sinks allows it to stay cool in most cases, they can prove to be inadequate in especially heavy situations. deployment:Based on the 11-C variant and first fielded in 3073, this Cyclops is a company command-level machine that carries a pair of C3 Master Computers. To make room for these massive computers, the Gauss Rifle, its ammunition, and some armor were replaced by a single ER PPC. This leaves the Cyclops slightly undergunned for an assault 'Mech, but it shouldn't be engaging the enemy closely anyway. diff --git a/megamek/data/mechfiles/mechs/3085u/ONN/Cyclops CP-11-C3.mtf b/megamek/data/mechfiles/mechs/3085u/ONN/Cyclops CP-11-C3.mtf index 09f2af2032d..62bce1917df 100644 --- a/megamek/data/mechfiles/mechs/3085u/ONN/Cyclops CP-11-C3.mtf +++ b/megamek/data/mechfiles/mechs/3085u/ONN/Cyclops CP-11-C3.mtf @@ -160,7 +160,7 @@ Heavy Ferro-Fibrous overview:The Cyclops began production in 2710 as an assault BattleMech and headquarters unit for Star League Defense Force field commanders. -capabilities:A decent mix of weapons provided the Cyclops with both long- and short-range firepower and a sizable engine to keep up with mobile operations. But the centerpiece of the Cyclops is its sophisticated holographic battle computer, the Tacticon B-2000. When combined with the Omstead Olmstead 840 tight beam comm suite with SatNav module, the Cyclops can effectively command a brigade across the surface of an entire world. Unfortunately the Cyclops is poorly protected relative to other assault 'Mechs with only ten tons of armor, and while its normal load of twelve heat sinks allows it to stay cool in most cases, they can prove to be inadequate in especially heavy situations. +capabilities:A decent mix of weapons provided the Cyclops with both long- and short-range firepower and a sizable engine to keep up with mobile operations. But the centerpiece of the Cyclops is its sophisticated holographic battle computer, the Tacticon B-2000. When combined with the Olmstead 840 tight beam comm suite with SatNav module, the Cyclops can effectively command a brigade across the surface of an entire world. Unfortunately the Cyclops is poorly protected relative to other assault 'Mechs with only ten tons of armor, and while its normal load of twelve heat sinks allows it to stay cool in most cases, they can prove to be inadequate in especially heavy situations. deployment:This version, introduced in 3077, is based on the 11-C as well but uses an experimental C3 Boosted Master computer to cut through the ECM commonly found on Jihad-era battlefields. It carries a Streak SRM-4, Gauss Rifle, and an ER Medium Laser in each arm. diff --git a/megamek/data/mechfiles/mechs/3085u/ONN/Dragonfly (Viper) U.mtf b/megamek/data/mechfiles/mechs/3085u/ONN/Dragonfly (Viper) U.mtf index 0c99d32317c..8e4cbb3d2b8 100644 --- a/megamek/data/mechfiles/mechs/3085u/ONN/Dragonfly (Viper) U.mtf +++ b/megamek/data/mechfiles/mechs/3085u/ONN/Dragonfly (Viper) U.mtf @@ -156,7 +156,7 @@ Jump Jet overview:The Viper is a fast, highly-maneuverable medium OmniMech originally designed by Clan Fire Mandrill on Shadow. Codenamed the Dragonfly by the Inner Sphere forces that first encountered this small but fierce OmniMech, the name stuck because of its ability to move swiftly over the battlefield. The Viper is fast and well-armored, but significantly under-gunned compared with other Clan OmniMechs massing 35-45 tons (including the Adder, Battle Cobra, Grendel, Shadow Cat, Pouncer, and Cougar). -capabilities:Intended to support boarding operations, this version of the Viper carries additional reaction mass in a Liquid Storage tank. An ECM Suite makes it more difficult to hit while approaching the target vessel. An Anti-Missile System swats down any missiles that come near the Viper U. Two ER Medium Lasers allow it to breach enemy armor from a distance, while the Hatchet in the left arm allows the Viper pilot to smash through armor. The Viper is built on a lightweight Endo Steel chassis and powered by a weight saving 320 XL engine that propels the Viper to a top speed of 129.6 km/h. The Viper augments its impressive ground speed with eight jump jets that allow it to jump up to a distance of two hundred and forty meters. The Viper has seven tons of Ferro-Fibrous armor to absorb any damage from shots that are lucky enough to strike it and has eight and a half tons of podspace for its weapons payload. +capabilities:Intended to support boarding operations, this version of the Viper carries additional reaction mass in a Liquid Storage tank. An ECM Suite makes it more difficult to hit while approaching the target vessel. An Anti-Missile System swats down any missiles that come near the Viper U. Two ER Medium Lasers allow it to breach enemy armor from a distance, while the Hatchet in the left arm allows the Viper pilot to smash through armor. The Viper is built on a lightweight Endo Steel chassis and powered by a weight saving 320 XL engine that propels the Viper to a top speed of 129.6 km/h. The Viper augments its impressive ground speed with eight jump jets that allow it to jump up to a distance of two hundred and forty meters. The Viper has seven tons of Ferro-Fibrous armor to absorb any damage from shots that are lucky enough to strike it and has eight and a half tons of pod space for its weapons payload. history:Clan Ghost Bear came into possession of the design in 3002 when they traded several production runs of Executioner OmniMechs for the design and production facilities on Shadow. Rather than trial for land rights to Shadow, and become embroiled in the internecine struggles of the Fire Mandrills, the Bears restructured the facility, making the lines modular, and relocated production to Strana Mechty - this modular technology proved very useful when the Ghost Bears migrated back to the Inner Sphere in the late 3050s. Surprisingly, the Bears left their first modular production facility on Strana Mechty. Production continued on Strana Mechty for Clan Ghost Bear until the mid-3060s when the Hell's Horses won the production rights and the facility (and then promptly lost the facility to Clan Ice Hellion in 3068). In addition to the manufacturing plant on Strana Mechty, at least one other planet in the Homeworlds was home to a manufacturing line producing Vipers; in 3071 Clan Goliath Scorpion captured a Viper factory from Clan Coyote on Delios, although it is unknown if the planet survived the Wars of Reaving, Goliath Scorpion Abjurement and the subsequent abandonment of the planet by the Coyotes and Cloud Cobras. manufacturer:Upsilon Plant 2J, Dominion Facility Kappa-5 diff --git a/megamek/data/mechfiles/mechs/3085u/ONN/King Crab KGC-005r.mtf b/megamek/data/mechfiles/mechs/3085u/ONN/King Crab KGC-005r.mtf index 57deeafd9c3..e0a75d2d4db 100644 --- a/megamek/data/mechfiles/mechs/3085u/ONN/King Crab KGC-005r.mtf +++ b/megamek/data/mechfiles/mechs/3085u/ONN/King Crab KGC-005r.mtf @@ -161,7 +161,7 @@ manufacturer:Field Refit primaryfactory:Various systemmanufacturer:CHASSIS:Hollis Mark IIe systemmanufacturer:ENGINE:Vlar 300 -systemmanufacturer:ARMOR:Protec Tech 12 +systemmanufacturer:ARMOR:ProtecTech 12 systemmanufacturer:COMMUNICATIONS:Dalban Commline systemmanufacturer:TARGETING:Dalban HiRez-B diff --git a/megamek/data/mechfiles/mechs/3085u/ONN/UrbanMech UM-AIV.mtf b/megamek/data/mechfiles/mechs/3085u/ONN/UrbanMech UM-AIV.mtf index 0522dbaff52..1142e91c704 100644 --- a/megamek/data/mechfiles/mechs/3085u/ONN/UrbanMech UM-AIV.mtf +++ b/megamek/data/mechfiles/mechs/3085u/ONN/UrbanMech UM-AIV.mtf @@ -162,7 +162,7 @@ capabilities:This was achieved by starting with a cheap, easily-produced chassis deployment:This variant of the UrbanMech replaces the standard weaponry with an Arrow IV missile launcher and ER Medium Laser. It requires an Endo Steel chassis and Small Cockpit to provide room, and the UrbanMech can only carry ten rounds for the Arrow system. Despite these limitations, it is still a decent fire support unit. Notably, it can be used to launch nuclear-tipped Arrow IV missiles (see Notes below). -history:Large numbers of UrbanMechs were produced by Orguss Industries from 2675 until the destruction of their assembly lines. The UrbanMech reentered production at the Betelgeuse facility of Hellespont Industrials during the Jihad, and continued to be manufactured up through 3149. As such, UrbanMechs could be found in all of the armies of the Successor States. However most military leaders saw the slow little 'Mech as a liability, confining their stockpiles to garrison duty or stripping them of parts. This dismissive attitude towards the UrbanMech saved it from the ravages of the Succession Wars and ensured its continued use into the thirty-first century. The Capellan Confederation remained the largest and only user of UrbanMechs to actually deploy them for front-line duty, a result of the devastation of the Fourth Succession War and their desperation for any 'Mech to replenish their losses. The Confederation Reserve Cavalry and Capellan Defense Force had the lion's share of UrbanMechs, followed by the Tikonov Republican Guard and St. Ives Armored Cavalry; outside the Confederation the Federated Suns' Capellan March Militia fielded the largest number of UrbanMechs due to the fact it was composed of large amounts of captured Capellan equipment. Its prominence within the Confederation meant the UrbanMech was among those 'Mechs within the CCAF to receive upgrades following the recovery of lostech; the other States followed suit with much less priority over improving other 'Mechs. Despite this the sheer costs necessary to replace the UrbanMech's engine and increase its top speed meant even the Confederation limited their refit packages to improving the weapons and armor only. A testament to the desperation of the Word of Blake Jihad, Hellespont Industrials would reactivate a shuttered production facility on Betelgeuse to produce the UrbanMech alongside primitive "retrotech" designs for material starved Capellan garrison forces. This plant would maintain production of the UrbanMech in a steadily increasing volume of configurations throughout the Dark Age Era as the CCAF secretly expanded before it waged war against the Republic of the Sphere. Rather than dramatic and expensive enhancements, Hellespont's new variants retain the venerable design's low ground speed urban combat focus and can be applied as refits as readily as new production. +history:Large numbers of UrbanMechs were produced by Orgus Industries from 2675 until the destruction of their assembly lines. The UrbanMech reentered production at the Betelgeuse facility of Hellespont Industrials during the Jihad, and continued to be manufactured up through 3149. As such, UrbanMechs could be found in all of the armies of the Successor States. However most military leaders saw the slow little 'Mech as a liability, confining their stockpiles to garrison duty or stripping them of parts. This dismissive attitude towards the UrbanMech saved it from the ravages of the Succession Wars and ensured its continued use into the thirty-first century. The Capellan Confederation remained the largest and only user of UrbanMechs to actually deploy them for front-line duty, a result of the devastation of the Fourth Succession War and their desperation for any 'Mech to replenish their losses. The Confederation Reserve Cavalry and Capellan Defense Force had the lion's share of UrbanMechs, followed by the Tikonov Republican Guard and St. Ives Armored Cavalry; outside the Confederation the Federated Suns' Capellan March Militia fielded the largest number of UrbanMechs due to the fact it was composed of large amounts of captured Capellan equipment. Its prominence within the Confederation meant the UrbanMech was among those 'Mechs within the CCAF to receive upgrades following the recovery of lostech; the other States followed suit with much less priority over improving other 'Mechs. Despite this the sheer costs necessary to replace the UrbanMech's engine and increase its top speed meant even the Confederation limited their refit packages to improving the weapons and armor only. A testament to the desperation of the Word of Blake Jihad, Hellespont Industrials would reactivate a shuttered production facility on Betelgeuse to produce the UrbanMech alongside primitive "retrotech" designs for material starved Capellan garrison forces. This plant would maintain production of the UrbanMech in a steadily increasing volume of configurations throughout the Dark Age Era as the CCAF secretly expanded before it waged war against the Republic of the Sphere. Rather than dramatic and expensive enhancements, Hellespont's new variants retain the venerable design's low ground speed urban combat focus and can be applied as refits as readily as new production. manufacturer:Refit primaryfactory:Various diff --git a/megamek/data/mechfiles/mechs/3085u/ONN/UrbanMech UM-R80.mtf b/megamek/data/mechfiles/mechs/3085u/ONN/UrbanMech UM-R80.mtf index 95597a1c60c..6c9135b4b18 100644 --- a/megamek/data/mechfiles/mechs/3085u/ONN/UrbanMech UM-R80.mtf +++ b/megamek/data/mechfiles/mechs/3085u/ONN/UrbanMech UM-R80.mtf @@ -162,7 +162,7 @@ capabilities:This was achieved by starting with a cheap, easily-produced chassis deployment:This variant carries a Snub-Nose PPC, Small Pulse Laser, TAG, Beagle Active Probe, and Guardian ECM Suite. It retains the Small Laser of the standard UrbanMech as well. Improved Jump Jets help the UrbanMech move around the city it defends more effectively. -history:Large numbers of UrbanMechs were produced by Orguss Industries from 2675 until the destruction of their assembly lines. The UrbanMech reentered production at the Betelgeuse facility of Hellespont Industrials during the Jihad, and continued to be manufactured up through 3149. As such, UrbanMechs could be found in all of the armies of the Successor States. However most military leaders saw the slow little 'Mech as a liability, confining their stockpiles to garrison duty or stripping them of parts. This dismissive attitude towards the UrbanMech saved it from the ravages of the Succession Wars and ensured its continued use into the thirty-first century. The Capellan Confederation remained the largest and only user of UrbanMechs to actually deploy them for front-line duty, a result of the devastation of the Fourth Succession War and their desperation for any 'Mech to replenish their losses. The Confederation Reserve Cavalry and Capellan Defense Force had the lion's share of UrbanMechs, followed by the Tikonov Republican Guard and St. Ives Armored Cavalry; outside the Confederation the Federated Suns' Capellan March Militia fielded the largest number of UrbanMechs due to the fact it was composed of large amounts of captured Capellan equipment. Its prominence within the Confederation meant the UrbanMech was among those 'Mechs within the CCAF to receive upgrades following the recovery of lostech; the other States followed suit with much less priority over improving other 'Mechs. Despite this the sheer costs necessary to replace the UrbanMech's engine and increase its top speed meant even the Confederation limited their refit packages to improving the weapons and armor only. A testament to the desperation of the Word of Blake Jihad, Hellespont Industrials would reactivate a shuttered production facility on Betelgeuse to produce the UrbanMech alongside primitive "retrotech" designs for material starved Capellan garrison forces. This plant would maintain production of the UrbanMech in a steadily increasing volume of configurations throughout the Dark Age Era as the CCAF secretly expanded before it waged war against the Republic of the Sphere. Rather than dramatic and expensive enhancements, Hellespont's new variants retain the venerable design's low ground speed urban combat focus and can be applied as refits as readily as new production. +history:Large numbers of UrbanMechs were produced by Orgus Industries from 2675 until the destruction of their assembly lines. The UrbanMech reentered production at the Betelgeuse facility of Hellespont Industrials during the Jihad, and continued to be manufactured up through 3149. As such, UrbanMechs could be found in all of the armies of the Successor States. However most military leaders saw the slow little 'Mech as a liability, confining their stockpiles to garrison duty or stripping them of parts. This dismissive attitude towards the UrbanMech saved it from the ravages of the Succession Wars and ensured its continued use into the thirty-first century. The Capellan Confederation remained the largest and only user of UrbanMechs to actually deploy them for front-line duty, a result of the devastation of the Fourth Succession War and their desperation for any 'Mech to replenish their losses. The Confederation Reserve Cavalry and Capellan Defense Force had the lion's share of UrbanMechs, followed by the Tikonov Republican Guard and St. Ives Armored Cavalry; outside the Confederation the Federated Suns' Capellan March Militia fielded the largest number of UrbanMechs due to the fact it was composed of large amounts of captured Capellan equipment. Its prominence within the Confederation meant the UrbanMech was among those 'Mechs within the CCAF to receive upgrades following the recovery of lostech; the other States followed suit with much less priority over improving other 'Mechs. Despite this the sheer costs necessary to replace the UrbanMech's engine and increase its top speed meant even the Confederation limited their refit packages to improving the weapons and armor only. A testament to the desperation of the Word of Blake Jihad, Hellespont Industrials would reactivate a shuttered production facility on Betelgeuse to produce the UrbanMech alongside primitive "retrotech" designs for material starved Capellan garrison forces. This plant would maintain production of the UrbanMech in a steadily increasing volume of configurations throughout the Dark Age Era as the CCAF secretly expanded before it waged war against the Republic of the Sphere. Rather than dramatic and expensive enhancements, Hellespont's new variants retain the venerable design's low ground speed urban combat focus and can be applied as refits as readily as new production. manufacturer:Hellespont Industrials primaryfactory:Betelgeuse diff --git a/megamek/data/mechfiles/mechs/3085u/Phoenix/Griffin GRF-5K.mtf b/megamek/data/mechfiles/mechs/3085u/Phoenix/Griffin GRF-5K.mtf index 98090a188b8..990fab013f1 100644 --- a/megamek/data/mechfiles/mechs/3085u/Phoenix/Griffin GRF-5K.mtf +++ b/megamek/data/mechfiles/mechs/3085u/Phoenix/Griffin GRF-5K.mtf @@ -176,4 +176,4 @@ systemmanufacturer:ENGINE:Defiance 275 Light Engine systemmanufacturer:ARMOR:Starshield A Light Ferro-Fibrous armor with CASE systemmanufacturer:JUMPJET:Chilton 950 systemmanufacturer:COMMUNICATIONS:Neil 6000 -systemmanufacturer:TARGETING:RCA Instatrack Mk X +systemmanufacturer:TARGETING:RCA Instatrac Mk X diff --git a/megamek/data/mechfiles/mechs/3085u/Phoenix/Griffin GRF-6CS.mtf b/megamek/data/mechfiles/mechs/3085u/Phoenix/Griffin GRF-6CS.mtf index 986d7e014a0..26fc7f156d9 100644 --- a/megamek/data/mechfiles/mechs/3085u/Phoenix/Griffin GRF-6CS.mtf +++ b/megamek/data/mechfiles/mechs/3085u/Phoenix/Griffin GRF-6CS.mtf @@ -175,5 +175,5 @@ systemmanufacturer:ENGINE:CoreTek 275 XL systemmanufacturer:ARMOR:Starshield A systemmanufacturer:JUMPJET:Rawlings 55 systemmanufacturer:COMMUNICATIONS:Neil 6000 -systemmanufacturer:TARGETING:RCA Instatrack Mk X +systemmanufacturer:TARGETING:RCA Instatrac Mk X diff --git a/megamek/data/mechfiles/mechs/3085u/Phoenix/Griffin GRF-6S.mtf b/megamek/data/mechfiles/mechs/3085u/Phoenix/Griffin GRF-6S.mtf index d53a224b6a3..b04f5ebd76d 100644 --- a/megamek/data/mechfiles/mechs/3085u/Phoenix/Griffin GRF-6S.mtf +++ b/megamek/data/mechfiles/mechs/3085u/Phoenix/Griffin GRF-6S.mtf @@ -164,7 +164,7 @@ overview:Built in 2492 the Griffin was originally classified as a heavy BattleMe capabilities:The massive and efficient fusion engine of the Griffin, giving it a cruising speed of 57.1 km/h, combined with five jump jets occupying the rear torso areas for a total jumping distance of 150 meters, is what distinguishes it from other medium 'Mechs and has kept the Griffin in the game over the centuries. Unfortunately, like most other early 'Mechs, the Griffin suffers from insufficient heat capacity with only twelve heat sinks installed. The result is that Griffin pilots, lacking the ability to do both, must choose at the outset of a fight whether to engage or withdraw. Nine and a half tons of armor plating compares quite favorably to many other medium 'Mechs, although as is often the case the Griffin will find itself in combat with larger 'Mechs. For this reason, two pairs of false armor baffles were added to the 'Mech, one on its shoulders providing limited protection to the LRM launcher and cockpit, and a smaller pair on the legs protecting the knees joints. -deployment:The Lyran 6S Griffin was built in 3066 using an Earthwerks GRF Endo Steel chassis and mounted a Defiance 275 Light Fusion Engine for power. This allowed the 6S model to carry a Defiance 1001 ER PPC in the right arm, a Coventry StarFire LRM-15 over the right shoulder with Artemis IV, and two RAMTech 1500Z ER Medium Lasers, one in the center torso and one in the left arm. It carried twelve tons of Starshield A armor plating using layered sections at steeper angles, which allowed it to withstand more attacks than the 6CS, but only ten double heat sinks. Two tons of LRM reloads were mounted in the right torso and protected by CASE. Although still carrying the five Rawlings 55 jump jets and Neil 6000 communications system of the original model, the targeting-tracking system was updated to a RCA Instatrack Mk X and, perhaps most importantly, the cockpit was renovated for additional comfort and incorporate a Full-Head Ejection System. +deployment:The Lyran 6S Griffin was built in 3066 using an Earthwerks GRF Endo Steel chassis and mounted a Defiance 275 Light Fusion Engine for power. This allowed the 6S model to carry a Defiance 1001 ER PPC in the right arm, a Coventry StarFire LRM-15 over the right shoulder with Artemis IV, and two RAMTech 1500Z ER Medium Lasers, one in the center torso and one in the left arm. It carried twelve tons of Starshield A armor plating using layered sections at steeper angles, which allowed it to withstand more attacks than the 6CS, but only ten double heat sinks. Two tons of LRM reloads were mounted in the right torso and protected by CASE. Although still carrying the five Rawlings 55 jump jets and Neil 6000 communications system of the original model, the targeting-tracking system was updated to a RCA Instatrac Mk X and, perhaps most importantly, the cockpit was renovated for additional comfort and incorporate a Full-Head Ejection System. history:Combining tremendous speed and firepower in one frame the Griffin briefly dominated in this role before being superseded by larger and better-equipped 'Mechs. However the Griffin was very popular among commanders and pilots alike and so Earthwerks Incorporated kept it in production, this time reclassified as a medium 'Mech and tasked with long-range fire support for medium lances. In this capacity the Griffin has excelled, combining good striking power, endurance and speed, with its only major weakness being a lack of close-range defensive weapons. During the Succession Wars the Griffin could be found in almost every unit of all the Great Houses, thanks in part to its diverse number of manufacturers. Besides being constructed from Earthwerks' factory on Keystone the Griffin was later acquired and built by Defiance Industries (Hesperus II), Kallon Industries (Talon), Brigadier Corporation (Oliver), and Norse BattleMech Works (later Victory Industries, Marduk). It was even manufactured in the Periphery by Vandenberg Mechanized Industries on Illiushin. Only the Capellan Confederation lacked a means of building the 'Mech, although they made up for it by purchasing a limited number from the Taurian Concordat. During the Fourth Succession War some of these manufacturers exchanged hands, with the Draconis Combine capturing Marduk from the Federated Suns and the Lyran Commonwealth taking Oliver from the Free Worlds League. This exchange also happened to coincide with several new variants being designed to exploit recently-recovered lostech. As such variants meant specifically for either Houses Kurita, Marik or the Federated Commonwealth found their way into the arsenals of all of them. During the Clan Invasion these manufacturers produced the new variants to meet the Clan threat while Vandenberg Industries continued to build original GRF-1N Griffins. When Vicore Industries began shopping around its "Project Phoenix" initiative, Defiance and Kallon Industries signed on to begin producing the completely redesigned GRF-6S Griffin. Victory Industries later signed up as well after the legal battle between Wolf's Dragoons and the Lyran Alliance saw the famous mercenary group selling its Light Fusion technology to both the Draconis Combine and Free Worlds League. The League designed a native update to the Griffin while ComStar had their own built as well which, ominously, soon began appearing in the ranks of the Word of Blake Militia. The Griffin would continue to remain a staple of the battlefields of the Inner Sphere during the maelstrom of the Jihad, the era of the Republic of the Sphere and the rise of the ilClan, with models still in production within the Free Worlds League and the Wolf Empire. @@ -175,4 +175,4 @@ systemmanufacturer:ENGINE:Defiance 275 Light Engine systemmanufacturer:ARMOR:Starshield A Light Ferro-Fibrous armor with CASE systemmanufacturer:JUMPJET:Chilton 950 systemmanufacturer:COMMUNICATIONS:Neil 6000 -systemmanufacturer:TARGETING:RCA Instatrack Mk X +systemmanufacturer:TARGETING:RCA Instatrac Mk X diff --git a/megamek/data/mechfiles/mechs/3085u/Phoenix/Ostroc OSR-4C.mtf b/megamek/data/mechfiles/mechs/3085u/Phoenix/Ostroc OSR-4C.mtf index 5a52e4d5acb..c06ed435e00 100644 --- a/megamek/data/mechfiles/mechs/3085u/Phoenix/Ostroc OSR-4C.mtf +++ b/megamek/data/mechfiles/mechs/3085u/Phoenix/Ostroc OSR-4C.mtf @@ -164,7 +164,7 @@ capabilities:Its unique walker/pod profile, later seen in the Stalker and Maraud deployment:A Periphery variant of the Ostroc produced by Vandenberg Mechanized on New Vandenberg, the 4C is strikingly similar to the Capellan's 4L variant. It's armor has been upgraded with nine tons of Ferro-Fibrous armor, giving it more protection than previous models. Additionally, the SRM-4 launcher has been removed in favor of two Rocket Launcher 10s and two Rocket Launcher 15s, giving the 'Mech an incredible one-shot damage capability. -history:The best-known of Ostman Industries' Ost Class of 'Mechs, the Ostroc debuted in 2511 and proved so successful in this role production continued for approximately 200 years. While a quality 'Mech, the low production capacity of Ostman Industries made the Ostroc a rarity; indeed the company licensed their other Ost 'Mechs out to Kong Interstellar just to maintain their rate of production, and the majority of those produced were assigned garrison duties within the Terran Hegemony. Still, the 'Mech saw action in every major conflict of the Star League, especially towards the end in the civil war and subsequent First Succession War. The destruction of Ostman Industries meant an end to any new Ostrocs, although all sides of the Succession Wars continued to field these 'Mechs in combat, particularly the Draconis Combine. It was because of the small number and wide dispersal of surviving Ostrocs that the design was largely passed over while others were being updated after the Helm Memory Core discovery. A major revitalization of the design took place within the Capellan Confederation after the Clan Invasion. Having largely rebuilt their forces after the previous decades' setbacks, the Strategios wanted to update the ancient 'Mech, but rather than reverse-engineering the original they ordered all Capellan 'Mech manufacturers to submit bids for a replacement. Ceres Metals was the only one to send in a proposal which matched exactly what they wanted and won the contract, completing the first production run in January 3067. Versions of these new Ostrocs also started showing up in the Taurian Concordat and Circinus Federation, a result of espionage according to Capellan charges. +history:The best-known of Ostmann Industries' Ost Class of 'Mechs, the Ostroc debuted in 2511 and proved so successful in this role production continued for approximately 200 years. While a quality 'Mech, the low production capacity of Ostmann Industries made the Ostroc a rarity; indeed the company licensed their other Ost 'Mechs out to Kong Interstellar just to maintain their rate of production, and the majority of those produced were assigned garrison duties within the Terran Hegemony. Still, the 'Mech saw action in every major conflict of the Star League, especially towards the end in the civil war and subsequent First Succession War. The destruction of Ostmann Industries meant an end to any new Ostrocs, although all sides of the Succession Wars continued to field these 'Mechs in combat, particularly the Draconis Combine. It was because of the small number and wide dispersal of surviving Ostrocs that the design was largely passed over while others were being updated after the Helm Memory Core discovery. A major revitalization of the design took place within the Capellan Confederation after the Clan Invasion. Having largely rebuilt their forces after the previous decades' setbacks, the Strategios wanted to update the ancient 'Mech, but rather than reverse-engineering the original they ordered all Capellan 'Mech manufacturers to submit bids for a replacement. Ceres Metals was the only one to send in a proposal which matched exactly what they wanted and won the contract, completing the first production run in January 3067. Versions of these new Ostrocs also started showing up in the Taurian Concordat and Circinus Federation, a result of espionage according to Capellan charges. manufacturer:Gift of the Magi, Inc,Vandenberg Mechanized Industries primaryfactory:Baltazar III,New Vandenberg diff --git a/megamek/data/mechfiles/mechs/3085u/Phoenix/Ostroc OSR-4K.mtf b/megamek/data/mechfiles/mechs/3085u/Phoenix/Ostroc OSR-4K.mtf index 6db57a9e4ba..9b25d6ac5f4 100644 --- a/megamek/data/mechfiles/mechs/3085u/Phoenix/Ostroc OSR-4K.mtf +++ b/megamek/data/mechfiles/mechs/3085u/Phoenix/Ostroc OSR-4K.mtf @@ -162,9 +162,9 @@ capabilities:Its unique walker/pod profile, later seen in the Stalker and Maraud deployment:This version was introduced by House Kurita in 3077. A Heavy Duty Gyro allows it to stay in the fight longer, making good use of twin Snub-Nose PPCs and ER Medium Lasers. Though it's slightly slower than the standard Ostroc, jump jets allow it to maneuver around the battlefield, striking where it will inflict the most damage. After the Jihad ended, this model went into factory production. -history:The best-known of Ostman Industries' Ost Class of 'Mechs, the Ostroc debuted in 2511 and proved so successful in this role production continued for approximately 200 years. While a quality 'Mech, the low production capacity of Ostman Industries made the Ostroc a rarity; indeed the company licensed their other Ost 'Mechs out to Kong Interstellar just to maintain their rate of production, and the majority of those produced were assigned garrison duties within the Terran Hegemony. Still, the 'Mech saw action in every major conflict of the Star League, especially towards the end in the civil war and subsequent First Succession War. The destruction of Ostman Industries meant an end to any new Ostrocs, although all sides of the Succession Wars continued to field these 'Mechs in combat, particularly the Draconis Combine. It was because of the small number and wide dispersal of surviving Ostrocs that the design was largely passed over while others were being updated after the Helm Memory Core discovery. A major revitalization of the design took place within the Capellan Confederation after the Clan Invasion. Having largely rebuilt their forces after the previous decades' setbacks, the Strategios wanted to update the ancient 'Mech, but rather than reverse-engineering the original they ordered all Capellan 'Mech manufacturers to submit bids for a replacement. Ceres Metals was the only one to send in a proposal which matched exactly what they wanted and won the contract, completing the first production run in January 3067. Versions of these new Ostrocs also started showing up in the Taurian Concordat and Circinus Federation, a result of espionage according to Capellan charges. +history:The best-known of Ostmann Industries' Ost Class of 'Mechs, the Ostroc debuted in 2511 and proved so successful in this role production continued for approximately 200 years. While a quality 'Mech, the low production capacity of Ostmann Industries made the Ostroc a rarity; indeed the company licensed their other Ost 'Mechs out to Kong Interstellar just to maintain their rate of production, and the majority of those produced were assigned garrison duties within the Terran Hegemony. Still, the 'Mech saw action in every major conflict of the Star League, especially towards the end in the civil war and subsequent First Succession War. The destruction of Ostmann Industries meant an end to any new Ostrocs, although all sides of the Succession Wars continued to field these 'Mechs in combat, particularly the Draconis Combine. It was because of the small number and wide dispersal of surviving Ostrocs that the design was largely passed over while others were being updated after the Helm Memory Core discovery. A major revitalization of the design took place within the Capellan Confederation after the Clan Invasion. Having largely rebuilt their forces after the previous decades' setbacks, the Strategios wanted to update the ancient 'Mech, but rather than reverse-engineering the original they ordered all Capellan 'Mech manufacturers to submit bids for a replacement. Ceres Metals was the only one to send in a proposal which matched exactly what they wanted and won the contract, completing the first production run in January 3067. Versions of these new Ostrocs also started showing up in the Taurian Concordat and Circinus Federation, a result of espionage according to Capellan charges. -manufacturer:Kressly Warworks,Luthien Armor Works +manufacturer:Kressly WarWorks,Luthien Armor Works primaryfactory:Epsilon Eridani,Nykvarn systemmanufacturer:CHASSIS:Ceresplex Ostroc Lite Endo Steel systemmanufacturer:ENGINE:Pitban 240 diff --git a/megamek/data/mechfiles/mechs/3085u/Phoenix/Ostroc OSR-4L.mtf b/megamek/data/mechfiles/mechs/3085u/Phoenix/Ostroc OSR-4L.mtf index 6c43dc08e59..97708274555 100644 --- a/megamek/data/mechfiles/mechs/3085u/Phoenix/Ostroc OSR-4L.mtf +++ b/megamek/data/mechfiles/mechs/3085u/Phoenix/Ostroc OSR-4L.mtf @@ -160,7 +160,7 @@ capabilities:Its unique walker/pod profile, later seen in the Stalker and Maraud deployment:A complete redesign of the Ostroc, the 4L carries the best technology the Capellan Confederation has to offer in 3067. It uses an Ceresplex Ostroc Light Endo Steel chassis to carry two Martell ER Large Lasers and two Ceres Arms ER Medium Lasers split between the side torsos. Five HildCo 13 jump jets split between the side and center torsos gives it a jumping distance of 180 meters. Finally, the 4L Ostroc has a Guardian ECM Suite for electronics warfare use and also to work with ten and a half tons of Stealth Armor which makes it extremely difficult to hit. While it was originally suppose to use only standard armor, the addition of stealth capabilities makes this variant well suited for operating as a member of Capellan Shadow Lances. For electronics the Ostroc carries the Ceres Metals Model 686 and Ceres Bullseye systems. -history:The best-known of Ostman Industries' Ost Class of 'Mechs, the Ostroc debuted in 2511 and proved so successful in this role production continued for approximately 200 years. While a quality 'Mech, the low production capacity of Ostman Industries made the Ostroc a rarity; indeed the company licensed their other Ost 'Mechs out to Kong Interstellar just to maintain their rate of production, and the majority of those produced were assigned garrison duties within the Terran Hegemony. Still, the 'Mech saw action in every major conflict of the Star League, especially towards the end in the civil war and subsequent First Succession War. The destruction of Ostman Industries meant an end to any new Ostrocs, although all sides of the Succession Wars continued to field these 'Mechs in combat, particularly the Draconis Combine. It was because of the small number and wide dispersal of surviving Ostrocs that the design was largely passed over while others were being updated after the Helm Memory Core discovery. A major revitalization of the design took place within the Capellan Confederation after the Clan Invasion. Having largely rebuilt their forces after the previous decades' setbacks, the Strategios wanted to update the ancient 'Mech, but rather than reverse-engineering the original they ordered all Capellan 'Mech manufacturers to submit bids for a replacement. Ceres Metals was the only one to send in a proposal which matched exactly what they wanted and won the contract, completing the first production run in January 3067. Versions of these new Ostrocs also started showing up in the Taurian Concordat and Circinus Federation, a result of espionage according to Capellan charges. +history:The best-known of Ostmann Industries' Ost Class of 'Mechs, the Ostroc debuted in 2511 and proved so successful in this role production continued for approximately 200 years. While a quality 'Mech, the low production capacity of Ostmann Industries made the Ostroc a rarity; indeed the company licensed their other Ost 'Mechs out to Kong Interstellar just to maintain their rate of production, and the majority of those produced were assigned garrison duties within the Terran Hegemony. Still, the 'Mech saw action in every major conflict of the Star League, especially towards the end in the civil war and subsequent First Succession War. The destruction of Ostmann Industries meant an end to any new Ostrocs, although all sides of the Succession Wars continued to field these 'Mechs in combat, particularly the Draconis Combine. It was because of the small number and wide dispersal of surviving Ostrocs that the design was largely passed over while others were being updated after the Helm Memory Core discovery. A major revitalization of the design took place within the Capellan Confederation after the Clan Invasion. Having largely rebuilt their forces after the previous decades' setbacks, the Strategios wanted to update the ancient 'Mech, but rather than reverse-engineering the original they ordered all Capellan 'Mech manufacturers to submit bids for a replacement. Ceres Metals was the only one to send in a proposal which matched exactly what they wanted and won the contract, completing the first production run in January 3067. Versions of these new Ostrocs also started showing up in the Taurian Concordat and Circinus Federation, a result of espionage according to Capellan charges. manufacturer:Ceres Metals Industries,Detroit Consolidated Mechworks,Ceres Metals Industries primaryfactory:Capella,Detroit,Warlock diff --git a/megamek/data/mechfiles/mechs/3085u/Phoenix/Ostroc OSR-5C.mtf b/megamek/data/mechfiles/mechs/3085u/Phoenix/Ostroc OSR-5C.mtf index deefde4b224..3f83ecb9976 100644 --- a/megamek/data/mechfiles/mechs/3085u/Phoenix/Ostroc OSR-5C.mtf +++ b/megamek/data/mechfiles/mechs/3085u/Phoenix/Ostroc OSR-5C.mtf @@ -160,7 +160,7 @@ capabilities:Its unique walker/pod profile, later seen in the Stalker and Maraud deployment:Based on the 4C, this Taurian version introduced in 3082 uses an XL Engine, Endo Steel chassis, and five jump jets. The armament has been replaced with a Heavy PPC and Light PPC. -history:The best-known of Ostman Industries' Ost Class of 'Mechs, the Ostroc debuted in 2511 and proved so successful in this role production continued for approximately 200 years. While a quality 'Mech, the low production capacity of Ostman Industries made the Ostroc a rarity; indeed the company licensed their other Ost 'Mechs out to Kong Interstellar just to maintain their rate of production, and the majority of those produced were assigned garrison duties within the Terran Hegemony. Still, the 'Mech saw action in every major conflict of the Star League, especially towards the end in the civil war and subsequent First Succession War. The destruction of Ostman Industries meant an end to any new Ostrocs, although all sides of the Succession Wars continued to field these 'Mechs in combat, particularly the Draconis Combine. It was because of the small number and wide dispersal of surviving Ostrocs that the design was largely passed over while others were being updated after the Helm Memory Core discovery. A major revitalization of the design took place within the Capellan Confederation after the Clan Invasion. Having largely rebuilt their forces after the previous decades' setbacks, the Strategios wanted to update the ancient 'Mech, but rather than reverse-engineering the original they ordered all Capellan 'Mech manufacturers to submit bids for a replacement. Ceres Metals was the only one to send in a proposal which matched exactly what they wanted and won the contract, completing the first production run in January 3067. Versions of these new Ostrocs also started showing up in the Taurian Concordat and Circinus Federation, a result of espionage according to Capellan charges. +history:The best-known of Ostmann Industries' Ost Class of 'Mechs, the Ostroc debuted in 2511 and proved so successful in this role production continued for approximately 200 years. While a quality 'Mech, the low production capacity of Ostmann Industries made the Ostroc a rarity; indeed the company licensed their other Ost 'Mechs out to Kong Interstellar just to maintain their rate of production, and the majority of those produced were assigned garrison duties within the Terran Hegemony. Still, the 'Mech saw action in every major conflict of the Star League, especially towards the end in the civil war and subsequent First Succession War. The destruction of Ostmann Industries meant an end to any new Ostrocs, although all sides of the Succession Wars continued to field these 'Mechs in combat, particularly the Draconis Combine. It was because of the small number and wide dispersal of surviving Ostrocs that the design was largely passed over while others were being updated after the Helm Memory Core discovery. A major revitalization of the design took place within the Capellan Confederation after the Clan Invasion. Having largely rebuilt their forces after the previous decades' setbacks, the Strategios wanted to update the ancient 'Mech, but rather than reverse-engineering the original they ordered all Capellan 'Mech manufacturers to submit bids for a replacement. Ceres Metals was the only one to send in a proposal which matched exactly what they wanted and won the contract, completing the first production run in January 3067. Versions of these new Ostrocs also started showing up in the Taurian Concordat and Circinus Federation, a result of espionage according to Capellan charges. manufacturer:Vandenberg Mechanized Industries primaryfactory:New Vandenberg diff --git a/megamek/data/mechfiles/mechs/3085u/Phoenix/Ostroc OSR-5W.mtf b/megamek/data/mechfiles/mechs/3085u/Phoenix/Ostroc OSR-5W.mtf index 52906a21887..f89e800d6f1 100644 --- a/megamek/data/mechfiles/mechs/3085u/Phoenix/Ostroc OSR-5W.mtf +++ b/megamek/data/mechfiles/mechs/3085u/Phoenix/Ostroc OSR-5W.mtf @@ -160,11 +160,11 @@ overview:The Ostroc is a heavy 'Mech, weighing in at the lower end of its weight capabilities:Its unique walker/pod profile, later seen in the Stalker and Marauder, combined with a low silhouette similar to the UrbanMech makes the Ostroc difficult to spot in an urban environment. Fast for its size, well-armored and boasting good medium- and short-range firepower, the Ostroc was also capable when fighting outside a cityscape, particularly as a heavy scout/raider. -deployment:An upgrade of the 4L, the 5W was produced by Kressly Warworks for the Word of Blake starting in 3070. It uses Kallon Unity Weave Ferro-Fibrous armor, a Defiance Light Engine, and a Small Cockpit to save weight. It uses a Compact Gyro to save space. The ER Large Lasers are replaced with Ceres Arms Thrasher Snub-Nose PPCs, while the ER Medium Lasers are essentially the same, but Diverse Optics models instead. Instead of the ECM, the 5W carries an Improved C3 Computer in the head. +deployment:An upgrade of the 4L, the 5W was produced by Kressly WarWorks for the Word of Blake starting in 3070. It uses Kallon Unity Weave Ferro-Fibrous armor, a Defiance Light Engine, and a Small Cockpit to save weight. It uses a Compact Gyro to save space. The ER Large Lasers are replaced with Ceres Arms Thrasher Snub-Nose PPCs, while the ER Medium Lasers are essentially the same, but Diverse Optics models instead. Instead of the ECM, the 5W carries an Improved C3 Computer in the head. -history:The best-known of Ostman Industries' Ost Class of 'Mechs, the Ostroc debuted in 2511 and proved so successful in this role production continued for approximately 200 years. While a quality 'Mech, the low production capacity of Ostman Industries made the Ostroc a rarity; indeed the company licensed their other Ost 'Mechs out to Kong Interstellar just to maintain their rate of production, and the majority of those produced were assigned garrison duties within the Terran Hegemony. Still, the 'Mech saw action in every major conflict of the Star League, especially towards the end in the civil war and subsequent First Succession War. The destruction of Ostman Industries meant an end to any new Ostrocs, although all sides of the Succession Wars continued to field these 'Mechs in combat, particularly the Draconis Combine. It was because of the small number and wide dispersal of surviving Ostrocs that the design was largely passed over while others were being updated after the Helm Memory Core discovery. A major revitalization of the design took place within the Capellan Confederation after the Clan Invasion. Having largely rebuilt their forces after the previous decades' setbacks, the Strategios wanted to update the ancient 'Mech, but rather than reverse-engineering the original they ordered all Capellan 'Mech manufacturers to submit bids for a replacement. Ceres Metals was the only one to send in a proposal which matched exactly what they wanted and won the contract, completing the first production run in January 3067. Versions of these new Ostrocs also started showing up in the Taurian Concordat and Circinus Federation, a result of espionage according to Capellan charges. +history:The best-known of Ostmann Industries' Ost Class of 'Mechs, the Ostroc debuted in 2511 and proved so successful in this role production continued for approximately 200 years. While a quality 'Mech, the low production capacity of Ostmann Industries made the Ostroc a rarity; indeed the company licensed their other Ost 'Mechs out to Kong Interstellar just to maintain their rate of production, and the majority of those produced were assigned garrison duties within the Terran Hegemony. Still, the 'Mech saw action in every major conflict of the Star League, especially towards the end in the civil war and subsequent First Succession War. The destruction of Ostmann Industries meant an end to any new Ostrocs, although all sides of the Succession Wars continued to field these 'Mechs in combat, particularly the Draconis Combine. It was because of the small number and wide dispersal of surviving Ostrocs that the design was largely passed over while others were being updated after the Helm Memory Core discovery. A major revitalization of the design took place within the Capellan Confederation after the Clan Invasion. Having largely rebuilt their forces after the previous decades' setbacks, the Strategios wanted to update the ancient 'Mech, but rather than reverse-engineering the original they ordered all Capellan 'Mech manufacturers to submit bids for a replacement. Ceres Metals was the only one to send in a proposal which matched exactly what they wanted and won the contract, completing the first production run in January 3067. Versions of these new Ostrocs also started showing up in the Taurian Concordat and Circinus Federation, a result of espionage according to Capellan charges. -manufacturer:Kressly Warworks +manufacturer:Kressly WarWorks primaryfactory:Epsilon Eridani systemmanufacturer:CHASSIS:Ost-III Ostroc Endo Steel systemmanufacturer:ENGINE:Defiance 300 Light Fusion diff --git a/megamek/data/mechfiles/mechs/3085u/Phoenix/Phoenix Hawk IIC 3.mtf b/megamek/data/mechfiles/mechs/3085u/Phoenix/Phoenix Hawk IIC 3.mtf index 534cab1c6d0..441c9f07ea4 100644 --- a/megamek/data/mechfiles/mechs/3085u/Phoenix/Phoenix Hawk IIC 3.mtf +++ b/megamek/data/mechfiles/mechs/3085u/Phoenix/Phoenix Hawk IIC 3.mtf @@ -162,5 +162,5 @@ systemmanufacturer:ENGINE:Type 70 400 XL Fusion systemmanufacturer:ARMOR:Forging AM15 Ferro-Fibrous with CASE systemmanufacturer:JUMPJET:Grandthrust Mk. 5 systemmanufacturer:COMMUNICATIONS:MegaBand System 21 -systemmanufacturer:TARGETING:Dtrac Suit 4 +systemmanufacturer:TARGETING:Dtrac Suite 4 diff --git a/megamek/data/mechfiles/mechs/3085u/Phoenix/Phoenix Hawk IIC 4.mtf b/megamek/data/mechfiles/mechs/3085u/Phoenix/Phoenix Hawk IIC 4.mtf index 9b216512e28..912e0a7f0c5 100644 --- a/megamek/data/mechfiles/mechs/3085u/Phoenix/Phoenix Hawk IIC 4.mtf +++ b/megamek/data/mechfiles/mechs/3085u/Phoenix/Phoenix Hawk IIC 4.mtf @@ -165,5 +165,5 @@ systemmanufacturer:ENGINE:Type 70 400 XL Fusion systemmanufacturer:ARMOR:Forging AM15 Ferro-Fibrous with CASE systemmanufacturer:JUMPJET:Grandthrust Mk. 5 systemmanufacturer:COMMUNICATIONS:MegaBand System 21 -systemmanufacturer:TARGETING:Dtrac Suit 4 +systemmanufacturer:TARGETING:Dtrac Suite 4 diff --git a/megamek/data/mechfiles/mechs/3085u/Phoenix/Phoenix Hawk IIC 5.mtf b/megamek/data/mechfiles/mechs/3085u/Phoenix/Phoenix Hawk IIC 5.mtf index 5671d542666..78f7ae1b6e7 100644 --- a/megamek/data/mechfiles/mechs/3085u/Phoenix/Phoenix Hawk IIC 5.mtf +++ b/megamek/data/mechfiles/mechs/3085u/Phoenix/Phoenix Hawk IIC 5.mtf @@ -165,5 +165,5 @@ systemmanufacturer:ENGINE:Type 70 400 XL Fusion systemmanufacturer:ARMOR:Forging AM15 Ferro-Fibrous with CASE systemmanufacturer:JUMPJET:Grandthrust Mk. 5 systemmanufacturer:COMMUNICATIONS:MegaBand System 21 -systemmanufacturer:TARGETING:Dtrac Suit 4 +systemmanufacturer:TARGETING:Dtrac Suite 4 diff --git a/megamek/data/mechfiles/mechs/3085u/Phoenix/Phoenix Hawk IIC 6.mtf b/megamek/data/mechfiles/mechs/3085u/Phoenix/Phoenix Hawk IIC 6.mtf index 0409e3480b8..b514e79df41 100644 --- a/megamek/data/mechfiles/mechs/3085u/Phoenix/Phoenix Hawk IIC 6.mtf +++ b/megamek/data/mechfiles/mechs/3085u/Phoenix/Phoenix Hawk IIC 6.mtf @@ -161,5 +161,5 @@ systemmanufacturer:ENGINE:Type 70 400 XL Fusion systemmanufacturer:ARMOR:Forging AM15 Ferro-Fibrous with CASE systemmanufacturer:JUMPJET:Grandthrust Mk. 5 systemmanufacturer:COMMUNICATIONS:MegaBand System 21 -systemmanufacturer:TARGETING:Dtrac Suit 4 +systemmanufacturer:TARGETING:Dtrac Suite 4 diff --git a/megamek/data/mechfiles/mechs/3085u/Phoenix/Phoenix Hawk IIC 7.mtf b/megamek/data/mechfiles/mechs/3085u/Phoenix/Phoenix Hawk IIC 7.mtf index afb04be10b5..061ec5f0b6e 100644 --- a/megamek/data/mechfiles/mechs/3085u/Phoenix/Phoenix Hawk IIC 7.mtf +++ b/megamek/data/mechfiles/mechs/3085u/Phoenix/Phoenix Hawk IIC 7.mtf @@ -167,5 +167,5 @@ systemmanufacturer:ENGINE:Type 70 400 XL Fusion systemmanufacturer:ARMOR:Forging AM15 Ferro-Fibrous with CASE systemmanufacturer:JUMPJET:Grandthrust Mk. 5 systemmanufacturer:COMMUNICATIONS:MegaBand System 21 -systemmanufacturer:TARGETING:Dtrac Suit 4 +systemmanufacturer:TARGETING:Dtrac Suite 4 diff --git a/megamek/data/mechfiles/mechs/3085u/Phoenix/Phoenix Hawk IIC 8.mtf b/megamek/data/mechfiles/mechs/3085u/Phoenix/Phoenix Hawk IIC 8.mtf index 0585e7ba58d..680247b6811 100644 --- a/megamek/data/mechfiles/mechs/3085u/Phoenix/Phoenix Hawk IIC 8.mtf +++ b/megamek/data/mechfiles/mechs/3085u/Phoenix/Phoenix Hawk IIC 8.mtf @@ -163,5 +163,5 @@ systemmanufacturer:ENGINE:Type 70 400 XL Fusion systemmanufacturer:ARMOR:Forging AM15 Ferro-Fibrous with CASE systemmanufacturer:JUMPJET:Grandthrust Mk. 5 systemmanufacturer:COMMUNICATIONS:MegaBand System 21 -systemmanufacturer:TARGETING:Dtrac Suit 4 +systemmanufacturer:TARGETING:Dtrac Suite 4 diff --git a/megamek/data/mechfiles/mechs/3085u/Phoenix/Wasp WSP-3A.mtf b/megamek/data/mechfiles/mechs/3085u/Phoenix/Wasp WSP-3A.mtf index 3e0218a09e4..c4f6393b2cb 100644 --- a/megamek/data/mechfiles/mechs/3085u/Phoenix/Wasp WSP-3A.mtf +++ b/megamek/data/mechfiles/mechs/3085u/Phoenix/Wasp WSP-3A.mtf @@ -171,5 +171,5 @@ systemmanufacturer:CHASSIS:1A Type 3 systemmanufacturer:ENGINE:Hermes 100 XL systemmanufacturer:ARMOR:Durallex Light systemmanufacturer:JUMPJET:Unknown -systemmanufacturer:COMMUNICATIONS:Duotech 65 +systemmanufacturer:COMMUNICATIONS:Duoteck 65 systemmanufacturer:TARGETING:RadCom TXX diff --git a/megamek/data/mechfiles/mechs/3085u/Phoenix/Wasp WSP-3S.mtf b/megamek/data/mechfiles/mechs/3085u/Phoenix/Wasp WSP-3S.mtf index a659b53c190..6f010a5f2c4 100644 --- a/megamek/data/mechfiles/mechs/3085u/Phoenix/Wasp WSP-3S.mtf +++ b/megamek/data/mechfiles/mechs/3085u/Phoenix/Wasp WSP-3S.mtf @@ -172,5 +172,5 @@ systemmanufacturer:CHASSIS:Irian Second Generation Class 20 Endo Steel systemmanufacturer:ENGINE:Hermes 120 Light systemmanufacturer:ARMOR:Durallex Light systemmanufacturer:JUMPJET:Rawlings 52 -systemmanufacturer:COMMUNICATIONS:Duotech 65 +systemmanufacturer:COMMUNICATIONS:Duoteck 65 systemmanufacturer:TARGETING:RadCom TXX diff --git a/megamek/data/mechfiles/mechs/3085u/Phoenix/Wasp WSP-7MAF.mtf b/megamek/data/mechfiles/mechs/3085u/Phoenix/Wasp WSP-7MAF.mtf index 6cd0bc0f6ae..2512cd9bf43 100644 --- a/megamek/data/mechfiles/mechs/3085u/Phoenix/Wasp WSP-7MAF.mtf +++ b/megamek/data/mechfiles/mechs/3085u/Phoenix/Wasp WSP-7MAF.mtf @@ -163,5 +163,5 @@ systemmanufacturer:CHASSIS:Hellespont Type W Endo Steel systemmanufacturer:ENGINE:Hermes 160 XL systemmanufacturer:ARMOR:Jolassa-328 Ferro-Fibrous systemmanufacturer:JUMPJET:Rawlings 52 -systemmanufacturer:COMMUNICATIONS:Duotech 65 +systemmanufacturer:COMMUNICATIONS:Duoteck 65 systemmanufacturer:TARGETING:RadCom TXX diff --git a/megamek/data/mechfiles/mechs/3085u/Phoenix/Wasp WSP-8T.mtf b/megamek/data/mechfiles/mechs/3085u/Phoenix/Wasp WSP-8T.mtf index b55ce27ea4a..914c834320a 100644 --- a/megamek/data/mechfiles/mechs/3085u/Phoenix/Wasp WSP-8T.mtf +++ b/megamek/data/mechfiles/mechs/3085u/Phoenix/Wasp WSP-8T.mtf @@ -171,5 +171,5 @@ systemmanufacturer:CHASSIS:Hellespont Type W Endo Steel systemmanufacturer:ENGINE:Hermes 120 XL systemmanufacturer:ARMOR:Durallex Light systemmanufacturer:JUMPJET:Rawlings 52 -systemmanufacturer:COMMUNICATIONS:Duotech 65 +systemmanufacturer:COMMUNICATIONS:Duoteck 65 systemmanufacturer:TARGETING:RadCom TXX diff --git a/megamek/data/mechfiles/mechs/3145/Davion/Atlas III AS7-D2.mtf b/megamek/data/mechfiles/mechs/3145/Davion/Atlas III AS7-D2.mtf index 0bc45373311..12f9d26d4c1 100644 --- a/megamek/data/mechfiles/mechs/3145/Davion/Atlas III AS7-D2.mtf +++ b/megamek/data/mechfiles/mechs/3145/Davion/Atlas III AS7-D2.mtf @@ -172,6 +172,6 @@ primaryfactory:El Dorado,Robinson systemmanufacturer:CHASSIS:Foundation 12X Endo Steel systemmanufacturer:ENGINE:Vlar 300 systemmanufacturer:ARMOR:Starshield Special Heavy with CASE II -systemmanufacturer:COMMUNICATIONS:Rander Comm- Marshal with Angel ECM Suite +systemmanufacturer:COMMUNICATIONS:Rander Comm-Marshal with Angel ECM Suite systemmanufacturer:TARGETING:Dalban HiRez V diff --git a/megamek/data/mechfiles/mechs/3145/Davion/Atlas III AS7-D3.mtf b/megamek/data/mechfiles/mechs/3145/Davion/Atlas III AS7-D3.mtf index dbb5df1014d..98aa278e31a 100644 --- a/megamek/data/mechfiles/mechs/3145/Davion/Atlas III AS7-D3.mtf +++ b/megamek/data/mechfiles/mechs/3145/Davion/Atlas III AS7-D3.mtf @@ -170,6 +170,6 @@ primaryfactory:El Dorado,Robinson systemmanufacturer:CHASSIS:Foundation 12X Endo Steel systemmanufacturer:ENGINE:Vlar 300 systemmanufacturer:ARMOR:Starshield Special Heavy with CASE II -systemmanufacturer:COMMUNICATIONS:Rander Comm- Marshal with Angel ECM Suite +systemmanufacturer:COMMUNICATIONS:Rander Comm-Marshal with Angel ECM Suite systemmanufacturer:TARGETING:Dalban HiRez V diff --git a/megamek/data/mechfiles/mechs/3145/NTNU RS/Griffin GRF-6S2.mtf b/megamek/data/mechfiles/mechs/3145/NTNU RS/Griffin GRF-6S2.mtf index a6c0ac08a1c..76f27775254 100644 --- a/megamek/data/mechfiles/mechs/3145/NTNU RS/Griffin GRF-6S2.mtf +++ b/megamek/data/mechfiles/mechs/3145/NTNU RS/Griffin GRF-6S2.mtf @@ -174,5 +174,5 @@ systemmanufacturer:ENGINE:Defiance 275 Light Engine systemmanufacturer:ARMOR:Starshield A with CASE II systemmanufacturer:JUMPJET:Chilton 950 systemmanufacturer:COMMUNICATIONS:Neil 6000 -systemmanufacturer:TARGETING:RCA Instatrack Mk X +systemmanufacturer:TARGETING:RCA Instatrac Mk X diff --git a/megamek/data/mechfiles/mechs/3145/NTNU RS/Wasp WSP-3K.mtf b/megamek/data/mechfiles/mechs/3145/NTNU RS/Wasp WSP-3K.mtf index ff1b2957955..5180fcade5f 100644 --- a/megamek/data/mechfiles/mechs/3145/NTNU RS/Wasp WSP-3K.mtf +++ b/megamek/data/mechfiles/mechs/3145/NTNU RS/Wasp WSP-3K.mtf @@ -170,6 +170,6 @@ systemmanufacturer:CHASSIS:Irian Second Generation Class 20 Endo Steel systemmanufacturer:ENGINE:Hermes 120 XL systemmanufacturer:ARMOR:Durallex Light systemmanufacturer:JUMPJET:Rawlings 52 -systemmanufacturer:COMMUNICATIONS:Duotech 65 +systemmanufacturer:COMMUNICATIONS:Duoteck 65 systemmanufacturer:TARGETING:RadCom TXX diff --git a/megamek/data/mechfiles/mechs/3145/NTNU RS/Wasp WSP-3P.mtf b/megamek/data/mechfiles/mechs/3145/NTNU RS/Wasp WSP-3P.mtf index 9758186336a..a34e3c1f42e 100644 --- a/megamek/data/mechfiles/mechs/3145/NTNU RS/Wasp WSP-3P.mtf +++ b/megamek/data/mechfiles/mechs/3145/NTNU RS/Wasp WSP-3P.mtf @@ -170,6 +170,6 @@ systemmanufacturer:CHASSIS:Irian Chassis Second Generation Class 20 Endo Steel systemmanufacturer:ENGINE:Hermes 120 systemmanufacturer:ARMOR:Durallex Light systemmanufacturer:JUMPJET:Rawlings 52 -systemmanufacturer:COMMUNICATIONS:Duotech 65 +systemmanufacturer:COMMUNICATIONS:Duoteck 65 systemmanufacturer:TARGETING:RadCom TXX diff --git a/megamek/data/mechfiles/mechs/3145/Steiner/King Crab KGC-009.mtf b/megamek/data/mechfiles/mechs/3145/Steiner/King Crab KGC-009.mtf index 2b842887dd4..d559993c5af 100644 --- a/megamek/data/mechfiles/mechs/3145/Steiner/King Crab KGC-009.mtf +++ b/megamek/data/mechfiles/mechs/3145/Steiner/King Crab KGC-009.mtf @@ -173,6 +173,6 @@ manufacturer:StarCorps Industries primaryfactory:Loburg systemmanufacturer:CHASSIS:StarFrame Hill Endo Steel systemmanufacturer:ENGINE:Vlar 300 -systemmanufacturer:ARMOR:Protec Tech 12 with CASE +systemmanufacturer:ARMOR:ProtecTech 12 with CASE systemmanufacturer:COMMUNICATIONS:Dalban Commline with ECM systemmanufacturer:TARGETING:Dalban HiRez-B diff --git a/megamek/data/mechfiles/mechs/3150/King Crab KGC-009C.mtf b/megamek/data/mechfiles/mechs/3150/King Crab KGC-009C.mtf index 68f25301519..f8ea95a54e1 100644 --- a/megamek/data/mechfiles/mechs/3150/King Crab KGC-009C.mtf +++ b/megamek/data/mechfiles/mechs/3150/King Crab KGC-009C.mtf @@ -168,7 +168,7 @@ manufacturer:Unknown primaryfactory:Unknown systemmanufacturer:CHASSIS:StarFrame Hill Endo Steel systemmanufacturer:ENGINE:Vlar 300 -systemmanufacturer:ARMOR:Protec Tech 12 with CASE +systemmanufacturer:ARMOR:ProtecTech 12 with CASE systemmanufacturer:COMMUNICATIONS:Dalban Commline with ECM systemmanufacturer:TARGETING:Dalban HiRez-B diff --git a/megamek/data/mechfiles/mechs/ER 2750/Crab CRB-27sl.mtf b/megamek/data/mechfiles/mechs/ER 2750/Crab CRB-27sl.mtf index 459c7425045..405bd83b13d 100644 --- a/megamek/data/mechfiles/mechs/ER 2750/Crab CRB-27sl.mtf +++ b/megamek/data/mechfiles/mechs/ER 2750/Crab CRB-27sl.mtf @@ -158,7 +158,7 @@ overview:Designed in 2719 during the last days of the Star League, the Crab was capabilities:Although lacking hand actuators or jump jets, it possessed good overland speed and its all-energy weapons payload was suitable for long-range missions without the prospect for resupply. The Crab also boasted a highly advanced communications system, the Dalban Series K, and was built mostly with proven parts easy to maintain. The term "Crab walk" soon became synonymous with easy duty, since technicians spent less than half the time maintaining the Crab than with other 'Mechs of the same weight class. -deployment:The Crab carries two RamTech 1200 Large Lasers, each housed in the claw and forearm of either arm. While excellent weapons they are quite delicate with the focusing mirrors liable to be knocked out of alignment if used in hand-to-hand combat; fixing them requires the pilot to leave their cockpit and stick their head up into each arm's elbow to make the necessary adjustments. Backing up the large lasers is a Ceres Arms Medium Laser in the center torso, well-protected from the fusion engine and with easy access to the sixteen heat sinks, and an Exostar Small Laser in the head, a last-resort weapon more suitable for fighting infantry and rioting citizens. Nine tons of Ferro-Fibrous Armor provides good protection for its size as even the weakest locations, the left and right torso, can each survive a shot from a PPC. Originally lacking hand actuators, Cosara later provided a refit kit to install one in either or both arms. +deployment:The Crab carries two RamTech 1200 Large Lasers, each housed in the claw and forearm of either arm. While excellent weapons they are quite delicate with the focusing mirrors liable to be knocked out of alignment if used in hand-to-hand combat; fixing them requires the pilot to leave their cockpit and stick their head up into each arm's elbow to make the necessary adjustments. Backing up the large lasers is a Ceres Arms Medium Laser in the center torso, well-protected from the fusion engine and with easy access to the sixteen heat sinks, and an ExoStar Small Laser in the head, a last-resort weapon more suitable for fighting infantry and rioting citizens. Nine tons of Ferro-Fibrous Armor provides good protection for its size as even the weakest locations, the left and right torso, can each survive a shot from a PPC. Originally lacking hand actuators, Cosara later provided a refit kit to install one in either or both arms. history:Less than a thousand Crabs had been produced when the Succession Wars began. So popular was the Crab that many believed it was likely to become the standard medium 'Mech of the SLDF. Unfortunately the Amaris Civil War and the dissolution of the Star League put an end to any future plans for the Crab. Cosara Weaponries' Crab factory on Northwind was practically destroyed in 2786, one of many strategic targets attacked in the opening salvos of the First Succession War. Although dedicated technicians were able to keep portions of the assembly line open, producing what spare parts they still could to rebuild damaged Crabs, the technology used for both the original's advanced armor plating and communications system became lost. Designated as CRB-20 models, these Crabs were only slightly inferior to the original: with the destruction of the military infrastructure necessary for the Dalban Series K's more advanced functions to work, its replacement by lesser systems ironically became less of an issue. By the end of the Fourth Succession War a hundred or so Crabs were still active in the Inner Sphere and all were CRB-20s. Unbeknownst to many, ComStar had secreted away massive stockpiles of Star League technology and 'Mechs, including the Crab. When it came time to form their own military original CRB-27 Crabs were used to outfit the Com Guards, while at the same time gifting downgraded CRB-20s to the Draconis Combine during the War of 3039 as part of Operation Rosebud. Concurrently the discovery of the Helm Memory Core allowed the refit line on Northwind to start upgrading the remaining downgraded Crabs to their original specification. Unknown to anyone in the Inner Sphere was the continued existence of the Crab in the arsenal of the Clans, although by the time of the Clan Invasion these had been relegated to second-line and garrison units. Eventually Cosara Weaponries was able to restart production of the original Crab in the 3050s and brand-new variants began turning up. Among these were new CRB-30s built by ComStar (later acquired by the Word of Blake) which made use of new C3 technology; it was also rumored ComStar sold these models to the rump Free Rasalhague Republic. During the Jihad the Word of Blake managed to capture the Northwind factory and begin producing their own radical variant known as the CRB-45. diff --git a/megamek/data/mechfiles/mechs/ForcePacks/UrbanMech/UrbanMech UM-R27.mtf b/megamek/data/mechfiles/mechs/ForcePacks/UrbanMech/UrbanMech UM-R27.mtf index 1a5781f3896..84cdfde538f 100644 --- a/megamek/data/mechfiles/mechs/ForcePacks/UrbanMech/UrbanMech UM-R27.mtf +++ b/megamek/data/mechfiles/mechs/ForcePacks/UrbanMech/UrbanMech UM-R27.mtf @@ -161,7 +161,7 @@ capabilities:This was achieved by starting with a cheap, easily-produced chassis deployment:No Information on this Variant -history:Large numbers of UrbanMechs were produced by Orguss Industries from 2675 until the destruction of their assembly lines. The UrbanMech reentered production at the Betelgeuse facility of Hellespont Industrials during the Jihad, and continued to be manufactured up through 3149. As such, UrbanMechs could be found in all of the armies of the Successor States. However most military leaders saw the slow little 'Mech as a liability, confining their stockpiles to garrison duty or stripping them of parts. This dismissive attitude towards the UrbanMech saved it from the ravages of the Succession Wars and ensured its continued use into the thirty-first century. The Capellan Confederation remained the largest and only user of UrbanMechs to actually deploy them for front-line duty, a result of the devastation of the Fourth Succession War and their desperation for any 'Mech to replenish their losses. The Confederation Reserve Cavalry and Capellan Defense Force had the lion's share of UrbanMechs, followed by the Tikonov Republican Guard and St. Ives Armored Cavalry; outside the Confederation the Federated Suns' Capellan March Militia fielded the largest number of UrbanMechs due to the fact it was composed of large amounts of captured Capellan equipment. Its prominence within the Confederation meant the UrbanMech was among those 'Mechs within the CCAF to receive upgrades following the recovery of lostech; the other States followed suit with much less priority over improving other 'Mechs. Despite this the sheer costs necessary to replace the UrbanMech's engine and increase its top speed meant even the Confederation limited their refit packages to improving the weapons and armor only. A testament to the desperation of the Word of Blake Jihad, Hellespont Industrials would reactivate a shuttered production facility on Betelgeuse to produce the UrbanMech alongside primitive "retrotech" designs for material starved Capellan garrison forces. This plant would maintain production of the UrbanMech in a steadily increasing volume of configurations throughout the Dark Age Era as the CCAF secretly expanded before it waged war against the Republic of the Sphere. Rather than dramatic and expensive enhancements, Hellespont's new variants retain the venerable design's low ground speed urban combat focus and can be applied as refits as readily as new production. +history:Large numbers of UrbanMechs were produced by Orgus Industries from 2675 until the destruction of their assembly lines. The UrbanMech reentered production at the Betelgeuse facility of Hellespont Industrials during the Jihad, and continued to be manufactured up through 3149. As such, UrbanMechs could be found in all of the armies of the Successor States. However most military leaders saw the slow little 'Mech as a liability, confining their stockpiles to garrison duty or stripping them of parts. This dismissive attitude towards the UrbanMech saved it from the ravages of the Succession Wars and ensured its continued use into the thirty-first century. The Capellan Confederation remained the largest and only user of UrbanMechs to actually deploy them for front-line duty, a result of the devastation of the Fourth Succession War and their desperation for any 'Mech to replenish their losses. The Confederation Reserve Cavalry and Capellan Defense Force had the lion's share of UrbanMechs, followed by the Tikonov Republican Guard and St. Ives Armored Cavalry; outside the Confederation the Federated Suns' Capellan March Militia fielded the largest number of UrbanMechs due to the fact it was composed of large amounts of captured Capellan equipment. Its prominence within the Confederation meant the UrbanMech was among those 'Mechs within the CCAF to receive upgrades following the recovery of lostech; the other States followed suit with much less priority over improving other 'Mechs. Despite this the sheer costs necessary to replace the UrbanMech's engine and increase its top speed meant even the Confederation limited their refit packages to improving the weapons and armor only. A testament to the desperation of the Word of Blake Jihad, Hellespont Industrials would reactivate a shuttered production facility on Betelgeuse to produce the UrbanMech alongside primitive "retrotech" designs for material starved Capellan garrison forces. This plant would maintain production of the UrbanMech in a steadily increasing volume of configurations throughout the Dark Age Era as the CCAF secretly expanded before it waged war against the Republic of the Sphere. Rather than dramatic and expensive enhancements, Hellespont's new variants retain the venerable design's low ground speed urban combat focus and can be applied as refits as readily as new production. manufacturer:Orgus Industries primaryfactory:Marcus diff --git a/megamek/data/mechfiles/mechs/ISP3/Reptar EPT-C-1 MilitiaMech.mtf b/megamek/data/mechfiles/mechs/ISP3/Reptar EPT-C-1 MilitiaMech.mtf index a69ce35f1c2..2e318f8f95b 100644 --- a/megamek/data/mechfiles/mechs/ISP3/Reptar EPT-C-1 MilitiaMech.mtf +++ b/megamek/data/mechfiles/mechs/ISP3/Reptar EPT-C-1 MilitiaMech.mtf @@ -5,7 +5,7 @@ mul id:5797 Config:Biped TechBase:Clan Era:3086 -Source:Intersteller Players 3 +Source:Interstellar Players 3 Rules Level:3 Mass:35 diff --git a/megamek/data/mechfiles/mechs/Operation Klondike/Crockett CRK-5003-1b.mtf b/megamek/data/mechfiles/mechs/Operation Klondike/Crockett CRK-5003-1b.mtf index 500f56d1691..9393e500f46 100644 --- a/megamek/data/mechfiles/mechs/Operation Klondike/Crockett CRK-5003-1b.mtf +++ b/megamek/data/mechfiles/mechs/Operation Klondike/Crockett CRK-5003-1b.mtf @@ -148,7 +148,7 @@ capabilities:Due to the fact that the Crockett was originally a training 'Mech, deployment:This SLDF Royal variant introduced in 2752 replaces the LB 10-X autocannon and SRM launchers with a suite of Medium Lasers and Medium Pulse Lasers. Each arm mounts an ER Large Laser with a medium laser and MPL mounted alongside. The head and center torso each mount a MPL as well. For long range firepower, a Gauss Rifle with two tons of ammo is mounted in the left torso. -history:Ten years after its introduction, however, Star League Defense Force commanders began to realize that Blankenburg Technologies had taken the "combat capability" requirement almost too seriously, and began to field the 'Mech on the front lines. Beyond its heavy weapons load-out, large number of heat sinks and use of jump jets, part of what made the Crockett successful was the enemy's unfamiliarity with this design, giving it an added advantage. Its cockpit systems, simplified for use as a trainer, allowed anyone to pilot the Crockett with only a minimal amount of familiarization training. The Crockett did not go without its growing pains, however. Once it was pressed into combat there was a flaw found in the cockpit's life support system that resulted in the death of three MechWarriors. This flaw was corrected in future production, with previously-issued machines recalled and refitted with the life support system upgrade. In service to the SLDF the hallmark tactic of the Crockett was to engage an enemy 'Mech at range and, before the enemy could accurately target it, jump behind them to attack their weaker rear. So effective was the Crockett that, following the dissolution of the Star League and start of the Succession Wars, many of the Great Houses removed the 'Mech from their training programs and used them to fight on the front lines. As many of the Crockett's components became lostech Blankenburg was forced to make do with inferior spare parts, reducing its capabilities with every year. Eventually the last few Crocketts were little more than a collection of salvaged parts, largely unrecognizable from their original design, until the 'Mech finally went extinct within the Inner Sphere. This changed starting in the thirty-first century, thanks to ComStar's secret stockpile of Star League-era 'Mechs. Original models of the Crockett were used to outfit the Com Guards while downgraded versions were gifted to the Draconis Combine as part of Operation Rosebud. With the Clan Invasion surviving models of the design were also seen among second-line Clan forces. As part of Precentor Martial Anastasius Focht's rearmament program the Blankenberg production line on Terra was reopened to start producing new Crocketts starting in 3054, although it would be only a few years until the Word of Blake conquered the planet and began supplying themselves and their Free Worlds League allies. In order to maintain their supply ComStar contracted Grumium Creations to begin producing Crocketts starting in 3062 and the 'Mech fought on both sides during the Jihad. +history:Ten years after its introduction, however, Star League Defense Force commanders began to realize that Blankenburg Technologies had taken the "combat capability" requirement almost too seriously, and began to field the 'Mech on the front lines. Beyond its heavy weapons load-out, large number of heat sinks and use of jump jets, part of what made the Crockett successful was the enemy's unfamiliarity with this design, giving it an added advantage. Its cockpit systems, simplified for use as a trainer, allowed anyone to pilot the Crockett with only a minimal amount of familiarization training. The Crockett did not go without its growing pains, however. Once it was pressed into combat there was a flaw found in the cockpit's life support system that resulted in the death of three MechWarriors. This flaw was corrected in future production, with previously-issued machines recalled and refitted with the life support system upgrade. In service to the SLDF the hallmark tactic of the Crockett was to engage an enemy 'Mech at range and, before the enemy could accurately target it, jump behind them to attack their weaker rear. So effective was the Crockett that, following the dissolution of the Star League and start of the Succession Wars, many of the Great Houses removed the 'Mech from their training programs and used them to fight on the front lines. As many of the Crockett's components became lostech Blankenburg was forced to make do with inferior spare parts, reducing its capabilities with every year. Eventually the last few Crocketts were little more than a collection of salvaged parts, largely unrecognizable from their original design, until the 'Mech finally went extinct within the Inner Sphere. This changed starting in the thirty-first century, thanks to ComStar's secret stockpile of Star League-era 'Mechs. Original models of the Crockett were used to outfit the Com Guards while downgraded versions were gifted to the Draconis Combine as part of Operation Rosebud. With the Clan Invasion surviving models of the design were also seen among second-line Clan forces. As part of Precentor Martial Anastasius Focht's rearmament program the Blankenburg production line on Terra was reopened to start producing new Crocketts starting in 3054, although it would be only a few years until the Word of Blake conquered the planet and began supplying themselves and their Free Worlds League allies. In order to maintain their supply ComStar contracted Grumium Creations to begin producing Crocketts starting in 3062 and the 'Mech fought on both sides during the Jihad. manufacturer:Blankenburg Technologies primaryfactory:Terra diff --git a/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 15/Phoenix Hawk IIC 10.mtf b/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 15/Phoenix Hawk IIC 10.mtf index ab78562d977..36db6a33398 100644 --- a/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 15/Phoenix Hawk IIC 10.mtf +++ b/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 15/Phoenix Hawk IIC 10.mtf @@ -165,5 +165,5 @@ systemmanufacturer:ENGINE:Type 70 400 XL Fusion systemmanufacturer:ARMOR:Forging AM15 Ferro-Fibrous with CASE systemmanufacturer:JUMPJET:Grandthrust Mk. 5 systemmanufacturer:COMMUNICATIONS:MegaBand System 21 -systemmanufacturer:TARGETING:Dtrac Suit 4 +systemmanufacturer:TARGETING:Dtrac Suite 4 diff --git a/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 15/Phoenix Hawk IIC 2.mtf b/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 15/Phoenix Hawk IIC 2.mtf index 5e61eeccfde..907dae681d3 100644 --- a/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 15/Phoenix Hawk IIC 2.mtf +++ b/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 15/Phoenix Hawk IIC 2.mtf @@ -165,5 +165,5 @@ systemmanufacturer:ENGINE:Type 70 400 XL Fusion systemmanufacturer:ARMOR:Forging AM15 Ferro-Fibrous with CASE systemmanufacturer:JUMPJET:Grandthrust Mk. 5 systemmanufacturer:COMMUNICATIONS:MegaBand System 21 -systemmanufacturer:TARGETING:Dtrac Suit 4 +systemmanufacturer:TARGETING:Dtrac Suite 4 diff --git a/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 15/Phoenix Hawk IIC 9.mtf b/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 15/Phoenix Hawk IIC 9.mtf index e3a9fbdb99c..a53ebef3edd 100644 --- a/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 15/Phoenix Hawk IIC 9.mtf +++ b/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 15/Phoenix Hawk IIC 9.mtf @@ -166,5 +166,5 @@ systemmanufacturer:ENGINE:Type 70 400 XL Fusion systemmanufacturer:ARMOR:Forging AM15 Ferro-Fibrous with CASE systemmanufacturer:JUMPJET:Grandthrust Mk. 5 systemmanufacturer:COMMUNICATIONS:MegaBand System 21 -systemmanufacturer:TARGETING:Dtrac Suit 4 +systemmanufacturer:TARGETING:Dtrac Suite 4 diff --git a/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 15/Phoenix Hawk IIC.mtf b/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 15/Phoenix Hawk IIC.mtf index 390d794befc..c8c6d53a973 100644 --- a/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 15/Phoenix Hawk IIC.mtf +++ b/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 15/Phoenix Hawk IIC.mtf @@ -169,5 +169,5 @@ systemmanufacturer:ENGINE:Type 70 400 XL Fusion systemmanufacturer:ARMOR:Forging AM15 Ferro-Fibrous with CASE systemmanufacturer:JUMPJET:Grandthrust Mk. 5 systemmanufacturer:COMMUNICATIONS:MegaBand System 21 -systemmanufacturer:TARGETING:Dtrac Suit 4 +systemmanufacturer:TARGETING:Dtrac Suite 4 diff --git a/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 2/UrbanMech UM-R96.mtf b/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 2/UrbanMech UM-R96.mtf index 194f233d7ed..484dbc4c6f8 100644 --- a/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 2/UrbanMech UM-R96.mtf +++ b/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 2/UrbanMech UM-R96.mtf @@ -160,7 +160,7 @@ capabilities:This was achieved by starting with a cheap, easily-produced chassis deployment:Another field refit developed by chronic tinker Njord Wing in 3149, the R96 is an evolution of the R80 with features of Wing's R93 refit. The R80's Snub-Nose PPC serves as the R96's main weapon, supported by a Small X-Pulse Laser, reducing its logistical needs. The weight saved allows the use of the R93's Harded Armor shell for enhanced protection at the cost of speed. This is partially offset with the addition of three Improved Jump Jets giving the new model a 90 meter range. -history:Large numbers of UrbanMechs were produced by Orguss Industries from 2675 until the destruction of their assembly lines. The UrbanMech reentered production at the Betelgeuse facility of Hellespont Industrials during the Jihad, and continued to be manufactured up through 3149. As such, UrbanMechs could be found in all of the armies of the Successor States. However most military leaders saw the slow little 'Mech as a liability, confining their stockpiles to garrison duty or stripping them of parts. This dismissive attitude towards the UrbanMech saved it from the ravages of the Succession Wars and ensured its continued use into the thirty-first century. The Capellan Confederation remained the largest and only user of UrbanMechs to actually deploy them for front-line duty, a result of the devastation of the Fourth Succession War and their desperation for any 'Mech to replenish their losses. The Confederation Reserve Cavalry and Capellan Defense Force had the lion's share of UrbanMechs, followed by the Tikonov Republican Guard and St. Ives Armored Cavalry; outside the Confederation the Federated Suns' Capellan March Militia fielded the largest number of UrbanMechs due to the fact it was composed of large amounts of captured Capellan equipment. Its prominence within the Confederation meant the UrbanMech was among those 'Mechs within the CCAF to receive upgrades following the recovery of lostech; the other States followed suit with much less priority over improving other 'Mechs. Despite this the sheer costs necessary to replace the UrbanMech's engine and increase its top speed meant even the Confederation limited their refit packages to improving the weapons and armor only. A testament to the desperation of the Word of Blake Jihad, Hellespont Industrials would reactivate a shuttered production facility on Betelgeuse to produce the UrbanMech alongside primitive "retrotech" designs for material starved Capellan garrison forces. This plant would maintain production of the UrbanMech in a steadily increasing volume of configurations throughout the Dark Age Era as the CCAF secretly expanded before it waged war against the Republic of the Sphere. Rather than dramatic and expensive enhancements, Hellespont's new variants retain the venerable design's low ground speed urban combat focus and can be applied as refits as readily as new production. +history:Large numbers of UrbanMechs were produced by Orgus Industries from 2675 until the destruction of their assembly lines. The UrbanMech reentered production at the Betelgeuse facility of Hellespont Industrials during the Jihad, and continued to be manufactured up through 3149. As such, UrbanMechs could be found in all of the armies of the Successor States. However most military leaders saw the slow little 'Mech as a liability, confining their stockpiles to garrison duty or stripping them of parts. This dismissive attitude towards the UrbanMech saved it from the ravages of the Succession Wars and ensured its continued use into the thirty-first century. The Capellan Confederation remained the largest and only user of UrbanMechs to actually deploy them for front-line duty, a result of the devastation of the Fourth Succession War and their desperation for any 'Mech to replenish their losses. The Confederation Reserve Cavalry and Capellan Defense Force had the lion's share of UrbanMechs, followed by the Tikonov Republican Guard and St. Ives Armored Cavalry; outside the Confederation the Federated Suns' Capellan March Militia fielded the largest number of UrbanMechs due to the fact it was composed of large amounts of captured Capellan equipment. Its prominence within the Confederation meant the UrbanMech was among those 'Mechs within the CCAF to receive upgrades following the recovery of lostech; the other States followed suit with much less priority over improving other 'Mechs. Despite this the sheer costs necessary to replace the UrbanMech's engine and increase its top speed meant even the Confederation limited their refit packages to improving the weapons and armor only. A testament to the desperation of the Word of Blake Jihad, Hellespont Industrials would reactivate a shuttered production facility on Betelgeuse to produce the UrbanMech alongside primitive "retrotech" designs for material starved Capellan garrison forces. This plant would maintain production of the UrbanMech in a steadily increasing volume of configurations throughout the Dark Age Era as the CCAF secretly expanded before it waged war against the Republic of the Sphere. Rather than dramatic and expensive enhancements, Hellespont's new variants retain the venerable design's low ground speed urban combat focus and can be applied as refits as readily as new production. manufacturer:Hellespont Industrials primaryfactory:Betelgeuse diff --git a/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 21/Cyclops C.mtf b/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 21/Cyclops C.mtf index a63c2da767a..06b7e7f6d80 100644 --- a/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 21/Cyclops C.mtf +++ b/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 21/Cyclops C.mtf @@ -159,7 +159,7 @@ Foot Actuator -Empty- overview:The Cyclops began production in 2710 as an assault BattleMech and headquarters unit for Star League Defense Force field commanders. -capabilities:A decent mix of weapons provided the Cyclops with both long- and short-range firepower and a sizable engine to keep up with mobile operations. But the centerpiece of the Cyclops is its sophisticated holographic battle computer, the Tacticon B-2000. When combined with the Omstead Olmstead 840 tight beam comm suite with SatNav module, the Cyclops can effectively command a brigade across the surface of an entire world. Unfortunately the Cyclops is poorly protected relative to other assault 'Mechs with only ten tons of armor, and while its normal load of twelve heat sinks allows it to stay cool in most cases, they can prove to be inadequate in especially heavy situations. +capabilities:A decent mix of weapons provided the Cyclops with both long- and short-range firepower and a sizable engine to keep up with mobile operations. But the centerpiece of the Cyclops is its sophisticated holographic battle computer, the Tacticon B-2000. When combined with the Olmstead 840 tight beam comm suite with SatNav module, the Cyclops can effectively command a brigade across the surface of an entire world. Unfortunately the Cyclops is poorly protected relative to other assault 'Mechs with only ten tons of armor, and while its normal load of twelve heat sinks allows it to stay cool in most cases, they can prove to be inadequate in especially heavy situations. deployment:Unknown history:Unfortunately the Cyclops did not fare so well with the onset of the Amaris Civil War when the Rim Worlds Republic Military destroyed its primary factory on Caph in 2774. Spare parts for the machine quickly began to dry up, until by the end of the Succession Wars less than ten percent still had a working B-2000 computer. Lacking the critical part of being a command vehicle many Cyclopses were pressed into an assault role. Acting as the bodyguard or decoy for the real commanding officer, they proved to be swift if mediocre combat machines. As most enemies know about the vulnerable head and automatically target it in combat, many Cyclops pilots also began adding false head protectors to defend against impacts. A study by the NAIS after the Fourth Succession War would eventually find that these caused more harm than good by restricting vision and increasing shrapnel, ending the practice altogether. The rediscovery of the Helm Memory Core kick-started a number of attempts to replicate the B-2000 computer, however there were no successful attempts prior to the Clan Invasion. Also, the invention of the C3 Computer with its emphasis on small-scale networking, and a switch in doctrine to using DropShips as command posts, saw the Cyclops' command role decline. However Grumium Creations was eventually able to restart production of new variants of the 'Mech, and where it has participated a Cyclops with a working B-2000 has had noticeable effects. For this reason Cyclops 'Mechs with a working battle computer were reserved for high-ranking officers. manufacturer:Grumium Creations diff --git a/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 21/Kodiak 6.mtf b/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 21/Kodiak 6.mtf index 06218d57b25..e693ed392c7 100644 --- a/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 21/Kodiak 6.mtf +++ b/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 21/Kodiak 6.mtf @@ -162,7 +162,7 @@ CLDoubleHeatSink -Empty- -Empty- -capabilities:Though not taken to the same extreme as other Clan Totem 'Mechs, the Kodiak does epitomize the Ghost Bears' method of warfare, combining an impressive defensive platform with surprising amounts of speed and firepower. Its massive 400-rated XL Engine propels the Kodiak to a maximum speed of 64.8 km/h, while seventeen and a half tons of Compound 12A2 gives it impressive armor protection. Though it mounts an incredible amount of firepower, even the use of twenty double heat sinks cannot prevent overheating problems when they are all fired simultaneously, though most MechWarriors learn to use their weapons sparingly and love the 'Mech's ability to deliver a massive knockout punch. The Kodiak incorporates the Garret L20 as its communications system, and uses the RCA Instatrack Mark IX for targeting, however the "claws" mounted on both of its arms are purely aesthetic. +capabilities:Though not taken to the same extreme as other Clan Totem 'Mechs, the Kodiak does epitomize the Ghost Bears' method of warfare, combining an impressive defensive platform with surprising amounts of speed and firepower. Its massive 400-rated XL Engine propels the Kodiak to a maximum speed of 64.8 km/h, while seventeen and a half tons of Compound 12A2 gives it impressive armor protection. Though it mounts an incredible amount of firepower, even the use of twenty double heat sinks cannot prevent overheating problems when they are all fired simultaneously, though most MechWarriors learn to use their weapons sparingly and love the 'Mech's ability to deliver a massive knockout punch. The Kodiak incorporates the Garret L20 as its communications system, and uses the RCA Instatrac Mark IX for targeting, however the "claws" mounted on both of its arms are purely aesthetic. deployment:Unknown diff --git a/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 21/Ostroc OSR-2D.mtf b/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 21/Ostroc OSR-2D.mtf index 6a8294ca57b..e6049307233 100644 --- a/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 21/Ostroc OSR-2D.mtf +++ b/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 21/Ostroc OSR-2D.mtf @@ -161,7 +161,7 @@ capabilities:Its unique walker/pod profile, later seen in the Stalker and Maraud deployment:Upgraded with Star League technology, the 2D variant of the Ostroc extends the 'Mechs maximum range by replacing the Large Lasers with two ER Large Lasers. The 2D retains the Medium Lasers and SRM-4 of the 2C model. To handle the heat burden it is also equipped with double heat sinks. Being a relatively rare design, the Ostroc had no official field refit kit but the 2D variant was a common upgrade in 3050 if the parts could be obtained. -history:The best-known of Ostman Industries' Ost Class of 'Mechs, the Ostroc debuted in 2511 and proved so successful in this role production continued for approximately 200 years. While a quality 'Mech, the low production capacity of Ostman Industries made the Ostroc a rarity; indeed the company licensed their other Ost 'Mechs out to Kong Interstellar just to maintain their rate of production, and the majority of those produced were assigned garrison duties within the Terran Hegemony. Still, the 'Mech saw action in every major conflict of the Star League, especially towards the end in the civil war and subsequent First Succession War. The destruction of Ostman Industries meant an end to any new Ostrocs, although all sides of the Succession Wars continued to field these 'Mechs in combat, particularly the Draconis Combine. It was because of the small number and wide dispersal of surviving Ostrocs that the design was largely passed over while others were being updated after the Helm Memory Core discovery. A major revitalization of the design took place within the Capellan Confederation after the Clan Invasion. Having largely rebuilt their forces after the previous decades' setbacks, the Strategios wanted to update the ancient 'Mech, but rather than reverse-engineering the original they ordered all Capellan 'Mech manufacturers to submit bids for a replacement. Ceres Metals was the only one to send in a proposal which matched exactly what they wanted and won the contract, completing the first production run in January 3067. Versions of these new Ostrocs also started showing up in the Taurian Concordat and Circinus Federation, a result of espionage according to Capellan charges. +history:The best-known of Ostmann Industries' Ost Class of 'Mechs, the Ostroc debuted in 2511 and proved so successful in this role production continued for approximately 200 years. While a quality 'Mech, the low production capacity of Ostmann Industries made the Ostroc a rarity; indeed the company licensed their other Ost 'Mechs out to Kong Interstellar just to maintain their rate of production, and the majority of those produced were assigned garrison duties within the Terran Hegemony. Still, the 'Mech saw action in every major conflict of the Star League, especially towards the end in the civil war and subsequent First Succession War. The destruction of Ostmann Industries meant an end to any new Ostrocs, although all sides of the Succession Wars continued to field these 'Mechs in combat, particularly the Draconis Combine. It was because of the small number and wide dispersal of surviving Ostrocs that the design was largely passed over while others were being updated after the Helm Memory Core discovery. A major revitalization of the design took place within the Capellan Confederation after the Clan Invasion. Having largely rebuilt their forces after the previous decades' setbacks, the Strategios wanted to update the ancient 'Mech, but rather than reverse-engineering the original they ordered all Capellan 'Mech manufacturers to submit bids for a replacement. Ceres Metals was the only one to send in a proposal which matched exactly what they wanted and won the contract, completing the first production run in January 3067. Versions of these new Ostrocs also started showing up in the Taurian Concordat and Circinus Federation, a result of espionage according to Capellan charges. manufacturer:Diplass BattleMechs,Kong Interstellar Corporation,Kong Interstellar Corporation,Ostmann Industries primaryfactory:Apollo,Connaught,Loxley,Terra diff --git a/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 21/Ostroc OSR-3M.mtf b/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 21/Ostroc OSR-3M.mtf index 21ae1ff2ae8..ddda08f0d41 100644 --- a/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 21/Ostroc OSR-3M.mtf +++ b/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 21/Ostroc OSR-3M.mtf @@ -161,7 +161,7 @@ capabilities:Its unique walker/pod profile, later seen in the Stalker and Maraud deployment:Unknown -history:The best-known of Ostman Industries' Ost Class of 'Mechs, the Ostroc debuted in 2511 and proved so successful in this role production continued for approximately 200 years. While a quality 'Mech, the low production capacity of Ostman Industries made the Ostroc a rarity; indeed the company licensed their other Ost 'Mechs out to Kong Interstellar just to maintain their rate of production, and the majority of those produced were assigned garrison duties within the Terran Hegemony. Still, the 'Mech saw action in every major conflict of the Star League, especially towards the end in the civil war and subsequent First Succession War. The destruction of Ostman Industries meant an end to any new Ostrocs, although all sides of the Succession Wars continued to field these 'Mechs in combat, particularly the Draconis Combine. It was because of the small number and wide dispersal of surviving Ostrocs that the design was largely passed over while others were being updated after the Helm Memory Core discovery. A major revitalization of the design took place within the Capellan Confederation after the Clan Invasion. Having largely rebuilt their forces after the previous decades' setbacks, the Strategios wanted to update the ancient 'Mech, but rather than reverse-engineering the original they ordered all Capellan 'Mech manufacturers to submit bids for a replacement. Ceres Metals was the only one to send in a proposal which matched exactly what they wanted and won the contract, completing the first production run in January 3067. Versions of these new Ostrocs also started showing up in the Taurian Concordat and Circinus Federation, a result of espionage according to Capellan charges. +history:The best-known of Ostmann Industries' Ost Class of 'Mechs, the Ostroc debuted in 2511 and proved so successful in this role production continued for approximately 200 years. While a quality 'Mech, the low production capacity of Ostmann Industries made the Ostroc a rarity; indeed the company licensed their other Ost 'Mechs out to Kong Interstellar just to maintain their rate of production, and the majority of those produced were assigned garrison duties within the Terran Hegemony. Still, the 'Mech saw action in every major conflict of the Star League, especially towards the end in the civil war and subsequent First Succession War. The destruction of Ostmann Industries meant an end to any new Ostrocs, although all sides of the Succession Wars continued to field these 'Mechs in combat, particularly the Draconis Combine. It was because of the small number and wide dispersal of surviving Ostrocs that the design was largely passed over while others were being updated after the Helm Memory Core discovery. A major revitalization of the design took place within the Capellan Confederation after the Clan Invasion. Having largely rebuilt their forces after the previous decades' setbacks, the Strategios wanted to update the ancient 'Mech, but rather than reverse-engineering the original they ordered all Capellan 'Mech manufacturers to submit bids for a replacement. Ceres Metals was the only one to send in a proposal which matched exactly what they wanted and won the contract, completing the first production run in January 3067. Versions of these new Ostrocs also started showing up in the Taurian Concordat and Circinus Federation, a result of espionage according to Capellan charges. manufacturer:Ronin Incorporated primaryfactory:Wallis diff --git a/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 21/Ostroc OSR-6R.mtf b/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 21/Ostroc OSR-6R.mtf index 6e61ed63612..2d0c19bfb22 100644 --- a/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 21/Ostroc OSR-6R.mtf +++ b/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 21/Ostroc OSR-6R.mtf @@ -162,7 +162,7 @@ capabilities:Its unique walker/pod profile, later seen in the Stalker and Maraud deployment:Unknown -history:The best-known of Ostman Industries' Ost Class of 'Mechs, the Ostroc debuted in 2511 and proved so successful in this role production continued for approximately 200 years. While a quality 'Mech, the low production capacity of Ostman Industries made the Ostroc a rarity; indeed the company licensed their other Ost 'Mechs out to Kong Interstellar just to maintain their rate of production, and the majority of those produced were assigned garrison duties within the Terran Hegemony. Still, the 'Mech saw action in every major conflict of the Star League, especially towards the end in the civil war and subsequent First Succession War. The destruction of Ostman Industries meant an end to any new Ostrocs, although all sides of the Succession Wars continued to field these 'Mechs in combat, particularly the Draconis Combine. It was because of the small number and wide dispersal of surviving Ostrocs that the design was largely passed over while others were being updated after the Helm Memory Core discovery. A major revitalization of the design took place within the Capellan Confederation after the Clan Invasion. Having largely rebuilt their forces after the previous decades' setbacks, the Strategios wanted to update the ancient 'Mech, but rather than reverse-engineering the original they ordered all Capellan 'Mech manufacturers to submit bids for a replacement. Ceres Metals was the only one to send in a proposal which matched exactly what they wanted and won the contract, completing the first production run in January 3067. Versions of these new Ostrocs also started showing up in the Taurian Concordat and Circinus Federation, a result of espionage according to Capellan charges. +history:The best-known of Ostmann Industries' Ost Class of 'Mechs, the Ostroc debuted in 2511 and proved so successful in this role production continued for approximately 200 years. While a quality 'Mech, the low production capacity of Ostmann Industries made the Ostroc a rarity; indeed the company licensed their other Ost 'Mechs out to Kong Interstellar just to maintain their rate of production, and the majority of those produced were assigned garrison duties within the Terran Hegemony. Still, the 'Mech saw action in every major conflict of the Star League, especially towards the end in the civil war and subsequent First Succession War. The destruction of Ostmann Industries meant an end to any new Ostrocs, although all sides of the Succession Wars continued to field these 'Mechs in combat, particularly the Draconis Combine. It was because of the small number and wide dispersal of surviving Ostrocs that the design was largely passed over while others were being updated after the Helm Memory Core discovery. A major revitalization of the design took place within the Capellan Confederation after the Clan Invasion. Having largely rebuilt their forces after the previous decades' setbacks, the Strategios wanted to update the ancient 'Mech, but rather than reverse-engineering the original they ordered all Capellan 'Mech manufacturers to submit bids for a replacement. Ceres Metals was the only one to send in a proposal which matched exactly what they wanted and won the contract, completing the first production run in January 3067. Versions of these new Ostrocs also started showing up in the Taurian Concordat and Circinus Federation, a result of espionage according to Capellan charges. manufacturer:Kong Interstellar Corporation primaryfactory:Connaught diff --git a/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 21/Ostroc OSR-9C.mtf b/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 21/Ostroc OSR-9C.mtf index a8a140ed2e3..d229669c04b 100644 --- a/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 21/Ostroc OSR-9C.mtf +++ b/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 21/Ostroc OSR-9C.mtf @@ -162,7 +162,7 @@ capabilities:Its unique walker/pod profile, later seen in the Stalker and Maraud deployment:Known as the Ostroc Mk II, this 'Mech might as well be considered a new, different design (much like the Grand Dragon evolved from the Dragon, the Mauler from the Daboku or the Hatamoto-Chi from the Charger). The Ostroc Mk II swaps the SRM-4 for one SRM-2 launcher in each side torso, with one ton of ammunition in the center torso. Half a ton of armor was added to the front torso and legs (adding one point to each leg and side torso, and four to center torso), and four more heat sinks were installed along with three jump jets for a jump capacity of 90 meters. To make room for these components, the engine had to be changed to a Pitban 240, reducing the top speed to 64.8 km/h. -history:The best-known of Ostman Industries' Ost Class of 'Mechs, the Ostroc debuted in 2511 and proved so successful in this role production continued for approximately 200 years. While a quality 'Mech, the low production capacity of Ostman Industries made the Ostroc a rarity; indeed the company licensed their other Ost 'Mechs out to Kong Interstellar just to maintain their rate of production, and the majority of those produced were assigned garrison duties within the Terran Hegemony. Still, the 'Mech saw action in every major conflict of the Star League, especially towards the end in the civil war and subsequent First Succession War. The destruction of Ostman Industries meant an end to any new Ostrocs, although all sides of the Succession Wars continued to field these 'Mechs in combat, particularly the Draconis Combine. It was because of the small number and wide dispersal of surviving Ostrocs that the design was largely passed over while others were being updated after the Helm Memory Core discovery. A major revitalization of the design took place within the Capellan Confederation after the Clan Invasion. Having largely rebuilt their forces after the previous decades' setbacks, the Strategios wanted to update the ancient 'Mech, but rather than reverse-engineering the original they ordered all Capellan 'Mech manufacturers to submit bids for a replacement. Ceres Metals was the only one to send in a proposal which matched exactly what they wanted and won the contract, completing the first production run in January 3067. Versions of these new Ostrocs also started showing up in the Taurian Concordat and Circinus Federation, a result of espionage according to Capellan charges. +history:The best-known of Ostmann Industries' Ost Class of 'Mechs, the Ostroc debuted in 2511 and proved so successful in this role production continued for approximately 200 years. While a quality 'Mech, the low production capacity of Ostmann Industries made the Ostroc a rarity; indeed the company licensed their other Ost 'Mechs out to Kong Interstellar just to maintain their rate of production, and the majority of those produced were assigned garrison duties within the Terran Hegemony. Still, the 'Mech saw action in every major conflict of the Star League, especially towards the end in the civil war and subsequent First Succession War. The destruction of Ostmann Industries meant an end to any new Ostrocs, although all sides of the Succession Wars continued to field these 'Mechs in combat, particularly the Draconis Combine. It was because of the small number and wide dispersal of surviving Ostrocs that the design was largely passed over while others were being updated after the Helm Memory Core discovery. A major revitalization of the design took place within the Capellan Confederation after the Clan Invasion. Having largely rebuilt their forces after the previous decades' setbacks, the Strategios wanted to update the ancient 'Mech, but rather than reverse-engineering the original they ordered all Capellan 'Mech manufacturers to submit bids for a replacement. Ceres Metals was the only one to send in a proposal which matched exactly what they wanted and won the contract, completing the first production run in January 3067. Versions of these new Ostrocs also started showing up in the Taurian Concordat and Circinus Federation, a result of espionage according to Capellan charges. manufacturer:Diplass BattleMechs,Kong Interstellar Corporation,Kong Interstellar Corporation,Ostmann Industries primaryfactory:Apollo,Connaught,Loxley,Terra diff --git a/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 29/Charger C.mtf b/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 29/Charger C.mtf index c5de900985b..14994f012ca 100644 --- a/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 29/Charger C.mtf +++ b/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 29/Charger C.mtf @@ -164,6 +164,6 @@ systemmanufacturer:CHASSIS:Wells 990 systemmanufacturer:ENGINE:LTV 400 XL systemmanufacturer:ARMOR:Compound LZ-7 systemmanufacturer:JUMPJET:Icarus 81 -systemmanufacturer:COMMUNICATIONS:Tek Batt with Angel ECM +systemmanufacturer:COMMUNICATIONS:Tek BattleComwith Angel ECM systemmanufacturer:TARGETING:Dalban Hirez with Bloodhound Active Probe diff --git a/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 31/Clint CLNT-3 4T.mtf b/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 31/Clint CLNT-3 4T.mtf index eb171b81c44..8a24fbd6164 100644 --- a/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 31/Clint CLNT-3 4T.mtf +++ b/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 31/Clint CLNT-3 4T.mtf @@ -169,7 +169,7 @@ manufacturer:Pinard Protectorates Limited primaryfactory:Macleod's Land systemmanufacturer:CHASSIS:Andoran Model III systemmanufacturer:ENGINE:Ceres Motors 240 XL -systemmanufacturer:ARMOR:StarGuard Reflec with CASEII +systemmanufacturer:ARMOR:StarGuard Reflec with CASE II systemmanufacturer:COMMUNICATIONS:Raldon R1 systemmanufacturer:TARGETING:Sloane 220 Lockover System systemmanufacturer:JUMPJET:Andoran Model JJII diff --git a/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 4/Wasp WSP-3W.mtf b/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 4/Wasp WSP-3W.mtf index 6572e31eb76..a9e3338e99a 100644 --- a/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 4/Wasp WSP-3W.mtf +++ b/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 4/Wasp WSP-3W.mtf @@ -173,5 +173,5 @@ systemmanufacturer:CHASSIS:1A Type 3 systemmanufacturer:ENGINE:Hermes 120 systemmanufacturer:ARMOR:Durallex Light Ferro-Fibrous systemmanufacturer:JUMPJET:Rawlings 52 -systemmanufacturer:COMMUNICATIONS:Duotech 65 +systemmanufacturer:COMMUNICATIONS:Duoteck 65 systemmanufacturer:TARGETING:RadCom TXX diff --git a/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 4/Wasp WSP-4W.mtf b/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 4/Wasp WSP-4W.mtf index 6fdc7202d90..4e12f915f9a 100644 --- a/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 4/Wasp WSP-4W.mtf +++ b/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 4/Wasp WSP-4W.mtf @@ -171,5 +171,5 @@ systemmanufacturer:CHASSIS:1A Type 3 systemmanufacturer:ENGINE:Hermes 120 Light systemmanufacturer:ARMOR:Durallex Light Ferro-Fibrous systemmanufacturer:JUMPJET:Rawlings 52 -systemmanufacturer:COMMUNICATIONS:Duotech 65 +systemmanufacturer:COMMUNICATIONS:Duoteck 65 systemmanufacturer:TARGETING:RadCom TXX diff --git a/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/Hellhound (Conjurer) 7.mtf b/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/Hellhound (Conjurer) 7.mtf index 73992bddd2a..e5fc4870077 100644 --- a/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/Hellhound (Conjurer) 7.mtf +++ b/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/Hellhound (Conjurer) 7.mtf @@ -165,7 +165,7 @@ history:Even with an established infrastructure, rebuilding a destroyed Touman f manufacturer:Kallon Weapon Industries primaryfactory:Thermopolis systemmanufacturer:CHASSIS:Puma Type Medium Endo Steel -systemmanufacturer:ENGINE:Star League Standart 300 +systemmanufacturer:ENGINE:Star League Standard 300 systemmanufacturer:ARMOR:Alpha Plate Special Ferro-Fibrous systemmanufacturer:COMMUNICATIONS:JNE II Integrated systemmanufacturer:TARGETING:Build 4 CAT Advanced TTS diff --git a/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/Hellhound (Conjurer).mtf b/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/Hellhound (Conjurer).mtf index 28d2f8d7fc0..6951aa8abfd 100644 --- a/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/Hellhound (Conjurer).mtf +++ b/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/Hellhound (Conjurer).mtf @@ -167,7 +167,7 @@ history:Even with an established infrastructure, rebuilding a destroyed Touman f manufacturer:Strana Mechty MechWorks,Kallon Weapon Industries primaryfactory:Strana Mechty,Thermopolis systemmanufacturer:CHASSIS:Puma Type Medium Endo Steel -systemmanufacturer:ENGINE:Star League Standart 300 +systemmanufacturer:ENGINE:Star League Standard 300 systemmanufacturer:ARMOR:Alpha Plate Special Ferro-Fibrous systemmanufacturer:COMMUNICATIONS:JNE II Integrated systemmanufacturer:TARGETING:Build 4 CAT Advanced TTS diff --git a/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/King Crab KGC-011.mtf b/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/King Crab KGC-011.mtf index e2e33001fe0..6b3e61647a8 100644 --- a/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/King Crab KGC-011.mtf +++ b/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/King Crab KGC-011.mtf @@ -166,6 +166,6 @@ manufacturer:Cosara Weaponries,Cosara Weaponries primaryfactory:Mars,Northwind systemmanufacturer:CHASSIS:Hollis Mark Composite systemmanufacturer:ENGINE:Defiance 400 XXL -systemmanufacturer:ARMOR:Protec Tech 12 +systemmanufacturer:ARMOR:ProtecTech 12 systemmanufacturer:COMMUNICATIONS:Dalban Commline systemmanufacturer:TARGETING:Dalban HiRez-B diff --git a/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 8/Dragonfly (Viper) J.mtf b/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 8/Dragonfly (Viper) J.mtf index 093ce20e39c..b05f72ec82a 100644 --- a/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 8/Dragonfly (Viper) J.mtf +++ b/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 8/Dragonfly (Viper) J.mtf @@ -160,7 +160,7 @@ Jump Jet overview:The Viper is a fast, highly-maneuverable medium OmniMech originally designed by Clan Fire Mandrill on Shadow. Codenamed the Dragonfly by the Inner Sphere forces that first encountered this small but fierce OmniMech, the name stuck because of its ability to move swiftly over the battlefield. The Viper is fast and well-armored, but significantly under-gunned compared with other Clan OmniMechs massing 35-45 tons (including the Adder, Battle Cobra, Grendel, Shadow Cat, Pouncer, and Cougar). -capabilities: The Viper is built on a lightweight Endo Steel chassis and powered by a weight saving 320 XL engine that propels the Viper to a top speed of 129.6 km/h. The Viper augments its impressive ground speed with eight jump jets that allow it to jump up to a distance of two hundred and forty meters. The Viper has seven tons of Ferro-Fibrous armor to absorb any damage from shots that are lucky enough to strike it and has eight and a half tons of podspace for its weapons payload. +capabilities: The Viper is built on a lightweight Endo Steel chassis and powered by a weight saving 320 XL engine that propels the Viper to a top speed of 129.6 km/h. The Viper augments its impressive ground speed with eight jump jets that allow it to jump up to a distance of two hundred and forty meters. The Viper has seven tons of Ferro-Fibrous armor to absorb any damage from shots that are lucky enough to strike it and has eight and a half tons of pod space for its weapons payload. history:Clan Ghost Bear came into possession of the design in 3002 when they traded several production runs of Executioner OmniMechs for the design and production facilities on Shadow. Rather than trial for land rights to Shadow, and become embroiled in the internecine struggles of the Fire Mandrills, the Bears restructured the facility, making the lines modular, and relocated production to Strana Mechty - this modular technology proved very useful when the Ghost Bears migrated back to the Inner Sphere in the late 3050s. Surprisingly, the Bears left their first modular production facility on Strana Mechty. Production continued on Strana Mechty for Clan Ghost Bear until the mid-3060s when the Hell's Horses won the production rights and the facility (and then promptly lost the facility to Clan Ice Hellion in 3068). In addition to the manufacturing plant on Strana Mechty, at least one other planet in the Homeworlds was home to a manufacturing line producing Vipers; in 3071 Clan Goliath Scorpion captured a Viper factory from Clan Coyote on Delios, although it is unknown if the planet survived the Wars of Reaving, Goliath Scorpion Abjurement and the subsequent abandonment of the planet by the Coyotes and Cloud Cobras. manufacturer:Upsilon Plant 2J, Dominion Facility Kappa-5 diff --git a/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 8/Dragonfly (Viper) K.mtf b/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 8/Dragonfly (Viper) K.mtf index e549aaf3f11..e6e659d4662 100644 --- a/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 8/Dragonfly (Viper) K.mtf +++ b/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 8/Dragonfly (Viper) K.mtf @@ -159,7 +159,7 @@ Jump Jet overview:The Viper is a fast, highly-maneuverable medium OmniMech originally designed by Clan Fire Mandrill on Shadow. Codenamed the Dragonfly by the Inner Sphere forces that first encountered this small but fierce OmniMech, the name stuck because of its ability to move swiftly over the battlefield. The Viper is fast and well-armored, but significantly under-gunned compared with other Clan OmniMechs massing 35-45 tons (including the Adder, Battle Cobra, Grendel, Shadow Cat, Pouncer, and Cougar). -capabilities: The Viper is built on a lightweight Endo Steel chassis and powered by a weight saving 320 XL engine that propels the Viper to a top speed of 129.6 km/h. The Viper augments its impressive ground speed with eight jump jets that allow it to jump up to a distance of two hundred and forty meters. The Viper has seven tons of Ferro-Fibrous armor to absorb any damage from shots that are lucky enough to strike it and has eight and a half tons of podspace for its weapons payload. +capabilities: The Viper is built on a lightweight Endo Steel chassis and powered by a weight saving 320 XL engine that propels the Viper to a top speed of 129.6 km/h. The Viper augments its impressive ground speed with eight jump jets that allow it to jump up to a distance of two hundred and forty meters. The Viper has seven tons of Ferro-Fibrous armor to absorb any damage from shots that are lucky enough to strike it and has eight and a half tons of pod space for its weapons payload. history:Clan Ghost Bear came into possession of the design in 3002 when they traded several production runs of Executioner OmniMechs for the design and production facilities on Shadow. Rather than trial for land rights to Shadow, and become embroiled in the internecine struggles of the Fire Mandrills, the Bears restructured the facility, making the lines modular, and relocated production to Strana Mechty - this modular technology proved very useful when the Ghost Bears migrated back to the Inner Sphere in the late 3050s. Surprisingly, the Bears left their first modular production facility on Strana Mechty. Production continued on Strana Mechty for Clan Ghost Bear until the mid-3060s when the Hell's Horses won the production rights and the facility (and then promptly lost the facility to Clan Ice Hellion in 3068). In addition to the manufacturing plant on Strana Mechty, at least one other planet in the Homeworlds was home to a manufacturing line producing Vipers; in 3071 Clan Goliath Scorpion captured a Viper factory from Clan Coyote on Delios, although it is unknown if the planet survived the Wars of Reaving, Goliath Scorpion Abjurement and the subsequent abandonment of the planet by the Coyotes and Cloud Cobras. manufacturer:Upsilon Plant 2J, Dominion Facility Kappa-5 diff --git a/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 8/Dragonfly (Viper) L.mtf b/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 8/Dragonfly (Viper) L.mtf index 5ea9f91920f..7900ed47b2c 100644 --- a/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 8/Dragonfly (Viper) L.mtf +++ b/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 8/Dragonfly (Viper) L.mtf @@ -158,7 +158,7 @@ Jump Jet overview:The Viper is a fast, highly-maneuverable medium OmniMech originally designed by Clan Fire Mandrill on Shadow. Codenamed the Dragonfly by the Inner Sphere forces that first encountered this small but fierce OmniMech, the name stuck because of its ability to move swiftly over the battlefield. The Viper is fast and well-armored, but significantly under-gunned compared with other Clan OmniMechs massing 35-45 tons (including the Adder, Battle Cobra, Grendel, Shadow Cat, Pouncer, and Cougar). -capabilities: The Viper is built on a lightweight Endo Steel chassis and powered by a weight saving 320 XL engine that propels the Viper to a top speed of 129.6 km/h. The Viper augments its impressive ground speed with eight jump jets that allow it to jump up to a distance of two hundred and forty meters. The Viper has seven tons of Ferro-Fibrous armor to absorb any damage from shots that are lucky enough to strike it and has eight and a half tons of podspace for its weapons payload. +capabilities: The Viper is built on a lightweight Endo Steel chassis and powered by a weight saving 320 XL engine that propels the Viper to a top speed of 129.6 km/h. The Viper augments its impressive ground speed with eight jump jets that allow it to jump up to a distance of two hundred and forty meters. The Viper has seven tons of Ferro-Fibrous armor to absorb any damage from shots that are lucky enough to strike it and has eight and a half tons of pod space for its weapons payload. history:Clan Ghost Bear came into possession of the design in 3002 when they traded several production runs of Executioner OmniMechs for the design and production facilities on Shadow. Rather than trial for land rights to Shadow, and become embroiled in the internecine struggles of the Fire Mandrills, the Bears restructured the facility, making the lines modular, and relocated production to Strana Mechty - this modular technology proved very useful when the Ghost Bears migrated back to the Inner Sphere in the late 3050s. Surprisingly, the Bears left their first modular production facility on Strana Mechty. Production continued on Strana Mechty for Clan Ghost Bear until the mid-3060s when the Hell's Horses won the production rights and the facility (and then promptly lost the facility to Clan Ice Hellion in 3068). In addition to the manufacturing plant on Strana Mechty, at least one other planet in the Homeworlds was home to a manufacturing line producing Vipers; in 3071 Clan Goliath Scorpion captured a Viper factory from Clan Coyote on Delios, although it is unknown if the planet survived the Wars of Reaving, Goliath Scorpion Abjurement and the subsequent abandonment of the planet by the Coyotes and Cloud Cobras. manufacturer:Upsilon Plant 2J, Dominion Facility Kappa-5 diff --git a/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 8/Dragonfly (Viper) M.mtf b/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 8/Dragonfly (Viper) M.mtf index a1b1d4dcf3e..2e370af84d1 100644 --- a/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 8/Dragonfly (Viper) M.mtf +++ b/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 8/Dragonfly (Viper) M.mtf @@ -158,7 +158,7 @@ Jump Jet overview:The Viper is a fast, highly-maneuverable medium OmniMech originally designed by Clan Fire Mandrill on Shadow. Codenamed the Dragonfly by the Inner Sphere forces that first encountered this small but fierce OmniMech, the name stuck because of its ability to move swiftly over the battlefield. The Viper is fast and well-armored, but significantly under-gunned compared with other Clan OmniMechs massing 35-45 tons (including the Adder, Battle Cobra, Grendel, Shadow Cat, Pouncer, and Cougar). -capabilities: The Viper is built on a lightweight Endo Steel chassis and powered by a weight saving 320 XL engine that propels the Viper to a top speed of 129.6 km/h. The Viper augments its impressive ground speed with eight jump jets that allow it to jump up to a distance of two hundred and forty meters. The Viper has seven tons of Ferro-Fibrous armor to absorb any damage from shots that are lucky enough to strike it and has eight and a half tons of podspace for its weapons payload. +capabilities: The Viper is built on a lightweight Endo Steel chassis and powered by a weight saving 320 XL engine that propels the Viper to a top speed of 129.6 km/h. The Viper augments its impressive ground speed with eight jump jets that allow it to jump up to a distance of two hundred and forty meters. The Viper has seven tons of Ferro-Fibrous armor to absorb any damage from shots that are lucky enough to strike it and has eight and a half tons of pod space for its weapons payload. history:Clan Ghost Bear came into possession of the design in 3002 when they traded several production runs of Executioner OmniMechs for the design and production facilities on Shadow. Rather than trial for land rights to Shadow, and become embroiled in the internecine struggles of the Fire Mandrills, the Bears restructured the facility, making the lines modular, and relocated production to Strana Mechty - this modular technology proved very useful when the Ghost Bears migrated back to the Inner Sphere in the late 3050s. Surprisingly, the Bears left their first modular production facility on Strana Mechty. Production continued on Strana Mechty for Clan Ghost Bear until the mid-3060s when the Hell's Horses won the production rights and the facility (and then promptly lost the facility to Clan Ice Hellion in 3068). In addition to the manufacturing plant on Strana Mechty, at least one other planet in the Homeworlds was home to a manufacturing line producing Vipers; in 3071 Clan Goliath Scorpion captured a Viper factory from Clan Coyote on Delios, although it is unknown if the planet survived the Wars of Reaving, Goliath Scorpion Abjurement and the subsequent abandonment of the planet by the Coyotes and Cloud Cobras. manufacturer:Upsilon Plant 2J, Dominion Facility Kappa-5 diff --git a/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 8/Dragonfly (Viper) R.mtf b/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 8/Dragonfly (Viper) R.mtf index 3ac33f733b8..43a73fdc86e 100644 --- a/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 8/Dragonfly (Viper) R.mtf +++ b/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 8/Dragonfly (Viper) R.mtf @@ -157,7 +157,7 @@ Jump Jet overview:The Viper is a fast, highly-maneuverable medium OmniMech originally designed by Clan Fire Mandrill on Shadow. Codenamed the Dragonfly by the Inner Sphere forces that first encountered this small but fierce OmniMech, the name stuck because of its ability to move swiftly over the battlefield. The Viper is fast and well-armored, but significantly under-gunned compared with other Clan OmniMechs massing 35-45 tons (including the Adder, Battle Cobra, Grendel, Shadow Cat, Pouncer, and Cougar). -capabilities: The Viper is built on a lightweight Endo Steel chassis and powered by a weight saving 320 XL engine that propels the Viper to a top speed of 129.6 km/h. The Viper augments its impressive ground speed with eight jump jets that allow it to jump up to a distance of two hundred and forty meters. The Viper has seven tons of Ferro-Fibrous armor to absorb any damage from shots that are lucky enough to strike it and has eight and a half tons of podspace for its weapons payload. +capabilities: The Viper is built on a lightweight Endo Steel chassis and powered by a weight saving 320 XL engine that propels the Viper to a top speed of 129.6 km/h. The Viper augments its impressive ground speed with eight jump jets that allow it to jump up to a distance of two hundred and forty meters. The Viper has seven tons of Ferro-Fibrous armor to absorb any damage from shots that are lucky enough to strike it and has eight and a half tons of pod space for its weapons payload. history:Clan Ghost Bear came into possession of the design in 3002 when they traded several production runs of Executioner OmniMechs for the design and production facilities on Shadow. Rather than trial for land rights to Shadow, and become embroiled in the internecine struggles of the Fire Mandrills, the Bears restructured the facility, making the lines modular, and relocated production to Strana Mechty - this modular technology proved very useful when the Ghost Bears migrated back to the Inner Sphere in the late 3050s. Surprisingly, the Bears left their first modular production facility on Strana Mechty. Production continued on Strana Mechty for Clan Ghost Bear until the mid-3060s when the Hell's Horses won the production rights and the facility (and then promptly lost the facility to Clan Ice Hellion in 3068). In addition to the manufacturing plant on Strana Mechty, at least one other planet in the Homeworlds was home to a manufacturing line producing Vipers; in 3071 Clan Goliath Scorpion captured a Viper factory from Clan Coyote on Delios, although it is unknown if the planet survived the Wars of Reaving, Goliath Scorpion Abjurement and the subsequent abandonment of the planet by the Coyotes and Cloud Cobras. manufacturer:Upsilon Plant 2J, Dominion Facility Kappa-5 diff --git a/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 8/Dragonfly (Viper) T.mtf b/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 8/Dragonfly (Viper) T.mtf index a131176c0bc..bbf6599a60e 100644 --- a/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 8/Dragonfly (Viper) T.mtf +++ b/megamek/data/mechfiles/mechs/Rec Guides ilClan/Vol 8/Dragonfly (Viper) T.mtf @@ -159,7 +159,7 @@ Jump Jet overview:The Viper is a fast, highly-maneuverable medium OmniMech originally designed by Clan Fire Mandrill on Shadow. Codenamed the Dragonfly by the Inner Sphere forces that first encountered this small but fierce OmniMech, the name stuck because of its ability to move swiftly over the battlefield. The Viper is fast and well-armored, but significantly under-gunned compared with other Clan OmniMechs massing 35-45 tons (including the Adder, Battle Cobra, Grendel, Shadow Cat, Pouncer, and Cougar). -capabilities: The Viper is built on a lightweight Endo Steel chassis and powered by a weight saving 320 XL engine that propels the Viper to a top speed of 129.6 km/h. The Viper augments its impressive ground speed with eight jump jets that allow it to jump up to a distance of two hundred and forty meters. The Viper has seven tons of Ferro-Fibrous armor to absorb any damage from shots that are lucky enough to strike it and has eight and a half tons of podspace for its weapons payload. +capabilities: The Viper is built on a lightweight Endo Steel chassis and powered by a weight saving 320 XL engine that propels the Viper to a top speed of 129.6 km/h. The Viper augments its impressive ground speed with eight jump jets that allow it to jump up to a distance of two hundred and forty meters. The Viper has seven tons of Ferro-Fibrous armor to absorb any damage from shots that are lucky enough to strike it and has eight and a half tons of pod space for its weapons payload. history:Clan Ghost Bear came into possession of the design in 3002 when they traded several production runs of Executioner OmniMechs for the design and production facilities on Shadow. Rather than trial for land rights to Shadow, and become embroiled in the internecine struggles of the Fire Mandrills, the Bears restructured the facility, making the lines modular, and relocated production to Strana Mechty - this modular technology proved very useful when the Ghost Bears migrated back to the Inner Sphere in the late 3050s. Surprisingly, the Bears left their first modular production facility on Strana Mechty. Production continued on Strana Mechty for Clan Ghost Bear until the mid-3060s when the Hell's Horses won the production rights and the facility (and then promptly lost the facility to Clan Ice Hellion in 3068). In addition to the manufacturing plant on Strana Mechty, at least one other planet in the Homeworlds was home to a manufacturing line producing Vipers; in 3071 Clan Goliath Scorpion captured a Viper factory from Clan Coyote on Delios, although it is unknown if the planet survived the Wars of Reaving, Goliath Scorpion Abjurement and the subsequent abandonment of the planet by the Coyotes and Cloud Cobras. manufacturer:Upsilon Plant 2J, Dominion Facility Kappa-5 diff --git a/megamek/data/mechfiles/mechs/Shrapnel/Vol 4/SuburbanMech UM-R100.mtf b/megamek/data/mechfiles/mechs/Shrapnel/Vol 4/SuburbanMech UM-R100.mtf index e279fd92cd5..97b1106f356 100644 --- a/megamek/data/mechfiles/mechs/Shrapnel/Vol 4/SuburbanMech UM-R100.mtf +++ b/megamek/data/mechfiles/mechs/Shrapnel/Vol 4/SuburbanMech UM-R100.mtf @@ -162,7 +162,7 @@ capabilities:This was achieved by starting with a cheap, easily-produced chassis deployment:A variant proposed during the Clan Invasion but ultimately never put into production because of high cost and the Clan Invasion, this SuburbanMech would have used a 120-rated engine to reach a running speed of 64km/h and power four jump jets. Ten double heat sinks were to be installed. The PPC would be swapped for an extended-range model but the rest of the weaponry matched the UM-R90 variant. Six and a half tons of armor would be carried. -history:Large numbers of UrbanMechs were produced by Orguss Industries from 2675 until the destruction of their assembly lines. The UrbanMech reentered production at the Betelgeuse facility of Hellespont Industrials during the Jihad, and continued to be manufactured up through 3149. As such, UrbanMechs could be found in all of the armies of the Successor States. However most military leaders saw the slow little 'Mech as a liability, confining their stockpiles to garrison duty or stripping them of parts. This dismissive attitude towards the UrbanMech saved it from the ravages of the Succession Wars and ensured its continued use into the thirty-first century. The Capellan Confederation remained the largest and only user of UrbanMechs to actually deploy them for front-line duty, a result of the devastation of the Fourth Succession War and their desperation for any 'Mech to replenish their losses. The Confederation Reserve Cavalry and Capellan Defense Force had the lion's share of UrbanMechs, followed by the Tikonov Republican Guard and St. Ives Armored Cavalry; outside the Confederation the Federated Suns' Capellan March Militia fielded the largest number of UrbanMechs due to the fact it was composed of large amounts of captured Capellan equipment. Its prominence within the Confederation meant the UrbanMech was among those 'Mechs within the CCAF to receive upgrades following the recovery of lostech; the other States followed suit with much less priority over improving other 'Mechs. Despite this the sheer costs necessary to replace the UrbanMech's engine and increase its top speed meant even the Confederation limited their refit packages to improving the weapons and armor only. A testament to the desperation of the Word of Blake Jihad, Hellespont Industrials would reactivate a shuttered production facility on Betelgeuse to produce the UrbanMech alongside primitive "retrotech" designs for material starved Capellan garrison forces. This plant would maintain production of the UrbanMech in a steadily increasing volume of configurations throughout the Dark Age Era as the CCAF secretly expanded before it waged war against the Republic of the Sphere. Rather than dramatic and expensive enhancements, Hellespont's new variants retain the venerable design's low ground speed urban combat focus and can be applied as refits as readily as new production. +history:Large numbers of UrbanMechs were produced by Orgus Industries from 2675 until the destruction of their assembly lines. The UrbanMech reentered production at the Betelgeuse facility of Hellespont Industrials during the Jihad, and continued to be manufactured up through 3149. As such, UrbanMechs could be found in all of the armies of the Successor States. However most military leaders saw the slow little 'Mech as a liability, confining their stockpiles to garrison duty or stripping them of parts. This dismissive attitude towards the UrbanMech saved it from the ravages of the Succession Wars and ensured its continued use into the thirty-first century. The Capellan Confederation remained the largest and only user of UrbanMechs to actually deploy them for front-line duty, a result of the devastation of the Fourth Succession War and their desperation for any 'Mech to replenish their losses. The Confederation Reserve Cavalry and Capellan Defense Force had the lion's share of UrbanMechs, followed by the Tikonov Republican Guard and St. Ives Armored Cavalry; outside the Confederation the Federated Suns' Capellan March Militia fielded the largest number of UrbanMechs due to the fact it was composed of large amounts of captured Capellan equipment. Its prominence within the Confederation meant the UrbanMech was among those 'Mechs within the CCAF to receive upgrades following the recovery of lostech; the other States followed suit with much less priority over improving other 'Mechs. Despite this the sheer costs necessary to replace the UrbanMech's engine and increase its top speed meant even the Confederation limited their refit packages to improving the weapons and armor only. A testament to the desperation of the Word of Blake Jihad, Hellespont Industrials would reactivate a shuttered production facility on Betelgeuse to produce the UrbanMech alongside primitive "retrotech" designs for material starved Capellan garrison forces. This plant would maintain production of the UrbanMech in a steadily increasing volume of configurations throughout the Dark Age Era as the CCAF secretly expanded before it waged war against the Republic of the Sphere. Rather than dramatic and expensive enhancements, Hellespont's new variants retain the venerable design's low ground speed urban combat focus and can be applied as refits as readily as new production. manufacturer:Phoenix Heavy Industries,Refit primaryfactory:Ashkum,Various diff --git a/megamek/data/mechfiles/mechs/Shrapnel/Vol 4/SuburbanMech UM-R90.mtf b/megamek/data/mechfiles/mechs/Shrapnel/Vol 4/SuburbanMech UM-R90.mtf index ae8fa70088c..6294b0915c7 100644 --- a/megamek/data/mechfiles/mechs/Shrapnel/Vol 4/SuburbanMech UM-R90.mtf +++ b/megamek/data/mechfiles/mechs/Shrapnel/Vol 4/SuburbanMech UM-R90.mtf @@ -163,7 +163,7 @@ capabilities:This was achieved by starting with a cheap, easily-produced chassis deployment:This redesign was created by Hanse Davion as a way to reduce the power of Michael Hasek-Davion by fixing AFFS supply lines. The SuburbanMech is visually identical to an UrbanMech but has a larger engine that allows it to reach 54km/h. The autocannon is replaced with a single PPC and two Medium Lasers. The small laser remains in place, but jump range has been increased to 90 meters. Thirteen single heat sinks struggle to dissipate the heat of an alpha strike. -history:Large numbers of UrbanMechs were produced by Orguss Industries from 2675 until the destruction of their assembly lines. The UrbanMech reentered production at the Betelgeuse facility of Hellespont Industrials during the Jihad, and continued to be manufactured up through 3149. As such, UrbanMechs could be found in all of the armies of the Successor States. However most military leaders saw the slow little 'Mech as a liability, confining their stockpiles to garrison duty or stripping them of parts. This dismissive attitude towards the UrbanMech saved it from the ravages of the Succession Wars and ensured its continued use into the thirty-first century. The Capellan Confederation remained the largest and only user of UrbanMechs to actually deploy them for front-line duty, a result of the devastation of the Fourth Succession War and their desperation for any 'Mech to replenish their losses. The Confederation Reserve Cavalry and Capellan Defense Force had the lion's share of UrbanMechs, followed by the Tikonov Republican Guard and St. Ives Armored Cavalry; outside the Confederation the Federated Suns' Capellan March Militia fielded the largest number of UrbanMechs due to the fact it was composed of large amounts of captured Capellan equipment. Its prominence within the Confederation meant the UrbanMech was among those 'Mechs within the CCAF to receive upgrades following the recovery of lostech; the other States followed suit with much less priority over improving other 'Mechs. Despite this the sheer costs necessary to replace the UrbanMech's engine and increase its top speed meant even the Confederation limited their refit packages to improving the weapons and armor only. A testament to the desperation of the Word of Blake Jihad, Hellespont Industrials would reactivate a shuttered production facility on Betelgeuse to produce the UrbanMech alongside primitive "retrotech" designs for material starved Capellan garrison forces. This plant would maintain production of the UrbanMech in a steadily increasing volume of configurations throughout the Dark Age Era as the CCAF secretly expanded before it waged war against the Republic of the Sphere. Rather than dramatic and expensive enhancements, Hellespont's new variants retain the venerable design's low ground speed urban combat focus and can be applied as refits as readily as new production. +history:Large numbers of UrbanMechs were produced by Orgus Industries from 2675 until the destruction of their assembly lines. The UrbanMech reentered production at the Betelgeuse facility of Hellespont Industrials during the Jihad, and continued to be manufactured up through 3149. As such, UrbanMechs could be found in all of the armies of the Successor States. However most military leaders saw the slow little 'Mech as a liability, confining their stockpiles to garrison duty or stripping them of parts. This dismissive attitude towards the UrbanMech saved it from the ravages of the Succession Wars and ensured its continued use into the thirty-first century. The Capellan Confederation remained the largest and only user of UrbanMechs to actually deploy them for front-line duty, a result of the devastation of the Fourth Succession War and their desperation for any 'Mech to replenish their losses. The Confederation Reserve Cavalry and Capellan Defense Force had the lion's share of UrbanMechs, followed by the Tikonov Republican Guard and St. Ives Armored Cavalry; outside the Confederation the Federated Suns' Capellan March Militia fielded the largest number of UrbanMechs due to the fact it was composed of large amounts of captured Capellan equipment. Its prominence within the Confederation meant the UrbanMech was among those 'Mechs within the CCAF to receive upgrades following the recovery of lostech; the other States followed suit with much less priority over improving other 'Mechs. Despite this the sheer costs necessary to replace the UrbanMech's engine and increase its top speed meant even the Confederation limited their refit packages to improving the weapons and armor only. A testament to the desperation of the Word of Blake Jihad, Hellespont Industrials would reactivate a shuttered production facility on Betelgeuse to produce the UrbanMech alongside primitive "retrotech" designs for material starved Capellan garrison forces. This plant would maintain production of the UrbanMech in a steadily increasing volume of configurations throughout the Dark Age Era as the CCAF secretly expanded before it waged war against the Republic of the Sphere. Rather than dramatic and expensive enhancements, Hellespont's new variants retain the venerable design's low ground speed urban combat focus and can be applied as refits as readily as new production. manufacturer:Phoenix Heavy Industries,Refit primaryfactory:Ashkum,Various diff --git a/megamek/data/mechfiles/mechs/Starterpack Sword and Dragon/Black Knight BL-10-KNT Ross.mtf b/megamek/data/mechfiles/mechs/Starterpack Sword and Dragon/Black Knight BL-10-KNT Ross.mtf index 898f3830765..1c9959824b1 100644 --- a/megamek/data/mechfiles/mechs/Starterpack Sword and Dragon/Black Knight BL-10-KNT Ross.mtf +++ b/megamek/data/mechfiles/mechs/Starterpack Sword and Dragon/Black Knight BL-10-KNT Ross.mtf @@ -159,7 +159,7 @@ Ferro-Fibrous overview:The Black Knight was introduced in 2578 both as a front-line combatant and as a command BattleMech at the company and battalion level for the Star League Defense Force. -capabilities:Thirteen tons of armor protection on an Endo Steel frame allows the Black Knight to withstand significant punishment. The biggest disadvantage of the design is its challenging heat curve, though the fact that it mounts twenty heat sinks ensures that the Black Knight can still disperse a significant amount of heat produced by its weapons. However, if the 'Mech is involved in a prolonged combat situation, a less experienced MechWarrior who is not competent at heat management may be in trouble. The Black Knight's superior communications equipment allowed it to readily coordinate a whole company of 'Mechs at the same time, as well as link together the command frequencies of an entire parent regiment and connect with orbital support satellites. Improved construction materials provided the Black Knight with a light but sturdy chassis capable of carrying more weaponry and armor for less weight. With the type and amount of weapons carried by the 'Mech, the only challenge the Black Knight faces is heat management. +capabilities:The biggest disadvantage of the design is its challenging heat curve, though the fact that it mounts fifteen double heat sinks ensures that the Black Knight can still disperse a significant amount of heat produced by its weapons. However, if the 'Mech is involved in a prolonged combat situation, a less experienced MechWarrior who is not competent at heat management may be in trouble. The Black Knight's superior communications equipment allowed it to readily coordinate a whole company of 'Mechs at the same time, as well as link together the command frequencies of an entire parent regiment and connect with orbital support satellites. Improved construction materials provided the Black Knight with a light but sturdy chassis capable of carrying more weaponry and armor for less weight. With the type and amount of weapons carried by the 'Mech, the only challenge the Black Knight faces is heat management. deployment:Given to Ross McKinnon upon his father's retirement in 3051, the family 'Mech continued to be upgraded with the latest technology. By the FedCom Civil War the right arm and torso weaponry of Ross's 'Mech was upgraded to extended range models, with the triple strength myomers and hatchet retained. The use of production grade ferro-fibrous and double heat sinks, along with downgrading the large lasers to medium pulse lasers and the left arm medium for an ER Small Laser, freed up enough weight for a Targeting Computer to be added. diff --git a/megamek/data/mechfiles/mechs/Tukayyid/Black Knight BL-9-KNT.mtf b/megamek/data/mechfiles/mechs/Tukayyid/Black Knight BL-9-KNT.mtf index f572ea09a47..89adc78a335 100644 --- a/megamek/data/mechfiles/mechs/Tukayyid/Black Knight BL-9-KNT.mtf +++ b/megamek/data/mechfiles/mechs/Tukayyid/Black Knight BL-9-KNT.mtf @@ -160,7 +160,7 @@ IS Endo Steel overview:The Black Knight was introduced in 2578 both as a front-line combatant and as a command BattleMech at the company and battalion level for the Star League Defense Force. -capabilities:Thirteen tons of armor protection on an Endo Steel frame allows the Black Knight to withstand significant punishment. The biggest disadvantage of the design is its challenging heat curve, though the fact that it mounts twenty heat sinks ensures that the Black Knight can still disperse a significant amount of heat produced by its weapons. However, if the 'Mech is involved in a prolonged combat situation, a less experienced MechWarrior who is not competent at heat management may be in trouble. The Black Knight's superior communications equipment allowed it to readily coordinate a whole company of 'Mechs at the same time, as well as link together the command frequencies of an entire parent regiment and connect with orbital support satellites. Improved construction materials provided the Black Knight with a light but sturdy chassis capable of carrying more weaponry and armor for less weight. With the type and amount of weapons carried by the 'Mech, the only challenge the Black Knight faces is heat management. +capabilities:Thirteen tons of armor protection on an Endo Steel frame allows the Black Knight to withstand significant punishment. The biggest disadvantage of the design is its challenging heat curve, though the fact that it mounts fifteen double heat sinks ensures that the Black Knight can still disperse a significant amount of heat produced by its weapons. However, if the 'Mech is involved in a prolonged combat situation, a less experienced MechWarrior who is not competent at heat management may be in trouble. The Black Knight's superior communications equipment allowed it to readily coordinate a whole company of 'Mechs at the same time, as well as link together the command frequencies of an entire parent regiment and connect with orbital support satellites. Improved construction materials provided the Black Knight with a light but sturdy chassis capable of carrying more weaponry and armor for less weight. With the type and amount of weapons carried by the 'Mech, the only challenge the Black Knight faces is heat management. deployment:One of the so-called "Clanbuster" refits developed by ComStar in the lead-up to the Battle of Tukayyid, this variant has been equipped with an Vlar 300 XL engine, allowing it to mount an upgraded and heavier weapons load. The PPC was upgraded to a Magna Sunspot ER PPC, the medium lasers switched to Aberdovey Medium Pulse Lasers, an Aberdovey Large Pulse Laser added to the center torso, and both the small laser and Beagle Active Probe removed. To handle the heavier heat load, the heat sinks were upgraded to double strength versions. In addition, for close-in work, the Black Knight carries long-sword shaped 5-ton Hatchet in its left hand, allowing it to make devastating physical attacks. diff --git a/megamek/data/mechfiles/mechs/Turning Points/HTP Misery/Ostroc OSR-2C Michi.mtf b/megamek/data/mechfiles/mechs/Turning Points/HTP Misery/Ostroc OSR-2C Michi.mtf index 760f9061218..3a0546a6545 100644 --- a/megamek/data/mechfiles/mechs/Turning Points/HTP Misery/Ostroc OSR-2C Michi.mtf +++ b/megamek/data/mechfiles/mechs/Turning Points/HTP Misery/Ostroc OSR-2C Michi.mtf @@ -143,7 +143,7 @@ capabilities:Its unique walker/pod profile, later seen in the Stalker and Maraud deployment:Unknown -history:The best-known of Ostman Industries' Ost Class of 'Mechs, the Ostroc debuted in 2511 and proved so successful in this role production continued for approximately 200 years. While a quality 'Mech, the low production capacity of Ostman Industries made the Ostroc a rarity; indeed the company licensed their other Ost 'Mechs out to Kong Interstellar just to maintain their rate of production, and the majority of those produced were assigned garrison duties within the Terran Hegemony. Still, the 'Mech saw action in every major conflict of the Star League, especially towards the end in the civil war and subsequent First Succession War. The destruction of Ostman Industries meant an end to any new Ostrocs, although all sides of the Succession Wars continued to field these 'Mechs in combat, particularly the Draconis Combine. It was because of the small number and wide dispersal of surviving Ostrocs that the design was largely passed over while others were being updated after the Helm Memory Core discovery. A major revitalization of the design took place within the Capellan Confederation after the Clan Invasion. Having largely rebuilt their forces after the previous decades' setbacks, the Strategios wanted to update the ancient 'Mech, but rather than reverse-engineering the original they ordered all Capellan 'Mech manufacturers to submit bids for a replacement. Ceres Metals was the only one to send in a proposal which matched exactly what they wanted and won the contract, completing the first production run in January 3067. Versions of these new Ostrocs also started showing up in the Taurian Concordat and Circinus Federation, a result of espionage according to Capellan charges. +history:The best-known of Ostmann Industries' Ost Class of 'Mechs, the Ostroc debuted in 2511 and proved so successful in this role production continued for approximately 200 years. While a quality 'Mech, the low production capacity of Ostmann Industries made the Ostroc a rarity; indeed the company licensed their other Ost 'Mechs out to Kong Interstellar just to maintain their rate of production, and the majority of those produced were assigned garrison duties within the Terran Hegemony. Still, the 'Mech saw action in every major conflict of the Star League, especially towards the end in the civil war and subsequent First Succession War. The destruction of Ostmann Industries meant an end to any new Ostrocs, although all sides of the Succession Wars continued to field these 'Mechs in combat, particularly the Draconis Combine. It was because of the small number and wide dispersal of surviving Ostrocs that the design was largely passed over while others were being updated after the Helm Memory Core discovery. A major revitalization of the design took place within the Capellan Confederation after the Clan Invasion. Having largely rebuilt their forces after the previous decades' setbacks, the Strategios wanted to update the ancient 'Mech, but rather than reverse-engineering the original they ordered all Capellan 'Mech manufacturers to submit bids for a replacement. Ceres Metals was the only one to send in a proposal which matched exactly what they wanted and won the contract, completing the first production run in January 3067. Versions of these new Ostrocs also started showing up in the Taurian Concordat and Circinus Federation, a result of espionage according to Capellan charges. manufacturer:Field Refit primaryfactory:Various diff --git a/megamek/data/mechfiles/mechs/Turning Points/JTP Dieron/Kodiak Cale.mtf b/megamek/data/mechfiles/mechs/Turning Points/JTP Dieron/Kodiak Cale.mtf index 3949b7c3f73..62a0cdcbdbc 100644 --- a/megamek/data/mechfiles/mechs/Turning Points/JTP Dieron/Kodiak Cale.mtf +++ b/megamek/data/mechfiles/mechs/Turning Points/JTP Dieron/Kodiak Cale.mtf @@ -145,7 +145,7 @@ Foot Actuator CLDouble Heat Sink CLDouble Heat Sink -capabilities:Though not taken to the same extreme as other Clan Totem 'Mechs, the Kodiak does epitomize the Ghost Bears' method of warfare, combining an impressive defensive platform with surprising amounts of speed and firepower. Its massive 400-rated XL Engine propels the Kodiak to a maximum speed of 64.8 km/h, while seventeen and a half tons of Compound 12A2 gives it impressive armor protection. Though it mounts an incredible amount of firepower, even the use of twenty double heat sinks cannot prevent overheating problems when they are all fired simultaneously, though most MechWarriors learn to use their weapons sparingly and love the 'Mech's ability to deliver a massive knockout punch. The Kodiak incorporates the Garret L20 as its communications system, and uses the RCA Instatrack Mark IX for targeting, however the "claws" mounted on both of its arms are purely aesthetic. +capabilities:Though not taken to the same extreme as other Clan Totem 'Mechs, the Kodiak does epitomize the Ghost Bears' method of warfare, combining an impressive defensive platform with surprising amounts of speed and firepower. Its massive 400-rated XL Engine propels the Kodiak to a maximum speed of 64.8 km/h, while seventeen and a half tons of Compound 12A2 gives it impressive armor protection. Though it mounts an incredible amount of firepower, even the use of twenty double heat sinks cannot prevent overheating problems when they are all fired simultaneously, though most MechWarriors learn to use their weapons sparingly and love the 'Mech's ability to deliver a massive knockout punch. The Kodiak incorporates the Garret L20 as its communications system, and uses the RCA Instatrac Mark IX for targeting, however the "claws" mounted on both of its arms are purely aesthetic. deployment:The Mech of the 2nd Dieron Regulars' commander, Tai-sa Cale Schultz-Tanaka, the Kodiak Cale was recovered from a battlefield on Dieron and re-equipped with Inner Sphere and Clan technologies. Keeping the standard Clan Endo-Steel chassis and double heat sinks, techs replaced the XL engine with a standard unit. This reduced the 'Mech's top speed to 54 km/h, but increased survivability. Most of the Clan weaponry was also removed: Only a trio of Clan ER Medium Lasers in the left arm and a pair of Streak SRM 6 launchers in the left torso remain. The Kodiak Cale uses an Autocannon/10 and Heavy PPC for its main hitting power. These are backed up by the Clan weapons and a pair of Inner Sphere ER Medium Lasers and a pair of Inner Sphere Medium Lasers. The most important addition to the Cale version is the electronics suite: A Beagle Active Probe in the right torso spots enemy forces, while a C3 Master computer in the left torso allows the Kodiak Cale to feed targeting data to supporting units. diff --git a/megamek/data/mechfiles/mechs/WoR Supplemental/Dragonfly (Viper) Z.mtf b/megamek/data/mechfiles/mechs/WoR Supplemental/Dragonfly (Viper) Z.mtf index 8fb802bae43..c1ed332bb7f 100644 --- a/megamek/data/mechfiles/mechs/WoR Supplemental/Dragonfly (Viper) Z.mtf +++ b/megamek/data/mechfiles/mechs/WoR Supplemental/Dragonfly (Viper) Z.mtf @@ -159,7 +159,7 @@ Jump Jet overview:The Viper is a fast, highly-maneuverable medium OmniMech originally designed by Clan Fire Mandrill on Shadow. Codenamed the Dragonfly by the Inner Sphere forces that first encountered this small but fierce OmniMech, the name stuck because of its ability to move swiftly over the battlefield. The Viper is fast and well-armored, but significantly under-gunned compared with other Clan OmniMechs massing 35-45 tons (including the Adder, Battle Cobra, Grendel, Shadow Cat, Pouncer, and Cougar). -capabilities:This variant of the Viper is equipped with a Nova CEWS to offset the low skill levels of The Society's MechWarriors. The right arm mounts a pair of Improved Heavy Medium Lasers, while the left arm mounts a single Improved Heavy Medium Laser and a single iATM 3. A Light TAG system in the right torso allows the Viper Z to designate artillery strikes, and a Laser AMS provides additional protection against missile fire. The Viper is built on a lightweight Endo Steel chassis and powered by a weight saving 320 XL engine that propels the Viper to a top speed of 129.6 km/h. The Viper augments its impressive ground speed with eight jump jets that allow it to jump up to a distance of two hundred and forty meters. The Viper has seven tons of Ferro-Fibrous armor to absorb any damage from shots that are lucky enough to strike it and has eight and a half tons of podspace for its weapons payload. +capabilities:This variant of the Viper is equipped with a Nova CEWS to offset the low skill levels of The Society's MechWarriors. The right arm mounts a pair of Improved Heavy Medium Lasers, while the left arm mounts a single Improved Heavy Medium Laser and a single iATM 3. A Light TAG system in the right torso allows the Viper Z to designate artillery strikes, and a Laser AMS provides additional protection against missile fire. The Viper is built on a lightweight Endo Steel chassis and powered by a weight saving 320 XL engine that propels the Viper to a top speed of 129.6 km/h. The Viper augments its impressive ground speed with eight jump jets that allow it to jump up to a distance of two hundred and forty meters. The Viper has seven tons of Ferro-Fibrous armor to absorb any damage from shots that are lucky enough to strike it and has eight and a half tons of pod space for its weapons payload. history:Clan Ghost Bear came into possession of the design in 3002 when they traded several production runs of Executioner OmniMechs for the design and production facilities on Shadow. Rather than trial for land rights to Shadow, and become embroiled in the internecine struggles of the Fire Mandrills, the Bears restructured the facility, making the lines modular, and relocated production to Strana Mechty - this modular technology proved very useful when the Ghost Bears migrated back to the Inner Sphere in the late 3050s. Surprisingly, the Bears left their first modular production facility on Strana Mechty. Production continued on Strana Mechty for Clan Ghost Bear until the mid-3060s when the Hell's Horses won the production rights and the facility (and then promptly lost the facility to Clan Ice Hellion in 3068). In addition to the manufacturing plant on Strana Mechty, at least one other planet in the Homeworlds was home to a manufacturing line producing Vipers; in 3071 Clan Goliath Scorpion captured a Viper factory from Clan Coyote on Delios, although it is unknown if the planet survived the Wars of Reaving, Goliath Scorpion Abjurement and the subsequent abandonment of the planet by the Coyotes and Cloud Cobras. manufacturer:Upsilon Plant 2J, Dominion Facility Kappa-5 diff --git a/megamek/data/mechfiles/mechs/Wolf and Blake/Griffin GRF-6S Francine II.mtf b/megamek/data/mechfiles/mechs/Wolf and Blake/Griffin GRF-6S Francine II.mtf index cc931758d12..67d0489646f 100644 --- a/megamek/data/mechfiles/mechs/Wolf and Blake/Griffin GRF-6S Francine II.mtf +++ b/megamek/data/mechfiles/mechs/Wolf and Blake/Griffin GRF-6S Francine II.mtf @@ -174,4 +174,4 @@ systemmanufacturer:ENGINE:Defiance 275 Light Engine systemmanufacturer:ARMOR:ArcShield Reflective systemmanufacturer:JUMPJET:Chilton 950 systemmanufacturer:COMMUNICATIONS:Neil 6000 -systemmanufacturer:TARGETING:RCA Instatrack Mk X +systemmanufacturer:TARGETING:RCA Instatrac Mk X diff --git a/megamek/data/mechfiles/mechs/Wolf and Blake/Griffin GRF-6S Francine.mtf b/megamek/data/mechfiles/mechs/Wolf and Blake/Griffin GRF-6S Francine.mtf index 4f05a0a6223..6af5ef8ae54 100644 --- a/megamek/data/mechfiles/mechs/Wolf and Blake/Griffin GRF-6S Francine.mtf +++ b/megamek/data/mechfiles/mechs/Wolf and Blake/Griffin GRF-6S Francine.mtf @@ -175,4 +175,4 @@ systemmanufacturer:ENGINE:Defiance 275 Light Engine systemmanufacturer:ARMOR:Starshield A Light Ferro-Fibrous armor with CASE systemmanufacturer:JUMPJET:Chilton 950 systemmanufacturer:COMMUNICATIONS:Neil 6000 -systemmanufacturer:TARGETING:RCA Instatrack Mk X +systemmanufacturer:TARGETING:RCA Instatrac Mk X diff --git a/megamek/data/mechfiles/mechs/XTRs/Primitives II/Wasp WSP-1.mtf b/megamek/data/mechfiles/mechs/XTRs/Primitives II/Wasp WSP-1.mtf index ed4b5f65d69..982a761ef8c 100644 --- a/megamek/data/mechfiles/mechs/XTRs/Primitives II/Wasp WSP-1.mtf +++ b/megamek/data/mechfiles/mechs/XTRs/Primitives II/Wasp WSP-1.mtf @@ -169,5 +169,5 @@ systemmanufacturer:CHASSIS:1A Type 3 systemmanufacturer:ENGINE:Unknown systemmanufacturer:ARMOR:Unknown systemmanufacturer:JUMPJET:Unknown -systemmanufacturer:COMMUNICATIONS:Duotech 65 +systemmanufacturer:COMMUNICATIONS:Duoteck 65 systemmanufacturer:TARGETING:RadCom TXX diff --git a/megamek/data/mechfiles/mechs/XTRs/Republic II/UrbanMech UM-R93.mtf b/megamek/data/mechfiles/mechs/XTRs/Republic II/UrbanMech UM-R93.mtf index 9ae1e3115ee..c4bdbff0d63 100644 --- a/megamek/data/mechfiles/mechs/XTRs/Republic II/UrbanMech UM-R93.mtf +++ b/megamek/data/mechfiles/mechs/XTRs/Republic II/UrbanMech UM-R93.mtf @@ -155,7 +155,7 @@ Foot Actuator overview:The UrbanMech was designed for just what its name suggests: urban combat and defense. capabilities:This was achieved by starting with a cheap, easily-produced chassis, giving it six tons of Durallex armor to rival the protection found on many medium-weight BattleMechs, and mounting a pair of Pitban 6000 jump jets for a jumping distance of 60 meters. The trade-off was that it could only mount the miserable Leenex 60 engine, making the UrbanMech the slowest light 'Mech in existence with a cruising speed of 21.6 km/h and top speed of only 32.4 km/h. This was a severe disadvantage if the 'Mech attempted to fight in open country - something for only the foolish or desperate - but off-set by the fact that fighting in the close confines of a Star League city left little room to maneuver anyways and the UrbanMech's low profile made it difficult to target. Thus the 'Mech was primarily used for fighting guerrillas and other light 'Mechs in an urban environment, an arena where it also achieved some success fighting medium and even heavy-weight 'Mechs. Standard tactics for an UrbanMech lance was to split up into its constituent parts and occupy various buildings in order to snipe the enemy before falling back to the next defensive line. deployment:First appeared in 3130, this Capellan Confederation Dark Age Era upgrade of the UrbanMech carries a Plasma Rifle, ER Medium Laser and ER Small Laser. Additionally, it carries 12 tons of Hardened Armor, which, while making it as tough as many Medium 'Mechs, reduces its already slow speed even further. -history:Large numbers of UrbanMechs were produced by Orguss Industries from 2675 until the destruction of their assembly lines. The UrbanMech reentered production at the Betelgeuse facility of Hellespont Industrials during the Jihad, and continued to be manufactured up through 3149. As such, UrbanMechs could be found in all of the armies of the Successor States. However most military leaders saw the slow little 'Mech as a liability, confining their stockpiles to garrison duty or stripping them of parts. This dismissive attitude towards the UrbanMech saved it from the ravages of the Succession Wars and ensured its continued use into the thirty-first century. The Capellan Confederation remained the largest and only user of UrbanMechs to actually deploy them for front-line duty, a result of the devastation of the Fourth Succession War and their desperation for any 'Mech to replenish their losses. The Confederation Reserve Cavalry and Capellan Defense Force had the lion's share of UrbanMechs, followed by the Tikonov Republican Guard and St. Ives Armored Cavalry; outside the Confederation the Federated Suns' Capellan March Militia fielded the largest number of UrbanMechs due to the fact it was composed of large amounts of captured Capellan equipment. Its prominence within the Confederation meant the UrbanMech was among those 'Mechs within the CCAF to receive upgrades following the recovery of lostech; the other States followed suit with much less priority over improving other 'Mechs. Despite this the sheer costs necessary to replace the UrbanMech's engine and increase its top speed meant even the Confederation limited their refit packages to improving the weapons and armor only. A testament to the desperation of the Word of Blake Jihad, Hellespont Industrials would reactivate a shuttered production facility on Betelgeuse to produce the UrbanMech alongside primitive "retrotech" designs for material starved Capellan garrison forces. This plant would maintain production of the UrbanMech in a steadily increasing volume of configurations throughout the Dark Age Era as the CCAF secretly expanded before it waged war against the Republic of the Sphere. Rather than dramatic and expensive enhancements, Hellespont's new variants retain the venerable design's low ground speed urban combat focus and can be applied as refits as readily as new production. +history:Large numbers of UrbanMechs were produced by Orgus Industries from 2675 until the destruction of their assembly lines. The UrbanMech reentered production at the Betelgeuse facility of Hellespont Industrials during the Jihad, and continued to be manufactured up through 3149. As such, UrbanMechs could be found in all of the armies of the Successor States. However most military leaders saw the slow little 'Mech as a liability, confining their stockpiles to garrison duty or stripping them of parts. This dismissive attitude towards the UrbanMech saved it from the ravages of the Succession Wars and ensured its continued use into the thirty-first century. The Capellan Confederation remained the largest and only user of UrbanMechs to actually deploy them for front-line duty, a result of the devastation of the Fourth Succession War and their desperation for any 'Mech to replenish their losses. The Confederation Reserve Cavalry and Capellan Defense Force had the lion's share of UrbanMechs, followed by the Tikonov Republican Guard and St. Ives Armored Cavalry; outside the Confederation the Federated Suns' Capellan March Militia fielded the largest number of UrbanMechs due to the fact it was composed of large amounts of captured Capellan equipment. Its prominence within the Confederation meant the UrbanMech was among those 'Mechs within the CCAF to receive upgrades following the recovery of lostech; the other States followed suit with much less priority over improving other 'Mechs. Despite this the sheer costs necessary to replace the UrbanMech's engine and increase its top speed meant even the Confederation limited their refit packages to improving the weapons and armor only. A testament to the desperation of the Word of Blake Jihad, Hellespont Industrials would reactivate a shuttered production facility on Betelgeuse to produce the UrbanMech alongside primitive "retrotech" designs for material starved Capellan garrison forces. This plant would maintain production of the UrbanMech in a steadily increasing volume of configurations throughout the Dark Age Era as the CCAF secretly expanded before it waged war against the Republic of the Sphere. Rather than dramatic and expensive enhancements, Hellespont's new variants retain the venerable design's low ground speed urban combat focus and can be applied as refits as readily as new production. manufacturer:Hellespont Industrials primaryfactory:Betelgeuse systemmanufacturer:CHASSIS:Republic-R diff --git a/megamek/data/mechfiles/mechs/XTRs/Succession Wars/Super Wasp WSP-2A-X.mtf b/megamek/data/mechfiles/mechs/XTRs/Succession Wars/Super Wasp WSP-2A-X.mtf index ef54c8fe3fd..6849e98d165 100644 --- a/megamek/data/mechfiles/mechs/XTRs/Succession Wars/Super Wasp WSP-2A-X.mtf +++ b/megamek/data/mechfiles/mechs/XTRs/Succession Wars/Super Wasp WSP-2A-X.mtf @@ -168,6 +168,6 @@ systemmanufacturer:CHASSIS:Unknown systemmanufacturer:ENGINE:Nissan 200 systemmanufacturer:ARMOR:Durallex Light systemmanufacturer:JUMPJET:Rawlings 52 -systemmanufacturer:COMMUNICATIONS:Duotech 65 +systemmanufacturer:COMMUNICATIONS:Duoteck 65 systemmanufacturer:TARGETING:RadCom TXX diff --git a/megamek/data/mechfiles/vehicles/3075/Crow Scout Helicopter.blk b/megamek/data/mechfiles/vehicles/3075/Crow Scout Helicopter.blk index 172b1dbdad1..245672974c6 100644 --- a/megamek/data/mechfiles/vehicles/3075/Crow Scout Helicopter.blk +++ b/megamek/data/mechfiles/vehicles/3075/Crow Scout Helicopter.blk @@ -88,7 +88,7 @@ The Crow Scout VTOL is a military-grade, scout combat vehicle that is based upon -As a scout and spotter, the TAG is the Crow's strongest offense, though it requires coordinating with other units. The only weaponry the Crow mounts is a pair of Exostar ER Small Lasers in its front +As a scout and spotter, the TAG is the Crow's strongest offense, though it requires coordinating with other units. The only weaponry the Crow mounts is a pair of ExoStar ER Small Lasers in its front diff --git a/megamek/data/mechfiles/vehicles/DarkAge/Shackleton AESV.blk b/megamek/data/mechfiles/vehicles/DarkAge/Shackleton AESV.blk index 2eae35af5f6..34dae812fc2 100644 --- a/megamek/data/mechfiles/vehicles/DarkAge/Shackleton AESV.blk +++ b/megamek/data/mechfiles/vehicles/DarkAge/Shackleton AESV.blk @@ -101,7 +101,7 @@ BeagleActiveProbe -Intersteller Players 3 +Interstellar Players 3