The history of the Gladiator is a saga of ingenuity, perseverance, and evolving military strategy within the Draconis Combine. Initiated in 2461, following a successful raid that netted BattleMech plans, the development of the Gladiator marked the Combine's ambitious entry into the era of BattleMech technology. Coordinated by Kozo Von Rohrs and meticulously overseen by the Draconis Elite Strike Teams, the project was shrouded in secrecy, leading to the establishment of New Samarkand Armor Works for its design and production. Despite significant challenges, including mechanical and electronic instabilities that sometimes caused the Gladiator to topple over or crippled its electronic systems, the GLD-1R model was pressed into service, with continuous field upgrades attempting to address these "minor technical difficulties."
The Gladiator's operational history was as tumultuous as its development. Early models, particularly the GLD-1R, were quickly pushed into service despite their flaws. The elite Second Sword of Light's failure to secure Nox in 2475, despite being equipped with refit kits, was a notable blot on the Gladiator's record. This episode and subsequent combat performances led to the design falling out of favor with Coordinator Von Rohrs and the Combine's military. While well-armed and armored, it struggled against the Terran Hegemony's larger mechs and lacked the finesse of more experienced Davion or Steiner MechWarriors. Production of the Gladiator officially ceased in 2488, giving way to the Von Rohrs as the new standard. However, the Gladiator lingered in second-line and militia services before fading into obscurity.
Despite its official retirement, the Gladiator's presence persisted across the Inner Sphere and Periphery, thanks to salvaged models and secondhand markets. Its resilience in various military capacities, even in the face of technological advancements and changing warfare dynamics, highlights its enduring legacy. The Gladiator's story is a reflection of the Draconis Combine's early struggles and eventual strides in the realm of BattleMech engineering, embodying a period of rapid technological adaptation and military innovation.
manufacturer:Merryweather Industries -primaryfactory:Alula Australis +primaryfactory:Alulua Australis systemmanufacturer:CHASSIS:MW240 systemmanufacturer:ENGINE:CoreTek 275 systemmanufacturer:ARMOR:Kemplar 5000 diff --git a/megameklab/data/mechfiles/mechs/3075/Gladiator GLD-4R.mtf b/megameklab/data/mechfiles/mechs/3075/Gladiator GLD-4R.mtf index 21b5d0732..7d3df5260 100644 --- a/megameklab/data/mechfiles/mechs/3075/Gladiator GLD-4R.mtf +++ b/megameklab/data/mechfiles/mechs/3075/Gladiator GLD-4R.mtf @@ -164,7 +164,7 @@ deployment:A Lord's Light P1 PPC provides long range firepower. Two Argra 1L med history:The history of the Gladiator is a saga of ingenuity, perseverance, and evolving military strategy within the Draconis Combine. Initiated in 2461, following a successful raid that netted BattleMech plans, the development of the Gladiator marked the Combine's ambitious entry into the era of BattleMech technology. Coordinated by Kozo Von Rohrs and meticulously overseen by the Draconis Elite Strike Teams, the project was shrouded in secrecy, leading to the establishment of New Samarkand Armor Works for its design and production. Despite significant challenges, including mechanical and electronic instabilities that sometimes caused the Gladiator to topple over or crippled its electronic systems, the GLD-1R model was pressed into service, with continuous field upgrades attempting to address these "minor technical difficulties."
The Gladiator's operational history was as tumultuous as its development. Early models, particularly the GLD-1R, were quickly pushed into service despite their flaws. The elite Second Sword of Light's failure to secure Nox in 2475, despite being equipped with refit kits, was a notable blot on the Gladiator's record. This episode and subsequent combat performances led to the design falling out of favor with Coordinator Von Rohrs and the Combine's military. While well-armed and armored, it struggled against the Terran Hegemony's larger mechs and lacked the finesse of more experienced Davion or Steiner MechWarriors. Production of the Gladiator officially ceased in 2488, giving way to the Von Rohrs as the new standard. However, the Gladiator lingered in second-line and militia services before fading into obscurity.
Despite its official retirement, the Gladiator's presence persisted across the Inner Sphere and Periphery, thanks to salvaged models and secondhand markets. Its resilience in various military capacities, even in the face of technological advancements and changing warfare dynamics, highlights its enduring legacy. The Gladiator's story is a reflection of the Draconis Combine's early struggles and eventual strides in the realm of BattleMech engineering, embodying a period of rapid technological adaptation and military innovation.
manufacturer:Merryweather Industries -primaryfactory:Alula Australis +primaryfactory:Alulua Australis systemmanufacturer:CHASSIS:MW240 systemmanufacturer:ENGINE:CoreTek 275 systemmanufacturer:ARMOR:Kemplar 5000 diff --git a/megameklab/data/mechfiles/mechs/3075/Highlander HGN-732b.mtf b/megameklab/data/mechfiles/mechs/3075/Highlander HGN-732b.mtf index f8a31f26e..f9eb0b971 100644 --- a/megameklab/data/mechfiles/mechs/3075/Highlander HGN-732b.mtf +++ b/megameklab/data/mechfiles/mechs/3075/Highlander HGN-732b.mtf @@ -165,7 +165,7 @@ capabilities:Initially designed as a dedicated city and installation defender, t deployment:The 732b model is a upgrade of the classic 732 built exclusively for SLDF Royal units. This variant drops two heat sinks and a ton of SRM ammo. Artemis IV FCS is added to the LRM and SRM launcher, while the heat sinks are upgraded to doubles. Additional short-range firepower comes in the form of a medium laser added to the right torso. -history:during the design's initial trial runs that pilots began using these 'Mechs in what would infamously become known as the "Highlander Burial". Leaping into the air and landing directly on their enemy, a Highlander could literally drive a light 'Mech into the ground. So successful was this maneuver that the design team re-engineered the legs to withstand repeated death-from-above attacks and turned what had been a desperation move into an art form, giving Highlander pilots an additional psychological edge. As with other Star League era designs the Highlander would suffer the loss of technology brought about by the Succession Wars, and when StarCorps' factory on Son Hoa was devastated towards the end of the Second Succession War the original HGN-732 became virtually extinct. An agreement between StarCorps and Hollis Incorporated to rebuild destroyed chassis from scratch using readily-available technology kept the line going until the mid-3030s when limited production was restarted by StarCorps on Son Hoa and Corey, producing barely a dozen new 'Mechs per year. These HGN-733 Highlanders were used in small numbers by the Capellan Confederation and Lyran Commonwealth, commonly as part of lances containing Exterminators, Victors, Grasshoppers and Catapults. Unbeknownst to many, ComStar also maintained a large stock of Highlanders left over from the Star League, some of which they gifted to the Draconis Combine during the War of 3039. The appearance of so many seemingly rare 733s, along with a few 732s whose advanced technology managed to slip through ComStar screening, had a large impact on Lyran morale during that conflict. ComStar would also use the design in their own military forces, the Com Guard, and even during the Clan Invasion a few original 732s would take to the field as part of the Clans' fighting forces. The Northwind Highlanders especially favored this namesake Battlemech. In fact, during the Succession Wars, they were the only Inner Sphere army to keep a large number of them operational, along with ComStar. The Highlanders are specially skilled in delivering the famed Highlander Burial maneuver. By 3057 StarCorps' Son Hoa line was at full production, producing brand-new original-spec Highlanders for Lyran units of the Federated Commonwealth, just in time to take part in the FedCom Civil War. Highlanders would continue to be produced all the way through to the Jihad, where advanced variants fought both for and against the Word of Blake. +history:During the design's initial trial runs pilots began using these 'Mechs in what would infamously become known as the "Highlander Burial". Leaping into the air and landing directly on their enemy, a Highlander could literally drive a light 'Mech into the ground. So successful was this maneuver that the design team re-engineered the legs to withstand repeated death-from-above attacks and turned what had been a desperation move into an art form, giving Highlander pilots an additional psychological edge. As with other Star League era designs the Highlander would suffer the loss of technology brought about by the Succession Wars, and when StarCorps' factory on Son Hoa was devastated towards the end of the Second Succession War the original HGN-732 became virtually extinct. An agreement between StarCorps and Hollis Incorporated to rebuild destroyed chassis from scratch using readily-available technology kept the line going until the mid-3030s when limited production was restarted by StarCorps on Son Hoa and Corey, producing barely a dozen new 'Mechs per year. These HGN-733 Highlanders were used in small numbers by the Capellan Confederation and Lyran Commonwealth, commonly as part of lances containing Exterminators, Victors, Grasshoppers and Catapults. Unbeknownst to many, ComStar also maintained a large stock of Highlanders left over from the Star League, some of which they gifted to the Draconis Combine during the War of 3039. The appearance of so many seemingly rare 733s, along with a few 732s whose advanced technology managed to slip through ComStar screening, had a large impact on Lyran morale during that conflict. ComStar would also use the design in their own military forces, the Com Guard, and even during the Clan Invasion a few original 732s would take to the field as part of the Clans' fighting forces. The Northwind Highlanders especially favored this namesake Battlemech. In fact, during the Succession Wars, they were the only Inner Sphere army to keep a large number of them operational, along with ComStar. The Highlanders are specially skilled in delivering the famed Highlander Burial maneuver. By 3057 StarCorps' Son Hoa line was at full production, producing brand-new original-spec Highlanders for Lyran units of the Federated Commonwealth, just in time to take part in the FedCom Civil War. Highlanders would continue to be produced all the way through to the Jihad, where advanced variants fought both for and against the Word of Blake. manufacturer:StarCorps Industries, Field Refits primaryfactory:Son Hoa, Various diff --git a/megameklab/data/mechfiles/mechs/3075/King Crab KGC-000b.mtf b/megameklab/data/mechfiles/mechs/3075/King Crab KGC-000b.mtf index c3ff2fd7b..ae96653e1 100644 --- a/megameklab/data/mechfiles/mechs/3075/King Crab KGC-000b.mtf +++ b/megameklab/data/mechfiles/mechs/3075/King Crab KGC-000b.mtf @@ -156,7 +156,7 @@ Ferro-Fibrous overview:The King Crab has been a horror on the battlefield since its introduction just before the old Star League's demise, and it is well known for its ability to quickly kill most BattleMechs under eighty tons. -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,[6] and has been described as a "notorious hangar queen". +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 000b variant is an upgrade of the classic KGC-000 built exclusively for the Star League Defense Force Royal units. Introduced at the same time as the original model its upgrade to double heat sink technology allowed the removal of three heat sinks as well as the addition of an extra ton of ammunition for each autocannon and an Artemis IV FCS for the missile launcher. diff --git a/megameklab/data/mechfiles/mechs/3075/Ostscout OTT-7Jb.mtf b/megameklab/data/mechfiles/mechs/3075/Ostscout OTT-7Jb.mtf index b718d772d..50bbe04e1 100644 --- a/megameklab/data/mechfiles/mechs/3075/Ostscout OTT-7Jb.mtf +++ b/megameklab/data/mechfiles/mechs/3075/Ostscout OTT-7Jb.mtf @@ -160,7 +160,7 @@ capabilities:The Ostscout is quick enough to escape most traps, and very few oth deployment:Introduced at the same time as the original model and used by the SLDF Royal units, the 7Jb is the only variant of the Ostscout built prior to the Clan Invasion. This variant uses Endo Steel to free up enough mass to add a Beagle Active Probe. -history:Starting in 2600 Ostmann built and sold the Ostscout to fulfill many armies' need for a swift reconnaissance 'Mech, but eventually found that demand was outstripping their production ability. Rather than sacrifice their popular Ostroc line of urban-combat 'Mechs, the company licensed Kong Interstellar to start building the 'Mech in 2700, an arrangement similar to that struck regarding the Ostsol. Kong would continue to build Ostscouts for the next hundred years until the destruction of their factory on Connaught at the outset of the Succession Wars. Deprive of the possibility of replacement, many commanders began to hoard their Ostscouts like valuable treasure, parceling them out only for special missions. Most Ostscout pilots would not even attempt to engage enemy 'Mechs, as the advanced sensor system became extremely rare and nearly impossible to replace. This unwillingness to put the 'Mech in danger meant many survived the Succession Wars in practically mint condition, although many which suffered damage to their advanced sensors were forced to replace them with inferior, albeit more robust, systems. Besides the Great Houses, ComStar also utilized the Ostscout, and in the aftermath of the Clan Invasion and ComStar Schism began developing a new Ostscout variant for their Com Guards. This new model would maintain the same maneuverability and intelligence-gathering capabilities of the original while improving its offensive and defensive capabilities. Debuting with success in 3064, within the next three years nearly half of all Com Guard Ostscouts had been upgraded to the new variant; however it was soon discovered that both the Lyran Alliance and Word of Blake were fielding their own updated Ostscouts identical to ComStar's. The intelligence leak would be confirmed and traced back to Dag Kesselring, former Precentor of the 66th Division, who passed on information about the program to both the Lyrans and Blakists. Used by both sides in the Blakist Jihad, the newborn Republic of the Sphere would maintain production of the 11J model Ostscout after the fall of Terra both for its own relatively limited needs as well as export sales to the Federated Suns and Lyran Commonwealth. Still produced during the Dark Age era, aside from the Krupp plant's combat focused Phoenix models both Kong Interstellar and Robinson Standard BattleWorks reintroduced variants that lean more heavily towards the original look and recon aspects of the venerable 7J model. +history:Starting in 2600 Ostmann built and sold the Ostscout to fulfill many armies' need for a swift reconnaissance 'Mech, but eventually found that demand was outstripping their production ability. Rather than sacrifice their popular Ostroc line of urban-combat 'Mechs, the company licensed Kong Interstellar to start building the 'Mech in 2700, an arrangement similar to that struck regarding the Ostsol. Kong would continue to build Ostscouts for the next hundred years until the destruction of their factory on Connaught at the outset of the Succession Wars. Deprived of the possibility of replacement, many commanders began to hoard their Ostscouts like valuable treasure, parceling them out only for special missions. Most Ostscout pilots would not even attempt to engage enemy 'Mechs, as the advanced sensor system became extremely rare and nearly impossible to replace. This unwillingness to put the 'Mech in danger meant many survived the Succession Wars in practically mint condition, although many which suffered damage to their advanced sensors were forced to replace them with inferior, albeit more robust, systems. Besides the Great Houses, ComStar also utilized the Ostscout, and in the aftermath of the Clan Invasion and ComStar Schism began developing a new Ostscout variant for their Com Guards. This new model would maintain the same maneuverability and intelligence-gathering capabilities of the original while improving its offensive and defensive capabilities. Debuting with success in 3064, within the next three years nearly half of all Com Guard Ostscouts had been upgraded to the new variant; however it was soon discovered that both the Lyran Alliance and Word of Blake were fielding their own updated Ostscouts identical to ComStar's. The intelligence leak would be confirmed and traced back to Dag Kesselring, former Precentor of the 66th Division, who passed on information about the program to both the Lyrans and Blakists. Used by both sides in the Blakist Jihad, the newborn Republic of the Sphere would maintain production of the 11J model Ostscout after the fall of Terra both for its own relatively limited needs as well as export sales to the Federated Suns and Lyran Commonwealth. Still produced during the Dark Age era, aside from the Krupp plant's combat focused Phoenix models both Kong Interstellar and Robinson Standard BattleWorks reintroduced variants that lean more heavily towards the original look and recon aspects of the venerable 7J model. manufacturer:Kong Interstellar Corporation,Ostmann Industries primaryfactory:Connaught,Terra diff --git a/megameklab/data/mechfiles/mechs/3075/Pariah Prime.mtf b/megameklab/data/mechfiles/mechs/3075/Pariah Prime.mtf index 475371de2..e84da152b 100644 --- a/megameklab/data/mechfiles/mechs/3075/Pariah Prime.mtf +++ b/megameklab/data/mechfiles/mechs/3075/Pariah Prime.mtf @@ -156,7 +156,7 @@ Foot Actuator overview:The backbone of The Society's military forces, the Septicemia was a utilitarian medium-class workhorse. Devoid of the more experimental technology utilized by the Cephalus and Osteon to allow it to be built in higher volumes, the Septicemia saves weight with an XL Engine, Endo Steel chassis, and nine tons of Ferro-Fibrous armor. While the location of its weaponry in its torsos hampers its ability to carry Battle Armor, this was intentional to try and ensure hand actuators were retained to maximize its physical combat abilities. -capabilities:The primary configuration of the Septicemia is a long-range combatant. Its largest weapon is a HAG 40, though it can only deliver twelve payloads. An ER Large Laser provides effective backup and gives the 'Mech staying power. Both guns are aided by a Targeting Computer.. +capabilities:The primary configuration of the Septicemia is a long-range combatant. Its largest weapon is a HAG 40, though it can only deliver twelve payloads. An ER Large Laser provides effective backup and gives the 'Mech staying power. Both guns are aided by a Targeting Computer. deployment:Planning their OmniMech forces around a single mass-produced design intended to work in concert with two rarer but cutting-edge units, the Septicemia was built using proven technology with a focus towards mutual support on the battlefield, its every aspect intended to allow it to engage the Clan toumans using methods of warfare they found dezgra. Appearing during the Wars of Reaving when Clan warriors were even more intent on an exceedingly strict adherence of zellbrigen to avoid accusations of Taint, the Septicemia would prove frighteningly effective, earning it the nickname of "Pariah" by the Clan Diamond Shark forces that first faced it on Babylon in 3072. diff --git a/megameklab/data/mechfiles/mechs/3075/Thug THG-11Eb.mtf b/megameklab/data/mechfiles/mechs/3075/Thug THG-11Eb.mtf index 573b58ee3..f4322cf53 100644 --- a/megameklab/data/mechfiles/mechs/3075/Thug THG-11Eb.mtf +++ b/megameklab/data/mechfiles/mechs/3075/Thug THG-11Eb.mtf @@ -158,7 +158,7 @@ overview:The Thug was designed by Maltex Corporation as a direct competitor to t capabilities:The armament on the Thug is a very simple, yet effective, combination. For striking power, it carries two Tiegart Particle Projector Cannons in either arm, similar in performance to those found on the Warhammer yet ten percent smaller and more redundant. Backing up the PPCs are two Bical-6 SRM launchers mounted in either side torso with one ton of CASE-protected reloads. These allow the 'Mech to fight off enemies which get within the minimum range of its PPCs and use special dilating covers when not in use. Eighteen double heat sinks gives the Thug a far superior heat dissipation compared to the Warhammer while a ten-ton heavier Endo Steel frame allows it to carry fifteen and a half tons of armor, more than half again as much carried by the Warhammer. The Thug also benefits from the fact that it has hand actuators, making it a mean close-quarters combatant and a good raider able to carry away the spoils of its labor. The 11Eb is an upgrade of the Thug used by the SLDF Royal Brigades in 2760. It upgrades the PPCs to ER PPCs. -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. +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. manufacturer:Maltex Corporation, Earthwerks Incorporated primaryfactory:Errai, Keystone diff --git a/megameklab/data/mechfiles/mechs/3075/Wolverine II WVR-7H.mtf b/megameklab/data/mechfiles/mechs/3075/Wolverine II WVR-7H.mtf index 1195c7e42..13fc98e2f 100644 --- a/megameklab/data/mechfiles/mechs/3075/Wolverine II WVR-7H.mtf +++ b/megameklab/data/mechfiles/mechs/3075/Wolverine II WVR-7H.mtf @@ -162,7 +162,7 @@ capabilities:The autocannon, missile system and laser found on most Wolverines a deployment:Similar in many ways to the 7D, the 7H—referred to as the Wolverine II—was used by the Royal Brigades of the SLDF starting in 2770 and was also an upgrade of the 6R. It utilizes an Endo Steel structure, Ferro-Fibrous armor, and double heat sinks to increase combat capabilities. Extra armor protects the legs, while CASE protects all the ammo bins. Like the 7D, the autocannon is upgraded to an Ultra-class model and the medium laser is upgraded to a pulse version. In addition, the SRM-6 is slaved to an Artemis IV Fire Control System to improve the accuracy of the individual missiles. -history:A widespread part of every major military, the Wolverine has manufacturing plants scattered throughout the entire Inner Sphere. While certain states-notable the Free Worlds League-have larger numbers of the design, only the Capellans began facing a shortage of the Wolverine after the loss of their Nanking facilities. +history:A widespread part of every major military, the Wolverine has manufacturing plants scattered throughout the entire Inner Sphere. While certain states-notably the Free Worlds League-have larger numbers of the design, only the Capellans began facing a shortage of the Wolverine after the loss of their Nanking facilities. manufacturer:Kallon Industries and SLDF Research Division primaryfactory:New Earth diff --git a/megameklab/data/mechfiles/mechs/3085u/Cutting Edge/Atlas AS7-Dr.mtf b/megameklab/data/mechfiles/mechs/3085u/Cutting Edge/Atlas AS7-Dr.mtf index 39852cff8..02247f63b 100644 --- a/megameklab/data/mechfiles/mechs/3085u/Cutting Edge/Atlas AS7-Dr.mtf +++ b/megameklab/data/mechfiles/mechs/3085u/Cutting Edge/Atlas AS7-Dr.mtf @@ -163,7 +163,7 @@ Heat Sink overview:"A 'Mech as powerful as possible, as impenetrable as possible, and as ugly and foreboding as conceivable, so that fear itself will be our ally.”-Aleksandr Kerensky -capabilities:The Atlas is probably the best-known BattleMech to ever set foot on the modern battlefield. Designed with specifications from Aleksandr Kerensky himself in 2755 in the midst of the Cameron Edicts, the Atlas was originally intended to ensure SLDF superiority over the Star League member states. Carrying the largest LRM launcher, the largest autocannon, and the largest SRM launcher possible, the Atlas can deal frightening amounts of damage in short amounts of time. Often used as a command vehicle, the Atlas mounts an advanced antenna and communications array, allowing it to engage in surface-to space communications in real time. The massive 19-ton hide of armor that protects the Atlas makes it a difficult foe to take down. Indeed, most MechWarriors choose to fall back rather than face one head-one, as its lumbering gait mean it can rarely catch up to other 'Mechs that choose to flee it. A full year of development went into crafting the famous "Death's Head" of the 'Mech to achieve the perfect ratio of functionality and fear. The head is also quite roomy and allows a small satellite dish to be mounted for surface-to-space communications. During combat the pilot can easily fold up the dish and store it within a protective portion of the head. +capabilities:The Atlas is probably the best-known BattleMech to ever set foot on the modern battlefield. Designed with specifications from Aleksandr Kerensky himself in 2755 in the midst of the Cameron Edicts, the Atlas was originally intended to ensure SLDF superiority over the Star League member states. Carrying the largest LRM launcher, the largest autocannon, and the largest SRM launcher possible, the Atlas can deal frightening amounts of damage in short amounts of time. Often used as a command vehicle, the Atlas mounts an advanced antenna and communications array, allowing it to engage in surface-to-space communications in real time. The massive 19-ton hide of armor that protects the Atlas makes it a difficult foe to take down. Indeed, most MechWarriors choose to fall back rather than face one head-on, as its lumbering gait means it can rarely catch up to other 'Mechs that choose to flee it. A full year of development went into crafting the famous "Death's Head" of the 'Mech to achieve the perfect ratio of functionality and fear. The head is also quite roomy and allows a small satellite dish to be mounted for surface-to-space communications. During combat the pilot can easily fold up the dish and store it within a protective portion of the head. deployment:A post-Jihad field refit introduced in 3070 to upgrade old Lyran militia Atlases for use by front-line LCAF units. The AS7-Dr replaced the mammoth AC/20 with a Heavy PPC, using the weight and space saved to upgrade the SRM launcher to a Streak model and add a Guardian ECM Suite, C3 Slave and two extra standard heat sinks diff --git a/megameklab/data/mechfiles/mechs/3085u/Cutting Edge/Atlas AS7-K2.mtf b/megameklab/data/mechfiles/mechs/3085u/Cutting Edge/Atlas AS7-K2.mtf index 9db6a15d0..c124d9212 100644 --- a/megameklab/data/mechfiles/mechs/3085u/Cutting Edge/Atlas AS7-K2.mtf +++ b/megameklab/data/mechfiles/mechs/3085u/Cutting Edge/Atlas AS7-K2.mtf @@ -161,7 +161,7 @@ Ferro-Fibrous overview:"A 'Mech as powerful as possible, as impenetrable as possible, and as ugly and foreboding as conceivable, so that fear itself will be our ally.”-Aleksandr Kerensky -capabilities:The Atlas is probably the best-known BattleMech to ever set foot on the modern battlefield. Designed with specifications from Aleksandr Kerensky himself in 2755 in the midst of the Cameron Edicts, the Atlas was originally intended to ensure SLDF superiority over the Star League member states. Carrying the largest LRM launcher, the largest autocannon, and the largest SRM launcher possible, the Atlas can deal frightening amounts of damage in short amounts of time. Often used as a command vehicle, the Atlas mounts an advanced antenna and communications array, allowing it to engage in surface-to space communications in real time. The massive 19-ton hide of armor that protects the Atlas makes it a difficult foe to take down. Indeed, most MechWarriors choose to fall back rather than face one head-one, as its lumbering gait mean it can rarely catch up to other 'Mechs that choose to flee it. A full year of development went into crafting the famous "Death's Head" of the 'Mech to achieve the perfect ratio of functionality and fear. The head is also quite roomy and allows a small satellite dish to be mounted for surface-to-space communications. During combat the pilot can easily fold up the dish and store it within a protective portion of the head. +capabilities:The Atlas is probably the best-known BattleMech to ever set foot on the modern battlefield. Designed with specifications from Aleksandr Kerensky himself in 2755 in the midst of the Cameron Edicts, the Atlas was originally intended to ensure SLDF superiority over the Star League member states. Carrying the largest LRM launcher, the largest autocannon, and the largest SRM launcher possible, the Atlas can deal frightening amounts of damage in short amounts of time. Often used as a command vehicle, the Atlas mounts an advanced antenna and communications array, allowing it to engage in surface-to-space communications in real time. The massive 19-ton hide of armor that protects the Atlas makes it a difficult foe to take down. Indeed, most MechWarriors choose to fall back rather than face one head-on, as its lumbering gait means it can rarely catch up to other 'Mechs that choose to flee it. A full year of development went into crafting the famous "Death's Head" of the 'Mech to achieve the perfect ratio of functionality and fear. The head is also quite roomy and allows a small satellite dish to be mounted for surface-to-space communications. During combat the pilot can easily fold up the dish and store it within a protective portion of the head. deployment:A post-Jihad Lyran Commonwealth take on the Combine's AS7-K introduced in 3082, the K2 model of the Atlas also used a Vlar XL Engine but increased its rating to 400, giving the K2 model a top speed of 64.8 km/h. Retaining only the Gauss Rifle and ER Large Lasers of the AS7-K, the K2 carried two Guided Technologies 2nd Gen Streak SRM-6 launchers. The K2 was protected with sixteen and a half tons of Ferro-Fibrous armor and, to protect against advanced enemy electronics, a Guardian ECM Suite. diff --git a/megameklab/data/mechfiles/mechs/3085u/Cutting Edge/Atlas AS7-K3.mtf b/megameklab/data/mechfiles/mechs/3085u/Cutting Edge/Atlas AS7-K3.mtf index d9b4dc995..4afb42c68 100644 --- a/megameklab/data/mechfiles/mechs/3085u/Cutting Edge/Atlas AS7-K3.mtf +++ b/megameklab/data/mechfiles/mechs/3085u/Cutting Edge/Atlas AS7-K3.mtf @@ -160,7 +160,7 @@ IS Ferro-Fibrous overview:"A 'Mech as powerful as possible, as impenetrable as possible, and as ugly and foreboding as conceivable, so that fear itself will be our ally.”-Aleksandr Kerensky -capabilities:The Atlas is probably the best-known BattleMech to ever set foot on the modern battlefield. Designed with specifications from Aleksandr Kerensky himself in 2755 in the midst of the Cameron Edicts, the Atlas was originally intended to ensure SLDF superiority over the Star League member states. Carrying the largest LRM launcher, the largest autocannon, and the largest SRM launcher possible, the Atlas can deal frightening amounts of damage in short amounts of time. Often used as a command vehicle, the Atlas mounts an advanced antenna and communications array, allowing it to engage in surface-to space communications in real time. The massive 19-ton hide of armor that protects the Atlas makes it a difficult foe to take down. Indeed, most MechWarriors choose to fall back rather than face one head-one, as its lumbering gait mean it can rarely catch up to other 'Mechs that choose to flee it. A full year of development went into crafting the famous "Death's Head" of the 'Mech to achieve the perfect ratio of functionality and fear. The head is also quite roomy and allows a small satellite dish to be mounted for surface-to-space communications. During combat the pilot can easily fold up the dish and store it within a protective portion of the head. +capabilities:The Atlas is probably the best-known BattleMech to ever set foot on the modern battlefield. Designed with specifications from Aleksandr Kerensky himself in 2755 in the midst of the Cameron Edicts, the Atlas was originally intended to ensure SLDF superiority over the Star League member states. Carrying the largest LRM launcher, the largest autocannon, and the largest SRM launcher possible, the Atlas can deal frightening amounts of damage in short amounts of time. Often used as a command vehicle, the Atlas mounts an advanced antenna and communications array, allowing it to engage in surface-to-space communications in real time. The massive 19-ton hide of armor that protects the Atlas makes it a difficult foe to take down. Indeed, most MechWarriors choose to fall back rather than face one head-on, as its lumbering gait means it can rarely catch up to other 'Mechs that choose to flee it. A full year of development went into crafting the famous "Death's Head" of the 'Mech to achieve the perfect ratio of functionality and fear. The head is also quite roomy and allows a small satellite dish to be mounted for surface-to-space communications. During combat the pilot can easily fold up the dish and store it within a protective portion of the head. deployment:A modification of the K2 built in 3083, the K3 removed the two Streak SRM-6 launchers and replaced them with three jump jets and a Streak SRM-4 launcher, giving the AS7-K3 incredible maneuverability. diff --git a/megameklab/data/mechfiles/mechs/3085u/Cutting Edge/Atlas AS8-D.mtf b/megameklab/data/mechfiles/mechs/3085u/Cutting Edge/Atlas AS8-D.mtf index 8d0935893..fa0850788 100644 --- a/megameklab/data/mechfiles/mechs/3085u/Cutting Edge/Atlas AS8-D.mtf +++ b/megameklab/data/mechfiles/mechs/3085u/Cutting Edge/Atlas AS8-D.mtf @@ -166,7 +166,7 @@ TSM overview:"A 'Mech as powerful as possible, as impenetrable as possible, and as ugly and foreboding as conceivable, so that fear itself will be our ally.”-Aleksandr Kerensky -capabilities:The Atlas is probably the best-known BattleMech to ever set foot on the modern battlefield. Designed with specifications from Aleksandr Kerensky himself in 2755 in the midst of the Cameron Edicts, the Atlas was originally intended to ensure SLDF superiority over the Star League member states. Carrying the largest LRM launcher, the largest autocannon, and the largest SRM launcher possible, the Atlas can deal frightening amounts of damage in short amounts of time. Often used as a command vehicle, the Atlas mounts an advanced antenna and communications array, allowing it to engage in surface-to space communications in real time. The massive 19-ton hide of armor that protects the Atlas makes it a difficult foe to take down. Indeed, most MechWarriors choose to fall back rather than face one head-one, as its lumbering gait mean it can rarely catch up to other 'Mechs that choose to flee it. A full year of development went into crafting the famous "Death's Head" of the 'Mech to achieve the perfect ratio of functionality and fear. The head is also quite roomy and allows a small satellite dish to be mounted for surface-to-space communications. During combat the pilot can easily fold up the dish and store it within a protective portion of the head. +capabilities:The Atlas is probably the best-known BattleMech to ever set foot on the modern battlefield. Designed with specifications from Aleksandr Kerensky himself in 2755 in the midst of the Cameron Edicts, the Atlas was originally intended to ensure SLDF superiority over the Star League member states. Carrying the largest LRM launcher, the largest autocannon, and the largest SRM launcher possible, the Atlas can deal frightening amounts of damage in short amounts of time. Often used as a command vehicle, the Atlas mounts an advanced antenna and communications array, allowing it to engage in surface-to-space communications in real time. The massive 19-ton hide of armor that protects the Atlas makes it a difficult foe to take down. Indeed, most MechWarriors choose to fall back rather than face one head-on, as its lumbering gait means it can rarely catch up to other 'Mechs that choose to flee it. A full year of development went into crafting the famous "Death's Head" of the 'Mech to achieve the perfect ratio of functionality and fear. The head is also quite roomy and allows a small satellite dish to be mounted for surface-to-space communications. During combat the pilot can easily fold up the dish and store it within a protective portion of the head. deployment:Released as a prototype in 3074 and entering limited production after the Jihad, this new version sports a Light PPC in each arm. A pair of MML-9s give the design a good punch at both long and short range while a Rotary AC/5, one Snub-Nose PPC, two ER Small Lasers and two Small Lasers round up the configuration's closer range damage. The AS8-D mounts fourteen double heat sinks to balance the heat load generated by the weapons, but the design also incorporated Triple Strength Myomer so that when the AS8-D is running hot it can reach speeds of almost sixty-five kph. diff --git a/megameklab/data/mechfiles/mechs/3085u/Cutting Edge/Hatchetman HCT-6M.mtf b/megameklab/data/mechfiles/mechs/3085u/Cutting Edge/Hatchetman HCT-6M.mtf index 3a9726099..d08ef5be2 100644 --- a/megameklab/data/mechfiles/mechs/3085u/Cutting Edge/Hatchetman HCT-6M.mtf +++ b/megameklab/data/mechfiles/mechs/3085u/Cutting Edge/Hatchetman HCT-6M.mtf @@ -161,7 +161,7 @@ capabilities:As well as being the first design to carry one, the Hatchetman itse deployment:Produced from ex-Lyran trophies by the FWLM after early stages of the Jihad, this version of the 5S variant has medium pulse lasers and the trademark hatchet and adds a Beagle Active Probe. The main firepower for this variant comes from a Heavy PPC housed in the right torso. The 5S' CASE system has been omitted. -history:s well as being the first design to carry one, the Hatchetman itself was the first totally new 'Mech produced in the Inner Sphere in over a century, and was also the first production 'Mech to use a Full-Head Ejection System. Despite being first manufactured in the Lyran Commonwealth the Hatchetman was actually designed by the enigmatic Dr. B. Banzai of Team Banzai, a mercenary unit associated with the Federated Suns' New Avalon Institute of Science. Thus the 'Mech was also a signal of the growing cooperation between these newly-allied Successor States. in the design's first combat test, when elements of the 4th Proserpina Hussars raided Sevren and were literally cut to pieces by a mostly Hatchetman-equipped battalion of the 26th Lyran Guards which lured the enemy into an industrial park. Where the Hatchetman is at a disadvantage is on open terrain, as its relatively slow speed, light armoring and general frailty leaves it vulnerable to other 'Mechs. Initially the Hatchetman's first production run was limited to garrisoning large Lyran cities, but its early successes inspired further deployments and the 'Mech soon began appearing in the arsenal of the Federated Suns, particularly among the Crucis Lancers and 1st Kathil Uhlans. In the wake of the Fourth Succession War and the formal creation of the Federated Commonwealth, the Hatchetman was selected to become one of the standard designs for the Armed Forces of the Federated Commonwealth. Demand for the 'Mech soon began to outstrip Defiance Industries' ability to supply it, even after tripling output from their Hesperus II factory, and so it contracted Johnston Industries to set up a Hatchetman line on Johnston. The recovery of lost Star League technology eventually allowed for the creation of the HCT-5S in 3049, with additional variants created in years hence. Among the other realms, the Draconis Combine managed to capture a few examples of the Hatchetman and successfully copy most of the design to produce their own following the War of 3039, however the 'Mech proved to be unpopular and the program was canceled. Hoping to salvage the project, Independence Weaponry experimented with the design and eventually created a variant more palatable to Kuritan pilots. Out in the Periphery, the introduction of the Hatchetman caused quite a stir within the Taurian Concordat when a group of mercenaries brought along their old HCT-3Fs upon integrating with the Taurian Defense Forces. Protector of the Realm Thomas Calderon ordered Taurus Territorial Industries to reverse-engineer the design, which they finally succeeded in accomplishing after much delay by 3054, only for production to be halted in 3066 when the Fighting Urukhai destroyed the Taurus Territorial Industries facility. +history:As well as being the first design to carry one, the Hatchetman itself was the first totally new 'Mech produced in the Inner Sphere in over a century, and was also the first production 'Mech to use a Full-Head Ejection System. Despite being first manufactured in the Lyran Commonwealth the Hatchetman was actually designed by the enigmatic Dr. B. Banzai of Team Banzai, a mercenary unit associated with the Federated Suns' New Avalon Institute of Science. Thus the 'Mech was also a signal of the growing cooperation between these newly-allied Successor States. In the design's first combat test, elements of the 4th Proserpina Hussars raided Sevren and were literally cut to pieces by a mostly Hatchetman-equipped battalion of the 26th Lyran Guards which lured the enemy into an industrial park. Where the Hatchetman is at a disadvantage is on open terrain, as its relatively slow speed, light armoring and general frailty leaves it vulnerable to other 'Mechs. Initially the Hatchetman's first production run was limited to garrisoning large Lyran cities, but its early successes inspired further deployments and the 'Mech soon began appearing in the arsenal of the Federated Suns, particularly among the Crucis Lancers and 1st Kathil Uhlans. In the wake of the Fourth Succession War and the formal creation of the Federated Commonwealth, the Hatchetman was selected to become one of the standard designs for the Armed Forces of the Federated Commonwealth. Demand for the 'Mech soon began to outstrip Defiance Industries' ability to supply it, even after tripling output from their Hesperus II factory, and so it contracted Johnston Industries to set up a Hatchetman line on Johnston. The recovery of lost Star League technology eventually allowed for the creation of the HCT-5S in 3049, with additional variants created in years hence. Among the other realms, the Draconis Combine managed to capture a few examples of the Hatchetman and successfully copy most of the design to produce their own following the War of 3039, however the 'Mech proved to be unpopular and the program was canceled. Hoping to salvage the project, Independence Weaponry experimented with the design and eventually created a variant more palatable to Kuritan pilots. Out in the Periphery, the introduction of the Hatchetman caused quite a stir within the Taurian Concordat when a group of mercenaries brought along their old HCT-3Fs upon integrating with the Taurian Defense Forces. Protector of the Realm Thomas Calderon ordered Taurus Territorial Industries to reverse-engineer the design, which they finally succeeded in accomplishing after much delay by 3054, only for production to be halted in 3066 when the Fighting Urukhai destroyed the Taurus Territorial Industries facility. manufacturer:Field Refit primaryfactory:Field Refit diff --git a/megameklab/data/mechfiles/mechs/3085u/Cutting Edge/Hatchetman HCT-7S.mtf b/megameklab/data/mechfiles/mechs/3085u/Cutting Edge/Hatchetman HCT-7S.mtf index 9b8d373da..da006cfe5 100644 --- a/megameklab/data/mechfiles/mechs/3085u/Cutting Edge/Hatchetman HCT-7S.mtf +++ b/megameklab/data/mechfiles/mechs/3085u/Cutting Edge/Hatchetman HCT-7S.mtf @@ -160,7 +160,7 @@ capabilities:As well as being the first design to carry one, the Hatchetman itse deployment:Developed during the Jihad in 3084, this Hatchetman variant has an expanded role beyond urban combat. By using a larger Light Engine, designers increased the 'Mech's cruising speed by 25% and added another jump jet to increase the jump range by 25%. The biggest change is in the 'Mech's armament. The traditional autocannon is replaced by a single MML-9 and three tons of ammunition. A Guardian ECM Suite disrupts enemy electronics while ferro-fibrous armor and CASE protect the 'Mech from weapons fire and an ammunition explosion. -history:s well as being the first design to carry one, the Hatchetman itself was the first totally new 'Mech produced in the Inner Sphere in over a century, and was also the first production 'Mech to use a Full-Head Ejection System. Despite being first manufactured in the Lyran Commonwealth the Hatchetman was actually designed by the enigmatic Dr. B. Banzai of Team Banzai, a mercenary unit associated with the Federated Suns' New Avalon Institute of Science. Thus the 'Mech was also a signal of the growing cooperation between these newly-allied Successor States. in the design's first combat test, when elements of the 4th Proserpina Hussars raided Sevren and were literally cut to pieces by a mostly Hatchetman-equipped battalion of the 26th Lyran Guards which lured the enemy into an industrial park. Where the Hatchetman is at a disadvantage is on open terrain, as its relatively slow speed, light armoring and general frailty leaves it vulnerable to other 'Mechs. Initially the Hatchetman's first production run was limited to garrisoning large Lyran cities, but its early successes inspired further deployments and the 'Mech soon began appearing in the arsenal of the Federated Suns, particularly among the Crucis Lancers and 1st Kathil Uhlans. In the wake of the Fourth Succession War and the formal creation of the Federated Commonwealth, the Hatchetman was selected to become one of the standard designs for the Armed Forces of the Federated Commonwealth. Demand for the 'Mech soon began to outstrip Defiance Industries' ability to supply it, even after tripling output from their Hesperus II factory, and so it contracted Johnston Industries to set up a Hatchetman line on Johnston. The recovery of lost Star League technology eventually allowed for the creation of the HCT-5S in 3049, with additional variants created in years hence. Among the other realms, the Draconis Combine managed to capture a few examples of the Hatchetman and successfully copy most of the design to produce their own following the War of 3039, however the 'Mech proved to be unpopular and the program was canceled. Hoping to salvage the project, Independence Weaponry experimented with the design and eventually created a variant more palatable to Kuritan pilots. Out in the Periphery, the introduction of the Hatchetman caused quite a stir within the Taurian Concordat when a group of mercenaries brought along their old HCT-3Fs upon integrating with the Taurian Defense Forces. Protector of the Realm Thomas Calderon ordered Taurus Territorial Industries to reverse-engineer the design, which they finally succeeded in accomplishing after much delay by 3054, only for production to be halted in 3066 when the Fighting Urukhai destroyed the Taurus Territorial Industries facility. +history:As well as being the first design to carry one, the Hatchetman itself was the first totally new 'Mech produced in the Inner Sphere in over a century, and was also the first production 'Mech to use a Full-Head Ejection System. Despite being first manufactured in the Lyran Commonwealth the Hatchetman was actually designed by the enigmatic Dr. B. Banzai of Team Banzai, a mercenary unit associated with the Federated Suns' New Avalon Institute of Science. Thus the 'Mech was also a signal of the growing cooperation between these newly-allied Successor States. In the design's first combat test, elements of the 4th Proserpina Hussars raided Sevren and were literally cut to pieces by a mostly Hatchetman-equipped battalion of the 26th Lyran Guards which lured the enemy into an industrial park. Where the Hatchetman is at a disadvantage is on open terrain, as its relatively slow speed, light armoring and general frailty leaves it vulnerable to other 'Mechs. Initially the Hatchetman's first production run was limited to garrisoning large Lyran cities, but its early successes inspired further deployments and the 'Mech soon began appearing in the arsenal of the Federated Suns, particularly among the Crucis Lancers and 1st Kathil Uhlans. In the wake of the Fourth Succession War and the formal creation of the Federated Commonwealth, the Hatchetman was selected to become one of the standard designs for the Armed Forces of the Federated Commonwealth. Demand for the 'Mech soon began to outstrip Defiance Industries' ability to supply it, even after tripling output from their Hesperus II factory, and so it contracted Johnston Industries to set up a Hatchetman line on Johnston. The recovery of lost Star League technology eventually allowed for the creation of the HCT-5S in 3049, with additional variants created in years hence. Among the other realms, the Draconis Combine managed to capture a few examples of the Hatchetman and successfully copy most of the design to produce their own following the War of 3039, however the 'Mech proved to be unpopular and the program was canceled. Hoping to salvage the project, Independence Weaponry experimented with the design and eventually created a variant more palatable to Kuritan pilots. Out in the Periphery, the introduction of the Hatchetman caused quite a stir within the Taurian Concordat when a group of mercenaries brought along their old HCT-3Fs upon integrating with the Taurian Defense Forces. Protector of the Realm Thomas Calderon ordered Taurus Territorial Industries to reverse-engineer the design, which they finally succeeded in accomplishing after much delay by 3054, only for production to be halted in 3066 when the Fighting Urukhai destroyed the Taurus Territorial Industries facility. manufacturer:Defiance Industries,Johnston Industries primaryfactory:Hesperus II,New Syrtis diff --git a/megameklab/data/mechfiles/mechs/3085u/Cutting Edge/Panther PNT-10K2.mtf b/megameklab/data/mechfiles/mechs/3085u/Cutting Edge/Panther PNT-10K2.mtf index 1692e99a1..d3f5e246f 100644 --- a/megameklab/data/mechfiles/mechs/3085u/Cutting Edge/Panther PNT-10K2.mtf +++ b/megameklab/data/mechfiles/mechs/3085u/Cutting Edge/Panther PNT-10K2.mtf @@ -160,7 +160,7 @@ capabilities:Luckily the Panther had also proved itself to be quite hardy, sport deployment:The -10K2 Panther retains the ER PPC of the -10K and removes the Artemis IV as well as a heat sink. In exchange the remaining heat sinks have been upgraded to double strength versions, alleviating the heat problems that plague the 10K, while an additional SRM-4 has been added. -history:The original PNT-8Z model underwent a revision after the disastrous Battle of St. John in 2759, when it was revealed that its main weapon, a Tronel Large Laser, was inefficient in both range and firepower for the immense waste heat generated. The Draconis Combine inherited Alshain Weapons' Panther factory on New Oslo when the Star League dissolved and quickly put the production line to work building new Panthers for the DCMS. Their first large-scale use by Kurita warriors came during the First Succession War in the battle for Quentin, when the 2nd Legion of Vega used their Panthers to severely maul the slower, heavier 'Mechs of the 42nd Avalon Hussars while avoiding return fire. Throughout the Succession Wars, the Combine was the only significant user of the Panther, often pairing it with the Jenner in a deadly combination of speed and firepower; though the other Successor States employed Panthers in smaller numbers, these were either the result of battlefield salvage or older League-era 8Z models. The Panther also proved itself a deadly urban combatant, using its mobility to easily navigate the more restricted space of a city environment and take out heavier opponents from rooftop sniping perches with its main weapon. Lyran MechWarriors eventually took to nicknaming the 'Mech the "Alley Cat" for its propensity to conduct dark alley-way "muggings. Demand for the Panther continued to increase, forcing Alshain to build a secondary factory on Jarett to keep up. In an ironic twist both factories fell within the borders of the Free Rasalhague Republic following its creation in 3034, transferring ownership to the new state, and soon the Panther became a mainstay of the KungsArmé. The situation did not last long however following the invasion of the Clans, and both planets were swiftly conquered by Clan Ghost Bear. While Alshain Weapons crash-built a new line on Tok Do in 3053, they could not maintain their pre-invasion production levels and focused on spare parts and refit kits instead. Eventually Wakazashi Enterprises bought the production license for the Panther and began rolling out new variants from its New Samarkand factory. These have gone on to serve in every DCMS unit since, including the bloody years of the Jihad. +history:The original PNT-8Z model underwent a revision after the disastrous Battle of St. John in 2759, when it was revealed that its main weapon, a Tronel Large Laser, was inefficient in both range and firepower for the immense waste heat generated. The Draconis Combine inherited Alshain Weapons' Panther factory on New Oslo when the Star League dissolved and quickly put the production line to work building new Panthers for the DCMS. Their first large-scale use by Kurita warriors came during the First Succession War in the battle for Quentin, when the 2nd Legion of Vega used their Panthers to severely maul the slower, heavier 'Mechs of the 42nd Avalon Hussars while avoiding return fire. Throughout the Succession Wars, the Combine was the only significant user of the Panther, often pairing it with the Jenner in a deadly combination of speed and firepower; though the other Successor States employed Panthers in smaller numbers, these were either the result of battlefield salvage or older League-era 8Z models. The Panther also proved itself a deadly urban combatant, using its mobility to easily navigate the more restricted space of a city environment and take out heavier opponents from rooftop sniping perches with its main weapon. Lyran MechWarriors eventually took to nicknaming the 'Mech the "Alley Cat" for its propensity to conduct dark alley-way "muggings. Demand for the Panther continued to increase, forcing Alshain to build a secondary factory on Jarett to keep up. In an ironic twist both factories fell within the borders of the Free Rasalhague Republic following its creation in 3034, transferring ownership to the new state, and soon the Panther became a mainstay of the KungsArmé. The situation did not last long however following the invasion of the Clans, and both planets were swiftly conquered by Clan Ghost Bear. While Alshain Weapons crash-built a new line on Tok Do in 3053, they could not maintain their pre-invasion production levels and focused on spare parts and refit kits instead. Eventually Wakazashi Enterprises bought the production license for the Panther and began rolling out new variants from its New Samarkand factory. These have gone on to serve in every DCMS unit since, including the bloody years of the Jihad. manufacturer:Field Refit primaryfactory:Field Refit diff --git a/megameklab/data/mechfiles/mechs/3085u/Cutting Edge/Panther PNT-12K.mtf b/megameklab/data/mechfiles/mechs/3085u/Cutting Edge/Panther PNT-12K.mtf index aecdfd787..84a1e6df9 100644 --- a/megameklab/data/mechfiles/mechs/3085u/Cutting Edge/Panther PNT-12K.mtf +++ b/megameklab/data/mechfiles/mechs/3085u/Cutting Edge/Panther PNT-12K.mtf @@ -158,7 +158,7 @@ overview:The Panther is one of the BattleMechs that is most iconic of the Dracon capabilities:Luckily the Panther had also proved itself to be quite hardy, sporting six and a half tons of armor, and maneuverable, thanks to four Lexington Lifter jump jets split between both legs for a total jumping distance of 120 meters, thus an attempt to fix its one deficiency was made by League engineers by replacing the laser with a Lord's Light Particle Projection Cannon. The swap in weaponry, along with a superior armor composite, gave the PNT-9R Panther a new lease on life, such that it has seen over three centuries of continuous use since its introduction. -history:The original PNT-8Z model underwent a revision after the disastrous Battle of St. John in 2759, when it was revealed that its main weapon, a Tronel Large Laser, was inefficient in both range and firepower for the immense waste heat generated. The Draconis Combine inherited Alshain Weapons' Panther factory on New Oslo when the Star League dissolved and quickly put the production line to work building new Panthers for the DCMS. Their first large-scale use by Kurita warriors came during the First Succession War in the battle for Quentin, when the 2nd Legion of Vega used their Panthers to severely maul the slower, heavier 'Mechs of the 42nd Avalon Hussars while avoiding return fire. Throughout the Succession Wars, the Combine was the only significant user of the Panther, often pairing it with the Jenner in a deadly combination of speed and firepower; though the other Successor States employed Panthers in smaller numbers, these were either the result of battlefield salvage or older League-era 8Z models. The Panther also proved itself a deadly urban combatant, using its mobility to easily navigate the more restricted space of a city environment and take out heavier opponents from rooftop sniping perches with its main weapon. Lyran MechWarriors eventually took to nicknaming the 'Mech the "Alley Cat" for its propensity to conduct dark alley-way "muggings. Demand for the Panther continued to increase, forcing Alshain to build a secondary factory on Jarett to keep up. In an ironic twist both factories fell within the borders of the Free Rasalhague Republic following its creation in 3034, transferring ownership to the new state, and soon the Panther became a mainstay of the KungsArmé. The situation did not last long however following the invasion of the Clans, and both planets were swiftly conquered by Clan Ghost Bear. While Alshain Weapons crash-built a new line on Tok Do in 3053, they could not maintain their pre-invasion production levels and focused on spare parts and refit kits instead. Eventually Wakazashi Enterprises bought the production license for the Panther and began rolling out new variants from its New Samarkand factory. These have gone on to serve in every DCMS unit since, including the bloody years of the Jihad. +history:The original PNT-8Z model underwent a revision after the disastrous Battle of St. John in 2759, when it was revealed that its main weapon, a Tronel Large Laser, was inefficient in both range and firepower for the immense waste heat generated. The Draconis Combine inherited Alshain Weapons' Panther factory on New Oslo when the Star League dissolved and quickly put the production line to work building new Panthers for the DCMS. Their first large-scale use by Kurita warriors came during the First Succession War in the battle for Quentin, when the 2nd Legion of Vega used their Panthers to severely maul the slower, heavier 'Mechs of the 42nd Avalon Hussars while avoiding return fire. Throughout the Succession Wars, the Combine was the only significant user of the Panther, often pairing it with the Jenner in a deadly combination of speed and firepower; though the other Successor States employed Panthers in smaller numbers, these were either the result of battlefield salvage or older League-era 8Z models. The Panther also proved itself a deadly urban combatant, using its mobility to easily navigate the more restricted space of a city environment and take out heavier opponents from rooftop sniping perches with its main weapon. Lyran MechWarriors eventually took to nicknaming the 'Mech the "Alley Cat" for its propensity to conduct dark alley-way "muggings. Demand for the Panther continued to increase, forcing Alshain to build a secondary factory on Jarett to keep up. In an ironic twist both factories fell within the borders of the Free Rasalhague Republic following its creation in 3034, transferring ownership to the new state, and soon the Panther became a mainstay of the KungsArmé. The situation did not last long however following the invasion of the Clans, and both planets were swiftly conquered by Clan Ghost Bear. While Alshain Weapons crash-built a new line on Tok Do in 3053, they could not maintain their pre-invasion production levels and focused on spare parts and refit kits instead. Eventually Wakazashi Enterprises bought the production license for the Panther and began rolling out new variants from its New Samarkand factory. These have gone on to serve in every DCMS unit since, including the bloody years of the Jihad. manufacturer:Field Refit primaryfactory:Field Refit diff --git a/megameklab/data/mechfiles/mechs/3085u/Cutting Edge/Panther PNT-12K2.mtf b/megameklab/data/mechfiles/mechs/3085u/Cutting Edge/Panther PNT-12K2.mtf index 756a3ee0c..e2f7ffe22 100644 --- a/megameklab/data/mechfiles/mechs/3085u/Cutting Edge/Panther PNT-12K2.mtf +++ b/megameklab/data/mechfiles/mechs/3085u/Cutting Edge/Panther PNT-12K2.mtf @@ -159,7 +159,7 @@ capabilities:Luckily the Panther had also proved itself to be quite hardy, sport deployment:The -12K2 Panther is also an upgrade of the -10K. This version is almost identical to the -10K2, but has replaced the two SRM-4 launchers with a single MRM-10 and an additional ton of armor. -history:The original PNT-8Z model underwent a revision after the disastrous Battle of St. John in 2759, when it was revealed that its main weapon, a Tronel Large Laser, was inefficient in both range and firepower for the immense waste heat generated. The Draconis Combine inherited Alshain Weapons' Panther factory on New Oslo when the Star League dissolved and quickly put the production line to work building new Panthers for the DCMS. Their first large-scale use by Kurita warriors came during the First Succession War in the battle for Quentin, when the 2nd Legion of Vega used their Panthers to severely maul the slower, heavier 'Mechs of the 42nd Avalon Hussars while avoiding return fire. Throughout the Succession Wars, the Combine was the only significant user of the Panther, often pairing it with the Jenner in a deadly combination of speed and firepower; though the other Successor States employed Panthers in smaller numbers, these were either the result of battlefield salvage or older League-era 8Z models. The Panther also proved itself a deadly urban combatant, using its mobility to easily navigate the more restricted space of a city environment and take out heavier opponents from rooftop sniping perches with its main weapon. Lyran MechWarriors eventually took to nicknaming the 'Mech the "Alley Cat" for its propensity to conduct dark alley-way "muggings. Demand for the Panther continued to increase, forcing Alshain to build a secondary factory on Jarett to keep up. In an ironic twist both factories fell within the borders of the Free Rasalhague Republic following its creation in 3034, transferring ownership to the new state, and soon the Panther became a mainstay of the KungsArmé. The situation did not last long however following the invasion of the Clans, and both planets were swiftly conquered by Clan Ghost Bear. While Alshain Weapons crash-built a new line on Tok Do in 3053, they could not maintain their pre-invasion production levels and focused on spare parts and refit kits instead. Eventually Wakazashi Enterprises bought the production license for the Panther and began rolling out new variants from its New Samarkand factory. These have gone on to serve in every DCMS unit since, including the bloody years of the Jihad. +history:The original PNT-8Z model underwent a revision after the disastrous Battle of St. John in 2759, when it was revealed that its main weapon, a Tronel Large Laser, was inefficient in both range and firepower for the immense waste heat generated. The Draconis Combine inherited Alshain Weapons' Panther factory on New Oslo when the Star League dissolved and quickly put the production line to work building new Panthers for the DCMS. Their first large-scale use by Kurita warriors came during the First Succession War in the battle for Quentin, when the 2nd Legion of Vega used their Panthers to severely maul the slower, heavier 'Mechs of the 42nd Avalon Hussars while avoiding return fire. Throughout the Succession Wars, the Combine was the only significant user of the Panther, often pairing it with the Jenner in a deadly combination of speed and firepower; though the other Successor States employed Panthers in smaller numbers, these were either the result of battlefield salvage or older League-era 8Z models. The Panther also proved itself a deadly urban combatant, using its mobility to easily navigate the more restricted space of a city environment and take out heavier opponents from rooftop sniping perches with its main weapon. Lyran MechWarriors eventually took to nicknaming the 'Mech the "Alley Cat" for its propensity to conduct dark alley-way "muggings. Demand for the Panther continued to increase, forcing Alshain to build a secondary factory on Jarett to keep up. In an ironic twist both factories fell within the borders of the Free Rasalhague Republic following its creation in 3034, transferring ownership to the new state, and soon the Panther became a mainstay of the KungsArmé. The situation did not last long however following the invasion of the Clans, and both planets were swiftly conquered by Clan Ghost Bear. While Alshain Weapons crash-built a new line on Tok Do in 3053, they could not maintain their pre-invasion production levels and focused on spare parts and refit kits instead. Eventually Wakazashi Enterprises bought the production license for the Panther and began rolling out new variants from its New Samarkand factory. These have gone on to serve in every DCMS unit since, including the bloody years of the Jihad. manufacturer:Field Refit primaryfactory:Field Refit diff --git a/megameklab/data/mechfiles/mechs/3085u/Cutting Edge/Panther PNT-13K.mtf b/megameklab/data/mechfiles/mechs/3085u/Cutting Edge/Panther PNT-13K.mtf index 25b1c5c4a..e3f253440 100644 --- a/megameklab/data/mechfiles/mechs/3085u/Cutting Edge/Panther PNT-13K.mtf +++ b/megameklab/data/mechfiles/mechs/3085u/Cutting Edge/Panther PNT-13K.mtf @@ -161,7 +161,7 @@ capabilities:Luckily the Panther had also proved itself to be quite hardy, sport deployment:Designed before the Jihad this version only entered service after that war started. An XL engine increases the 'Mech's top speed to 86 km/h while eight Improved Jump Jets maximizes mobility on the battlefield. An XL Gyro allows the PNT-13K to carry a SRM-4 and a Plasma Rifle. -history:The original PNT-8Z model underwent a revision after the disastrous Battle of St. John in 2759, when it was revealed that its main weapon, a Tronel Large Laser, was inefficient in both range and firepower for the immense waste heat generated. The Draconis Combine inherited Alshain Weapons' Panther factory on New Oslo when the Star League dissolved and quickly put the production line to work building new Panthers for the DCMS. Their first large-scale use by Kurita warriors came during the First Succession War in the battle for Quentin, when the 2nd Legion of Vega used their Panthers to severely maul the slower, heavier 'Mechs of the 42nd Avalon Hussars while avoiding return fire. Throughout the Succession Wars, the Combine was the only significant user of the Panther, often pairing it with the Jenner in a deadly combination of speed and firepower; though the other Successor States employed Panthers in smaller numbers, these were either the result of battlefield salvage or older League-era 8Z models. The Panther also proved itself a deadly urban combatant, using its mobility to easily navigate the more restricted space of a city environment and take out heavier opponents from rooftop sniping perches with its main weapon. Lyran MechWarriors eventually took to nicknaming the 'Mech the "Alley Cat" for its propensity to conduct dark alley-way "muggings. Demand for the Panther continued to increase, forcing Alshain to build a secondary factory on Jarett to keep up. In an ironic twist both factories fell within the borders of the Free Rasalhague Republic following its creation in 3034, transferring ownership to the new state, and soon the Panther became a mainstay of the KungsArmé. The situation did not last long however following the invasion of the Clans, and both planets were swiftly conquered by Clan Ghost Bear. While Alshain Weapons crash-built a new line on Tok Do in 3053, they could not maintain their pre-invasion production levels and focused on spare parts and refit kits instead. Eventually Wakazashi Enterprises bought the production license for the Panther and began rolling out new variants from its New Samarkand factory. These have gone on to serve in every DCMS unit since, including the bloody years of the Jihad. +history:The original PNT-8Z model underwent a revision after the disastrous Battle of St. John in 2759, when it was revealed that its main weapon, a Tronel Large Laser, was inefficient in both range and firepower for the immense waste heat generated. The Draconis Combine inherited Alshain Weapons' Panther factory on New Oslo when the Star League dissolved and quickly put the production line to work building new Panthers for the DCMS. Their first large-scale use by Kurita warriors came during the First Succession War in the battle for Quentin, when the 2nd Legion of Vega used their Panthers to severely maul the slower, heavier 'Mechs of the 42nd Avalon Hussars while avoiding return fire. Throughout the Succession Wars, the Combine was the only significant user of the Panther, often pairing it with the Jenner in a deadly combination of speed and firepower; though the other Successor States employed Panthers in smaller numbers, these were either the result of battlefield salvage or older League-era 8Z models. The Panther also proved itself a deadly urban combatant, using its mobility to easily navigate the more restricted space of a city environment and take out heavier opponents from rooftop sniping perches with its main weapon. Lyran MechWarriors eventually took to nicknaming the 'Mech the "Alley Cat" for its propensity to conduct dark alley-way "muggings. Demand for the Panther continued to increase, forcing Alshain to build a secondary factory on Jarett to keep up. In an ironic twist both factories fell within the borders of the Free Rasalhague Republic following its creation in 3034, transferring ownership to the new state, and soon the Panther became a mainstay of the KungsArmé. The situation did not last long however following the invasion of the Clans, and both planets were swiftly conquered by Clan Ghost Bear. While Alshain Weapons crash-built a new line on Tok Do in 3053, they could not maintain their pre-invasion production levels and focused on spare parts and refit kits instead. Eventually Wakazashi Enterprises bought the production license for the Panther and began rolling out new variants from its New Samarkand factory. These have gone on to serve in every DCMS unit since, including the bloody years of the Jihad. manufacturer:Wakazashi Enterprises primaryfactory:New Samarkand diff --git a/megameklab/data/mechfiles/mechs/3085u/Cutting Edge/Wolfhound WLF-3M.mtf b/megameklab/data/mechfiles/mechs/3085u/Cutting Edge/Wolfhound WLF-3M.mtf index ca1831a1d..06f5b5ad7 100644 --- a/megameklab/data/mechfiles/mechs/3085u/Cutting Edge/Wolfhound WLF-3M.mtf +++ b/megameklab/data/mechfiles/mechs/3085u/Cutting Edge/Wolfhound WLF-3M.mtf @@ -159,7 +159,7 @@ capabilities:Archon Katrina Steiner directed TharHes Industries to create a Batt deployment:A post-Jihad field refit of the WLF-3S in use among the states of the former Free Worlds League, the 3M removes two double heat sinks and one half ton of armor to replace the ER PPC, ER medium lasers, and ER small laser with a right arm-mounted light Gauss rifle with a single ton of reloads. -history:The Kell Hounds were the first unit chosen to field-test the Wolfhound in combat because of their intense loyalty to House Steiner, followed shortly after by Wolf's Dragoons. The design was put through its paces during the Fourth Succession War, where it outperformed all expectations. This was especially true when the Wolfhound faced its intended targets, hitting the Jenner beyond its capacity to return fire while closing the distance on the Panther to get inside range of its primary armament. After the war's triumphant conclusion, the Federated Commonwealth purchased more Wolfhounds to outfit its troops, and the design was utilized again during the War of 3039. Wolfhounds sustained substantially fewer deaths than other 'Mechs during that fight, and as a result, only a few were captured by the Combine. While awed by the 'Mech, the Kuritans were too proud to replicate it, instead relying on captured examples to help create the Wolf Trap particularly to defeat the 'Mech. Arc-Royal MechWorks was eventually recruited in to construct Wolfhounds under license from TharHes, and the recovery of lostech owing to the Helm Memory Core allowed for the production of a more advanced model to combat the Clan Invasion. Sadly, it took too long for TharHes' factories to be retooled in order to build the WLF-2 model, which was introduced in 3052, before ComStar ended the invasion with the Battle of Tukayyid. These updated Wolfhounds were still created for both FedCom member states, but once the Lyran Alliance was formed, TharHes manufacturers began creating the newer WLF-3S variant. This new type was only distributed to units loyal to the Lyran state, and so fought on Katherine Steiner-side Davion's during the FedCom Civil War. During the Jihad, the Word of Blake launched a crushing attack on Tharkad, essentially shutting down TharHes' Wolfhound factory line; in response, Arc-Royal expanded production and created the WLF-4 variant to compensate for allied troops combating the Blakists' losses. +history:The Kell Hounds were the first unit chosen to field-test the Wolfhound in combat because of their intense loyalty to House Steiner, followed shortly after by Wolf's Dragoons. The design was put through its paces during the Fourth Succession War, where it outperformed all expectations. This was especially true when the Wolfhound faced its intended targets, hitting the Jenner beyond its capacity to return fire while closing the distance on the Panther to get inside range of its primary armament. After the war's triumphant conclusion, the Federated Commonwealth purchased more Wolfhounds to outfit its troops, and the design was utilized again during the War of 3039. Wolfhounds sustained substantially fewer deaths than other 'Mechs during that fight, and as a result, only a few were captured by the Combine. While awed by the 'Mech, the Kuritans were too proud to replicate it, instead relying on captured examples to help create the Wolf Trap particularly to defeat the 'Mech. Arc-Royal MechWorks was eventually recruited in to construct Wolfhounds under license from TharHes, and the recovery of lostech owing to the Helm Memory Core allowed for the production of a more advanced model to combat the Clan Invasion. Sadly, it took too long for TharHes' factories to be retooled in order to build the WLF-2 model, which was introduced in 3052, before ComStar ended the invasion with the Battle of Tukayyid. These updated Wolfhounds were still created for both FedCom member states, but once the Lyran Alliance was formed, TharHes manufacturers began creating the newer WLF-3S variant. This new type was only distributed to units loyal to the Lyran state, and so fought on Katherine Steiner-Davion's side during the FedCom Civil War. During the Jihad, the Word of Blake launched a crushing attack on Tharkad, essentially shutting down TharHes' Wolfhound factory line; in response, Arc-Royal expanded production and created the WLF-4 variant to compensate for allied troops combating the Blakists' losses. manufacturer:Field Refit primaryfactory:Various diff --git a/megameklab/data/mechfiles/mechs/3085u/Cutting Edge/Wolfhound WLF-5.mtf b/megameklab/data/mechfiles/mechs/3085u/Cutting Edge/Wolfhound WLF-5.mtf index 0eadbd3ee..bd3f3fb7c 100644 --- a/megameklab/data/mechfiles/mechs/3085u/Cutting Edge/Wolfhound WLF-5.mtf +++ b/megameklab/data/mechfiles/mechs/3085u/Cutting Edge/Wolfhound WLF-5.mtf @@ -162,7 +162,7 @@ capabilities:Archon Katrina Steiner directed TharHes Industries to create a Batt deployment:A post-Jihad variant produced on Arc-Royal alongside the WLF-4W in 3079, the WLF-5 is built on an endo steel frame and is powered by the larger 245-rated XL engine to increase its ground speed by 20 km/h, capable of almost 150 km/h in short bursts due to the inclusion of MASC. Replacing the armament of lasers with an array of PPCs; a right arm-mounted Hound's-tooth snub-nose PPC is supported by a pair of torso-mounted Defiance 1002 light PPCs. -history:The Kell Hounds were the first unit chosen to field-test the Wolfhound in combat because of their intense loyalty to House Steiner, followed shortly after by Wolf's Dragoons. The design was put through its paces during the Fourth Succession War, where it outperformed all expectations. This was especially true when the Wolfhound faced its intended targets, hitting the Jenner beyond its capacity to return fire while closing the distance on the Panther to get inside range of its primary armament. After the war's triumphant conclusion, the Federated Commonwealth purchased more Wolfhounds to outfit its troops, and the design was utilized again during the War of 3039. Wolfhounds sustained substantially fewer deaths than other 'Mechs during that fight, and as a result, only a few were captured by the Combine. While awed by the 'Mech, the Kuritans were too proud to replicate it, instead relying on captured examples to help create the Wolf Trap particularly to defeat the 'Mech. Arc-Royal MechWorks was eventually recruited in to construct Wolfhounds under license from TharHes, and the recovery of lostech owing to the Helm Memory Core allowed for the production of a more advanced model to combat the Clan Invasion. Sadly, it took too long for TharHes' factories to be retooled in order to build the WLF-2 model, which was introduced in 3052, before ComStar ended the invasion with the Battle of Tukayyid. These updated Wolfhounds were still created for both FedCom member states, but once the Lyran Alliance was formed, TharHes manufacturers began creating the newer WLF-3S variant. This new type was only distributed to units loyal to the Lyran state, and so fought on Katherine Steiner-side Davion's during the FedCom Civil War. During the Jihad, the Word of Blake launched a crushing attack on Tharkad, essentially shutting down TharHes' Wolfhound factory line; in response, Arc-Royal expanded production and created the WLF-4 variant to compensate for allied troops combating the Blakists' losses. +history:The Kell Hounds were the first unit chosen to field-test the Wolfhound in combat because of their intense loyalty to House Steiner, followed shortly after by Wolf's Dragoons. The design was put through its paces during the Fourth Succession War, where it outperformed all expectations. This was especially true when the Wolfhound faced its intended targets, hitting the Jenner beyond its capacity to return fire while closing the distance on the Panther to get inside range of its primary armament. After the war's triumphant conclusion, the Federated Commonwealth purchased more Wolfhounds to outfit its troops, and the design was utilized again during the War of 3039. Wolfhounds sustained substantially fewer deaths than other 'Mechs during that fight, and as a result, only a few were captured by the Combine. While awed by the 'Mech, the Kuritans were too proud to replicate it, instead relying on captured examples to help create the Wolf Trap particularly to defeat the 'Mech. Arc-Royal MechWorks was eventually recruited in to construct Wolfhounds under license from TharHes, and the recovery of lostech owing to the Helm Memory Core allowed for the production of a more advanced model to combat the Clan Invasion. Sadly, it took too long for TharHes' factories to be retooled in order to build the WLF-2 model, which was introduced in 3052, before ComStar ended the invasion with the Battle of Tukayyid. These updated Wolfhounds were still created for both FedCom member states, but once the Lyran Alliance was formed, TharHes manufacturers began creating the newer WLF-3S variant. This new type was only distributed to units loyal to the Lyran state, and so fought on Katherine Steiner-Davion's side during the FedCom Civil War. During the Jihad, the Word of Blake launched a crushing attack on Tharkad, essentially shutting down TharHes' Wolfhound factory line; in response, Arc-Royal expanded production and created the WLF-4 variant to compensate for allied troops combating the Blakists' losses. manufacturer:Arc-Royal MechWorks primaryfactory:Arc-Royal diff --git a/megameklab/data/mechfiles/mechs/3085u/ONN/Bandersnatch BNDR-01Ar.mtf b/megameklab/data/mechfiles/mechs/3085u/ONN/Bandersnatch BNDR-01Ar.mtf index 9f63722de..7b5689144 100644 --- a/megameklab/data/mechfiles/mechs/3085u/ONN/Bandersnatch BNDR-01Ar.mtf +++ b/megameklab/data/mechfiles/mechs/3085u/ONN/Bandersnatch BNDR-01Ar.mtf @@ -165,7 +165,7 @@ overview:The Bandersnatch, who receives his name from the monster mentioned in L capabilities:The Bandersnatch is built using some common components with the Marauder in an attempt to make the 'Mech cheaper and easier to repair. The 'Mech has a top speed of 64.8 kph which is average for a 'Mech of its weight. The Bandersnatch also uses double heat sinks for their superior heat dissipation capabilities, allowing a heavy weapons payload to be used by the 'Mech. Finally, the Bandersnatch carries a respectable eleven tons of armor. While not the maximum amount of armor that the chassis can handle, the 'Mech is still well protected. -deployment:A simple refit, this version carries a Guardian ECM Suite in the center torso to offset the Blakist C3i system. To make room for this system, all rear defenses have been removed except for a single ER Small Laser.[4] BV (2.0) = 1522 +deployment:A simple refit, this version carries a Guardian ECM Suite in the center torso to offset the Blakist C3i system. To make room for this system, all rear defenses have been removed except for a single ER Small Laser. BV (2.0) = 1522 manufacturer:Bander BattleMechs, Kressly WarWorks primaryfactory:Terra Firma (Bander BattleMechs), Epsilon Eridani (Kressly WarWorks) diff --git a/megameklab/data/mechfiles/mechs/3085u/ONN/Black Hawk (Nova) U.mtf b/megameklab/data/mechfiles/mechs/3085u/ONN/Black Hawk (Nova) U.mtf index 59a27ab88..cc8e9b849 100644 --- a/megameklab/data/mechfiles/mechs/3085u/ONN/Black Hawk (Nova) U.mtf +++ b/megameklab/data/mechfiles/mechs/3085u/ONN/Black Hawk (Nova) U.mtf @@ -169,7 +169,7 @@ overview:The Nova is a versatile medium OmniMech that is capable of acting as a capabilities:Equipped with a 250 XL Model SF-2 Fusion Engine, the Nova has a ground speed of 86.4 km/h that allows it to keep up with most heavy and assault 'Mechs while being outpaced by most lighter 'Mechs. However, the Nova remains very maneuverable through the use of five jump jets, allowing the Nova to jump up to 150 meters. The fourteen double heat sinks that the Nova mounts are barely sufficient to handle its heavy heat load of its variants. The Nova is also protected by ten tons of armor, providing the 'Mech with ninety-six percent of its maximum armor protection. -deployment:This unusual configuration appears to be used to support boarding actions against enemy spacecraft. Two torso mounted Liquid Storage tanks provide additional reaction mass for the jump jets. Eight machine guns can rapidly destroy enemy battle armor, while three Heavy Medium Lasers and three Micro Pulse Lasers scour the armor off of hardened targets. To keep track of enemy units, the U configuration carries a Light Active Probe, and a Clan ECM Suite interferes with enemy targeting systems. The right arm carries a Spot Welder presumably to seal hull breaches. Strangely, this configuration carries a Sword, marking the first time a Clan unit has carried a dedicated melee weapon +deployment:This unusual configuration appears to be used to support boarding actions against enemy spacecraft. Two torso mounted Liquid Storage tanks provide additional reaction mass for the jump jets. Eight machine guns can rapidly destroy enemy battle armor, while three Heavy Medium Lasers and three Micro Pulse Lasers scour the armor off of hardened targets. To keep track of enemy units, the U configuration carries a Light Active Probe, and a Clan ECM Suite interferes with enemy targeting systems. The right arm carries a Spot Welder presumably to seal hull breaches. Strangely, this configuration carries a Sword, marking the first time a Clan unit has carried a dedicated melee weapon. history:The Black Hawk's debut battle was the combined assault on Kindraa Smythe-Jewel on Foster in 2872 launched by the Hell's Horses, Clan Coyote and Kindraa Payne that saw the Smythe-Jewels wiped out as a faction. However, the number of Novas has been diminishing. Only spare parts have been in production since 2921. Designed as an early OmniMech by Clan Hell's Horses, the Nova was produced at the famous Tokasha Mechworks beginning in 2870. At the time of its introduction, the Nova was designed for infantry support, and was the first OmniMech designed with hardpoints allowing Elementals to easily mount and dismount the chassis. However, after Tokasha was taken by Clan Ghost Bear during the Battle of Tokasha, production of the Nova ceased. Since 2921, every Clan has acquired Nova OmniMechs as isorla. Although the last Nova factory was replaced to create Pouncers, the very few remaining in Clan Space have gotten into the hands of Aggressor Mechwarriors. diff --git a/megameklab/data/mechfiles/mechs/3085u/ONN/Cauldron-Born (Ebon Jaguar) U.mtf b/megameklab/data/mechfiles/mechs/3085u/ONN/Cauldron-Born (Ebon Jaguar) U.mtf index 3473f6da9..9bb74692e 100644 --- a/megameklab/data/mechfiles/mechs/3085u/ONN/Cauldron-Born (Ebon Jaguar) U.mtf +++ b/megameklab/data/mechfiles/mechs/3085u/ONN/Cauldron-Born (Ebon Jaguar) U.mtf @@ -160,7 +160,7 @@ overview:Introduced in 3049 to address flaws in the venerable Hellbringer, by Op capabilities:Intended for use underwater, this variant carries five experimental UMUs. Each arm carries a single Large Pulse Laser and ER Small Laser to capitalize on armor breaches inflicted by the pair of LRT-15s carried in the torso. -history:Facing it for the first time when engaging the First Jaguar Guards Cluster in the Kado-Guchi Valley, the 'Mech's ability to take damage and remain operational led the Inner Sphere warriors who fought it to call it the Cauldron-Born after the unstoppable zombies of Irish myth. Paradoxically many of the other Clans also used the Inner Sphere Cauldron-Born reporting name, having first learned detailed information of the design from Inner Sphere sources. y Operation BULLDOG the Cauldron-Born made up a large proportion of the heavy 'Mechs of the rebuilding Smoke Jaguars, and following their Annihilation the design proliferated the remaining Clans, save the Jade Falcons, Wolves and Coyotes who continued to favor the Hellbringer. Following the Wars of Reaving the Ebon Jaguar had finally supplanted the Hellbringer in most Homeworld Clans, save the Coyotes who remained loyal to redeeming the honor of the design. +history:Facing it for the first time when engaging the First Jaguar Guards Cluster in the Kado-Guchi Valley, the 'Mech's ability to take damage and remain operational led the Inner Sphere warriors who fought it to call it the Cauldron-Born after the unstoppable zombies of Irish myth. Paradoxically many of the other Clans also used the Inner Sphere Cauldron-Born reporting name, having first learned detailed information of the design from Inner Sphere sources. By Operation BULLDOG the Cauldron-Born made up a large proportion of the heavy 'Mechs of the rebuilding Smoke Jaguars, and following their Annihilation the design proliferated the remaining Clans, save the Jade Falcons, Wolves and Coyotes who continued to favor the Hellbringer. Following the Wars of Reaving the Ebon Jaguar had finally supplanted the Hellbringer in most Homeworld Clans, save the Coyotes who remained loyal to redeeming the honor of the design. manufacturer:Huntress Manufacturing Plant DL-6 primaryfactory:Huntress diff --git a/megameklab/data/mechfiles/mechs/3085u/ONN/Charger CGR-3Kr.mtf b/megameklab/data/mechfiles/mechs/3085u/ONN/Charger CGR-3Kr.mtf index b45307652..a677b6359 100644 --- a/megameklab/data/mechfiles/mechs/3085u/ONN/Charger CGR-3Kr.mtf +++ b/megameklab/data/mechfiles/mechs/3085u/ONN/Charger CGR-3Kr.mtf @@ -161,7 +161,7 @@ Jump Jet overview:The Charger is seen as an example of abject failure in BattleMech design. Wells Technologies originally wanted to produce an ultra-heavy scout 'Mech for the Star League Defense Force that was not only fast but could survive contact with the enemy. -capabilities:The Charger is seen as an example of abject failure in BattleMech design. Wells Technologies originally wanted to produce an ultra-heavy scout 'Mech for the Star League Defense Force that was not only fast but could survive contact with the enemy. This was to be the 'Mech's downfall, as its popgun laser array proved to be quite laughable, capable of little more than fighting infantry and light combat vehicles. Its armoring, while respectable, could not stand up to sustained punishment, which meant if the 'Mech got too close to heavy combat or trapped by superior numbers it could be shot to pieces. +capabilities:This was to be the 'Mech's downfall, as its popgun laser array proved to be quite laughable, capable of little more than fighting infantry and light combat vehicles. Its armoring, while respectable, could not stand up to sustained punishment, which meant if the 'Mech got too close to heavy combat or trapped by superior numbers it could be shot to pieces. deployment:A Jihad-era field refit based on the Combine's CGR-3K, this variant used Triple Strength Myomer and a Sword to create a close-combat 'Mech. To keep the TSM active it used the heat generated from its impressive arsenal: a Light PPC, Snub-Nose PPC, a pair of ER medium lasers, and one each of a small laser, ER small laser, and medium laser. Like its progenitor, it could jump 150 meters. The weapons were also more accurate due to the presence of a Targeting Computer. Light Ferro-Fibrous armor protected the chassis. diff --git a/megameklab/data/mechfiles/mechs/3085u/ONN/Fenris (Ice Ferret) U.mtf b/megameklab/data/mechfiles/mechs/3085u/ONN/Fenris (Ice Ferret) U.mtf index f25901d5b..06ea0c675 100644 --- a/megameklab/data/mechfiles/mechs/3085u/ONN/Fenris (Ice Ferret) U.mtf +++ b/megameklab/data/mechfiles/mechs/3085u/ONN/Fenris (Ice Ferret) U.mtf @@ -154,13 +154,13 @@ Clan Endo Steel -Empty- -Empty- -overview:A powerful medium scout and recon 'Mech, the Ice Ferret was regarded as something of a foreign concept when it was first encountered by Inner Sphere forces. Referred to as the Fenris by Inner Sphere forces, the Ice Ferret is a very capable medium scout OmniMech, which is well armored and fast, and can be configured as a strike/headhunter or as a fire-support 'Mech.[ +overview:A powerful medium scout and recon 'Mech, the Ice Ferret was regarded as something of a foreign concept when it was first encountered by Inner Sphere forces. Referred to as the Fenris by Inner Sphere forces, the Ice Ferret is a very capable medium scout OmniMech, which is well armored and fast, and can be configured as a strike/headhunter or as a fire-support 'Mech. capabilities:An underwater specialist, this configuration carries an SRT-4, LRT-5, and a pair of ER Medium Lasers. To maneuver quickly through the water, it's equipped with seven UMUs. deployment:The Ice Ferret is built on a lightweight Endo Steel chassis that saves weight and is powered by a massive 360 XL engine that gives the Ice Ferret a top speed of 129.6 km/h and also accounts for one third of the 'Mech's total weight. The Ice Ferret has twelve double heat sinks mounted on the chassis and is protected by seven and a half tons of Ferro-Fibrous armor, giving the 'Mech almost the maximum amount of armor protection for its weight. -history:Deployed extensively by Clan Wolf, the Ice Ferret was actually designed to combat the pride of Clan Wolf, the Timber Wolf OmniMech. Originally named the Wolf Hunter, the Ice Ferret was first produced in the mid-2900s by Clan Ice Hellion, but performed poorly due to lack-luster weapon configurations. Annoyed by the constant Hellion harassment, but appreciating the potential of the new OmniMech, Clan Wolf warriors eventually began challenging for the OmniMech, and eventually won the production facility for the design. The Wolves renamed the design after the only natural predator of the Ice Hellion, the Ice Ferret, and altered the configurations to improve performance. The Ice Hellions would maintain a large number of the "Wolf Hunters" in their touman during their existence. However, in the early years of the Jihad era, the Ice Ferret's few production facilities would end up being destroyed during the chaotic fighting in Clan Homeworlds. The design would end up being phased out of use and replaced by the Viper. +history:Deployed extensively by Clan Wolf, the Ice Ferret was actually designed to combat the pride of Clan Wolf, the Timber Wolf OmniMech. Originally named the Wolf Hunter, the Ice Ferret was first produced in the mid-2900s by Clan Ice Hellion, but performed poorly due to lack-luster weapon configurations. Annoyed by the constant Hellion harassment, but appreciating the potential of the new OmniMech, Clan Wolf warriors eventually began challenging for the OmniMech, and eventually won the production facility for the design. The Wolves renamed the design after the only natural predator of the Ice Hellion, the Ice Ferret, and altered the configurations to improve performance. The Ice Hellions would maintain a large number of the "Wolf Hunters" in their touman during their existence. However, in the early years of the Jihad era, the Ice Ferret's few production facilities would end up being destroyed during the chaotic fighting in Clan Homeworlds. The design would end up being phased out of use and replaced by the Viper. manufacturer:W-7 Facilities, Wolf Clan Site 3, Assault Tech Industries primaryfactory:Tranquil, Arc-Royal, Donegal systemmanufacturer:CHASSIS:Hellion Medium Gamma ES diff --git a/megameklab/data/mechfiles/mechs/3085u/ONN/Jenner JR7-C4.mtf b/megameklab/data/mechfiles/mechs/3085u/ONN/Jenner JR7-C4.mtf index 05788a105..d580d9bec 100644 --- a/megameklab/data/mechfiles/mechs/3085u/ONN/Jenner JR7-C4.mtf +++ b/megameklab/data/mechfiles/mechs/3085u/ONN/Jenner JR7-C4.mtf @@ -160,7 +160,7 @@ capabilities:Five Smithson Lifter jump jets, two in each side torso and one in t deployment:This variant uses an experimental C3 Boosted Slave to share targeting data. Its weapons have been removed and replaced with a pair of MML-5 launchers. Ten Double Heat Sinks keep it cool, and Heavy Ferro-Fibrous armor increases protection. -history:The Jenner became the standard light warhorse of the DCMS with the outbreak of the First Succession War, though its reputation would be forever tarnished following its role in the Kentares Massacre. The Jenner became the standard light warhorse of the DCMS with the outbreak of the First Succession War, though its reputation would be forever tarnished following its role in the Kentares Massacre. Construction of new Jenners continued at Diplan MechYard's factory on Ozawa until a raw mineral shortage caused a halt in 2815, though they continued to produce new chassis. In 2823 production resumed on Ozawa, with some three thousand chassis shipped to Diplan's subsidiary on Luthien for final assembly, which itself was retooling to begin full-scale production; by 2830 both production lines were producing 1,350 Jenners a year. The sheer destruction of the Succession Wars finally took their toll when the last Jenner factory was destroyed in 2848, though so many Jenners had been produced by then that nearly every DCMS battalion had at least one of these 'Mechs well into the War of 3039. While the other Successor States eventually managed to procure operational Jenners (every AFFS regiment along the Combine border had at least one), the design remained in predominant use by House Kurita. +history:Construction of new Jenners continued at Diplan MechYard's factory on Ozawa until a raw mineral shortage caused a halt in 2815, though they continued to produce new chassis. In 2823 production resumed on Ozawa, with some three thousand chassis shipped to Diplan's subsidiary on Luthien for final assembly, which itself was retooling to begin full-scale production; by 2830 both production lines were producing 1,350 Jenners a year. The sheer destruction of the Succession Wars finally took their toll when the last Jenner factory was destroyed in 2848, though so many Jenners had been produced by then that nearly every DCMS battalion had at least one of these 'Mechs well into the War of 3039. While the other Successor States eventually managed to procure operational Jenners (every AFFS regiment along the Combine border had at least one), the design remained in predominant use by House Kurita. manufacturer:Luthien Armor Works, Diplan 'Mechyards, Luthien Armor Works, Luthien Armor Works, Diplan 'Mechyards primaryfactory:Luthien, Abiy Adi, New Samarkand, Ozawa diff --git a/megameklab/data/mechfiles/mechs/3085u/ONN/King Crab KGC-005r.mtf b/megameklab/data/mechfiles/mechs/3085u/ONN/King Crab KGC-005r.mtf index d8b670e76..57deeafd9 100644 --- a/megameklab/data/mechfiles/mechs/3085u/ONN/King Crab KGC-005r.mtf +++ b/megameklab/data/mechfiles/mechs/3085u/ONN/King Crab KGC-005r.mtf @@ -154,8 +154,8 @@ IS Endo Steel -Empty- overview:The King Crab has been a horror on the battlefield since its introduction just before the old Star League's demise, and it is well known for its ability to quickly kill most BattleMechs under eighty tons. -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,[6] and has been described as a "notorious hangar queen". -deployment:This simple field refit of the 005, a result of the Jihad and efforts to upgrade old designs with what was available, was introduced in 3071. By downgrading to a C3 slave, removing the large laser, one of the Streak launchers, and a half-ton of armor, engineers were able to cram a Heavy PPC into the torso.[ +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:This simple field refit of the 005, a result of the Jihad and efforts to upgrade old designs with what was available, was introduced in 3071. By downgrading to a C3 slave, removing the large laser, one of the Streak launchers, and a half-ton of armor, engineers were able to cram a Heavy PPC into the 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. manufacturer:Field Refit primaryfactory:Various diff --git a/megameklab/data/mechfiles/mechs/3085u/ONN/Mad Cat (Timber Wolf) U.mtf b/megameklab/data/mechfiles/mechs/3085u/ONN/Mad Cat (Timber Wolf) U.mtf index ae1af6629..46e66c126 100644 --- a/megameklab/data/mechfiles/mechs/3085u/ONN/Mad Cat (Timber Wolf) U.mtf +++ b/megameklab/data/mechfiles/mechs/3085u/ONN/Mad Cat (Timber Wolf) U.mtf @@ -157,11 +157,11 @@ Clan Endo Steel -Empty- -Empty- -overview:overview:The Timber Wolf is a fast, heavy OmniMech. A signature design of the Clans' military might, it was arguably the first Clan OmniMech encountered by Inner Sphere forces (as opposed to periphery forces) on The Rock in 3049 by Phelan Kell. The Timber Wolf is vastly more powerful than either the Marauder or the Catapult. It uses its speed and firepower to engage an enemy at the range of its choosing. When first encountered by Inner Sphere forces the idea that a heavy 'Mech could move so swiftly while being as heavily armed and armored as the Timber Wolf was inconceivable. With its twelve tons of Ferro-Fibrous armor and arsenal that rivaled that of most assault 'Mechs of the era, it was completely alien to Inner Sphere military planners, commanders, and even the Precentor Martial of ComStar. Its technological secrets have since been reverse-engineered by the Inner Sphere. +overview:The Timber Wolf is a fast, heavy OmniMech. A signature design of the Clans' military might, it was arguably the first Clan OmniMech encountered by Inner Sphere forces (as opposed to periphery forces) on The Rock in 3049 by Phelan Kell. The Timber Wolf is vastly more powerful than either the Marauder or the Catapult. It uses its speed and firepower to engage an enemy at the range of its choosing. When first encountered by Inner Sphere forces the idea that a heavy 'Mech could move so swiftly while being as heavily armed and armored as the Timber Wolf was inconceivable. With its twelve tons of Ferro-Fibrous armor and arsenal that rivaled that of most assault 'Mechs of the era, it was completely alien to Inner Sphere military planners, commanders, and even the Precentor Martial of ComStar. Its technological secrets have since been reverse-engineered by the Inner Sphere. capabilities:Similar to the primary configuration's armament, this version is used in underwater combat. In addition to a BattleMech HarJel System that protects the torsos from hull breaches, the Timber Wolf U also carries four UMUs that allow it to cruise through the water at 43km/h. The weapons are restricted to a pair of Artemis IV-enhanced LRT-15s on each shoulder, while each arm carries an ER Large Laser and ER Micro Laser. -deployment:First introduced in 2945, the Timber Wolf was designed by Clan Wolf as a second generation OmniMech along with the Gargoyle and the Naga to replace the aging Woodsman. While the Gargoyle may have been a very capable, fast assault OmniMech, and the Naga may have been an excellent fire-support OmniMech, Clan Wolf (and indeed every other Clan) instantly realized the value of the Timber Wolf; thus, production rights to the Timber Wolf were jealously (and successfully) defended. Only through trade, gifts and battlefield salvage has the Timber Wolf entered the armies of other Clans. Until the invasion of the Inner Sphere, production of the Timber Wolf has been limited to a single facility on Strana Mechty. Despite it's prominence among the Wolves during the Clan Invasion, Refusal War and Word of Blake Jihad, the Timber Wolf became increasingly rare following the sundering of ties with the Homeworld Clans during the Wars of Reaving and Blakist scouring of Tamar. Being built by hand at W-7 plant on Weingarten as of 3080, with some parts even being individually machined due to missing data,[1] attrition vastly outstripped supply as the Wolves looked toward other designs. When Alaric Ward forged the Wolf Empire, he left the W-7 facilities to Clan Hell's Horses and ordered the Kallon plant on Thermopolis be retooled for Timber Wolf production, restoring it's position within the Wolves touman. +deployment:First introduced in 2945, the Timber Wolf was designed by Clan Wolf as a second generation OmniMech along with the Gargoyle and the Naga to replace the aging Woodsman. While the Gargoyle may have been a very capable, fast assault OmniMech, and the Naga may have been an excellent fire-support OmniMech, Clan Wolf (and indeed every other Clan) instantly realized the value of the Timber Wolf; thus, production rights to the Timber Wolf were jealously (and successfully) defended. Only through trade, gifts and battlefield salvage has the Timber Wolf entered the armies of other Clans. Until the invasion of the Inner Sphere, production of the Timber Wolf has been limited to a single facility on Strana Mechty. Despite it's prominence among the Wolves during the Clan Invasion, Refusal War and Word of Blake Jihad, the Timber Wolf became increasingly rare following the sundering of ties with the Homeworld Clans during the Wars of Reaving and Blakist scouring of Tamar. Being built by hand at W-7 plant on Weingarten as of 3080, with some parts even being individually machined due to missing data, attrition vastly outstripped supply as the Wolves looked toward other designs. When Alaric Ward forged the Wolf Empire, he left the W-7 facilities to Clan Hell's Horses and ordered the Kallon plant on Thermopolis be retooled for Timber Wolf production, restoring it's position within the Wolves touman. history:Vaguely resembling a cross-over between the MAD (Marauder) and CAT (Catapult) series, the Timber Wolf was tagged with the Inner Sphere reporting name Mad Cat on first contact. (The targeting computer on Phelan Kell's Wolfhound switched between MAD and CAT when trying to identify it; upon analyzing the data recording from Kell's 'Mech, Precentor Martial Anastasius Focht later officially designated it "Mad Cat". diff --git a/megameklab/data/mechfiles/mechs/3085u/ONN/UrbanMech UM-AIV.mtf b/megameklab/data/mechfiles/mechs/3085u/ONN/UrbanMech UM-AIV.mtf index 9e69db627..0522dbaff 100644 --- a/megameklab/data/mechfiles/mechs/3085u/ONN/UrbanMech UM-AIV.mtf +++ b/megameklab/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 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. manufacturer:Refit primaryfactory:Various diff --git a/megameklab/data/mechfiles/mechs/3085u/ONN/UrbanMech UM-R80.mtf b/megameklab/data/mechfiles/mechs/3085u/ONN/UrbanMech UM-R80.mtf index be7c2737d..95597a1c6 100644 --- a/megameklab/data/mechfiles/mechs/3085u/ONN/UrbanMech UM-R80.mtf +++ b/megameklab/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 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. manufacturer:Hellespont Industrials primaryfactory:Betelgeuse diff --git a/megameklab/data/mechfiles/mechs/3085u/ONN/Vulture (Mad Dog) U.mtf b/megameklab/data/mechfiles/mechs/3085u/ONN/Vulture (Mad Dog) U.mtf index 92cdec719..e2423205a 100644 --- a/megameklab/data/mechfiles/mechs/3085u/ONN/Vulture (Mad Dog) U.mtf +++ b/megameklab/data/mechfiles/mechs/3085u/ONN/Vulture (Mad Dog) U.mtf @@ -158,7 +158,7 @@ UMU (OMNIPOD) overview:The Mad Dog is a heavy Clan OmniMech used for long-range indirect fire support. With hunched shoulders, a protruding head, and reverse-jointed legs, the Mad Dog resembles a vulture, so much so that it was codenamed Vulture and Hagetaka ("Vulture" in Japanese) by the Inner Sphere forces which first encountered it. capabilities:An underwater configuration, this version uses BattleMech HarJel System to prevent hull breaches. It's equipped with five UMUs to maintain a high cruising speed underwater. Its weaponry consists of twin LRT-15s with Artemis IV guidance and each arm carries a Medium Pulse Laser and ER Medium Laser. -deployment:The name also fit the battlefield role of the Mad Dog; the main role of the Mad Dog is to act as a support 'Mech, and it often holds a hill maintaining constant watch over the entire battlefield, like a vulture waiting for its prey. With its ample firepower and decent speed of 86.4 km/h, it makes a highly mobile firing platform, and as such has spread to near ubiquity among the forces deployed by the Clans, although the design is favored more by Clan Ghost Bear MechWarriors. The Mad Dog carries eight and a half tons of Ferro-Fibrous armor for decent protection, although it will not be able to stand up to heavy fire. +deployment:The name also fit the battlefield role of the Mad Dog; to act as a support 'Mech, and it often holds a hill maintaining constant watch over the entire battlefield, like a vulture waiting for its prey. With its ample firepower and decent speed of 86.4 km/h, it makes a highly mobile firing platform, and as such has spread to near ubiquity among the forces deployed by the Clans, although the design is favored more by Clan Ghost Bear MechWarriors. The Mad Dog carries eight and a half tons of Ferro-Fibrous armor for decent protection, although it will not be able to stand up to heavy fire. history:The Mad Dog was designed by Clan Smoke Jaguar as a second generation OmniMech based on the original heavy OmniMech Lupus of Clan Coyote. The Mad Dog also used some of the same moulds of the Clan Wolf Timber Wolf OmniMech. However, despite using some of the same moulds (which might be viewed as high praise), the Mad Dog was named as a slur to the Lupus and Timber Wolf, and to Clans Wolf and Coyote. Because of its widespread production, most Clans maintain a large number of Mad Dogs in their toumans. manufacturer:Various,Svarstaad Industriplex Beta primaryfactory:Various,Svarstaad diff --git a/megameklab/data/mechfiles/mechs/3085u/Phoenix/Archer ARC-6S.mtf b/megameklab/data/mechfiles/mechs/3085u/Phoenix/Archer ARC-6S.mtf index 2184a6794..58f5e2f46 100644 --- a/megameklab/data/mechfiles/mechs/3085u/Phoenix/Archer ARC-6S.mtf +++ b/megameklab/data/mechfiles/mechs/3085u/Phoenix/Archer ARC-6S.mtf @@ -163,7 +163,7 @@ Endo Steel overview:One of the most iconic BattleMechs is the Archer, with its low-slung torso, enormous fists, and missile-bay covers. The Archer was first manufactured in 2474 for heavy-hitting, long-range brawling, and fire-support. -capabilities:Two enormous missile launchers with tons of ammo power the Archer. The missiles were formidable, but their short-range inaccuracy required four medium lasers, two rear-facing and one in each arm. Enlarged hand actuators allow the design to undertake severe physical attacks and transport captured supplies during raids. The cockpit of the Archer situated beneath the center midsection, giving the pilot a unique battlefield view. The torso armor belt above the cockpit protects the gyro and engine from the superior armor. Many pilots initially entered battle with their missile bays locked to hide the 'Mech's real capabilities, leading some to believe it was a close-combat design. As the Archer became famous, this pretext became meaningless. Archer pilots rarely learn new skills, but this hasn't tarnished the 'Mech's reputation. +capabilities:Two enormous missile launchers with tons of ammo power the Archer. The missiles were formidable, but their short-range inaccuracy required four medium lasers, two rear-facing and one in each arm. Enlarged hand actuators allow the design to undertake severe physical attacks and transport captured supplies during raids. The cockpit of the Archer is situated beneath the center midsection, giving the pilot a unique battlefield view. The torso armor belt above the cockpit protects the gyro and engine from the superior armor. Many pilots initially entered battle with their missile bays locked to hide the 'Mech's real capabilities, leading some to believe it was a close-combat design. As the Archer became famous, this pretext became meaningless. Archer pilots rarely learn new skills, but this hasn't tarnished the 'Mech's reputation. deployment:The 6S variant of the Archer was built in 3067 by Bowie Industries using a new light fusion engine, which weighed three quarters of the mass of the original engine. The 'Mech carried two LRM-20 launchers linked to an Artemis IV fire control system, two Streak SRM-2 launchers, and two medium lasers for close combat. As a defensive measure, the 'Mech had an ER Small Laser mounted in the rear of its head. The variant carried six tons of ammo for the LRM and two tons for the SRM, all of which were protected by CASE. diff --git a/megameklab/data/mechfiles/mechs/3085u/Phoenix/Archer ARC-6W.mtf b/megameklab/data/mechfiles/mechs/3085u/Phoenix/Archer ARC-6W.mtf index 757403b50..531a57d38 100644 --- a/megameklab/data/mechfiles/mechs/3085u/Phoenix/Archer ARC-6W.mtf +++ b/megameklab/data/mechfiles/mechs/3085u/Phoenix/Archer ARC-6W.mtf @@ -170,7 +170,7 @@ Heat Sink overview:One of the most iconic BattleMechs is the Archer, with its low-slung torso, enormous fists, and missile-bay covers. The Archer was first manufactured in 2474 for heavy-hitting, long-range brawling, and fire-support. -capabilities:Two enormous missile launchers with tons of ammo power the Archer. The missiles were formidable, but their short-range inaccuracy required four medium lasers, two rear-facing and one in each arm. Enlarged hand actuators allow the design to undertake severe physical attacks and transport captured supplies during raids. The cockpit of the Archer situated beneath the center midsection, giving the pilot a unique battlefield view. The torso armor belt above the cockpit protects the gyro and engine from the superior armor. Many pilots initially entered battle with their missile bays locked to hide the 'Mech's real capabilities, leading some to believe it was a close-combat design. As the Archer became famous, this pretext became meaningless. Archer pilots rarely learn new skills, but this hasn't tarnished the 'Mech's reputation. +capabilities:Two enormous missile launchers with tons of ammo power the Archer. The missiles were formidable, but their short-range inaccuracy required four medium lasers, two rear-facing and one in each arm. Enlarged hand actuators allow the design to undertake severe physical attacks and transport captured supplies during raids. The cockpit of the Archer is situated beneath the center midsection, giving the pilot a unique battlefield view. The torso armor belt above the cockpit protects the gyro and engine from the superior armor. Many pilots initially entered battle with their missile bays locked to hide the 'Mech's real capabilities, leading some to believe it was a close-combat design. As the Archer became famous, this pretext became meaningless. Archer pilots rarely learn new skills, but this hasn't tarnished the 'Mech's reputation. deployment:The 6W was a Periphery modification of the Archer built by VMI out of New Vandenberg, which used older rather than newer technology. This variant carried its four medium lasers in its arms and mounted eight Rocket Launcher 20s and two Rocket Launcher 10s. These weapons gave it a powerful one-shot capability or could be used one at a time over an extended period. diff --git a/megameklab/data/mechfiles/mechs/3085u/Phoenix/Archer ARC-7L.mtf b/megameklab/data/mechfiles/mechs/3085u/Phoenix/Archer ARC-7L.mtf index d3d945471..4b33446c2 100644 --- a/megameklab/data/mechfiles/mechs/3085u/Phoenix/Archer ARC-7L.mtf +++ b/megameklab/data/mechfiles/mechs/3085u/Phoenix/Archer ARC-7L.mtf @@ -158,7 +158,7 @@ IS Stealth -Empty- overview:One of the most iconic BattleMechs is the Archer, with its low-slung torso, enormous fists, and missile-bay covers. The Archer was first manufactured in 2474 for heavy-hitting, long-range brawling, and fire-support. -capabilities:Two enormous missile launchers with tons of ammo power the Archer. The missiles were formidable, but their short-range inaccuracy required four medium lasers, two rear-facing and one in each arm. Enlarged hand actuators allow the design to undertake severe physical attacks and transport captured supplies during raids. The cockpit of the Archer situated beneath the center midsection, giving the pilot a unique battlefield view. The torso armor belt above the cockpit protects the gyro and engine from the superior armor. Many pilots initially entered battle with their missile bays locked to hide the 'Mech's real capabilities, leading some to believe it was a close-combat design. As the Archer became famous, this pretext became meaningless. Archer pilots rarely learn new skills, but this hasn't tarnished the 'Mech's reputation. +capabilities:Two enormous missile launchers with tons of ammo power the Archer. The missiles were formidable, but their short-range inaccuracy required four medium lasers, two rear-facing and one in each arm. Enlarged hand actuators allow the design to undertake severe physical attacks and transport captured supplies during raids. The cockpit of the Archer is situated beneath the center midsection, giving the pilot a unique battlefield view. The torso armor belt above the cockpit protects the gyro and engine from the superior armor. Many pilots initially entered battle with their missile bays locked to hide the 'Mech's real capabilities, leading some to believe it was a close-combat design. As the Archer became famous, this pretext became meaningless. Archer pilots rarely learn new skills, but this hasn't tarnished the 'Mech's reputation. deployment:Built for the Capellan Confederation by Earthwerks in 3067, the 7L variant of the Archer incorporated new Stealth Armor and a Guardian ECM Suite for protection against enemy electronics in addition to making the Archer harder to target. The 'Mech carried twelve and a half tons of Stealth Armor and was armed with two LRM-20 launchers with Artemis IV pods and two ER medium lasers. The tradeoff for this massive upgrade was that the 'Mech's top speed was reduced to 54 km/h. In an attempt to compensate for this, the 'Mech also had three jump jets mounted, making it capable of jumping up to ninety meters at a time. The 7L was slated to enter the Capellan Confederation Armed Forces' new Shadow Lances. history:The design was constructed at the request of Terran Hegemony's HAF for a new "heavy fire support BattleMech" and took nearly nine years to complete. This was owing in part to the design team, which included former HAF MechWarriors, field technicians, and general officer advisors, and the company's engineer team, led by Supervising Engineer Linn Tommi, disputing over theoretical and practical concerns. The intricate engineering proposal presented to the HAF includes complicated, difficult-to-repair stabilizing technology and powerful, computer-slaved sensors designed to make the Archer the most accurate BattleMech in existence. However, the final prototype abandoned these criteria in favor of a sturdier, blockier, and more heavily armored frame that is still in use today. It was so effective that it remained the Hegemony standard for more than a decade and a half, until technological developments allowed Earthwerks to produce a more efficient variant. The Archer, which debuted in 2474, quickly became one of the most well-known and commonly deployed BattleMechs. The Archer was a contemporary of 'Mechs such as the Thunderbolt and the Banshee, and its primary job was fire support, though early in its combat career it was regarded an attack 'Mech capable of long-range brawling, and it was deployed in a variety of different duties. More than 100,000 Archers were built between its introduction and the outbreak of the First Succession War, with tens of thousands of variation types produced over the centuries. Though many were destroyed or deconstructed for spare components, they remained a common sight in the Great House troops, with six distinct manufacturers creating new Archers throughout the Succession Wars. The retrieval of the Helm Memory Core had a significant impact on the creation of the Archer. New variations were created that used rediscovered lostech, giving the venerable 'Mech a few new tricks to surprise its opponents. By the time of the Clan Invasion, most of the major manufacturers had switched over to building these new variants for the Free Worlds League, Federated Commonwealth, Free Rasalhague Republic, and Wolf's Dragoons; only Vandenberg Mechanized Industries continued to build original ARC-2R Archers for the Taurian Concordat. As technology advanced, newer, more advanced models of the Archer were produced. manufacturer:Earthwerks Ltd. diff --git a/megameklab/data/mechfiles/mechs/3085u/Phoenix/Archer ARC-7S.mtf b/megameklab/data/mechfiles/mechs/3085u/Phoenix/Archer ARC-7S.mtf index 3f2720827..aad6f47cb 100644 --- a/megameklab/data/mechfiles/mechs/3085u/Phoenix/Archer ARC-7S.mtf +++ b/megameklab/data/mechfiles/mechs/3085u/Phoenix/Archer ARC-7S.mtf @@ -162,7 +162,7 @@ Heavy Ferro-Fibrous overview:One of the most iconic BattleMechs is the Archer, with its low-slung torso, enormous fists, and missile-bay covers. The Archer was first manufactured in 2474 for heavy-hitting, long-range brawling, and fire-support. -capabilities:Two enormous missile launchers with tons of ammo power the Archer. The missiles were formidable, but their short-range inaccuracy required four medium lasers, two rear-facing and one in each arm. Enlarged hand actuators allow the design to undertake severe physical attacks and transport captured supplies during raids. The cockpit of the Archer situated beneath the center midsection, giving the pilot a unique battlefield view. The torso armor belt above the cockpit protects the gyro and engine from the superior armor. Many pilots initially entered battle with their missile bays locked to hide the 'Mech's real capabilities, leading some to believe it was a close-combat design. As the Archer became famous, this pretext became meaningless. Archer pilots rarely learn new skills, but this hasn't tarnished the 'Mech's reputation. +capabilities:Two enormous missile launchers with tons of ammo power the Archer. The missiles were formidable, but their short-range inaccuracy required four medium lasers, two rear-facing and one in each arm. Enlarged hand actuators allow the design to undertake severe physical attacks and transport captured supplies during raids. The cockpit of the Archer is situated beneath the center midsection, giving the pilot a unique battlefield view. The torso armor belt above the cockpit protects the gyro and engine from the superior armor. Many pilots initially entered battle with their missile bays locked to hide the 'Mech's real capabilities, leading some to believe it was a close-combat design. As the Archer became famous, this pretext became meaningless. Archer pilots rarely learn new skills, but this hasn't tarnished the 'Mech's reputation. deployment:The Archer 7S was an upgrade of the 6S model, and was introduced in 3070. It used Durallex Guardian Heavy Ferro-Fibrous armor with CASE in place of the Endo Steel structure used on the 6S. The 7S had two LRM-20 launchers with Artemis IV for increased missile accuracy and, for close range defense, carried a Diverse Optics ER medium laser and a rear-facing Magna 200P small pulse laser, in addition to the pair of Hovertec Streak SRM-2 launchers. diff --git a/megameklab/data/mechfiles/mechs/3085u/Phoenix/Archer ARC-8M.mtf b/megameklab/data/mechfiles/mechs/3085u/Phoenix/Archer ARC-8M.mtf index a742cd6e4..ab8c0ed19 100644 --- a/megameklab/data/mechfiles/mechs/3085u/Phoenix/Archer ARC-8M.mtf +++ b/megameklab/data/mechfiles/mechs/3085u/Phoenix/Archer ARC-8M.mtf @@ -162,7 +162,7 @@ Foot Actuator overview:One of the most iconic BattleMechs is the Archer, with its low-slung torso, enormous fists, and missile-bay covers. The Archer was first manufactured in 2474 for heavy-hitting, long-range brawling, and fire-support. -capabilities:Two enormous missile launchers with tons of ammo power the Archer. The missiles were formidable, but their short-range inaccuracy required four medium lasers, two rear-facing and one in each arm. Enlarged hand actuators allow the design to undertake severe physical attacks and transport captured supplies during raids. The cockpit of the Archer situated beneath the center midsection, giving the pilot a unique battlefield view. The torso armor belt above the cockpit protects the gyro and engine from the superior armor. Many pilots initially entered battle with their missile bays locked to hide the 'Mech's real capabilities, leading some to believe it was a close-combat design. As the Archer became famous, this pretext became meaningless. Archer pilots rarely learn new skills, but this hasn't tarnished the 'Mech's reputation. +capabilities:Two enormous missile launchers with tons of ammo power the Archer. The missiles were formidable, but their short-range inaccuracy required four medium lasers, two rear-facing and one in each arm. Enlarged hand actuators allow the design to undertake severe physical attacks and transport captured supplies during raids. The cockpit of the Archer is situated beneath the center midsection, giving the pilot a unique battlefield view. The torso armor belt above the cockpit protects the gyro and engine from the superior armor. Many pilots initially entered battle with their missile bays locked to hide the 'Mech's real capabilities, leading some to believe it was a close-combat design. As the Archer became famous, this pretext became meaningless. Archer pilots rarely learn new skills, but this hasn't tarnished the 'Mech's reputation. deployment:The 8M variant of the Archer was built on an Earthwerk Archer II Endo Steel chassis and mixed elements of several past variants. Introduced in 3067 by Earthwerks for the Word of Blake Militia, this variant was armed with two Delta Dart LRM-15 launchers linked to Artemis IV fire control systems in either side torso and a Diverse Optics Sunbeam ER Large Laser in the center torso for long-range combat. It also mounted three Diverse Optics Sunfire ER medium lasers for short ranged support, one in each arm and the third in its head. This made the 8M effective at all ranges and gave it both long-range direct and indirect capabilities. The 8M was protected by thirteen and a half tons of Maximilian 100 standard armor which was better sloped in order to deflect weapons fire more easily. It carried twelve double heat sinks, and had a similar speed profile to the original Archer. Its upper body traversing assembly was improved over the original to better protect its hip actuators and its feet were redesigned to make it a more stable firing platform, whether standing or on the move. Four tons of LRM reloads were split between the side torsos and were protected by CASE. diff --git a/megameklab/data/mechfiles/mechs/3085u/Phoenix/Archer ARC-9K.mtf b/megameklab/data/mechfiles/mechs/3085u/Phoenix/Archer ARC-9K.mtf index b766b9a79..e0fc1d70e 100644 --- a/megameklab/data/mechfiles/mechs/3085u/Phoenix/Archer ARC-9K.mtf +++ b/megameklab/data/mechfiles/mechs/3085u/Phoenix/Archer ARC-9K.mtf @@ -163,7 +163,7 @@ Endo Steel overview:One of the most iconic BattleMechs is the Archer, with its low-slung torso, enormous fists, and missile-bay covers. The Archer was first manufactured in 2474 for heavy-hitting, long-range brawling, and fire-support. -capabilities:Two enormous missile launchers with tons of ammo power the Archer. The missiles were formidable, but their short-range inaccuracy required four medium lasers, two rear-facing and one in each arm. Enlarged hand actuators allow the design to undertake severe physical attacks and transport captured supplies during raids. The cockpit of the Archer situated beneath the center midsection, giving the pilot a unique battlefield view. The torso armor belt above the cockpit protects the gyro and engine from the superior armor. Many pilots initially entered battle with their missile bays locked to hide the 'Mech's real capabilities, leading some to believe it was a close-combat design. As the Archer became famous, this pretext became meaningless. Archer pilots rarely learn new skills, but this hasn't tarnished the 'Mech's reputation. +capabilities:Two enormous missile launchers with tons of ammo power the Archer. The missiles were formidable, but their short-range inaccuracy required four medium lasers, two rear-facing and one in each arm. Enlarged hand actuators allow the design to undertake severe physical attacks and transport captured supplies during raids. The cockpit of the Archer is situated beneath the center midsection, giving the pilot a unique battlefield view. The torso armor belt above the cockpit protects the gyro and engine from the superior armor. Many pilots initially entered battle with their missile bays locked to hide the 'Mech's real capabilities, leading some to believe it was a close-combat design. As the Archer became famous, this pretext became meaningless. Archer pilots rarely learn new skills, but this hasn't tarnished the 'Mech's reputation. deployment:The Archer 9K, introduced in 3071, carried four new MML-5 launchers that were capable of firing both LRM and SRM ammunition. These gave the 'Mech a great deal of tactical flexibility. For long range direct fire capabilities, the 'Mech had three light PPCs and a C3 slave that allowed the 'Mech to share targeting data with friendly units. diff --git a/megameklab/data/mechfiles/mechs/3085u/Phoenix/Archer ARC-9M.mtf b/megameklab/data/mechfiles/mechs/3085u/Phoenix/Archer ARC-9M.mtf index 5b3c09dc8..854fff877 100644 --- a/megameklab/data/mechfiles/mechs/3085u/Phoenix/Archer ARC-9M.mtf +++ b/megameklab/data/mechfiles/mechs/3085u/Phoenix/Archer ARC-9M.mtf @@ -162,7 +162,7 @@ Improved Jump Jet overview:One of the most iconic BattleMechs is the Archer, with its low-slung torso, enormous fists, and missile-bay covers. The Archer was first manufactured in 2474 for heavy-hitting, long-range brawling, and fire-support. -capabilities:Two enormous missile launchers with tons of ammo power the Archer. The missiles were formidable, but their short-range inaccuracy required four medium lasers, two rear-facing and one in each arm. Enlarged hand actuators allow the design to undertake severe physical attacks and transport captured supplies during raids. The cockpit of the Archer situated beneath the center midsection, giving the pilot a unique battlefield view. The torso armor belt above the cockpit protects the gyro and engine from the superior armor. Many pilots initially entered battle with their missile bays locked to hide the 'Mech's real capabilities, leading some to believe it was a close-combat design. As the Archer became famous, this pretext became meaningless. Archer pilots rarely learn new skills, but this hasn't tarnished the 'Mech's reputation. +capabilities:Two enormous missile launchers with tons of ammo power the Archer. The missiles were formidable, but their short-range inaccuracy required four medium lasers, two rear-facing and one in each arm. Enlarged hand actuators allow the design to undertake severe physical attacks and transport captured supplies during raids. The cockpit of the Archer is situated beneath the center midsection, giving the pilot a unique battlefield view. The torso armor belt above the cockpit protects the gyro and engine from the superior armor. Many pilots initially entered battle with their missile bays locked to hide the 'Mech's real capabilities, leading some to believe it was a close-combat design. As the Archer became famous, this pretext became meaningless. Archer pilots rarely learn new skills, but this hasn't tarnished the 'Mech's reputation. deployment:This variant used a Defiance 210 light engine, which dropped the top speed to 54 km/h, but five Improved Jump Jets were added to compensate for this lack of speed. Built in 3076 on an endo steel chassis, the standard weapons were replaced by a Delta Dart LRM-15 with Artemis IV FCS and a Diverse Optics ER medium laser in each torso, and a Defiance 250 light PPC was mounted in each arm. Eleven tons of Light Ferro-Fibrous armor and CASE protected the 'Mech. diff --git a/megameklab/data/mechfiles/mechs/3085u/Phoenix/Archer ARC-9W.mtf b/megameklab/data/mechfiles/mechs/3085u/Phoenix/Archer ARC-9W.mtf index 88995226f..9cfca78eb 100644 --- a/megameklab/data/mechfiles/mechs/3085u/Phoenix/Archer ARC-9W.mtf +++ b/megameklab/data/mechfiles/mechs/3085u/Phoenix/Archer ARC-9W.mtf @@ -160,7 +160,7 @@ Endo Steel overview:One of the most iconic BattleMechs is the Archer, with its low-slung torso, enormous fists, and missile-bay covers. The Archer was first manufactured in 2474 for heavy-hitting, long-range brawling, and fire-support. -capabilities:Two enormous missile launchers with tons of ammo power the Archer. The missiles were formidable, but their short-range inaccuracy required four medium lasers, two rear-facing and one in each arm. Enlarged hand actuators allow the design to undertake severe physical attacks and transport captured supplies during raids. The cockpit of the Archer situated beneath the center midsection, giving the pilot a unique battlefield view. The torso armor belt above the cockpit protects the gyro and engine from the superior armor. Many pilots initially entered battle with their missile bays locked to hide the 'Mech's real capabilities, leading some to believe it was a close-combat design. As the Archer became famous, this pretext became meaningless. Archer pilots rarely learn new skills, but this hasn't tarnished the 'Mech's reputation. +capabilities:Two enormous missile launchers with tons of ammo power the Archer. The missiles were formidable, but their short-range inaccuracy required four medium lasers, two rear-facing and one in each arm. Enlarged hand actuators allow the design to undertake severe physical attacks and transport captured supplies during raids. The cockpit of the Archer is situated beneath the center midsection, giving the pilot a unique battlefield view. The torso armor belt above the cockpit protects the gyro and engine from the superior armor. Many pilots initially entered battle with their missile bays locked to hide the 'Mech's real capabilities, leading some to believe it was a close-combat design. As the Archer became famous, this pretext became meaningless. Archer pilots rarely learn new skills, but this hasn't tarnished the 'Mech's reputation. deployment:Used by the Word of Blake's Protectorate Militia in 3078, this Archer variant carried a pair of ER Large Lasers and Artemis IV-enhanced LRM-15 launchers, with a maximum speed of 86 km/h. For protection, the 9W used an experimental Angel ECM Suite and Void Signature System. diff --git a/megameklab/data/mechfiles/mechs/3085u/Phoenix/Griffin GRF-1DS.mtf b/megameklab/data/mechfiles/mechs/3085u/Phoenix/Griffin GRF-1DS.mtf index ab1dbd647..df37194bc 100644 --- a/megameklab/data/mechfiles/mechs/3085u/Phoenix/Griffin GRF-1DS.mtf +++ b/megameklab/data/mechfiles/mechs/3085u/Phoenix/Griffin GRF-1DS.mtf @@ -163,7 +163,7 @@ capabilities:The massive and efficient fusion engine of the Griffin, giving it a deployment:The 1DS variant of the Griffin, built by Defiance Industries, Kallon Industries and Norse BattleMech Works from their respective production lines starting in 3049, was intended to become the new standard model for the Federated Commonwealth. The engine was upgraded to Hermes 275 extralight engine, fourteen double heat sinks improved cooling and the weapons were stripped from the chassis. The 'Mech now carried a Doombud LRM-20 launcher over the right shoulder and a Thunderbolt-12 Large Pulse Laser in the right arm. It also employed CASE to protect the two tons of missile reloads stored in the left torso. The capture of Norse BattleMech Works on Marduk by the Draconis Combine meant this variant was also employed by the Draconis Combine Mustered Soldiery. -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. +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. manufacturer:Defiance Industries,Victory Industries (formerly Norse BattleMech Works),Kallon Weapon Industries primaryfactory:Hesperus II,Marduk,Talon (Wernke) diff --git a/megameklab/data/mechfiles/mechs/3085u/Phoenix/Griffin GRF-3M.mtf b/megameklab/data/mechfiles/mechs/3085u/Phoenix/Griffin GRF-3M.mtf index 70b66af24..4448230f8 100644 --- a/megameklab/data/mechfiles/mechs/3085u/Phoenix/Griffin GRF-3M.mtf +++ b/megameklab/data/mechfiles/mechs/3085u/Phoenix/Griffin GRF-3M.mtf @@ -164,7 +164,7 @@ capabilities:The massive and efficient fusion engine of the Griffin, giving it a deployment:The 3M Griffin was an upgraded version of the design built for House Marik by Earthwerks and Brigadier Corps starting in 3049. With production lines on Keystone and Oliver this variant sought to enhance the original's long-range capabilities. The engine was exchanged for a Hermes 275 extralight model and carried fourteen double heat sinks to improve heat management. The normal PPC was replaced by a Fusigon Longtooth ER PPC, for longer reach at the expense of more heat, and the LRM launcher had been upgraded to a Doombud LRM-20 launcher, for more indirect fire support capabilities. Finally a ChisComp Small Laser was mounted in the head and the two tons of LRM reloads in the left torso were protected by CASE. While intended for the Free Worlds League Military the capture of Oliver by FedCom forces meant the 3M also appeared in large numbers in the Armed Forces of the Federated Commonwealth. -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. +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. manufacturer:Earthwerks-FWL, Inc.,Brigadier Corporation primaryfactory:Keystone,Oliver diff --git a/megameklab/data/mechfiles/mechs/3085u/Phoenix/Griffin GRF-5L.mtf b/megameklab/data/mechfiles/mechs/3085u/Phoenix/Griffin GRF-5L.mtf index 81c03c6b9..d79502d96 100644 --- a/megameklab/data/mechfiles/mechs/3085u/Phoenix/Griffin GRF-5L.mtf +++ b/megameklab/data/mechfiles/mechs/3085u/Phoenix/Griffin GRF-5L.mtf @@ -166,7 +166,7 @@ capabilities:The massive and efficient fusion engine of the Griffin, giving it a deployment:This variant, introduced in 3070, uses an XL engine to max out armor protection at eleven and a half tons of Stealth Armor. As with all Stealth-equipped designs, the 5L used a Guardian ECM Suite. It was armed with a Plasma Rifle and an MML-5, which could threaten enemies at all ranges. Three medium lasers provided added short-range firepower. Fourteen double heat sinks kept the 'Mech relatively cool, even when the Stealth Armor was active. -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. +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. manufacturer:Earthwerks Ltd. primaryfactory:Grand Base diff --git a/megameklab/data/mechfiles/mechs/3085u/Phoenix/Griffin GRF-5M.mtf b/megameklab/data/mechfiles/mechs/3085u/Phoenix/Griffin GRF-5M.mtf index 7a2f7d373..098906ff2 100644 --- a/megameklab/data/mechfiles/mechs/3085u/Phoenix/Griffin GRF-5M.mtf +++ b/megameklab/data/mechfiles/mechs/3085u/Phoenix/Griffin GRF-5M.mtf @@ -165,7 +165,7 @@ capabilities:The massive and efficient fusion engine of the Griffin, giving it a deployment:The 5M variant of the Griffin was designed in 3066 with a distinctive flair for the Free Worlds League. Unlike other "Phoenix" 'Mechs it was powered by an extralight engine and carried, as its primary weapon, a Light Gauss Rifle. This was backed up by an LRM-10 launcher and a small laser for close range work. The variant utilized double heat sinks and also carried ten and a half tons of armor. -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. +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. manufacturer:Brigadier Corporation primaryfactory:Oliver diff --git a/megameklab/data/mechfiles/mechs/3085u/Phoenix/Marauder II Bounty Hunter.mtf b/megameklab/data/mechfiles/mechs/3085u/Phoenix/Marauder II Bounty Hunter.mtf index 6d84a52d7..af316b598 100644 --- a/megameklab/data/mechfiles/mechs/3085u/Phoenix/Marauder II Bounty Hunter.mtf +++ b/megameklab/data/mechfiles/mechs/3085u/Phoenix/Marauder II Bounty Hunter.mtf @@ -160,7 +160,7 @@ Clan Ferro-Fibrous overview:First built in 3012, the Marauder II is a successful attempt to take the firepower of the Marauder and combine it with the reliability and ruggedness of an assault chassis. capabilities:With the Marauder already a powerful and popular 'Mech, the Dragoons' goals with the Marauder II were to enhance its abilities by strengthening its chassis to carry a much heavier armor and weapons load. The 'Mech was then armored with nineteen tons of Valiant Lamellor armor, giving it protection that rivals that of the Atlas and fitted with thirteen additional heat sinks, a total of twenty-nine, to allow a more ferocious rate of fire. Retaining its progenitor's Vlar 300-rated engine, with the MAD-5A built around an extralight fusion engine to save more weight for weapons. To make up for the reduced mobility, the Marauder II was outfitted with three Chilton 600 jump jets that give it a jumping capability of up to ninety meters. deployment:This version is built with Clan technology similar to the Marauder II C. It uses a standard 300-rated fusion engine with sixteen tons of ferro-fibrous armor and endo steel internal structure. The 'Mech is equipped with 17 Clan double heat sinks but no lower arm actuators. It is armed with an ER PPC and two medium pulse lasers in each arm. A Gauss rifle sits in the right torso with two tons of ammunition, and a targeting computer is in the left torso for increased accuracy. It has a Clan-tech CASE system to protect the Gauss rifle, and can jump 90 meters at a time. -history:In 3010 officers of the famous Wolf's Dragoons mercenary unit contracted with Blackwell Industries of New Valencia on the project of modifying the highly successful 75-ton Marauder into a 100-ton assault 'Mech. Working from existing plans the design phase proved to be very short, the process of reinforcing the Marauder chassis turned out to be easier than expected, enhanced by the removal of the finicky and temperamental General Motors Whirlwind Autocannon for a much simpler Large Laser. First appearing with the famous Zeta Battalion before spreading to Alpha Regiment, the Dragoons' enemies soon learned to fear the appearance of Marauder IIs as foreshadowing a major advance, as for the remainder of the Third Succession War it remained the exclusive property of the mysterious Dragoons. This changed after the Fourth Succession War when Colonel Jaime Wolf authorized Blackwell to increase production and allow outside buyers access, on the provision that each sale had to be approved by the Dragoons. Now spreading in limited numbers, the largest buyer outside the Dragoons would be the Miller's Marauders mercenary unit, famed for its almost exclusive use of the Marauder chassis and the secret loan of its DropShips to Zeta Battalion for their climactic rescue of the rest of the Dragoons on Crossing. When new unit commander Major Susan Barber expressed interest in the Marauder II, Colonel Wolf gave Blackwell the go-ahead to supply her with all she needed, by the Clan Invasion the now renamed Barber's Marauder II would boast almost a regiment's worth of the fearsome assault 'Mech. Though Barber's Marauder II would help drive the considerable interest and demand for the powerful assault 'Mech, they would also damage its seeming aura of invincibility following their ignoble destruction by Clan Jade Falcon on Koniz in June 3064. Seeking to rekindle interest in their flagship 'Mech following its disastrous showing on Koniz, GM/Blackwell noted the Vicore Industries triggered refresh of "classic" designs to develop a more powerful and visually refreshed model. The resulting MAD-4S variant was the first widely available Marauder II, Wolf's Dragoons' easing of sale restrictions partly motivated by profit but also as a means to punish the Lyran Alliance for the theft of the Blackwell developed light fusion engine, as of 3067 selling the 'Mech to all interested parties save those the Dragoons were fighting against in the Chaos March; the Word of Blake and the members of Trinity Alliance. The demand for the Marauder II would only increase in the Jihad following the Blakist destruction of GM and Blackwell's production facilities for the 'Mech as part of their vendetta against the Wolf's Dragoons, with many salvaged examples in use among the nations of the Inner Sphere in a large number of variations following the Blakists' fall, the most notable being the MAD-6D developed by the Federated Suns and shared with the Republic of the Sphere. +history:In 3010 officers of the famous Wolf's Dragoons mercenary unit contracted with Blackwell Industries of New Valencia on the project of modifying the highly successful 75-ton Marauder into a 100-ton assault 'Mech. Working from existing plans the design phase proved to be very short, the process of reinforcing the Marauder chassis turned out to be easier than expected, enhanced by the removal of the finicky and temperamental General Motors Whirlwind Autocannon for a much simpler Large Laser. First appearing with the famous Zeta Battalion before spreading to Alpha Regiment, the Dragoons' enemies soon learned to fear the appearance of Marauder IIs as foreshadowing a major advance, as for the remainder of the Third Succession War it remained the exclusive property of the mysterious Dragoons. This changed after the Fourth Succession War when Colonel Jaime Wolf authorized Blackwell to increase production and allow outside buyers access, on the provision that each sale had to be approved by the Dragoons. Now spreading in limited numbers, the largest buyer outside the Dragoons would be the Miller's Marauders mercenary unit, famed for its almost exclusive use of the Marauder chassis and the secret loan of its DropShips to Zeta Battalion for their climactic rescue of the rest of the Dragoons on Crossing. When new unit commander Major Susan Barber expressed interest in the Marauder II, Colonel Wolf gave Blackwell the go-ahead to supply her with all she needed, by the Clan Invasion the now renamed Barber's Marauders would boast almost a regiment's worth of the fearsome assault 'Mech. Though Barber's Marauder II would help drive the considerable interest and demand for the powerful assault 'Mech, they would also damage its seeming aura of invincibility following their ignoble destruction by Clan Jade Falcon on Koniz in June 3064. Seeking to rekindle interest in their flagship 'Mech following its disastrous showing on Koniz, GM/Blackwell noted the Vicore Industries triggered refresh of "classic" designs to develop a more powerful and visually refreshed model. The resulting MAD-4S variant was the first widely available Marauder II, Wolf's Dragoons' easing of sale restrictions partly motivated by profit but also as a means to punish the Lyran Alliance for the theft of the Blackwell developed light fusion engine, as of 3067 selling the 'Mech to all interested parties save those the Dragoons were fighting against in the Chaos March; the Word of Blake and the members of Trinity Alliance. The demand for the Marauder II would only increase in the Jihad following the Blakist destruction of GM and Blackwell's production facilities for the 'Mech as part of their vendetta against the Wolf's Dragoons, with many salvaged examples in use among the nations of the Inner Sphere in a large number of variations following the Blakists' fall, the most notable being the MAD-6D developed by the Federated Suns and shared with the Republic of the Sphere. manufacturer:Refit primaryfactory:Various systemmanufacturer:CHASSIS:GM Marauder-E diff --git a/megameklab/data/mechfiles/mechs/3085u/Phoenix/Marauder II MAD-4H.mtf b/megameklab/data/mechfiles/mechs/3085u/Phoenix/Marauder II MAD-4H.mtf index b88d420e7..ff3b985c9 100644 --- a/megameklab/data/mechfiles/mechs/3085u/Phoenix/Marauder II MAD-4H.mtf +++ b/megameklab/data/mechfiles/mechs/3085u/Phoenix/Marauder II MAD-4H.mtf @@ -173,7 +173,7 @@ capabilities:With the Marauder already a powerful and popular 'Mech, the Dragoon deployment:Using a shipment of Lyran bound MAD-4S hijacked by pirates, the 4H Marauder II is a refit developed by the Marian Hegemony that replaces the Heavy Gauss Rifle with four Rocket Launcher 20s, six Rocket Launcher 15s, and a Rocket Launcher 10 which gives the 4H incredible close range damage capabilities. -history:In 3010 officers of the famous Wolf's Dragoons mercenary unit contracted with Blackwell Industries of New Valencia on the project of modifying the highly successful 75-ton Marauder into a 100-ton assault 'Mech. Working from existing plans the design phase proved to be very short, the process of reinforcing the Marauder chassis turned out to be easier than expected, enhanced by the removal of the finicky and temperamental General Motors Whirlwind Autocannon for a much simpler Large Laser. First appearing with the famous Zeta Battalion before spreading to Alpha Regiment, the Dragoons' enemies soon learned to fear the appearance of Marauder IIs as foreshadowing a major advance, as for the remainder of the Third Succession War it remained the exclusive property of the mysterious Dragoons. This changed after the Fourth Succession War when Colonel Jaime Wolf authorized Blackwell to increase production and allow outside buyers access, on the provision that each sale had to be approved by the Dragoons. Now spreading in limited numbers, the largest buyer outside the Dragoons would be the Miller's Marauders mercenary unit, famed for its almost exclusive use of the Marauder chassis and the secret loan of its DropShips to Zeta Battalion for their climactic rescue of the rest of the Dragoons on Crossing. When new unit commander Major Susan Barber expressed interest in the Marauder II, Colonel Wolf gave Blackwell the go-ahead to supply her with all she needed, by the Clan Invasion the now renamed Barber's Marauder II would boast almost a regiment's worth of the fearsome assault 'Mech. Though Barber's Marauder II would help drive the considerable interest and demand for the powerful assault 'Mech, they would also damage its seeming aura of invincibility following their ignoble destruction by Clan Jade Falcon on Koniz in June 3064. Seeking to rekindle interest in their flagship 'Mech following its disastrous showing on Koniz, GM/Blackwell noted the Vicore Industries triggered refresh of "classic" designs to develop a more powerful and visually refreshed model. The resulting MAD-4S variant was the first widely available Marauder II, Wolf's Dragoons' easing of sale restrictions partly motivated by profit but also as a means to punish the Lyran Alliance for the theft of the Blackwell developed light fusion engine, as of 3067 selling the 'Mech to all interested parties save those the Dragoons were fighting against in the Chaos March; the Word of Blake and the members of Trinity Alliance. The demand for the Marauder II would only increase in the Jihad following the Blakist destruction of GM and Blackwell's production facilities for the 'Mech as part of their vendetta against the Wolf's Dragoons, with many salvaged examples in use among the nations of the Inner Sphere in a large number of variations following the Blakists' fall, the most notable being the MAD-6D developed by the Federated Suns and shared with the Republic of the Sphere. +history:In 3010 officers of the famous Wolf's Dragoons mercenary unit contracted with Blackwell Industries of New Valencia on the project of modifying the highly successful 75-ton Marauder into a 100-ton assault 'Mech. Working from existing plans the design phase proved to be very short, the process of reinforcing the Marauder chassis turned out to be easier than expected, enhanced by the removal of the finicky and temperamental General Motors Whirlwind Autocannon for a much simpler Large Laser. First appearing with the famous Zeta Battalion before spreading to Alpha Regiment, the Dragoons' enemies soon learned to fear the appearance of Marauder IIs as foreshadowing a major advance, as for the remainder of the Third Succession War it remained the exclusive property of the mysterious Dragoons. This changed after the Fourth Succession War when Colonel Jaime Wolf authorized Blackwell to increase production and allow outside buyers access, on the provision that each sale had to be approved by the Dragoons. Now spreading in limited numbers, the largest buyer outside the Dragoons would be the Miller's Marauders mercenary unit, famed for its almost exclusive use of the Marauder chassis and the secret loan of its DropShips to Zeta Battalion for their climactic rescue of the rest of the Dragoons on Crossing. When new unit commander Major Susan Barber expressed interest in the Marauder II, Colonel Wolf gave Blackwell the go-ahead to supply her with all she needed, by the Clan Invasion the now renamed Barber's Marauders would boast almost a regiment's worth of the fearsome assault 'Mech. Though Barber's Marauder II would help drive the considerable interest and demand for the powerful assault 'Mech, they would also damage its seeming aura of invincibility following their ignoble destruction by Clan Jade Falcon on Koniz in June 3064. Seeking to rekindle interest in their flagship 'Mech following its disastrous showing on Koniz, GM/Blackwell noted the Vicore Industries triggered refresh of "classic" designs to develop a more powerful and visually refreshed model. The resulting MAD-4S variant was the first widely available Marauder II, Wolf's Dragoons' easing of sale restrictions partly motivated by profit but also as a means to punish the Lyran Alliance for the theft of the Blackwell developed light fusion engine, as of 3067 selling the 'Mech to all interested parties save those the Dragoons were fighting against in the Chaos March; the Word of Blake and the members of Trinity Alliance. The demand for the Marauder II would only increase in the Jihad following the Blakist destruction of GM and Blackwell's production facilities for the 'Mech as part of their vendetta against the Wolf's Dragoons, with many salvaged examples in use among the nations of the Inner Sphere in a large number of variations following the Blakists' fall, the most notable being the MAD-6D developed by the Federated Suns and shared with the Republic of the Sphere. manufacturer:Marian Arms (Refit) primaryfactory:Alphard (MH) diff --git a/megameklab/data/mechfiles/mechs/3085u/Phoenix/Marauder II MAD-4K.mtf b/megameklab/data/mechfiles/mechs/3085u/Phoenix/Marauder II MAD-4K.mtf index 20b798a19..26d825d42 100644 --- a/megameklab/data/mechfiles/mechs/3085u/Phoenix/Marauder II MAD-4K.mtf +++ b/megameklab/data/mechfiles/mechs/3085u/Phoenix/Marauder II MAD-4K.mtf @@ -161,9 +161,9 @@ overview:First built in 3012, the Marauder II is a successful attempt to take th capabilities:With the Marauder already a powerful and popular 'Mech, the Dragoons' goals with the Marauder II were to enhance its abilities by strengthening its chassis to carry a much heavier armor and weapons load. The 'Mech was then armored with nineteen tons of Valiant Lamellor armor, giving it protection that rivals that of the Atlas and fitted with thirteen additional heat sinks, a total of twenty-nine, to allow a more ferocious rate of fire. Retaining its progenitor's Vlar 300-rated engine, with the MAD-5A built around an extralight fusion engine to save more weight for weapons. To make up for the reduced mobility, the Marauder II was outfitted with three Chilton 600 jump jets that give it a jumping capability of up to ninety meters. -deployment:The 4K is a variant based mostly on the 4S. Though it retains the GM 300 Light Engine of its predecessor, the 4K has a Lord's Light 3 Heavy PPC mounted in each arm. Under each PPC is a Diverse Optics ER Small Laser. In order to make room for the larger cannons, the Heavy Gauss Rifle is replaced with a lighter, standard Poland Main Model A Gauss rifle.[ +deployment:The 4K is a variant based mostly on the 4S. Though it retains the GM 300 Light Engine of its predecessor, the 4K has a Lord's Light 3 Heavy PPC mounted in each arm. Under each PPC is a Diverse Optics ER Small Laser. In order to make room for the larger cannons, the Heavy Gauss Rifle is replaced with a lighter, standard Poland Main Model A Gauss rifle. -history:In 3010 officers of the famous Wolf's Dragoons mercenary unit contracted with Blackwell Industries of New Valencia on the project of modifying the highly successful 75-ton Marauder into a 100-ton assault 'Mech. Working from existing plans the design phase proved to be very short, the process of reinforcing the Marauder chassis turned out to be easier than expected, enhanced by the removal of the finicky and temperamental General Motors Whirlwind Autocannon for a much simpler Large Laser. First appearing with the famous Zeta Battalion before spreading to Alpha Regiment, the Dragoons' enemies soon learned to fear the appearance of Marauder IIs as foreshadowing a major advance, as for the remainder of the Third Succession War it remained the exclusive property of the mysterious Dragoons. This changed after the Fourth Succession War when Colonel Jaime Wolf authorized Blackwell to increase production and allow outside buyers access, on the provision that each sale had to be approved by the Dragoons. Now spreading in limited numbers, the largest buyer outside the Dragoons would be the Miller's Marauders mercenary unit, famed for its almost exclusive use of the Marauder chassis and the secret loan of its DropShips to Zeta Battalion for their climactic rescue of the rest of the Dragoons on Crossing. When new unit commander Major Susan Barber expressed interest in the Marauder II, Colonel Wolf gave Blackwell the go-ahead to supply her with all she needed, by the Clan Invasion the now renamed Barber's Marauder II would boast almost a regiment's worth of the fearsome assault 'Mech. Though Barber's Marauder II would help drive the considerable interest and demand for the powerful assault 'Mech, they would also damage its seeming aura of invincibility following their ignoble destruction by Clan Jade Falcon on Koniz in June 3064. Seeking to rekindle interest in their flagship 'Mech following its disastrous showing on Koniz, GM/Blackwell noted the Vicore Industries triggered refresh of "classic" designs to develop a more powerful and visually refreshed model. The resulting MAD-4S variant was the first widely available Marauder II, Wolf's Dragoons' easing of sale restrictions partly motivated by profit but also as a means to punish the Lyran Alliance for the theft of the Blackwell developed light fusion engine, as of 3067 selling the 'Mech to all interested parties save those the Dragoons were fighting against in the Chaos March; the Word of Blake and the members of Trinity Alliance. The demand for the Marauder II would only increase in the Jihad following the Blakist destruction of GM and Blackwell's production facilities for the 'Mech as part of their vendetta against the Wolf's Dragoons, with many salvaged examples in use among the nations of the Inner Sphere in a large number of variations following the Blakists' fall, the most notable being the MAD-6D developed by the Federated Suns and shared with the Republic of the Sphere. +history:In 3010 officers of the famous Wolf's Dragoons mercenary unit contracted with Blackwell Industries of New Valencia on the project of modifying the highly successful 75-ton Marauder into a 100-ton assault 'Mech. Working from existing plans the design phase proved to be very short, the process of reinforcing the Marauder chassis turned out to be easier than expected, enhanced by the removal of the finicky and temperamental General Motors Whirlwind Autocannon for a much simpler Large Laser. First appearing with the famous Zeta Battalion before spreading to Alpha Regiment, the Dragoons' enemies soon learned to fear the appearance of Marauder IIs as foreshadowing a major advance, as for the remainder of the Third Succession War it remained the exclusive property of the mysterious Dragoons. This changed after the Fourth Succession War when Colonel Jaime Wolf authorized Blackwell to increase production and allow outside buyers access, on the provision that each sale had to be approved by the Dragoons. Now spreading in limited numbers, the largest buyer outside the Dragoons would be the Miller's Marauders mercenary unit, famed for its almost exclusive use of the Marauder chassis and the secret loan of its DropShips to Zeta Battalion for their climactic rescue of the rest of the Dragoons on Crossing. When new unit commander Major Susan Barber expressed interest in the Marauder II, Colonel Wolf gave Blackwell the go-ahead to supply her with all she needed, by the Clan Invasion the now renamed Barber's Marauders would boast almost a regiment's worth of the fearsome assault 'Mech. Though Barber's Marauder II would help drive the considerable interest and demand for the powerful assault 'Mech, they would also damage its seeming aura of invincibility following their ignoble destruction by Clan Jade Falcon on Koniz in June 3064. Seeking to rekindle interest in their flagship 'Mech following its disastrous showing on Koniz, GM/Blackwell noted the Vicore Industries triggered refresh of "classic" designs to develop a more powerful and visually refreshed model. The resulting MAD-4S variant was the first widely available Marauder II, Wolf's Dragoons' easing of sale restrictions partly motivated by profit but also as a means to punish the Lyran Alliance for the theft of the Blackwell developed light fusion engine, as of 3067 selling the 'Mech to all interested parties save those the Dragoons were fighting against in the Chaos March; the Word of Blake and the members of Trinity Alliance. The demand for the Marauder II would only increase in the Jihad following the Blakist destruction of GM and Blackwell's production facilities for the 'Mech as part of their vendetta against the Wolf's Dragoons, with many salvaged examples in use among the nations of the Inner Sphere in a large number of variations following the Blakists' fall, the most notable being the MAD-6D developed by the Federated Suns and shared with the Republic of the Sphere. manufacturer:Field Refit primaryfactory:Various diff --git a/megameklab/data/mechfiles/mechs/3085u/Phoenix/Marauder II MAD-4S.mtf b/megameklab/data/mechfiles/mechs/3085u/Phoenix/Marauder II MAD-4S.mtf index c65c078be..af5d4117a 100644 --- a/megameklab/data/mechfiles/mechs/3085u/Phoenix/Marauder II MAD-4S.mtf +++ b/megameklab/data/mechfiles/mechs/3085u/Phoenix/Marauder II MAD-4S.mtf @@ -163,7 +163,7 @@ capabilities:With the Marauder already a powerful and popular 'Mech, the Dragoon deployment:This variant was introduced in the Dark Age. It has a top speed of 54 km/h and a 90 meter jump radius. Powered by a light fusion engine it carries an ER PPC and medium pulse laser in each arm. A Gauss rifle is carried in the right torso, and is protected by CASE. It also carries a forward facing ER small laser and a head-mounted anti-missile system that covers the 'Mech's rear. Seventeen double heat sinks deal with the heat. -history:In 3010 officers of the famous Wolf's Dragoons mercenary unit contracted with Blackwell Industries of New Valencia on the project of modifying the highly successful 75-ton Marauder into a 100-ton assault 'Mech. Working from existing plans the design phase proved to be very short, the process of reinforcing the Marauder chassis turned out to be easier than expected, enhanced by the removal of the finicky and temperamental General Motors Whirlwind Autocannon for a much simpler Large Laser. First appearing with the famous Zeta Battalion before spreading to Alpha Regiment, the Dragoons' enemies soon learned to fear the appearance of Marauder IIs as foreshadowing a major advance, as for the remainder of the Third Succession War it remained the exclusive property of the mysterious Dragoons. This changed after the Fourth Succession War when Colonel Jaime Wolf authorized Blackwell to increase production and allow outside buyers access, on the provision that each sale had to be approved by the Dragoons. Now spreading in limited numbers, the largest buyer outside the Dragoons would be the Miller's Marauders mercenary unit, famed for its almost exclusive use of the Marauder chassis and the secret loan of its DropShips to Zeta Battalion for their climactic rescue of the rest of the Dragoons on Crossing. When new unit commander Major Susan Barber expressed interest in the Marauder II, Colonel Wolf gave Blackwell the go-ahead to supply her with all she needed, by the Clan Invasion the now renamed Barber's Marauder II would boast almost a regiment's worth of the fearsome assault 'Mech. Though Barber's Marauder II would help drive the considerable interest and demand for the powerful assault 'Mech, they would also damage its seeming aura of invincibility following their ignoble destruction by Clan Jade Falcon on Koniz in June 3064. Seeking to rekindle interest in their flagship 'Mech following its disastrous showing on Koniz, GM/Blackwell noted the Vicore Industries triggered refresh of "classic" designs to develop a more powerful and visually refreshed model. The resulting MAD-4S variant was the first widely available Marauder II, Wolf's Dragoons' easing of sale restrictions partly motivated by profit but also as a means to punish the Lyran Alliance for the theft of the Blackwell developed light fusion engine, as of 3067 selling the 'Mech to all interested parties save those the Dragoons were fighting against in the Chaos March; the Word of Blake and the members of Trinity Alliance. The demand for the Marauder II would only increase in the Jihad following the Blakist destruction of GM and Blackwell's production facilities for the 'Mech as part of their vendetta against the Wolf's Dragoons, with many salvaged examples in use among the nations of the Inner Sphere in a large number of variations following the Blakists' fall, the most notable being the MAD-6D developed by the Federated Suns and shared with the Republic of the Sphere. +history:In 3010 officers of the famous Wolf's Dragoons mercenary unit contracted with Blackwell Industries of New Valencia on the project of modifying the highly successful 75-ton Marauder into a 100-ton assault 'Mech. Working from existing plans the design phase proved to be very short, the process of reinforcing the Marauder chassis turned out to be easier than expected, enhanced by the removal of the finicky and temperamental General Motors Whirlwind Autocannon for a much simpler Large Laser. First appearing with the famous Zeta Battalion before spreading to Alpha Regiment, the Dragoons' enemies soon learned to fear the appearance of Marauder IIs as foreshadowing a major advance, as for the remainder of the Third Succession War it remained the exclusive property of the mysterious Dragoons. This changed after the Fourth Succession War when Colonel Jaime Wolf authorized Blackwell to increase production and allow outside buyers access, on the provision that each sale had to be approved by the Dragoons. Now spreading in limited numbers, the largest buyer outside the Dragoons would be the Miller's Marauders mercenary unit, famed for its almost exclusive use of the Marauder chassis and the secret loan of its DropShips to Zeta Battalion for their climactic rescue of the rest of the Dragoons on Crossing. When new unit commander Major Susan Barber expressed interest in the Marauder II, Colonel Wolf gave Blackwell the go-ahead to supply her with all she needed, by the Clan Invasion the now renamed Barber's Marauders would boast almost a regiment's worth of the fearsome assault 'Mech. Though Barber's Marauder II would help drive the considerable interest and demand for the powerful assault 'Mech, they would also damage its seeming aura of invincibility following their ignoble destruction by Clan Jade Falcon on Koniz in June 3064. Seeking to rekindle interest in their flagship 'Mech following its disastrous showing on Koniz, GM/Blackwell noted the Vicore Industries triggered refresh of "classic" designs to develop a more powerful and visually refreshed model. The resulting MAD-4S variant was the first widely available Marauder II, Wolf's Dragoons' easing of sale restrictions partly motivated by profit but also as a means to punish the Lyran Alliance for the theft of the Blackwell developed light fusion engine, as of 3067 selling the 'Mech to all interested parties save those the Dragoons were fighting against in the Chaos March; the Word of Blake and the members of Trinity Alliance. The demand for the Marauder II would only increase in the Jihad following the Blakist destruction of GM and Blackwell's production facilities for the 'Mech as part of their vendetta against the Wolf's Dragoons, with many salvaged examples in use among the nations of the Inner Sphere in a large number of variations following the Blakists' fall, the most notable being the MAD-6D developed by the Federated Suns and shared with the Republic of the Sphere. manufacturer:General Motors/Blackwell Corporation primaryfactory:New Valencia diff --git a/megameklab/data/mechfiles/mechs/3085u/Phoenix/Marauder II MAD-5W.mtf b/megameklab/data/mechfiles/mechs/3085u/Phoenix/Marauder II MAD-5W.mtf index d4230411d..008da85e7 100644 --- a/megameklab/data/mechfiles/mechs/3085u/Phoenix/Marauder II MAD-5W.mtf +++ b/megameklab/data/mechfiles/mechs/3085u/Phoenix/Marauder II MAD-5W.mtf @@ -161,7 +161,7 @@ capabilities:With the Marauder already a powerful and popular 'Mech, the Dragoon deployment:Developed by the Word of Blake but also used by ComStar, this 3070 variant uses a standard fusion engine. Each arm contains a Snub-Nose PPC that does its best work up close, while a heavy PPC is mounted in the body. A C3i computer helps makes this Marauder II's weapons more accurate. Perhaps the most startling feature is enough improved jump jets to move up to one hundred fifty meters in a single leap. -history:In 3010 officers of the famous Wolf's Dragoons mercenary unit contracted with Blackwell Industries of New Valencia on the project of modifying the highly successful 75-ton Marauder into a 100-ton assault 'Mech. Working from existing plans the design phase proved to be very short, the process of reinforcing the Marauder chassis turned out to be easier than expected, enhanced by the removal of the finicky and temperamental General Motors Whirlwind Autocannon for a much simpler Large Laser. First appearing with the famous Zeta Battalion before spreading to Alpha Regiment, the Dragoons' enemies soon learned to fear the appearance of Marauder IIs as foreshadowing a major advance, as for the remainder of the Third Succession War it remained the exclusive property of the mysterious Dragoons. This changed after the Fourth Succession War when Colonel Jaime Wolf authorized Blackwell to increase production and allow outside buyers access, on the provision that each sale had to be approved by the Dragoons. Now spreading in limited numbers, the largest buyer outside the Dragoons would be the Miller's Marauders mercenary unit, famed for its almost exclusive use of the Marauder chassis and the secret loan of its DropShips to Zeta Battalion for their climactic rescue of the rest of the Dragoons on Crossing. When new unit commander Major Susan Barber expressed interest in the Marauder II, Colonel Wolf gave Blackwell the go-ahead to supply her with all she needed, by the Clan Invasion the now renamed Barber's Marauder II would boast almost a regiment's worth of the fearsome assault 'Mech. Though Barber's Marauder II would help drive the considerable interest and demand for the powerful assault 'Mech, they would also damage its seeming aura of invincibility following their ignoble destruction by Clan Jade Falcon on Koniz in June 3064. Seeking to rekindle interest in their flagship 'Mech following its disastrous showing on Koniz, GM/Blackwell noted the Vicore Industries triggered refresh of "classic" designs to develop a more powerful and visually refreshed model. The resulting MAD-4S variant was the first widely available Marauder II, Wolf's Dragoons' easing of sale restrictions partly motivated by profit but also as a means to punish the Lyran Alliance for the theft of the Blackwell developed light fusion engine, as of 3067 selling the 'Mech to all interested parties save those the Dragoons were fighting against in the Chaos March; the Word of Blake and the members of Trinity Alliance. The demand for the Marauder II would only increase in the Jihad following the Blakist destruction of GM and Blackwell's production facilities for the 'Mech as part of their vendetta against the Wolf's Dragoons, with many salvaged examples in use among the nations of the Inner Sphere in a large number of variations following the Blakists' fall, the most notable being the MAD-6D developed by the Federated Suns and shared with the Republic of the Sphere. +history:In 3010 officers of the famous Wolf's Dragoons mercenary unit contracted with Blackwell Industries of New Valencia on the project of modifying the highly successful 75-ton Marauder into a 100-ton assault 'Mech. Working from existing plans the design phase proved to be very short, the process of reinforcing the Marauder chassis turned out to be easier than expected, enhanced by the removal of the finicky and temperamental General Motors Whirlwind Autocannon for a much simpler Large Laser. First appearing with the famous Zeta Battalion before spreading to Alpha Regiment, the Dragoons' enemies soon learned to fear the appearance of Marauder IIs as foreshadowing a major advance, as for the remainder of the Third Succession War it remained the exclusive property of the mysterious Dragoons. This changed after the Fourth Succession War when Colonel Jaime Wolf authorized Blackwell to increase production and allow outside buyers access, on the provision that each sale had to be approved by the Dragoons. Now spreading in limited numbers, the largest buyer outside the Dragoons would be the Miller's Marauders mercenary unit, famed for its almost exclusive use of the Marauder chassis and the secret loan of its DropShips to Zeta Battalion for their climactic rescue of the rest of the Dragoons on Crossing. When new unit commander Major Susan Barber expressed interest in the Marauder II, Colonel Wolf gave Blackwell the go-ahead to supply her with all she needed, by the Clan Invasion the now renamed Barber's Marauders would boast almost a regiment's worth of the fearsome assault 'Mech. Though Barber's Marauder II would help drive the considerable interest and demand for the powerful assault 'Mech, they would also damage its seeming aura of invincibility following their ignoble destruction by Clan Jade Falcon on Koniz in June 3064. Seeking to rekindle interest in their flagship 'Mech following its disastrous showing on Koniz, GM/Blackwell noted the Vicore Industries triggered refresh of "classic" designs to develop a more powerful and visually refreshed model. The resulting MAD-4S variant was the first widely available Marauder II, Wolf's Dragoons' easing of sale restrictions partly motivated by profit but also as a means to punish the Lyran Alliance for the theft of the Blackwell developed light fusion engine, as of 3067 selling the 'Mech to all interested parties save those the Dragoons were fighting against in the Chaos March; the Word of Blake and the members of Trinity Alliance. The demand for the Marauder II would only increase in the Jihad following the Blakist destruction of GM and Blackwell's production facilities for the 'Mech as part of their vendetta against the Wolf's Dragoons, with many salvaged examples in use among the nations of the Inner Sphere in a large number of variations following the Blakists' fall, the most notable being the MAD-6D developed by the Federated Suns and shared with the Republic of the Sphere. manufacturer:Field Refit primaryfactory:Various diff --git a/megameklab/data/mechfiles/mechs/3085u/Phoenix/Marauder II MAD-6D.mtf b/megameklab/data/mechfiles/mechs/3085u/Phoenix/Marauder II MAD-6D.mtf index fd1750c2e..48a80fbcb 100644 --- a/megameklab/data/mechfiles/mechs/3085u/Phoenix/Marauder II MAD-6D.mtf +++ b/megameklab/data/mechfiles/mechs/3085u/Phoenix/Marauder II MAD-6D.mtf @@ -163,7 +163,7 @@ capabilities:With the Marauder already a powerful and popular 'Mech, the Dragoon deployment:Based on the standard MAD-5A Marauder II, this variant uses an XL Engine to provide power. The weapons have been replaced with Snub-Nose PPCs, Light PPCs, and a Rotary AC/5. Three tons of ammunition in a CASE protected bay provides plenty of endurance. The single heat sinks were traded out for double heat sinks, and Improved Jump Jets provide a 150 meter jump radius. -history:In 3010 officers of the famous Wolf's Dragoons mercenary unit contracted with Blackwell Industries of New Valencia on the project of modifying the highly successful 75-ton Marauder into a 100-ton assault 'Mech. Working from existing plans the design phase proved to be very short, the process of reinforcing the Marauder chassis turned out to be easier than expected, enhanced by the removal of the finicky and temperamental General Motors Whirlwind Autocannon for a much simpler Large Laser. First appearing with the famous Zeta Battalion before spreading to Alpha Regiment, the Dragoons' enemies soon learned to fear the appearance of Marauder IIs as foreshadowing a major advance, as for the remainder of the Third Succession War it remained the exclusive property of the mysterious Dragoons. This changed after the Fourth Succession War when Colonel Jaime Wolf authorized Blackwell to increase production and allow outside buyers access, on the provision that each sale had to be approved by the Dragoons. Now spreading in limited numbers, the largest buyer outside the Dragoons would be the Miller's Marauders mercenary unit, famed for its almost exclusive use of the Marauder chassis and the secret loan of its DropShips to Zeta Battalion for their climactic rescue of the rest of the Dragoons on Crossing. When new unit commander Major Susan Barber expressed interest in the Marauder II, Colonel Wolf gave Blackwell the go-ahead to supply her with all she needed, by the Clan Invasion the now renamed Barber's Marauder II would boast almost a regiment's worth of the fearsome assault 'Mech. Though Barber's Marauder II would help drive the considerable interest and demand for the powerful assault 'Mech, they would also damage its seeming aura of invincibility following their ignoble destruction by Clan Jade Falcon on Koniz in June 3064. Seeking to rekindle interest in their flagship 'Mech following its disastrous showing on Koniz, GM/Blackwell noted the Vicore Industries triggered refresh of "classic" designs to develop a more powerful and visually refreshed model. The resulting MAD-4S variant was the first widely available Marauder II, Wolf's Dragoons' easing of sale restrictions partly motivated by profit but also as a means to punish the Lyran Alliance for the theft of the Blackwell developed light fusion engine, as of 3067 selling the 'Mech to all interested parties save those the Dragoons were fighting against in the Chaos March; the Word of Blake and the members of Trinity Alliance. The demand for the Marauder II would only increase in the Jihad following the Blakist destruction of GM and Blackwell's production facilities for the 'Mech as part of their vendetta against the Wolf's Dragoons, with many salvaged examples in use among the nations of the Inner Sphere in a large number of variations following the Blakists' fall, the most notable being the MAD-6D developed by the Federated Suns and shared with the Republic of the Sphere. +history:In 3010 officers of the famous Wolf's Dragoons mercenary unit contracted with Blackwell Industries of New Valencia on the project of modifying the highly successful 75-ton Marauder into a 100-ton assault 'Mech. Working from existing plans the design phase proved to be very short, the process of reinforcing the Marauder chassis turned out to be easier than expected, enhanced by the removal of the finicky and temperamental General Motors Whirlwind Autocannon for a much simpler Large Laser. First appearing with the famous Zeta Battalion before spreading to Alpha Regiment, the Dragoons' enemies soon learned to fear the appearance of Marauder IIs as foreshadowing a major advance, as for the remainder of the Third Succession War it remained the exclusive property of the mysterious Dragoons. This changed after the Fourth Succession War when Colonel Jaime Wolf authorized Blackwell to increase production and allow outside buyers access, on the provision that each sale had to be approved by the Dragoons. Now spreading in limited numbers, the largest buyer outside the Dragoons would be the Miller's Marauders mercenary unit, famed for its almost exclusive use of the Marauder chassis and the secret loan of its DropShips to Zeta Battalion for their climactic rescue of the rest of the Dragoons on Crossing. When new unit commander Major Susan Barber expressed interest in the Marauder II, Colonel Wolf gave Blackwell the go-ahead to supply her with all she needed, by the Clan Invasion the now renamed Barber's Marauders would boast almost a regiment's worth of the fearsome assault 'Mech. Though Barber's Marauder II would help drive the considerable interest and demand for the powerful assault 'Mech, they would also damage its seeming aura of invincibility following their ignoble destruction by Clan Jade Falcon on Koniz in June 3064. Seeking to rekindle interest in their flagship 'Mech following its disastrous showing on Koniz, GM/Blackwell noted the Vicore Industries triggered refresh of "classic" designs to develop a more powerful and visually refreshed model. The resulting MAD-4S variant was the first widely available Marauder II, Wolf's Dragoons' easing of sale restrictions partly motivated by profit but also as a means to punish the Lyran Alliance for the theft of the Blackwell developed light fusion engine, as of 3067 selling the 'Mech to all interested parties save those the Dragoons were fighting against in the Chaos March; the Word of Blake and the members of Trinity Alliance. The demand for the Marauder II would only increase in the Jihad following the Blakist destruction of GM and Blackwell's production facilities for the 'Mech as part of their vendetta against the Wolf's Dragoons, with many salvaged examples in use among the nations of the Inner Sphere in a large number of variations following the Blakists' fall, the most notable being the MAD-6D developed by the Federated Suns and shared with the Republic of the Sphere. manufacturer:General Motors/Blackwell Corporation primaryfactory:New Valencia diff --git a/megameklab/data/mechfiles/mechs/3085u/Phoenix/Marauder II MAD-6M.mtf b/megameklab/data/mechfiles/mechs/3085u/Phoenix/Marauder II MAD-6M.mtf index b0ed18742..dbbe0c153 100644 --- a/megameklab/data/mechfiles/mechs/3085u/Phoenix/Marauder II MAD-6M.mtf +++ b/megameklab/data/mechfiles/mechs/3085u/Phoenix/Marauder II MAD-6M.mtf @@ -163,7 +163,7 @@ capabilities:With the Marauder already a powerful and popular 'Mech, the Dragoon deployment:A refit developed in the fragmented Free Worlds League, the 6M is built around an Endo Steel frame and uses a 400 rated XL Engine to push its top speed to 64 km/h. The jump range is also increased to 120 meters. It carries a Guardian ECM Suite in the torso, but the biggest change is to the weaponry. The dorsal cannon is an ER PPC, while the arm pods mount experimental Large and Medium X-Pulse Lasers. -history:In 3010 officers of the famous Wolf's Dragoons mercenary unit contracted with Blackwell Industries of New Valencia on the project of modifying the highly successful 75-ton Marauder into a 100-ton assault 'Mech. Working from existing plans the design phase proved to be very short, the process of reinforcing the Marauder chassis turned out to be easier than expected, enhanced by the removal of the finicky and temperamental General Motors Whirlwind Autocannon for a much simpler Large Laser. First appearing with the famous Zeta Battalion before spreading to Alpha Regiment, the Dragoons' enemies soon learned to fear the appearance of Marauder IIs as foreshadowing a major advance, as for the remainder of the Third Succession War it remained the exclusive property of the mysterious Dragoons. This changed after the Fourth Succession War when Colonel Jaime Wolf authorized Blackwell to increase production and allow outside buyers access, on the provision that each sale had to be approved by the Dragoons. Now spreading in limited numbers, the largest buyer outside the Dragoons would be the Miller's Marauders mercenary unit, famed for its almost exclusive use of the Marauder chassis and the secret loan of its DropShips to Zeta Battalion for their climactic rescue of the rest of the Dragoons on Crossing. When new unit commander Major Susan Barber expressed interest in the Marauder II, Colonel Wolf gave Blackwell the go-ahead to supply her with all she needed, by the Clan Invasion the now renamed Barber's Marauder II would boast almost a regiment's worth of the fearsome assault 'Mech. Though Barber's Marauder II would help drive the considerable interest and demand for the powerful assault 'Mech, they would also damage its seeming aura of invincibility following their ignoble destruction by Clan Jade Falcon on Koniz in June 3064. Seeking to rekindle interest in their flagship 'Mech following its disastrous showing on Koniz, GM/Blackwell noted the Vicore Industries triggered refresh of "classic" designs to develop a more powerful and visually refreshed model. The resulting MAD-4S variant was the first widely available Marauder II, Wolf's Dragoons' easing of sale restrictions partly motivated by profit but also as a means to punish the Lyran Alliance for the theft of the Blackwell developed light fusion engine, as of 3067 selling the 'Mech to all interested parties save those the Dragoons were fighting against in the Chaos March; the Word of Blake and the members of Trinity Alliance. The demand for the Marauder II would only increase in the Jihad following the Blakist destruction of GM and Blackwell's production facilities for the 'Mech as part of their vendetta against the Wolf's Dragoons, with many salvaged examples in use among the nations of the Inner Sphere in a large number of variations following the Blakists' fall, the most notable being the MAD-6D developed by the Federated Suns and shared with the Republic of the Sphere. +history:In 3010 officers of the famous Wolf's Dragoons mercenary unit contracted with Blackwell Industries of New Valencia on the project of modifying the highly successful 75-ton Marauder into a 100-ton assault 'Mech. Working from existing plans the design phase proved to be very short, the process of reinforcing the Marauder chassis turned out to be easier than expected, enhanced by the removal of the finicky and temperamental General Motors Whirlwind Autocannon for a much simpler Large Laser. First appearing with the famous Zeta Battalion before spreading to Alpha Regiment, the Dragoons' enemies soon learned to fear the appearance of Marauder IIs as foreshadowing a major advance, as for the remainder of the Third Succession War it remained the exclusive property of the mysterious Dragoons. This changed after the Fourth Succession War when Colonel Jaime Wolf authorized Blackwell to increase production and allow outside buyers access, on the provision that each sale had to be approved by the Dragoons. Now spreading in limited numbers, the largest buyer outside the Dragoons would be the Miller's Marauders mercenary unit, famed for its almost exclusive use of the Marauder chassis and the secret loan of its DropShips to Zeta Battalion for their climactic rescue of the rest of the Dragoons on Crossing. When new unit commander Major Susan Barber expressed interest in the Marauder II, Colonel Wolf gave Blackwell the go-ahead to supply her with all she needed, by the Clan Invasion the now renamed Barber's Marauders would boast almost a regiment's worth of the fearsome assault 'Mech. Though Barber's Marauder II would help drive the considerable interest and demand for the powerful assault 'Mech, they would also damage its seeming aura of invincibility following their ignoble destruction by Clan Jade Falcon on Koniz in June 3064. Seeking to rekindle interest in their flagship 'Mech following its disastrous showing on Koniz, GM/Blackwell noted the Vicore Industries triggered refresh of "classic" designs to develop a more powerful and visually refreshed model. The resulting MAD-4S variant was the first widely available Marauder II, Wolf's Dragoons' easing of sale restrictions partly motivated by profit but also as a means to punish the Lyran Alliance for the theft of the Blackwell developed light fusion engine, as of 3067 selling the 'Mech to all interested parties save those the Dragoons were fighting against in the Chaos March; the Word of Blake and the members of Trinity Alliance. The demand for the Marauder II would only increase in the Jihad following the Blakist destruction of GM and Blackwell's production facilities for the 'Mech as part of their vendetta against the Wolf's Dragoons, with many salvaged examples in use among the nations of the Inner Sphere in a large number of variations following the Blakists' fall, the most notable being the MAD-6D developed by the Federated Suns and shared with the Republic of the Sphere. manufacturer:Field Refit primaryfactory:Various diff --git a/megameklab/data/mechfiles/mechs/3085u/Phoenix/Ostscout OTT-10CS.mtf b/megameklab/data/mechfiles/mechs/3085u/Phoenix/Ostscout OTT-10CS.mtf index 68da80371..c3415cd49 100644 --- a/megameklab/data/mechfiles/mechs/3085u/Phoenix/Ostscout OTT-10CS.mtf +++ b/megameklab/data/mechfiles/mechs/3085u/Phoenix/Ostscout OTT-10CS.mtf @@ -163,7 +163,7 @@ capabilities:The Ostscout is quick enough to escape most traps, and very few oth deployment:Produced by Krupp Armament Works, the 10CS Ostscout saves weight through the use of an XL Engine and an XL Gyro, which gives up durability for more combat payload weight, allowing the 'Mech to jump up to 300 meters through the use of ten Rawlings 45i Improved Jump Jets. The 10CS carries an improved C3 computer to communicate with similarly equipped units and carries two Diverse Optics ER Medium Lasers for defensive combat capabilities. -history:Starting in 2600 Ostmann built and sold the Ostscout to fulfill many armies' need for a swift reconnaissance 'Mech, but eventually found that demand was outstripping their production ability. Rather than sacrifice their popular Ostroc line of urban-combat 'Mechs, the company licensed Kong Interstellar to start building the 'Mech in 2700, an arrangement similar to that struck regarding the Ostsol. Kong would continue to build Ostscouts for the next hundred years until the destruction of their factory on Connaught at the outset of the Succession Wars. Deprive of the possibility of replacement, many commanders began to hoard their Ostscouts like valuable treasure, parceling them out only for special missions. Most Ostscout pilots would not even attempt to engage enemy 'Mechs, as the advanced sensor system became extremely rare and nearly impossible to replace. This unwillingness to put the 'Mech in danger meant many survived the Succession Wars in practically mint condition, although many which suffered damage to their advanced sensors were forced to replace them with inferior, albeit more robust, systems. Besides the Great Houses, ComStar also utilized the Ostscout, and in the aftermath of the Clan Invasion and ComStar Schism began developing a new Ostscout variant for their Com Guards. This new model would maintain the same maneuverability and intelligence-gathering capabilities of the original while improving its offensive and defensive capabilities. Debuting with success in 3064, within the next three years nearly half of all Com Guard Ostscouts had been upgraded to the new variant; however it was soon discovered that both the Lyran Alliance and Word of Blake were fielding their own updated Ostscouts identical to ComStar's. The intelligence leak would be confirmed and traced back to Dag Kesselring, former Precentor of the 66th Division, who passed on information about the program to both the Lyrans and Blakists. Used by both sides in the Blakist Jihad, the newborn Republic of the Sphere would maintain production of the 11J model Ostscout after the fall of Terra both for its own relatively limited needs as well as export sales to the Federated Suns and Lyran Commonwealth. Still produced during the Dark Age era, aside from the Krupp plant's combat focused Phoenix models both Kong Interstellar and Robinson Standard BattleWorks reintroduced variants that lean more heavily towards the original look and recon aspects of the venerable 7J model. +history:Starting in 2600 Ostmann built and sold the Ostscout to fulfill many armies' need for a swift reconnaissance 'Mech, but eventually found that demand was outstripping their production ability. Rather than sacrifice their popular Ostroc line of urban-combat 'Mechs, the company licensed Kong Interstellar to start building the 'Mech in 2700, an arrangement similar to that struck regarding the Ostsol. Kong would continue to build Ostscouts for the next hundred years until the destruction of their factory on Connaught at the outset of the Succession Wars. Deprived of the possibility of replacement, many commanders began to hoard their Ostscouts like valuable treasure, parceling them out only for special missions. Most Ostscout pilots would not even attempt to engage enemy 'Mechs, as the advanced sensor system became extremely rare and nearly impossible to replace. This unwillingness to put the 'Mech in danger meant many survived the Succession Wars in practically mint condition, although many which suffered damage to their advanced sensors were forced to replace them with inferior, albeit more robust, systems. Besides the Great Houses, ComStar also utilized the Ostscout, and in the aftermath of the Clan Invasion and ComStar Schism began developing a new Ostscout variant for their Com Guards. This new model would maintain the same maneuverability and intelligence-gathering capabilities of the original while improving its offensive and defensive capabilities. Debuting with success in 3064, within the next three years nearly half of all Com Guard Ostscouts had been upgraded to the new variant; however it was soon discovered that both the Lyran Alliance and Word of Blake were fielding their own updated Ostscouts identical to ComStar's. The intelligence leak would be confirmed and traced back to Dag Kesselring, former Precentor of the 66th Division, who passed on information about the program to both the Lyrans and Blakists. Used by both sides in the Blakist Jihad, the newborn Republic of the Sphere would maintain production of the 11J model Ostscout after the fall of Terra both for its own relatively limited needs as well as export sales to the Federated Suns and Lyran Commonwealth. Still produced during the Dark Age era, aside from the Krupp plant's combat focused Phoenix models both Kong Interstellar and Robinson Standard BattleWorks reintroduced variants that lean more heavily towards the original look and recon aspects of the venerable 7J model. manufacturer:Odin Manufacturing,Krupp Armament Works primaryfactory:Orestes,Terra diff --git a/megameklab/data/mechfiles/mechs/3085u/Phoenix/Ostscout OTT-11J.mtf b/megameklab/data/mechfiles/mechs/3085u/Phoenix/Ostscout OTT-11J.mtf index f04a88e9e..29c787ceb 100644 --- a/megameklab/data/mechfiles/mechs/3085u/Phoenix/Ostscout OTT-11J.mtf +++ b/megameklab/data/mechfiles/mechs/3085u/Phoenix/Ostscout OTT-11J.mtf @@ -162,7 +162,7 @@ capabilities:The Ostscout is quick enough to escape most traps, and very few oth deployment:This variant is also produced by Krupp Armament Works. The top speed of the 'Mech is close to 150 km/h thanks to a GM 315 XL Engine. It uses eight standard jump jets and Ferro-Fibrous Armor, but removes all the advanced electronic equipment except for a TAG. The weapons and electronics are replaced by a pair of Moscovia Light PPCs. -history:Starting in 2600 Ostmann built and sold the Ostscout to fulfill many armies' need for a swift reconnaissance 'Mech, but eventually found that demand was outstripping their production ability. Rather than sacrifice their popular Ostroc line of urban-combat 'Mechs, the company licensed Kong Interstellar to start building the 'Mech in 2700, an arrangement similar to that struck regarding the Ostsol. Kong would continue to build Ostscouts for the next hundred years until the destruction of their factory on Connaught at the outset of the Succession Wars. Deprive of the possibility of replacement, many commanders began to hoard their Ostscouts like valuable treasure, parceling them out only for special missions. Most Ostscout pilots would not even attempt to engage enemy 'Mechs, as the advanced sensor system became extremely rare and nearly impossible to replace. This unwillingness to put the 'Mech in danger meant many survived the Succession Wars in practically mint condition, although many which suffered damage to their advanced sensors were forced to replace them with inferior, albeit more robust, systems. Besides the Great Houses, ComStar also utilized the Ostscout, and in the aftermath of the Clan Invasion and ComStar Schism began developing a new Ostscout variant for their Com Guards. This new model would maintain the same maneuverability and intelligence-gathering capabilities of the original while improving its offensive and defensive capabilities. Debuting with success in 3064, within the next three years nearly half of all Com Guard Ostscouts had been upgraded to the new variant; however it was soon discovered that both the Lyran Alliance and Word of Blake were fielding their own updated Ostscouts identical to ComStar's. The intelligence leak would be confirmed and traced back to Dag Kesselring, former Precentor of the 66th Division, who passed on information about the program to both the Lyrans and Blakists. Used by both sides in the Blakist Jihad, the newborn Republic of the Sphere would maintain production of the 11J model Ostscout after the fall of Terra both for its own relatively limited needs as well as export sales to the Federated Suns and Lyran Commonwealth. Still produced during the Dark Age era, aside from the Krupp plant's combat focused Phoenix models both Kong Interstellar and Robinson Standard BattleWorks reintroduced variants that lean more heavily towards the original look and recon aspects of the venerable 7J model. +history:Starting in 2600 Ostmann built and sold the Ostscout to fulfill many armies' need for a swift reconnaissance 'Mech, but eventually found that demand was outstripping their production ability. Rather than sacrifice their popular Ostroc line of urban-combat 'Mechs, the company licensed Kong Interstellar to start building the 'Mech in 2700, an arrangement similar to that struck regarding the Ostsol. Kong would continue to build Ostscouts for the next hundred years until the destruction of their factory on Connaught at the outset of the Succession Wars. Deprived of the possibility of replacement, many commanders began to hoard their Ostscouts like valuable treasure, parceling them out only for special missions. Most Ostscout pilots would not even attempt to engage enemy 'Mechs, as the advanced sensor system became extremely rare and nearly impossible to replace. This unwillingness to put the 'Mech in danger meant many survived the Succession Wars in practically mint condition, although many which suffered damage to their advanced sensors were forced to replace them with inferior, albeit more robust, systems. Besides the Great Houses, ComStar also utilized the Ostscout, and in the aftermath of the Clan Invasion and ComStar Schism began developing a new Ostscout variant for their Com Guards. This new model would maintain the same maneuverability and intelligence-gathering capabilities of the original while improving its offensive and defensive capabilities. Debuting with success in 3064, within the next three years nearly half of all Com Guard Ostscouts had been upgraded to the new variant; however it was soon discovered that both the Lyran Alliance and Word of Blake were fielding their own updated Ostscouts identical to ComStar's. The intelligence leak would be confirmed and traced back to Dag Kesselring, former Precentor of the 66th Division, who passed on information about the program to both the Lyrans and Blakists. Used by both sides in the Blakist Jihad, the newborn Republic of the Sphere would maintain production of the 11J model Ostscout after the fall of Terra both for its own relatively limited needs as well as export sales to the Federated Suns and Lyran Commonwealth. Still produced during the Dark Age era, aside from the Krupp plant's combat focused Phoenix models both Kong Interstellar and Robinson Standard BattleWorks reintroduced variants that lean more heavily towards the original look and recon aspects of the venerable 7J model. manufacturer:Krupp Armament Works primaryfactory:Terra diff --git a/megameklab/data/mechfiles/mechs/3085u/Phoenix/Ostscout OTT-7K.mtf b/megameklab/data/mechfiles/mechs/3085u/Phoenix/Ostscout OTT-7K.mtf index 105e00480..378520775 100644 --- a/megameklab/data/mechfiles/mechs/3085u/Phoenix/Ostscout OTT-7K.mtf +++ b/megameklab/data/mechfiles/mechs/3085u/Phoenix/Ostscout OTT-7K.mtf @@ -160,7 +160,7 @@ capabilities:The Ostscout is quick enough to escape most traps, and very few oth deployment:The 7K Ostscout was introduced in 3050 and replaces the medium laser with a Garret Mole TAG laser designator, sacrificing its limited offensive capability to allow it to designate targets for Arrow IV artillery missiles. Otherwise, the 7K Ostscout is identical to the 7J model, and while utterly defenseless is still swift enough to escape from most danger. -history:Starting in 2600 Ostmann built and sold the Ostscout to fulfill many armies' need for a swift reconnaissance 'Mech, but eventually found that demand was outstripping their production ability. Rather than sacrifice their popular Ostroc line of urban-combat 'Mechs, the company licensed Kong Interstellar to start building the 'Mech in 2700, an arrangement similar to that struck regarding the Ostsol. Kong would continue to build Ostscouts for the next hundred years until the destruction of their factory on Connaught at the outset of the Succession Wars. Deprive of the possibility of replacement, many commanders began to hoard their Ostscouts like valuable treasure, parceling them out only for special missions. Most Ostscout pilots would not even attempt to engage enemy 'Mechs, as the advanced sensor system became extremely rare and nearly impossible to replace. This unwillingness to put the 'Mech in danger meant many survived the Succession Wars in practically mint condition, although many which suffered damage to their advanced sensors were forced to replace them with inferior, albeit more robust, systems. Besides the Great Houses, ComStar also utilized the Ostscout, and in the aftermath of the Clan Invasion and ComStar Schism began developing a new Ostscout variant for their Com Guards. This new model would maintain the same maneuverability and intelligence-gathering capabilities of the original while improving its offensive and defensive capabilities. Debuting with success in 3064, within the next three years nearly half of all Com Guard Ostscouts had been upgraded to the new variant; however it was soon discovered that both the Lyran Alliance and Word of Blake were fielding their own updated Ostscouts identical to ComStar's. The intelligence leak would be confirmed and traced back to Dag Kesselring, former Precentor of the 66th Division, who passed on information about the program to both the Lyrans and Blakists. Used by both sides in the Blakist Jihad, the newborn Republic of the Sphere would maintain production of the 11J model Ostscout after the fall of Terra both for its own relatively limited needs as well as export sales to the Federated Suns and Lyran Commonwealth. Still produced during the Dark Age era, aside from the Krupp plant's combat focused Phoenix models both Kong Interstellar and Robinson Standard BattleWorks reintroduced variants that lean more heavily towards the original look and recon aspects of the venerable 7J model. +history:Starting in 2600 Ostmann built and sold the Ostscout to fulfill many armies' need for a swift reconnaissance 'Mech, but eventually found that demand was outstripping their production ability. Rather than sacrifice their popular Ostroc line of urban-combat 'Mechs, the company licensed Kong Interstellar to start building the 'Mech in 2700, an arrangement similar to that struck regarding the Ostsol. Kong would continue to build Ostscouts for the next hundred years until the destruction of their factory on Connaught at the outset of the Succession Wars. Deprived of the possibility of replacement, many commanders began to hoard their Ostscouts like valuable treasure, parceling them out only for special missions. Most Ostscout pilots would not even attempt to engage enemy 'Mechs, as the advanced sensor system became extremely rare and nearly impossible to replace. This unwillingness to put the 'Mech in danger meant many survived the Succession Wars in practically mint condition, although many which suffered damage to their advanced sensors were forced to replace them with inferior, albeit more robust, systems. Besides the Great Houses, ComStar also utilized the Ostscout, and in the aftermath of the Clan Invasion and ComStar Schism began developing a new Ostscout variant for their Com Guards. This new model would maintain the same maneuverability and intelligence-gathering capabilities of the original while improving its offensive and defensive capabilities. Debuting with success in 3064, within the next three years nearly half of all Com Guard Ostscouts had been upgraded to the new variant; however it was soon discovered that both the Lyran Alliance and Word of Blake were fielding their own updated Ostscouts identical to ComStar's. The intelligence leak would be confirmed and traced back to Dag Kesselring, former Precentor of the 66th Division, who passed on information about the program to both the Lyrans and Blakists. Used by both sides in the Blakist Jihad, the newborn Republic of the Sphere would maintain production of the 11J model Ostscout after the fall of Terra both for its own relatively limited needs as well as export sales to the Federated Suns and Lyran Commonwealth. Still produced during the Dark Age era, aside from the Krupp plant's combat focused Phoenix models both Kong Interstellar and Robinson Standard BattleWorks reintroduced variants that lean more heavily towards the original look and recon aspects of the venerable 7J model. manufacturer:Field Refit primaryfactory:Various diff --git a/megameklab/data/mechfiles/mechs/3085u/Phoenix/Ostscout OTT-9CS.mtf b/megameklab/data/mechfiles/mechs/3085u/Phoenix/Ostscout OTT-9CS.mtf index ec17ec2e7..1c8f7ff48 100644 --- a/megameklab/data/mechfiles/mechs/3085u/Phoenix/Ostscout OTT-9CS.mtf +++ b/megameklab/data/mechfiles/mechs/3085u/Phoenix/Ostscout OTT-9CS.mtf @@ -163,7 +163,7 @@ capabilities:The Ostscout is quick enough to escape most traps, and very few oth deployment:The 9CS model is a complete upgrade of the venerable Ostscout, developed by ComStar and introduced in 3064. The 'Mech has been rebuilt from the ground up with a Krupp 255 Endo Steel internal structure. While still maintaining the same number of jump jets the design uses a 280 VOX extralight engine to free up weight for advanced electronics and weaponry. The arm-mounted sensor arrays were shifted to fixed points around the torso and included new side-scanning, Doppler and triangulation sensors to maintain the same data-gathering capability. Additionally a new high-speed computer, capable of handling terabytes of data in seconds, meant the Ostscout no longer had to slow down when using its sensors. The targeting-tracking system was also replaced with a TRSS Eagle Eye system mated to a Beagle Active Probe, Guardian ECM, and head-mounted TAG, while the comm system was upgraded to the Exeter Longscan 300 w/C3i Computer for better fire mission coordination. For self-defense, the 9CS model carries two Diverse Optics ER Medium Lasers in either arm and an Diverse Optics ER Small Laser in its center torso. Finally six tons of Krupp 155 Ferro-Fibrous armor provides superior protection from weapons fire. -history:Starting in 2600 Ostmann built and sold the Ostscout to fulfill many armies' need for a swift reconnaissance 'Mech, but eventually found that demand was outstripping their production ability. Rather than sacrifice their popular Ostroc line of urban-combat 'Mechs, the company licensed Kong Interstellar to start building the 'Mech in 2700, an arrangement similar to that struck regarding the Ostsol. Kong would continue to build Ostscouts for the next hundred years until the destruction of their factory on Connaught at the outset of the Succession Wars. Deprive of the possibility of replacement, many commanders began to hoard their Ostscouts like valuable treasure, parceling them out only for special missions. Most Ostscout pilots would not even attempt to engage enemy 'Mechs, as the advanced sensor system became extremely rare and nearly impossible to replace. This unwillingness to put the 'Mech in danger meant many survived the Succession Wars in practically mint condition, although many which suffered damage to their advanced sensors were forced to replace them with inferior, albeit more robust, systems. Besides the Great Houses, ComStar also utilized the Ostscout, and in the aftermath of the Clan Invasion and ComStar Schism began developing a new Ostscout variant for their Com Guards. This new model would maintain the same maneuverability and intelligence-gathering capabilities of the original while improving its offensive and defensive capabilities. Debuting with success in 3064, within the next three years nearly half of all Com Guard Ostscouts had been upgraded to the new variant; however it was soon discovered that both the Lyran Alliance and Word of Blake were fielding their own updated Ostscouts identical to ComStar's. The intelligence leak would be confirmed and traced back to Dag Kesselring, former Precentor of the 66th Division, who passed on information about the program to both the Lyrans and Blakists. Used by both sides in the Blakist Jihad, the newborn Republic of the Sphere would maintain production of the 11J model Ostscout after the fall of Terra both for its own relatively limited needs as well as export sales to the Federated Suns and Lyran Commonwealth. Still produced during the Dark Age era, aside from the Krupp plant's combat focused Phoenix models both Kong Interstellar and Robinson Standard BattleWorks reintroduced variants that lean more heavily towards the original look and recon aspects of the venerable 7J model. +history:Starting in 2600 Ostmann built and sold the Ostscout to fulfill many armies' need for a swift reconnaissance 'Mech, but eventually found that demand was outstripping their production ability. Rather than sacrifice their popular Ostroc line of urban-combat 'Mechs, the company licensed Kong Interstellar to start building the 'Mech in 2700, an arrangement similar to that struck regarding the Ostsol. Kong would continue to build Ostscouts for the next hundred years until the destruction of their factory on Connaught at the outset of the Succession Wars. Deprived of the possibility of replacement, many commanders began to hoard their Ostscouts like valuable treasure, parceling them out only for special missions. Most Ostscout pilots would not even attempt to engage enemy 'Mechs, as the advanced sensor system became extremely rare and nearly impossible to replace. This unwillingness to put the 'Mech in danger meant many survived the Succession Wars in practically mint condition, although many which suffered damage to their advanced sensors were forced to replace them with inferior, albeit more robust, systems. Besides the Great Houses, ComStar also utilized the Ostscout, and in the aftermath of the Clan Invasion and ComStar Schism began developing a new Ostscout variant for their Com Guards. This new model would maintain the same maneuverability and intelligence-gathering capabilities of the original while improving its offensive and defensive capabilities. Debuting with success in 3064, within the next three years nearly half of all Com Guard Ostscouts had been upgraded to the new variant; however it was soon discovered that both the Lyran Alliance and Word of Blake were fielding their own updated Ostscouts identical to ComStar's. The intelligence leak would be confirmed and traced back to Dag Kesselring, former Precentor of the 66th Division, who passed on information about the program to both the Lyrans and Blakists. Used by both sides in the Blakist Jihad, the newborn Republic of the Sphere would maintain production of the 11J model Ostscout after the fall of Terra both for its own relatively limited needs as well as export sales to the Federated Suns and Lyran Commonwealth. Still produced during the Dark Age era, aside from the Krupp plant's combat focused Phoenix models both Kong Interstellar and Robinson Standard BattleWorks reintroduced variants that lean more heavily towards the original look and recon aspects of the venerable 7J model. manufacturer:Kong Interstellar Corporation,Kong Interstellar Corporation,Ostmann Industries primaryfactory:Connaught,Loxley,Terra diff --git a/megameklab/data/mechfiles/mechs/3085u/Phoenix/Ostscout OTT-9S.mtf b/megameklab/data/mechfiles/mechs/3085u/Phoenix/Ostscout OTT-9S.mtf index 486616442..b0738f916 100644 --- a/megameklab/data/mechfiles/mechs/3085u/Phoenix/Ostscout OTT-9S.mtf +++ b/megameklab/data/mechfiles/mechs/3085u/Phoenix/Ostscout OTT-9S.mtf @@ -162,7 +162,7 @@ capabilities:The Ostscout is quick enough to escape most traps, and very few oth deployment:The -9S model is also a rebuild of the Ostscout. This model also uses an Endo Steel chassis, as well as Ferro-Fibrous armor. For protection, the 'Mech carries two ER Medium Lasers and two Anti-Personnel Pods to discourage infantry attacks. The electronics carried by this 'Mech include a Beagle Active Probe, Guardian ECM suite, and a TAG laser designator. -history:Starting in 2600 Ostmann built and sold the Ostscout to fulfill many armies' need for a swift reconnaissance 'Mech, but eventually found that demand was outstripping their production ability. Rather than sacrifice their popular Ostroc line of urban-combat 'Mechs, the company licensed Kong Interstellar to start building the 'Mech in 2700, an arrangement similar to that struck regarding the Ostsol. Kong would continue to build Ostscouts for the next hundred years until the destruction of their factory on Connaught at the outset of the Succession Wars. Deprive of the possibility of replacement, many commanders began to hoard their Ostscouts like valuable treasure, parceling them out only for special missions. Most Ostscout pilots would not even attempt to engage enemy 'Mechs, as the advanced sensor system became extremely rare and nearly impossible to replace. This unwillingness to put the 'Mech in danger meant many survived the Succession Wars in practically mint condition, although many which suffered damage to their advanced sensors were forced to replace them with inferior, albeit more robust, systems. Besides the Great Houses, ComStar also utilized the Ostscout, and in the aftermath of the Clan Invasion and ComStar Schism began developing a new Ostscout variant for their Com Guards. This new model would maintain the same maneuverability and intelligence-gathering capabilities of the original while improving its offensive and defensive capabilities. Debuting with success in 3064, within the next three years nearly half of all Com Guard Ostscouts had been upgraded to the new variant; however it was soon discovered that both the Lyran Alliance and Word of Blake were fielding their own updated Ostscouts identical to ComStar's. The intelligence leak would be confirmed and traced back to Dag Kesselring, former Precentor of the 66th Division, who passed on information about the program to both the Lyrans and Blakists. Used by both sides in the Blakist Jihad, the newborn Republic of the Sphere would maintain production of the 11J model Ostscout after the fall of Terra both for its own relatively limited needs as well as export sales to the Federated Suns and Lyran Commonwealth. Still produced during the Dark Age era, aside from the Krupp plant's combat focused Phoenix models both Kong Interstellar and Robinson Standard BattleWorks reintroduced variants that lean more heavily towards the original look and recon aspects of the venerable 7J model. +history:Starting in 2600 Ostmann built and sold the Ostscout to fulfill many armies' need for a swift reconnaissance 'Mech, but eventually found that demand was outstripping their production ability. Rather than sacrifice their popular Ostroc line of urban-combat 'Mechs, the company licensed Kong Interstellar to start building the 'Mech in 2700, an arrangement similar to that struck regarding the Ostsol. Kong would continue to build Ostscouts for the next hundred years until the destruction of their factory on Connaught at the outset of the Succession Wars. Deprived of the possibility of replacement, many commanders began to hoard their Ostscouts like valuable treasure, parceling them out only for special missions. Most Ostscout pilots would not even attempt to engage enemy 'Mechs, as the advanced sensor system became extremely rare and nearly impossible to replace. This unwillingness to put the 'Mech in danger meant many survived the Succession Wars in practically mint condition, although many which suffered damage to their advanced sensors were forced to replace them with inferior, albeit more robust, systems. Besides the Great Houses, ComStar also utilized the Ostscout, and in the aftermath of the Clan Invasion and ComStar Schism began developing a new Ostscout variant for their Com Guards. This new model would maintain the same maneuverability and intelligence-gathering capabilities of the original while improving its offensive and defensive capabilities. Debuting with success in 3064, within the next three years nearly half of all Com Guard Ostscouts had been upgraded to the new variant; however it was soon discovered that both the Lyran Alliance and Word of Blake were fielding their own updated Ostscouts identical to ComStar's. The intelligence leak would be confirmed and traced back to Dag Kesselring, former Precentor of the 66th Division, who passed on information about the program to both the Lyrans and Blakists. Used by both sides in the Blakist Jihad, the newborn Republic of the Sphere would maintain production of the 11J model Ostscout after the fall of Terra both for its own relatively limited needs as well as export sales to the Federated Suns and Lyran Commonwealth. Still produced during the Dark Age era, aside from the Krupp plant's combat focused Phoenix models both Kong Interstellar and Robinson Standard BattleWorks reintroduced variants that lean more heavily towards the original look and recon aspects of the venerable 7J model. manufacturer:Blackstone BattleMechs, Ltd primaryfactory:Inarcs diff --git a/megameklab/data/mechfiles/mechs/3085u/Phoenix/Wolverine WVR-8C.mtf b/megameklab/data/mechfiles/mechs/3085u/Phoenix/Wolverine WVR-8C.mtf index 7a209b7b3..56d4179ec 100644 --- a/megameklab/data/mechfiles/mechs/3085u/Phoenix/Wolverine WVR-8C.mtf +++ b/megameklab/data/mechfiles/mechs/3085u/Phoenix/Wolverine WVR-8C.mtf @@ -168,7 +168,7 @@ capabilities:The autocannon, missile system and laser found on most Wolverines a deployment:The 8C variant of the Wolverine, introduced by Victory Industries in 3067 after the success of the 8K, is built on an Endo Steel chassis and uses an XL Engine for power. It carries a large pulse laser as its primary weapon, as well as a medium pulse laser and a small pulse laser. For additional close-combat capability this version carries two Streak SRM-6 launchers while a C3 Slave Unit allows it to share targeting telemetry with friendly units but only carries thirteen double heat sinks. -history:A widespread part of every major military, the Wolverine has manufacturing plants scattered throughout the entire Inner Sphere. While certain states-notable the Free Worlds League-have larger numbers of the design, only the Capellans began facing a shortage of the Wolverine after the loss of their Nanking facilities. +history:A widespread part of every major military, the Wolverine has manufacturing plants scattered throughout the entire Inner Sphere. While certain states-notably the Free Worlds League-have larger numbers of the design, only the Capellans began facing a shortage of the Wolverine after the loss of their Nanking facilities. manufacturer:Victory Industries (formerly Norse BattleMech Works) primaryfactory:Marduk diff --git a/megameklab/data/mechfiles/mechs/3085u/Phoenix/Wolverine WVR-8D.mtf b/megameklab/data/mechfiles/mechs/3085u/Phoenix/Wolverine WVR-8D.mtf index 1b9d6a6f0..d5f34faaf 100644 --- a/megameklab/data/mechfiles/mechs/3085u/Phoenix/Wolverine WVR-8D.mtf +++ b/megameklab/data/mechfiles/mechs/3085u/Phoenix/Wolverine WVR-8D.mtf @@ -166,7 +166,7 @@ capabilities:The autocannon, missile system and laser found on most Wolverines a deployment:The 8D Wolverine is an one of two updated versions introduced by Kallon in 3066 that incorporates some of the newest equipment to the AFFS. The 'Mech is built with an Endo Steel chassis and uses an XL engine augmented with MASC, enabling speeds of up to 108 km/h. Its main gun is a Rotary Autocannon/2, backed up by an ER Medium Laser and a Streak SRM-6 launcher. Both the Rotary Autocannon and the ER Medium Laser are linked to an advanced Targeting Computer, making the Wolverine extremely accurate. However the design carries only ten double heat sinks. -history:A widespread part of every major military, the Wolverine has manufacturing plants scattered throughout the entire Inner Sphere. While certain states-notable the Free Worlds League-have larger numbers of the design, only the Capellans began facing a shortage of the Wolverine after the loss of their Nanking facilities. +history:A widespread part of every major military, the Wolverine has manufacturing plants scattered throughout the entire Inner Sphere. While certain states-notably the Free Worlds League-have larger numbers of the design, only the Capellans began facing a shortage of the Wolverine after the loss of their Nanking facilities. manufacturer:Victory Industries (formerly Norse BattleMech Works),Kallon Weapon Industries primaryfactory:Marduk,Talon (Wernke) diff --git a/megameklab/data/mechfiles/mechs/3085u/Phoenix/Wolverine WVR-8K.mtf b/megameklab/data/mechfiles/mechs/3085u/Phoenix/Wolverine WVR-8K.mtf index 1d2b09d01..c8097e642 100644 --- a/megameklab/data/mechfiles/mechs/3085u/Phoenix/Wolverine WVR-8K.mtf +++ b/megameklab/data/mechfiles/mechs/3085u/Phoenix/Wolverine WVR-8K.mtf @@ -167,7 +167,7 @@ capabilities:The autocannon, missile system and laser found on most Wolverines a deployment:The 8K Wolverine was first introduced for the Combine in 3064 when Victory Industries decided to update the design. It is built using an XL engine for power and uses fifteen double heat sinks for its high heat load. This variant carries, as its main weapon, a Lords Light ER PPC in the right arm backed up by an Diverse Optics ER medium laser also in the right arm and a Victory Heartbeat medium pulse laser in the head. Finally, to exploit any weak points in an enemy's armor, the 'Mech carries a Guided Technologies Second Gen Streak SRM-6 launcher in the left torso along with one ton of ammo. Twelve tons of Starshield A armor with CASE provide additional protection, with the plating designed specifically to make repairs quicker to accomplish. Although certain prestigious Combine units turned their noses up at using a refurbished 'Mech to replenish their ranks, many others were less picky and the design proliferated after its success on Al Na'ir. -history:A widespread part of every major military, the Wolverine has manufacturing plants scattered throughout the entire Inner Sphere. While certain states-notable the Free Worlds League-have larger numbers of the design, only the Capellans began facing a shortage of the Wolverine after the loss of their Nanking facilities. +history:A widespread part of every major military, the Wolverine has manufacturing plants scattered throughout the entire Inner Sphere. While certain states-notably the Free Worlds League-have larger numbers of the design, only the Capellans began facing a shortage of the Wolverine after the loss of their Nanking facilities. manufacturer:Victory Industries (formerly Norse BattleMech Works) primaryfactory:Marduk diff --git a/megameklab/data/mechfiles/mechs/3085u/Phoenix/Wolverine WVR-9D.mtf b/megameklab/data/mechfiles/mechs/3085u/Phoenix/Wolverine WVR-9D.mtf index 698628df4..06c9c91ad 100644 --- a/megameklab/data/mechfiles/mechs/3085u/Phoenix/Wolverine WVR-9D.mtf +++ b/megameklab/data/mechfiles/mechs/3085u/Phoenix/Wolverine WVR-9D.mtf @@ -168,7 +168,7 @@ capabilities:The autocannon, missile system and laser found on most Wolverines a deployment:The 9D Wolverine is the companion of the 8D and shares some similarities, such as the Endo Steel chassis and the XL engine. First fielded at the same time as the 8D the 'Mech carries, as its main weapon, a Rotary Autocannon/2 backed up by two medium pulse lasers and a Streak SRM-6 launcher. It also carries a TAG laser designator, to designate targets for Arrow IV artillery attacks. Unlike the 8D, this variant does not jump, though it does retain the MASC and has twelve double heat sinks. -history:A widespread part of every major military, the Wolverine has manufacturing plants scattered throughout the entire Inner Sphere. While certain states-notable the Free Worlds League-have larger numbers of the design, only the Capellans began facing a shortage of the Wolverine after the loss of their Nanking facilities. +history:A widespread part of every major military, the Wolverine has manufacturing plants scattered throughout the entire Inner Sphere. While certain states-notably the Free Worlds League-have larger numbers of the design, only the Capellans began facing a shortage of the Wolverine after the loss of their Nanking facilities. manufacturer:Kallon Weapon Industries primaryfactory:Talon (Wernke) diff --git a/megameklab/data/mechfiles/mechs/3085u/Phoenix/Wolverine WVR-9K.mtf b/megameklab/data/mechfiles/mechs/3085u/Phoenix/Wolverine WVR-9K.mtf index 57d5ed2c6..93ad3c2f4 100644 --- a/megameklab/data/mechfiles/mechs/3085u/Phoenix/Wolverine WVR-9K.mtf +++ b/megameklab/data/mechfiles/mechs/3085u/Phoenix/Wolverine WVR-9K.mtf @@ -173,7 +173,7 @@ capabilities:The autocannon, missile system and laser found on most Wolverines a deployment:The 9K Wolverine introduced in 3074 uses a Light Engine for power. The resulting decrease in tonnage necessitated a complete revision of the weapon systems. Its main gun is the Snub-Nose PPC mounted in the right arm. An SRM-4 is the only other heat-building weapon mounted on the 'Mech. A trio of Light Machine Guns are also in the arm, linked to a Machine Gun Array to deter infantry. To counteract battle armor, the 9K carries a pair of B-Pods. This Wolverine variant carries a Sword in its left hand and a C3 Slave in the head to feed targeting telemetry back to lance-mates. Triple Strength Myomers make the sword more powerful and the design faster when they heat up, but a MechWarrior must disengage some of the ten double heat sinks in order to build the necessary heat. In light of the heavier engine, the inclusion of a Compact Gyro seems unhelpful at best. -history:A widespread part of every major military, the Wolverine has manufacturing plants scattered throughout the entire Inner Sphere. While certain states-notable the Free Worlds League-have larger numbers of the design, only the Capellans began facing a shortage of the Wolverine after the loss of their Nanking facilities. +history:A widespread part of every major military, the Wolverine has manufacturing plants scattered throughout the entire Inner Sphere. While certain states-notably the Free Worlds League-have larger numbers of the design, only the Capellans began facing a shortage of the Wolverine after the loss of their Nanking facilities. manufacturer:Victory Industries (formerly Norse BattleMech Works) primaryfactory:Marduk diff --git a/megameklab/data/mechfiles/mechs/3085u/Phoenix/Wolverine WVR-9M.mtf b/megameklab/data/mechfiles/mechs/3085u/Phoenix/Wolverine WVR-9M.mtf index b5f708ee7..fcbdb1e83 100644 --- a/megameklab/data/mechfiles/mechs/3085u/Phoenix/Wolverine WVR-9M.mtf +++ b/megameklab/data/mechfiles/mechs/3085u/Phoenix/Wolverine WVR-9M.mtf @@ -166,7 +166,7 @@ capabilities:The autocannon, missile system and laser found on most Wolverines a deployment:The Wolverine 9M introduced in 3073 is powered by a Nissan XL Engine that allows the 'Mech to move at speeds of up to 86.4 km/h while sacrificing durability. The 9M can also jump up to one hundred and fifty meters, as with most other variants. The 9M is armed with a Fusigon Strongtooth Heavy PPC as its primary weapon, which has a similar damage profile to a Clan ER PPC, but at reduced ranges. This is backed up by a Diverse Optics ER medium laser and a Guided Technologies Second Generation Streak SRM-6 launcher for close combat. -history:A widespread part of every major military, the Wolverine has manufacturing plants scattered throughout the entire Inner Sphere. While certain states-notable the Free Worlds League-have larger numbers of the design, only the Capellans began facing a shortage of the Wolverine after the loss of their Nanking facilities. +history:A widespread part of every major military, the Wolverine has manufacturing plants scattered throughout the entire Inner Sphere. While certain states-notably the Free Worlds League-have larger numbers of the design, only the Capellans began facing a shortage of the Wolverine after the loss of their Nanking facilities. manufacturer:Kallon Weapon Industries primaryfactory:Thermopolis diff --git a/megameklab/data/mechfiles/mechs/3085u/Phoenix/Wolverine WVR-9W.mtf b/megameklab/data/mechfiles/mechs/3085u/Phoenix/Wolverine WVR-9W.mtf index 3886c0b99..fa78da8b9 100644 --- a/megameklab/data/mechfiles/mechs/3085u/Phoenix/Wolverine WVR-9W.mtf +++ b/megameklab/data/mechfiles/mechs/3085u/Phoenix/Wolverine WVR-9W.mtf @@ -167,7 +167,7 @@ capabilities:The autocannon, missile system and laser found on most Wolverines a deployment:This 3077 variant carries a pair of Light PPCs, an MML-5 with Artemis IV, and a single ER medium laser. To coordinate fire with friendly units, it's equipped with an Improved C3 Computer. Seven Improved Jump Jets provide a 210 meter jump range, and the Mech is protected by an experimental CASE II system and Light Ferro-Fibrous armor. -history:A widespread part of every major military, the Wolverine has manufacturing plants scattered throughout the entire Inner Sphere. While certain states-notable the Free Worlds League-have larger numbers of the design, only the Capellans began facing a shortage of the Wolverine after the loss of their Nanking facilities. +history:A widespread part of every major military, the Wolverine has manufacturing plants scattered throughout the entire Inner Sphere. While certain states-notably the Free Worlds League-have larger numbers of the design, only the Capellans began facing a shortage of the Wolverine after the loss of their Nanking facilities. manufacturer:Luthien Armor Works primaryfactory:Dieron diff --git a/megameklab/data/mechfiles/mechs/3085u/Phoenix/Wolverine WVR-9W2.mtf b/megameklab/data/mechfiles/mechs/3085u/Phoenix/Wolverine WVR-9W2.mtf index f57c2d9a7..5531a2050 100644 --- a/megameklab/data/mechfiles/mechs/3085u/Phoenix/Wolverine WVR-9W2.mtf +++ b/megameklab/data/mechfiles/mechs/3085u/Phoenix/Wolverine WVR-9W2.mtf @@ -168,7 +168,7 @@ capabilities:The autocannon, missile system and laser found on most Wolverines a deployment:Introduced in 3084 this variant has an ER medium laser and ER small laser to provide close range firepower. An Artemis IV system attached to an MML-5 and a pair of Light PPCs provide long range firepower. A C3 Slave shares targeting data, while a Guardian ECM Suite disrupts enemy electronics. Light Ferro-Fibrous armor and CASE protect the Wolverine. Seven Improved Jump Jets improve mobility. -history:A widespread part of every major military, the Wolverine has manufacturing plants scattered throughout the entire Inner Sphere. While certain states-notable the Free Worlds League-have larger numbers of the design, only the Capellans began facing a shortage of the Wolverine after the loss of their Nanking facilities. +history:A widespread part of every major military, the Wolverine has manufacturing plants scattered throughout the entire Inner Sphere. While certain states-notably the Free Worlds League-have larger numbers of the design, only the Capellans began facing a shortage of the Wolverine after the loss of their Nanking facilities. manufacturer:Luthien Armor Works primaryfactory:New Samarkand diff --git a/megameklab/data/mechfiles/mechs/3145/Clans/Shrike 2.mtf b/megameklab/data/mechfiles/mechs/3145/Clans/Shrike 2.mtf index 4117b0b23..0c6187c24 100644 --- a/megameklab/data/mechfiles/mechs/3145/Clans/Shrike 2.mtf +++ b/megameklab/data/mechfiles/mechs/3145/Clans/Shrike 2.mtf @@ -159,7 +159,7 @@ Clan Ferro-Fibrous overview:The Shrike's humble origins derive from Red Devil Industries' Onager, which was clearly inspired by the aesthetics of Olivetti's Flamberge and Eyrie. capabilities:Despite being heavier than its spiritual forefather, the Shrike outperforms the Onager in every way. It can outmaneuver many heavy and assault 'Mechs, and jump jets combined with a partial wing allow the Shrike to reach regions where most 'Mechs in its weight class cannot. The Shrike's armaments and targeting computer let it to remain a safe distance from its opponents, perhaps keeping the pilot safe without sacrificing accuracy, and reinforced legs promote Death From Above strikes on those who get too close. The Shrike is a command 'Mech with heavy armor, a command station, and a terrifying falcon shape. deployment:Introduced in 3115, the second variant of the Shrike replaces the ER Large Lasers with ER medium lasers, which allows the autocannons to be upgraded to pair of Ultra Autocannon/10s. -history:At first appearance, one might mistake the ferocious Shrike for another falcon-themed BattleMech manufactured by Olivetti Weaponry. Eagle Craft Group adopted the Onager concept and retooled it to fit the Clan Council's rejuvenation mandates and design philosophy, following in the footsteps of the Eyrie. The heavier Shrike, which debuted shortly after Olivetti's similarly fashioned Gyrfalcon, drew praise from the warrior caste when it outperformed the Onager in every category. Many Falcon fighters issued Trials of Possession for Shrikes after observing them struggle against fast, heavy 'Mechs. Because of its agility, thick armor, range, precision, and terrifying battlefield presence, the Shrike has quickly become a favorite among Galaxy and Cluster commanders. Although a few salvaged chassis have appeared on Lyran black markets, the Shrike remains a Jade Falcon asset. +history:At first appearance, one might mistake the ferocious Shrike for another falcon-themed BattleMech manufactured by Olivetti Weaponry. Eagle Craft Group adopted the Onager concept and retooled it to fit the Clan Council's rejuvenation mandates and design philosophy, following in the footsteps of the Eyrie. The heavier Shrike, which debuted shortly after Olivetti's similarly fashioned Gyrfalcon, drew praise from the warrior caste when it outperformed the Onager in every category. Many Falcon fighters issued Trials of Possession for Shrikes after observing them struggle against fast, heavy 'Mechs. Because of its agility, thick armor, range, precision, and terrifying battlefield presence, the Shrike has quickly become a favorite among Galaxy and Cluster commanders. Although a few salvaged chassis have appeared on Lyran black markets, the Shrike remains a Jade Falcon asset. manufacturer:Eagle Craft Group primaryfactory:Erewhon systemmanufacturer:CHASSIS:DSAM Endo 4 diff --git a/megameklab/data/mechfiles/mechs/3145/Clans/Shrike 3.mtf b/megameklab/data/mechfiles/mechs/3145/Clans/Shrike 3.mtf index c1ce28c26..af7f1e3f3 100644 --- a/megameklab/data/mechfiles/mechs/3145/Clans/Shrike 3.mtf +++ b/megameklab/data/mechfiles/mechs/3145/Clans/Shrike 3.mtf @@ -158,8 +158,8 @@ Clan Ferro-Fibrous overview:The Shrike's humble origins derive from Red Devil Industries' Onager, which was clearly inspired by the aesthetics of Olivetti's Flamberge and Eyrie. capabilities:Despite being heavier than its spiritual forefather, the Shrike outperforms the Onager in every way. It can outmaneuver many heavy and assault 'Mechs, and jump jets combined with a partial wing allow the Shrike to reach regions where most 'Mechs in its weight class cannot. The Shrike's armaments and targeting computer let it to remain a safe distance from its opponents, perhaps keeping the pilot safe without sacrificing accuracy, and reinforced legs promote Death From Above strikes on those who get too close. The Shrike is a command 'Mech with heavy armor, a command station, and a terrifying falcon shape. -deployment:his variant of the Shrike was introduced in 3116. The Shrike 3 is similar to the standard model, save the swapping out of the 'Mech's autocannons for pair of Extended Range Particle Projection Cannons. -history:At first appearance, one might mistake the ferocious Shrike for another falcon-themed BattleMech manufactured by Olivetti Weaponry. Eagle Craft Group adopted the Onager concept and retooled it to fit the Clan Council's rejuvenation mandates and design philosophy, following in the footsteps of the Eyrie. The heavier Shrike, which debuted shortly after Olivetti's similarly fashioned Gyrfalcon, drew praise from the warrior caste when it outperformed the Onager in every category. Many Falcon fighters issued Trials of Possession for Shrikes after observing them struggle against fast, heavy 'Mechs. Because of its agility, thick armor, range, precision, and terrifying battlefield presence, the Shrike has quickly become a favorite among Galaxy and Cluster commanders. Although a few salvaged chassis have appeared on Lyran black markets, the Shrike remains a Jade Falcon asset. +deployment:This variant of the Shrike was introduced in 3116. The Shrike 3 is similar to the standard model, save the swapping out of the 'Mech's autocannons for pair of Extended Range Particle Projection Cannons. +history:At first appearance, one might mistake the ferocious Shrike for another falcon-themed BattleMech manufactured by Olivetti Weaponry. Eagle Craft Group adopted the Onager concept and retooled it to fit the Clan Council's rejuvenation mandates and design philosophy, following in the footsteps of the Eyrie. The heavier Shrike, which debuted shortly after Olivetti's similarly fashioned Gyrfalcon, drew praise from the warrior caste when it outperformed the Onager in every category. Many Falcon fighters issued Trials of Possession for Shrikes after observing them struggle against fast, heavy 'Mechs. Because of its agility, thick armor, range, precision, and terrifying battlefield presence, the Shrike has quickly become a favorite among Galaxy and Cluster commanders. Although a few salvaged chassis have appeared on Lyran black markets, the Shrike remains a Jade Falcon asset. manufacturer:Eagle Craft Group primaryfactory:Erewhon systemmanufacturer:CHASSIS:DSAM Endo 4 diff --git a/megameklab/data/mechfiles/mechs/3145/Clans/Shrike.mtf b/megameklab/data/mechfiles/mechs/3145/Clans/Shrike.mtf index 9e0cdcada..5af9d560d 100644 --- a/megameklab/data/mechfiles/mechs/3145/Clans/Shrike.mtf +++ b/megameklab/data/mechfiles/mechs/3145/Clans/Shrike.mtf @@ -164,7 +164,7 @@ capabilities:Despite being heavier than its spiritual forefather, the Shrike out deployment:The Shrike is outfitted with a powerful Targeting Computer that allows it to bring accurate firepower to bear on the battlefield. It has a hard-hitting armament that gives the 'Mech a powerful sting in combat at most ranges. A Type X "Long Bow" LRM-10-rack allows pilots to engage enemies at long range, and two Type 9 Ultra Autocannon/5s are effective against even other assault-class 'Mechs. Lastly, two Series 2b ER Large Lasers provide a fairly powerful punch should the other weapon systems deplete their ammunition. -history:At first appearance, one might mistake the ferocious Shrike for another falcon-themed BattleMech manufactured by Olivetti Weaponry. Eagle Craft Group adopted the Onager concept and retooled it to fit the Clan Council's rejuvenation mandates and design philosophy, following in the footsteps of the Eyrie. The heavier Shrike, which debuted shortly after Olivetti's similarly fashioned Gyrfalcon, drew praise from the warrior caste when it outperformed the Onager in every category. Many Falcon fighters issued Trials of Possession for Shrikes after observing them struggle against fast, heavy 'Mechs. Because of its agility, thick armor, range, precision, and terrifying battlefield presence, the Shrike has quickly become a favorite among Galaxy and Cluster commanders. Although a few salvaged chassis have appeared on Lyran black markets, the Shrike remains a Jade Falcon asset. +history:At first appearance, one might mistake the ferocious Shrike for another falcon-themed BattleMech manufactured by Olivetti Weaponry. Eagle Craft Group adopted the Onager concept and retooled it to fit the Clan Council's rejuvenation mandates and design philosophy, following in the footsteps of the Eyrie. The heavier Shrike, which debuted shortly after Olivetti's similarly fashioned Gyrfalcon, drew praise from the warrior caste when it outperformed the Onager in every category. Many Falcon fighters issued Trials of Possession for Shrikes after observing them struggle against fast, heavy 'Mechs. Because of its agility, thick armor, range, precision, and terrifying battlefield presence, the Shrike has quickly become a favorite among Galaxy and Cluster commanders. Although a few salvaged chassis have appeared on Lyran black markets, the Shrike remains a Jade Falcon asset. manufacturer:Eagle Craft Group primaryfactory:Erewhon diff --git a/megameklab/data/mechfiles/mechs/3145/Clans/Tomahawk II (Prime).mtf b/megameklab/data/mechfiles/mechs/3145/Clans/Tomahawk II (Prime).mtf index 81354e133..53c09c27d 100644 --- a/megameklab/data/mechfiles/mechs/3145/Clans/Tomahawk II (Prime).mtf +++ b/megameklab/data/mechfiles/mechs/3145/Clans/Tomahawk II (Prime).mtf @@ -165,7 +165,7 @@ capabilities:The Tomahawk II is designed around the use of a DSAM Endo 10-Compos deployment:The 'Mech's Primary Configuration is fitted with a pair of Class 30 Hyper-Assault Gauss Rifles, one mounted in each of the arm actuators. Protected by CASE II, both weapons have a combined eight tons of ammunition split between them, giving each weapon 16 rounds of fire. Backing up the main guns are three long-reaching Extended-Range Large Lasers, with one found in each of the Tomahawk II's arms and one in the head. A pair of Medium Pulse Lasers rounds out the 'Mech's weaponry, giving it additional firepower at close-in ranges. Five additional Double Heat Sinks are fitted in the Omni Pod bays to help the 'Mech cope with the weapons' great heat buildup. -history:The Tomahawk II was based on early prototypes developed during the Clan Invasion era, which were produced in limited numbers. The Tomahawk II was originally produced at the Wolves' W-7 Facilities on Weingarten until the late 3130s when the Clan undertook its migration to then exFree Worlds League space. Production of the 'Mech would resume on Keystone at Earthwerks-FWL, Incorporated. One of the Tomahawk II's most notable uses was during Clan Wolf's invasion of Tharkad in 3143. Beta Galaxy's Galaxy Commander Alaric Ward[5] utilized a binary of Tomahawk IIs in order to demoralize Tharkard's Lyran defenders. He deployed this elite Binary of Tomahawk IIs to defeat elements of the 2nd Royals at Nagelring in July. +history:The Tomahawk II was based on early prototypes developed during the Clan Invasion era, which were produced in limited numbers. The Tomahawk II was originally produced at the Wolves' W-7 Facilities on Weingarten until the late 3130s when the Clan undertook its migration to then exFree Worlds League space. Production of the 'Mech would resume on Keystone at Earthwerks-FWL, Incorporated. One of the Tomahawk II's most notable uses was during Clan Wolf's invasion of Tharkad in 3143. Beta Galaxy's Galaxy Commander Alaric Ward utilized a binary of Tomahawk IIs in order to demoralize Tharkard's Lyran defenders. He deployed this elite Binary of Tomahawk IIs to defeat elements of the 2nd Royals at Nagelring in July. manufacturer:Earthwerks-FWL, Inc. primaryfactory:Keystone diff --git a/megameklab/data/mechfiles/mechs/3145/Clans/Tomahawk II A.mtf b/megameklab/data/mechfiles/mechs/3145/Clans/Tomahawk II A.mtf index 5f639ffd6..a2086a2bc 100644 --- a/megameklab/data/mechfiles/mechs/3145/Clans/Tomahawk II A.mtf +++ b/megameklab/data/mechfiles/mechs/3145/Clans/Tomahawk II A.mtf @@ -168,7 +168,7 @@ capabilities:The Tomahawk II is designed around the use of a DSAM Endo 10-Compos deployment:Designed around the accurate LB-X Autocannon and Pulse Laser technologies, this configuration is quite ideal when used at close range against enemies, as well as for anti-aircraft purposes. The Configuration's main weapons are found in the arm actuators, each arm sports a single LB 10-X Autocannon and a pair of AP Gauss Rifles. While the Autocannons' two tons worth of ammunition is stored in the arms under the protection of CASE II, the AP Rifles' ammunition can be found in each of the side torsos. The aforementioned pulse laser weaponry includes a pair of side torso-mounted Large and Medium Pulse Lasers, and a single ER Large Laser is allocated to the A Configuration's head. There are seven Double Heat Sinks, in addition to the twelve base-model Heat Sinks, fitted into this configuration. -history:The Tomahawk II was based on early prototypes developed during the Clan Invasion era, which were produced in limited numbers. The Tomahawk II was originally produced at the Wolves' W-7 Facilities on Weingarten until the late 3130s when the Clan undertook its migration to then exFree Worlds League space. Production of the 'Mech would resume on Keystone at Earthwerks-FWL, Incorporated. One of the Tomahawk II's most notable uses was during Clan Wolf's invasion of Tharkad in 3143. Beta Galaxy's Galaxy Commander Alaric Ward[5] utilized a binary of Tomahawk IIs in order to demoralize Tharkard's Lyran defenders. He deployed this elite Binary of Tomahawk IIs to defeat elements of the 2nd Royals at Nagelring in July. +history:The Tomahawk II was based on early prototypes developed during the Clan Invasion era, which were produced in limited numbers. The Tomahawk II was originally produced at the Wolves' W-7 Facilities on Weingarten until the late 3130s when the Clan undertook its migration to then exFree Worlds League space. Production of the 'Mech would resume on Keystone at Earthwerks-FWL, Incorporated. One of the Tomahawk II's most notable uses was during Clan Wolf's invasion of Tharkad in 3143. Beta Galaxy's Galaxy Commander Alaric Ward utilized a binary of Tomahawk IIs in order to demoralize Tharkard's Lyran defenders. He deployed this elite Binary of Tomahawk IIs to defeat elements of the 2nd Royals at Nagelring in July. manufacturer:Earthwerks-FWL, Inc. primaryfactory:Keystone diff --git a/megameklab/data/mechfiles/mechs/3145/Clans/Tomahawk II B.mtf b/megameklab/data/mechfiles/mechs/3145/Clans/Tomahawk II B.mtf index 921ceb9bc..bc18e1c39 100644 --- a/megameklab/data/mechfiles/mechs/3145/Clans/Tomahawk II B.mtf +++ b/megameklab/data/mechfiles/mechs/3145/Clans/Tomahawk II B.mtf @@ -165,7 +165,7 @@ capabilities:The Tomahawk II is designed around the use of a DSAM Endo 10-Compos deployment:Suggested for use in urban combat, the B Configuration comes with a large array of energy and missile weapon systems. This configuration's long-range firepower comes from a pair of arm-mounted Streak LRM-15 launchers and a pair of long-range, torso-mounted ER Large Lasers. For closer ranges, the 'Mech makes use of an ER Large Pulse Laser in each of the arms, and a single ER Medium Laser in the torso. To help this configuration of the Tomahawk II cope with urban settings, the 'Mech sports three Jump Jets, while ten additional Double Heat Sinks try to help with the heat management. A single head-mounted Laser Anti-Missile System is fitted in the head to fight off enemy missiles. -history:The Tomahawk II was based on early prototypes developed during the Clan Invasion era, which were produced in limited numbers. The Tomahawk II was originally produced at the Wolves' W-7 Facilities on Weingarten until the late 3130s when the Clan undertook its migration to then exFree Worlds League space. Production of the 'Mech would resume on Keystone at Earthwerks-FWL, Incorporated. One of the Tomahawk II's most notable uses was during Clan Wolf's invasion of Tharkad in 3143. Beta Galaxy's Galaxy Commander Alaric Ward[5] utilized a binary of Tomahawk IIs in order to demoralize Tharkard's Lyran defenders. He deployed this elite Binary of Tomahawk IIs to defeat elements of the 2nd Royals at Nagelring in July. +history:The Tomahawk II was based on early prototypes developed during the Clan Invasion era, which were produced in limited numbers. The Tomahawk II was originally produced at the Wolves' W-7 Facilities on Weingarten until the late 3130s when the Clan undertook its migration to then exFree Worlds League space. Production of the 'Mech would resume on Keystone at Earthwerks-FWL, Incorporated. One of the Tomahawk II's most notable uses was during Clan Wolf's invasion of Tharkad in 3143. Beta Galaxy's Galaxy Commander Alaric Ward utilized a binary of Tomahawk IIs in order to demoralize Tharkard's Lyran defenders. He deployed this elite Binary of Tomahawk IIs to defeat elements of the 2nd Royals at Nagelring in July. manufacturer:Earthwerks-FWL, Inc. primaryfactory:Keystone diff --git a/megameklab/data/mechfiles/mechs/3145/Clans/Tomahawk II C.mtf b/megameklab/data/mechfiles/mechs/3145/Clans/Tomahawk II C.mtf index d07a0c624..e3fd8029f 100644 --- a/megameklab/data/mechfiles/mechs/3145/Clans/Tomahawk II C.mtf +++ b/megameklab/data/mechfiles/mechs/3145/Clans/Tomahawk II C.mtf @@ -166,7 +166,7 @@ capabilities:The Tomahawk II is designed around the use of a DSAM Endo 10-Compos deployment:Intended for the fire support role, the C Configuration carries a number of missile batteries and Pulse Laser technologies to play its role, while also providing a means of self-defense. The C Configuration sports six LRM-15 Launchers - one in each arm and two allocated to each side torso. The 'Mech's missile ammunition is found in the arms, with five tons worth of LRM munitions protected by CASE II. Backing up the 'Mech at closer ranges are three Large Pulse Lasers, each mounted in each of the 'Mech's torsos. Six additional Double Heat Sinks are provided to help manage the tremendous heat levels generated. -history:The Tomahawk II was based on early prototypes developed during the Clan Invasion era, which were produced in limited numbers. The Tomahawk II was originally produced at the Wolves' W-7 Facilities on Weingarten until the late 3130s when the Clan undertook its migration to then exFree Worlds League space. Production of the 'Mech would resume on Keystone at Earthwerks-FWL, Incorporated. One of the Tomahawk II's most notable uses was during Clan Wolf's invasion of Tharkad in 3143. Beta Galaxy's Galaxy Commander Alaric Ward[5] utilized a binary of Tomahawk IIs in order to demoralize Tharkard's Lyran defenders. He deployed this elite Binary of Tomahawk IIs to defeat elements of the 2nd Royals at Nagelring in July. +history:The Tomahawk II was based on early prototypes developed during the Clan Invasion era, which were produced in limited numbers. The Tomahawk II was originally produced at the Wolves' W-7 Facilities on Weingarten until the late 3130s when the Clan undertook its migration to then exFree Worlds League space. Production of the 'Mech would resume on Keystone at Earthwerks-FWL, Incorporated. One of the Tomahawk II's most notable uses was during Clan Wolf's invasion of Tharkad in 3143. Beta Galaxy's Galaxy Commander Alaric Ward utilized a binary of Tomahawk IIs in order to demoralize Tharkard's Lyran defenders. He deployed this elite Binary of Tomahawk IIs to defeat elements of the 2nd Royals at Nagelring in July. manufacturer:Earthwerks-FWL, Inc. primaryfactory:Keystone diff --git a/megameklab/data/mechfiles/mechs/3145/Davion/Black Knight BLK-NT-2Y.mtf b/megameklab/data/mechfiles/mechs/3145/Davion/Black Knight BLK-NT-2Y.mtf index f627f2148..6f7fd38d1 100644 --- a/megameklab/data/mechfiles/mechs/3145/Davion/Black Knight BLK-NT-2Y.mtf +++ b/megameklab/data/mechfiles/mechs/3145/Davion/Black Knight BLK-NT-2Y.mtf @@ -154,7 +154,7 @@ IS Endo-Composite 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 of them 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 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:Another Dark Age version of the Black Knight, the -2Y is equipped with an XL engine that drives it to 54 km/h. The weight freed by the XL engine is used to add a Beagle Active Probe, Guardian ECM Suite, and C3 slave unit. It has thirteen and a half tons of armor to protect an Endo-Composite skeleton. It is also equipped with a Targeting Computer, and a Medium Shield is carried on the right arm. Offensively, it mounts a PPC, two large lasers, and three medium lasers. All equipment is of Inner Sphere quality. diff --git a/megameklab/data/mechfiles/mechs/3145/Davion/Black Knight BLK-NT-3A.mtf b/megameklab/data/mechfiles/mechs/3145/Davion/Black Knight BLK-NT-3A.mtf index ec86e4655..86ad1742d 100644 --- a/megameklab/data/mechfiles/mechs/3145/Davion/Black Knight BLK-NT-3A.mtf +++ b/megameklab/data/mechfiles/mechs/3145/Davion/Black Knight BLK-NT-3A.mtf @@ -156,7 +156,7 @@ IS Endo-Composite 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 of them 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 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:This version was also introduced during the Dark Age. It uses the Endo-Composite structure of the other models and is protected by the same thirteen and a half tons of armor, but has a larger XL engine that gives it a top speed of 64 km/h. It also carries a Medium Shield on the right arm, and its weapon array consists of a pair of ER Large Lasers, four ER medium lasers, and a pair of ER Small Lasers. It also carries a single Flamer for anti-infantry work. It lacks the electronics of other versions, and carries nineteen double heat sinks. Again, all equipment is of Inner Sphere manufacture. diff --git a/megameklab/data/mechfiles/mechs/3145/Davion/Black Knight BLK-NT-3B.mtf b/megameklab/data/mechfiles/mechs/3145/Davion/Black Knight BLK-NT-3B.mtf index 66981d0a0..ec7f7eb92 100644 --- a/megameklab/data/mechfiles/mechs/3145/Davion/Black Knight BLK-NT-3B.mtf +++ b/megameklab/data/mechfiles/mechs/3145/Davion/Black Knight BLK-NT-3B.mtf @@ -160,7 +160,7 @@ IS Endo-Composite 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 of them 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 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:This version uses the same Endo-Composite skeleton and XL engine of the 3A variant. Its weapons array has been modified however. Keeping the right arm mounted Medium Shield, this variant carries twin ER PPCs, two ER Small Lasers, twin Small Pulse Lasers, and a pair of Small Lasers. This version has also been equipped with seventeen double heat sinks. For increased speed and strength, the 3B version uses Triple Strength Myomer. diff --git a/megameklab/data/mechfiles/mechs/3145/Davion/Black Knight BLK-NT-4D.mtf b/megameklab/data/mechfiles/mechs/3145/Davion/Black Knight BLK-NT-4D.mtf index f53d57efb..0626ace9f 100644 --- a/megameklab/data/mechfiles/mechs/3145/Davion/Black Knight BLK-NT-4D.mtf +++ b/megameklab/data/mechfiles/mechs/3145/Davion/Black Knight BLK-NT-4D.mtf @@ -161,7 +161,7 @@ CLDoubleHeatSink 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 of them 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 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:This version is equipped with an ER PPC, two ER Medium Pulse Lasers, two ER small lasers, and two small pulse lasers, all made to Clan specifications. This Black Knight also carries a plasma rifle in each arm, which use three tons of ammunition. The Medium Shield and thirteen and a half tons of armor protect the Endo-Composite structure. An Angel ECM Suite provides electronic warfare support, and eighteen Clan-spec double heat sinks keep the 'Mech running cool. Its max speed is 54 km/h. diff --git a/megameklab/data/mechfiles/mechs/3145/Davion/Black Knight BLK-NT-5H.mtf b/megameklab/data/mechfiles/mechs/3145/Davion/Black Knight BLK-NT-5H.mtf index 405d975ed..1b6647e9b 100644 --- a/megameklab/data/mechfiles/mechs/3145/Davion/Black Knight BLK-NT-5H.mtf +++ b/megameklab/data/mechfiles/mechs/3145/Davion/Black Knight BLK-NT-5H.mtf @@ -161,7 +161,7 @@ CLDoubleHeatSink 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 of them 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 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:This Dark Age version of the Black Knight uses a Light Engine to reach a top speed of 54 km/h. It also has an advanced Endo-Composite skeleton protected by thirteen and a half tons of armor. Seventeen Clan-spec double heat sinks keep heat load under control. The right arm carries a Medium Shield, and it has an advanced Targeting Computer. Its weaponry is all Clan-spec. An ER PPC, two ER Large Lasers, two ER medium lasers, two ER Small Lasers and twin Small Pulse Lasers arm the Black Knight. diff --git a/megameklab/data/mechfiles/mechs/3145/Liao/Gun GN-2O.mtf b/megameklab/data/mechfiles/mechs/3145/Liao/Gun GN-2O.mtf index cdb4519d2..3767d7092 100644 --- a/megameklab/data/mechfiles/mechs/3145/Liao/Gun GN-2O.mtf +++ b/megameklab/data/mechfiles/mechs/3145/Liao/Gun GN-2O.mtf @@ -1,4 +1,4 @@ -chassis:Gun +chassis:Gùn model:GN-2O mul id:6450 diff --git a/megameklab/data/mechfiles/mechs/3145/Liao/Gun GN-2OA.mtf b/megameklab/data/mechfiles/mechs/3145/Liao/Gun GN-2OA.mtf index 759d08e04..162019713 100644 --- a/megameklab/data/mechfiles/mechs/3145/Liao/Gun GN-2OA.mtf +++ b/megameklab/data/mechfiles/mechs/3145/Liao/Gun GN-2OA.mtf @@ -1,4 +1,4 @@ -chassis:Gun +chassis:Gùn model:GN-2OA mul id:6451 diff --git a/megameklab/data/mechfiles/mechs/3145/Liao/Gun GN-2OC.mtf b/megameklab/data/mechfiles/mechs/3145/Liao/Gun GN-2OC.mtf index 8e153d2b7..75a419977 100644 --- a/megameklab/data/mechfiles/mechs/3145/Liao/Gun GN-2OC.mtf +++ b/megameklab/data/mechfiles/mechs/3145/Liao/Gun GN-2OC.mtf @@ -1,4 +1,4 @@ -chassis:Gun +chassis:Gùn model:GN-2OB mul id:6452 diff --git a/megameklab/data/mechfiles/mechs/3145/NTNU RS/Archer ARC-9KC.mtf b/megameklab/data/mechfiles/mechs/3145/NTNU RS/Archer ARC-9KC.mtf index 4d8cb482c..2d755d5d3 100644 --- a/megameklab/data/mechfiles/mechs/3145/NTNU RS/Archer ARC-9KC.mtf +++ b/megameklab/data/mechfiles/mechs/3145/NTNU RS/Archer ARC-9KC.mtf @@ -163,7 +163,7 @@ IS Endo Steel overview:One of the most iconic BattleMechs is the Archer, with its low-slung torso, enormous fists, and missile-bay covers. The Archer was first manufactured in 2474 for heavy-hitting, long-range brawling, and fire-support. -capabilities:Two enormous missile launchers with tons of ammo power the Archer. The missiles were formidable, but their short-range inaccuracy required four medium lasers, two rear-facing and one in each arm. Enlarged hand actuators allow the design to undertake severe physical attacks and transport captured supplies during raids. The cockpit of the Archer situated beneath the center midsection, giving the pilot a unique battlefield view. The torso armor belt above the cockpit protects the gyro and engine from the superior armor. Many pilots initially entered battle with their missile bays locked to hide the 'Mech's real capabilities, leading some to believe it was a close-combat design. As the Archer became famous, this pretext became meaningless. Archer pilots rarely learn new skills, but this hasn't tarnished the 'Mech's reputation. +capabilities:Two enormous missile launchers with tons of ammo power the Archer. The missiles were formidable, but their short-range inaccuracy required four medium lasers, two rear-facing and one in each arm. Enlarged hand actuators allow the design to undertake severe physical attacks and transport captured supplies during raids. The cockpit of the Archer is situated beneath the center midsection, giving the pilot a unique battlefield view. The torso armor belt above the cockpit protects the gyro and engine from the superior armor. Many pilots initially entered battle with their missile bays locked to hide the 'Mech's real capabilities, leading some to believe it was a close-combat design. As the Archer became famous, this pretext became meaningless. Archer pilots rarely learn new skills, but this hasn't tarnished the 'Mech's reputation. deployment:This Archer variant, based on the 9K, was introduced during the Dark Ages. It retained the four MML-5 launchers and two of the three light PPCs of the earlier design, but replaced the third light PPC and C3 slave with a C3 boosted slave and an ER medium laser. diff --git a/megameklab/data/mechfiles/mechs/3145/NTNU RS/Atlas AS7-K4.mtf b/megameklab/data/mechfiles/mechs/3145/NTNU RS/Atlas AS7-K4.mtf index 84c55b330..a76d75d92 100644 --- a/megameklab/data/mechfiles/mechs/3145/NTNU RS/Atlas AS7-K4.mtf +++ b/megameklab/data/mechfiles/mechs/3145/NTNU RS/Atlas AS7-K4.mtf @@ -161,7 +161,7 @@ IS Ferro-Fibrous overview:"A 'Mech as powerful as possible, as impenetrable as possible, and as ugly and foreboding as conceivable, so that fear itself will be our ally.”-Aleksandr Kerensky -capabilities:The Atlas is probably the best-known BattleMech to ever set foot on the modern battlefield. Designed with specifications from Aleksandr Kerensky himself in 2755 in the midst of the Cameron Edicts, the Atlas was originally intended to ensure SLDF superiority over the Star League member states. Carrying the largest LRM launcher, the largest autocannon, and the largest SRM launcher possible, the Atlas can deal frightening amounts of damage in short amounts of time. Often used as a command vehicle, the Atlas mounts an advanced antenna and communications array, allowing it to engage in surface-to space communications in real time. The massive 19-ton hide of armor that protects the Atlas makes it a difficult foe to take down. Indeed, most MechWarriors choose to fall back rather than face one head-one, as its lumbering gait mean it can rarely catch up to other 'Mechs that choose to flee it. A full year of development went into crafting the famous "Death's Head" of the 'Mech to achieve the perfect ratio of functionality and fear. The head is also quite roomy and allows a small satellite dish to be mounted for surface-to-space communications. During combat the pilot can easily fold up the dish and store it within a protective portion of the head. +capabilities:The Atlas is probably the best-known BattleMech to ever set foot on the modern battlefield. Designed with specifications from Aleksandr Kerensky himself in 2755 in the midst of the Cameron Edicts, the Atlas was originally intended to ensure SLDF superiority over the Star League member states. Carrying the largest LRM launcher, the largest autocannon, and the largest SRM launcher possible, the Atlas can deal frightening amounts of damage in short amounts of time. Often used as a command vehicle, the Atlas mounts an advanced antenna and communications array, allowing it to engage in surface-to-space communications in real time. The massive 19-ton hide of armor that protects the Atlas makes it a difficult foe to take down. Indeed, most MechWarriors choose to fall back rather than face one head-on, as its lumbering gait means it can rarely catch up to other 'Mechs that choose to flee it. A full year of development went into crafting the famous "Death's Head" of the 'Mech to achieve the perfect ratio of functionality and fear. The head is also quite roomy and allows a small satellite dish to be mounted for surface-to-space communications. During combat the pilot can easily fold up the dish and store it within a protective portion of the head. deployment:This Dark Age Atlas is equipped with an ER PPC in each arm, an SRM-6 in the side torsos, and a Rotary AC/5 in the left torso. A Guardian ECM Suite is carried in the center torso. The two tons of SRM ammunition and three tons of RAC/5 ammunition are carried in a CASE protected bay in the right torso. The Atlas K4 is equipped with an extralight engine to allow it to hit a top speed of 64km/h. diff --git a/megameklab/data/mechfiles/mechs/3145/NTNU RS/Blackjack BJ-2r.mtf b/megameklab/data/mechfiles/mechs/3145/NTNU RS/Blackjack BJ-2r.mtf index a7f053c21..1057eeb2d 100644 --- a/megameklab/data/mechfiles/mechs/3145/NTNU RS/Blackjack BJ-2r.mtf +++ b/megameklab/data/mechfiles/mechs/3145/NTNU RS/Blackjack BJ-2r.mtf @@ -159,7 +159,7 @@ capabilities:The Blackjack's original mission was to assist in suppressing insur deployment:Introduced in the Dark Age, this Blackjack variant replaces the weaponry of the BJ-2 with a large re-engineered laser in each arm, backed up by a single medium laser. It can jump 120 meters at a time, and uses 11 double heat sinks. -history:The Blackjack had limited use in the Star League, and manufacture was shortly discontinued. The Blackjack, relegated to service with Hegemony planetary militia or sold to League member nations, 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. +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. manufacturer:Various primaryfactory:Various diff --git a/megameklab/data/mechfiles/mechs/3145/NTNU RS/Deimos D.mtf b/megameklab/data/mechfiles/mechs/3145/NTNU RS/Deimos D.mtf index 3186f4c78..a16aaf6ba 100644 --- a/megameklab/data/mechfiles/mechs/3145/NTNU RS/Deimos D.mtf +++ b/megameklab/data/mechfiles/mechs/3145/NTNU RS/Deimos D.mtf @@ -160,7 +160,7 @@ overview:The Deimos is a Clan Assault OmniMech, which was developed by Clan Snow capabilities:The 85-tonner is powered by a Type 255-rated Extralight Fusion Engine, which it shares with the second-line Assault 'Mech, the Omen. Fourteen Double Heat Sinks are fitted to mitigate any heat issues that the 'Mech's systems may generate. Because its top speed is slower than more typical OmniMechs of the same size, engineers installed a MASC system, which allows the Deimos to go marginally faster and keep up with comparable older designs. The 'Mech is protected by 14.5 tons of Standard Armor, where it again differs from more typical contemporaries. Aside from its 43-ton equipment capacity, the 'Mech has a few permanently mounted weapons. These include two ER Medium Lasers, one assigned to each of the 'Mech's side torsos. To provide protection from inbound missile fire, an Anti-Missile System is mounted in the Deimos' head. The single ton of ammunition for the AMS is located in the center torso. -deployment:The D configuration was introduced during the Dark Age era in 3119[6]. It carries two Streak LRM-20s, two Rotary AC/2s, and two ER Medium Lasers. The single Anti-Missile System is retained. +deployment:The D configuration was introduced during the Dark Age era in 3119. It carries two Streak LRM-20s, two Rotary AC/2s, and two ER Medium Lasers. The single Anti-Missile System is retained. history:The 'Mech was first introduced during the middle of the 3060s, allegedly on the Kerensky Cluster world of Lum. However, Inner Sphere intelligence agencies stopped hearing rumors about the 'Mech during the Jihad and it faded from memory. In 3085, the Snow Ravens revealed the existence of the Deimos to the Inner Sphere. It was produced on the Clan's Inner Sphere world, Dante. When it first appeared in the Inner Sphere, the Deimos was considered the pride of the Clan and at least one was assigned to every cluster within the Snow Raven touman. diff --git a/megameklab/data/mechfiles/mechs/3145/NTNU RS/Loki (Hellbringer) G.mtf b/megameklab/data/mechfiles/mechs/3145/NTNU RS/Loki (Hellbringer) G.mtf index ec85d8698..294a8fff7 100644 --- a/megameklab/data/mechfiles/mechs/3145/NTNU RS/Loki (Hellbringer) G.mtf +++ b/megameklab/data/mechfiles/mechs/3145/NTNU RS/Loki (Hellbringer) G.mtf @@ -159,7 +159,7 @@ overview:The Hellbringer is a very widespread design developed by Clan Hell's Ho capabilities:This version carries an Inner Sphere built Improved Heavy Gauss Rifle with three tons of ammunition. This massive weapon is supported by an Improved Heavy Large Laser and three ER Small Lasers. -history:The Inner Sphere first encountered the Hellbringer facing Clan Jade Falcon, which favors the design for its immense offensive potential. Earning the codename Loki by Galen Cox, an AFFC officer who declared each of the Hellbringer's various versions as an "utterly mad configuration," the 'Mech does at first glance appear to be highly unusual, mounting a spread of weapons, anti-personnel equipment and electronics. The Hellbringer utilizes a standard internal structure, and has decent mobility, with a top speed of 86.4 km/h. Though it has vast firepower at its disposal, the design is not particularly durable, mounting a mere eight tons of Standard armor, and the Hellbringer is not particularly suitable for defensive situations or extended engagements. In the aftermath of the Battle of Tokasha and the loss of Tokasha Mechworks, the Hell's Horses began developing several OmniMechs. Only the Hellbringer met with success. Development time for the Hellbringer was reduced through the use of modules used in the Summoner. Despite the poor armor, the Hellbringer devotes almost 43% of its mass to pods, allowing for great offensive potential. The design spread quickly after its introduction for two reasons: the Horses promptly lost the primary production facility, and used their remaining production to curry favor with other Clans through trade and gifts. After The Wars of Reaving in Clan Space, the Hellbringer would fall out of favor with the surviving Home Clans due in part to its association with the Inner Sphere based Clans. The design would be replaced by the Ebon Jaguar in military service of those in Clan Space, with the exception of Clan Coyote which still fields the 'Mech.[9] Even after the introduction of the updated and upgraded Loki II successor design in 3121, Clan Jade Falcon would continue to produce the cheap and easy to manufacture original version on Sudeten during the Dark Age era, with disgraced, solahma or even just overly aggressive warriors still finding its offense over defense focus desirable. +history:The Inner Sphere first encountered the Hellbringer facing Clan Jade Falcon, which favors the design for its immense offensive potential. Earning the codename Loki by Galen Cox, an AFFC officer who declared each of the Hellbringer's various versions as an "utterly mad configuration," the 'Mech does at first glance appear to be highly unusual, mounting a spread of weapons, anti-personnel equipment and electronics. The Hellbringer utilizes a standard internal structure, and has decent mobility, with a top speed of 86.4 km/h. Though it has vast firepower at its disposal, the design is not particularly durable, mounting a mere eight tons of Standard armor, and the Hellbringer is not particularly suitable for defensive situations or extended engagements. In the aftermath of the Battle of Tokasha and the loss of Tokasha Mechworks, the Hell's Horses began developing several OmniMechs. Only the Hellbringer met with success. Development time for the Hellbringer was reduced through the use of modules used in the Summoner. Despite the poor armor, the Hellbringer devotes almost 43% of its mass to pods, allowing for great offensive potential. The design spread quickly after its introduction for two reasons: the Horses promptly lost the primary production facility, and used their remaining production to curry favor with other Clans through trade and gifts. After The Wars of Reaving in Clan Space, the Hellbringer would fall out of favor with the surviving Home Clans due in part to its association with the Inner Sphere based Clans. The design would be replaced by the Ebon Jaguar in military service of those in Clan Space, with the exception of Clan Coyote which still fields the 'Mech. Even after the introduction of the updated and upgraded Loki II successor design in 3121, Clan Jade Falcon would continue to produce the cheap and easy to manufacture original version on Sudeten during the Dark Age era, with disgraced, solahma or even just overly aggressive warriors still finding its offense over defense focus desirable. manufacturer:Various, Olivetti Weaponry primaryfactory:Various, Sudeten systemmanufacturer:CHASSIS:T-E H65 Standard diff --git a/megameklab/data/mechfiles/mechs/3145/NTNU RS/Mad Cat Mk II 4.mtf b/megameklab/data/mechfiles/mechs/3145/NTNU RS/Mad Cat Mk II 4.mtf index a7a50face..850a6f351 100644 --- a/megameklab/data/mechfiles/mechs/3145/NTNU RS/Mad Cat Mk II 4.mtf +++ b/megameklab/data/mechfiles/mechs/3145/NTNU RS/Mad Cat Mk II 4.mtf @@ -158,7 +158,7 @@ overview:Designed to be sold to fellow Clans, this rebuild of the Timber Wolf ca capabilities:This variant of the Mad Cat carries two ER Large Lasers in each arm and a pair of LRM-15 launchers. A Light Active Probe identifies hidden units. It also boasts an expanded jump range of 120 meters. -deployment:Despite this, Mk II's most notable potential buyers, Clan Wolf and Clan Jade Falcon, did not purchase even a single unit, though they won some numbers in Trials. Significant numbers of Mad Cat Mk II were sold to Clan Nova Cat, and the Mech served also in Clan Ice Hellion, Clan Jade Falcon, Clan Wolf-in-Exile in addition to Diamond Shark itself. On a limited basis, Clan Diamond Shark sold unmodified Mad Cat Mk IIs to Inner Sphere factions, most notably the Draconis Combine and Federated Commonwealth, and also the Lyran Alliance bought an unknown amount of Mad Cat Mark IIs. +deployment:Despite this, Mk II's most notable potential buyers, Clan Wolf and Clan Jade Falcon, did not purchase even a single unit, though they won some numbers in Trials. Significant numbers of Mad Cat Mk II were sold to Clan Nova Cat, and the Mech served also in Clan Ice Hellion, Clan Jade Falcon, Clan Wolf-in-Exile in addition to Diamond Shark itself. On a limited basis, Clan Diamond Shark sold unmodified Mad Cat Mk IIs to Inner Sphere factions, most notably the Draconis Combine and Federated Commonwealth, and also the Lyran Alliance bought an unknown amount of Mad Cat Mark IIs. history:The Mad Cat Mk II was in development for fifteen months by the time production began in 3061. The sole rationale for the Mad Cat Mk II was to increase profits for Clan Diamond Shark after war with the Inner Sphere in the 3050s. diff --git a/megameklab/data/mechfiles/mechs/3145/NTNU RS/Mad Cat Mk II 5.mtf b/megameklab/data/mechfiles/mechs/3145/NTNU RS/Mad Cat Mk II 5.mtf index 6a2126e21..2ec5ae94f 100644 --- a/megameklab/data/mechfiles/mechs/3145/NTNU RS/Mad Cat Mk II 5.mtf +++ b/megameklab/data/mechfiles/mechs/3145/NTNU RS/Mad Cat Mk II 5.mtf @@ -155,7 +155,7 @@ overview:Designed to be sold to fellow Clans, this rebuild of the Timber Wolf ca capabilities:This variant carries a Gauss Rifle in the right arm, supported by an Improved Heavy Large Laser and Improved Heavy Medium Laser in the left arm. Six Improved Jump Jets allow it to cover 180 meters at a time. -deployment:Despite this, Mk II's most notable potential buyers, Clan Wolf and Clan Jade Falcon, did not purchase even a single unit, though they won some numbers in Trials. Significant numbers of Mad Cat Mk II were sold to Clan Nova Cat, and the Mech served also in Clan Ice Hellion, Clan Jade Falcon, Clan Wolf-in-Exile in addition to Diamond Shark itself. On a limited basis, Clan Diamond Shark sold unmodified Mad Cat Mk IIs to Inner Sphere factions, most notably the Draconis Combine and Federated Commonwealth, and also the Lyran Alliance bought an unknown amount of Mad Cat Mark IIs. +deployment:Despite this, Mk II's most notable potential buyers, Clan Wolf and Clan Jade Falcon, did not purchase even a single unit, though they won some numbers in Trials. Significant numbers of Mad Cat Mk II were sold to Clan Nova Cat, and the Mech served also in Clan Ice Hellion, Clan Jade Falcon, Clan Wolf-in-Exile in addition to Diamond Shark itself. On a limited basis, Clan Diamond Shark sold unmodified Mad Cat Mk IIs to Inner Sphere factions, most notably the Draconis Combine and Federated Commonwealth, and also the Lyran Alliance bought an unknown amount of Mad Cat Mark IIs. history:The Mad Cat Mk II was in development for fifteen months by the time production began in 3061. The sole rationale for the Mad Cat Mk II was to increase profits for Clan Diamond Shark after war with the Inner Sphere in the 3050s. diff --git a/megameklab/data/mechfiles/mechs/3145/NTNU RS/Mad Cat Mk II 6.mtf b/megameklab/data/mechfiles/mechs/3145/NTNU RS/Mad Cat Mk II 6.mtf index 23acb662f..2baae3a9d 100644 --- a/megameklab/data/mechfiles/mechs/3145/NTNU RS/Mad Cat Mk II 6.mtf +++ b/megameklab/data/mechfiles/mechs/3145/NTNU RS/Mad Cat Mk II 6.mtf @@ -158,7 +158,7 @@ overview:Designed to be sold to fellow Clans, this rebuild of the Timber Wolf ca capabilities:This version carries an ER PPC in each arm, backed up by a pair of ER Medium Lasers in each side torso. Each arm, leg, and torso location is equipped with a Harjel III repair system. -deployment:Despite this, Mk II's most notable potential buyers, Clan Wolf and Clan Jade Falcon, did not purchase even a single unit, though they won some numbers in Trials. Significant numbers of Mad Cat Mk II were sold to Clan Nova Cat, and the Mech served also in Clan Ice Hellion, Clan Jade Falcon, Clan Wolf-in-Exile in addition to Diamond Shark itself. On a limited basis, Clan Diamond Shark sold unmodified Mad Cat Mk IIs to Inner Sphere factions, most notably the Draconis Combine and Federated Commonwealth, and also the Lyran Alliance bought an unknown amount of Mad Cat Mark IIs. +deployment:Despite this, Mk II's most notable potential buyers, Clan Wolf and Clan Jade Falcon, did not purchase even a single unit, though they won some numbers in Trials. Significant numbers of Mad Cat Mk II were sold to Clan Nova Cat, and the Mech served also in Clan Ice Hellion, Clan Jade Falcon, Clan Wolf-in-Exile in addition to Diamond Shark itself. On a limited basis, Clan Diamond Shark sold unmodified Mad Cat Mk IIs to Inner Sphere factions, most notably the Draconis Combine and Federated Commonwealth, and also the Lyran Alliance bought an unknown amount of Mad Cat Mark IIs. history:The Mad Cat Mk II was in development for fifteen months by the time production began in 3061. The sole rationale for the Mad Cat Mk II was to increase profits for Clan Diamond Shark after war with the Inner Sphere in the 3050s. diff --git a/megameklab/data/mechfiles/mechs/3145/NTNU RS/Marauder II MAD-4L.mtf b/megameklab/data/mechfiles/mechs/3145/NTNU RS/Marauder II MAD-4L.mtf index 553dd03c3..0c0a6a68a 100644 --- a/megameklab/data/mechfiles/mechs/3145/NTNU RS/Marauder II MAD-4L.mtf +++ b/megameklab/data/mechfiles/mechs/3145/NTNU RS/Marauder II MAD-4L.mtf @@ -161,7 +161,7 @@ capabilities:With the Marauder already a powerful and popular 'Mech, the Dragoon deployment:This Dark Age-era variant was created by the Capellan Confederation. It uses a light fusion engine to reduce vulnerability to engine destruction, and carries a Gauss Rifle in each arm. These are supported by a single torso-mounted ER PPC. A Guardian ECM Suite powers the Stealth Armor that encases this design. It retains the ability to jump 90 meters at a time. -history:In 3010 officers of the famous Wolf's Dragoons mercenary unit contracted with Blackwell Industries of New Valencia on the project of modifying the highly successful 75-ton Marauder into a 100-ton assault 'Mech. Working from existing plans the design phase proved to be very short, the process of reinforcing the Marauder chassis turned out to be easier than expected, enhanced by the removal of the finicky and temperamental General Motors Whirlwind Autocannon for a much simpler Large Laser. First appearing with the famous Zeta Battalion before spreading to Alpha Regiment, the Dragoons' enemies soon learned to fear the appearance of Marauder IIs as foreshadowing a major advance, as for the remainder of the Third Succession War it remained the exclusive property of the mysterious Dragoons. This changed after the Fourth Succession War when Colonel Jaime Wolf authorized Blackwell to increase production and allow outside buyers access, on the provision that each sale had to be approved by the Dragoons. Now spreading in limited numbers, the largest buyer outside the Dragoons would be the Miller's Marauders mercenary unit, famed for its almost exclusive use of the Marauder chassis and the secret loan of its DropShips to Zeta Battalion for their climactic rescue of the rest of the Dragoons on Crossing. When new unit commander Major Susan Barber expressed interest in the Marauder II, Colonel Wolf gave Blackwell the go-ahead to supply her with all she needed, by the Clan Invasion the now renamed Barber's Marauder II would boast almost a regiment's worth of the fearsome assault 'Mech. Though Barber's Marauder II would help drive the considerable interest and demand for the powerful assault 'Mech, they would also damage its seeming aura of invincibility following their ignoble destruction by Clan Jade Falcon on Koniz in June 3064. Seeking to rekindle interest in their flagship 'Mech following its disastrous showing on Koniz, GM/Blackwell noted the Vicore Industries triggered refresh of "classic" designs to develop a more powerful and visually refreshed model. The resulting MAD-4S variant was the first widely available Marauder II, Wolf's Dragoons' easing of sale restrictions partly motivated by profit but also as a means to punish the Lyran Alliance for the theft of the Blackwell developed light fusion engine, as of 3067 selling the 'Mech to all interested parties save those the Dragoons were fighting against in the Chaos March; the Word of Blake and the members of Trinity Alliance. The demand for the Marauder II would only increase in the Jihad following the Blakist destruction of GM and Blackwell's production facilities for the 'Mech as part of their vendetta against the Wolf's Dragoons, with many salvaged examples in use among the nations of the Inner Sphere in a large number of variations following the Blakists' fall, the most notable being the MAD-6D developed by the Federated Suns and shared with the Republic of the Sphere. +history:In 3010 officers of the famous Wolf's Dragoons mercenary unit contracted with Blackwell Industries of New Valencia on the project of modifying the highly successful 75-ton Marauder into a 100-ton assault 'Mech. Working from existing plans the design phase proved to be very short, the process of reinforcing the Marauder chassis turned out to be easier than expected, enhanced by the removal of the finicky and temperamental General Motors Whirlwind Autocannon for a much simpler Large Laser. First appearing with the famous Zeta Battalion before spreading to Alpha Regiment, the Dragoons' enemies soon learned to fear the appearance of Marauder IIs as foreshadowing a major advance, as for the remainder of the Third Succession War it remained the exclusive property of the mysterious Dragoons. This changed after the Fourth Succession War when Colonel Jaime Wolf authorized Blackwell to increase production and allow outside buyers access, on the provision that each sale had to be approved by the Dragoons. Now spreading in limited numbers, the largest buyer outside the Dragoons would be the Miller's Marauders mercenary unit, famed for its almost exclusive use of the Marauder chassis and the secret loan of its DropShips to Zeta Battalion for their climactic rescue of the rest of the Dragoons on Crossing. When new unit commander Major Susan Barber expressed interest in the Marauder II, Colonel Wolf gave Blackwell the go-ahead to supply her with all she needed, by the Clan Invasion the now renamed Barber's Marauders would boast almost a regiment's worth of the fearsome assault 'Mech. Though Barber's Marauder II would help drive the considerable interest and demand for the powerful assault 'Mech, they would also damage its seeming aura of invincibility following their ignoble destruction by Clan Jade Falcon on Koniz in June 3064. Seeking to rekindle interest in their flagship 'Mech following its disastrous showing on Koniz, GM/Blackwell noted the Vicore Industries triggered refresh of "classic" designs to develop a more powerful and visually refreshed model. The resulting MAD-4S variant was the first widely available Marauder II, Wolf's Dragoons' easing of sale restrictions partly motivated by profit but also as a means to punish the Lyran Alliance for the theft of the Blackwell developed light fusion engine, as of 3067 selling the 'Mech to all interested parties save those the Dragoons were fighting against in the Chaos March; the Word of Blake and the members of Trinity Alliance. The demand for the Marauder II would only increase in the Jihad following the Blakist destruction of GM and Blackwell's production facilities for the 'Mech as part of their vendetta against the Wolf's Dragoons, with many salvaged examples in use among the nations of the Inner Sphere in a large number of variations following the Blakists' fall, the most notable being the MAD-6D developed by the Federated Suns and shared with the Republic of the Sphere. manufacturer:McCarron's Trading Company (Refit) primaryfactory:Menke diff --git a/megameklab/data/mechfiles/mechs/3145/NTNU RS/Panther PNT-12KC.mtf b/megameklab/data/mechfiles/mechs/3145/NTNU RS/Panther PNT-12KC.mtf index 38492438f..ab6fc28d5 100644 --- a/megameklab/data/mechfiles/mechs/3145/NTNU RS/Panther PNT-12KC.mtf +++ b/megameklab/data/mechfiles/mechs/3145/NTNU RS/Panther PNT-12KC.mtf @@ -159,7 +159,7 @@ capabilities:Luckily the Panther had also proved itself to be quite hardy, sport deployment:This Panther was introduced in the Dark Age. It uses eleven Clan-spec double heat sinks to dissipate the heat from an ER PPC and Medium Laser. The -12KC carries a single Boosted C3 Slave into combat and is protected by Ballistic-Reinforced Armor. -history:The original PNT-8Z model underwent a revision after the disastrous Battle of St. John in 2759, when it was revealed that its main weapon, a Tronel Large Laser, was inefficient in both range and firepower for the immense waste heat generated. The Draconis Combine inherited Alshain Weapons' Panther factory on New Oslo when the Star League dissolved and quickly put the production line to work building new Panthers for the DCMS. Their first large-scale use by Kurita warriors came during the First Succession War in the battle for Quentin, when the 2nd Legion of Vega used their Panthers to severely maul the slower, heavier 'Mechs of the 42nd Avalon Hussars while avoiding return fire. Throughout the Succession Wars, the Combine was the only significant user of the Panther, often pairing it with the Jenner in a deadly combination of speed and firepower; though the other Successor States employed Panthers in smaller numbers, these were either the result of battlefield salvage or older League-era 8Z models. The Panther also proved itself a deadly urban combatant, using its mobility to easily navigate the more restricted space of a city environment and take out heavier opponents from rooftop sniping perches with its main weapon. Lyran MechWarriors eventually took to nicknaming the 'Mech the "Alley Cat" for its propensity to conduct dark alley-way "muggings. Demand for the Panther continued to increase, forcing Alshain to build a secondary factory on Jarett to keep up. In an ironic twist both factories fell within the borders of the Free Rasalhague Republic following its creation in 3034, transferring ownership to the new state, and soon the Panther became a mainstay of the KungsArmé. The situation did not last long however following the invasion of the Clans, and both planets were swiftly conquered by Clan Ghost Bear. While Alshain Weapons crash-built a new line on Tok Do in 3053, they could not maintain their pre-invasion production levels and focused on spare parts and refit kits instead. Eventually Wakazashi Enterprises bought the production license for the Panther and began rolling out new variants from its New Samarkand factory. These have gone on to serve in every DCMS unit since, including the bloody years of the Jihad. +history:The original PNT-8Z model underwent a revision after the disastrous Battle of St. John in 2759, when it was revealed that its main weapon, a Tronel Large Laser, was inefficient in both range and firepower for the immense waste heat generated. The Draconis Combine inherited Alshain Weapons' Panther factory on New Oslo when the Star League dissolved and quickly put the production line to work building new Panthers for the DCMS. Their first large-scale use by Kurita warriors came during the First Succession War in the battle for Quentin, when the 2nd Legion of Vega used their Panthers to severely maul the slower, heavier 'Mechs of the 42nd Avalon Hussars while avoiding return fire. Throughout the Succession Wars, the Combine was the only significant user of the Panther, often pairing it with the Jenner in a deadly combination of speed and firepower; though the other Successor States employed Panthers in smaller numbers, these were either the result of battlefield salvage or older League-era 8Z models. The Panther also proved itself a deadly urban combatant, using its mobility to easily navigate the more restricted space of a city environment and take out heavier opponents from rooftop sniping perches with its main weapon. Lyran MechWarriors eventually took to nicknaming the 'Mech the "Alley Cat" for its propensity to conduct dark alley-way "muggings. Demand for the Panther continued to increase, forcing Alshain to build a secondary factory on Jarett to keep up. In an ironic twist both factories fell within the borders of the Free Rasalhague Republic following its creation in 3034, transferring ownership to the new state, and soon the Panther became a mainstay of the KungsArmé. The situation did not last long however following the invasion of the Clans, and both planets were swiftly conquered by Clan Ghost Bear. While Alshain Weapons crash-built a new line on Tok Do in 3053, they could not maintain their pre-invasion production levels and focused on spare parts and refit kits instead. Eventually Wakazashi Enterprises bought the production license for the Panther and began rolling out new variants from its New Samarkand factory. These have gone on to serve in every DCMS unit since, including the bloody years of the Jihad. manufacturer:Field Refit primaryfactory:Field Refit diff --git a/megameklab/data/mechfiles/mechs/3145/NTNU RS/Spider SDR-10K.mtf b/megameklab/data/mechfiles/mechs/3145/NTNU RS/Spider SDR-10K.mtf index 2ab04f937..fc2d7cf0e 100644 --- a/megameklab/data/mechfiles/mechs/3145/NTNU RS/Spider SDR-10K.mtf +++ b/megameklab/data/mechfiles/mechs/3145/NTNU RS/Spider SDR-10K.mtf @@ -157,7 +157,7 @@ overview:The Spider was the first BattleMech produced by Newhart Industries, des capabilities:In terms of maneuverability the Spider has a ground speed comparable to a Locust and can out-jump either the vaunted Wasp or Stinger light 'Mechs. Built with top-of-the-line reliable parts, sophisticated reconnaissance equipment and an energy weapon payload which allowed for extended operations without resupply, the Spider was a great success. While not produced in large numbers it could be rapidly manufactured and so served up through to the end of the Star League. -deployment:his variant removes the standard weaponry and replaces it with a single Large Re-engineered Laser. It's protected by Ballistic-Reinforced Armor. +deployment:This variant removes the standard weaponry and replaces it with a single Large Re-engineered Laser. It's protected by Ballistic-Reinforced Armor. history:Beyond exceeding all of the SLDF's minimum requirements Newhart had actually designed the Spider before receiving the Star League's request for proposals and were ready to begin production immediately, factors which helped the company win the contract very quickly. Newhart's Spider factory on New Earth was destroyed in 2776 as part of the Amaris Civil War and very few Spiders ended up in the hands of the Successor States when the Star League dissolved. As their numbers began to dwindle during the Succession Wars, entire offensive operations were conducted simply to secure spare parts for these 'Mechs. So rare was the Spider that Wolf's Dragoons were notable for having an entire lance of Spiders (albeit split among the various regiments). This trend towards extinction was finally reversed when the Free Worlds League was able to secure the schematics for the Spider. In a deal with Nimakachi Fusion Products Limited, the company was given exclusive control of the 'Mech's technical specifications in exchange for building them for the Free Worlds League. Nimakachi began building new Spiders from their factory on Tematagi and later expanded their facilities on Lapida II to produce them as well, resulting in the Free Worlds League and Draconis Combine having the largest number of Spiders in active service. The recovery of lost Star League technology inspired Nimakachi to update the Spider with new upgrades, resulting in the improved SDR-7M and the derivative Venom. While the Free Worlds League did not express much interest in these 'Mechs, Nimakachi found ready buyers among the other Great Houses. In particular the Draconis Combine had lost a large number of light 'Mechs during the Clan Invasion and bought up local- and foreign-made Spiders to replenish their ranks. The Word of Blake also expressed an interest in these Spiders and bought a number to outfit their military. These Spiders were used as part of the Blakist conquest of Terra and were later gifted to the Protectorate Militia, where they fought in the Jihad. Starting in 3067, the Spider was restyled by Nimakachi which allowed the addition of an ejection system to the cockpit of the new SDR-7K, 7K2, and 7KC. diff --git a/megameklab/data/mechfiles/mechs/3145/NTNU RS/Trebuchet TBT-9R.mtf b/megameklab/data/mechfiles/mechs/3145/NTNU RS/Trebuchet TBT-9R.mtf index b305af94f..a2520a28d 100644 --- a/megameklab/data/mechfiles/mechs/3145/NTNU RS/Trebuchet TBT-9R.mtf +++ b/megameklab/data/mechfiles/mechs/3145/NTNU RS/Trebuchet TBT-9R.mtf @@ -165,7 +165,7 @@ deployment:This Trebuchet was introduced in the Dark Age era. It uses an XXL Fus history:The Trebuchet first walked off assembly lines in 2780 for the SLDF in the final years of the Star League, between the liberation of Terra from Stefan Amaris and Aleksandr Kerensky's departure. With the onset of the Succession Wars the Trebuchet would become an almost exclusive staple of the Free Worlds League since its manufacturing site on Stewart fell within their territory. However the original TBT-3C models proved to be too difficult to repair and produce with the disappearance of advanced technology, and in 2799 Corean Enterprises went back to the drawing board to create the TBT-5N using older, mass-producible technology. The Free Worlds League Military often partnered the Trebuchet with the Archer, while lances consisting of an Archer, two Trebuchets and a Centurion became a common configuration used for siege operations and by the Regulan Hussars. However the design also found its way into the hands of the other Great Houses and served with distinction during the Succession Wars in nearly every major operation, with a number of variants created to fulfill various needs. The technological renaissance which swept through the Inner Sphere during the 3030s allowed first Kali Yama and then the Irian corporations to begin producing the Trebuchet as well, culminating in upgraded designs debuting several years prior to the Clan Invasion. As late as 3071 advanced Trebuchet variants would continue to be produced and found themselves used by new actors on the galactic stage, most notoriously the Word of Blake. manufacturer:Tvastar Enterprises -primaryfactory:Regulas +primaryfactory:Regulus systemmanufacturer:CHASSIS:Corean-II Deluxe Endo Steel systemmanufacturer:ENGINE:Magna 350 XXL systemmanufacturer:ARMOR:Starshield with CASE diff --git a/megameklab/data/mechfiles/mechs/3145/Steiner/Firestarter FS9-M2.mtf b/megameklab/data/mechfiles/mechs/3145/Steiner/Firestarter FS9-M2.mtf index 77d8ee26e..85896af99 100644 --- a/megameklab/data/mechfiles/mechs/3145/Steiner/Firestarter FS9-M2.mtf +++ b/megameklab/data/mechfiles/mechs/3145/Steiner/Firestarter FS9-M2.mtf @@ -170,7 +170,7 @@ capabilities:Despite being shielded by five and a half tons of armor and capable deployment:Manufactured on Coventry for the mercenary market in 3101, possibly a descendant of the -B and almost the polar opposite of the -M variant, the -M2 variant of the Firestarter is an upgrade that is built on a Foundation Ultralight endo steel chassis and is armored with seven tons of Durallex Nova standard armor. 11 double heat sinks attempt to keep the -M2 cool, while a single Defiance Model XII ER medium laser mounted in the head and three Hotshot flamers in each arm work to tax those same heat sinks. The life support system was also substantially redesigned to be more rugged in support of the -M2's primary mission. -history:Firestarters, both ancient and contemporary, can still be found in abundance among planetary militias and House troops. Even though Blakist forces have taken over CMW's principal plant on Coventry, spare parts are still accessible from other Firestarter producers (including LAW, Ceres Metals, Defiance, and Independence Weaponry). Loki field offices near the Circinus Federation frontier are concerned about reports of a new variety using endo steel technology on Federation- occupied worlds. With its particular load-out, this new variation appears to be designed to spread chaos and destruction. Firestarters have also been seen in Level II formations with Blakist soldiers in their Protectorate, most frequently at "police demonstrations" and guarding suspected prison sites. These versions are thought to be Coventry goods. +history:Firestarters, both ancient and contemporary, can still be found in abundance among planetary militias and House troops. Even though Blakist forces have taken over CMW's principal plant on Coventry, spare parts are still accessible from other Firestarter producers (including LAW, Ceres Metals, Defiance, and Independence Weaponry). Loki field offices near the Circinus Federation frontier are concerned about reports of a new variety using endo steel technology on Federation-occupied worlds. With its particular load-out, this new variation appears to be designed to spread chaos and destruction. Firestarters have also been seen in Level II formations with Blakist soldiers in their Protectorate, most frequently at "police demonstrations" and guarding suspected prison sites. These versions are thought to be Coventry goods. manufacturer:Coventry Metal Works primaryfactory:Coventry diff --git a/megameklab/data/mechfiles/mechs/3145/Steiner/Firestarter FS9-M3.mtf b/megameklab/data/mechfiles/mechs/3145/Steiner/Firestarter FS9-M3.mtf index fcda67f80..00a62cdb9 100644 --- a/megameklab/data/mechfiles/mechs/3145/Steiner/Firestarter FS9-M3.mtf +++ b/megameklab/data/mechfiles/mechs/3145/Steiner/Firestarter FS9-M3.mtf @@ -164,7 +164,7 @@ capabilities:Despite being shielded by five and a half tons of armor and capable deployment:The -M3 is a modification of the -M2 Firestarter introduced in 3104 that has been optimized for artillery spotting. The 'Mech has removed the three flamers mounted in the left arm, replacing them with a single ER small laser, added a TAG laser designator to the right torso, allowing it to spot for artillery, and MASC, which allows it to move at up to 129.6 km/h. The -M3 also dropped a single double heat sink but added another half ton of armor, giving it a total of seven and a half tons of standard armor. -history:Firestarters, both ancient and contemporary, can still be found in abundance among planetary militias and House troops. Even though Blakist forces have taken over CMW's principal plant on Coventry, spare parts are still accessible from other Firestarter producers (including LAW, Ceres Metals, Defiance, and Independence Weaponry). Loki field offices near the Circinus Federation frontier are concerned about reports of a new variety using endo steel technology on Federation- occupied worlds. With its particular load-out, this new variation appears to be designed to spread chaos and destruction. Firestarters have also been seen in Level II formations with Blakist soldiers in their Protectorate, most frequently at "police demonstrations" and guarding suspected prison sites. These versions are thought to be Coventry goods. +history:Firestarters, both ancient and contemporary, can still be found in abundance among planetary militias and House troops. Even though Blakist forces have taken over CMW's principal plant on Coventry, spare parts are still accessible from other Firestarter producers (including LAW, Ceres Metals, Defiance, and Independence Weaponry). Loki field offices near the Circinus Federation frontier are concerned about reports of a new variety using endo steel technology on Federation-occupied worlds. With its particular load-out, this new variation appears to be designed to spread chaos and destruction. Firestarters have also been seen in Level II formations with Blakist soldiers in their Protectorate, most frequently at "police demonstrations" and guarding suspected prison sites. These versions are thought to be Coventry goods. manufacturer:Coventry Metal Works primaryfactory:Coventry diff --git a/megameklab/data/mechfiles/mechs/3145/Steiner/Firestarter FS9-M4.mtf b/megameklab/data/mechfiles/mechs/3145/Steiner/Firestarter FS9-M4.mtf index ed1d91179..6a1dcd25a 100644 --- a/megameklab/data/mechfiles/mechs/3145/Steiner/Firestarter FS9-M4.mtf +++ b/megameklab/data/mechfiles/mechs/3145/Steiner/Firestarter FS9-M4.mtf @@ -164,7 +164,7 @@ capabilities:Despite being shielded by five and a half tons of armor and capable deployment:Another reworking of the -M2 variant debuting in 3109, the M4 strips out a double heat sink, the ER medium laser and the three flamers mounted in the left arm. The -M4 upgrades the engine to 210-rated XL engine and mounts a single RAC/2 in the left arm, supplied with one ton of ammunition stored in the left torso. The -M4 also adds another half ton of standard armor. -history:Firestarters, both ancient and contemporary, can still be found in abundance among planetary militias and House troops. Even though Blakist forces have taken over CMW's principal plant on Coventry, spare parts are still accessible from other Firestarter producers (including LAW, Ceres Metals, Defiance, and Independence Weaponry). Loki field offices near the Circinus Federation frontier are concerned about reports of a new variety using endo steel technology on Federation- occupied worlds. With its particular load-out, this new variation appears to be designed to spread chaos and destruction. Firestarters have also been seen in Level II formations with Blakist soldiers in their Protectorate, most frequently at "police demonstrations" and guarding suspected prison sites. These versions are thought to be Coventry goods. +history:Firestarters, both ancient and contemporary, can still be found in abundance among planetary militias and House troops. Even though Blakist forces have taken over CMW's principal plant on Coventry, spare parts are still accessible from other Firestarter producers (including LAW, Ceres Metals, Defiance, and Independence Weaponry). Loki field offices near the Circinus Federation frontier are concerned about reports of a new variety using endo steel technology on Federation-occupied worlds. With its particular load-out, this new variation appears to be designed to spread chaos and destruction. Firestarters have also been seen in Level II formations with Blakist soldiers in their Protectorate, most frequently at "police demonstrations" and guarding suspected prison sites. These versions are thought to be Coventry goods. manufacturer:Coventry Metal Works primaryfactory:Coventry diff --git a/megameklab/data/mechfiles/mechs/3145/Steiner/Gotterdammerung GTD-20S.mtf b/megameklab/data/mechfiles/mechs/3145/Steiner/Gotterdammerung GTD-20S.mtf index fc4329ac8..9112962c9 100644 --- a/megameklab/data/mechfiles/mechs/3145/Steiner/Gotterdammerung GTD-20S.mtf +++ b/megameklab/data/mechfiles/mechs/3145/Steiner/Gotterdammerung GTD-20S.mtf @@ -1,4 +1,4 @@ -chassis:Gotterdammerung +chassis:Götterdämmerung model:GTD-20S mul id:6629 Config:Biped diff --git a/megameklab/data/mechfiles/mechs/3145/Steiner/King Crab KGC-009.mtf b/megameklab/data/mechfiles/mechs/3145/Steiner/King Crab KGC-009.mtf index 90fa9cefa..2b842887d 100644 --- a/megameklab/data/mechfiles/mechs/3145/Steiner/King Crab KGC-009.mtf +++ b/megameklab/data/mechfiles/mechs/3145/Steiner/King Crab KGC-009.mtf @@ -163,7 +163,7 @@ IS Endo Steel overview:The King Crab has been a horror on the battlefield since its introduction just before the old Star League's demise, and it is well known for its ability to quickly kill most BattleMechs under eighty tons. -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,[6] and has been described as a "notorious hangar queen". +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:Manufactured from 3104 onward by StarCorps Industries from their facility on Loburg, the 009 variant of the King Crab was an update intended to meet the demands of the modern battlefield. Constructed around a StarFrame Hill Endo Steel chassis mated with the Vlar 300 engine of the original and a Heavy-Duty Gyro, the 009 is a rugged 'Mech even before StarCorps sheathed the 009 in nineteen and a half tons of ArcShield VII Mk. 5 armor with CASE, literally as much armor as could be fitted to the frame. For electronics StarCorps used a Dalban Commline communications system, augmented by a Guardian ECM Suite, and a Dalban HiRez-B targeting and tracking system. Fourteen double heat sinks were installed to try and mitigate the heat output of the heavy armament on the -009 - armament that consisted of a SarLon MiniCannon Light Class 5 Autocannon and a Defiance Novashot Model 2 plasma rifle in each arm, along with a Doombud 7-Tube Multi-Missile Launcher and a Phototec 806c medium laser in each of the left and right torsos. Each plasma rifle is served by two tons of ammunition stored in the arm alongside the Rifle, while each Light AC/5 draws on a ton of ammunition stored in the torso closest to the arm, and a total of three tons of ammunition is available for the two MML-7s to draw on. Despite the relatively low speed, ammunition dependency and Small Cockpit, the -009 was popular with senior Lyran officers. diff --git a/megameklab/data/mechfiles/mechs/3150/Gotterdammerung GTD-20C.mtf b/megameklab/data/mechfiles/mechs/3150/Gotterdammerung GTD-20C.mtf index 0a00fe6d7..46a9a712e 100644 --- a/megameklab/data/mechfiles/mechs/3150/Gotterdammerung GTD-20C.mtf +++ b/megameklab/data/mechfiles/mechs/3150/Gotterdammerung GTD-20C.mtf @@ -1,4 +1,4 @@ -chassis:Gotterdammerung +chassis:Götterdämmerung model:GTD-20C mul id:8061 Config:Biped diff --git a/megameklab/data/mechfiles/mechs/3150/Gotterdammerung GTD-30S.mtf b/megameklab/data/mechfiles/mechs/3150/Gotterdammerung GTD-30S.mtf index d89b56f2f..9e84aaad0 100644 --- a/megameklab/data/mechfiles/mechs/3150/Gotterdammerung GTD-30S.mtf +++ b/megameklab/data/mechfiles/mechs/3150/Gotterdammerung GTD-30S.mtf @@ -1,4 +1,4 @@ -chassis:Gotterdammerung +chassis:Götterdämmerung model:GTD-30S mul id:8062 Config:Biped diff --git a/megameklab/data/mechfiles/mechs/3150/Shrike Black Rose.mtf b/megameklab/data/mechfiles/mechs/3150/Shrike Black Rose.mtf index 9bf27a157..7a2a0a924 100644 --- a/megameklab/data/mechfiles/mechs/3150/Shrike Black Rose.mtf +++ b/megameklab/data/mechfiles/mechs/3150/Shrike Black Rose.mtf @@ -158,7 +158,7 @@ Clan Endo Steel overview:The Shrike's humble origins derive from Red Devil Industries' Onager, which was clearly inspired by the aesthetics of Olivetti's Flamberge and Eyrie. capabilities:Despite being heavier than its spiritual forefather, the Shrike outperforms the Onager in every way. It can outmaneuver many heavy and assault 'Mechs, and jump jets combined with a partial wing allow the Shrike to reach regions where most 'Mechs in its weight class cannot. The Shrike's armaments and targeting computer let it to remain a safe distance from its opponents, perhaps keeping the pilot safe without sacrificing accuracy, and reinforced legs promote Death From Above strikes on those who get too close. The Shrike is a command 'Mech with heavy armor, a command station, and a terrifying falcon shape. deployment:No information on this variant -history:At first appearance, one might mistake the ferocious Shrike for another falcon-themed BattleMech manufactured by Olivetti Weaponry. Eagle Craft Group adopted the Onager concept and retooled it to fit the Clan Council's rejuvenation mandates and design philosophy, following in the footsteps of the Eyrie. The heavier Shrike, which debuted shortly after Olivetti's similarly fashioned Gyrfalcon, drew praise from the warrior caste when it outperformed the Onager in every category. Many Falcon fighters issued Trials of Possession for Shrikes after observing them struggle against fast, heavy 'Mechs. Because of its agility, thick armor, range, precision, and terrifying battlefield presence, the Shrike has quickly become a favorite among Galaxy and Cluster commanders. Although a few salvaged chassis have appeared on Lyran black markets, the Shrike remains a Jade Falcon asset. +history:At first appearance, one might mistake the ferocious Shrike for another falcon-themed BattleMech manufactured by Olivetti Weaponry. Eagle Craft Group adopted the Onager concept and retooled it to fit the Clan Council's rejuvenation mandates and design philosophy, following in the footsteps of the Eyrie. The heavier Shrike, which debuted shortly after Olivetti's similarly fashioned Gyrfalcon, drew praise from the warrior caste when it outperformed the Onager in every category. Many Falcon fighters issued Trials of Possession for Shrikes after observing them struggle against fast, heavy 'Mechs. Because of its agility, thick armor, range, precision, and terrifying battlefield presence, the Shrike has quickly become a favorite among Galaxy and Cluster commanders. Although a few salvaged chassis have appeared on Lyran black markets, the Shrike remains a Jade Falcon asset. manufacturer:Eagle Craft Group primaryfactory:Erewhon systemmanufacturer:CHASSIS:DSAM Endo 4 diff --git a/megameklab/data/mechfiles/mechs/Arano Restoration/Atlas II AS7-D-HT.mtf b/megameklab/data/mechfiles/mechs/Arano Restoration/Atlas II AS7-D-HT.mtf index 9072a1095..f553de05d 100644 --- a/megameklab/data/mechfiles/mechs/Arano Restoration/Atlas II AS7-D-HT.mtf +++ b/megameklab/data/mechfiles/mechs/Arano Restoration/Atlas II AS7-D-HT.mtf @@ -165,7 +165,7 @@ overview:The technologically-advanced Hegemony counterpart to the SLDF's regular capabilities:The weapons payload gives the design more broad range attack ability versus the Atlas's brawling weaponry and its limited long range attack capacities. -deployment:Its origins unknown, the only known example of the AS7-D-HT was found inside Castle Nautilus, an SLDF Outpost Fortress found in the world of Artru, in the Aurigan Reach and used by Kamea Arano during her final defeat of the Aurigan Directorate.[12] This seemingly custom variant retains the bulk of the standard model's weapon loadout save swapping the LB-X-10 for a mammoth Autocannon/20 for enhanced short-range combat. +deployment:Its origins unknown, the only known example of the AS7-D-HT was found inside Castle Nautilus, an SLDF Outpost Fortress found in the world of Artru, in the Aurigan Reach and used by Kamea Arano during her final defeat of the Aurigan Directorate. This seemingly custom variant retains the bulk of the standard model's weapon loadout save swapping the LB-X-10 for a mammoth Autocannon/20 for enhanced short-range combat. history:First fielded in 2765, the Atlas II was designed by the Hegemony Research and Development Department, Weapons Division of the original Star League to maintain the technological edge over the other Great Houses. It was exclusively for the SLDF's Royal Regiments. In 2785, when General Aleksandr Kerensky put out his call for loyal forces to join him in his Exodus, every Atlas II pilot responded and left with him. These 'Mechs are prized by the Clans when they were found. One such 'Mech was spotted in 3052 during the Battle of Tukayyid. In the early 3070s, the design was resurrected by the Word of Blake when they captured Hesperus II's factories. After the liberation of Defiance Industries, Devlin Stone's coalition forces kept the 'Mechs in production. diff --git a/megameklab/data/mechfiles/mechs/Dark Age/Agrotera AGT-1A.mtf b/megameklab/data/mechfiles/mechs/Dark Age/Agrotera AGT-1A.mtf index 0438eddfb..c6e16fa4e 100644 --- a/megameklab/data/mechfiles/mechs/Dark Age/Agrotera AGT-1A.mtf +++ b/megameklab/data/mechfiles/mechs/Dark Age/Agrotera AGT-1A.mtf @@ -155,7 +155,7 @@ Jump Jet overview:The Agrotera is a medium BattleMech that would go on to serve in the armed forces of both the Magistracy of Canopus and its ally, the Capellan Confederation. Based on the Word of Blake's variant of the Phoenix Hawk, the Agrotera is designed as a multipurpose and ammunition-efficient design. capabilities:Designed with advanced technology in mind, the 'Mech's engineers outfitted the Agrotera with new advancements made during the Jihad. Like the 3060s redesigned Phoenix Hawk, the 'Mech is fitted with a Full-Head Ejection System, which allows for increased comfort and safety for the MechWarrior should its nine and a half tons of standard armor fail. A partial wing boosts mobility and cooling. The design also benefits from weight savings by being fitted with a Rawlings 300 XL extralight engine and an XL gyro. TAG equipment is fitted to allow the Agrotera to act as a spotter for friendly fire-support units. -deployment:The Agrotera's long-range weapon is its Ceres Arms Smasher ER PPC, mounted in its left arm actuator, its accuracy enhanced with the fitting of an Actuator Enhancement System. In addition to the ER PPC, the 'Mech also has a single Diverse Optics medium variable speed pulse laser found in the right arm, a regular medium pulse laser, and a pair of Diverse Optics small pulse lasers, one on each of the side torsos as a means to deter infantry and battle armor threats.[ +deployment:The Agrotera's long-range weapon is its Ceres Arms Smasher ER PPC, mounted in its left arm actuator, its accuracy enhanced with the fitting of an Actuator Enhancement System. In addition to the ER PPC, the 'Mech also has a single Diverse Optics medium variable speed pulse laser found in the right arm, a regular medium pulse laser, and a pair of Diverse Optics small pulse lasers, one on each of the side torsos as a means to deter infantry and battle armor threats. history:The design would see action with the MoC's 1st Magistracy Highlanders on Bethonolog in 3108 against more dangerous pirates, where a pair of Agroteras engaged a full lance of heavy BattleMechs. While trying to buy time for the rest of the Highlanders to arrive, the two 'Mechs managed to force the bandits into submission through the Agrotera's steady delivery of damaging blows against them while simultaneously outmaneuvering them. Their performance soon proved to be too much for the pirates, and the survivors surrendered just as the rest of the Highlanders' heavier units arrived on the scene. manufacturer:Majesty Metals and Manufacturing primaryfactory:Canopus IV diff --git a/megameklab/data/mechfiles/mechs/Dark Age/Atlas AS7-K2 (Jedra).mtf b/megameklab/data/mechfiles/mechs/Dark Age/Atlas AS7-K2 (Jedra).mtf index 5e43d12f8..da0ab14bb 100644 --- a/megameklab/data/mechfiles/mechs/Dark Age/Atlas AS7-K2 (Jedra).mtf +++ b/megameklab/data/mechfiles/mechs/Dark Age/Atlas AS7-K2 (Jedra).mtf @@ -165,7 +165,7 @@ Ferro-Fibrous overview:"A 'Mech as powerful as possible, as impenetrable as possible, and as ugly and foreboding as conceivable, so that fear itself will be our ally.”-Aleksandr Kerensky -capabilities:The Atlas is probably the best-known BattleMech to ever set foot on the modern battlefield. Designed with specifications from Aleksandr Kerensky himself in 2755 in the midst of the Cameron Edicts, the Atlas was originally intended to ensure SLDF superiority over the Star League member states. Carrying the largest LRM launcher, the largest autocannon, and the largest SRM launcher possible, the Atlas can deal frightening amounts of damage in short amounts of time. Often used as a command vehicle, the Atlas mounts an advanced antenna and communications array, allowing it to engage in surface-to space communications in real time. The massive 19-ton hide of armor that protects the Atlas makes it a difficult foe to take down. Indeed, most MechWarriors choose to fall back rather than face one head-one, as its lumbering gait mean it can rarely catch up to other 'Mechs that choose to flee it. A full year of development went into crafting the famous "Death's Head" of the 'Mech to achieve the perfect ratio of functionality and fear. The head is also quite roomy and allows a small satellite dish to be mounted for surface-to-space communications. During combat the pilot can easily fold up the dish and store it within a protective portion of the head. +capabilities:The Atlas is probably the best-known BattleMech to ever set foot on the modern battlefield. Designed with specifications from Aleksandr Kerensky himself in 2755 in the midst of the Cameron Edicts, the Atlas was originally intended to ensure SLDF superiority over the Star League member states. Carrying the largest LRM launcher, the largest autocannon, and the largest SRM launcher possible, the Atlas can deal frightening amounts of damage in short amounts of time. Often used as a command vehicle, the Atlas mounts an advanced antenna and communications array, allowing it to engage in surface-to-space communications in real time. The massive 19-ton hide of armor that protects the Atlas makes it a difficult foe to take down. Indeed, most MechWarriors choose to fall back rather than face one head-on, as its lumbering gait means it can rarely catch up to other 'Mechs that choose to flee it. A full year of development went into crafting the famous "Death's Head" of the 'Mech to achieve the perfect ratio of functionality and fear. The head is also quite roomy and allows a small satellite dish to be mounted for surface-to-space communications. During combat the pilot can easily fold up the dish and store it within a protective portion of the head. deployment:Used by Lord Jedra Kean of Vega this variant of the Atlas removed the standard weaponry. Each arm carried a Light Gauss Rifle. The right and left torsos each carried a pair of ER Medium Lasers and a single SRM 4. The center torso carried a single ER Medium Laser. The armor protection, heat sinks, and ground performance remained identical to a standard AS7-K2. diff --git a/megameklab/data/mechfiles/mechs/ER 2750/Crab CRB-27sl.mtf b/megameklab/data/mechfiles/mechs/ER 2750/Crab CRB-27sl.mtf index e5cb89b5b..459c74250 100644 --- a/megameklab/data/mechfiles/mechs/ER 2750/Crab CRB-27sl.mtf +++ b/megameklab/data/mechfiles/mechs/ER 2750/Crab CRB-27sl.mtf @@ -156,7 +156,7 @@ Jump Jet overview:Designed in 2719 during the last days of the Star League, the Crab was built as a medium-weight raider and guerrilla fighter for the Star League Defense Force. -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 +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. diff --git a/megameklab/data/mechfiles/mechs/ForcePacks/UrbanMech/UrbanMech UM-R27.mtf b/megameklab/data/mechfiles/mechs/ForcePacks/UrbanMech/UrbanMech UM-R27.mtf index 9be92b5df..1a5781f38 100644 --- a/megameklab/data/mechfiles/mechs/ForcePacks/UrbanMech/UrbanMech UM-R27.mtf +++ b/megameklab/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 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. manufacturer:Orgus Industries primaryfactory:Marcus diff --git a/megameklab/data/mechfiles/mechs/ForcePacks/Wolfs Dragoons/Archer C 2.mtf b/megameklab/data/mechfiles/mechs/ForcePacks/Wolfs Dragoons/Archer C 2.mtf index a6e17f8af..8e256651e 100644 --- a/megameklab/data/mechfiles/mechs/ForcePacks/Wolfs Dragoons/Archer C 2.mtf +++ b/megameklab/data/mechfiles/mechs/ForcePacks/Wolfs Dragoons/Archer C 2.mtf @@ -161,7 +161,7 @@ Foot Actuator overview:One of the most iconic BattleMechs is the Archer, with its low-slung torso, enormous fists, and missile-bay covers. The Archer was first manufactured in 2474 for heavy-hitting, long-range brawling, and fire-support. -capabilities:Two enormous missile launchers with tons of ammo power the Archer. The missiles were formidable, but their short-range inaccuracy required four medium lasers, two rear-facing and one in each arm. Enlarged hand actuators allow the design to undertake severe physical attacks and transport captured supplies during raids. The cockpit of the Archer situated beneath the center midsection, giving the pilot a unique battlefield view. The torso armor belt above the cockpit protects the gyro and engine from the superior armor. Many pilots initially entered battle with their missile bays locked to hide the 'Mech's real capabilities, leading some to believe it was a close-combat design. As the Archer became famous, this pretext became meaningless. Archer pilots rarely learn new skills, but this hasn't tarnished the 'Mech's reputation. +capabilities:Two enormous missile launchers with tons of ammo power the Archer. The missiles were formidable, but their short-range inaccuracy required four medium lasers, two rear-facing and one in each arm. Enlarged hand actuators allow the design to undertake severe physical attacks and transport captured supplies during raids. The cockpit of the Archer is situated beneath the center midsection, giving the pilot a unique battlefield view. The torso armor belt above the cockpit protects the gyro and engine from the superior armor. Many pilots initially entered battle with their missile bays locked to hide the 'Mech's real capabilities, leading some to believe it was a close-combat design. As the Archer became famous, this pretext became meaningless. Archer pilots rarely learn new skills, but this hasn't tarnished the 'Mech's reputation. deployment:A Civil War-era alternate configuration to the Archer C, the C 2 mounts two LRM-20s with Artemis IV functionality as its primary weapon group. Taking inspiration from the ARC-2S, the Archer C 2 also mounts a pair of Streak SRM-4s for close-range firepower, and a medium pulse laser in each arm complete the point-defense package. Twelve double heat sinks provide adequate heat dissipation, but operators should be wary of this variant's propensity to overheat itself with repeated alpha strikes. diff --git a/megameklab/data/mechfiles/mechs/ForcePacks/Wolfs Dragoons/Blackjack C.mtf b/megameklab/data/mechfiles/mechs/ForcePacks/Wolfs Dragoons/Blackjack C.mtf index 5303ae2a3..5e2077d62 100644 --- a/megameklab/data/mechfiles/mechs/ForcePacks/Wolfs Dragoons/Blackjack C.mtf +++ b/megameklab/data/mechfiles/mechs/ForcePacks/Wolfs Dragoons/Blackjack C.mtf @@ -155,7 +155,7 @@ capabilities:The Blackjack's original mission was to assist in suppressing insur deployment:A Clan-tech refit, equipped similarly to the BJ-2. This variant carries a large pulse laser in each arm, and a Streak SRM-4 in each side torso. The ammunition for the missile launchers is carried in the left torso, protected by a CASE II system - the 'Mech also sports double heat sinks and ferro-fibrous armor. -history:The Blackjack had limited use in the Star League, and manufacture was shortly discontinued. The Blackjack, relegated to service with Hegemony planetary militia or sold to League member nations, 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. +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. manufacturer:Various primaryfactory:Various diff --git a/megameklab/data/mechfiles/mechs/Golden Century/Excalibur EXC-B2b-EC.mtf b/megameklab/data/mechfiles/mechs/Golden Century/Excalibur EXC-B2b-EC.mtf index 174ed375a..6e1e9bdf6 100644 --- a/megameklab/data/mechfiles/mechs/Golden Century/Excalibur EXC-B2b-EC.mtf +++ b/megameklab/data/mechfiles/mechs/Golden Century/Excalibur EXC-B2b-EC.mtf @@ -154,5 +154,5 @@ IS Endo Steel -Empty- -Empty- -history:After KLONDIKE, Wolf techs radically altered the regular Excaliburs in their possession. They replaced the gauss rifle and LRM launcher with new improved versions, which freed up enough room to include a prototype ER medium laser in the left arm and four tons of additional armor. The biggest change to the old design was the replacement of the single heat sinks with surplus doubles and moving the anti-missile ammunition to a CASE-protected torso location. Throughout the early clan years, Wolf Excaliburs were some of the coolest-running ’Mechs in clan space. +history:After KLONDIKE, Wolf techs radically altered the regular Excaliburs in their possession. They replaced the gauss rifle and LRM launcher with new improved versions, which freed up enough room to include a prototype ER medium laser in the left arm and four tons of additional armor. The biggest change to the old design was the replacement of the single heat sinks with surplus doubles and moving the anti-missile ammunition to a CASE-protected torso location. Throughout the early clan years, Wolf Excaliburs were some of the coolest-running ’Mechs in clan space. diff --git a/megameklab/data/mechfiles/mechs/Golden Century/Exterminator EC EXT-4Db.mtf b/megameklab/data/mechfiles/mechs/Golden Century/Exterminator EC EXT-4Db.mtf index a1be14c26..53ebaf480 100644 --- a/megameklab/data/mechfiles/mechs/Golden Century/Exterminator EC EXT-4Db.mtf +++ b/megameklab/data/mechfiles/mechs/Golden Century/Exterminator EC EXT-4Db.mtf @@ -159,7 +159,7 @@ Foot Actuator overview:The Exterminator is a BattleMech that was designed in 2630 for the most dubious, but necessary, of purposes: Head Hunting. -capabilities:The weapons used by the Exterminator are not nearly as unique or high tech as the electronics on board. The primary weapons of the Exterminator are medium weight lasers, two of each in either arm. For long range engagements, the 'Mech also carries a missile launcher with one ton of reloads in the center torso. These weapons are backed up by a short range laser mounted in the head for when engagements close to point blank range, and, for defense against missile attacks, the Exterminator has a Anti-Missile System in the right torso with one ton of ammo. +capabilities:The weapons used by the Exterminator are not nearly as unique or high tech as the electronics on board. The primary weapons of the Exterminator are medium weight lasers, two in each arm. For long range engagements, the 'Mech also carries a missile launcher with one ton of reloads in the center torso. These weapons are backed up by a short range laser mounted in the head for when engagements close to point blank range, and, for defense against missile attacks, the Exterminator has a Anti-Missile System in the right torso with one ton of ammo. deployment:An early Clan Jade Falcon refit of the EXT-4Db trades the medium lasers for prototype ER medium lasers. It was popular for duels and Trials. diff --git a/megameklab/data/mechfiles/mechs/Historicals/Hist LOT II/Dragoon AEM-01.mtf b/megameklab/data/mechfiles/mechs/Historicals/Hist LOT II/Dragoon AEM-01.mtf index f0a7cf229..7a003b0f9 100644 --- a/megameklab/data/mechfiles/mechs/Historicals/Hist LOT II/Dragoon AEM-01.mtf +++ b/megameklab/data/mechfiles/mechs/Historicals/Hist LOT II/Dragoon AEM-01.mtf @@ -165,7 +165,7 @@ capabilities:Armed with only a few, but powerful weapons found only in the 'Mech deployment:The Dragoon 01 makes use of a pair of Krupp 120 KgK 78 L/66 LB 10-X Autocannons. Backup is given in the form of a long-reaching Blankenburg Technologies 200 ER PPC. -history:n the year following the Amaris Coup, now-Emperor Amaris would have a means to make his dream into reality, and he began swiftly issuing contracts which would lead to the creation of the Dragoon. Built by Krupp Stellar Technologies Inc. in 2771 as their second BattleMech design, the Dragoon was designed with a similar modular subsystem akin to the Mercury BattleMech. With this system, the 'Mech's maintenance loads would be eased. Its modular nature would allow repair depots and factories to be able to reconfigure the design's weapons systems and its power plant for any needed mission-specific specs. Produced in limited numbers, only the elite of Amaris's regiments and a select few of Amaris's loyal chosen would receive the design and its variants. The design would see service in the Star League Civil War, often being salvaged by the Star League Defense Force. However, after the liberation of Terra, General Kerensky would order the purging of the design and the retooling of Krupp's two Dragoon production lines. The few remaining Dragoons in service elsewhere would become extinct before the 3rd Succession War. +history:In the year following the Amaris Coup, now-Emperor Amaris would have a means to make his dream into reality, and he began swiftly issuing contracts which would lead to the creation of the Dragoon. Built by Krupp Stellar Technologies Inc. in 2771 as their second BattleMech design, the Dragoon was designed with a similar modular subsystem akin to the Mercury BattleMech. With this system, the 'Mech's maintenance loads would be eased. Its modular nature would allow repair depots and factories to be able to reconfigure the design's weapons systems and its power plant for any needed mission-specific specs. Produced in limited numbers, only the elite of Amaris's regiments and a select few of Amaris's loyal chosen would receive the design and its variants. The design would see service in the Star League Civil War, often being salvaged by the Star League Defense Force. However, after the liberation of Terra, General Kerensky would order the purging of the design and the retooling of Krupp's two Dragoon production lines. The few remaining Dragoons in service elsewhere would become extinct before the 3rd Succession War. manufacturer:Krupp Stellar Technologies, Inc. primaryfactory:Terra diff --git a/megameklab/data/mechfiles/mechs/Historicals/Hist LOT II/Dragoon AEM-02.mtf b/megameklab/data/mechfiles/mechs/Historicals/Hist LOT II/Dragoon AEM-02.mtf index 532e31a22..7b9e96d2f 100644 --- a/megameklab/data/mechfiles/mechs/Historicals/Hist LOT II/Dragoon AEM-02.mtf +++ b/megameklab/data/mechfiles/mechs/Historicals/Hist LOT II/Dragoon AEM-02.mtf @@ -158,7 +158,7 @@ capabilities:Armed with only a few, but powerful weapons found only in the 'Mech deployment:Designed as a short-ranged fighter, the Dragoon 02 is armed with a single ER PPC, the remaining weapons space is filled by five Medium Lasers, a Small Pulse Laser, and an AC/20. At the price of dropping its jump jets, the 'Mech's engine has been upgraded to an XL 350 to allow the 'Mech to close in quicker than the original model. -history:n the year following the Amaris Coup, now-Emperor Amaris would have a means to make his dream into reality, and he began swiftly issuing contracts which would lead to the creation of the Dragoon. Built by Krupp Stellar Technologies Inc. in 2771 as their second BattleMech design, the Dragoon was designed with a similar modular subsystem akin to the Mercury BattleMech. With this system, the 'Mech's maintenance loads would be eased. Its modular nature would allow repair depots and factories to be able to reconfigure the design's weapons systems and its power plant for any needed mission-specific specs. Produced in limited numbers, only the elite of Amaris's regiments and a select few of Amaris's loyal chosen would receive the design and its variants. The design would see service in the Star League Civil War, often being salvaged by the Star League Defense Force. However, after the liberation of Terra, General Kerensky would order the purging of the design and the retooling of Krupp's two Dragoon production lines. The few remaining Dragoons in service elsewhere would become extinct before the 3rd Succession War. +history:In the year following the Amaris Coup, now-Emperor Amaris would have a means to make his dream into reality, and he began swiftly issuing contracts which would lead to the creation of the Dragoon. Built by Krupp Stellar Technologies Inc. in 2771 as their second BattleMech design, the Dragoon was designed with a similar modular subsystem akin to the Mercury BattleMech. With this system, the 'Mech's maintenance loads would be eased. Its modular nature would allow repair depots and factories to be able to reconfigure the design's weapons systems and its power plant for any needed mission-specific specs. Produced in limited numbers, only the elite of Amaris's regiments and a select few of Amaris's loyal chosen would receive the design and its variants. The design would see service in the Star League Civil War, often being salvaged by the Star League Defense Force. However, after the liberation of Terra, General Kerensky would order the purging of the design and the retooling of Krupp's two Dragoon production lines. The few remaining Dragoons in service elsewhere would become extinct before the 3rd Succession War. manufacturer:Krupp Stellar Technologies, Inc. primaryfactory:Terra diff --git a/megameklab/data/mechfiles/mechs/Historicals/Hist LOT II/Dragoon AEM-03.mtf b/megameklab/data/mechfiles/mechs/Historicals/Hist LOT II/Dragoon AEM-03.mtf index bf9d1ac58..a22612da1 100644 --- a/megameklab/data/mechfiles/mechs/Historicals/Hist LOT II/Dragoon AEM-03.mtf +++ b/megameklab/data/mechfiles/mechs/Historicals/Hist LOT II/Dragoon AEM-03.mtf @@ -157,7 +157,7 @@ capabilities:Armed with only a few, but powerful weapons found only in the 'Mech deployment:Designed as a long-range fire support unit, the Dragoon 03 retains the same engine specifications of the Dragoon 01 model. Its principal weaponry includes 3 Artemis IV FCS-guided 15-tubed LRM Launchers with 2 tons of CASE-protected ammunition. Backup weapons include a single Medium Laser, with a duo of Medium and Small Pulse Lasers for close-in defense. -history:n the year following the Amaris Coup, now-Emperor Amaris would have a means to make his dream into reality, and he began swiftly issuing contracts which would lead to the creation of the Dragoon. Built by Krupp Stellar Technologies Inc. in 2771 as their second BattleMech design, the Dragoon was designed with a similar modular subsystem akin to the Mercury BattleMech. With this system, the 'Mech's maintenance loads would be eased. Its modular nature would allow repair depots and factories to be able to reconfigure the design's weapons systems and its power plant for any needed mission-specific specs. Produced in limited numbers, only the elite of Amaris's regiments and a select few of Amaris's loyal chosen would receive the design and its variants. The design would see service in the Star League Civil War, often being salvaged by the Star League Defense Force. However, after the liberation of Terra, General Kerensky would order the purging of the design and the retooling of Krupp's two Dragoon production lines. The few remaining Dragoons in service elsewhere would become extinct before the 3rd Succession War. +history:In the year following the Amaris Coup, now-Emperor Amaris would have a means to make his dream into reality, and he began swiftly issuing contracts which would lead to the creation of the Dragoon. Built by Krupp Stellar Technologies Inc. in 2771 as their second BattleMech design, the Dragoon was designed with a similar modular subsystem akin to the Mercury BattleMech. With this system, the 'Mech's maintenance loads would be eased. Its modular nature would allow repair depots and factories to be able to reconfigure the design's weapons systems and its power plant for any needed mission-specific specs. Produced in limited numbers, only the elite of Amaris's regiments and a select few of Amaris's loyal chosen would receive the design and its variants. The design would see service in the Star League Civil War, often being salvaged by the Star League Defense Force. However, after the liberation of Terra, General Kerensky would order the purging of the design and the retooling of Krupp's two Dragoon production lines. The few remaining Dragoons in service elsewhere would become extinct before the 3rd Succession War. manufacturer:Krupp Stellar Technologies, Inc. primaryfactory:Terra diff --git a/megameklab/data/mechfiles/mechs/Historicals/Hist LOT II/Dragoon AEM-04.mtf b/megameklab/data/mechfiles/mechs/Historicals/Hist LOT II/Dragoon AEM-04.mtf index b40999292..96ae738d1 100644 --- a/megameklab/data/mechfiles/mechs/Historicals/Hist LOT II/Dragoon AEM-04.mtf +++ b/megameklab/data/mechfiles/mechs/Historicals/Hist LOT II/Dragoon AEM-04.mtf @@ -157,7 +157,7 @@ capabilities:Armed with only a few, but powerful weapons found only in the 'Mech deployment:Based on a weapon-stripped 01 model, Dragoon 04's long-ranged weapons come in the form of a single Gauss Rifle and an ER PPC. Its short-ranged weapons include four SRM 4s and a pair of Medium Lasers. -history:n the year following the Amaris Coup, now-Emperor Amaris would have a means to make his dream into reality, and he began swiftly issuing contracts which would lead to the creation of the Dragoon. Built by Krupp Stellar Technologies Inc. in 2771 as their second BattleMech design, the Dragoon was designed with a similar modular subsystem akin to the Mercury BattleMech. With this system, the 'Mech's maintenance loads would be eased. Its modular nature would allow repair depots and factories to be able to reconfigure the design's weapons systems and its power plant for any needed mission-specific specs. Produced in limited numbers, only the elite of Amaris's regiments and a select few of Amaris's loyal chosen would receive the design and its variants. The design would see service in the Star League Civil War, often being salvaged by the Star League Defense Force. However, after the liberation of Terra, General Kerensky would order the purging of the design and the retooling of Krupp's two Dragoon production lines. The few remaining Dragoons in service elsewhere would become extinct before the 3rd Succession War. +history:In the year following the Amaris Coup, now-Emperor Amaris would have a means to make his dream into reality, and he began swiftly issuing contracts which would lead to the creation of the Dragoon. Built by Krupp Stellar Technologies Inc. in 2771 as their second BattleMech design, the Dragoon was designed with a similar modular subsystem akin to the Mercury BattleMech. With this system, the 'Mech's maintenance loads would be eased. Its modular nature would allow repair depots and factories to be able to reconfigure the design's weapons systems and its power plant for any needed mission-specific specs. Produced in limited numbers, only the elite of Amaris's regiments and a select few of Amaris's loyal chosen would receive the design and its variants. The design would see service in the Star League Civil War, often being salvaged by the Star League Defense Force. However, after the liberation of Terra, General Kerensky would order the purging of the design and the retooling of Krupp's two Dragoon production lines. The few remaining Dragoons in service elsewhere would become extinct before the 3rd Succession War. manufacturer:Krupp Stellar Technologies, Inc. primaryfactory:Terra diff --git a/megameklab/data/mechfiles/mechs/Historicals/Hist Reunification War/Alfar AL-D1 Dokkalfar.mtf b/megameklab/data/mechfiles/mechs/Historicals/Hist Reunification War/Alfar AL-D1 Dokkalfar.mtf index 16480f258..eba6dab09 100644 --- a/megameklab/data/mechfiles/mechs/Historicals/Hist Reunification War/Alfar AL-D1 Dokkalfar.mtf +++ b/megameklab/data/mechfiles/mechs/Historicals/Hist Reunification War/Alfar AL-D1 Dokkalfar.mtf @@ -1,5 +1,5 @@ chassis:Alfar -model:AL-D1 'Dokkalfar' +model:AL-D1 'Dökkálfar' mul id:3693 Config:Biped diff --git a/megameklab/data/mechfiles/mechs/ISP3/Arana MilitiaMech ARA-S-1.mtf b/megameklab/data/mechfiles/mechs/ISP3/Arana MilitiaMech ARA-S-1.mtf index 46a017275..05a39705e 100644 --- a/megameklab/data/mechfiles/mechs/ISP3/Arana MilitiaMech ARA-S-1.mtf +++ b/megameklab/data/mechfiles/mechs/ISP3/Arana MilitiaMech ARA-S-1.mtf @@ -1,11 +1,11 @@ -chassis:Arana +chassis:Araña model:ARA-S-1 MilitiaMech mul id:5798 Config:Quad TechBase:Clan Era:3087 -Source:Intersteller Players 3 +Source:Interstellar Players 3 Rules Level:3 Mass:40 diff --git a/megameklab/data/mechfiles/mechs/LAMS/Wasp LAM WSP-105.mtf b/megameklab/data/mechfiles/mechs/LAMS/Wasp LAM WSP-105.mtf index 358f0674f..f44433cd6 100644 --- a/megameklab/data/mechfiles/mechs/LAMS/Wasp LAM WSP-105.mtf +++ b/megameklab/data/mechfiles/mechs/LAMS/Wasp LAM WSP-105.mtf @@ -152,7 +152,7 @@ overview:Designed right after the Stinger LAM proved the Land-Air 'Mech concept, capabilities:The Wasp LAM is similar to the Stinger LAM, maintaining the same ground and air speed. The only real difference is in the armament. -deployment:the Wasp LAM is armed with a Martell Medium Laser and a Holly SRM-2. +deployment:The Wasp LAM is armed with a Martell Medium Laser and a Holly SRM-2. history:The Wasp LAM is able to convert from BattleMech to Aerospace Fighter faster than any other Land-Air 'Mech. The Wasp LAM also mounts no lostech (save the conversion equipment). The ease of use and ability to drop bombs from bomb bays made the Wasp LAM especially successful in air-to-ground strikes, no matter where that ground may be. During its first operation, Wasp LAMs were tasked with destroying a nuclear weapons facility orbiting in the Terran Oort Cloud in 2690. Generations of SLDF ground soldiers loved the Wasp LAM so much, they bestowed upon it the moniker "angels on our shoulders". The Wasp LAM was a highly sought-after prize, and a jealously guarded commodity when most of the Wasp LAM production facilities were destroyed shortly after the start of the First Succession War. By the thirty-first century, the Wasp LAM was an exceedingly rare sight within the Inner Sphere. diff --git a/megameklab/data/mechfiles/mechs/Operation Klondike/Annihilator ANH-1G.mtf b/megameklab/data/mechfiles/mechs/Operation Klondike/Annihilator ANH-1G.mtf index 3ba61cd29..921fd59e3 100644 --- a/megameklab/data/mechfiles/mechs/Operation Klondike/Annihilator ANH-1G.mtf +++ b/megameklab/data/mechfiles/mechs/Operation Klondike/Annihilator ANH-1G.mtf @@ -138,7 +138,7 @@ Foot Actuator overview:Originally developed in the final year of the Amaris Civil War as the ultimate fixed position city defense BattleMech. -capabilities:The Annihilator is armed with an arsenal that is built to instill fear in an enemy as much as damage them. The 100-ton 'Mech has a maximum speed of 32.4 km/h, making it one of the slowest 'Mechs ever designed together with the UrbanMech. It is by no means intended to use speed to outmaneuver an enemy, instead depending on its twelve and a half tons of armor to weather any fire that is directed at the 'Mech. +capabilities:The Annihilator is armed with an arsenal that is built to instill fear in an enemy as much as damage them. The 100-ton 'Mech has a maximum speed of 32.4 km/h, making it one of the slowest 'Mechs ever designed together with the UrbanMech. It is by no means intended to use speed to outmaneuver an enemy, instead depending on its twelve and a half tons of armor to weather any fire that is directed at the 'Mech. deployment:This variant had an ER PPC in the right torso, and three Gauss Rifles (one in each arm, and one in the left torso) to provide hard hitting firepower. Each Gauss Rifle had two tons of ammunition. Ten double heat sinks were more than adequate to keep the machine cool. diff --git a/megameklab/data/mechfiles/mechs/Operation Klondike/Annihilator ANH-1X.mtf b/megameklab/data/mechfiles/mechs/Operation Klondike/Annihilator ANH-1X.mtf index af1ec3195..ccf547c9e 100644 --- a/megameklab/data/mechfiles/mechs/Operation Klondike/Annihilator ANH-1X.mtf +++ b/megameklab/data/mechfiles/mechs/Operation Klondike/Annihilator ANH-1X.mtf @@ -146,7 +146,7 @@ Foot Actuator overview:Originally developed in the final year of the Amaris Civil War as the ultimate fixed position city defense BattleMech. -capabilities:The Annihilator is armed with an arsenal that is built to instill fear in an enemy as much as damage them. The 100-ton 'Mech has a maximum speed of 32.4 km/h, making it one of the slowest 'Mechs ever designed together with the UrbanMech. It is by no means intended to use speed to outmaneuver an enemy, instead depending on its twelve and a half tons of armor to weather any fire that is directed at the 'Mech. +capabilities:The Annihilator is armed with an arsenal that is built to instill fear in an enemy as much as damage them. The 100-ton 'Mech has a maximum speed of 32.4 km/h, making it one of the slowest 'Mechs ever designed together with the UrbanMech. It is by no means intended to use speed to outmaneuver an enemy, instead depending on its twelve and a half tons of armor to weather any fire that is directed at the 'Mech. deployment:The original model created in 2779 was equipped with a head-mounted Small Laser, four LB 10-X AC, a pair of Small Pulse Lasers, and four Medium Lasers. It carried six tons of LB 10-X ammunition, and the torsos were protected with CASE. Ten double heat sinks kept heat manageable. diff --git a/megameklab/data/mechfiles/mechs/Operation Klondike/Annihilator Bryan Gausszilla.mtf b/megameklab/data/mechfiles/mechs/Operation Klondike/Annihilator Bryan Gausszilla.mtf index 00ce7e104..4ef821882 100644 --- a/megameklab/data/mechfiles/mechs/Operation Klondike/Annihilator Bryan Gausszilla.mtf +++ b/megameklab/data/mechfiles/mechs/Operation Klondike/Annihilator Bryan Gausszilla.mtf @@ -139,7 +139,7 @@ CLDouble Heat Sink overview:Originally developed in the final year of the Amaris Civil War as the ultimate fixed position city defense BattleMech. -capabilities:The Annihilator is armed with an arsenal that is built to instill fear in an enemy as much as damage them. The 100-ton 'Mech has a maximum speed of 32.4 km/h, making it one of the slowest 'Mechs ever designed together with the UrbanMech. It is by no means intended to use speed to outmaneuver an enemy, instead depending on its twelve and a half tons of armor to weather any fire that is directed at the 'Mech. +capabilities:The Annihilator is armed with an arsenal that is built to instill fear in an enemy as much as damage them. The 100-ton 'Mech has a maximum speed of 32.4 km/h, making it one of the slowest 'Mechs ever designed together with the UrbanMech. It is by no means intended to use speed to outmaneuver an enemy, instead depending on its twelve and a half tons of armor to weather any fire that is directed at the 'Mech. deployment:Apparently based on the Annihilator C2, this customized variant carried a fifth Gauss Rifle in addition to the standard Gauss Rifle layout, with altogether only eight tons of ammunition. It was the customized personal 'Mech of early 29th century Clan Ghost Bear Star Colonel Bryan Kabrinski, and apparently a unique modification given the note (as of 3074) that the 'Mech was "lost to history". Known as "Gausszilla" in its time. diff --git a/megameklab/data/mechfiles/mechs/Operation Klondike/Annihilator C2.mtf b/megameklab/data/mechfiles/mechs/Operation Klondike/Annihilator C2.mtf index fa93eca43..7f042dc47 100644 --- a/megameklab/data/mechfiles/mechs/Operation Klondike/Annihilator C2.mtf +++ b/megameklab/data/mechfiles/mechs/Operation Klondike/Annihilator C2.mtf @@ -140,7 +140,7 @@ Endo-Steel overview:Originally developed in the final year of the Amaris Civil War as the ultimate fixed position city defense BattleMech. -capabilities:The Annihilator is armed with an arsenal that is built to instill fear in an enemy as much as damage them. The 100-ton 'Mech has a maximum speed of 32.4 km/h, making it one of the slowest 'Mechs ever designed together with the UrbanMech. It is by no means intended to use speed to outmaneuver an enemy, instead depending on its twelve and a half tons of armor to weather any fire that is directed at the 'Mech. +capabilities:The Annihilator is armed with an arsenal that is built to instill fear in an enemy as much as damage them. The 100-ton 'Mech has a maximum speed of 32.4 km/h, making it one of the slowest 'Mechs ever designed together with the UrbanMech. It is by no means intended to use speed to outmaneuver an enemy, instead depending on its twelve and a half tons of armor to weather any fire that is directed at the 'Mech. deployment:Apparently based on the ANH-1G, this variant only uses Clan technology. The 'Mech's top speed was 32.4 km/h and the armor protection was reduced, but four Gauss Rifles backed up by an ER PPC in the center torso and a head mounted ER Small Laser provided withering firepower for defensive engagements. Ten tons of ammunition kept the Gauss Rifles fed through the longest engagements. To make room for all these weapons, the C2 used an Endo Steel internal structure. Integrated CASE protected the arms and torsos from Gauss Rifle explosions. diff --git a/megameklab/data/mechfiles/mechs/Operation Klondike/Exterminator EXT-4Db.mtf b/megameklab/data/mechfiles/mechs/Operation Klondike/Exterminator EXT-4Db.mtf index fdd816090..e92cc0e35 100644 --- a/megameklab/data/mechfiles/mechs/Operation Klondike/Exterminator EXT-4Db.mtf +++ b/megameklab/data/mechfiles/mechs/Operation Klondike/Exterminator EXT-4Db.mtf @@ -142,7 +142,7 @@ Foot Actuator overview:The Exterminator is a BattleMech that was designed in 2630 for the most dubious, but necessary, of purposes: Head Hunting. -capabilities:The weapons used by the Exterminator are not nearly as unique or high tech as the electronics on board. The primary weapons of the Exterminator are medium weight lasers, two of each in either arm. For long range engagements, the 'Mech also carries a missile launcher with one ton of reloads in the center torso. These weapons are backed up by a short range laser mounted in the head for when engagements close to point blank range, and, for defense against missile attacks, the Exterminator has a Anti-Missile System in the right torso with one ton of ammo. +capabilities:The weapons used by the Exterminator are not nearly as unique or high tech as the electronics on board. The primary weapons of the Exterminator are medium weight lasers, two in each arm. For long range engagements, the 'Mech also carries a missile launcher with one ton of reloads in the center torso. These weapons are backed up by a short range laser mounted in the head for when engagements close to point blank range, and, for defense against missile attacks, the Exterminator has a Anti-Missile System in the right torso with one ton of ammo. deployment:This Star League Royal version, first introduced in 2718, replaces the LRM-10 and anti-missile system with an ER large laser. diff --git a/megameklab/data/mechfiles/mechs/Operation Klondike/Firefly FFL-3A.mtf b/megameklab/data/mechfiles/mechs/Operation Klondike/Firefly FFL-3A.mtf index 3e518956c..1b2fbcf94 100644 --- a/megameklab/data/mechfiles/mechs/Operation Klondike/Firefly FFL-3A.mtf +++ b/megameklab/data/mechfiles/mechs/Operation Klondike/Firefly FFL-3A.mtf @@ -167,7 +167,7 @@ capabilities: Although it was slow in comparison to other 'Mechs of its weight c deployment:First built in 2679, the standard Star League Defense Force model utilizes an XL engine, double heat sinks, and ferro-fibrous armor to reduce weight. A battery of four small lasers, three medium lasers, and an LRM-5 provide significant offensive capabilities for a recon 'Mech. TAG enhances its ability to spot for artillery, while CASE protects from ammunition explosion. -history:The Firefly, which entered service in the late 27th century, was one of the SLDF's primary light 'Mechs in its later years.Cases occurred in all House forces, but not in the numbers deployed by the SLDF, and all were presumed destroyed by the end of the Second Succession War, save for tales of anomalous examples in the Periphery. The design reappeared with Wolf's Dragoons in the early 31st century, raising eyebrows, yet the secret of the Firefly's origin was revealed when the Dragoons' Clan origins were revealed. In the 3040s, the advent of a small number of Fireflys with the Com Guard forces elicited a similar reaction. +history:The Firefly, which entered service in the late 27th century, was one of the SLDF's primary light 'Mechs in its later years. Cases occurred in all House forces, but not in the numbers deployed by the SLDF, and all were presumed destroyed by the end of the Second Succession War, save for tales of anomalous examples in the Periphery. The design reappeared with Wolf's Dragoons in the early 31st century, raising eyebrows, yet the secret of the Firefly's origin was exposed when the Dragoons' Clan origins were revealed. In the 3040s, the advent of a small number of Fireflys with the Com Guard forces elicited a similar reaction. manufacturer:Coventry/Earthwerks Combine primaryfactory:Terra diff --git a/megameklab/data/mechfiles/mechs/Operation Klondike/Firefly FFL-3PP.mtf b/megameklab/data/mechfiles/mechs/Operation Klondike/Firefly FFL-3PP.mtf index ac2e0fc0a..ab23d65be 100644 --- a/megameklab/data/mechfiles/mechs/Operation Klondike/Firefly FFL-3PP.mtf +++ b/megameklab/data/mechfiles/mechs/Operation Klondike/Firefly FFL-3PP.mtf @@ -146,7 +146,7 @@ capabilities: Although it was slow in comparison to other 'Mechs of its weight c deployment:A Pentagon Powers variant of the FFL-3SLE that removes the CASE and Guardian ECM suite in order to upgrade the missile rack to an LRM-10. -history:The Firefly, which entered service in the late 27th century, was one of the SLDF's primary light 'Mechs in its later years.Cases occurred in all House forces, but not in the numbers deployed by the SLDF, and all were presumed destroyed by the end of the Second Succession War, save for tales of anomalous examples in the Periphery. The design reappeared with Wolf's Dragoons in the early 31st century, raising eyebrows, yet the secret of the Firefly's origin was revealed when the Dragoons' Clan origins were revealed. In the 3040s, the advent of a small number of Fireflys with the Com Guard forces elicited a similar reaction. +history:The Firefly, which entered service in the late 27th century, was one of the SLDF's primary light 'Mechs in its later years. Cases occurred in all House forces, but not in the numbers deployed by the SLDF, and all were presumed destroyed by the end of the Second Succession War, save for tales of anomalous examples in the Periphery. The design reappeared with Wolf's Dragoons in the early 31st century, raising eyebrows, yet the secret of the Firefly's origin was exposed when the Dragoons' Clan origins were revealed. In the 3040s, the advent of a small number of Fireflys with the Com Guard forces elicited a similar reaction. manufacturer:Field Refit primaryfactory:Various diff --git a/megameklab/data/mechfiles/mechs/Operation Klondike/Firefly FFL-3PP2.mtf b/megameklab/data/mechfiles/mechs/Operation Klondike/Firefly FFL-3PP2.mtf index c11535f10..e3f2c10d1 100644 --- a/megameklab/data/mechfiles/mechs/Operation Klondike/Firefly FFL-3PP2.mtf +++ b/megameklab/data/mechfiles/mechs/Operation Klondike/Firefly FFL-3PP2.mtf @@ -147,7 +147,7 @@ capabilities: Although it was slow in comparison to other 'Mechs of its weight c deployment:Another refit of the FFL-3SLE, this time simply using standard armor plating instead of the advanced ferro-fibrous composites. -history:The Firefly, which entered service in the late 27th century, was one of the SLDF's primary light 'Mechs in its later years.Cases occurred in all House forces, but not in the numbers deployed by the SLDF, and all were presumed destroyed by the end of the Second Succession War, save for tales of anomalous examples in the Periphery. The design reappeared with Wolf's Dragoons in the early 31st century, raising eyebrows, yet the secret of the Firefly's origin was revealed when the Dragoons' Clan origins were revealed. In the 3040s, the advent of a small number of Fireflys with the Com Guard forces elicited a similar reaction. +history:The Firefly, which entered service in the late 27th century, was one of the SLDF's primary light 'Mechs in its later years. Cases occurred in all House forces, but not in the numbers deployed by the SLDF, and all were presumed destroyed by the end of the Second Succession War, save for tales of anomalous examples in the Periphery. The design reappeared with Wolf's Dragoons in the early 31st century, raising eyebrows, yet the secret of the Firefly's origin was exposed when the Dragoons' Clan origins were revealed. In the 3040s, the advent of a small number of Fireflys with the Com Guard forces elicited a similar reaction. manufacturer:Field Refit primaryfactory:Various diff --git a/megameklab/data/mechfiles/mechs/Operation Klondike/Firefly FFL-3PP3.mtf b/megameklab/data/mechfiles/mechs/Operation Klondike/Firefly FFL-3PP3.mtf index 58aeb9aec..3a29eb4e8 100644 --- a/megameklab/data/mechfiles/mechs/Operation Klondike/Firefly FFL-3PP3.mtf +++ b/megameklab/data/mechfiles/mechs/Operation Klondike/Firefly FFL-3PP3.mtf @@ -164,7 +164,7 @@ capabilities: Although it was slow in comparison to other 'Mechs of its weight c deployment:Again lacking in ferro-fibrous armor, this variation on the -3SLE also removes the Guardian ECM suite, instead upgrading the LRM-10 rack with an Artemis IV fire-control system. -history:The Firefly, which entered service in the late 27th century, was one of the SLDF's primary light 'Mechs in its later years.Cases occurred in all House forces, but not in the numbers deployed by the SLDF, and all were presumed destroyed by the end of the Second Succession War, save for tales of anomalous examples in the Periphery. The design reappeared with Wolf's Dragoons in the early 31st century, raising eyebrows, yet the secret of the Firefly's origin was revealed when the Dragoons' Clan origins were revealed. In the 3040s, the advent of a small number of Fireflys with the Com Guard forces elicited a similar reaction. +history:The Firefly, which entered service in the late 27th century, was one of the SLDF's primary light 'Mechs in its later years. Cases occurred in all House forces, but not in the numbers deployed by the SLDF, and all were presumed destroyed by the end of the Second Succession War, save for tales of anomalous examples in the Periphery. The design reappeared with Wolf's Dragoons in the early 31st century, raising eyebrows, yet the secret of the Firefly's origin was exposed when the Dragoons' Clan origins were revealed. In the 3040s, the advent of a small number of Fireflys with the Com Guard forces elicited a similar reaction. manufacturer:Field Refit primaryfactory:Various diff --git a/megameklab/data/mechfiles/mechs/Operation Klondike/Firefly FFL-3SLE.mtf b/megameklab/data/mechfiles/mechs/Operation Klondike/Firefly FFL-3SLE.mtf index d7ae78b12..3a5a4ffba 100644 --- a/megameklab/data/mechfiles/mechs/Operation Klondike/Firefly FFL-3SLE.mtf +++ b/megameklab/data/mechfiles/mechs/Operation Klondike/Firefly FFL-3SLE.mtf @@ -147,7 +147,7 @@ capabilities: Although it was slow in comparison to other 'Mechs of its weight c deployment:Built by the Star League in Exile at Strana Mechty MechWorks, the 3SLE is almost identical to the original 3A, carrying three Martell medium lasers, four Martell small lasers, and a Coventry Five-Tube LRM-5 for offensive firepower. The only difference is the replacement of the SLDF standard TAG with a Guardian ECM suite. -history:The Firefly, which entered service in the late 27th century, was one of the SLDF's primary light 'Mechs in its later years.Cases occurred in all House forces, but not in the numbers deployed by the SLDF, and all were presumed destroyed by the end of the Second Succession War, save for tales of anomalous examples in the Periphery. The design reappeared with Wolf's Dragoons in the early 31st century, raising eyebrows, yet the secret of the Firefly's origin was revealed when the Dragoons' Clan origins were revealed. In the 3040s, the advent of a small number of Fireflys with the Com Guard forces elicited a similar reaction. +history:The Firefly, which entered service in the late 27th century, was one of the SLDF's primary light 'Mechs in its later years. Cases occurred in all House forces, but not in the numbers deployed by the SLDF, and all were presumed destroyed by the end of the Second Succession War, save for tales of anomalous examples in the Periphery. The design reappeared with Wolf's Dragoons in the early 31st century, raising eyebrows, yet the secret of the Firefly's origin was exposed when the Dragoons' Clan origins were revealed. In the 3040s, the advent of a small number of Fireflys with the Com Guard forces elicited a similar reaction. manufacturer:Strana Mechty MechWorks primaryfactory:Strana Mechty diff --git a/megameklab/data/mechfiles/mechs/Operation Klondike/Griffin GRF-2N.mtf b/megameklab/data/mechfiles/mechs/Operation Klondike/Griffin GRF-2N.mtf index 9eb4cbef3..e08cf7b4d 100644 --- a/megameklab/data/mechfiles/mechs/Operation Klondike/Griffin GRF-2N.mtf +++ b/megameklab/data/mechfiles/mechs/Operation Klondike/Griffin GRF-2N.mtf @@ -147,7 +147,7 @@ capabilities:The massive and efficient fusion engine of the Griffin, giving it a deployment:The SLDF's Royal Griffin was introduced in 2751 and mounted an ER PPC, two SRM-6 launchers, and a Guardian ECM Suite. The heat-sinks were upgraded to double-strength models and the ammo was protected by CASE. To fit all this, the armor was changed to Ferro-Fibrous and the chassis was made of Endo Steel. Disappearing during the Succession Wars until a Jihad era return thanks to the discovery of the New Dallas Memory Core, the Clans also retained a number of original models among their solahma forces. -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. +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. manufacturer:Earthwerks-FWL, Inc.,Norse BattleMech Works,Brigadier Corporation,Earthwerks Incorporated primaryfactory:Keystone,Marduk,Oliver,Terra diff --git a/megameklab/data/mechfiles/mechs/Operation Klondike/Griffin GRF-2N2.mtf b/megameklab/data/mechfiles/mechs/Operation Klondike/Griffin GRF-2N2.mtf index 18df489e2..b974fb8c4 100644 --- a/megameklab/data/mechfiles/mechs/Operation Klondike/Griffin GRF-2N2.mtf +++ b/megameklab/data/mechfiles/mechs/Operation Klondike/Griffin GRF-2N2.mtf @@ -163,7 +163,7 @@ capabilities:The massive and efficient fusion engine of the Griffin, giving it a deployment:The SLDF's Royal Griffin was introduced in 2751 and mounted an ER PPC, two SRM-6 launchers, and a Guardian ECM Suite. The heat-sinks were upgraded to double-strength models and the ammo was protected by CASE. To fit all this, the armor was changed to Ferro-Fibrous and the chassis was made of Endo Steel. Disappearing during the Succession Wars until a Jihad era return thanks to the discovery of the New Dallas Memory Core, the Clans also retained a number of original models among their solahma forces. -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. +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. manufacturer:Earthwerks-FWL, Inc.,Norse BattleMech Works,Brigadier Corporation,Earthwerks Incorporated primaryfactory:Keystone,Marduk,Oliver,Terra systemmanufacturer:CHASSIS:Earthwerks GRF Endo diff --git a/megameklab/data/mechfiles/mechs/Operation Klondike/Highlander HGN-732 Colleen.mtf b/megameklab/data/mechfiles/mechs/Operation Klondike/Highlander HGN-732 Colleen.mtf index 56c6ceac2..474784e64 100644 --- a/megameklab/data/mechfiles/mechs/Operation Klondike/Highlander HGN-732 Colleen.mtf +++ b/megameklab/data/mechfiles/mechs/Operation Klondike/Highlander HGN-732 Colleen.mtf @@ -162,7 +162,7 @@ IS Ferro-Fibrous overview:The Highlander is one of the most well-known Star League Defense Force assault 'Mechs, serving with distinction for almost two centuries since first entering service in 2592. capabilities:Initially designed as a dedicated city and installation defender, the original model featured a variety of weaponry along with fifteen and a half tons of Ferro-Fibrous armor, but perhaps its most useful asset were the three Hildco jump jets giving it a jumping range of 90 meters. The heaviest 'Mech design to feature jump jets at the time, their original task was to allow the Highlander the ability to jump over inconvenient obstacles such as buildings and outpace other 'Mechs with a faster ground speed, but because of this increased mobility and its versatile weaponry the Highlander proved to be a capable fighter on any battlefield and within decades nearly every BattleMech regiment of the Regular and Royal Armies featured them. deployment:This version replaced the standard weaponry with an ER PPC, a prototype Streak SRM-6, twin Medium Pulse Lasers, and a pair of LRM-15 missile launchers. Fourteen double heat sinks keep everything cool. -history:during the design's initial trial runs that pilots began using these 'Mechs in what would infamously become known as the "Highlander Burial". Leaping into the air and landing directly on their enemy, a Highlander could literally drive a light 'Mech into the ground. So successful was this maneuver that the design team re-engineered the legs to withstand repeated death-from-above attacks and turned what had been a desperation move into an art form, giving Highlander pilots an additional psychological edge. As with other Star League era designs the Highlander would suffer the loss of technology brought about by the Succession Wars, and when StarCorps' factory on Son Hoa was devastated towards the end of the Second Succession War the original HGN-732 became virtually extinct. An agreement between StarCorps and Hollis Incorporated to rebuild destroyed chassis from scratch using readily-available technology kept the line going until the mid-3030s when limited production was restarted by StarCorps on Son Hoa and Corey, producing barely a dozen new 'Mechs per year. These HGN-733 Highlanders were used in small numbers by the Capellan Confederation and Lyran Commonwealth, commonly as part of lances containing Exterminators, Victors, Grasshoppers and Catapults. Unbeknownst to many, ComStar also maintained a large stock of Highlanders left over from the Star League, some of which they gifted to the Draconis Combine during the War of 3039. The appearance of so many seemingly rare 733s, along with a few 732s whose advanced technology managed to slip through ComStar screening, had a large impact on Lyran morale during that conflict. ComStar would also use the design in their own military forces, the Com Guard, and even during the Clan Invasion a few original 732s would take to the field as part of the Clans' fighting forces. The Northwind Highlanders especially favored this namesake Battlemech. In fact, during the Succession Wars, they were the only Inner Sphere army to keep a large number of them operational, along with ComStar. The Highlanders are specially skilled in delivering the famed Highlander Burial maneuver. By 3057 StarCorps' Son Hoa line was at full production, producing brand-new original-spec Highlanders for Lyran units of the Federated Commonwealth, just in time to take part in the FedCom Civil War. Highlanders would continue to be produced all the way through to the Jihad, where advanced variants fought both for and against the Word of Blake. +history:During the design's initial trial runs pilots began using these 'Mechs in what would infamously become known as the "Highlander Burial". Leaping into the air and landing directly on their enemy, a Highlander could literally drive a light 'Mech into the ground. So successful was this maneuver that the design team re-engineered the legs to withstand repeated death-from-above attacks and turned what had been a desperation move into an art form, giving Highlander pilots an additional psychological edge. As with other Star League era designs the Highlander would suffer the loss of technology brought about by the Succession Wars, and when StarCorps' factory on Son Hoa was devastated towards the end of the Second Succession War the original HGN-732 became virtually extinct. An agreement between StarCorps and Hollis Incorporated to rebuild destroyed chassis from scratch using readily-available technology kept the line going until the mid-3030s when limited production was restarted by StarCorps on Son Hoa and Corey, producing barely a dozen new 'Mechs per year. These HGN-733 Highlanders were used in small numbers by the Capellan Confederation and Lyran Commonwealth, commonly as part of lances containing Exterminators, Victors, Grasshoppers and Catapults. Unbeknownst to many, ComStar also maintained a large stock of Highlanders left over from the Star League, some of which they gifted to the Draconis Combine during the War of 3039. The appearance of so many seemingly rare 733s, along with a few 732s whose advanced technology managed to slip through ComStar screening, had a large impact on Lyran morale during that conflict. ComStar would also use the design in their own military forces, the Com Guard, and even during the Clan Invasion a few original 732s would take to the field as part of the Clans' fighting forces. The Northwind Highlanders especially favored this namesake Battlemech. In fact, during the Succession Wars, they were the only Inner Sphere army to keep a large number of them operational, along with ComStar. The Highlanders are specially skilled in delivering the famed Highlander Burial maneuver. By 3057 StarCorps' Son Hoa line was at full production, producing brand-new original-spec Highlanders for Lyran units of the Federated Commonwealth, just in time to take part in the FedCom Civil War. Highlanders would continue to be produced all the way through to the Jihad, where advanced variants fought both for and against the Word of Blake. manufacturer:Refit primaryfactory:Refit systemmanufacturer:CHASSIS:Star League XT diff --git a/megameklab/data/mechfiles/mechs/Operation Klondike/Thorn THE-Nb.mtf b/megameklab/data/mechfiles/mechs/Operation Klondike/Thorn THE-Nb.mtf index 7bde9ba42..62930b453 100644 --- a/megameklab/data/mechfiles/mechs/Operation Klondike/Thorn THE-Nb.mtf +++ b/megameklab/data/mechfiles/mechs/Operation Klondike/Thorn THE-Nb.mtf @@ -137,7 +137,7 @@ Endo-Steel overview:The Thorn is a light BattleMech which was originally intended to operate as a scout. -capabilities:Four and a half tons of armor provides the Thorn with good protection, especially when mated with CASE to contain any ammunition explosions. The use of an Endo Steel chassis is what allows the Thorn to carry all of this equipment, an alloy twice as strong as standard materials if somewhat bulky. The GM 120 fusion engine gives the Thorn a respectable cruising speed of 65 km/h but the lack of jump jets further compounds its issues with catching other light 'Mechs. Built with the standard number of ten engine-mounted heat sinks the Thorn is regarded as a "cool running" design, although the placement of the head laser right below the cockpit (despite additional cooling systems) makes repeated firings uncomfortable +capabilities:Four and a half tons of armor provides the Thorn with good protection, especially when mated with CASE to contain any ammunition explosions. The use of an Endo Steel chassis is what allows the Thorn to carry all of this equipment, an alloy twice as strong as standard materials if somewhat bulky. The GM 120 fusion engine gives the Thorn a respectable cruising speed of 65 km/h but the lack of jump jets further compounds its issues with catching other light 'Mechs. Built with the standard number of ten engine-mounted heat sinks the Thorn is regarded as a "cool running" design, although the placement of the head laser right below the cockpit (despite additional cooling systems) makes repeated firings uncomfortable. deployment:The advanced model employed by the Star League Defense Force Royal Divisions in 2743 changed the role of the 'Mech from a missile to an energy boat, replacing the LRM launcher with an ER Large Laser, retaining one medium laser and downgrading the other to a Small Laser. Dropping the no longer required CASE, the 'Mech also used a MASC system for temporary speed bursts and Double Heat Sinks to vent its increased waste heat output. The THE-Nb mounted an XL Engine to save the weight to mount this extra equipment, at the cost of reduced survivability. diff --git a/megameklab/data/mechfiles/mechs/ProtoTypes/Grasshopper GHR-7P.mtf b/megameklab/data/mechfiles/mechs/ProtoTypes/Grasshopper GHR-7P.mtf index efbf2b995..88f7fbfd9 100644 --- a/megameklab/data/mechfiles/mechs/ProtoTypes/Grasshopper GHR-7P.mtf +++ b/megameklab/data/mechfiles/mechs/ProtoTypes/Grasshopper GHR-7P.mtf @@ -164,7 +164,7 @@ capabilities:With great mobility and a predominately shorter-ranged, energy-base deployment:The production version of Arc-Royal MechWorks' GHR-7X prototype, the 7P uses a Torso Mounted Cockpit, Endo Steel skeleton and VOX 280 Light Fusion Engine, and mounts six Leviathan Enhanced Improved Jump Jets. The Type VI Bloodhound Active Probe was also retained. The main difference between the prototype 7X and production 7P, introduced in 3081, is its weaponry: instead of medium pulse lasers and problematic Bombast Lasers, the GHR-7P carries a Maxell X-pulsion Large X-Pulse Laser and an RAMTech 1500Z ER medium laser in each arm while another ER medium is mounted in the head. -history:Problems integrating the original stealth systems with the chassis meant the Grasshopper missed the climactic end to the conflict. The stealth systems were ultimately removed from the final design. The untested and unorthodox 'Mech was distributed primarily to the regular army rather than the more prestigious Royal units, and within four years it could be found in most Star League regiments. Thus as the League dissolved, with the chaos of Operation EXODUS and the defection of many SLDF units to the Successor States, Grasshoppers found their way into the various House armies one way or another. Besides hunting down lighter machines to clear the way for heavier, less-mobile 'Mechs, the Grasshopper's mobility and endurance meant it often spearheaded assaults to storm fortifications, led flanking attacks to hit the enemy from the rear, and served as back-up brawler for companies of light and medium 'Mechs. Its ability to operate independently made it an excellent choice as a raider and guerrilla fighter, an attribute also prized by mercenary units in need of self-reliant 'Mechs. While popular the Grasshopper was also an uncommon sight during the Succession Wars, causing many commanders to mistakenly treat it as just another heavy 'Mech. By the time they realized their mistake it was too late, though following ComStar's publication of Technical Readout: 3025 military leaders became more familiar with the 'Mech. In the midst of the Second Succession War the Lantren Corporation's factory on Bryant was destroyed in 2843, a result of worsening global storms and damage inflicted during the conflict, causing production of the 'Mech to cease. However, the Grasshopper was usually prioritized over other 'Mechs, even a unit commander's own, when it came time to repair and rebuild after a battle. Thus most of the original production run was still in active duty even after centuries of use. Lantren Corporation would eventually introduce a new variant in 3049, the GHR-5J, which upgraded many of its original systems with superior lostech components. Yet the original model was so popular that it would still outnumber the -5J for decades to come by a ratio of three to one. Only when the Draconis Combine introduced their own C3 variant that trend began to reverse. Further variants were introduced in the years following, and the Grasshopper participated in many conflicts, including both sides of the Jihad. +history:Problems integrating the original stealth systems with the chassis meant the Grasshopper missed the climactic end to the conflict. The stealth systems were ultimately removed from the final design. The untested and unorthodox 'Mech was distributed primarily to the regular army rather than the more prestigious Royal units, and within four years it could be found in most Star League regiments. Thus as the League dissolved, with the chaos of Operation EXODUS and the defection of many SLDF units to the Successor States, Grasshoppers found their way into the various House armies one way or another. Besides hunting down lighter machines to clear the way for heavier, less-mobile 'Mechs, the Grasshopper's mobility and endurance meant it often spearheaded assaults to storm fortifications, led flanking attacks to hit the enemy from the rear, and served as back-up brawler for companies of light and medium 'Mechs. Its ability to operate independently made it an excellent choice as a raider and guerrilla fighter, an attribute also prized by mercenary units in need of self-reliant 'Mechs. While popular the Grasshopper was also an uncommon sight during the Succession Wars, causing many commanders to mistakenly treat it as just another heavy 'Mech. By the time they realized their mistake it was too late, though following ComStar's publication of Technical Readout: 3025 military leaders became more familiar with the 'Mech. In the midst of the Second Succession War the Lantren Corporation's factory on Bryant was destroyed in 2843, a result of worsening global storms and damage inflicted during the conflict, causing production of the 'Mech to cease. However, the Grasshopper was usually prioritized over other 'Mechs, even a unit commander's own, when it came time to repair and rebuild after a battle. Thus most of the original production run was still in active duty even after centuries of use. Lantren Corporation would eventually introduce a new variant in 3049, the GHR-5J, which upgraded many of its original systems with superior lostech components. Yet the original model was so popular that it would still outnumber the -5J for decades to come by a ratio of three to one. Only when the Draconis Combine introduced their own C3 variant that trend began to reverse. Further variants were introduced in the years following, and the Grasshopper participated in many conflicts, including both sides of the Jihad. manufacturer:Arc-Royal MechWorks primaryfactory:Arc-Royal diff --git a/megameklab/data/mechfiles/mechs/ProtoTypes/Mad Cat Mk II Enhanced.mtf b/megameklab/data/mechfiles/mechs/ProtoTypes/Mad Cat Mk II Enhanced.mtf index d882763b2..2bc122ac1 100644 --- a/megameklab/data/mechfiles/mechs/ProtoTypes/Mad Cat Mk II Enhanced.mtf +++ b/megameklab/data/mechfiles/mechs/ProtoTypes/Mad Cat Mk II Enhanced.mtf @@ -156,7 +156,7 @@ Clan Endo Steel overview:Designed to be sold to fellow Clans, this rebuild of the Timber Wolf carries thirteen tons of ferro-fibrous armor while being one of most nimble BattleMechs of its class, yet still packing serious weaponry. capabilities:Produced on the Manufacturing Plant DSF-IT1 on Itabaiana. This version uses several Advanced Technology systems to increase its effectiveness on the battlefield. Each arm carries an ER Large Pulse Laser and an ER Medium Laser, while a pair of LRM-10's provide long range firepower. Four jump jets allow the Mad Cat Mk. II Enhanced to cover 120 meters at a time. The top speed of the 'Mech was reduced to 54 km/h, however, due to the use of twenty-five tons of Hardened Armor. This protection, outweighing some 'Mechs, ensures that the Mad Cat Mk. II-Enhanced can continue to fight long after most of its foes have been destroyed. -deployment:Despite this, Mk II's most notable potential buyers, Clan Wolf and Clan Jade Falcon, did not purchase even a single unit, though they won some numbers in Trials. Significant numbers of Mad Cat Mk II were sold to Clan Nova Cat, and the Mech served also in Clan Ice Hellion, Clan Jade Falcon, Clan Wolf-in-Exile in addition to Diamond Shark itself. On a limited basis, Clan Diamond Shark sold unmodified Mad Cat Mk IIs to Inner Sphere factions, most notably the Draconis Combine and Federated Commonwealth, and also the Lyran Alliance bought an unknown amount of Mad Cat Mark IIs. +deployment:Despite this, Mk II's most notable potential buyers, Clan Wolf and Clan Jade Falcon, did not purchase even a single unit, though they won some numbers in Trials. Significant numbers of Mad Cat Mk II were sold to Clan Nova Cat, and the Mech served also in Clan Ice Hellion, Clan Jade Falcon, Clan Wolf-in-Exile in addition to Diamond Shark itself. On a limited basis, Clan Diamond Shark sold unmodified Mad Cat Mk IIs to Inner Sphere factions, most notably the Draconis Combine and Federated Commonwealth, and also the Lyran Alliance bought an unknown amount of Mad Cat Mark IIs. history:The Mad Cat Mk II was in development for fifteen months by the time production began in 3061. The sole rationale for the Mad Cat Mk II was to increase profits for Clan Diamond Shark after war with the Inner Sphere in the 3050s. manufacturer:Manufacturing Plant DSF-94 systemmanufacturer:CHASSIS:DSAM Endo 4 diff --git a/megameklab/data/mechfiles/mechs/ProtoTypes/Wolfhound WLF-2H.mtf b/megameklab/data/mechfiles/mechs/ProtoTypes/Wolfhound WLF-2H.mtf index cc6fd66d0..2f011ded6 100644 --- a/megameklab/data/mechfiles/mechs/ProtoTypes/Wolfhound WLF-2H.mtf +++ b/megameklab/data/mechfiles/mechs/ProtoTypes/Wolfhound WLF-2H.mtf @@ -163,7 +163,7 @@ capabilities:Archon Katrina Steiner directed TharHes Industries to create a Batt deployment:The production model of the WLF-2X, introduced in 3082. To ease production, the Actuator Enhancement System has been removed and replaced by an extra double heat sink, and the laser reflective armor has been replaced by the standard armor available anywhere in the Inner Sphere. The heavy PPC retains the PPC capacitor, and the XL engine retains the supercharger that allows for impressive speed boosts. A pair of ER medium lasers and an ER small laser round out the weapons. -history:The Kell Hounds were the first unit chosen to field-test the Wolfhound in combat because of their intense loyalty to House Steiner, followed shortly after by Wolf's Dragoons. The design was put through its paces during the Fourth Succession War, where it outperformed all expectations. This was especially true when the Wolfhound faced its intended targets, hitting the Jenner beyond its capacity to return fire while closing the distance on the Panther to get inside range of its primary armament. After the war's triumphant conclusion, the Federated Commonwealth purchased more Wolfhounds to outfit its troops, and the design was utilized again during the War of 3039. Wolfhounds sustained substantially fewer deaths than other 'Mechs during that fight, and as a result, only a few were captured by the Combine. While awed by the 'Mech, the Kuritans were too proud to replicate it, instead relying on captured examples to help create the Wolf Trap particularly to defeat the 'Mech. Arc-Royal MechWorks was eventually recruited in to construct Wolfhounds under license from TharHes, and the recovery of lostech owing to the Helm Memory Core allowed for the production of a more advanced model to combat the Clan Invasion. Sadly, it took too long for TharHes' factories to be retooled in order to build the WLF-2 model, which was introduced in 3052, before ComStar ended the invasion with the Battle of Tukayyid. These updated Wolfhounds were still created for both FedCom member states, but once the Lyran Alliance was formed, TharHes manufacturers began creating the newer WLF-3S variant. This new type was only distributed to units loyal to the Lyran state, and so fought on Katherine Steiner-side Davion's during the FedCom Civil War. During the Jihad, the Word of Blake launched a crushing attack on Tharkad, essentially shutting down TharHes' Wolfhound factory line; in response, Arc-Royal expanded production and created the WLF-4 variant to compensate for allied troops combating the Blakists' losses. +history:The Kell Hounds were the first unit chosen to field-test the Wolfhound in combat because of their intense loyalty to House Steiner, followed shortly after by Wolf's Dragoons. The design was put through its paces during the Fourth Succession War, where it outperformed all expectations. This was especially true when the Wolfhound faced its intended targets, hitting the Jenner beyond its capacity to return fire while closing the distance on the Panther to get inside range of its primary armament. After the war's triumphant conclusion, the Federated Commonwealth purchased more Wolfhounds to outfit its troops, and the design was utilized again during the War of 3039. Wolfhounds sustained substantially fewer deaths than other 'Mechs during that fight, and as a result, only a few were captured by the Combine. While awed by the 'Mech, the Kuritans were too proud to replicate it, instead relying on captured examples to help create the Wolf Trap particularly to defeat the 'Mech. Arc-Royal MechWorks was eventually recruited in to construct Wolfhounds under license from TharHes, and the recovery of lostech owing to the Helm Memory Core allowed for the production of a more advanced model to combat the Clan Invasion. Sadly, it took too long for TharHes' factories to be retooled in order to build the WLF-2 model, which was introduced in 3052, before ComStar ended the invasion with the Battle of Tukayyid. These updated Wolfhounds were still created for both FedCom member states, but once the Lyran Alliance was formed, TharHes manufacturers began creating the newer WLF-3S variant. This new type was only distributed to units loyal to the Lyran state, and so fought on Katherine Steiner-Davion's side during the FedCom Civil War. During the Jihad, the Word of Blake launched a crushing attack on Tharkad, essentially shutting down TharHes' Wolfhound factory line; in response, Arc-Royal expanded production and created the WLF-4 variant to compensate for allied troops combating the Blakists' losses. manufacturer:Arc-Royal MechWorks primaryfactory:Arc-Royal diff --git a/megameklab/data/mechfiles/mechs/RS Succession Wars/Atlas AS7-A.mtf b/megameklab/data/mechfiles/mechs/RS Succession Wars/Atlas AS7-A.mtf index 28e555836..6245951b4 100644 --- a/megameklab/data/mechfiles/mechs/RS Succession Wars/Atlas AS7-A.mtf +++ b/megameklab/data/mechfiles/mechs/RS Succession Wars/Atlas AS7-A.mtf @@ -165,7 +165,7 @@ Heat Sink overview:"A 'Mech as powerful as possible, as impenetrable as possible, and as ugly and foreboding as conceivable, so that fear itself will be our ally.”-Aleksandr Kerensky -capabilities:The Atlas is probably the best-known BattleMech to ever set foot on the modern battlefield. Designed with specifications from Aleksandr Kerensky himself in 2755 in the midst of the Cameron Edicts, the Atlas was originally intended to ensure SLDF superiority over the Star League member states. Carrying the largest LRM launcher, the largest autocannon, and the largest SRM launcher possible, the Atlas can deal frightening amounts of damage in short amounts of time. Often used as a command vehicle, the Atlas mounts an advanced antenna and communications array, allowing it to engage in surface-to space communications in real time. The massive 19-ton hide of armor that protects the Atlas makes it a difficult foe to take down. Indeed, most MechWarriors choose to fall back rather than face one head-one, as its lumbering gait mean it can rarely catch up to other 'Mechs that choose to flee it. A full year of development went into crafting the famous "Death's Head" of the 'Mech to achieve the perfect ratio of functionality and fear. The head is also quite roomy and allows a small satellite dish to be mounted for surface-to-space communications. During combat the pilot can easily fold up the dish and store it within a protective portion of the head. +capabilities:The Atlas is probably the best-known BattleMech to ever set foot on the modern battlefield. Designed with specifications from Aleksandr Kerensky himself in 2755 in the midst of the Cameron Edicts, the Atlas was originally intended to ensure SLDF superiority over the Star League member states. Carrying the largest LRM launcher, the largest autocannon, and the largest SRM launcher possible, the Atlas can deal frightening amounts of damage in short amounts of time. Often used as a command vehicle, the Atlas mounts an advanced antenna and communications array, allowing it to engage in surface-to-space communications in real time. The massive 19-ton hide of armor that protects the Atlas makes it a difficult foe to take down. Indeed, most MechWarriors choose to fall back rather than face one head-on, as its lumbering gait means it can rarely catch up to other 'Mechs that choose to flee it. A full year of development went into crafting the famous "Death's Head" of the 'Mech to achieve the perfect ratio of functionality and fear. The head is also quite roomy and allows a small satellite dish to be mounted for surface-to-space communications. During combat the pilot can easily fold up the dish and store it within a protective portion of the head. deployment:This variant of the Atlas replaces the standard weaponry with an LRM-10 and Autocannon/5 in the left torso. At short range, the pilot can use the arm mounted Medium Lasers and capitalize on damaged armor by using the five SRM-6 launchers in the right torso. The autocannon and LRM each have a ton of ammunition while the SRMs receive four tons of ammunition. All the ammunition is carried in the left torso. The armor, ground speed, and heat sinks are identical to the AS7-D. diff --git a/megameklab/data/mechfiles/mechs/RS Succession Wars/Wolverine WVR-6D.mtf b/megameklab/data/mechfiles/mechs/RS Succession Wars/Wolverine WVR-6D.mtf index 69581d168..488ce920d 100644 --- a/megameklab/data/mechfiles/mechs/RS Succession Wars/Wolverine WVR-6D.mtf +++ b/megameklab/data/mechfiles/mechs/RS Succession Wars/Wolverine WVR-6D.mtf @@ -161,7 +161,7 @@ Jump Jet overview:The Wolverine commonly served as a heavy scout unit. Often deployed in situations where heavy opposition could easily destroy lighter BattleMechs, it has had a reliable service record ever since its initial deployment within the Star League Defense Force. With respectable armor, speed, and firepower, it can easily outfight lighter enemy scouts and defend itself capably if ambushed. capabilities:The autocannon, missile system and laser found on most Wolverines are all reliable and well-storied systems. Unfortunately, the jump jets suffer from an opposing reputation; the Northrup 12000's are underpowered and prone to breakdowns. The one defining system to be found on the Wolverine, however, are its superb Tek BattleCom and Garret T11-b communications systems. The comgear, regardless of the manufacturer, is well-shielded and features a multi-channel transmitter and receiver, making the Wolverine a powerful Command BattleMech for scouting formations. deployment:Introduced in 2834, the 6D drops the SRM and one heat sink of the 6R to upgrade the AC/5 to an Autocannon/10, mounted in the left arm. Two tons of ammunition in the left side supply it, spread through the arm and torso. One jump jet is moved from each leg to the corresponding side torso. -history:A widespread part of every major military, the Wolverine has manufacturing plants scattered throughout the entire Inner Sphere. While certain states-notable the Free Worlds League-have larger numbers of the design, only the Capellans began facing a shortage of the Wolverine after the loss of their Nanking facilities. +history:A widespread part of every major military, the Wolverine has manufacturing plants scattered throughout the entire Inner Sphere. While certain states-notably the Free Worlds League-have larger numbers of the design, only the Capellans began facing a shortage of the Wolverine after the loss of their Nanking facilities. manufacturer:Kallon Industries, Victory Industries, Free Worlds Defense Industries primaryfactory:Nanking, Thermopolis (Kallon), Marduk (Victory), Gibson (FWDI) systemmanufacturer:CHASSIS:Crucis-A diff --git a/megameklab/data/mechfiles/mechs/RS Succession Wars/Zeus ZEU-6A.mtf b/megameklab/data/mechfiles/mechs/RS Succession Wars/Zeus ZEU-6A.mtf index cee82f03c..24e0984ad 100644 --- a/megameklab/data/mechfiles/mechs/RS Succession Wars/Zeus ZEU-6A.mtf +++ b/megameklab/data/mechfiles/mechs/RS Succession Wars/Zeus ZEU-6A.mtf @@ -160,7 +160,7 @@ Heat Sink overview:The Zeus was first built by the Lyran Commonwealth in 2787, just as the First Succession War began. Built at the request of Lyran Commonwealth Armed Forces commanders for a new light-assault 'Mech designed to engage the enemy at long range and perform hit-and-run attacks. -capabilities:the Zeus is fast enough to keep up with most heavy 'Mechs, and with a sturdy frame, eleven and a half tons of standard armor and a versatile weapons array, is equally capable of defeating them. Its use of reliable, low-maintenance and easily modified systems at a time when most 'Mechs were built with cutting-edge technology also proved fortuitous, allowing the Zeus to be produced long after those advanced components had become Lostech. +capabilities:The Zeus is fast enough to keep up with most heavy 'Mechs, and with a sturdy frame, eleven and a half tons of standard armor and a versatile weapons array, is equally capable of defeating them. Its use of reliable, low-maintenance and easily modified systems at a time when most 'Mechs were built with cutting-edge technology also proved fortuitous, allowing the Zeus to be produced long after those advanced components had become Lostech. deployment:Introduced in 2940, and an apparent precursor to the 6T, the 6A trades the LRM-15 and two heat sinks for three SRM-6's with one ton of ammunition in the right arm. diff --git a/megameklab/data/mechfiles/mechs/RS Unique/Assassin Alice.mtf b/megameklab/data/mechfiles/mechs/RS Unique/Assassin Alice.mtf index ad70ee070..6d37089c9 100644 --- a/megameklab/data/mechfiles/mechs/RS Unique/Assassin Alice.mtf +++ b/megameklab/data/mechfiles/mechs/RS Unique/Assassin Alice.mtf @@ -144,7 +144,7 @@ Ferro-Fibrous overview:Many military finance experts outside the Star League saw the Assassin as more of a political pork project than a powerful fighting machine, yet it turned out to be a strong 'Mech in combat against light lances. -capabilities:The Assassin was able to destroy these lighter 'Mechs due to its good speed and maneuverability, good armor coverage (in comparison to the 'Mechs it was built to battle against), and strong weaponry. The weapons of the 'Mechs is essentially comprised of three systems: the long-range missile rack, the short-range missile rack, and the arm-mounted Martell midrange laser. The design is limited in durability unless assigned supply units for support because it can only carry a total of seventy-four salvos for both launchers. The most significant disadvantage for most pilots is the incredibly tight cockpit—one of the most confined cockpit designs in the Inner Sphere. +capabilities:The Assassin was able to destroy these lighter 'Mechs due to its good speed and maneuverability, good armor coverage (in comparison to the 'Mechs it was built to battle against), and strong weaponry. The weapons of the 'Mech is essentially comprised of three systems: the long-range missile rack, the short-range missile rack, and the arm-mounted Martell midrange laser. The design is limited in durability unless assigned supply units for support because it can only carry a total of seventy-four salvos for both launchers. The most significant disadvantage for most pilots is the incredibly tight cockpit—one of the most confined cockpit designs in the Inner Sphere. deployment:A customized Assassin created by Lyran MechWarrior Alice Humpterderby of the 24th Lyran Guards. This Assassin was rebuilt with Davion salvage during the FedCom Civil War, and was equipped with seven and a half tons of ferro-fibrous armor, four ER medium lasers split between the torsos and the right arm. The lasers have been connected to a salvaged targeting computer, and a C3 slave computer, a Beagle active probe, and 10 double heat sinks have also been mounted. diff --git a/megameklab/data/mechfiles/mechs/RS Unique/Jenner Samuli.mtf b/megameklab/data/mechfiles/mechs/RS Unique/Jenner Samuli.mtf index 1a420299f..e8f2f69b7 100644 --- a/megameklab/data/mechfiles/mechs/RS Unique/Jenner Samuli.mtf +++ b/megameklab/data/mechfiles/mechs/RS Unique/Jenner Samuli.mtf @@ -143,7 +143,7 @@ capabilities:Five Smithson Lifter jump jets, two in each side torso and one in t deployment:A customized Jenner for MechWarrior Samuli Rinne, which is in the service of House Kurita. The 'Mech's engine was upgraded with a 245 rated XL Engine and 3.5 tons of Ferro-Fibrous Armor. By removing the standard SRM launcher, DCMS techs freed enough room to add CASE and a single LRM-15 with two tons of ammunition. Rinne's Jenner keeps the standard complement of Medium Lasers. -history:The Jenner became the standard light warhorse of the DCMS with the outbreak of the First Succession War, though its reputation would be forever tarnished following its role in the Kentares Massacre. The Jenner became the standard light warhorse of the DCMS with the outbreak of the First Succession War, though its reputation would be forever tarnished following its role in the Kentares Massacre. Construction of new Jenners continued at Diplan MechYard's factory on Ozawa until a raw mineral shortage caused a halt in 2815, though they continued to produce new chassis. In 2823 production resumed on Ozawa, with some three thousand chassis shipped to Diplan's subsidiary on Luthien for final assembly, which itself was retooling to begin full-scale production; by 2830 both production lines were producing 1,350 Jenners a year. The sheer destruction of the Succession Wars finally took their toll when the last Jenner factory was destroyed in 2848, though so many Jenners had been produced by then that nearly every DCMS battalion had at least one of these 'Mechs well into the War of 3039. While the other Successor States eventually managed to procure operational Jenners (every AFFS regiment along the Combine border had at least one), the design remained in predominant use by House Kurita. +history:Construction of new Jenners continued at Diplan MechYard's factory on Ozawa until a raw mineral shortage caused a halt in 2815, though they continued to produce new chassis. In 2823 production resumed on Ozawa, with some three thousand chassis shipped to Diplan's subsidiary on Luthien for final assembly, which itself was retooling to begin full-scale production; by 2830 both production lines were producing 1,350 Jenners a year. The sheer destruction of the Succession Wars finally took their toll when the last Jenner factory was destroyed in 2848, though so many Jenners had been produced by then that nearly every DCMS battalion had at least one of these 'Mechs well into the War of 3039. While the other Successor States eventually managed to procure operational Jenners (every AFFS regiment along the Combine border had at least one), the design remained in predominant use by House Kurita. manufacturer:Luthien Armor Works, Diplan 'Mechyards, Luthien Armor Works, Luthien Armor Works, Diplan 'Mechyards primaryfactory:Luthien, Abiy Adi, New Samarkand, Ozawa diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 1/Grasshopper GHR-8K.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 1/Grasshopper GHR-8K.mtf index da3862321..a926ef291 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 1/Grasshopper GHR-8K.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 1/Grasshopper GHR-8K.mtf @@ -164,7 +164,7 @@ capabilities:With great mobility and a predominately shorter-ranged, energy-base deployment:Eschewing the advanced electronics of other recent models, the GHR-8K is a return to the Grasshopper's roots, combining 7K's Light PPCs with the 5H's weapon layout. Mounting an Light PPC in each arm and side torso, supported by a center torso mounted ER Large Laser, made possible by an Endo Steel skeleton and double heat sinks, the return of the 5H's head-mounted LRM-5 rack is a curious choice even with a single ton of reloads in a CASE II protected ammo bin. -history:Problems integrating the original stealth systems with the chassis meant the Grasshopper missed the climactic end to the conflict. The stealth systems were ultimately removed from the final design. The untested and unorthodox 'Mech was distributed primarily to the regular army rather than the more prestigious Royal units, and within four years it could be found in most Star League regiments. Thus as the League dissolved, with the chaos of Operation EXODUS and the defection of many SLDF units to the Successor States, Grasshoppers found their way into the various House armies one way or another. Besides hunting down lighter machines to clear the way for heavier, less-mobile 'Mechs, the Grasshopper's mobility and endurance meant it often spearheaded assaults to storm fortifications, led flanking attacks to hit the enemy from the rear, and served as back-up brawler for companies of light and medium 'Mechs. Its ability to operate independently made it an excellent choice as a raider and guerrilla fighter, an attribute also prized by mercenary units in need of self-reliant 'Mechs. While popular the Grasshopper was also an uncommon sight during the Succession Wars, causing many commanders to mistakenly treat it as just another heavy 'Mech. By the time they realized their mistake it was too late, though following ComStar's publication of Technical Readout: 3025 military leaders became more familiar with the 'Mech. In the midst of the Second Succession War the Lantren Corporation's factory on Bryant was destroyed in 2843, a result of worsening global storms and damage inflicted during the conflict, causing production of the 'Mech to cease. However, the Grasshopper was usually prioritized over other 'Mechs, even a unit commander's own, when it came time to repair and rebuild after a battle. Thus most of the original production run was still in active duty even after centuries of use. Lantren Corporation would eventually introduce a new variant in 3049, the GHR-5J, which upgraded many of its original systems with superior lostech components. Yet the original model was so popular that it would still outnumber the -5J for decades to come by a ratio of three to one. Only when the Draconis Combine introduced their own C3 variant that trend began to reverse. Further variants were introduced in the years following, and the Grasshopper participated in many conflicts, including both sides of the Jihad. +history:Problems integrating the original stealth systems with the chassis meant the Grasshopper missed the climactic end to the conflict. The stealth systems were ultimately removed from the final design. The untested and unorthodox 'Mech was distributed primarily to the regular army rather than the more prestigious Royal units, and within four years it could be found in most Star League regiments. Thus as the League dissolved, with the chaos of Operation EXODUS and the defection of many SLDF units to the Successor States, Grasshoppers found their way into the various House armies one way or another. Besides hunting down lighter machines to clear the way for heavier, less-mobile 'Mechs, the Grasshopper's mobility and endurance meant it often spearheaded assaults to storm fortifications, led flanking attacks to hit the enemy from the rear, and served as back-up brawler for companies of light and medium 'Mechs. Its ability to operate independently made it an excellent choice as a raider and guerrilla fighter, an attribute also prized by mercenary units in need of self-reliant 'Mechs. While popular the Grasshopper was also an uncommon sight during the Succession Wars, causing many commanders to mistakenly treat it as just another heavy 'Mech. By the time they realized their mistake it was too late, though following ComStar's publication of Technical Readout: 3025 military leaders became more familiar with the 'Mech. In the midst of the Second Succession War the Lantren Corporation's factory on Bryant was destroyed in 2843, a result of worsening global storms and damage inflicted during the conflict, causing production of the 'Mech to cease. However, the Grasshopper was usually prioritized over other 'Mechs, even a unit commander's own, when it came time to repair and rebuild after a battle. Thus most of the original production run was still in active duty even after centuries of use. Lantren Corporation would eventually introduce a new variant in 3049, the GHR-5J, which upgraded many of its original systems with superior lostech components. Yet the original model was so popular that it would still outnumber the -5J for decades to come by a ratio of three to one. Only when the Draconis Combine introduced their own C3 variant that trend began to reverse. Further variants were introduced in the years following, and the Grasshopper participated in many conflicts, including both sides of the Jihad. manufacturer:LexaTech Industries primaryfactory:Hun Ho diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 1/Griffin C.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 1/Griffin C.mtf index 0b3df7725..613c63ff0 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 1/Griffin C.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 1/Griffin C.mtf @@ -151,7 +151,7 @@ Improved Jump Jet overview:Built in 2492 the Griffin was originally classified as a heavy BattleMech, filling in the weight gap between mammoth machines like the Mackie and smaller recon 'Mechs like the Wasp, and intended for close assaults 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 primary weapon on the Griffin is a Fusigon PPC in the right arm. The PPC allows the Griffin to work in a long-range fire support role and is backed up by a Delta Dart LRM-10 launcher mounted in a drum over the right shoulder. The LRM launcher also gives the Griffin some indirect fire support capabilities and the two tons of reloads in the right torso allows for good endurance. The Achilles' heel of the design is its lack of short-range weapons, for when an enemy is capable of closing ranges and engaging in close quarters combat, and the fact that all of its weapons are located on the right side. The 'Mech is however equipped with two powerful battle fists for hand-to-hand combat. -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.[5] 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. +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. manufacturer:Earthwerks-FWL, Inc, Refit primaryfactory:Keystone, Various systemmanufacturer:CHASSIS:Earthwerks GRF Endo Steel diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 1/Griffin GRF-1RG.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 1/Griffin GRF-1RG.mtf index 8e8491019..06201a425 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 1/Griffin GRF-1RG.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 1/Griffin GRF-1RG.mtf @@ -165,7 +165,7 @@ Heat Sink overview:Built in 2492 the Griffin was originally classified as a heavy BattleMech, filling in the weight gap between mammoth machines like the Mackie and smaller recon 'Mechs like the Wasp, and intended for close assaults 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:No information on this variant -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. +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. manufacturer:Defiance Industries primaryfactory:Hesperus II systemmanufacturer:CHASSIS:Earthwerks GRF diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 1/Griffin GRF-3RG.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 1/Griffin GRF-3RG.mtf index 56ca90aa1..12e8a895c 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 1/Griffin GRF-3RG.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 1/Griffin GRF-3RG.mtf @@ -165,7 +165,7 @@ Foot Actuator overview:Built in 2492 the Griffin was originally classified as a heavy BattleMech, filling in the weight gap between mammoth machines like the Mackie and smaller recon 'Mechs like the Wasp, and intended for close assaults 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:No information on this variant -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. +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. manufacturer:Defiance Industries primaryfactory:Hesperus II systemmanufacturer:CHASSIS:Earthwerks GRF diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 1/Griffin GRF-6R.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 1/Griffin GRF-6R.mtf index a1014f691..d37685f47 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 1/Griffin GRF-6R.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 1/Griffin GRF-6R.mtf @@ -158,7 +158,7 @@ IS Stealth overview:Built in 2492 the Griffin was originally classified as a heavy BattleMech, filling in the weight gap between mammoth machines like the Mackie and smaller recon 'Mechs like the Wasp, and intended for close assaults 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:No Information on this variant -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. +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. manufacturer:Earthwerks-FWL, Inc.,Brigadier Corporation primaryfactory:Keystone,Oliver systemmanufacturer:CHASSIS:Earthwerks GRF diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 1/Loki (Hellbringer) J.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 1/Loki (Hellbringer) J.mtf index 2c922c430..5ad54e962 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 1/Loki (Hellbringer) J.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 1/Loki (Hellbringer) J.mtf @@ -162,7 +162,7 @@ overview:The Hellbringer is a very widespread design developed by Clan Hell's Ho capabilities:A highly mobile scout unit, the Loki J is carries an Ultra AC/5 and ER PPC in its arms supported by twin ER Medium Lasers in each torso and a Streak SRM-4 rack. Fitted with Jump Jets, the J also mounts an Anti-Missile System and an Active Probe, each ammo-dependant weapon carrying a single ton of reloads. -history:The Inner Sphere first encountered the Hellbringer facing Clan Jade Falcon, which favors the design for its immense offensive potential. Earning the codename Loki by Galen Cox, an AFFC officer who declared each of the Hellbringer's various versions as an "utterly mad configuration," the 'Mech does at first glance appear to be highly unusual, mounting a spread of weapons, anti-personnel equipment and electronics. The Hellbringer utilizes a standard internal structure, and has decent mobility, with a top speed of 86.4 km/h. Though it has vast firepower at its disposal, the design is not particularly durable, mounting a mere eight tons of Standard armor, and the Hellbringer is not particularly suitable for defensive situations or extended engagements. In the aftermath of the Battle of Tokasha and the loss of Tokasha Mechworks, the Hell's Horses began developing several OmniMechs. Only the Hellbringer met with success. Development time for the Hellbringer was reduced through the use of modules used in the Summoner. Despite the poor armor, the Hellbringer devotes almost 43% of its mass to pods, allowing for great offensive potential. The design spread quickly after its introduction for two reasons: the Horses promptly lost the primary production facility, and used their remaining production to curry favor with other Clans through trade and gifts. After The Wars of Reaving in Clan Space, the Hellbringer would fall out of favor with the surviving Home Clans due in part to its association with the Inner Sphere based Clans. The design would be replaced by the Ebon Jaguar in military service of those in Clan Space, with the exception of Clan Coyote which still fields the 'Mech.[9] Even after the introduction of the updated and upgraded Loki II successor design in 3121, Clan Jade Falcon would continue to produce the cheap and easy to manufacture original version on Sudeten during the Dark Age era, with disgraced, solahma or even just overly aggressive warriors still finding its offense over defense focus desirable. +history:The Inner Sphere first encountered the Hellbringer facing Clan Jade Falcon, which favors the design for its immense offensive potential. Earning the codename Loki by Galen Cox, an AFFC officer who declared each of the Hellbringer's various versions as an "utterly mad configuration," the 'Mech does at first glance appear to be highly unusual, mounting a spread of weapons, anti-personnel equipment and electronics. The Hellbringer utilizes a standard internal structure, and has decent mobility, with a top speed of 86.4 km/h. Though it has vast firepower at its disposal, the design is not particularly durable, mounting a mere eight tons of Standard armor, and the Hellbringer is not particularly suitable for defensive situations or extended engagements. In the aftermath of the Battle of Tokasha and the loss of Tokasha Mechworks, the Hell's Horses began developing several OmniMechs. Only the Hellbringer met with success. Development time for the Hellbringer was reduced through the use of modules used in the Summoner. Despite the poor armor, the Hellbringer devotes almost 43% of its mass to pods, allowing for great offensive potential. The design spread quickly after its introduction for two reasons: the Horses promptly lost the primary production facility, and used their remaining production to curry favor with other Clans through trade and gifts. After The Wars of Reaving in Clan Space, the Hellbringer would fall out of favor with the surviving Home Clans due in part to its association with the Inner Sphere based Clans. The design would be replaced by the Ebon Jaguar in military service of those in Clan Space, with the exception of Clan Coyote which still fields the 'Mech. Even after the introduction of the updated and upgraded Loki II successor design in 3121, Clan Jade Falcon would continue to produce the cheap and easy to manufacture original version on Sudeten during the Dark Age era, with disgraced, solahma or even just overly aggressive warriors still finding its offense over defense focus desirable. manufacturer:Various, Olivetti Weaponry primaryfactory:Various, Sudeten systemmanufacturer:CHASSIS:T-E H65 Standard diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 1/Loki (Hellbringer) T.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 1/Loki (Hellbringer) T.mtf index 64a7034b3..77768ac38 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 1/Loki (Hellbringer) T.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 1/Loki (Hellbringer) T.mtf @@ -163,7 +163,7 @@ overview:The Hellbringer is a very widespread design developed by Clan Hell's Ho capabilities:A Dark Ages refinement of the Prime, the T configuration mounts an ER PPC in each arm supported by a shoulder mounted ATM-6, a trio of ER Medium Lasers and twin Anti-Personnel Gauss Rifles. Protected by an Anti-Missile System and CASE II for the two tons of ATM missiles and single ton each of AP Gauss and AMS ammo, the remaining weight is devoted to double heat sinks. -history:The Inner Sphere first encountered the Hellbringer facing Clan Jade Falcon, which favors the design for its immense offensive potential. Earning the codename Loki by Galen Cox, an AFFC officer who declared each of the Hellbringer's various versions as an "utterly mad configuration," the 'Mech does at first glance appear to be highly unusual, mounting a spread of weapons, anti-personnel equipment and electronics. The Hellbringer utilizes a standard internal structure, and has decent mobility, with a top speed of 86.4 km/h. Though it has vast firepower at its disposal, the design is not particularly durable, mounting a mere eight tons of Standard armor, and the Hellbringer is not particularly suitable for defensive situations or extended engagements. In the aftermath of the Battle of Tokasha and the loss of Tokasha Mechworks, the Hell's Horses began developing several OmniMechs. Only the Hellbringer met with success. Development time for the Hellbringer was reduced through the use of modules used in the Summoner. Despite the poor armor, the Hellbringer devotes almost 43% of its mass to pods, allowing for great offensive potential. The design spread quickly after its introduction for two reasons: the Horses promptly lost the primary production facility, and used their remaining production to curry favor with other Clans through trade and gifts. After The Wars of Reaving in Clan Space, the Hellbringer would fall out of favor with the surviving Home Clans due in part to its association with the Inner Sphere based Clans. The design would be replaced by the Ebon Jaguar in military service of those in Clan Space, with the exception of Clan Coyote which still fields the 'Mech.[9] Even after the introduction of the updated and upgraded Loki II successor design in 3121, Clan Jade Falcon would continue to produce the cheap and easy to manufacture original version on Sudeten during the Dark Age era, with disgraced, solahma or even just overly aggressive warriors still finding its offense over defense focus desirable. +history:The Inner Sphere first encountered the Hellbringer facing Clan Jade Falcon, which favors the design for its immense offensive potential. Earning the codename Loki by Galen Cox, an AFFC officer who declared each of the Hellbringer's various versions as an "utterly mad configuration," the 'Mech does at first glance appear to be highly unusual, mounting a spread of weapons, anti-personnel equipment and electronics. The Hellbringer utilizes a standard internal structure, and has decent mobility, with a top speed of 86.4 km/h. Though it has vast firepower at its disposal, the design is not particularly durable, mounting a mere eight tons of Standard armor, and the Hellbringer is not particularly suitable for defensive situations or extended engagements. In the aftermath of the Battle of Tokasha and the loss of Tokasha Mechworks, the Hell's Horses began developing several OmniMechs. Only the Hellbringer met with success. Development time for the Hellbringer was reduced through the use of modules used in the Summoner. Despite the poor armor, the Hellbringer devotes almost 43% of its mass to pods, allowing for great offensive potential. The design spread quickly after its introduction for two reasons: the Horses promptly lost the primary production facility, and used their remaining production to curry favor with other Clans through trade and gifts. After The Wars of Reaving in Clan Space, the Hellbringer would fall out of favor with the surviving Home Clans due in part to its association with the Inner Sphere based Clans. The design would be replaced by the Ebon Jaguar in military service of those in Clan Space, with the exception of Clan Coyote which still fields the 'Mech. Even after the introduction of the updated and upgraded Loki II successor design in 3121, Clan Jade Falcon would continue to produce the cheap and easy to manufacture original version on Sudeten during the Dark Age era, with disgraced, solahma or even just overly aggressive warriors still finding its offense over defense focus desirable. manufacturer:Various, Olivetti Weaponry primaryfactory:Various, Sudeten systemmanufacturer:CHASSIS:T-E H65 Standard diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 10/Archer (Wolf).mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 10/Archer (Wolf).mtf index 76977bbc3..03b1bc5ac 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 10/Archer (Wolf).mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 10/Archer (Wolf).mtf @@ -163,7 +163,7 @@ CLDoubleHeatSink overview:One of the most iconic BattleMechs is the Archer, with its low-slung torso, enormous fists, and missile-bay covers. The Archer was first manufactured in 2474 for heavy-hitting, long-range brawling, and fire-support. -capabilities:Two enormous missile launchers with tons of ammo power the Archer. The missiles were formidable, but their short-range inaccuracy required four medium lasers, two rear-facing and one in each arm. Enlarged hand actuators allow the design to undertake severe physical attacks and transport captured supplies during raids. The cockpit of the Archer situated beneath the center midsection, giving the pilot a unique battlefield view. The torso armor belt above the cockpit protects the gyro and engine from the superior armor. Many pilots initially entered battle with their missile bays locked to hide the 'Mech's real capabilities, leading some to believe it was a close-combat design. As the Archer became famous, this pretext became meaningless. Archer pilots rarely learn new skills, but this hasn't tarnished the 'Mech's reputation. +capabilities:Two enormous missile launchers with tons of ammo power the Archer. The missiles were formidable, but their short-range inaccuracy required four medium lasers, two rear-facing and one in each arm. Enlarged hand actuators allow the design to undertake severe physical attacks and transport captured supplies during raids. The cockpit of the Archer is situated beneath the center midsection, giving the pilot a unique battlefield view. The torso armor belt above the cockpit protects the gyro and engine from the superior armor. Many pilots initially entered battle with their missile bays locked to hide the 'Mech's real capabilities, leading some to believe it was a close-combat design. As the Archer became famous, this pretext became meaningless. Archer pilots rarely learn new skills, but this hasn't tarnished the 'Mech's reputation. deployment:Originally an ARC-2W, this Archer was rebuilt with Clan-spec equipment. The arms mounted ER Large Lasers, while a pair of Small Pulse Lasers covered the rear. The LRM-20s were enhanced with Artemis IV Fire Control Systems, and an ECM Suite and AMS protected against incoming fire. CASE was carried in each side torso and fifteen double heat sinks kept the 'Mech cool. Following Wolf's death, piloting this machine became an honor given to top Dragoon cadets during ceremonies. diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 10/Archer ARC-2Rb.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 10/Archer ARC-2Rb.mtf index 525f5d36c..6c91b3e9a 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 10/Archer ARC-2Rb.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 10/Archer ARC-2Rb.mtf @@ -161,7 +161,7 @@ Foot Actuator overview:One of the most iconic BattleMechs is the Archer, with its low-slung torso, enormous fists, and missile-bay covers. The Archer was first manufactured in 2474 for heavy-hitting, long-range brawling, and fire-support. -capabilities:Two enormous missile launchers with tons of ammo power the Archer. The missiles were formidable, but their short-range inaccuracy required four medium lasers, two rear-facing and one in each arm. Enlarged hand actuators allow the design to undertake severe physical attacks and transport captured supplies during raids. The cockpit of the Archer situated beneath the center midsection, giving the pilot a unique battlefield view. The torso armor belt above the cockpit protects the gyro and engine from the superior armor. Many pilots initially entered battle with their missile bays locked to hide the 'Mech's real capabilities, leading some to believe it was a close-combat design. As the Archer became famous, this pretext became meaningless. Archer pilots rarely learn new skills, but this hasn't tarnished the 'Mech's reputation. +capabilities:Two enormous missile launchers with tons of ammo power the Archer. The missiles were formidable, but their short-range inaccuracy required four medium lasers, two rear-facing and one in each arm. Enlarged hand actuators allow the design to undertake severe physical attacks and transport captured supplies during raids. The cockpit of the Archer is situated beneath the center midsection, giving the pilot a unique battlefield view. The torso armor belt above the cockpit protects the gyro and engine from the superior armor. Many pilots initially entered battle with their missile bays locked to hide the 'Mech's real capabilities, leading some to believe it was a close-combat design. As the Archer became famous, this pretext became meaningless. Archer pilots rarely learn new skills, but this hasn't tarnished the 'Mech's reputation. deployment:Equipped with Star League technology, the 2Rb variant of the Archer was built for SLDF Royal units starting in 2752. Built on an Endo Steel internal structure, this variant dropped one of the rear-firing medium lasers and one ton of ammunition to equip the LRM-20s with Artemis IV fire control systems and CASE. The 2Rb also used ten double heat sinks to keep the 'Mech cool. diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 10/Archer ARC-4M.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 10/Archer ARC-4M.mtf index 7d412efb1..df0076bfa 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 10/Archer ARC-4M.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 10/Archer ARC-4M.mtf @@ -162,7 +162,7 @@ Foot Actuator overview:One of the most iconic BattleMechs is the Archer, with its low-slung torso, enormous fists, and missile-bay covers. The Archer was first manufactured in 2474 for heavy-hitting, long-range brawling, and fire-support. -capabilities:Two enormous missile launchers with tons of ammo power the Archer. The missiles were formidable, but their short-range inaccuracy required four medium lasers, two rear-facing and one in each arm. Enlarged hand actuators allow the design to undertake severe physical attacks and transport captured supplies during raids. The cockpit of the Archer situated beneath the center midsection, giving the pilot a unique battlefield view. The torso armor belt above the cockpit protects the gyro and engine from the superior armor. Many pilots initially entered battle with their missile bays locked to hide the 'Mech's real capabilities, leading some to believe it was a close-combat design. As the Archer became famous, this pretext became meaningless. Archer pilots rarely learn new skills, but this hasn't tarnished the 'Mech's reputation. +capabilities:Two enormous missile launchers with tons of ammo power the Archer. The missiles were formidable, but their short-range inaccuracy required four medium lasers, two rear-facing and one in each arm. Enlarged hand actuators allow the design to undertake severe physical attacks and transport captured supplies during raids. The cockpit of the Archer is situated beneath the center midsection, giving the pilot a unique battlefield view. The torso armor belt above the cockpit protects the gyro and engine from the superior armor. Many pilots initially entered battle with their missile bays locked to hide the 'Mech's real capabilities, leading some to believe it was a close-combat design. As the Archer became famous, this pretext became meaningless. Archer pilots rarely learn new skills, but this hasn't tarnished the 'Mech's reputation. deployment:An upgrade using rediscovered Star League technology, the 4M was built on Calloway VI by Earthwerks in 3049 for the Free Worlds League. It used an Earthwerk Archer II Endo Steel chassis to free up weight for a number of improvements. It carried an additional half-ton of Maximillian 100 armor and utilized ten double heat sinks for added heat dissipation capabilities. The 'Mech also upgraded its twin Doombud LRM-20 launchers by adding Artemis IV fire control systems to the launchers and incorporated CASE to protect the four tons of missile ammo. diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 10/Archer ARC-4M2.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 10/Archer ARC-4M2.mtf index 8c150fa0f..0a2a5da27 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 10/Archer ARC-4M2.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 10/Archer ARC-4M2.mtf @@ -162,7 +162,7 @@ Foot Actuator overview:One of the most iconic BattleMechs is the Archer, with its low-slung torso, enormous fists, and missile-bay covers. The Archer was first manufactured in 2474 for heavy-hitting, long-range brawling, and fire-support. -capabilities:Two enormous missile launchers with tons of ammo power the Archer. The missiles were formidable, but their short-range inaccuracy required four medium lasers, two rear-facing and one in each arm. Enlarged hand actuators allow the design to undertake severe physical attacks and transport captured supplies during raids. The cockpit of the Archer situated beneath the center midsection, giving the pilot a unique battlefield view. The torso armor belt above the cockpit protects the gyro and engine from the superior armor. Many pilots initially entered battle with their missile bays locked to hide the 'Mech's real capabilities, leading some to believe it was a close-combat design. As the Archer became famous, this pretext became meaningless. Archer pilots rarely learn new skills, but this hasn't tarnished the 'Mech's reputation. +capabilities:Two enormous missile launchers with tons of ammo power the Archer. The missiles were formidable, but their short-range inaccuracy required four medium lasers, two rear-facing and one in each arm. Enlarged hand actuators allow the design to undertake severe physical attacks and transport captured supplies during raids. The cockpit of the Archer is situated beneath the center midsection, giving the pilot a unique battlefield view. The torso armor belt above the cockpit protects the gyro and engine from the superior armor. Many pilots initially entered battle with their missile bays locked to hide the 'Mech's real capabilities, leading some to believe it was a close-combat design. As the Archer became famous, this pretext became meaningless. Archer pilots rarely learn new skills, but this hasn't tarnished the 'Mech's reputation. deployment:A simple upgrade to the ARC-4M, this version trades the medium lasers for extended-range versions. diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 10/Archer ARC-5R.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 10/Archer ARC-5R.mtf index 5d791c442..87dc1b2d7 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 10/Archer ARC-5R.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 10/Archer ARC-5R.mtf @@ -160,7 +160,7 @@ Foot Actuator overview:One of the most iconic BattleMechs is the Archer, with its low-slung torso, enormous fists, and missile-bay covers. The Archer was first manufactured in 2474 for heavy-hitting, long-range brawling, and fire-support. -capabilities:Two enormous missile launchers with tons of ammo power the Archer. The missiles were formidable, but their short-range inaccuracy required four medium lasers, two rear-facing and one in each arm. Enlarged hand actuators allow the design to undertake severe physical attacks and transport captured supplies during raids. The cockpit of the Archer situated beneath the center midsection, giving the pilot a unique battlefield view. The torso armor belt above the cockpit protects the gyro and engine from the superior armor. Many pilots initially entered battle with their missile bays locked to hide the 'Mech's real capabilities, leading some to believe it was a close-combat design. As the Archer became famous, this pretext became meaningless. Archer pilots rarely learn new skills, but this hasn't tarnished the 'Mech's reputation. +capabilities:Two enormous missile launchers with tons of ammo power the Archer. The missiles were formidable, but their short-range inaccuracy required four medium lasers, two rear-facing and one in each arm. Enlarged hand actuators allow the design to undertake severe physical attacks and transport captured supplies during raids. The cockpit of the Archer is situated beneath the center midsection, giving the pilot a unique battlefield view. The torso armor belt above the cockpit protects the gyro and engine from the superior armor. Many pilots initially entered battle with their missile bays locked to hide the 'Mech's real capabilities, leading some to believe it was a close-combat design. As the Archer became famous, this pretext became meaningless. Archer pilots rarely learn new skills, but this hasn't tarnished the 'Mech's reputation. deployment:Built by the GKT Enterprise factory on Satalice for the Free Rasalhague Republic, the 5R was introduced in 3050 and bore similarities to the 2K model of the Archer. It carried a pair of FarFire LRM-15 launchers but mounted two Victory Nickel Alloy ER Large Lasers, one in either arm, in place of the medium lasers. It also linked Artemis IV fire control systems to the launchers and utilized twelve double heat sinks to improve waste heat dissipation. Despite being built around an Endo-Steel chassis, these improvements necessitated a decrease in armor protection by two tons. diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 10/Archer ARC-5S.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 10/Archer ARC-5S.mtf index 843b8a518..29d27516d 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 10/Archer ARC-5S.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 10/Archer ARC-5S.mtf @@ -165,7 +165,7 @@ Foot Actuator overview:One of the most iconic BattleMechs is the Archer, with its low-slung torso, enormous fists, and missile-bay covers. The Archer was first manufactured in 2474 for heavy-hitting, long-range brawling, and fire-support. -capabilities:Two enormous missile launchers with tons of ammo power the Archer. The missiles were formidable, but their short-range inaccuracy required four medium lasers, two rear-facing and one in each arm. Enlarged hand actuators allow the design to undertake severe physical attacks and transport captured supplies during raids. The cockpit of the Archer situated beneath the center midsection, giving the pilot a unique battlefield view. The torso armor belt above the cockpit protects the gyro and engine from the superior armor. Many pilots initially entered battle with their missile bays locked to hide the 'Mech's real capabilities, leading some to believe it was a close-combat design. As the Archer became famous, this pretext became meaningless. Archer pilots rarely learn new skills, but this hasn't tarnished the 'Mech's reputation. +capabilities:Two enormous missile launchers with tons of ammo power the Archer. The missiles were formidable, but their short-range inaccuracy required four medium lasers, two rear-facing and one in each arm. Enlarged hand actuators allow the design to undertake severe physical attacks and transport captured supplies during raids. The cockpit of the Archer is situated beneath the center midsection, giving the pilot a unique battlefield view. The torso armor belt above the cockpit protects the gyro and engine from the superior armor. Many pilots initially entered battle with their missile bays locked to hide the 'Mech's real capabilities, leading some to believe it was a close-combat design. As the Archer became famous, this pretext became meaningless. Archer pilots rarely learn new skills, but this hasn't tarnished the 'Mech's reputation. deployment:The 5S variant of the Archer, built out of Defiance Industries' massive Hesperus II complex in 3050, was the official variant for the Armed Forces of the Federated Commonwealth. The 5S upgraded the engine to an Edasich Motors 280 XL engine, cutting the engine's weight in half while retaining the same speed profile. The 5S also reduced the LRM-20 launchers to Coventry Star Fire LRM-15s. This saved weight was used to add two Coventry T4H Streak SRM-2 launchers, one in each arm and fed by two tons of reloads in the side torsos. They also upgraded the four medium lasers to medium pulse lasers. Finally, the 'Mech carried a Doering Electronics Glowworm Narc Missile Beacon launcher in its left torso along with one ton of ammo. This allowed the Archer to tag enemy units with a beacon so that friendly 'Mechs could more easily hit the unit with their own missile weapons. All of the ammunition carried by the 5S was protected by CASE. diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 10/Archer ARC-5W.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 10/Archer ARC-5W.mtf index 014c87476..ed3e9d58d 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 10/Archer ARC-5W.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 10/Archer ARC-5W.mtf @@ -161,7 +161,7 @@ Foot Actuator overview:One of the most iconic BattleMechs is the Archer, with its low-slung torso, enormous fists, and missile-bay covers. The Archer was first manufactured in 2474 for heavy-hitting, long-range brawling, and fire-support. -capabilities:Two enormous missile launchers with tons of ammo power the Archer. The missiles were formidable, but their short-range inaccuracy required four medium lasers, two rear-facing and one in each arm. Enlarged hand actuators allow the design to undertake severe physical attacks and transport captured supplies during raids. The cockpit of the Archer situated beneath the center midsection, giving the pilot a unique battlefield view. The torso armor belt above the cockpit protects the gyro and engine from the superior armor. Many pilots initially entered battle with their missile bays locked to hide the 'Mech's real capabilities, leading some to believe it was a close-combat design. As the Archer became famous, this pretext became meaningless. Archer pilots rarely learn new skills, but this hasn't tarnished the 'Mech's reputation. +capabilities:Two enormous missile launchers with tons of ammo power the Archer. The missiles were formidable, but their short-range inaccuracy required four medium lasers, two rear-facing and one in each arm. Enlarged hand actuators allow the design to undertake severe physical attacks and transport captured supplies during raids. The cockpit of the Archer is situated beneath the center midsection, giving the pilot a unique battlefield view. The torso armor belt above the cockpit protects the gyro and engine from the superior armor. Many pilots initially entered battle with their missile bays locked to hide the 'Mech's real capabilities, leading some to believe it was a close-combat design. As the Archer became famous, this pretext became meaningless. Archer pilots rarely learn new skills, but this hasn't tarnished the 'Mech's reputation. deployment:The 5W was an upgrade of the 2W variant, and was produced for Wolf's Dragoons by Bowie Industries at Alarion. This was done in an orbital 'Mech repair facility which was converted into a 'Mech assembly line. Introduced in 3050, the 'Mech was upgraded with an XL engine to save weight and used ten double heat sinks for greater heat dissipation. It retained the two LRM-20 launchers but replaced all other weaponry with one TharHes Blue SRM-4 launchers in each arm and a Doering Electronics Glowworm Narc Missile Beacon launcher in the center torso. The 5W was supplied with four tons of LRM reloads, two tons of SRM reloads, and two tons of Narc reloads, all carried in the CASE-protected side torsos. diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 10/Archer ARC-7C.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 10/Archer ARC-7C.mtf index 23e000df7..dba18eadc 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 10/Archer ARC-7C.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 10/Archer ARC-7C.mtf @@ -162,7 +162,7 @@ Foot Actuator overview:One of the most iconic BattleMechs is the Archer, with its low-slung torso, enormous fists, and missile-bay covers. The Archer was first manufactured in 2474 for heavy-hitting, long-range brawling, and fire-support. -capabilities:Two enormous missile launchers with tons of ammo power the Archer. The missiles were formidable, but their short-range inaccuracy required four medium lasers, two rear-facing and one in each arm. Enlarged hand actuators allow the design to undertake severe physical attacks and transport captured supplies during raids. The cockpit of the Archer situated beneath the center midsection, giving the pilot a unique battlefield view. The torso armor belt above the cockpit protects the gyro and engine from the superior armor. Many pilots initially entered battle with their missile bays locked to hide the 'Mech's real capabilities, leading some to believe it was a close-combat design. As the Archer became famous, this pretext became meaningless. Archer pilots rarely learn new skills, but this hasn't tarnished the 'Mech's reputation. +capabilities:Two enormous missile launchers with tons of ammo power the Archer. The missiles were formidable, but their short-range inaccuracy required four medium lasers, two rear-facing and one in each arm. Enlarged hand actuators allow the design to undertake severe physical attacks and transport captured supplies during raids. The cockpit of the Archer is situated beneath the center midsection, giving the pilot a unique battlefield view. The torso armor belt above the cockpit protects the gyro and engine from the superior armor. Many pilots initially entered battle with their missile bays locked to hide the 'Mech's real capabilities, leading some to believe it was a close-combat design. As the Archer became famous, this pretext became meaningless. Archer pilots rarely learn new skills, but this hasn't tarnished the 'Mech's reputation. deployment:This mixed tech design was produced on Terra and used the Republic of the Sphere. A 350-rated XL engine gives it a top speed of 86 km/h. Two Clan-spec LRM-20s are equipped with Artemis V Fire Control Systems, and carry two tons for each launcher in a CASE II protected bay in each torso. The medium lasers were swapped for Clan spec versions and are tied into a Targeting Computer. Fourteen double heat sinks control the heat, and it's protected by thirteen tons of armor. diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 10/Archer ARC-9R.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 10/Archer ARC-9R.mtf index 2d4c72fb1..12b859741 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 10/Archer ARC-9R.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 10/Archer ARC-9R.mtf @@ -160,7 +160,7 @@ Foot Actuator overview:One of the most iconic BattleMechs is the Archer, with its low-slung torso, enormous fists, and missile-bay covers. The Archer was first manufactured in 2474 for heavy-hitting, long-range brawling, and fire-support. -capabilities:Two enormous missile launchers with tons of ammo power the Archer. The missiles were formidable, but their short-range inaccuracy required four medium lasers, two rear-facing and one in each arm. Enlarged hand actuators allow the design to undertake severe physical attacks and transport captured supplies during raids. The cockpit of the Archer situated beneath the center midsection, giving the pilot a unique battlefield view. The torso armor belt above the cockpit protects the gyro and engine from the superior armor. Many pilots initially entered battle with their missile bays locked to hide the 'Mech's real capabilities, leading some to believe it was a close-combat design. As the Archer became famous, this pretext became meaningless. Archer pilots rarely learn new skills, but this hasn't tarnished the 'Mech's reputation. +capabilities:Two enormous missile launchers with tons of ammo power the Archer. The missiles were formidable, but their short-range inaccuracy required four medium lasers, two rear-facing and one in each arm. Enlarged hand actuators allow the design to undertake severe physical attacks and transport captured supplies during raids. The cockpit of the Archer is situated beneath the center midsection, giving the pilot a unique battlefield view. The torso armor belt above the cockpit protects the gyro and engine from the superior armor. Many pilots initially entered battle with their missile bays locked to hide the 'Mech's real capabilities, leading some to believe it was a close-combat design. As the Archer became famous, this pretext became meaningless. Archer pilots rarely learn new skills, but this hasn't tarnished the 'Mech's reputation. deployment:This Republic of the Sphere variant started with an ARC-4M and replaced the engine with a 280-rated light engine and replaced the arm mounted lasers with ER versions. The rear-firing lasers were removed entirely. A C3 slave unit was mounted in the head. The LRM-20s were replaced by Extended LRM-15s with three tons of ammo per launcher. This ammunition was carried in CASE II protected bays in the torso. diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 10/Archer C.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 10/Archer C.mtf index 510927e78..3812b8e97 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 10/Archer C.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 10/Archer C.mtf @@ -162,7 +162,7 @@ Heat Sink overview:One of the most iconic BattleMechs is the Archer, with its low-slung torso, enormous fists, and missile-bay covers. The Archer was first manufactured in 2474 for heavy-hitting, long-range brawling, and fire-support. -capabilities:Two enormous missile launchers with tons of ammo power the Archer. The missiles were formidable, but their short-range inaccuracy required four medium lasers, two rear-facing and one in each arm. Enlarged hand actuators allow the design to undertake severe physical attacks and transport captured supplies during raids. The cockpit of the Archer situated beneath the center midsection, giving the pilot a unique battlefield view. The torso armor belt above the cockpit protects the gyro and engine from the superior armor. Many pilots initially entered battle with their missile bays locked to hide the 'Mech's real capabilities, leading some to believe it was a close-combat design. As the Archer became famous, this pretext became meaningless. Archer pilots rarely learn new skills, but this hasn't tarnished the 'Mech's reputation. +capabilities:Two enormous missile launchers with tons of ammo power the Archer. The missiles were formidable, but their short-range inaccuracy required four medium lasers, two rear-facing and one in each arm. Enlarged hand actuators allow the design to undertake severe physical attacks and transport captured supplies during raids. The cockpit of the Archer is situated beneath the center midsection, giving the pilot a unique battlefield view. The torso armor belt above the cockpit protects the gyro and engine from the superior armor. Many pilots initially entered battle with their missile bays locked to hide the 'Mech's real capabilities, leading some to believe it was a close-combat design. As the Archer became famous, this pretext became meaningless. Archer pilots rarely learn new skills, but this hasn't tarnished the 'Mech's reputation. deployment:A Clan-tech retrofit of the standard Star League Defense Force ARC-2R Archer and intended for second-line and solahma troops, the Archer C replaced all Inner Sphere weaponry with their Clan counterparts and used the weight savings to add ten more heat sinks. The Archer C mounted a pair of LRM-20s, capable of launching Swarm LRM munitions, and a quartet of ER medium lasers. diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 10/Highlander HGN-740.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 10/Highlander HGN-740.mtf index 981c54a7e..f560eeaaf 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 10/Highlander HGN-740.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 10/Highlander HGN-740.mtf @@ -168,7 +168,7 @@ capabilities:Initially designed as a dedicated city and installation defender, t deployment:This Dark Age variant of the Highlander uses an ER PPC with a PPC Capacitor for it's main firepower. This is supplemented by an LRM-20 with an Artemis IV Fire Control System to enhance accuracy. The left arm carries a Streak SRM-6 and the right torso has a pair of ER Medium Lasers. Light Ferro-Fibrous armor provides protection. CASE II protects the two tons of LRM and one ton of Streak SRM ammunition. The final weapons system is a pair of M-Pods on each leg. -history:during the design's initial trial runs that pilots began using these 'Mechs in what would infamously become known as the "Highlander Burial". Leaping into the air and landing directly on their enemy, a Highlander could literally drive a light 'Mech into the ground. So successful was this maneuver that the design team re-engineered the legs to withstand repeated death-from-above attacks and turned what had been a desperation move into an art form, giving Highlander pilots an additional psychological edge. As with other Star League era designs the Highlander would suffer the loss of technology brought about by the Succession Wars, and when StarCorps' factory on Son Hoa was devastated towards the end of the Second Succession War the original HGN-732 became virtually extinct. An agreement between StarCorps and Hollis Incorporated to rebuild destroyed chassis from scratch using readily-available technology kept the line going until the mid-3030s when limited production was restarted by StarCorps on Son Hoa and Corey, producing barely a dozen new 'Mechs per year. These HGN-733 Highlanders were used in small numbers by the Capellan Confederation and Lyran Commonwealth, commonly as part of lances containing Exterminators, Victors, Grasshoppers and Catapults. Unbeknownst to many, ComStar also maintained a large stock of Highlanders left over from the Star League, some of which they gifted to the Draconis Combine during the War of 3039. The appearance of so many seemingly rare 733s, along with a few 732s whose advanced technology managed to slip through ComStar screening, had a large impact on Lyran morale during that conflict. ComStar would also use the design in their own military forces, the Com Guard, and even during the Clan Invasion a few original 732s would take to the field as part of the Clans' fighting forces. The Northwind Highlanders especially favored this namesake Battlemech. In fact, during the Succession Wars, they were the only Inner Sphere army to keep a large number of them operational, along with ComStar. The Highlanders are specially skilled in delivering the famed Highlander Burial maneuver. By 3057 StarCorps' Son Hoa line was at full production, producing brand-new original-spec Highlanders for Lyran units of the Federated Commonwealth, just in time to take part in the FedCom Civil War. Highlanders would continue to be produced all the way through to the Jihad, where advanced variants fought both for and against the Word of Blake. +history:During the design's initial trial runs pilots began using these 'Mechs in what would infamously become known as the "Highlander Burial". Leaping into the air and landing directly on their enemy, a Highlander could literally drive a light 'Mech into the ground. So successful was this maneuver that the design team re-engineered the legs to withstand repeated death-from-above attacks and turned what had been a desperation move into an art form, giving Highlander pilots an additional psychological edge. As with other Star League era designs the Highlander would suffer the loss of technology brought about by the Succession Wars, and when StarCorps' factory on Son Hoa was devastated towards the end of the Second Succession War the original HGN-732 became virtually extinct. An agreement between StarCorps and Hollis Incorporated to rebuild destroyed chassis from scratch using readily-available technology kept the line going until the mid-3030s when limited production was restarted by StarCorps on Son Hoa and Corey, producing barely a dozen new 'Mechs per year. These HGN-733 Highlanders were used in small numbers by the Capellan Confederation and Lyran Commonwealth, commonly as part of lances containing Exterminators, Victors, Grasshoppers and Catapults. Unbeknownst to many, ComStar also maintained a large stock of Highlanders left over from the Star League, some of which they gifted to the Draconis Combine during the War of 3039. The appearance of so many seemingly rare 733s, along with a few 732s whose advanced technology managed to slip through ComStar screening, had a large impact on Lyran morale during that conflict. ComStar would also use the design in their own military forces, the Com Guard, and even during the Clan Invasion a few original 732s would take to the field as part of the Clans' fighting forces. The Northwind Highlanders especially favored this namesake Battlemech. In fact, during the Succession Wars, they were the only Inner Sphere army to keep a large number of them operational, along with ComStar. The Highlanders are specially skilled in delivering the famed Highlander Burial maneuver. By 3057 StarCorps' Son Hoa line was at full production, producing brand-new original-spec Highlanders for Lyran units of the Federated Commonwealth, just in time to take part in the FedCom Civil War. Highlanders would continue to be produced all the way through to the Jihad, where advanced variants fought both for and against the Word of Blake. manufacturer:StarCorps Industries primaryfactory:Son Hoa diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 10/Vulture (Mad Dog) DD.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 10/Vulture (Mad Dog) DD.mtf index 094dbc3c7..d06478ef1 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 10/Vulture (Mad Dog) DD.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 10/Vulture (Mad Dog) DD.mtf @@ -161,9 +161,9 @@ overview:The Mad Dog is a heavy Clan OmniMech used for long-range indirect fire capabilities:The Double D is built for long ranged combat on the left side and short range combat on the right. The right arm carries a trio of Medium Pulse Lasers. A Streak SRM-6 and one ton of ammo are carried in the right torso. The left torso carries an Artemis IV enhanced LRM-20 with a meager one ton of ammunition. A pair of LB 2-X ACs and their shared ton of ammo are mounted in the left arm. (Note: this variant is a canonization of the D variant featured in the German Solaris VII boxset. -deployment:The name also fit the battlefield role of the Mad Dog; the main role of the Mad Dog is to act as a support 'Mech, and it often holds a hill maintaining constant watch over the entire battlefield, like a vulture waiting for its prey. With its ample firepower and decent speed of 86.4 km/h, it makes a highly mobile firing platform, and as such has spread to near ubiquity among the forces deployed by the Clans, although the design is favored more by Clan Ghost Bear MechWarriors. The Mad Dog carries eight and a half tons of Ferro-Fibrous armor for decent protection, although it will not be able to stand up to heavy fire. +deployment:The name also fit the battlefield role of the Mad Dog; to act as a support 'Mech, and it often holds a hill maintaining constant watch over the entire battlefield, like a vulture waiting for its prey. With its ample firepower and decent speed of 86.4 km/h, it makes a highly mobile firing platform, and as such has spread to near ubiquity among the forces deployed by the Clans, although the design is favored more by Clan Ghost Bear MechWarriors. The Mad Dog carries eight and a half tons of Ferro-Fibrous armor for decent protection, although it will not be able to stand up to heavy fire. -history:The Mad Dog was designed by Clan Smoke Jaguar as a second generation OmniMech based on the original heavy OmniMech Lupus of Clan Coyote.[7] The Mad Dog also used some of the same moulds of the Clan Wolf Timber Wolf OmniMech. However, despite using some of the same moulds (which might be viewed as high praise), the Mad Dog was named as a slur to the Lupus and Timber Wolf, and to Clans Wolf and Coyote. Because of its widespread production, most Clans maintain a large number of Mad Dogs in their toumans. +history:The Mad Dog was designed by Clan Smoke Jaguar as a second generation OmniMech based on the original heavy OmniMech Lupus of Clan Coyote. The Mad Dog also used some of the same moulds of the Clan Wolf Timber Wolf OmniMech. However, despite using some of the same moulds (which might be viewed as high praise), the Mad Dog was named as a slur to the Lupus and Timber Wolf, and to Clans Wolf and Coyote. Because of its widespread production, most Clans maintain a large number of Mad Dogs in their toumans. manufacturer:Various,Svarstaad Industriplex Beta primaryfactory:Various,Svarstaad systemmanufacturer:CHASSIS:Eden Mk 60-OM diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 10/Vulture (Mad Dog) G.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 10/Vulture (Mad Dog) G.mtf index cbf8c54ba..4fc09fa11 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 10/Vulture (Mad Dog) G.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 10/Vulture (Mad Dog) G.mtf @@ -161,8 +161,8 @@ overview:The Mad Dog is a heavy Clan OmniMech used for long-range indirect fire capabilities:This variant carries a pair of Streak SRM-6s in the right torso and a Streak LRM-15 in the left. The Mad Dog G carries a single ER PPC in the left arm, while the right mounts a trio of ER Medium Pulse Lasers. -deployment:The name also fit the battlefield role of the Mad Dog; the main role of the Mad Dog is to act as a support 'Mech, and it often holds a hill maintaining constant watch over the entire battlefield, like a vulture waiting for its prey. With its ample firepower and decent speed of 86.4 km/h, it makes a highly mobile firing platform, and as such has spread to near ubiquity among the forces deployed by the Clans, although the design is favored more by Clan Ghost Bear MechWarriors. The Mad Dog carries eight and a half tons of Ferro-Fibrous armor for decent protection, although it will not be able to stand up to heavy fire. -history:The Mad Dog was designed by Clan Smoke Jaguar as a second generation OmniMech based on the original heavy OmniMech Lupus of Clan Coyote.[7] The Mad Dog also used some of the same moulds of the Clan Wolf Timber Wolf OmniMech. However, despite using some of the same moulds (which might be viewed as high praise), the Mad Dog was named as a slur to the Lupus and Timber Wolf, and to Clans Wolf and Coyote. Because of its widespread production, most Clans maintain a large number of Mad Dogs in their toumans. +deployment:The name also fit the battlefield role of the Mad Dog; to act as a support 'Mech, and it often holds a hill maintaining constant watch over the entire battlefield, like a vulture waiting for its prey. With its ample firepower and decent speed of 86.4 km/h, it makes a highly mobile firing platform, and as such has spread to near ubiquity among the forces deployed by the Clans, although the design is favored more by Clan Ghost Bear MechWarriors. The Mad Dog carries eight and a half tons of Ferro-Fibrous armor for decent protection, although it will not be able to stand up to heavy fire. +history:The Mad Dog was designed by Clan Smoke Jaguar as a second generation OmniMech based on the original heavy OmniMech Lupus of Clan Coyote. The Mad Dog also used some of the same moulds of the Clan Wolf Timber Wolf OmniMech. However, despite using some of the same moulds (which might be viewed as high praise), the Mad Dog was named as a slur to the Lupus and Timber Wolf, and to Clans Wolf and Coyote. Because of its widespread production, most Clans maintain a large number of Mad Dogs in their toumans. manufacturer:Various,Svarstaad Industriplex Beta primaryfactory:Various,Svarstaad systemmanufacturer:CHASSIS:Eden Mk 60-OM diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 10/Vulture (Mad Dog) I.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 10/Vulture (Mad Dog) I.mtf index b5b41344a..2822a9724 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 10/Vulture (Mad Dog) I.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 10/Vulture (Mad Dog) I.mtf @@ -157,8 +157,8 @@ overview:The Mad Dog is a heavy Clan OmniMech used for long-range indirect fire capabilities:With its capacitor enhanced left arm ER PPC, the Vulture I can create giant holes in its foes at long range. Following that up with its twin clan built Rotary AC/2s the I is able to damage internal components with ease. Two tons of ammo feed the autocannons. Three additional heatsinks are used to keep the design cool. -deployment:The name also fit the battlefield role of the Mad Dog; the main role of the Mad Dog is to act as a support 'Mech, and it often holds a hill maintaining constant watch over the entire battlefield, like a vulture waiting for its prey. With its ample firepower and decent speed of 86.4 km/h, it makes a highly mobile firing platform, and as such has spread to near ubiquity among the forces deployed by the Clans, although the design is favored more by Clan Ghost Bear MechWarriors. The Mad Dog carries eight and a half tons of Ferro-Fibrous armor for decent protection, although it will not be able to stand up to heavy fire. -history:The Mad Dog was designed by Clan Smoke Jaguar as a second generation OmniMech based on the original heavy OmniMech Lupus of Clan Coyote.[7] The Mad Dog also used some of the same moulds of the Clan Wolf Timber Wolf OmniMech. However, despite using some of the same moulds (which might be viewed as high praise), the Mad Dog was named as a slur to the Lupus and Timber Wolf, and to Clans Wolf and Coyote. Because of its widespread production, most Clans maintain a large number of Mad Dogs in their toumans. +deployment:The name also fit the battlefield role of the Mad Dog; to act as a support 'Mech, and it often holds a hill maintaining constant watch over the entire battlefield, like a vulture waiting for its prey. With its ample firepower and decent speed of 86.4 km/h, it makes a highly mobile firing platform, and as such has spread to near ubiquity among the forces deployed by the Clans, although the design is favored more by Clan Ghost Bear MechWarriors. The Mad Dog carries eight and a half tons of Ferro-Fibrous armor for decent protection, although it will not be able to stand up to heavy fire. +history:The Mad Dog was designed by Clan Smoke Jaguar as a second generation OmniMech based on the original heavy OmniMech Lupus of Clan Coyote. The Mad Dog also used some of the same moulds of the Clan Wolf Timber Wolf OmniMech. However, despite using some of the same moulds (which might be viewed as high praise), the Mad Dog was named as a slur to the Lupus and Timber Wolf, and to Clans Wolf and Coyote. Because of its widespread production, most Clans maintain a large number of Mad Dogs in their toumans. manufacturer:Various,Svarstaad Industriplex Beta primaryfactory:Various,Svarstaad systemmanufacturer:CHASSIS:Eden Mk 60-OM diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 10/Vulture (Mad Dog) T.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 10/Vulture (Mad Dog) T.mtf index a6abc9868..85c9fbc49 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 10/Vulture (Mad Dog) T.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 10/Vulture (Mad Dog) T.mtf @@ -160,8 +160,8 @@ overview:The Mad Dog is a heavy Clan OmniMech used for long-range indirect fire capabilities:The T sacrifices the Prime’s accuracy for improved long range damage capabilities. Gone are the pulse lasers and in their place is an ER Large Laser and an ER Medium Laser in each arm. The Prime’s LRM-20s are still in place but now feature Artemis V. Each launcher has a two ton magazine. An extra double heatsink is mounted in the CT. -deployment:The name also fit the battlefield role of the Mad Dog; the main role of the Mad Dog is to act as a support 'Mech, and it often holds a hill maintaining constant watch over the entire battlefield, like a vulture waiting for its prey. With its ample firepower and decent speed of 86.4 km/h, it makes a highly mobile firing platform, and as such has spread to near ubiquity among the forces deployed by the Clans, although the design is favored more by Clan Ghost Bear MechWarriors. The Mad Dog carries eight and a half tons of Ferro-Fibrous armor for decent protection, although it will not be able to stand up to heavy fire. -history:The Mad Dog was designed by Clan Smoke Jaguar as a second generation OmniMech based on the original heavy OmniMech Lupus of Clan Coyote.[7] The Mad Dog also used some of the same moulds of the Clan Wolf Timber Wolf OmniMech. However, despite using some of the same moulds (which might be viewed as high praise), the Mad Dog was named as a slur to the Lupus and Timber Wolf, and to Clans Wolf and Coyote. Because of its widespread production, most Clans maintain a large number of Mad Dogs in their toumans. +deployment:The name also fit the battlefield role of the Mad Dog; to act as a support 'Mech, and it often holds a hill maintaining constant watch over the entire battlefield, like a vulture waiting for its prey. With its ample firepower and decent speed of 86.4 km/h, it makes a highly mobile firing platform, and as such has spread to near ubiquity among the forces deployed by the Clans, although the design is favored more by Clan Ghost Bear MechWarriors. The Mad Dog carries eight and a half tons of Ferro-Fibrous armor for decent protection, although it will not be able to stand up to heavy fire. +history:The Mad Dog was designed by Clan Smoke Jaguar as a second generation OmniMech based on the original heavy OmniMech Lupus of Clan Coyote. The Mad Dog also used some of the same moulds of the Clan Wolf Timber Wolf OmniMech. However, despite using some of the same moulds (which might be viewed as high praise), the Mad Dog was named as a slur to the Lupus and Timber Wolf, and to Clans Wolf and Coyote. Because of its widespread production, most Clans maintain a large number of Mad Dogs in their toumans. manufacturer:Various,Svarstaad Industriplex Beta primaryfactory:Various,Svarstaad systemmanufacturer:CHASSIS:Eden Mk 60-OM diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 10/Vulture (Mad Dog) V.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 10/Vulture (Mad Dog) V.mtf index dc69c784a..c61464b27 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 10/Vulture (Mad Dog) V.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 10/Vulture (Mad Dog) V.mtf @@ -158,10 +158,10 @@ Foot Actuator overview:The Mad Dog is a heavy Clan OmniMech used for long-range indirect fire support. With hunched shoulders, a protruding head, and reverse-jointed legs, the Mad Dog resembles a vulture, so much so that it was codenamed Vulture and Hagetaka ("Vulture" in Japanese) by the Inner Sphere forces which first encountered it. -capabilities:An unusual design, the V is used for mobile artillery. An Arrow IV launcher is jammed into the right torso with some of the weapon spilling out into the right arm as well. Two tons of ammo Arrow ammo are carried in the left torso. Unlike some designs, like the Naga, the Vulture V is more than capable of self-defense, and isn’t nearly worthless when out of artillery ammo. An LRM-20 is carried in the left torso and is provided with its own two tons of ammo. Additionally, each arm carries both a Medium Pulse Laser and an [ER Medium Laser]]. +capabilities:An unusual design, the V is used for mobile artillery. An Arrow IV launcher is jammed into the right torso with some of the weapon spilling out into the right arm as well. Two tons of ammo Arrow ammo are carried in the left torso. Unlike some designs, like the Naga, the Vulture V is more than capable of self-defense, and isn’t nearly worthless when out of artillery ammo. An LRM-20 is carried in the left torso and is provided with its own two tons of ammo. Additionally, each arm carries both a Medium Pulse Laser and an ER Medium Laser. -deployment:The name also fit the battlefield role of the Mad Dog; the main role of the Mad Dog is to act as a support 'Mech, and it often holds a hill maintaining constant watch over the entire battlefield, like a vulture waiting for its prey. With its ample firepower and decent speed of 86.4 km/h, it makes a highly mobile firing platform, and as such has spread to near ubiquity among the forces deployed by the Clans, although the design is favored more by Clan Ghost Bear MechWarriors. The Mad Dog carries eight and a half tons of Ferro-Fibrous armor for decent protection, although it will not be able to stand up to heavy fire. -history:The Mad Dog was designed by Clan Smoke Jaguar as a second generation OmniMech based on the original heavy OmniMech Lupus of Clan Coyote.[7] The Mad Dog also used some of the same moulds of the Clan Wolf Timber Wolf OmniMech. However, despite using some of the same moulds (which might be viewed as high praise), the Mad Dog was named as a slur to the Lupus and Timber Wolf, and to Clans Wolf and Coyote. Because of its widespread production, most Clans maintain a large number of Mad Dogs in their toumans. +deployment:The name also fit the battlefield role of the Mad Dog; to act as a support 'Mech, and it often holds a hill maintaining constant watch over the entire battlefield, like a vulture waiting for its prey. With its ample firepower and decent speed of 86.4 km/h, it makes a highly mobile firing platform, and as such has spread to near ubiquity among the forces deployed by the Clans, although the design is favored more by Clan Ghost Bear MechWarriors. The Mad Dog carries eight and a half tons of Ferro-Fibrous armor for decent protection, although it will not be able to stand up to heavy fire. +history:The Mad Dog was designed by Clan Smoke Jaguar as a second generation OmniMech based on the original heavy OmniMech Lupus of Clan Coyote. The Mad Dog also used some of the same moulds of the Clan Wolf Timber Wolf OmniMech. However, despite using some of the same moulds (which might be viewed as high praise), the Mad Dog was named as a slur to the Lupus and Timber Wolf, and to Clans Wolf and Coyote. Because of its widespread production, most Clans maintain a large number of Mad Dogs in their toumans. manufacturer:Various,Svarstaad Industriplex Beta primaryfactory:Various,Svarstaad systemmanufacturer:CHASSIS:Eden Mk 60-OM diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 12/Black Knight BL-18-KNT.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 12/Black Knight BL-18-KNT.mtf index e9f382224..9767147ae 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 12/Black Knight BL-18-KNT.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 12/Black Knight BL-18-KNT.mtf @@ -155,7 +155,7 @@ CLDoubleHeatSink 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 of them 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 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:Produced for the Republic of the Sphere by Kong Interstellar, this variant uses a Light Engine to run at 64 km/h. The Endo-Composite frame carries a Clan-spec ER PPC, two ER Large Lasers, and four ER medium lasers. For anti-infantry work, a Clan Small Pulse Laser is mounted in the head. Twenty Clan-built double heat sinks are provided to keep the 'Mech cool. All these weapons are tied into an Inner Sphere Targeting Computer. diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 12/Hatchetman HCT-8S.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 12/Hatchetman HCT-8S.mtf index d49493ebb..32889173b 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 12/Hatchetman HCT-8S.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 12/Hatchetman HCT-8S.mtf @@ -155,7 +155,7 @@ capabilities:As well as being the first design to carry one, the Hatchetman itse deployment:This Dark Age LCAF configuration uses a Clan-spec engine to move at 86 km/h and five jump jets to cover 150 meters at a time. The traditional arm-mounted medium lasers have been replaced by Clan-spec ER Medium Lasers. The typical LB 10-X remains, but the traditional hatchet has been augmented by an Actuator Enhancement System for better close-combat capabilities. -history:s well as being the first design to carry one, the Hatchetman itself was the first totally new 'Mech produced in the Inner Sphere in over a century, and was also the first production 'Mech to use a Full-Head Ejection System. Despite being first manufactured in the Lyran Commonwealth the Hatchetman was actually designed by the enigmatic Dr. B. Banzai of Team Banzai, a mercenary unit associated with the Federated Suns' New Avalon Institute of Science. Thus the 'Mech was also a signal of the growing cooperation between these newly-allied Successor States. in the design's first combat test, when elements of the 4th Proserpina Hussars raided Sevren and were literally cut to pieces by a mostly Hatchetman-equipped battalion of the 26th Lyran Guards which lured the enemy into an industrial park. Where the Hatchetman is at a disadvantage is on open terrain, as its relatively slow speed, light armoring and general frailty leaves it vulnerable to other 'Mechs. Initially the Hatchetman's first production run was limited to garrisoning large Lyran cities, but its early successes inspired further deployments and the 'Mech soon began appearing in the arsenal of the Federated Suns, particularly among the Crucis Lancers and 1st Kathil Uhlans. In the wake of the Fourth Succession War and the formal creation of the Federated Commonwealth, the Hatchetman was selected to become one of the standard designs for the Armed Forces of the Federated Commonwealth. Demand for the 'Mech soon began to outstrip Defiance Industries' ability to supply it, even after tripling output from their Hesperus II factory, and so it contracted Johnston Industries to set up a Hatchetman line on Johnston. The recovery of lost Star League technology eventually allowed for the creation of the HCT-5S in 3049, with additional variants created in years hence. Among the other realms, the Draconis Combine managed to capture a few examples of the Hatchetman and successfully copy most of the design to produce their own following the War of 3039, however the 'Mech proved to be unpopular and the program was canceled. Hoping to salvage the project, Independence Weaponry experimented with the design and eventually created a variant more palatable to Kuritan pilots. Out in the Periphery, the introduction of the Hatchetman caused quite a stir within the Taurian Concordat when a group of mercenaries brought along their old HCT-3Fs upon integrating with the Taurian Defense Forces. Protector of the Realm Thomas Calderon ordered Taurus Territorial Industries to reverse-engineer the design, which they finally succeeded in accomplishing after much delay by 3054, only for production to be halted in 3066 when the Fighting Urukhai destroyed the Taurus Territorial Industries facility. +history:As well as being the first design to carry one, the Hatchetman itself was the first totally new 'Mech produced in the Inner Sphere in over a century, and was also the first production 'Mech to use a Full-Head Ejection System. Despite being first manufactured in the Lyran Commonwealth the Hatchetman was actually designed by the enigmatic Dr. B. Banzai of Team Banzai, a mercenary unit associated with the Federated Suns' New Avalon Institute of Science. Thus the 'Mech was also a signal of the growing cooperation between these newly-allied Successor States. In the design's first combat test, elements of the 4th Proserpina Hussars raided Sevren and were literally cut to pieces by a mostly Hatchetman-equipped battalion of the 26th Lyran Guards which lured the enemy into an industrial park. Where the Hatchetman is at a disadvantage is on open terrain, as its relatively slow speed, light armoring and general frailty leaves it vulnerable to other 'Mechs. Initially the Hatchetman's first production run was limited to garrisoning large Lyran cities, but its early successes inspired further deployments and the 'Mech soon began appearing in the arsenal of the Federated Suns, particularly among the Crucis Lancers and 1st Kathil Uhlans. In the wake of the Fourth Succession War and the formal creation of the Federated Commonwealth, the Hatchetman was selected to become one of the standard designs for the Armed Forces of the Federated Commonwealth. Demand for the 'Mech soon began to outstrip Defiance Industries' ability to supply it, even after tripling output from their Hesperus II factory, and so it contracted Johnston Industries to set up a Hatchetman line on Johnston. The recovery of lost Star League technology eventually allowed for the creation of the HCT-5S in 3049, with additional variants created in years hence. Among the other realms, the Draconis Combine managed to capture a few examples of the Hatchetman and successfully copy most of the design to produce their own following the War of 3039, however the 'Mech proved to be unpopular and the program was canceled. Hoping to salvage the project, Independence Weaponry experimented with the design and eventually created a variant more palatable to Kuritan pilots. Out in the Periphery, the introduction of the Hatchetman caused quite a stir within the Taurian Concordat when a group of mercenaries brought along their old HCT-3Fs upon integrating with the Taurian Defense Forces. Protector of the Realm Thomas Calderon ordered Taurus Territorial Industries to reverse-engineer the design, which they finally succeeded in accomplishing after much delay by 3054, only for production to be halted in 3066 when the Fighting Urukhai destroyed the Taurus Territorial Industries facility. manufacturer:Defiance Industries primaryfactory:Hesperus II diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 14/Exterminator EXT-7X.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 14/Exterminator EXT-7X.mtf index 2dbb39f82..2a502ba9d 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 14/Exterminator EXT-7X.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 14/Exterminator EXT-7X.mtf @@ -159,7 +159,7 @@ IS Stealth overview:The Exterminator is a BattleMech that was designed in 2630 for the most dubious, but necessary, of purposes: Head Hunting. -capabilities:The weapons used by the Exterminator are not nearly as unique or high tech as the electronics on board. The primary weapons of the Exterminator are medium weight lasers, two of each in either arm. For long range engagements, the 'Mech also carries a missile launcher with one ton of reloads in the center torso. These weapons are backed up by a short range laser mounted in the head for when engagements close to point blank range, and, for defense against missile attacks, the Exterminator has a Anti-Missile System in the right torso with one ton of ammo. +capabilities:The weapons used by the Exterminator are not nearly as unique or high tech as the electronics on board. The primary weapons of the Exterminator are medium weight lasers, two in each arm. For long range engagements, the 'Mech also carries a missile launcher with one ton of reloads in the center torso. These weapons are backed up by a short range laser mounted in the head for when engagements close to point blank range, and, for defense against missile attacks, the Exterminator has a Anti-Missile System in the right torso with one ton of ammo. deployment:Appearing in the Dark Age, this variant uses an XXL fusion engine and composite internal structure to save weight. Slower than other Exterminators, it has a top speed of 86 km/h in most cases, but can use an engine supercharger to reach a sprint speed of 108 km/h; five jump jets let it cover 150 meters at a time. It is protected by thirteen tons of stealth armor driven by a Guardian ECM suite. A laser AMS destroys incoming missiles. The main firepower comes from two medium variable speed pulse lasers in each arm, while the missile launcher is an MRM-10 with one ton of ammunition. The final weapon is an ER small laser mounted in the head. Thirteen double heat sinks are also fitted and supplemented by a coolant pod for emergency use. diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 14/Thug THG-13U.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 14/Thug THG-13U.mtf index 5674597dc..8f0a1def7 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 14/Thug THG-13U.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 14/Thug THG-13U.mtf @@ -160,7 +160,7 @@ overview:The Thug was designed by Maltex Corporation as a direct competitor to t capabilities:The armament on the Thug is a very simple, yet effective, combination. -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. +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. manufacturer:Maltex Corporation, Earthwerks Incorporated primaryfactory:Errai, Keystone diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 16/Cauldron-Born (Ebon Jaguar) E.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 16/Cauldron-Born (Ebon Jaguar) E.mtf index f1c09f7ae..af127765c 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 16/Cauldron-Born (Ebon Jaguar) E.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 16/Cauldron-Born (Ebon Jaguar) E.mtf @@ -158,7 +158,7 @@ overview:Introduced in 3049 to address flaws in the venerable Hellbringer, by Op capabilities:The E configuration is equipped with an ATM 12 launcher, a HAG 20, an ER Medium Laser and a Large Pulse Laser. -history:Facing it for the first time when engaging the First Jaguar Guards Cluster in the Kado-Guchi Valley, the 'Mech's ability to take damage and remain operational led the Inner Sphere warriors who fought it to call it the Cauldron-Born after the unstoppable zombies of Irish myth. Paradoxically many of the other Clans also used the Inner Sphere Cauldron-Born reporting name, having first learned detailed information of the design from Inner Sphere sources. y Operation BULLDOG the Cauldron-Born made up a large proportion of the heavy 'Mechs of the rebuilding Smoke Jaguars, and following their Annihilation the design proliferated the remaining Clans, save the Jade Falcons, Wolves and Coyotes who continued to favor the Hellbringer. Following the Wars of Reaving the Ebon Jaguar had finally supplanted the Hellbringer in most Homeworld Clans, save the Coyotes who remained loyal to redeeming the honor of the design. +history:Facing it for the first time when engaging the First Jaguar Guards Cluster in the Kado-Guchi Valley, the 'Mech's ability to take damage and remain operational led the Inner Sphere warriors who fought it to call it the Cauldron-Born after the unstoppable zombies of Irish myth. Paradoxically many of the other Clans also used the Inner Sphere Cauldron-Born reporting name, having first learned detailed information of the design from Inner Sphere sources. By Operation BULLDOG the Cauldron-Born made up a large proportion of the heavy 'Mechs of the rebuilding Smoke Jaguars, and following their Annihilation the design proliferated the remaining Clans, save the Jade Falcons, Wolves and Coyotes who continued to favor the Hellbringer. Following the Wars of Reaving the Ebon Jaguar had finally supplanted the Hellbringer in most Homeworld Clans, save the Coyotes who remained loyal to redeeming the honor of the design. manufacturer:Huntress Manufacturing Plant DL-6 primaryfactory:Huntress diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 16/Cauldron-Born (Ebon Jaguar) F.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 16/Cauldron-Born (Ebon Jaguar) F.mtf index 2a5148802..c5c1985b9 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 16/Cauldron-Born (Ebon Jaguar) F.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 16/Cauldron-Born (Ebon Jaguar) F.mtf @@ -158,7 +158,7 @@ overview:Introduced in 3049 to address flaws in the venerable Hellbringer, by Op capabilities:Mounting an ER PPC in each arm and an ATM 6 in each side torso the Ebon Jaguar F is a fearsome variant that can tear into its foes and any range. Three tons of ATM ammo split between the side torsos, two in the right and one in the left, allow the full tactical flexibility of the launchers. A Targeting Computer resides in the right torso and makes the PPCs deadly accurate. The left torso carries one additional heat sink while each arm carries two. Eighteen total heatsinks allows the F to fire its primary armament relentlessly. -history:Facing it for the first time when engaging the First Jaguar Guards Cluster in the Kado-Guchi Valley, the 'Mech's ability to take damage and remain operational led the Inner Sphere warriors who fought it to call it the Cauldron-Born after the unstoppable zombies of Irish myth. Paradoxically many of the other Clans also used the Inner Sphere Cauldron-Born reporting name, having first learned detailed information of the design from Inner Sphere sources. y Operation BULLDOG the Cauldron-Born made up a large proportion of the heavy 'Mechs of the rebuilding Smoke Jaguars, and following their Annihilation the design proliferated the remaining Clans, save the Jade Falcons, Wolves and Coyotes who continued to favor the Hellbringer. Following the Wars of Reaving the Ebon Jaguar had finally supplanted the Hellbringer in most Homeworld Clans, save the Coyotes who remained loyal to redeeming the honor of the design. +history:Facing it for the first time when engaging the First Jaguar Guards Cluster in the Kado-Guchi Valley, the 'Mech's ability to take damage and remain operational led the Inner Sphere warriors who fought it to call it the Cauldron-Born after the unstoppable zombies of Irish myth. Paradoxically many of the other Clans also used the Inner Sphere Cauldron-Born reporting name, having first learned detailed information of the design from Inner Sphere sources. By Operation BULLDOG the Cauldron-Born made up a large proportion of the heavy 'Mechs of the rebuilding Smoke Jaguars, and following their Annihilation the design proliferated the remaining Clans, save the Jade Falcons, Wolves and Coyotes who continued to favor the Hellbringer. Following the Wars of Reaving the Ebon Jaguar had finally supplanted the Hellbringer in most Homeworld Clans, save the Coyotes who remained loyal to redeeming the honor of the design. manufacturer:Huntress Manufacturing Plant DL-6 primaryfactory:Huntress diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 16/Cauldron-Born (Ebon Jaguar) G.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 16/Cauldron-Born (Ebon Jaguar) G.mtf index acb97180a..735c54639 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 16/Cauldron-Born (Ebon Jaguar) G.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 16/Cauldron-Born (Ebon Jaguar) G.mtf @@ -156,7 +156,7 @@ overview:Introduced in 3049 to address flaws in the venerable Hellbringer, by Op capabilities:The G devotes most of its tonnage to a massive Hyper-Assault Gauss Rifle 40 that is spread between the left arm and torso. This weapon is fed from a three-ton ammunition bay in the left torso. An Improved Heavy Large Laser provides heavy secondary fire from the right arm. A right torso targeting computer enhances the accuracy of both weapons. -history:Facing it for the first time when engaging the First Jaguar Guards Cluster in the Kado-Guchi Valley, the 'Mech's ability to take damage and remain operational led the Inner Sphere warriors who fought it to call it the Cauldron-Born after the unstoppable zombies of Irish myth. Paradoxically many of the other Clans also used the Inner Sphere Cauldron-Born reporting name, having first learned detailed information of the design from Inner Sphere sources. y Operation BULLDOG the Cauldron-Born made up a large proportion of the heavy 'Mechs of the rebuilding Smoke Jaguars, and following their Annihilation the design proliferated the remaining Clans, save the Jade Falcons, Wolves and Coyotes who continued to favor the Hellbringer. Following the Wars of Reaving the Ebon Jaguar had finally supplanted the Hellbringer in most Homeworld Clans, save the Coyotes who remained loyal to redeeming the honor of the design. +history:Facing it for the first time when engaging the First Jaguar Guards Cluster in the Kado-Guchi Valley, the 'Mech's ability to take damage and remain operational led the Inner Sphere warriors who fought it to call it the Cauldron-Born after the unstoppable zombies of Irish myth. Paradoxically many of the other Clans also used the Inner Sphere Cauldron-Born reporting name, having first learned detailed information of the design from Inner Sphere sources. By Operation BULLDOG the Cauldron-Born made up a large proportion of the heavy 'Mechs of the rebuilding Smoke Jaguars, and following their Annihilation the design proliferated the remaining Clans, save the Jade Falcons, Wolves and Coyotes who continued to favor the Hellbringer. Following the Wars of Reaving the Ebon Jaguar had finally supplanted the Hellbringer in most Homeworld Clans, save the Coyotes who remained loyal to redeeming the honor of the design. manufacturer:Huntress Manufacturing Plant DL-6 primaryfactory:Huntress diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 16/Cauldron-Born (Ebon Jaguar) T.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 16/Cauldron-Born (Ebon Jaguar) T.mtf index 49397b133..efdb54790 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 16/Cauldron-Born (Ebon Jaguar) T.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 16/Cauldron-Born (Ebon Jaguar) T.mtf @@ -160,7 +160,7 @@ overview:Introduced in 3049 to address flaws in the venerable Hellbringer, by Op capabilities:The T variant uses a mix of Inner Sphere and Clan weaponry. A Clan ER PPC is mounted in the right arm, opposite a Clan Ultra Autocannon/5 in the left. A Streak LRM-10 and an Improved Heavy Medium Laser are carried in the left torso with one ton of both LRM and Autocannon ammunition. The right torso mounts twin Thunderbolt 5 launchers and their two tons of ammunition. Both side torsos are equipped with CASE II. -history:Facing it for the first time when engaging the First Jaguar Guards Cluster in the Kado-Guchi Valley, the 'Mech's ability to take damage and remain operational led the Inner Sphere warriors who fought it to call it the Cauldron-Born after the unstoppable zombies of Irish myth. Paradoxically many of the other Clans also used the Inner Sphere Cauldron-Born reporting name, having first learned detailed information of the design from Inner Sphere sources. y Operation BULLDOG the Cauldron-Born made up a large proportion of the heavy 'Mechs of the rebuilding Smoke Jaguars, and following their Annihilation the design proliferated the remaining Clans, save the Jade Falcons, Wolves and Coyotes who continued to favor the Hellbringer. Following the Wars of Reaving the Ebon Jaguar had finally supplanted the Hellbringer in most Homeworld Clans, save the Coyotes who remained loyal to redeeming the honor of the design. +history:Facing it for the first time when engaging the First Jaguar Guards Cluster in the Kado-Guchi Valley, the 'Mech's ability to take damage and remain operational led the Inner Sphere warriors who fought it to call it the Cauldron-Born after the unstoppable zombies of Irish myth. Paradoxically many of the other Clans also used the Inner Sphere Cauldron-Born reporting name, having first learned detailed information of the design from Inner Sphere sources. By Operation BULLDOG the Cauldron-Born made up a large proportion of the heavy 'Mechs of the rebuilding Smoke Jaguars, and following their Annihilation the design proliferated the remaining Clans, save the Jade Falcons, Wolves and Coyotes who continued to favor the Hellbringer. Following the Wars of Reaving the Ebon Jaguar had finally supplanted the Hellbringer in most Homeworld Clans, save the Coyotes who remained loyal to redeeming the honor of the design. manufacturer:Huntress Manufacturing Plant DL-6 primaryfactory:Huntress diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 16/Cauldron-Born (Ebon Jaguar) X.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 16/Cauldron-Born (Ebon Jaguar) X.mtf index 3ce79d4b2..7d852073b 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 16/Cauldron-Born (Ebon Jaguar) X.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 16/Cauldron-Born (Ebon Jaguar) X.mtf @@ -157,7 +157,7 @@ Clan Endo Steel overview:Introduced in 3049 to address flaws in the venerable Hellbringer, by Operation REVIVAL the Ebon Jaguar had only just started to spread through the Jaguar's touman with the Inner Sphere first encountering the design during the Battle of Luthien. capabilities:The X variant is equipped with an Angel ECM Suite for protection, and a Targeting Computer linked to the weapon systems. This configuration carries a Rotary AC/5 in the right arm, three ER Medium Pulse Lasers and a single ER Small Pulse Laser. -history:Facing it for the first time when engaging the First Jaguar Guards Cluster in the Kado-Guchi Valley, the 'Mech's ability to take damage and remain operational led the Inner Sphere warriors who fought it to call it the Cauldron-Born after the unstoppable zombies of Irish myth. Paradoxically many of the other Clans also used the Inner Sphere Cauldron-Born reporting name, having first learned detailed information of the design from Inner Sphere sources. y Operation BULLDOG the Cauldron-Born made up a large proportion of the heavy 'Mechs of the rebuilding Smoke Jaguars, and following their Annihilation the design proliferated the remaining Clans, save the Jade Falcons, Wolves and Coyotes who continued to favor the Hellbringer. Following the Wars of Reaving the Ebon Jaguar had finally supplanted the Hellbringer in most Homeworld Clans, save the Coyotes who remained loyal to redeeming the honor of the design. +history:Facing it for the first time when engaging the First Jaguar Guards Cluster in the Kado-Guchi Valley, the 'Mech's ability to take damage and remain operational led the Inner Sphere warriors who fought it to call it the Cauldron-Born after the unstoppable zombies of Irish myth. Paradoxically many of the other Clans also used the Inner Sphere Cauldron-Born reporting name, having first learned detailed information of the design from Inner Sphere sources. By Operation BULLDOG the Cauldron-Born made up a large proportion of the heavy 'Mechs of the rebuilding Smoke Jaguars, and following their Annihilation the design proliferated the remaining Clans, save the Jade Falcons, Wolves and Coyotes who continued to favor the Hellbringer. Following the Wars of Reaving the Ebon Jaguar had finally supplanted the Hellbringer in most Homeworld Clans, save the Coyotes who remained loyal to redeeming the honor of the design. manufacturer:Huntress Manufacturing Plant DL-6 primaryfactory:Huntress systemmanufacturer:CHASSIS:CSJ Type 65.43 Endo diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 17/Panther PNT-14R.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 17/Panther PNT-14R.mtf index 198f605d4..9fb9b91c4 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 17/Panther PNT-14R.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 17/Panther PNT-14R.mtf @@ -159,7 +159,7 @@ capabilities:Luckily the Panther had also proved itself to be quite hardy, sport deployment:This Dark Age variant carries an ER PPC and a Clan-spec Streak SRM-4 in the center torso. A standard fusion engine retains the typical speed of 64km/h, but a Supercharger does allow the 'Mech to sprint at 86km/h. Ten Clan-spec double heat sinks are carried. Protection is provided by carrying the maximum amount of Ballistic Reinforced Armor the endo steel chassis can carry. The Streak ammo is carried in a CASE protected bay in the left torso. -history:The original PNT-8Z model underwent a revision after the disastrous Battle of St. John in 2759, when it was revealed that its main weapon, a Tronel Large Laser, was inefficient in both range and firepower for the immense waste heat generated. The Draconis Combine inherited Alshain Weapons' Panther factory on New Oslo when the Star League dissolved and quickly put the production line to work building new Panthers for the DCMS. Their first large-scale use by Kurita warriors came during the First Succession War in the battle for Quentin, when the 2nd Legion of Vega used their Panthers to severely maul the slower, heavier 'Mechs of the 42nd Avalon Hussars while avoiding return fire. Throughout the Succession Wars, the Combine was the only significant user of the Panther, often pairing it with the Jenner in a deadly combination of speed and firepower; though the other Successor States employed Panthers in smaller numbers, these were either the result of battlefield salvage or older League-era 8Z models. The Panther also proved itself a deadly urban combatant, using its mobility to easily navigate the more restricted space of a city environment and take out heavier opponents from rooftop sniping perches with its main weapon. Lyran MechWarriors eventually took to nicknaming the 'Mech the "Alley Cat" for its propensity to conduct dark alley-way "muggings. Demand for the Panther continued to increase, forcing Alshain to build a secondary factory on Jarett to keep up. In an ironic twist both factories fell within the borders of the Free Rasalhague Republic following its creation in 3034, transferring ownership to the new state, and soon the Panther became a mainstay of the KungsArmé. The situation did not last long however following the invasion of the Clans, and both planets were swiftly conquered by Clan Ghost Bear. While Alshain Weapons crash-built a new line on Tok Do in 3053, they could not maintain their pre-invasion production levels and focused on spare parts and refit kits instead. Eventually Wakazashi Enterprises bought the production license for the Panther and began rolling out new variants from its New Samarkand factory. These have gone on to serve in every DCMS unit since, including the bloody years of the Jihad. +history:The original PNT-8Z model underwent a revision after the disastrous Battle of St. John in 2759, when it was revealed that its main weapon, a Tronel Large Laser, was inefficient in both range and firepower for the immense waste heat generated. The Draconis Combine inherited Alshain Weapons' Panther factory on New Oslo when the Star League dissolved and quickly put the production line to work building new Panthers for the DCMS. Their first large-scale use by Kurita warriors came during the First Succession War in the battle for Quentin, when the 2nd Legion of Vega used their Panthers to severely maul the slower, heavier 'Mechs of the 42nd Avalon Hussars while avoiding return fire. Throughout the Succession Wars, the Combine was the only significant user of the Panther, often pairing it with the Jenner in a deadly combination of speed and firepower; though the other Successor States employed Panthers in smaller numbers, these were either the result of battlefield salvage or older League-era 8Z models. The Panther also proved itself a deadly urban combatant, using its mobility to easily navigate the more restricted space of a city environment and take out heavier opponents from rooftop sniping perches with its main weapon. Lyran MechWarriors eventually took to nicknaming the 'Mech the "Alley Cat" for its propensity to conduct dark alley-way "muggings. Demand for the Panther continued to increase, forcing Alshain to build a secondary factory on Jarett to keep up. In an ironic twist both factories fell within the borders of the Free Rasalhague Republic following its creation in 3034, transferring ownership to the new state, and soon the Panther became a mainstay of the KungsArmé. The situation did not last long however following the invasion of the Clans, and both planets were swiftly conquered by Clan Ghost Bear. While Alshain Weapons crash-built a new line on Tok Do in 3053, they could not maintain their pre-invasion production levels and focused on spare parts and refit kits instead. Eventually Wakazashi Enterprises bought the production license for the Panther and began rolling out new variants from its New Samarkand factory. These have gone on to serve in every DCMS unit since, including the bloody years of the Jihad. manufacturer:Alshain Weapons,Luthien Armor Works,Alshain Weapons(formerly GK&T owned),Gorton, Kingsley, and Thorpe Enterprises ,Gorton, Kingsley, and Thorpe Enterprises, Wakazashi Enterprises primaryfactory:Alshain,Dieron,Jarett,New Oslo,New Oslo,New Samarkand diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 17/Wolfhound WLF-6S.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 17/Wolfhound WLF-6S.mtf index 277b6139d..ed4205672 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 17/Wolfhound WLF-6S.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 17/Wolfhound WLF-6S.mtf @@ -164,7 +164,7 @@ capabilities:Archon Katrina Steiner directed TharHes Industries to create a Batt deployment:A Dark Age variant, this Wolfhound carries an ER medium laser in each torso, while the center torso carries a small X-Pulse laser to cover the rear. The right arm is equipped with an Actuator Enhancement System to steady the large re-engineered laser that provides the bulk of the firepower. An XL engine is fitted and allows the Wolfhound to reach a top speed of 111 km/h. An endo steel chassis and light ferro-fibrous armor are fitted as well. -history:The Kell Hounds were the first unit chosen to field-test the Wolfhound in combat because of their intense loyalty to House Steiner, followed shortly after by Wolf's Dragoons. The design was put through its paces during the Fourth Succession War, where it outperformed all expectations. This was especially true when the Wolfhound faced its intended targets, hitting the Jenner beyond its capacity to return fire while closing the distance on the Panther to get inside range of its primary armament. After the war's triumphant conclusion, the Federated Commonwealth purchased more Wolfhounds to outfit its troops, and the design was utilized again during the War of 3039. Wolfhounds sustained substantially fewer deaths than other 'Mechs during that fight, and as a result, only a few were captured by the Combine. While awed by the 'Mech, the Kuritans were too proud to replicate it, instead relying on captured examples to help create the Wolf Trap particularly to defeat the 'Mech. Arc-Royal MechWorks was eventually recruited in to construct Wolfhounds under license from TharHes, and the recovery of lostech owing to the Helm Memory Core allowed for the production of a more advanced model to combat the Clan Invasion. Sadly, it took too long for TharHes' factories to be retooled in order to build the WLF-2 model, which was introduced in 3052, before ComStar ended the invasion with the Battle of Tukayyid. These updated Wolfhounds were still created for both FedCom member states, but once the Lyran Alliance was formed, TharHes manufacturers began creating the newer WLF-3S variant. This new type was only distributed to units loyal to the Lyran state, and so fought on Katherine Steiner-side Davion's during the FedCom Civil War. During the Jihad, the Word of Blake launched a crushing attack on Tharkad, essentially shutting down TharHes' Wolfhound factory line; in response, Arc-Royal expanded production and created the WLF-4 variant to compensate for allied troops combating the Blakists' losses. +history:The Kell Hounds were the first unit chosen to field-test the Wolfhound in combat because of their intense loyalty to House Steiner, followed shortly after by Wolf's Dragoons. The design was put through its paces during the Fourth Succession War, where it outperformed all expectations. This was especially true when the Wolfhound faced its intended targets, hitting the Jenner beyond its capacity to return fire while closing the distance on the Panther to get inside range of its primary armament. After the war's triumphant conclusion, the Federated Commonwealth purchased more Wolfhounds to outfit its troops, and the design was utilized again during the War of 3039. Wolfhounds sustained substantially fewer deaths than other 'Mechs during that fight, and as a result, only a few were captured by the Combine. While awed by the 'Mech, the Kuritans were too proud to replicate it, instead relying on captured examples to help create the Wolf Trap particularly to defeat the 'Mech. Arc-Royal MechWorks was eventually recruited in to construct Wolfhounds under license from TharHes, and the recovery of lostech owing to the Helm Memory Core allowed for the production of a more advanced model to combat the Clan Invasion. Sadly, it took too long for TharHes' factories to be retooled in order to build the WLF-2 model, which was introduced in 3052, before ComStar ended the invasion with the Battle of Tukayyid. These updated Wolfhounds were still created for both FedCom member states, but once the Lyran Alliance was formed, TharHes manufacturers began creating the newer WLF-3S variant. This new type was only distributed to units loyal to the Lyran state, and so fought on Katherine Steiner-Davion's side during the FedCom Civil War. During the Jihad, the Word of Blake launched a crushing attack on Tharkad, essentially shutting down TharHes' Wolfhound factory line; in response, Arc-Royal expanded production and created the WLF-4 variant to compensate for allied troops combating the Blakists' losses. manufacturer:TharHes Industries primaryfactory:Tharkad diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 18/Jenner JR7-N.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 18/Jenner JR7-N.mtf index d107624ea..505c9e249 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 18/Jenner JR7-N.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 18/Jenner JR7-N.mtf @@ -159,7 +159,7 @@ overview:The Jenner became the standard light warhorse of the DCMS with the outb capabilities:Five Smithson Lifter jump jets, two in each side torso and one in the center torso gave it a jumping distance of 150 meters, while its 245-rated Magna fusion engine allowed for a top speed of over 118 km/h, making it faster than most other 'Mechs. A favorite tactic of Jenner lances was to gang up on larger 'Mechs and unleash a devastating alpha strike. One or two of the 'Mechs would be equipped with inferno rounds, so even if the enemy survived the first strike they were badly damaged and running hot, allowing the Jenners to jump to safety and cool down themselves. A few seconds later the attack would be repeated until finally, the enemy was dead. It was also common practice to pair the Jenner with another Combine 'Mech, the Panther, creating a deadly combination of sheer speed and firepower with the slower Panther provided cover fire for the Jenner's flanking attack. The Jenner was such a favorite among Kurita MechWarriors that it became the benchmark against which all other newly designed Combine 'Mechs were compared. -history:The Jenner became the standard light warhorse of the DCMS with the outbreak of the First Succession War, though its reputation would be forever tarnished following its role in the Kentares Massacre. The Jenner became the standard light warhorse of the DCMS with the outbreak of the First Succession War, though its reputation would be forever tarnished following its role in the Kentares Massacre. Construction of new Jenners continued at Diplan MechYard's factory on Ozawa until a raw mineral shortage caused a halt in 2815, though they continued to produce new chassis. In 2823 production resumed on Ozawa, with some three thousand chassis shipped to Diplan's subsidiary on Luthien for final assembly, which itself was retooling to begin full-scale production; by 2830 both production lines were producing 1,350 Jenners a year. The sheer destruction of the Succession Wars finally took their toll when the last Jenner factory was destroyed in 2848, though so many Jenners had been produced by then that nearly every DCMS battalion had at least one of these 'Mechs well into the War of 3039. While the other Successor States eventually managed to procure operational Jenners (every AFFS regiment along the Combine border had at least one), the design remained in predominant use by House Kurita. +history:Construction of new Jenners continued at Diplan MechYard's factory on Ozawa until a raw mineral shortage caused a halt in 2815, though they continued to produce new chassis. In 2823 production resumed on Ozawa, with some three thousand chassis shipped to Diplan's subsidiary on Luthien for final assembly, which itself was retooling to begin full-scale production; by 2830 both production lines were producing 1,350 Jenners a year. The sheer destruction of the Succession Wars finally took their toll when the last Jenner factory was destroyed in 2848, though so many Jenners had been produced by then that nearly every DCMS battalion had at least one of these 'Mechs well into the War of 3039. While the other Successor States eventually managed to procure operational Jenners (every AFFS regiment along the Combine border had at least one), the design remained in predominant use by House Kurita. manufacturer:Luthien Armor Works, Diplan 'Mechyards, Luthien Armor Works, Luthien Armor Works, Diplan 'Mechyards primaryfactory:Luthien, Abiy Adi, New Samarkand, Ozawa diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 18/Wolverine WVR-10D.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 18/Wolverine WVR-10D.mtf index d9e61069d..b6a5bbe39 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 18/Wolverine WVR-10D.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 18/Wolverine WVR-10D.mtf @@ -164,7 +164,7 @@ overview:The Wolverine commonly served as a heavy scout unit. Often deployed in capabilities:The autocannon, missile system and laser found on most Wolverines are all reliable and well-storied systems. Unfortunately, the jump jets suffer from an opposing reputation; the Northrup 12000's are underpowered and prone to breakdowns. The one defining system to be found on the Wolverine, however, are its superb Tek BattleCom and Garret T11-b communications systems. The comgear, regardless of the manufacturer, is well-shielded and features a multi-channel transmitter and receiver, making the Wolverine a powerful Command BattleMech for scouting formations. -history:A widespread part of every major military, the Wolverine has manufacturing plants scattered throughout the entire Inner Sphere. While certain states-notable the Free Worlds League-have larger numbers of the design, only the Capellans began facing a shortage of the Wolverine after the loss of their Nanking facilities. +history:A widespread part of every major military, the Wolverine has manufacturing plants scattered throughout the entire Inner Sphere. While certain states-notably the Free Worlds League-have larger numbers of the design, only the Capellans began facing a shortage of the Wolverine after the loss of their Nanking facilities. manufacturer:Gibson Federated BattleMechs (A Division of Free Worlds Defense Industries),Kallon Weapon Industries primaryfactory:Gibson,Thermopolis diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 18/Wolverine WVR-10R.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 18/Wolverine WVR-10R.mtf index 486130bcb..dd462dd5d 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 18/Wolverine WVR-10R.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 18/Wolverine WVR-10R.mtf @@ -165,7 +165,7 @@ overview:The Wolverine commonly served as a heavy scout unit. Often deployed in capabilities:The autocannon, missile system and laser found on most Wolverines are all reliable and well-storied systems. Unfortunately, the jump jets suffer from an opposing reputation; the Northrup 12000's are underpowered and prone to breakdowns. The one defining system to be found on the Wolverine, however, are its superb Tek BattleCom and Garret T11-b communications systems. The comgear, regardless of the manufacturer, is well-shielded and features a multi-channel transmitter and receiver, making the Wolverine a powerful Command BattleMech for scouting formations. -history:A widespread part of every major military, the Wolverine has manufacturing plants scattered throughout the entire Inner Sphere. While certain states-notable the Free Worlds League-have larger numbers of the design, only the Capellans began facing a shortage of the Wolverine after the loss of their Nanking facilities. +history:A widespread part of every major military, the Wolverine has manufacturing plants scattered throughout the entire Inner Sphere. While certain states-notably the Free Worlds League-have larger numbers of the design, only the Capellans began facing a shortage of the Wolverine after the loss of their Nanking facilities. manufacturer:Gibson Federated BattleMechs (A Division of Free Worlds Defense Industries),Kallon Weapon Industries primaryfactory:Gibson,Thermopolis diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 18/Wolverine WVR-10V2.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 18/Wolverine WVR-10V2.mtf index e4f8bad37..eb9ce3a42 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 18/Wolverine WVR-10V2.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 18/Wolverine WVR-10V2.mtf @@ -163,7 +163,7 @@ overview:The Wolverine commonly served as a heavy scout unit. Often deployed in capabilities:The autocannon, missile system and laser found on most Wolverines are all reliable and well-storied systems. Unfortunately, the jump jets suffer from an opposing reputation; the Northrup 12000's are underpowered and prone to breakdowns. The one defining system to be found on the Wolverine, however, are its superb Tek BattleCom and Garret T11-b communications systems. The comgear, regardless of the manufacturer, is well-shielded and features a multi-channel transmitter and receiver, making the Wolverine a powerful Command BattleMech for scouting formations. -history:A widespread part of every major military, the Wolverine has manufacturing plants scattered throughout the entire Inner Sphere. While certain states-notable the Free Worlds League-have larger numbers of the design, only the Capellans began facing a shortage of the Wolverine after the loss of their Nanking facilities. +history:A widespread part of every major military, the Wolverine has manufacturing plants scattered throughout the entire Inner Sphere. While certain states-notably the Free Worlds League-have larger numbers of the design, only the Capellans began facing a shortage of the Wolverine after the loss of their Nanking facilities. manufacturer:Gibson Federated BattleMechs (A Division of Free Worlds Defense Industries),Kallon Weapon Industries primaryfactory:Gibson,Thermopolis diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 18/Wolverine WVR-11M.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 18/Wolverine WVR-11M.mtf index 4210fd980..d6ba31921 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 18/Wolverine WVR-11M.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 18/Wolverine WVR-11M.mtf @@ -164,7 +164,7 @@ overview:The Wolverine commonly served as a heavy scout unit. Often deployed in capabilities:The autocannon, missile system and laser found on most Wolverines are all reliable and well-storied systems. Unfortunately, the jump jets suffer from an opposing reputation; the Northrup 12000's are underpowered and prone to breakdowns. The one defining system to be found on the Wolverine, however, are its superb Tek BattleCom and Garret T11-b communications systems. The comgear, regardless of the manufacturer, is well-shielded and features a multi-channel transmitter and receiver, making the Wolverine a powerful Command BattleMech for scouting formations. -history:A widespread part of every major military, the Wolverine has manufacturing plants scattered throughout the entire Inner Sphere. While certain states-notable the Free Worlds League-have larger numbers of the design, only the Capellans began facing a shortage of the Wolverine after the loss of their Nanking facilities. +history:A widespread part of every major military, the Wolverine has manufacturing plants scattered throughout the entire Inner Sphere. While certain states-notably the Free Worlds League-have larger numbers of the design, only the Capellans began facing a shortage of the Wolverine after the loss of their Nanking facilities. manufacturer:Gibson Federated BattleMechs (A Division of Free Worlds Defense Industries),Kallon Weapon Industries primaryfactory:Gibson,Thermopolis diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 18/Wolverine WVR-7D.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 18/Wolverine WVR-7D.mtf index 702f82de9..6f1925c98 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 18/Wolverine WVR-7D.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 18/Wolverine WVR-7D.mtf @@ -166,7 +166,7 @@ capabilities:The autocannon, missile system and laser found on most Wolverines a deployment:The 7D variant of the Wolverine is a major upgrade to the design introduced in 3050 by the Federated Suns' new Nanking factory. The standard engine on the 'Mech was replaced with a Nissan 275 XL version and the armor has been upgraded to Kallon Unity Weave Ferro-Fibrous material with an extra half-ton added. To increase the Wolverine's speed, MASC has been added, allowing it to move up to 108 km/h in bursts. Finally, the weapons payload has been upgraded as well. The autocannon has been upgraded to a General Motors Nova-5 Ultra Autocannon/5 and the medium laser is now a Sutel Precision Line Medium Pulse Laser. The design retains its jumping capability, as well as the SRM-6, although CASE now protects the SRM reloads. -history:A widespread part of every major military, the Wolverine has manufacturing plants scattered throughout the entire Inner Sphere. While certain states-notable the Free Worlds League-have larger numbers of the design, only the Capellans began facing a shortage of the Wolverine after the loss of their Nanking facilities. +history:A widespread part of every major military, the Wolverine has manufacturing plants scattered throughout the entire Inner Sphere. While certain states-notably the Free Worlds League-have larger numbers of the design, only the Capellans began facing a shortage of the Wolverine after the loss of their Nanking facilities. manufacturer:Kallon Weapon Industries primaryfactory:Nanking diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 18/Wolverine WVR-7K.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 18/Wolverine WVR-7K.mtf index f99558317..b3db259c0 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 18/Wolverine WVR-7K.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 18/Wolverine WVR-7K.mtf @@ -168,7 +168,7 @@ capabilities:The autocannon, missile system and laser found on most Wolverines a deployment:Another major upgrade of the Wolverine, this one for the Combine and first rolling off Marduk's production lines in 3050, the 7K model is also built with an XL Engine for power with the saved weight used to increase and upgrade its arsenal. The primary weapon is a Victory Drumbeat Large Pulse Laser and a Victory Throb Small Pulse Laser in the right arm, which is backed up by a medium pulse laser in the head and two Telos-6 SRM-6 launchers in the left and right torsos with one ton of reloads each. The 'Mech uses thirteen double heat sinks to dissipate the added heat from the laser arsenal. Additionally, the 7K does have jump jets and can jump up to 150 meters, and while still carrying standard armor it increases the amount by one and a half tons for added protection. -history:A widespread part of every major military, the Wolverine has manufacturing plants scattered throughout the entire Inner Sphere. While certain states-notable the Free Worlds League-have larger numbers of the design, only the Capellans began facing a shortage of the Wolverine after the loss of their Nanking facilities. +history:A widespread part of every major military, the Wolverine has manufacturing plants scattered throughout the entire Inner Sphere. While certain states-notably the Free Worlds League-have larger numbers of the design, only the Capellans began facing a shortage of the Wolverine after the loss of their Nanking facilities. manufacturer:Victory Industries (formerly Norse BattleMech Works) primaryfactory:Marduk diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 18/Wolverine WVR-7M.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 18/Wolverine WVR-7M.mtf index d86d889f3..d33a990e5 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 18/Wolverine WVR-7M.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 18/Wolverine WVR-7M.mtf @@ -168,7 +168,7 @@ capabilities:The autocannon, missile system and laser found on most Wolverines a deployment:The 7M variant of the Wolverine has aspects of both the 7D and the 7K versions but is much closer to the original model. Introduced by FWDI in 3050 the 'Mech uses an XL engine, which is augmented with MASC, so as to push the machine up to 108 km/h in bursts. The 7M has twelve double heat sinks and, for a weapons package, it carries two Diverse Optics Sunbeam ER Large Lasers in the right arm and two Magna 400P medium pulse lasers in the head mount while retaining the SRM-6 for close range work. -history:A widespread part of every major military, the Wolverine has manufacturing plants scattered throughout the entire Inner Sphere. While certain states-notable the Free Worlds League-have larger numbers of the design, only the Capellans began facing a shortage of the Wolverine after the loss of their Nanking facilities. +history:A widespread part of every major military, the Wolverine has manufacturing plants scattered throughout the entire Inner Sphere. While certain states-notably the Free Worlds League-have larger numbers of the design, only the Capellans began facing a shortage of the Wolverine after the loss of their Nanking facilities. manufacturer:Gibson Federated BattleMechs (A Division of Free Worlds Defense Industries),Kallon Weapon Industries primaryfactory:Gibson,Thermopolis diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 18/Wolverine WVR-7M2.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 18/Wolverine WVR-7M2.mtf index c77420396..7d0bdcca7 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 18/Wolverine WVR-7M2.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 18/Wolverine WVR-7M2.mtf @@ -165,7 +165,7 @@ overview:The Wolverine commonly served as a heavy scout unit. Often deployed in capabilities:The autocannon, missile system and laser found on most Wolverines are all reliable and well-storied systems. Unfortunately, the jump jets suffer from an opposing reputation; the Northrup 12000's are underpowered and prone to breakdowns. The one defining system to be found on the Wolverine, however, are its superb Tek BattleCom and Garret T11-b communications systems. The comgear, regardless of the manufacturer, is well-shielded and features a multi-channel transmitter and receiver, making the Wolverine a powerful Command BattleMech for scouting formations. -history:A widespread part of every major military, the Wolverine has manufacturing plants scattered throughout the entire Inner Sphere. While certain states-notable the Free Worlds League-have larger numbers of the design, only the Capellans began facing a shortage of the Wolverine after the loss of their Nanking facilities. +history:A widespread part of every major military, the Wolverine has manufacturing plants scattered throughout the entire Inner Sphere. While certain states-notably the Free Worlds League-have larger numbers of the design, only the Capellans began facing a shortage of the Wolverine after the loss of their Nanking facilities. manufacturer:Gibson Federated BattleMechs (A Division of Free Worlds Defense Industries),Kallon Weapon Industries primaryfactory:Gibson,Thermopolis diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 18/Wolverine WVR-9R.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 18/Wolverine WVR-9R.mtf index a58fdd48b..b4871ea24 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 18/Wolverine WVR-9R.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 18/Wolverine WVR-9R.mtf @@ -164,7 +164,7 @@ overview:The Wolverine commonly served as a heavy scout unit. Often deployed in capabilities:The autocannon, missile system and laser found on most Wolverines are all reliable and well-storied systems. Unfortunately, the jump jets suffer from an opposing reputation; the Northrup 12000's are underpowered and prone to breakdowns. The one defining system to be found on the Wolverine, however, are its superb Tek BattleCom and Garret T11-b communications systems. The comgear, regardless of the manufacturer, is well-shielded and features a multi-channel transmitter and receiver, making the Wolverine a powerful Command BattleMech for scouting formations. -history:A widespread part of every major military, the Wolverine has manufacturing plants scattered throughout the entire Inner Sphere. While certain states-notable the Free Worlds League-have larger numbers of the design, only the Capellans began facing a shortage of the Wolverine after the loss of their Nanking facilities. +history:A widespread part of every major military, the Wolverine has manufacturing plants scattered throughout the entire Inner Sphere. While certain states-notably the Free Worlds League-have larger numbers of the design, only the Capellans began facing a shortage of the Wolverine after the loss of their Nanking facilities. manufacturer:Gibson Federated BattleMechs (A Division of Free Worlds Defense Industries),Kallon Weapon Industries primaryfactory:Gibson,Thermopolis diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 19/Scorpion C.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 19/Scorpion C.mtf index c9ae7e671..96f36feb4 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 19/Scorpion C.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 19/Scorpion C.mtf @@ -156,7 +156,7 @@ IS Endo Steel -Empty- -Empty- -overview: Every company has their beginnings. Many know Brigadier Corporation as one of the industrial powerhouses of the Free Worlds League. But at first, Brigadier was little more than a contract manufacturer for existing Hegemony designs. Ambition—along with a healthy lust for profits—would eventually spurn Brigadier to lunge towards manufacturing their own in-house designs, which would be boldly launched with the Scorpion: a quad BattleMech. Though Dr. Harrison, a strong proponent for quad designs, claimed that his new Scorpion would revolutionize 'Mech warfare, the Scorpion turned out to be barely more than a boondoggle. Sales were low, and few mourned the loss of the main factory on Oliver when they were destroyed in 2837. +overview: Every company has their beginnings. Many know Brigadier Corporation as one of the industrial powerhouses of the Free Worlds League. But at first, Brigadier was little more than a contract manufacturer for existing Hegemony designs. Ambition—along with a healthy lust for profits—would eventually spurn Brigadier to lunge towards manufacturing their own in-house designs, which would be boldly launched with the Scorpion: a quad BattleMech. Though Dr. Harrison, a strong proponent for quad designs, claimed that his new Scorpion would revolutionize 'Mech warfare, the Scorpion turned out to be barely more than a boondoggle. Sales were low, and few mourned the loss of the main factory on Oliver when it was destroyed in 2837. capabilities: The Scorpion is typically armed with a reliable one-two weapon combination. A primary large energy weapon or autocannon opens up holes, while a missile weapon usually takes advantage of any exposed weaknesses. While powerful in theory, in practice the Scorpion mounts barely more firepower than 'Mechs twenty tons lighter. With armor coverage barely better than some light 'Mechs, a badly positioned Scorpion is easy prey for better-armed BattleMechs. Combined with the bucking, bumpy ride the Scorpion has to offer, few choose to voluntarily pilot the design. deployment: Scorpions can be found throughout every part of the Inner Sphere. They are not a common design, and the limitations of the Succession Wars lead many Successor States to neglect their Scorpions in favor of better, more reliable designs. Upgrade kits would eventually appear with the discovery of the Helm Core, which gradually lead to the base SCP-1N Scorpion remaining solely in the hands of poorer nations or mercenary commands. systemmanufacturer:CHASSIS:Brigadier diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 19/Scorpion SCP-1BR.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 19/Scorpion SCP-1BR.mtf index d4d016dfe..9c6434752 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 19/Scorpion SCP-1BR.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 19/Scorpion SCP-1BR.mtf @@ -154,7 +154,7 @@ IS Heavy Ferro-Fibrous -Empty- -Empty- -overview:Every company has their beginnings. Many know Brigadier Corporation as one of the industrial powerhouses of the Free Worlds League. But at first, Brigadier was little more than a contract manufacturer for existing Hegemony designs. Ambition—along with a healthy lust for profits—would eventually spurn Brigadier to lunge towards manufacturing their own in-house designs, which would be boldly launched with the Scorpion: a quad BattleMech. Though Dr. Harrison, a strong proponent for quad designs, claimed that his new Scorpion would revolutionize 'Mech warfare, the Scorpion turned out to be barely more than a boondoggle. Sales were low, and few mourned the loss of the main factory on Oliver when they were destroyed in 2837. +overview:Every company has their beginnings. Many know Brigadier Corporation as one of the industrial powerhouses of the Free Worlds League. But at first, Brigadier was little more than a contract manufacturer for existing Hegemony designs. Ambition—along with a healthy lust for profits—would eventually spurn Brigadier to lunge towards manufacturing their own in-house designs, which would be boldly launched with the Scorpion: a quad BattleMech. Though Dr. Harrison, a strong proponent for quad designs, claimed that his new Scorpion would revolutionize 'Mech warfare, the Scorpion turned out to be barely more than a boondoggle. Sales were low, and few mourned the loss of the main factory on Oliver when it was destroyed in 2837. capabilities:The Scorpion is typically armed with a reliable one-two weapon combination. A primary large energy weapon or autocannon opens up holes, while a missile weapon usually takes advantage of any exposed weaknesses. While powerful in theory, in practice the Scorpion mounts barely more firepower than 'Mechs twenty tons lighter. With armor coverage barely better than some light 'Mechs, a badly positioned Scorpion is easy prey for better-armed BattleMechs. Combined with the bucking, bumpy ride the Scorpion has to offer, few choose to voluntarily pilot the design. deployment:Scorpions can be found throughout every part of the Inner Sphere. They are not a common design, and the limitations of the Succession Wars lead many Successor States to neglect their Scorpions in favor of better, more reliable designs. Upgrade kits would eventually appear with the discovery of the Helm Core, which gradually lead to the base SCP-1N Scorpion remaining solely in the hands of poorer nations or mercenary commands. manufacturer:Bander BattleMechs diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 19/Scorpion SCP-1TB.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 19/Scorpion SCP-1TB.mtf index f35d504a7..2240bab9d 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 19/Scorpion SCP-1TB.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 19/Scorpion SCP-1TB.mtf @@ -155,7 +155,7 @@ Foot Actuator -Empty- -Empty- -overview: Every company has their beginnings. Many know Brigadier Corporation as one of the industrial powerhouses of the Free Worlds League. But at first, Brigadier was little more than a contract manufacturer for existing Hegemony designs. Ambition—along with a healthy lust for profits—would eventually spurn Brigadier to lunge towards manufacturing their own in-house designs, which would be boldly launched with the Scorpion: a quad BattleMech. Though Dr. Harrison, a strong proponent for quad designs, claimed that his new Scorpion would revolutionize 'Mech warfare, the Scorpion turned out to be barely more than a boondoggle. Sales were low, and few mourned the loss of the main factory on Oliver when they were destroyed in 2837. +overview: Every company has their beginnings. Many know Brigadier Corporation as one of the industrial powerhouses of the Free Worlds League. But at first, Brigadier was little more than a contract manufacturer for existing Hegemony designs. Ambition—along with a healthy lust for profits—would eventually spurn Brigadier to lunge towards manufacturing their own in-house designs, which would be boldly launched with the Scorpion: a quad BattleMech. Though Dr. Harrison, a strong proponent for quad designs, claimed that his new Scorpion would revolutionize 'Mech warfare, the Scorpion turned out to be barely more than a boondoggle. Sales were low, and few mourned the loss of the main factory on Oliver when it was destroyed in 2837. capabilities: The Scorpion is typically armed with a reliable one-two weapon combination. A primary large energy weapon or autocannon opens up holes, while a missile weapon usually takes advantage of any exposed weaknesses. While powerful in theory, in practice the Scorpion mounts barely more firepower than 'Mechs twenty tons lighter. With armor coverage barely better than some light 'Mechs, a badly positioned Scorpion is easy prey for better-armed BattleMechs. Combined with the bucking, bumpy ride the Scorpion has to offer, few choose to voluntarily pilot the design. deployment: Scorpions can be found throughout every part of the Inner Sphere. They are not a common design, and the limitations of the Succession Wars lead many Successor States to neglect their Scorpions in favor of better, more reliable designs. Upgrade kits would eventually appear with the discovery of the Helm Core, which gradually lead to the base SCP-1N Scorpion remaining solely in the hands of poorer nations or mercenary commands. systemmanufacturer:CHASSIS:Brigadier diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 19/Scorpion SCP-2N.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 19/Scorpion SCP-2N.mtf index 7d70bfeb5..8a52b653a 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 19/Scorpion SCP-2N.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 19/Scorpion SCP-2N.mtf @@ -157,7 +157,7 @@ IS Endo Steel -Empty- -Empty- -overview: Every company has their beginnings. Many know Brigadier Corporation as one of the industrial powerhouses of the Free Worlds League. But at first, Brigadier was little more than a contract manufacturer for existing Hegemony designs. Ambition—along with a healthy lust for profits—would eventually spurn Brigadier to lunge towards manufacturing their own in-house designs, which would be boldly launched with the Scorpion: a quad BattleMech. Though Dr. Harrison, a strong proponent for quad designs, claimed that his new Scorpion would revolutionize 'Mech warfare, the Scorpion turned out to be barely more than a boondoggle. Sales were low, and few mourned the loss of the main factory on Oliver when they were destroyed in 2837. +overview: Every company has their beginnings. Many know Brigadier Corporation as one of the industrial powerhouses of the Free Worlds League. But at first, Brigadier was little more than a contract manufacturer for existing Hegemony designs. Ambition—along with a healthy lust for profits—would eventually spurn Brigadier to lunge towards manufacturing their own in-house designs, which would be boldly launched with the Scorpion: a quad BattleMech. Though Dr. Harrison, a strong proponent for quad designs, claimed that his new Scorpion would revolutionize 'Mech warfare, the Scorpion turned out to be barely more than a boondoggle. Sales were low, and few mourned the loss of the main factory on Oliver when it was destroyed in 2837. capabilities: The Scorpion is typically armed with a reliable one-two weapon combination. A primary large energy weapon or autocannon opens up holes, while a missile weapon usually takes advantage of any exposed weaknesses. While powerful in theory, in practice the Scorpion mounts barely more firepower than 'Mechs twenty tons lighter. With armor coverage barely better than some light 'Mechs, a badly positioned Scorpion is easy prey for better-armed BattleMechs. Combined with the bucking, bumpy ride the Scorpion has to offer, few choose to voluntarily pilot the design. deployment: Scorpions can be found throughout every part of the Inner Sphere. They are not a common design, and the limitations of the Succession Wars lead many Successor States to neglect their Scorpions in favor of better, more reliable designs. Upgrade kits would eventually appear with the discovery of the Helm Core, which gradually lead to the base SCP-1N Scorpion remaining solely in the hands of poorer nations or mercenary commands. manufacturer:Brigadier Corporation diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 2/Ostscout OTT-12R.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 2/Ostscout OTT-12R.mtf index 5718ee6f3..a34f8a90a 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 2/Ostscout OTT-12R.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 2/Ostscout OTT-12R.mtf @@ -160,7 +160,7 @@ capabilities:The Ostscout is quick enough to escape most traps, and very few oth deployment:Spawned of an alliance between Kong and Clan Sea Fox, the 12R variant is outfitted with Stealth Armor technology and Clan weaponry. Clad in four and half tons of Starshield Ultra-Tech Stealth plating linked to a Guardian ECM Suite, the 12R is built around a VOX 280 Light Fusion Engine and a fragile Endo-Composite frame allowing it to carry a single Clan grade Series 7K Extended-Range Large Laser to strike its foes at range. -history:Starting in 2600 Ostmann built and sold the Ostscout to fulfill many armies' need for a swift reconnaissance 'Mech, but eventually found that demand was outstripping their production ability. Rather than sacrifice their popular Ostroc line of urban-combat 'Mechs, the company licensed Kong Interstellar to start building the 'Mech in 2700, an arrangement similar to that struck regarding the Ostsol. Kong would continue to build Ostscouts for the next hundred years until the destruction of their factory on Connaught at the outset of the Succession Wars. Deprive of the possibility of replacement, many commanders began to hoard their Ostscouts like valuable treasure, parceling them out only for special missions. Most Ostscout pilots would not even attempt to engage enemy 'Mechs, as the advanced sensor system became extremely rare and nearly impossible to replace. This unwillingness to put the 'Mech in danger meant many survived the Succession Wars in practically mint condition, although many which suffered damage to their advanced sensors were forced to replace them with inferior, albeit more robust, systems. Besides the Great Houses, ComStar also utilized the Ostscout, and in the aftermath of the Clan Invasion and ComStar Schism began developing a new Ostscout variant for their Com Guards. This new model would maintain the same maneuverability and intelligence-gathering capabilities of the original while improving its offensive and defensive capabilities. Debuting with success in 3064, within the next three years nearly half of all Com Guard Ostscouts had been upgraded to the new variant; however it was soon discovered that both the Lyran Alliance and Word of Blake were fielding their own updated Ostscouts identical to ComStar's. The intelligence leak would be confirmed and traced back to Dag Kesselring, former Precentor of the 66th Division, who passed on information about the program to both the Lyrans and Blakists. Used by both sides in the Blakist Jihad, the newborn Republic of the Sphere would maintain production of the 11J model Ostscout after the fall of Terra both for its own relatively limited needs as well as export sales to the Federated Suns and Lyran Commonwealth. Still produced during the Dark Age era, aside from the Krupp plant's combat focused Phoenix models both Kong Interstellar and Robinson Standard BattleWorks reintroduced variants that lean more heavily towards the original look and recon aspects of the venerable 7J model. +history:Starting in 2600 Ostmann built and sold the Ostscout to fulfill many armies' need for a swift reconnaissance 'Mech, but eventually found that demand was outstripping their production ability. Rather than sacrifice their popular Ostroc line of urban-combat 'Mechs, the company licensed Kong Interstellar to start building the 'Mech in 2700, an arrangement similar to that struck regarding the Ostsol. Kong would continue to build Ostscouts for the next hundred years until the destruction of their factory on Connaught at the outset of the Succession Wars. Deprived of the possibility of replacement, many commanders began to hoard their Ostscouts like valuable treasure, parceling them out only for special missions. Most Ostscout pilots would not even attempt to engage enemy 'Mechs, as the advanced sensor system became extremely rare and nearly impossible to replace. This unwillingness to put the 'Mech in danger meant many survived the Succession Wars in practically mint condition, although many which suffered damage to their advanced sensors were forced to replace them with inferior, albeit more robust, systems. Besides the Great Houses, ComStar also utilized the Ostscout, and in the aftermath of the Clan Invasion and ComStar Schism began developing a new Ostscout variant for their Com Guards. This new model would maintain the same maneuverability and intelligence-gathering capabilities of the original while improving its offensive and defensive capabilities. Debuting with success in 3064, within the next three years nearly half of all Com Guard Ostscouts had been upgraded to the new variant; however it was soon discovered that both the Lyran Alliance and Word of Blake were fielding their own updated Ostscouts identical to ComStar's. The intelligence leak would be confirmed and traced back to Dag Kesselring, former Precentor of the 66th Division, who passed on information about the program to both the Lyrans and Blakists. Used by both sides in the Blakist Jihad, the newborn Republic of the Sphere would maintain production of the 11J model Ostscout after the fall of Terra both for its own relatively limited needs as well as export sales to the Federated Suns and Lyran Commonwealth. Still produced during the Dark Age era, aside from the Krupp plant's combat focused Phoenix models both Kong Interstellar and Robinson Standard BattleWorks reintroduced variants that lean more heavily towards the original look and recon aspects of the venerable 7J model. manufacturer:Kong Interstellar Corporation primaryfactory:Connaught diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 2/Ostscout OTT-8J.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 2/Ostscout OTT-8J.mtf index d1769e40b..e8a683a0d 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 2/Ostscout OTT-8J.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 2/Ostscout OTT-8J.mtf @@ -162,7 +162,7 @@ capabilities:The Ostscout is quick enough to escape most traps, and very few oth deployment:The Ostscout highly prized by the Draconis Combine, the 8J model is manufactured by the captured Robinson plant, sharing many parts with RSBW's Ostsol line. Using the classic 7J model as a base, the 8J uses a GM 280-rated XL Engine to free up weight to upgrade its electronics suite to modern standards, being fitted with an Angel ECM Suite and Bloodhound Active Probe. Offensively the Tronel II is swapped for a Martell-X Medium X-Pulse Laser supported by Double Heat Sinks and six tons of StarGuard Ferro-Fibrous armor -history:Starting in 2600 Ostmann built and sold the Ostscout to fulfill many armies' need for a swift reconnaissance 'Mech, but eventually found that demand was outstripping their production ability. Rather than sacrifice their popular Ostroc line of urban-combat 'Mechs, the company licensed Kong Interstellar to start building the 'Mech in 2700, an arrangement similar to that struck regarding the Ostsol. Kong would continue to build Ostscouts for the next hundred years until the destruction of their factory on Connaught at the outset of the Succession Wars. Deprive of the possibility of replacement, many commanders began to hoard their Ostscouts like valuable treasure, parceling them out only for special missions. Most Ostscout pilots would not even attempt to engage enemy 'Mechs, as the advanced sensor system became extremely rare and nearly impossible to replace. This unwillingness to put the 'Mech in danger meant many survived the Succession Wars in practically mint condition, although many which suffered damage to their advanced sensors were forced to replace them with inferior, albeit more robust, systems. Besides the Great Houses, ComStar also utilized the Ostscout, and in the aftermath of the Clan Invasion and ComStar Schism began developing a new Ostscout variant for their Com Guards. This new model would maintain the same maneuverability and intelligence-gathering capabilities of the original while improving its offensive and defensive capabilities. Debuting with success in 3064, within the next three years nearly half of all Com Guard Ostscouts had been upgraded to the new variant; however it was soon discovered that both the Lyran Alliance and Word of Blake were fielding their own updated Ostscouts identical to ComStar's. The intelligence leak would be confirmed and traced back to Dag Kesselring, former Precentor of the 66th Division, who passed on information about the program to both the Lyrans and Blakists. Used by both sides in the Blakist Jihad, the newborn Republic of the Sphere would maintain production of the 11J model Ostscout after the fall of Terra both for its own relatively limited needs as well as export sales to the Federated Suns and Lyran Commonwealth. Still produced during the Dark Age era, aside from the Krupp plant's combat focused Phoenix models both Kong Interstellar and Robinson Standard BattleWorks reintroduced variants that lean more heavily towards the original look and recon aspects of the venerable 7J model. +history:Starting in 2600 Ostmann built and sold the Ostscout to fulfill many armies' need for a swift reconnaissance 'Mech, but eventually found that demand was outstripping their production ability. Rather than sacrifice their popular Ostroc line of urban-combat 'Mechs, the company licensed Kong Interstellar to start building the 'Mech in 2700, an arrangement similar to that struck regarding the Ostsol. Kong would continue to build Ostscouts for the next hundred years until the destruction of their factory on Connaught at the outset of the Succession Wars. Deprived of the possibility of replacement, many commanders began to hoard their Ostscouts like valuable treasure, parceling them out only for special missions. Most Ostscout pilots would not even attempt to engage enemy 'Mechs, as the advanced sensor system became extremely rare and nearly impossible to replace. This unwillingness to put the 'Mech in danger meant many survived the Succession Wars in practically mint condition, although many which suffered damage to their advanced sensors were forced to replace them with inferior, albeit more robust, systems. Besides the Great Houses, ComStar also utilized the Ostscout, and in the aftermath of the Clan Invasion and ComStar Schism began developing a new Ostscout variant for their Com Guards. This new model would maintain the same maneuverability and intelligence-gathering capabilities of the original while improving its offensive and defensive capabilities. Debuting with success in 3064, within the next three years nearly half of all Com Guard Ostscouts had been upgraded to the new variant; however it was soon discovered that both the Lyran Alliance and Word of Blake were fielding their own updated Ostscouts identical to ComStar's. The intelligence leak would be confirmed and traced back to Dag Kesselring, former Precentor of the 66th Division, who passed on information about the program to both the Lyrans and Blakists. Used by both sides in the Blakist Jihad, the newborn Republic of the Sphere would maintain production of the 11J model Ostscout after the fall of Terra both for its own relatively limited needs as well as export sales to the Federated Suns and Lyran Commonwealth. Still produced during the Dark Age era, aside from the Krupp plant's combat focused Phoenix models both Kong Interstellar and Robinson Standard BattleWorks reintroduced variants that lean more heavily towards the original look and recon aspects of the venerable 7J model. manufacturer:Robinson Standard BattleWorks primaryfactory:Robinson diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 2/UrbanMech UM-R96.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 2/UrbanMech UM-R96.mtf index ba0b9e47e..194f233d7 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 2/UrbanMech UM-R96.mtf +++ b/megameklab/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 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. manufacturer:Hellespont Industrials primaryfactory:Betelgeuse diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 2/Zeus ZEU-11S.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 2/Zeus ZEU-11S.mtf index 4ea7a6a43..8d0c9c157 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 2/Zeus ZEU-11S.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 2/Zeus ZEU-11S.mtf @@ -160,7 +160,7 @@ IS Ferro-Fibrous overview:The Zeus was first built by the Lyran Commonwealth in 2787, just as the First Succession War began. Built at the request of Lyran Commonwealth Armed Forces commanders for a new light-assault 'Mech designed to engage the enemy at long range and perform hit-and-run attacks. -capabilities:the Zeus is fast enough to keep up with most heavy 'Mechs, and with a sturdy frame, eleven and a half tons of standard armor and a versatile weapons array, is equally capable of defeating them. Its use of reliable, low-maintenance and easily modified systems at a time when most 'Mechs were built with cutting-edge technology also proved fortuitous, allowing the Zeus to be produced long after those advanced components had become Lostech. +capabilities:The Zeus is fast enough to keep up with most heavy 'Mechs, and with a sturdy frame, eleven and a half tons of standard armor and a versatile weapons array, is equally capable of defeating them. Its use of reliable, low-maintenance and easily modified systems at a time when most 'Mechs were built with cutting-edge technology also proved fortuitous, allowing the Zeus to be produced long after those advanced components had become Lostech. deployment:Combining the best features of the ZEU-9T and Zeus X program, ZEU-11S blurs the Inner Sphere/Clan-tech divide thanks to Defiance's introduction of Clan-grade production lines. Built upon the 9T's frame, the 11S uses a Clan XL engine instead of a light model to free up more weight at no increase in bulk. Offensively a left-arm mounted Inner Sphere Gauss Rifle is supported by an Artemis IV enhanced Clan LRM-15 in the right arm and a Clan ER Large in the left torso, alongside two Clan ER mediums, one forward facing in the center torso with a rear-facing one in the right torso. Carrying three tons each of Gauss and LRM reloads, even with the inclusion of a Beagle Active Probe, the 11S mounts CASE II in the left arm and right torso to shield against gauss or ammo detonations, along with an increased volume of IS standard ferro-fibrous armor protection. diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 21/Kodiak 6.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 21/Kodiak 6.mtf index 625ffcb00..06218d57b 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 21/Kodiak 6.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 21/Kodiak 6.mtf @@ -166,7 +166,7 @@ capabilities:Though not taken to the same extreme as other Clan Totem 'Mechs, th deployment:Unknown -history:The vast majority of Kodiaks are used by the Ghost Bears, and indeed was exclusive to them in the first years since its introduction. Of those which are found in other toumans, Clan Snow Raven has the largest share, payment for their help in relocating to the Inner Sphere, followed by Clan Goliath Scorpion and Clan Cloud Cobra. Among the Crusader Clans though, only Clan Ice Hellion fields a handful of these 'Mechs.[3] As a interesting note, and proof of the expansion of the Kodiak, at least two of these mechs were found in a Smoke Jaguar unit on planet Asgard, during Operation Bulldog. +history:The vast majority of Kodiaks are used by the Ghost Bears, and indeed was exclusive to them in the first years since its introduction. Of those which are found in other toumans, Clan Snow Raven has the largest share, payment for their help in relocating to the Inner Sphere, followed by Clan Goliath Scorpion and Clan Cloud Cobra. Among the Crusader Clans though, only Clan Ice Hellion fields a handful of these 'Mechs. As a interesting note, and proof of the expansion of the Kodiak, at least two of these mechs were found in a Smoke Jaguar unit on planet Asgard, during Operation Bulldog. manufacturer:Bergan Industries primaryfactory:Alshain diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 22/Battle Cobra F.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 22/Battle Cobra F.mtf index d3fdafcb0..a61cecab8 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 22/Battle Cobra F.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 22/Battle Cobra F.mtf @@ -159,7 +159,7 @@ capabilities:The Battle Cobra makes use of Endo Steel and Ferro-Fibrous technolo deployment:A mid-range Jump Jet equipped brawler, the F config mounts an Ultra AC/5 and single ton of reloads in its right arm supported by a trio of ER Medium Lasers in its left. -history:The Battle Cobra prototypes were quickly redesigned to allow similar arm-mounted Omni-Pods, debuting only a few years later. Like the Crossbow, the Battle Cobra does not mount fixed jump jets and cannot mount them in their arms - therefore, early Battle Cobras would not be jump-capable. The first of the design saw deployment in 2873, and even though all of its weapon mounts are in the arms, this 'Mech has been in production ever since. However, the 'Mech's production facilities in Clan Space would end up being destroyed during the Annihilation of of Clan Steel Viper in 3075 on New Kent. +history:The Battle Cobra prototypes were quickly redesigned to allow similar arm-mounted Omni-Pods, debuting only a few years later. Like the Crossbow, the Battle Cobra does not mount fixed jump jets and cannot mount them in their arms - therefore, early Battle Cobras would not be jump-capable. The first of the design saw deployment in 2873, and even though all of its weapon mounts are in the arms, this 'Mech has been in production ever since. However, the 'Mech's production facilities in Clan Space would end up being destroyed during the Annihilation of of Clan Steel Viper in 3075 on New Kent. manufacturer:Novy Minsky Armaments Plant primaryfactory:New Kent diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 22/Battle Cobra G.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 22/Battle Cobra G.mtf index 88a845028..d741169b3 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 22/Battle Cobra G.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 22/Battle Cobra G.mtf @@ -161,7 +161,7 @@ capabilities:The Battle Cobra makes use of Endo Steel and Ferro-Fibrous technolo deployment:Unknown -history:The Battle Cobra prototypes were quickly redesigned to allow similar arm-mounted Omni-Pods, debuting only a few years later. Like the Crossbow, the Battle Cobra does not mount fixed jump jets and cannot mount them in their arms - therefore, early Battle Cobras would not be jump-capable. The first of the design saw deployment in 2873, and even though all of its weapon mounts are in the arms, this 'Mech has been in production ever since. However, the 'Mech's production facilities in Clan Space would end up being destroyed during the Annihilation of of Clan Steel Viper in 3075 on New Kent. +history:The Battle Cobra prototypes were quickly redesigned to allow similar arm-mounted Omni-Pods, debuting only a few years later. Like the Crossbow, the Battle Cobra does not mount fixed jump jets and cannot mount them in their arms - therefore, early Battle Cobras would not be jump-capable. The first of the design saw deployment in 2873, and even though all of its weapon mounts are in the arms, this 'Mech has been in production ever since. However, the 'Mech's production facilities in Clan Space would end up being destroyed during the Annihilation of of Clan Steel Viper in 3075 on New Kent. manufacturer:Arc-Royal MechWorks primaryfactory:Arc-Royal diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 22/Battle Cobra I.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 22/Battle Cobra I.mtf index 5c3c5bd4b..af06fd869 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 22/Battle Cobra I.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 22/Battle Cobra I.mtf @@ -157,7 +157,7 @@ capabilities:The Battle Cobra makes use of Endo Steel and Ferro-Fibrous technolo deployment:Unknown -history:The Battle Cobra prototypes were quickly redesigned to allow similar arm-mounted Omni-Pods, debuting only a few years later. Like the Crossbow, the Battle Cobra does not mount fixed jump jets and cannot mount them in their arms - therefore, early Battle Cobras would not be jump-capable. The first of the design saw deployment in 2873, and even though all of its weapon mounts are in the arms, this 'Mech has been in production ever since. However, the 'Mech's production facilities in Clan Space would end up being destroyed during the Annihilation of of Clan Steel Viper in 3075 on New Kent. +history:The Battle Cobra prototypes were quickly redesigned to allow similar arm-mounted Omni-Pods, debuting only a few years later. Like the Crossbow, the Battle Cobra does not mount fixed jump jets and cannot mount them in their arms - therefore, early Battle Cobras would not be jump-capable. The first of the design saw deployment in 2873, and even though all of its weapon mounts are in the arms, this 'Mech has been in production ever since. However, the 'Mech's production facilities in Clan Space would end up being destroyed during the Annihilation of of Clan Steel Viper in 3075 on New Kent. manufacturer:Arc-Royal MechWorks primaryfactory:Arc-Royal diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 22/Battle Cobra J.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 22/Battle Cobra J.mtf index b365aeff3..3f6495107 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 22/Battle Cobra J.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 22/Battle Cobra J.mtf @@ -158,7 +158,7 @@ capabilities:The Battle Cobra makes use of Endo Steel and Ferro-Fibrous technolo deployment:Unknown -history:The Battle Cobra prototypes were quickly redesigned to allow similar arm-mounted Omni-Pods, debuting only a few years later. Like the Crossbow, the Battle Cobra does not mount fixed jump jets and cannot mount them in their arms - therefore, early Battle Cobras would not be jump-capable. The first of the design saw deployment in 2873, and even though all of its weapon mounts are in the arms, this 'Mech has been in production ever since. However, the 'Mech's production facilities in Clan Space would end up being destroyed during the Annihilation of of Clan Steel Viper in 3075 on New Kent. +history:The Battle Cobra prototypes were quickly redesigned to allow similar arm-mounted Omni-Pods, debuting only a few years later. Like the Crossbow, the Battle Cobra does not mount fixed jump jets and cannot mount them in their arms - therefore, early Battle Cobras would not be jump-capable. The first of the design saw deployment in 2873, and even though all of its weapon mounts are in the arms, this 'Mech has been in production ever since. However, the 'Mech's production facilities in Clan Space would end up being destroyed during the Annihilation of of Clan Steel Viper in 3075 on New Kent. manufacturer:Arc-Royal MechWorks primaryfactory:Arc-Royal diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 22/Battle Cobra T.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 22/Battle Cobra T.mtf index 834b3d081..0682c8008 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 22/Battle Cobra T.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 22/Battle Cobra T.mtf @@ -159,7 +159,7 @@ capabilities:The Battle Cobra makes use of Endo Steel and Ferro-Fibrous technolo deployment:Unknown -history:The Battle Cobra prototypes were quickly redesigned to allow similar arm-mounted Omni-Pods, debuting only a few years later. Like the Crossbow, the Battle Cobra does not mount fixed jump jets and cannot mount them in their arms - therefore, early Battle Cobras would not be jump-capable. The first of the design saw deployment in 2873, and even though all of its weapon mounts are in the arms, this 'Mech has been in production ever since. However, the 'Mech's production facilities in Clan Space would end up being destroyed during the Annihilation of of Clan Steel Viper in 3075 on New Kent. +history:The Battle Cobra prototypes were quickly redesigned to allow similar arm-mounted Omni-Pods, debuting only a few years later. Like the Crossbow, the Battle Cobra does not mount fixed jump jets and cannot mount them in their arms - therefore, early Battle Cobras would not be jump-capable. The first of the design saw deployment in 2873, and even though all of its weapon mounts are in the arms, this 'Mech has been in production ever since. However, the 'Mech's production facilities in Clan Space would end up being destroyed during the Annihilation of of Clan Steel Viper in 3075 on New Kent. manufacturer:Arc-Royal MechWorks primaryfactory:Arc-Royal diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 22/Battle Cobra X.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 22/Battle Cobra X.mtf index 7d802ff2a..7310d135b 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 22/Battle Cobra X.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 22/Battle Cobra X.mtf @@ -160,7 +160,7 @@ capabilities:The Battle Cobra makes use of Endo Steel and Ferro-Fibrous technolo deployment:A Jihad era Experimental Technology config, the Battle Cobra X mounts five Improved Heavy Medium Lasers linked to a Targeting Computer and supported by eight additional double heat sinks -history:The Battle Cobra prototypes were quickly redesigned to allow similar arm-mounted Omni-Pods, debuting only a few years later. Like the Crossbow, the Battle Cobra does not mount fixed jump jets and cannot mount them in their arms - therefore, early Battle Cobras would not be jump-capable. The first of the design saw deployment in 2873, and even though all of its weapon mounts are in the arms, this 'Mech has been in production ever since. However, the 'Mech's production facilities in Clan Space would end up being destroyed during the Annihilation of of Clan Steel Viper in 3075 on New Kent. +history:The Battle Cobra prototypes were quickly redesigned to allow similar arm-mounted Omni-Pods, debuting only a few years later. Like the Crossbow, the Battle Cobra does not mount fixed jump jets and cannot mount them in their arms - therefore, early Battle Cobras would not be jump-capable. The first of the design saw deployment in 2873, and even though all of its weapon mounts are in the arms, this 'Mech has been in production ever since. However, the 'Mech's production facilities in Clan Space would end up being destroyed during the Annihilation of of Clan Steel Viper in 3075 on New Kent. manufacturer:Novy Minsky Armaments Plant primaryfactory:New Kent diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 24/Annihilator ANH-5W.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 24/Annihilator ANH-5W.mtf index 77948f3ba..aed53a1f8 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 24/Annihilator ANH-5W.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 24/Annihilator ANH-5W.mtf @@ -162,7 +162,7 @@ Clan Endo Steel overview:Originally developed in the final year of the Amaris Civil War as the ultimate fixed position city defense BattleMech. -capabilities:The Annihilator is armed with an arsenal that is built to instill fear in an enemy as much as damage them. The 100-ton 'Mech has a maximum speed of 32.4 km/h, making it one of the slowest 'Mechs ever designed together with the UrbanMech. It is by no means intended to use speed to outmaneuver an enemy, instead depending on its twelve and a half tons of armor to weather any fire that is directed at the 'Mech. +capabilities:The Annihilator is armed with an arsenal that is built to instill fear in an enemy as much as damage them. The 100-ton 'Mech has a maximum speed of 32.4 km/h, making it one of the slowest 'Mechs ever designed together with the UrbanMech. It is by no means intended to use speed to outmaneuver an enemy, instead depending on its twelve and a half tons of armor to weather any fire that is directed at the 'Mech. deployment:Unknown diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 24/Atlas AS7-K-DC.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 24/Atlas AS7-K-DC.mtf index 7bf6daee7..444420006 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 24/Atlas AS7-K-DC.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 24/Atlas AS7-K-DC.mtf @@ -162,7 +162,7 @@ Heat Sink -Empty- overview:"A 'Mech as powerful as possible, as impenetrable as possible, and as ugly and foreboding as conceivable, so that fear itself will be our ally.”-Aleksandr Kerensky -capabilities:The Atlas is probably the best-known BattleMech to ever set foot on the modern battlefield. Designed with specifications from Aleksandr Kerensky himself in 2755 in the midst of the Cameron Edicts, the Atlas was originally intended to ensure SLDF superiority over the Star League member states. Carrying the largest LRM launcher, the largest autocannon, and the largest SRM launcher possible, the Atlas can deal frightening amounts of damage in short amounts of time. Often used as a command vehicle, the Atlas mounts an advanced antenna and communications array, allowing it to engage in surface-to space communications in real time. The massive 19-ton hide of armor that protects the Atlas makes it a difficult foe to take down. Indeed, most MechWarriors choose to fall back rather than face one head-one, as its lumbering gait mean it can rarely catch up to other 'Mechs that choose to flee it. A full year of development went into crafting the famous "Death's Head" of the 'Mech to achieve the perfect ratio of functionality and fear. The head is also quite roomy and allows a small satellite dish to be mounted for surface-to-space communications. During combat the pilot can easily fold up the dish and store it within a protective portion of the head. +capabilities:The Atlas is probably the best-known BattleMech to ever set foot on the modern battlefield. Designed with specifications from Aleksandr Kerensky himself in 2755 in the midst of the Cameron Edicts, the Atlas was originally intended to ensure SLDF superiority over the Star League member states. Carrying the largest LRM launcher, the largest autocannon, and the largest SRM launcher possible, the Atlas can deal frightening amounts of damage in short amounts of time. Often used as a command vehicle, the Atlas mounts an advanced antenna and communications array, allowing it to engage in surface-to-space communications in real time. The massive 19-ton hide of armor that protects the Atlas makes it a difficult foe to take down. Indeed, most MechWarriors choose to fall back rather than face one head-on, as its lumbering gait means it can rarely catch up to other 'Mechs that choose to flee it. A full year of development went into crafting the famous "Death's Head" of the 'Mech to achieve the perfect ratio of functionality and fear. The head is also quite roomy and allows a small satellite dish to be mounted for surface-to-space communications. During combat the pilot can easily fold up the dish and store it within a protective portion of the head. deployment:Introduced in 3050, this variant trades one of the rear-mounted Medium Pulse Lasers and one ton of LRM ammunition for a Command Console. history:Though the inexorable arming of the Great Houses continued, the Atlas proved itself to be everything General Kerensky requested. With the largest amount of armor of nearly any 'Mech, crippling firepower, and the foreboding skull-shaped "Death's Head" cockpit/head assembly, the Atlas lived up to its reputation. The mere sight of an Atlas had been known to make even a veteran MechWarrior break out in a cold sweat, and theoretically a single Atlas can take on and wipe out an entire battalion of Stingers in exchange for minor armor loss. The Atlas' first combat trials came during the Amaris Civil War, where it served an instrumental role as a powerful command vehicle. Though General Kerensky is well-known for being the one who kicked down the palace doors of the Usurper in his Orion, it was his close friend Aaron DeChavilier who, in his Atlas, weathered the storm of enemy fire and breached the protective wall surrounding the complex. After this conflict it was therefore with little surprise that the General wished for all of these 'Mechs to accompany him on Operation Exodus, but ironically of those MechWarriors who refused his summons fully two-thirds were Atlas pilots. These units were spread among the Successor States and Atlas factories on Al Na'ir, Hesperus II and Quentin would continue production of the 'Mech through the Succession Wars. manufacturer:Field Refit diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 24/Atlas AS7-S3-DC.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 24/Atlas AS7-S3-DC.mtf index f6e5554f6..1519f0ab5 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 24/Atlas AS7-S3-DC.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 24/Atlas AS7-S3-DC.mtf @@ -162,7 +162,7 @@ Foot Actuator -Empty- overview:"A 'Mech as powerful as possible, as impenetrable as possible, and as ugly and foreboding as conceivable, so that fear itself will be our ally.”-Aleksandr Kerensky -capabilities:The Atlas is probably the best-known BattleMech to ever set foot on the modern battlefield. Designed with specifications from Aleksandr Kerensky himself in 2755 in the midst of the Cameron Edicts, the Atlas was originally intended to ensure SLDF superiority over the Star League member states. Carrying the largest LRM launcher, the largest autocannon, and the largest SRM launcher possible, the Atlas can deal frightening amounts of damage in short amounts of time. Often used as a command vehicle, the Atlas mounts an advanced antenna and communications array, allowing it to engage in surface-to space communications in real time. The massive 19-ton hide of armor that protects the Atlas makes it a difficult foe to take down. Indeed, most MechWarriors choose to fall back rather than face one head-one, as its lumbering gait mean it can rarely catch up to other 'Mechs that choose to flee it. A full year of development went into crafting the famous "Death's Head" of the 'Mech to achieve the perfect ratio of functionality and fear. The head is also quite roomy and allows a small satellite dish to be mounted for surface-to-space communications. During combat the pilot can easily fold up the dish and store it within a protective portion of the head. +capabilities:The Atlas is probably the best-known BattleMech to ever set foot on the modern battlefield. Designed with specifications from Aleksandr Kerensky himself in 2755 in the midst of the Cameron Edicts, the Atlas was originally intended to ensure SLDF superiority over the Star League member states. Carrying the largest LRM launcher, the largest autocannon, and the largest SRM launcher possible, the Atlas can deal frightening amounts of damage in short amounts of time. Often used as a command vehicle, the Atlas mounts an advanced antenna and communications array, allowing it to engage in surface-to-space communications in real time. The massive 19-ton hide of armor that protects the Atlas makes it a difficult foe to take down. Indeed, most MechWarriors choose to fall back rather than face one head-on, as its lumbering gait means it can rarely catch up to other 'Mechs that choose to flee it. A full year of development went into crafting the famous "Death's Head" of the 'Mech to achieve the perfect ratio of functionality and fear. The head is also quite roomy and allows a small satellite dish to be mounted for surface-to-space communications. During combat the pilot can easily fold up the dish and store it within a protective portion of the head. deployment:Unknown history:Though the inexorable arming of the Great Houses continued, the Atlas proved itself to be everything General Kerensky requested. With the largest amount of armor of nearly any 'Mech, crippling firepower, and the foreboding skull-shaped "Death's Head" cockpit/head assembly, the Atlas lived up to its reputation. The mere sight of an Atlas had been known to make even a veteran MechWarrior break out in a cold sweat, and theoretically a single Atlas can take on and wipe out an entire battalion of Stingers in exchange for minor armor loss. The Atlas' first combat trials came during the Amaris Civil War, where it served an instrumental role as a powerful command vehicle. Though General Kerensky is well-known for being the one who kicked down the palace doors of the Usurper in his Orion, it was his close friend Aaron DeChavilier who, in his Atlas, weathered the storm of enemy fire and breached the protective wall surrounding the complex. After this conflict it was therefore with little surprise that the General wished for all of these 'Mechs to accompany him on Operation Exodus, but ironically of those MechWarriors who refused his summons fully two-thirds were Atlas pilots. These units were spread among the Successor States and Atlas factories on Al Na'ir, Hesperus II and Quentin would continue production of the 'Mech through the Succession Wars. manufacturer:Defiance Industries diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 24/Atlas AS7-S3.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 24/Atlas AS7-S3.mtf index 969617be7..c09df435d 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 24/Atlas AS7-S3.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 24/Atlas AS7-S3.mtf @@ -163,7 +163,7 @@ Foot Actuator -Empty- overview:"A 'Mech as powerful as possible, as impenetrable as possible, and as ugly and foreboding as conceivable, so that fear itself will be our ally.”-Aleksandr Kerensky -capabilities:The Atlas is probably the best-known BattleMech to ever set foot on the modern battlefield. Designed with specifications from Aleksandr Kerensky himself in 2755 in the midst of the Cameron Edicts, the Atlas was originally intended to ensure SLDF superiority over the Star League member states. Carrying the largest LRM launcher, the largest autocannon, and the largest SRM launcher possible, the Atlas can deal frightening amounts of damage in short amounts of time. Often used as a command vehicle, the Atlas mounts an advanced antenna and communications array, allowing it to engage in surface-to space communications in real time. The massive 19-ton hide of armor that protects the Atlas makes it a difficult foe to take down. Indeed, most MechWarriors choose to fall back rather than face one head-one, as its lumbering gait mean it can rarely catch up to other 'Mechs that choose to flee it. A full year of development went into crafting the famous "Death's Head" of the 'Mech to achieve the perfect ratio of functionality and fear. The head is also quite roomy and allows a small satellite dish to be mounted for surface-to-space communications. During combat the pilot can easily fold up the dish and store it within a protective portion of the head. +capabilities:The Atlas is probably the best-known BattleMech to ever set foot on the modern battlefield. Designed with specifications from Aleksandr Kerensky himself in 2755 in the midst of the Cameron Edicts, the Atlas was originally intended to ensure SLDF superiority over the Star League member states. Carrying the largest LRM launcher, the largest autocannon, and the largest SRM launcher possible, the Atlas can deal frightening amounts of damage in short amounts of time. Often used as a command vehicle, the Atlas mounts an advanced antenna and communications array, allowing it to engage in surface-to-space communications in real time. The massive 19-ton hide of armor that protects the Atlas makes it a difficult foe to take down. Indeed, most MechWarriors choose to fall back rather than face one head-on, as its lumbering gait means it can rarely catch up to other 'Mechs that choose to flee it. A full year of development went into crafting the famous "Death's Head" of the 'Mech to achieve the perfect ratio of functionality and fear. The head is also quite roomy and allows a small satellite dish to be mounted for surface-to-space communications. During combat the pilot can easily fold up the dish and store it within a protective portion of the head. deployment:The S3 Atlas is a rearmament of the S2 version introduced in 3062. The Heavy Gauss Rifle is reduced to a standard model Gauss Rifle with sixteen shots while each arm contains a PPC and a Small Laser. An additional small laser is mounted in the head. For extra defense, an AMS is installed on the left arm. The Artemis IV-enhanced LRM-15 and Guardian ECM Suite of the S2 model remain. history:Though the inexorable arming of the Great Houses continued, the Atlas proved itself to be everything General Kerensky requested. With the largest amount of armor of nearly any 'Mech, crippling firepower, and the foreboding skull-shaped "Death's Head" cockpit/head assembly, the Atlas lived up to its reputation. The mere sight of an Atlas had been known to make even a veteran MechWarrior break out in a cold sweat, and theoretically a single Atlas can take on and wipe out an entire battalion of Stingers in exchange for minor armor loss. The Atlas' first combat trials came during the Amaris Civil War, where it served an instrumental role as a powerful command vehicle. Though General Kerensky is well-known for being the one who kicked down the palace doors of the Usurper in his Orion, it was his close friend Aaron DeChavilier who, in his Atlas, weathered the storm of enemy fire and breached the protective wall surrounding the complex. After this conflict it was therefore with little surprise that the General wished for all of these 'Mechs to accompany him on Operation Exodus, but ironically of those MechWarriors who refused his summons fully two-thirds were Atlas pilots. These units were spread among the Successor States and Atlas factories on Al Na'ir, Hesperus II and Quentin would continue production of the 'Mech through the Succession Wars. manufacturer:Defiance Industries diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 24/Atlas AS7-S4.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 24/Atlas AS7-S4.mtf index fb20006fb..2b6c25464 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 24/Atlas AS7-S4.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 24/Atlas AS7-S4.mtf @@ -162,7 +162,7 @@ IS Stealth -Empty- overview:"A 'Mech as powerful as possible, as impenetrable as possible, and as ugly and foreboding as conceivable, so that fear itself will be our ally.”-Aleksandr Kerensky -capabilities:The Atlas is probably the best-known BattleMech to ever set foot on the modern battlefield. Designed with specifications from Aleksandr Kerensky himself in 2755 in the midst of the Cameron Edicts, the Atlas was originally intended to ensure SLDF superiority over the Star League member states. Carrying the largest LRM launcher, the largest autocannon, and the largest SRM launcher possible, the Atlas can deal frightening amounts of damage in short amounts of time. Often used as a command vehicle, the Atlas mounts an advanced antenna and communications array, allowing it to engage in surface-to space communications in real time. The massive 19-ton hide of armor that protects the Atlas makes it a difficult foe to take down. Indeed, most MechWarriors choose to fall back rather than face one head-one, as its lumbering gait mean it can rarely catch up to other 'Mechs that choose to flee it. A full year of development went into crafting the famous "Death's Head" of the 'Mech to achieve the perfect ratio of functionality and fear. The head is also quite roomy and allows a small satellite dish to be mounted for surface-to-space communications. During combat the pilot can easily fold up the dish and store it within a protective portion of the head. +capabilities:The Atlas is probably the best-known BattleMech to ever set foot on the modern battlefield. Designed with specifications from Aleksandr Kerensky himself in 2755 in the midst of the Cameron Edicts, the Atlas was originally intended to ensure SLDF superiority over the Star League member states. Carrying the largest LRM launcher, the largest autocannon, and the largest SRM launcher possible, the Atlas can deal frightening amounts of damage in short amounts of time. Often used as a command vehicle, the Atlas mounts an advanced antenna and communications array, allowing it to engage in surface-to-space communications in real time. The massive 19-ton hide of armor that protects the Atlas makes it a difficult foe to take down. Indeed, most MechWarriors choose to fall back rather than face one head-on, as its lumbering gait means it can rarely catch up to other 'Mechs that choose to flee it. A full year of development went into crafting the famous "Death's Head" of the 'Mech to achieve the perfect ratio of functionality and fear. The head is also quite roomy and allows a small satellite dish to be mounted for surface-to-space communications. During combat the pilot can easily fold up the dish and store it within a protective portion of the head. deployment:Unknown history:Though the inexorable arming of the Great Houses continued, the Atlas proved itself to be everything General Kerensky requested. With the largest amount of armor of nearly any 'Mech, crippling firepower, and the foreboding skull-shaped "Death's Head" cockpit/head assembly, the Atlas lived up to its reputation. The mere sight of an Atlas had been known to make even a veteran MechWarrior break out in a cold sweat, and theoretically a single Atlas can take on and wipe out an entire battalion of Stingers in exchange for minor armor loss. The Atlas' first combat trials came during the Amaris Civil War, where it served an instrumental role as a powerful command vehicle. Though General Kerensky is well-known for being the one who kicked down the palace doors of the Usurper in his Orion, it was his close friend Aaron DeChavilier who, in his Atlas, weathered the storm of enemy fire and breached the protective wall surrounding the complex. After this conflict it was therefore with little surprise that the General wished for all of these 'Mechs to accompany him on Operation Exodus, but ironically of those MechWarriors who refused his summons fully two-thirds were Atlas pilots. These units were spread among the Successor States and Atlas factories on Al Na'ir, Hesperus II and Quentin would continue production of the 'Mech through the Succession Wars. manufacturer:Defiance Industries diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 24/Atlas AS8-K.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 24/Atlas AS8-K.mtf index b0fd948f8..778dbe94c 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 24/Atlas AS8-K.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 24/Atlas AS8-K.mtf @@ -164,7 +164,7 @@ IS Ballistic-Reinforced -Empty- overview:"A 'Mech as powerful as possible, as impenetrable as possible, and as ugly and foreboding as conceivable, so that fear itself will be our ally.”-Aleksandr Kerensky -capabilities:The Atlas is probably the best-known BattleMech to ever set foot on the modern battlefield. Designed with specifications from Aleksandr Kerensky himself in 2755 in the midst of the Cameron Edicts, the Atlas was originally intended to ensure SLDF superiority over the Star League member states. Carrying the largest LRM launcher, the largest autocannon, and the largest SRM launcher possible, the Atlas can deal frightening amounts of damage in short amounts of time. Often used as a command vehicle, the Atlas mounts an advanced antenna and communications array, allowing it to engage in surface-to space communications in real time. The massive 19-ton hide of armor that protects the Atlas makes it a difficult foe to take down. Indeed, most MechWarriors choose to fall back rather than face one head-one, as its lumbering gait mean it can rarely catch up to other 'Mechs that choose to flee it. A full year of development went into crafting the famous "Death's Head" of the 'Mech to achieve the perfect ratio of functionality and fear. The head is also quite roomy and allows a small satellite dish to be mounted for surface-to-space communications. During combat the pilot can easily fold up the dish and store it within a protective portion of the head. +capabilities:The Atlas is probably the best-known BattleMech to ever set foot on the modern battlefield. Designed with specifications from Aleksandr Kerensky himself in 2755 in the midst of the Cameron Edicts, the Atlas was originally intended to ensure SLDF superiority over the Star League member states. Carrying the largest LRM launcher, the largest autocannon, and the largest SRM launcher possible, the Atlas can deal frightening amounts of damage in short amounts of time. Often used as a command vehicle, the Atlas mounts an advanced antenna and communications array, allowing it to engage in surface-to-space communications in real time. The massive 19-ton hide of armor that protects the Atlas makes it a difficult foe to take down. Indeed, most MechWarriors choose to fall back rather than face one head-on, as its lumbering gait means it can rarely catch up to other 'Mechs that choose to flee it. A full year of development went into crafting the famous "Death's Head" of the 'Mech to achieve the perfect ratio of functionality and fear. The head is also quite roomy and allows a small satellite dish to be mounted for surface-to-space communications. During combat the pilot can easily fold up the dish and store it within a protective portion of the head. deployment:Unknown history:Though the inexorable arming of the Great Houses continued, the Atlas proved itself to be everything General Kerensky requested. With the largest amount of armor of nearly any 'Mech, crippling firepower, and the foreboding skull-shaped "Death's Head" cockpit/head assembly, the Atlas lived up to its reputation. The mere sight of an Atlas had been known to make even a veteran MechWarrior break out in a cold sweat, and theoretically a single Atlas can take on and wipe out an entire battalion of Stingers in exchange for minor armor loss. The Atlas' first combat trials came during the Amaris Civil War, where it served an instrumental role as a powerful command vehicle. Though General Kerensky is well-known for being the one who kicked down the palace doors of the Usurper in his Orion, it was his close friend Aaron DeChavilier who, in his Atlas, weathered the storm of enemy fire and breached the protective wall surrounding the complex. After this conflict it was therefore with little surprise that the General wished for all of these 'Mechs to accompany him on Operation Exodus, but ironically of those MechWarriors who refused his summons fully two-thirds were Atlas pilots. These units were spread among the Successor States and Atlas factories on Al Na'ir, Hesperus II and Quentin would continue production of the 'Mech through the Succession Wars. manufacturer:Independence Weaponry diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 24/Atlas AS8-KE.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 24/Atlas AS8-KE.mtf index f10c70f7d..8f5aec75e 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 24/Atlas AS8-KE.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 24/Atlas AS8-KE.mtf @@ -160,7 +160,7 @@ Foot Actuator -Empty- overview:"A 'Mech as powerful as possible, as impenetrable as possible, and as ugly and foreboding as conceivable, so that fear itself will be our ally.”-Aleksandr Kerensky -capabilities:The Atlas is probably the best-known BattleMech to ever set foot on the modern battlefield. Designed with specifications from Aleksandr Kerensky himself in 2755 in the midst of the Cameron Edicts, the Atlas was originally intended to ensure SLDF superiority over the Star League member states. Carrying the largest LRM launcher, the largest autocannon, and the largest SRM launcher possible, the Atlas can deal frightening amounts of damage in short amounts of time. Often used as a command vehicle, the Atlas mounts an advanced antenna and communications array, allowing it to engage in surface-to space communications in real time. The massive 19-ton hide of armor that protects the Atlas makes it a difficult foe to take down. Indeed, most MechWarriors choose to fall back rather than face one head-one, as its lumbering gait mean it can rarely catch up to other 'Mechs that choose to flee it. A full year of development went into crafting the famous "Death's Head" of the 'Mech to achieve the perfect ratio of functionality and fear. The head is also quite roomy and allows a small satellite dish to be mounted for surface-to-space communications. During combat the pilot can easily fold up the dish and store it within a protective portion of the head. +capabilities:The Atlas is probably the best-known BattleMech to ever set foot on the modern battlefield. Designed with specifications from Aleksandr Kerensky himself in 2755 in the midst of the Cameron Edicts, the Atlas was originally intended to ensure SLDF superiority over the Star League member states. Carrying the largest LRM launcher, the largest autocannon, and the largest SRM launcher possible, the Atlas can deal frightening amounts of damage in short amounts of time. Often used as a command vehicle, the Atlas mounts an advanced antenna and communications array, allowing it to engage in surface-to-space communications in real time. The massive 19-ton hide of armor that protects the Atlas makes it a difficult foe to take down. Indeed, most MechWarriors choose to fall back rather than face one head-on, as its lumbering gait means it can rarely catch up to other 'Mechs that choose to flee it. A full year of development went into crafting the famous "Death's Head" of the 'Mech to achieve the perfect ratio of functionality and fear. The head is also quite roomy and allows a small satellite dish to be mounted for surface-to-space communications. During combat the pilot can easily fold up the dish and store it within a protective portion of the head. deployment:Unknown history:Though the inexorable arming of the Great Houses continued, the Atlas proved itself to be everything General Kerensky requested. With the largest amount of armor of nearly any 'Mech, crippling firepower, and the foreboding skull-shaped "Death's Head" cockpit/head assembly, the Atlas lived up to its reputation. The mere sight of an Atlas had been known to make even a veteran MechWarrior break out in a cold sweat, and theoretically a single Atlas can take on and wipe out an entire battalion of Stingers in exchange for minor armor loss. The Atlas' first combat trials came during the Amaris Civil War, where it served an instrumental role as a powerful command vehicle. Though General Kerensky is well-known for being the one who kicked down the palace doors of the Usurper in his Orion, it was his close friend Aaron DeChavilier who, in his Atlas, weathered the storm of enemy fire and breached the protective wall surrounding the complex. After this conflict it was therefore with little surprise that the General wished for all of these 'Mechs to accompany him on Operation Exodus, but ironically of those MechWarriors who refused his summons fully two-thirds were Atlas pilots. These units were spread among the Successor States and Atlas factories on Al Na'ir, Hesperus II and Quentin would continue production of the 'Mech through the Succession Wars. manufacturer:Independence Weaponry diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 24/Atlas AS8-S.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 24/Atlas AS8-S.mtf index 34d30569a..c7db719ad 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 24/Atlas AS8-S.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 24/Atlas AS8-S.mtf @@ -161,7 +161,7 @@ ISImprovedHeavyGauss Ammo -Empty- overview:"A 'Mech as powerful as possible, as impenetrable as possible, and as ugly and foreboding as conceivable, so that fear itself will be our ally.”-Aleksandr Kerensky -capabilities:The Atlas is probably the best-known BattleMech to ever set foot on the modern battlefield. Designed with specifications from Aleksandr Kerensky himself in 2755 in the midst of the Cameron Edicts, the Atlas was originally intended to ensure SLDF superiority over the Star League member states. Carrying the largest LRM launcher, the largest autocannon, and the largest SRM launcher possible, the Atlas can deal frightening amounts of damage in short amounts of time. Often used as a command vehicle, the Atlas mounts an advanced antenna and communications array, allowing it to engage in surface-to space communications in real time. The massive 19-ton hide of armor that protects the Atlas makes it a difficult foe to take down. Indeed, most MechWarriors choose to fall back rather than face one head-one, as its lumbering gait mean it can rarely catch up to other 'Mechs that choose to flee it. A full year of development went into crafting the famous "Death's Head" of the 'Mech to achieve the perfect ratio of functionality and fear. The head is also quite roomy and allows a small satellite dish to be mounted for surface-to-space communications. During combat the pilot can easily fold up the dish and store it within a protective portion of the head. +capabilities:The Atlas is probably the best-known BattleMech to ever set foot on the modern battlefield. Designed with specifications from Aleksandr Kerensky himself in 2755 in the midst of the Cameron Edicts, the Atlas was originally intended to ensure SLDF superiority over the Star League member states. Carrying the largest LRM launcher, the largest autocannon, and the largest SRM launcher possible, the Atlas can deal frightening amounts of damage in short amounts of time. Often used as a command vehicle, the Atlas mounts an advanced antenna and communications array, allowing it to engage in surface-to-space communications in real time. The massive 19-ton hide of armor that protects the Atlas makes it a difficult foe to take down. Indeed, most MechWarriors choose to fall back rather than face one head-on, as its lumbering gait means it can rarely catch up to other 'Mechs that choose to flee it. A full year of development went into crafting the famous "Death's Head" of the 'Mech to achieve the perfect ratio of functionality and fear. The head is also quite roomy and allows a small satellite dish to be mounted for surface-to-space communications. During combat the pilot can easily fold up the dish and store it within a protective portion of the head. deployment:Unknown history:Though the inexorable arming of the Great Houses continued, the Atlas proved itself to be everything General Kerensky requested. With the largest amount of armor of nearly any 'Mech, crippling firepower, and the foreboding skull-shaped "Death's Head" cockpit/head assembly, the Atlas lived up to its reputation. The mere sight of an Atlas had been known to make even a veteran MechWarrior break out in a cold sweat, and theoretically a single Atlas can take on and wipe out an entire battalion of Stingers in exchange for minor armor loss. The Atlas' first combat trials came during the Amaris Civil War, where it served an instrumental role as a powerful command vehicle. Though General Kerensky is well-known for being the one who kicked down the palace doors of the Usurper in his Orion, it was his close friend Aaron DeChavilier who, in his Atlas, weathered the storm of enemy fire and breached the protective wall surrounding the complex. After this conflict it was therefore with little surprise that the General wished for all of these 'Mechs to accompany him on Operation Exodus, but ironically of those MechWarriors who refused his summons fully two-thirds were Atlas pilots. These units were spread among the Successor States and Atlas factories on Al Na'ir, Hesperus II and Quentin would continue production of the 'Mech through the Succession Wars. manufacturer:Defiance Industries diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 24/Atlas C 2.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 24/Atlas C 2.mtf index a8934ec12..01ae26945 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 24/Atlas C 2.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 24/Atlas C 2.mtf @@ -162,7 +162,7 @@ CLDoubleHeatSink -Empty- overview:"A 'Mech as powerful as possible, as impenetrable as possible, and as ugly and foreboding as conceivable, so that fear itself will be our ally.” -capabilities:The Atlas is probably the best-known BattleMech to ever set foot on the modern battlefield. Designed with specifications from Aleksandr Kerensky himself in 2755 in the midst of the Cameron Edicts, the Atlas was originally intended to ensure SLDF superiority over the Star League member states. Carrying the largest LRM launcher, the largest autocannon, and the largest SRM launcher possible, the Atlas can deal frightening amounts of damage in short amounts of time. Often used as a command vehicle, the Atlas mounts an advanced antenna and communications array, allowing it to engage in surface-to space communications in real time. The massive 19-ton hide of armor that protects the Atlas makes it a difficult foe to take down. Indeed, most MechWarriors choose to fall back rather than face one head-one, as its lumbering gait mean it can rarely catch up to other 'Mechs that choose to flee it. A full year of development went into crafting the famous "Death's Head" of the 'Mech to achieve the perfect ratio of functionality and fear. The head is also quite roomy and allows a small satellite dish to be mounted for surface-to-space communications. During combat the pilot can easily fold up the dish and store it within a protective portion of the head. +capabilities:The Atlas is probably the best-known BattleMech to ever set foot on the modern battlefield. Designed with specifications from Aleksandr Kerensky himself in 2755 in the midst of the Cameron Edicts, the Atlas was originally intended to ensure SLDF superiority over the Star League member states. Carrying the largest LRM launcher, the largest autocannon, and the largest SRM launcher possible, the Atlas can deal frightening amounts of damage in short amounts of time. Often used as a command vehicle, the Atlas mounts an advanced antenna and communications array, allowing it to engage in surface-to-space communications in real time. The massive 19-ton hide of armor that protects the Atlas makes it a difficult foe to take down. Indeed, most MechWarriors choose to fall back rather than face one head-on, as its lumbering gait means it can rarely catch up to other 'Mechs that choose to flee it. A full year of development went into crafting the famous "Death's Head" of the 'Mech to achieve the perfect ratio of functionality and fear. The head is also quite roomy and allows a small satellite dish to be mounted for surface-to-space communications. During combat the pilot can easily fold up the dish and store it within a protective portion of the head. deployment:A true Clan-tech retrofit of the AS7-D Atlas history:Though the inexorable arming of the Great Houses continued, the Atlas proved itself to be everything General Kerensky requested. With the largest amount of armor of nearly any 'Mech, crippling firepower, and the foreboding skull-shaped "Death's Head" cockpit/head assembly, the Atlas lived up to its reputation. The mere sight of an Atlas had been known to make even a veteran MechWarrior break out in a cold sweat, and theoretically a single Atlas can take on and wipe out an entire battalion of Stingers in exchange for minor armor loss. The Atlas' first combat trials came during the Amaris Civil War, where it served an instrumental role as a powerful command vehicle. Though General Kerensky is well-known for being the one who kicked down the palace doors of the Usurper in his Orion, it was his close friend Aaron DeChavilier who, in his Atlas, weathered the storm of enemy fire and breached the protective wall surrounding the complex. After this conflict it was therefore with little surprise that the General wished for all of these 'Mechs to accompany him on Operation Exodus, but ironically of those MechWarriors who refused his summons fully two-thirds were Atlas pilots. These units were spread among the Successor States and Atlas factories on Al Na'ir, Hesperus II and Quentin would continue production of the 'Mech through the Succession Wars. manufacturer:Field Refit diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 24/Atlas C 3.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 24/Atlas C 3.mtf index f6b062514..dcbb047ee 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 24/Atlas C 3.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 24/Atlas C 3.mtf @@ -159,7 +159,7 @@ CLDoubleHeatSink -Empty- overview:"A 'Mech as powerful as possible, as impenetrable as possible, and as ugly and foreboding as conceivable, so that fear itself will be our ally.” -capabilities:The Atlas is probably the best-known BattleMech to ever set foot on the modern battlefield. Designed with specifications from Aleksandr Kerensky himself in 2755 in the midst of the Cameron Edicts, the Atlas was originally intended to ensure SLDF superiority over the Star League member states. Carrying the largest LRM launcher, the largest autocannon, and the largest SRM launcher possible, the Atlas can deal frightening amounts of damage in short amounts of time. Often used as a command vehicle, the Atlas mounts an advanced antenna and communications array, allowing it to engage in surface-to space communications in real time. The massive 19-ton hide of armor that protects the Atlas makes it a difficult foe to take down. Indeed, most MechWarriors choose to fall back rather than face one head-one, as its lumbering gait mean it can rarely catch up to other 'Mechs that choose to flee it. A full year of development went into crafting the famous "Death's Head" of the 'Mech to achieve the perfect ratio of functionality and fear. The head is also quite roomy and allows a small satellite dish to be mounted for surface-to-space communications. During combat the pilot can easily fold up the dish and store it within a protective portion of the head. +capabilities:The Atlas is probably the best-known BattleMech to ever set foot on the modern battlefield. Designed with specifications from Aleksandr Kerensky himself in 2755 in the midst of the Cameron Edicts, the Atlas was originally intended to ensure SLDF superiority over the Star League member states. Carrying the largest LRM launcher, the largest autocannon, and the largest SRM launcher possible, the Atlas can deal frightening amounts of damage in short amounts of time. Often used as a command vehicle, the Atlas mounts an advanced antenna and communications array, allowing it to engage in surface-to-space communications in real time. The massive 19-ton hide of armor that protects the Atlas makes it a difficult foe to take down. Indeed, most MechWarriors choose to fall back rather than face one head-on, as its lumbering gait means it can rarely catch up to other 'Mechs that choose to flee it. A full year of development went into crafting the famous "Death's Head" of the 'Mech to achieve the perfect ratio of functionality and fear. The head is also quite roomy and allows a small satellite dish to be mounted for surface-to-space communications. During combat the pilot can easily fold up the dish and store it within a protective portion of the head. deployment:A true Clan-tech retrofit of the AS7-D Atlas history:Though the inexorable arming of the Great Houses continued, the Atlas proved itself to be everything General Kerensky requested. With the largest amount of armor of nearly any 'Mech, crippling firepower, and the foreboding skull-shaped "Death's Head" cockpit/head assembly, the Atlas lived up to its reputation. The mere sight of an Atlas had been known to make even a veteran MechWarrior break out in a cold sweat, and theoretically a single Atlas can take on and wipe out an entire battalion of Stingers in exchange for minor armor loss. The Atlas' first combat trials came during the Amaris Civil War, where it served an instrumental role as a powerful command vehicle. Though General Kerensky is well-known for being the one who kicked down the palace doors of the Usurper in his Orion, it was his close friend Aaron DeChavilier who, in his Atlas, weathered the storm of enemy fire and breached the protective wall surrounding the complex. After this conflict it was therefore with little surprise that the General wished for all of these 'Mechs to accompany him on Operation Exodus, but ironically of those MechWarriors who refused his summons fully two-thirds were Atlas pilots. These units were spread among the Successor States and Atlas factories on Al Na'ir, Hesperus II and Quentin would continue production of the 'Mech through the Succession Wars. manufacturer:Field Refit diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 24/Atlas C.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 24/Atlas C.mtf index 71afb17ed..c32730c83 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 24/Atlas C.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 24/Atlas C.mtf @@ -159,7 +159,7 @@ Heat Sink -Empty- overview:"A 'Mech as powerful as possible, as impenetrable as possible, and as ugly and foreboding as conceivable, so that fear itself will be our ally.” -capabilities:The Atlas is probably the best-known BattleMech to ever set foot on the modern battlefield. Designed with specifications from Aleksandr Kerensky himself in 2755 in the midst of the Cameron Edicts, the Atlas was originally intended to ensure SLDF superiority over the Star League member states. Carrying the largest LRM launcher, the largest autocannon, and the largest SRM launcher possible, the Atlas can deal frightening amounts of damage in short amounts of time. Often used as a command vehicle, the Atlas mounts an advanced antenna and communications array, allowing it to engage in surface-to space communications in real time. The massive 19-ton hide of armor that protects the Atlas makes it a difficult foe to take down. Indeed, most MechWarriors choose to fall back rather than face one head-one, as its lumbering gait mean it can rarely catch up to other 'Mechs that choose to flee it. A full year of development went into crafting the famous "Death's Head" of the 'Mech to achieve the perfect ratio of functionality and fear. The head is also quite roomy and allows a small satellite dish to be mounted for surface-to-space communications. During combat the pilot can easily fold up the dish and store it within a protective portion of the head. +capabilities:The Atlas is probably the best-known BattleMech to ever set foot on the modern battlefield. Designed with specifications from Aleksandr Kerensky himself in 2755 in the midst of the Cameron Edicts, the Atlas was originally intended to ensure SLDF superiority over the Star League member states. Carrying the largest LRM launcher, the largest autocannon, and the largest SRM launcher possible, the Atlas can deal frightening amounts of damage in short amounts of time. Often used as a command vehicle, the Atlas mounts an advanced antenna and communications array, allowing it to engage in surface-to-space communications in real time. The massive 19-ton hide of armor that protects the Atlas makes it a difficult foe to take down. Indeed, most MechWarriors choose to fall back rather than face one head-on, as its lumbering gait means it can rarely catch up to other 'Mechs that choose to flee it. A full year of development went into crafting the famous "Death's Head" of the 'Mech to achieve the perfect ratio of functionality and fear. The head is also quite roomy and allows a small satellite dish to be mounted for surface-to-space communications. During combat the pilot can easily fold up the dish and store it within a protective portion of the head. deployment:A Clan-tech retrofit of the AS7-D Atlas, the Atlas C replaced the older autocannon and missile launchers with a Clan standard Ultra AC/20, Swarm LRM compatible LRM-20, and Streak SRM-6 launchers; but the Inner Sphere Medium Lasers remained unchanged. Lighter Clan components allowed the Atlas C to carry 3 tons of autocannon ammunition. history:Though the inexorable arming of the Great Houses continued, the Atlas proved itself to be everything General Kerensky requested. With the largest amount of armor of nearly any 'Mech, crippling firepower, and the foreboding skull-shaped "Death's Head" cockpit/head assembly, the Atlas lived up to its reputation. The mere sight of an Atlas had been known to make even a veteran MechWarrior break out in a cold sweat, and theoretically a single Atlas can take on and wipe out an entire battalion of Stingers in exchange for minor armor loss. The Atlas' first combat trials came during the Amaris Civil War, where it served an instrumental role as a powerful command vehicle. Though General Kerensky is well-known for being the one who kicked down the palace doors of the Usurper in his Orion, it was his close friend Aaron DeChavilier who, in his Atlas, weathered the storm of enemy fire and breached the protective wall surrounding the complex. After this conflict it was therefore with little surprise that the General wished for all of these 'Mechs to accompany him on Operation Exodus, but ironically of those MechWarriors who refused his summons fully two-thirds were Atlas pilots. These units were spread among the Successor States and Atlas factories on Al Na'ir, Hesperus II and Quentin would continue production of the 'Mech through the Succession Wars. manufacturer:Field Refit diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 26/Flea FLE-21.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 26/Flea FLE-21.mtf index 5f1665d22..7d933771a 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 26/Flea FLE-21.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 26/Flea FLE-21.mtf @@ -157,7 +157,7 @@ IS Stealth overview:Focused on speed and firepower, the lightly armored Flea was an extremely rare sight until the arrival of the Wolf's Dragoons mercenary unit, with the design experiencing a revival as an inexpensive recon and anti-personnel militia 'Mech. capabilities:The Flea's inability to jump makes it difficult to navigate difficult terrain. Its incredible speed, on the other hand, ensures that few 'Mechs of any era can keep up with it in the open. While this Flea has more weaponry than its ultra-light predecessor, its armour is still incapable of withstanding direct combat. The Flea should only engage in hit and run attacks, with experienced MechWarriors focusing on the run aspect. Another specialty of the Flea, especially in large numbers, is incendiary operations behind enemy lines. deployment:No information available on current variant -history:Initially called the Trooper when it was introduced as the Free Worlds League's first light scout BattleMech in 2475, the design was so heavily flawed that it took 25 years before all the issues were corrected, with a new name selected to escape the bad press. The early prototype was designed by Colonel J. Marcus Llewelyn-Jaymes and his handpicked team at Toddlette Industries in a bid to create a dedicated reconnaissance BattleMech for the Free Worlds League Military. The design was considered highly maneuverable and lightweight at the time, and utilized a basic chassis similar to their larger WorkMechs; the 'Mech's systems appeared straightforward, with a power plant, gyroscope, cockpit, and other critical systems housed in an "armored-box" mounted on reinforced, armored "bird-walker" legs. Only with the help of Col. Llewelyn-Jaymes contacts in the military and government circles, and according to rumors, possible bribery of politicians and decision makers, the FWLM ultimately accepted delivery of the Trooper. While it was considered easy to maintain by technicians and logisticians, it wasn't long before it gained a poor reputation among those that piloted it. Since the design was based off their WorkMechs, it completely lacked any dedicated ejection mechanism, and forced pilots to manually exit should they become disabled. Additionally, the legs proved to be unable to cope with heavy combat, which became apparent in various failed trials before the FWLM's Minister of Defense. Despite these shortcomings, the League's Chief Armorer and Quartermaster General continued purchasing the prototype year after year. This ultimately led to the Trooper being selected as the very first FWLM 'Mech to be upgraded with "modern" technology in 2501 and rechristened as the FLE-4 Flea. While produced on and off until the early Succession Wars, excessive losses of the lightly armored design led Earthwerks to switch its production line to manufacturing heavier designs. This changed with the arrival of Wolf's Dragoons, who brought with them a large number of Fleas and reached an exclusive production arrangement with Earthwerks that resulted in the company opening new lines to replenish the Dragoons' losses in the Fourth Succession War.[9] With multiple lines on Asuncion, Bernardo and Victoria, after letting the Dragoons' exclusivity clause lapse, Earthwerks started selling the easy to manufacture, easy to maintain 'Mech by the DropShip load across the Inner Sphere. Originally produced exclusively for the Dragoons until the Capellan Confederation acquired the design's blueprints via a Maskirovka raid during the 3040s, the post–Helm Memory Core FLE-17 variant is based on the older FLE-15 model. Since the Dragoons used the Flea in a recon role more than an antipersonnel 'Mech, Earthwerks conceived a new design by incorporating recovered technology. Retaining the design's maximum speed of 97.2 km/h, the addition of an endo steel chassis frees up weight for a MASC system that allows the 'Mech's speed to be pushed up to 129.6 km/h in short bursts. The increase of speed is required to ensure survival on the modern battlefield, as the FLE-17 is only clad in a pitiful three tons of Livingston Ceramics armor plating. Once the FLE-17 plans were captured and the Dragoons' contract clause lapsed, Earthwerks began producing the new design almost exclusively for the Confederation until 3053, which saw use within their numerous militias. It was rarely seen among any of the other Great Houses' military, but some sightings did appear after on the mercenary markets with Dragoon serial numbers, which gave some credibility to reports of Wannamaker's Widowmakers operating an extensive salvage operation on Outreach. With the Confederation's later advances in stealth technology and light weaponry, the Flea became a logical test platform for new prototypes. These performed well, which encouraged Earthwerks to refit several older models. +history:Initially called the Trooper when it was introduced as the Free Worlds League's first light scout BattleMech in 2475, the design was so heavily flawed that it took 25 years before all the issues were corrected, with a new name selected to escape the bad press. The early prototype was designed by Colonel J. Marcus Llewelyn-Jaymes and his handpicked team at Toddlette Industries in a bid to create a dedicated reconnaissance BattleMech for the Free Worlds League Military. The design was considered highly maneuverable and lightweight at the time, and utilized a basic chassis similar to their larger WorkMechs; the 'Mech's systems appeared straightforward, with a power plant, gyroscope, cockpit, and other critical systems housed in an "armored-box" mounted on reinforced, armored "bird-walker" legs. Only with the help of Col. Llewelyn-Jaymes contacts in the military and government circles, and according to rumors, possible bribery of politicians and decision makers, the FWLM ultimately accepted delivery of the Trooper. While it was considered easy to maintain by technicians and logisticians, it wasn't long before it gained a poor reputation among those that piloted it. Since the design was based off their WorkMechs, it completely lacked any dedicated ejection mechanism, and forced pilots to manually exit should they become disabled. Additionally, the legs proved to be unable to cope with heavy combat, which became apparent in various failed trials before the FWLM's Minister of Defense. Despite these shortcomings, the League's Chief Armorer and Quartermaster General continued purchasing the prototype year after year. This ultimately led to the Trooper being selected as the very first FWLM 'Mech to be upgraded with "modern" technology in 2501 and rechristened as the FLE-4 Flea. While produced on and off until the early Succession Wars, excessive losses of the lightly armored design led Earthwerks to switch its production line to manufacturing heavier designs. This changed with the arrival of Wolf's Dragoons, who brought with them a large number of Fleas and reached an exclusive production arrangement with Earthwerks that resulted in the company opening new lines to replenish the Dragoons' losses in the Fourth Succession War. With multiple lines on Asuncion, Bernardo and Victoria, after letting the Dragoons' exclusivity clause lapse, Earthwerks started selling the easy to manufacture, easy to maintain 'Mech by the DropShip load across the Inner Sphere. Originally produced exclusively for the Dragoons until the Capellan Confederation acquired the design's blueprints via a Maskirovka raid during the 3040s, the post–Helm Memory Core FLE-17 variant is based on the older FLE-15 model. Since the Dragoons used the Flea in a recon role more than an antipersonnel 'Mech, Earthwerks conceived a new design by incorporating recovered technology. Retaining the design's maximum speed of 97.2 km/h, the addition of an endo steel chassis frees up weight for a MASC system that allows the 'Mech's speed to be pushed up to 129.6 km/h in short bursts. The increase of speed is required to ensure survival on the modern battlefield, as the FLE-17 is only clad in a pitiful three tons of Livingston Ceramics armor plating. Once the FLE-17 plans were captured and the Dragoons' contract clause lapsed, Earthwerks began producing the new design almost exclusively for the Confederation until 3053, which saw use within their numerous militias. It was rarely seen among any of the other Great Houses' military, but some sightings did appear after on the mercenary markets with Dragoon serial numbers, which gave some credibility to reports of Wannamaker's Widowmakers operating an extensive salvage operation on Outreach. With the Confederation's later advances in stealth technology and light weaponry, the Flea became a logical test platform for new prototypes. These performed well, which encouraged Earthwerks to refit several older models. manufacturer:Earthwerks-FWL, Inc., Earthwerks-FWL, Inc., Earthwerks Ltd. primaryfactory:Asuncion, Bernardo, Grand Base systemmanufacturer:CHASSIS:Earthwerk Trooper M diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 28/Cicada CDA-4A.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 28/Cicada CDA-4A.mtf index f1179fdd7..5bebd16a4 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 28/Cicada CDA-4A.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 28/Cicada CDA-4A.mtf @@ -151,9 +151,9 @@ Foot Actuator -Empty- overview:Designed as a supplement or replacement for the popular Locust scout ’Mech, the Cicada found limited use by the Star League after its introduction in 2740. -capabilities:The Cicada's main advantages are its speed and a lack of ammunition. A gigantic Pitban 320 engine, which accounts for more than half of the Cicada's entire mass, propels the 40-ton BattleMech to almost 130 kph. A trio of lasers, two medium and one small, providing the Cicada with ample firepower to take on the Cicada's chosen targets, the lighter 'Mechs. The lasers are implanted in the Cicada's armored midsection, beneath the toughest shielding the 'Mech mounts, however their shooting arcs are limited. A foe who is successful in getting behind the Cicada has little to fear. The rest of the 'Mech, however, is just minimally armored. Its limbs are vestigial—really, wings—and can only carry little armor. The Cicada's legs, while robust enough to carry the 'Mech at breakneck speeds, are also unarmored. +capabilities:The Cicada's main advantages are its speed and a lack of ammunition. A gigantic Pitban 320 engine, which accounts for more than half of the Cicada's entire mass, propels the 40-ton BattleMech to almost 130 kph. A trio of lasers, two medium and one small, provide the Cicada with ample firepower to take on its chosen targets: lighter 'Mechs. The lasers are implanted in the Cicada's armored midsection, beneath the toughest shielding the 'Mech mounts, however their shooting arcs are limited. A foe who is successful in getting behind the Cicada has little to fear. The rest of the 'Mech, however, is just minimally armored. Its limbs are vestigial—really, wings—and can only carry little armor. The Cicada's legs, while robust enough to carry the 'Mech at breakneck speeds, are also unarmored. deployment:No information on this variant -history:The Cicada was introduced amidst rising tensions in 2740 by HartfordCo Industries in an attempt to capitalize on the growing need for BattleMechs. At the time Bergan Industries had cornered the market in light recon 'Mechs with their Locust and HartfordCo's only prior experience was building communications and targeting systems. Nevertheless the company designed their 'Mech to compete directly with the Locust by making it just as fast but twice as large, allowing the Cicada to carry slightly better weaponry and give it an edge in physical combat, all while keeping costs down. The Star League was sufficiently impressed that they agreed to a limited contract with HartfordCo for a small number of Cicadas, using them to replace many Locusts lost in fighting along its border regions. The 'Mech's only major issue was faulty heat sinks, although these were eventually replaced in many models with modular sinks. With their base of operations and only Cicada factory located on Bryant, HartfordCo was among the many victims of the fall of the Star League and the onset of the Succession Wars. Although the factory was destroyed, there were a number of built Cicadas in storage on Bryant and its relative position compared to the five Successor States meant the planet was the target of many raids. Thus the Cicada found its way into all of the major House armies, where in service to the Successor Lords, the 'Mech earned a positive reputation. Unfortunately this also meant its expectations sometimes exceeded the design's actual capabilities, and, with no new models being produced, the Cicada's numbers began to dwindle. By the end of the Fourth Succession War the 'Mech was in danger of going extinct. The discovery of the Helm Memory Core allowed Free Worlds Defense Industries to save the Cicada by restarting production of the 'Mech from their newly-refurbished production line on Gibson. The great majority of these newly-built Cicadas went to the Free Worlds League Military, particularly federal units, which was in desperate need for recon 'Mechs after the loss of so many machines during their long battle with Andurien. The chassis was also the perfect platform to apply much of the now-recovered lostech and the improved CDA-3M was introduced shortly before the start of the Clan Invasion. New Cicadas were supplied to the Federated Commonwealth and Draconis Combine as part of an agreement to combat the Clans, and as reports filtered in from the front more variants of the 'Mech were produced. Following the ComStar Schism the Word of Blake relocated to Gibson and an increasing number of Cicada production was redirected to the Word of Blake Militia, which quickly rivaled the FWLM as the largest Cicada user. As such the 'Mech was found on both sides of the Jihad. +history:The Cicada was introduced amidst rising tensions in 2740 by HartfordCo Industries in an attempt to capitalize on the growing need for BattleMechs. At the time Bergan Industries had cornered the market in light recon 'Mechs with their Locust and HartfordCo's only prior experience was building communications and targeting systems. Nevertheless the company designed their 'Mech to compete directly with the Locust by making it just as fast but twice as large, allowing the Cicada to carry slightly better weaponry and give it an edge in physical combat, all while keeping costs down. The Star League was sufficiently impressed that they agreed to a limited contract with HartfordCo for a small number of Cicadas, using them to replace many Locusts lost in fighting along its border regions. The 'Mech's only major issue was faulty heat sinks, although these were eventually replaced in many models with modular sinks. With their base of operations and only Cicada factory located on Bryant, HartfordCo was among the many victims of the fall of the Star League and the onset of the Succession Wars. Although the factory was destroyed, there were a number of built Cicadas in storage on Bryant and its relative position compared to the five Successor States meant the planet was the target of many raids. Thus the Cicada found its way into all of the major House armies, where in service to the Successor Lords, the 'Mech earned a positive reputation. Unfortunately this also meant its expectations sometimes exceeded the design's actual capabilities, and, with no new models being produced, the Cicada's numbers began to dwindle. By the end of the Fourth Succession War the 'Mech was in danger of going extinct. The discovery of the Helm Memory Core allowed Free Worlds Defense Industries to save the Cicada by restarting production of the 'Mech from their newly-refurbished production line on Gibson. The great majority of these newly-built Cicadas went to the Free Worlds League Military, particularly federal units, which were in desperate need for recon 'Mechs after the loss of so many machines during their long battle with Andurien. The chassis was also the perfect platform to apply much of the now-recovered lostech and the improved CDA-3M was introduced shortly before the start of the Clan Invasion. New Cicadas were supplied to the Federated Commonwealth and Draconis Combine as part of an agreement to combat the Clans, and as reports filtered in from the front more variants of the 'Mech were produced. Following the ComStar Schism the Word of Blake relocated to Gibson and an increasing amount of Cicada production was redirected to the Word of Blake Militia, which quickly rivaled the FWLM as the largest Cicada user. As such the 'Mech was found on both sides of the Jihad. manufacturer:Westover BattleMechs primaryfactory:Westover systemmanufacturer:CHASSIS:Kell Reinforced 240 diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 28/Firestarter FS9-M 'Mirage II'.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 28/Firestarter FS9-M 'Mirage II'.mtf index 804463ac7..bbadfafde 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 28/Firestarter FS9-M 'Mirage II'.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 28/Firestarter FS9-M 'Mirage II'.mtf @@ -163,7 +163,7 @@ IS Endo-Composite overview:Originally intended as a mobile incendiary ’Mech, the Firestarter evolved into a decent scouting and reconnaissance platform. capabilities:Despite being shielded by five and a half tons of armor and capable of jumping 180 meters, the Firestarter was powerless against medium or heavyweight opponents. Instead, an entire strategy was built around its ability to cause wildfires, with strategically positioned blazes routing an opponent or covering a withdrawal and impeding any pursuit. Firestarter MechWarriors enjoyed setting fire to densely forested areas when enemy 'Mechs marched through them, as well as any buildings where the enemy was hiding. deployment:No information on this variant -history:Firestarters, both ancient and contemporary, can still be found in abundance among planetary militias and House troops. Even though Blakist forces have taken over CMW's principal plant on Coventry, spare parts are still accessible from other Firestarter producers (including LAW, Ceres Metals, Defiance, and Independence Weaponry). Loki field offices near the Circinus Federation frontier are concerned about reports of a new variety using endo steel technology on Federation- occupied worlds. With its particular load-out, this new variation appears to be designed to spread chaos and destruction. Firestarters have also been seen in Level II formations with Blakist soldiers in their Protectorate, most frequently at "police demonstrations" and guarding suspected prison sites. These versions are thought to be Coventry goods. +history:Firestarters, both ancient and contemporary, can still be found in abundance among planetary militias and House troops. Even though Blakist forces have taken over CMW's principal plant on Coventry, spare parts are still accessible from other Firestarter producers (including LAW, Ceres Metals, Defiance, and Independence Weaponry). Loki field offices near the Circinus Federation frontier are concerned about reports of a new variety using endo steel technology on Federation-occupied worlds. With its particular load-out, this new variation appears to be designed to spread chaos and destruction. Firestarters have also been seen in Level II formations with Blakist soldiers in their Protectorate, most frequently at "police demonstrations" and guarding suspected prison sites. These versions are thought to be Coventry goods. manufacturer:Defiance Industries primaryfactory:Kwangjong-ni systemmanufacturer:CHASSIS:Foundation Endo-Composite diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 29/Assassin ASN-109.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 29/Assassin ASN-109.mtf index 02257a1c8..7e3034824 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 29/Assassin ASN-109.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 29/Assassin ASN-109.mtf @@ -158,7 +158,7 @@ IS Stealth -Empty- overview:Many military finance experts outside the Star League saw the Assassin as more of a political pork project than a powerful fighting machine, yet it turned out to be a strong 'Mech in combat against light lances. -capabilities:The Assassin was able to destroy these lighter 'Mechs due to its good speed and maneuverability, good armor coverage (in comparison to the 'Mechs it was built to battle against), and strong weaponry. The weapons of the 'Mechs is essentially comprised of three systems: the long-range missile rack, the short-range missile rack, and the arm-mounted Martell midrange laser. The design is limited in durability unless assigned supply units for support because it can only carry a total of seventy-four salvos for both launchers. The most significant disadvantage for most pilots is the incredibly tight cockpit—one of the most confined cockpit designs in the Inner Sphere. +capabilities:The Assassin was able to destroy these lighter 'Mechs due to its good speed and maneuverability, good armor coverage (in comparison to the 'Mechs it was built to battle against), and strong weaponry. The weapons of the 'Mech is essentially comprised of three systems: the long-range missile rack, the short-range missile rack, and the arm-mounted Martell midrange laser. The design is limited in durability unless assigned supply units for support because it can only carry a total of seventy-four salvos for both launchers. The most significant disadvantage for most pilots is the incredibly tight cockpit—one of the most confined cockpit designs in the Inner Sphere. deployment:No Information on this variant history:Maltex has changed the cockpit cooling system dozens of times over the Assassin's four hundred year service history in a bid to provide extra elbow room, but none of the attempts have been effective. As a result, most pilots experience a tight, painful ride that limits in-cockpit time to half that of most other conventional designs; many ex-Assassin pilots have established a history of back issues that will bother them for the rest of their lives. The ammo feed system for the short-range missile rack was the only other issue with the Assassin (mostly those made up to 2815). It commonly failed during high-heat settings due to chronic jamming and could only be repaired through total disassembly in a mechanical bay. Under significant corporate pressure, Holly ultimately introduced a new feed system in 2815 and even paid several years of recall repairs; nonetheless, there are still a huge number of individually owned Assassins that may still mount the problematic system. Maltex produced only a few hundred ASN-21s after their launch. Due to a lack of spare parts, those Assassins in service were utilized sparingly, however House Marik enthusiastically used the 'Mech late in the Third Succession War. When a rush of new BattleMech types entered the markets after 3058, the Assassin was nearly phased out of service. Those that have stayed in service are usually family heirlooms with some modifications. manufacturer:Hellespont ’Mech Works diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 29/Charger C.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 29/Charger C.mtf index 6baa626dc..c5de90098 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 29/Charger C.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 29/Charger C.mtf @@ -155,7 +155,7 @@ Foot Actuator -Empty- overview:The Charger is seen as an example of abject failure in BattleMech design. Wells Technologies originally wanted to produce an ultra-heavy scout 'Mech for the Star League Defense Force that was not only fast but could survive contact with the enemy. -capabilities:The Charger is seen as an example of abject failure in BattleMech design. Wells Technologies originally wanted to produce an ultra-heavy scout 'Mech for the Star League Defense Force that was not only fast but could survive contact with the enemy. This was to be the 'Mech's downfall, as its popgun laser array proved to be quite laughable, capable of little more than fighting infantry and light combat vehicles. Its armoring, while respectable, could not stand up to sustained punishment, which meant if the 'Mech got too close to heavy combat or trapped by superior numbers it could be shot to pieces. +capabilities:This was to be the 'Mech's downfall, as its popgun laser array proved to be quite laughable, capable of little more than fighting infantry and light combat vehicles. Its armoring, while respectable, could not stand up to sustained punishment, which meant if the 'Mech got too close to heavy combat or trapped by superior numbers it could be shot to pieces. deployment:The Snow Ravens have raised the Charger, which was once regarded as one of the worst assault 'Mechs ever constructed. Shutting down the Charger line was one of the key reasons for Raveena Electronics' strong anti-Clan attitude, but the line's reinstatement put an end to their protests. The Charger C, when upgraded to a fully Clan-spec 'Mech with MASC and a supercharger, can meet the original design objective of a rapid assault-class scout with matching firepower. history:When the Charger debuted in 2665 it quickly became derided as "a light 'Mech trapped in an assault's frame" and the Star League quickly withdrew it from use; Wells Technologies eventually found itself wallowing in over a thousand Chargers which no one now wanted to buy. In an odd twist of fate, the fall of the Star League and the start of the First Succession War would save the company and the Charger. Desperate for any 'Mech they could get their hands on, the Draconis Combine bought the Charger in large numbers and established a long-term contract with the company. During the long attritional warfare of the Succession Wars era the Charger proved to be a reliable, low-maintenance 'Mech useful in rear areas and for garrison duty on low-tech worlds, especially in the Periphery. In its limited frontline engagements this close-assault 'Mech proved itself deadly against smaller recon elements like Wasps and Stingers and any machine whose main armament was already destroyed. Its greatest successes often came in less orthodox roles such as counterinsurgency operations. By 3025 nearly five hundred of the original thousand Chargers were still in use, largely with the Combine but also in the other Great Houses too. This was mainly due to battlefield salvage and black-market trading, the latter of which Wells itself took part in due to export restrictions placed on it by the Combine. The company was eventually bought out by its license-holder Luthien Armor Works in 3027 after the discovery of this underhanded dealing, and production of the original Charger ceased altogether in 3030. In the devastating aftermath of the Fourth Succession War however, the Combine once again needed 'Mechs to replace its losses, and the Coordinator himself ordered LAW to produce a 'Mech which would act as a symbol of the Combine's might. The resulting crash program to produce the Hatamoto-Chi gave LAW the ability to rework the Charger line using rediscovered technology, allowing them to produce "new" assault 'Mechs in half the time through a major modification program rather than starting from scratch. These new Charger variants debuted in time to meet the Clan Invasion, and while still close-in brawlers their varied weaponry and advanced technology made them far superior. Success with the revamped designs was such that by 3068 every Draconis Combine Mustered Soldiery unit had at least one new Charger in its inventory, though with the loss of LAW's Luthien plant production on the CGR-3K model ceased and many had moved on to the newer CGR-SA5 model. Some of the original Chargers are still used as labyrinthine fighters by backwater stables on Solaris VII. manufacturer:Raveena Electronics diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 29/Firefly FFL-5A.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 29/Firefly FFL-5A.mtf index 93992599d..0461d8b40 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 29/Firefly FFL-5A.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 29/Firefly FFL-5A.mtf @@ -160,7 +160,7 @@ capabilities: Although it was slow in comparison to other 'Mechs of its weight c deployment:No information on this variant -history:The Firefly, which entered service in the late 27th century, was one of the SLDF's primary light 'Mechs in its later years.Cases occurred in all House forces, but not in the numbers deployed by the SLDF, and all were presumed destroyed by the end of the Second Succession War, save for tales of anomalous examples in the Periphery. The design reappeared with Wolf's Dragoons in the early 31st century, raising eyebrows, yet the secret of the Firefly's origin was revealed when the Dragoons' Clan origins were revealed. In the 3040s, the advent of a small number of Fireflys with the Com Guard forces elicited a similar reaction. +history:The Firefly, which entered service in the late 27th century, was one of the SLDF's primary light 'Mechs in its later years. Cases occurred in all House forces, but not in the numbers deployed by the SLDF, and all were presumed destroyed by the end of the Second Succession War, save for tales of anomalous examples in the Periphery. The design reappeared with Wolf's Dragoons in the early 31st century, raising eyebrows, yet the secret of the Firefly's origin was exposed when the Dragoons' Clan origins were revealed. In the 3040s, the advent of a small number of Fireflys with the Com Guard forces elicited a similar reaction. manufacturer:Ceres Metals Industries primaryfactory:Lockton diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 30/Hellhound (Conjurer) 6.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 30/Hellhound (Conjurer) 6.mtf index 8c880f8ba..472004571 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 30/Hellhound (Conjurer) 6.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 30/Hellhound (Conjurer) 6.mtf @@ -156,7 +156,7 @@ CLDoubleHeatSink overview:The Conjurer (code-named the Hellhound by the Inner Sphere nations) is a fast, inexpensive medium BattleMech that excels at medium to short range. -capabilities:Starting as befitting its status as a second-line 'Mech, most Conjurers uses a standard engine, though it is constructed on an endo steel chassis and uses eight and a half tons of ferro-fibrous armor. Its jump jets enable it to leap up to 180 meters at a time. However Clan Nova Cat’s Conjurer program in the 3060s saw refits and various new builds at times only loosely based on the original. It is noteworthy that the Conjurer is, for all intents and purposes, the Wolverine IIC and was even reported as such by ComStar in early sightings, presumably for its obvious heritage; it was designed off the WVR-7H Wolverine II variant of the original Wolverine, taking the concept and rebuilding it with advanced technology in the fashion of a IIC rebuild. However the Clans would not retain the name of the Not-Named Clan for the redesigned 'Mech. +capabilities:Starting as befitting its status as a second-line 'Mech, most Conjurers uses a standard engine, though it is constructed on an endo steel chassis and uses eight and a half tons of ferro-fibrous armor. Its jump jets enable it to leap up to 180 meters at a time. However Clan Nova Cat’s Conjurer program in the 3060s saw refits and various new builds at times only loosely based on the original. It is noteworthy that the Conjurer is, for all intents and purposes, the Wolverine IIC and was even reported as such by ComStar in early sightings, presumably for its obvious heritage; it was designed off the WVR-7H Wolverine II variant of the original Wolverine, taking the concept and rebuilding it with advanced technology in the fashion of a IIC rebuild. However the Clans would not retain the name of the Not-Named Clan for the redesigned 'Mech. deployment:No Information on this variant diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 31/Clint CLNT-3 4T.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 31/Clint CLNT-3 4T.mtf index aab6a2c46..eb171b81c 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 31/Clint CLNT-3 4T.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 31/Clint CLNT-3 4T.mtf @@ -163,7 +163,7 @@ capabilities:With a top speed of 97.2 km/h and a jumping capability of 180 meter deployment:The latest Clint iteration is more of a refinement than a revolution. It has many similarities to the Cadaver. This is a significant advantage in the Periphery, where new components are often in short supply, especially for a volatile 'Mech like the Clint. To the delight of technicians, the upgrade eradicated several of its bothersome aspects. Concurrent improvements aided its weapon arsenal. This contains X-pulse technology, which was initially employed by the Taurians aboard the Brahma and had since matured enough for full-scale manufacture. The new Clint's reflective armor is still a risk that could erase its other practical advantages. -history:The Clint was built in 2607 as a direct result of the Star League Armaments Act, a law intended to provide frontier areas with cutting-edge warfare technology. However, Andoran Industries Ltd., a tiny BattleMech firm based on Bell, won the project by undercutting its competitors with cost-cutting design features. The Clint was not only made with substandard parts that rarely lasted a year, but it also employed very few standard components; modular pieces that could be easily transferred between many different 'Mechs could not be used in the Clint without extensive modification. The machine became a technician's nightmare, requiring more time to fix than comparable 'Mechs and allowing Andoran to recoup the Clint's low purchase price with a costly service contract. Before the Star League crumbled, over 300 Clints were created, and Andoran's factories were destroyed during conflict between the Federated Suns and the Capellan Confederation. House Davion and House Liao seized the majority of the remaining Clints and dispatched them to isolated regions inside their realms for defense purposes, however the Capellans retained several of the 'Mechs in front-line troops. Nonetheless, the explosion of the Bell facility destroyed not only the original Clint blueprints, effectively terminating new unit and spare part production, but also records of the exact number of Clints made and variants created. Clints could therefore be found across the Inner Sphere throughout the Succession Wars, proving rather popular in the Periphery, although the origins of many of these machines, and whether their different loadouts were official manufacture modifications or simple field-refits, remained unknown. Furthermore, the Clint's non-standard components quickly rose in price - the gyro, in instance, became worth its weight in gold - and many were simply stripped for parts to fix damaged machines.Despite the design's inherent maintenance challenges, an estimated 200 Clints remained in service until the Clan Invasion, largely in the hands of the Capellans or scattered throughout the Suns' border regions. The Confederation also created the 3U model, which the Federated Commonwealth swiftly adopted after the Bell Refit Yards were erected on the ruins of the original factory complex. The designs for the design finally made their way to Defiance Industries of Furillo, which began constructing new Clints for the first time in millennia in 3055. +history:The Clint was built in 2607 as a direct result of the Star League Armaments Act, a law intended to provide frontier areas with cutting-edge warfare technology. However, Andoran Industries Ltd., a tiny BattleMech firm based on Bell, won the project by undercutting its competitors with cost-cutting design features. The Clint was not only made with substandard parts that rarely lasted a year, but it also employed very few standard components; modular pieces that could be easily transferred between many different 'Mechs could not be used in the Clint without extensive modification. The machine became a technician's nightmare, requiring more time to fix than comparable 'Mechs and allowing Andoran to recoup the Clint's low purchase price with a costly service contract. Before the Star League crumbled, over 300 Clints were created, and Andoran's factories were destroyed during conflict between the Federated Suns and the Capellan Confederation. House Davion and House Liao seized the majority of the remaining Clints and dispatched them to isolated regions inside their realms for defense purposes, however the Capellans retained several of the 'Mechs in front-line troops. Nonetheless, the explosion of the Bell facility destroyed not only the original Clint blueprints, effectively terminating new unit and spare part production, but also records of the exact number of Clints made and variants created. Clints could therefore be found across the Inner Sphere throughout the Succession Wars, proving rather popular in the Periphery, although the origins of many of these machines, and whether their different loadouts were official manufacture modifications or simple field-refits, remained unknown. Furthermore, the Clint's non-standard components quickly rose in price - the gyro, in instance, became worth its weight in gold - and many were simply stripped for parts to fix damaged machines. Despite the design's inherent maintenance challenges, an estimated 200 Clints remained in service until the Clan Invasion, largely in the hands of the Capellans or scattered throughout the Suns' border regions. The Confederation also created the 3U model, which the Federated Commonwealth swiftly adopted after the Bell Refit Yards were erected on the ruins of the original factory complex. The plans for the design finally made their way to Defiance Industries of Furillo, which began constructing new Clints for the first time in millennia in 3055. manufacturer:Pinard Protectorates Limited primaryfactory:Macleod's Land diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 4/Awesome AWS-11H.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 4/Awesome AWS-11H.mtf index a45731f07..79d59298c 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 4/Awesome AWS-11H.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 4/Awesome AWS-11H.mtf @@ -156,7 +156,7 @@ CLDoubleHeatSink overview:The Awesome was designed in 2665 for the Star League by the Technicron Conglomorate and was based on the aging STR-2C Striker. While not as fast as its forefather, the Awesome is a strong assault 'Mech. -capabilities:The Awesome's abilities are nearly entirely dependent on its particle projection cannons. The AWS can withstand a severe and consistent onslaught from its weaponry thanks to several heat sinks. With one and a half tons more armor than the Striker, the AWS is more protected than even the BattleMaster. The Amazing, like any other BattleMech, has weaknesses. While it is lethal at range, it is less effective in close-quarters combat since its PPCs have a tougher time connecting with the victim. In that case, it just possesses a light weapon and a left fist to fall back on. Because of its limited mobility, it is vulnerable to flanking attacks from speedier opponents seeking to get past the PPCs. While they face arguably of the heaviest rear armor found on any BattleMech, the Awesome's lack of rear facing armaments or a weapon mount on its left arm has offered numerous MechWarriors a fighting chance. Formations of Awesomes (or even just a few) are incredibly effective and tough to stop or defeat when correctly placed by commanders who are knowledgeable of the AWS's limitations. +capabilities:The Awesome's abilities are nearly entirely dependent on its particle projection cannons. The AWS can withstand a severe and consistent onslaught from its weaponry thanks to several heat sinks. With one and a half tons more armor than the Striker, the AWS is more protected than even the BattleMaster. The Awesome, like any other BattleMech, has weaknesses. While it is lethal at range, it is less effective in close-quarters combat since its PPCs have a tougher time connecting with the victim. In that case, it just possesses a light weapon and a left fist to fall back on. Because of its limited mobility, it is vulnerable to flanking attacks from speedier opponents seeking to get past the PPCs. While they face arguably of the heaviest rear armor found on any BattleMech, the Awesome's lack of rear facing armaments or a weapon mount on its left arm has offered numerous MechWarriors a fighting chance. Formations of Awesomes (or even just a few) are incredibly effective and tough to stop or defeat when correctly placed by commanders who are knowledgeable of the AWS's limitations. deployment:Introduced after Technicron perfected production of Clan-spec Endo Steel and double heat sinks, the 11H Awesome carries three Heavy PPCs and can fire them continuously. In a nod to the traditional Awesome, the head carries an ER Small Laser. All the heat is dissipated by the twenty-three Clan-spec double heat sinks. diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 4/Blackjack BJ-5.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 4/Blackjack BJ-5.mtf index 08f453d2c..6f87d938c 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 4/Blackjack BJ-5.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 4/Blackjack BJ-5.mtf @@ -157,7 +157,7 @@ capabilities:The Blackjack's original mission was to assist in suppressing insur deployment:Introduced in 3107 this variant carries four light PPCs and two light AC/2s to extend the Blackjack's engagement range. To make room for this, the 'Mech uses endo steel chassis, light engine, and light ferro-fibrous armor.A single ton of autocannon ammunition is stored in a CASE II protected bay. -history:The Blackjack had limited use in the Star League, and manufacture was shortly discontinued. The Blackjack, relegated to service with Hegemony planetary militia or sold to League member nations, 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. +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. manufacturer:General Motors primaryfactory:Talcott diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 4/Fenris (Ice Ferret) F.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 4/Fenris (Ice Ferret) F.mtf index bc627ccda..68a15b8cc 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 4/Fenris (Ice Ferret) F.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 4/Fenris (Ice Ferret) F.mtf @@ -152,13 +152,13 @@ Clan Endo Steel -Empty- -Empty- -overview:A powerful medium scout and recon 'Mech, the Ice Ferret was regarded as something of a foreign concept when it was first encountered by Inner Sphere forces. Referred to as the Fenris by Inner Sphere forces, the Ice Ferret is a very capable medium scout OmniMech, which is well armored and fast, and can be configured as a strike/headhunter or as a fire-support 'Mech.[ +overview:A powerful medium scout and recon 'Mech, the Ice Ferret was regarded as something of a foreign concept when it was first encountered by Inner Sphere forces. Referred to as the Fenris by Inner Sphere forces, the Ice Ferret is a very capable medium scout OmniMech, which is well armored and fast, and can be configured as a strike/headhunter or as a fire-support 'Mech. capabilities:Providing direct-fire support the Fenris F carries a single ER Large Laser in each arm, while a Watchdog CEWS provides electronic support. deployment:The Ice Ferret is built on a lightweight Endo Steel chassis that saves weight and is powered by a massive 360 XL engine that gives the Ice Ferret a top speed of 129.6 km/h and also accounts for one third of the 'Mech's total weight. The Ice Ferret has twelve double heat sinks mounted on the chassis and is protected by seven and a half tons of Ferro-Fibrous armor, giving the 'Mech almost the maximum amount of armor protection for its weight. -history:Deployed extensively by Clan Wolf, the Ice Ferret was actually designed to combat the pride of Clan Wolf, the Timber Wolf OmniMech. Originally named the Wolf Hunter, the Ice Ferret was first produced in the mid-2900s by Clan Ice Hellion, but performed poorly due to lack-luster weapon configurations. Annoyed by the constant Hellion harassment, but appreciating the potential of the new OmniMech, Clan Wolf warriors eventually began challenging for the OmniMech, and eventually won the production facility for the design. The Wolves renamed the design after the only natural predator of the Ice Hellion, the Ice Ferret, and altered the configurations to improve performance. The Ice Hellions would maintain a large number of the "Wolf Hunters" in their touman during their existence. However, in the early years of the Jihad era, the Ice Ferret's few production facilities would end up being destroyed during the chaotic fighting in Clan Homeworlds. The design would end up being phased out of use and replaced by the Viper. +history:Deployed extensively by Clan Wolf, the Ice Ferret was actually designed to combat the pride of Clan Wolf, the Timber Wolf OmniMech. Originally named the Wolf Hunter, the Ice Ferret was first produced in the mid-2900s by Clan Ice Hellion, but performed poorly due to lack-luster weapon configurations. Annoyed by the constant Hellion harassment, but appreciating the potential of the new OmniMech, Clan Wolf warriors eventually began challenging for the OmniMech, and eventually won the production facility for the design. The Wolves renamed the design after the only natural predator of the Ice Hellion, the Ice Ferret, and altered the configurations to improve performance. The Ice Hellions would maintain a large number of the "Wolf Hunters" in their touman during their existence. However, in the early years of the Jihad era, the Ice Ferret's few production facilities would end up being destroyed during the chaotic fighting in Clan Homeworlds. The design would end up being phased out of use and replaced by the Viper. manufacturer:W-7 Facilities, Wolf Clan Site 3, Assault Tech Industries primaryfactory:Tranquil, Arc-Royal, Donegal systemmanufacturer:CHASSIS:Hellion Medium Gamma ES diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 4/Fenris (Ice Ferret) G.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 4/Fenris (Ice Ferret) G.mtf index c96a42a35..128a58cf5 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 4/Fenris (Ice Ferret) G.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 4/Fenris (Ice Ferret) G.mtf @@ -159,13 +159,13 @@ Clan Endo Steel -Empty- -Empty- -overview:A powerful medium scout and recon 'Mech, the Ice Ferret was regarded as something of a foreign concept when it was first encountered by Inner Sphere forces. Referred to as the Fenris by Inner Sphere forces, the Ice Ferret is a very capable medium scout OmniMech, which is well armored and fast, and can be configured as a strike/headhunter or as a fire-support 'Mech.[ +overview:A powerful medium scout and recon 'Mech, the Ice Ferret was regarded as something of a foreign concept when it was first encountered by Inner Sphere forces. Referred to as the Fenris by Inner Sphere forces, the Ice Ferret is a very capable medium scout OmniMech, which is well armored and fast, and can be configured as a strike/headhunter or as a fire-support 'Mech. capabilities:A striker/harrasser configuration that carries a single SRM-4 and two AP Gauss Rifles in each arm. An ER Small Pulse Laser is mounted in each side torso. For artillery support, a Light TAG unit is mounted in the center torso. deployment:The Ice Ferret is built on a lightweight Endo Steel chassis that saves weight and is powered by a massive 360 XL engine that gives the Ice Ferret a top speed of 129.6 km/h and also accounts for one third of the 'Mech's total weight. The Ice Ferret has twelve double heat sinks mounted on the chassis and is protected by seven and a half tons of Ferro-Fibrous armor, giving the 'Mech almost the maximum amount of armor protection for its weight. -history:Deployed extensively by Clan Wolf, the Ice Ferret was actually designed to combat the pride of Clan Wolf, the Timber Wolf OmniMech. Originally named the Wolf Hunter, the Ice Ferret was first produced in the mid-2900s by Clan Ice Hellion, but performed poorly due to lack-luster weapon configurations. Annoyed by the constant Hellion harassment, but appreciating the potential of the new OmniMech, Clan Wolf warriors eventually began challenging for the OmniMech, and eventually won the production facility for the design. The Wolves renamed the design after the only natural predator of the Ice Hellion, the Ice Ferret, and altered the configurations to improve performance. The Ice Hellions would maintain a large number of the "Wolf Hunters" in their touman during their existence. However, in the early years of the Jihad era, the Ice Ferret's few production facilities would end up being destroyed during the chaotic fighting in Clan Homeworlds. The design would end up being phased out of use and replaced by the Viper. +history:Deployed extensively by Clan Wolf, the Ice Ferret was actually designed to combat the pride of Clan Wolf, the Timber Wolf OmniMech. Originally named the Wolf Hunter, the Ice Ferret was first produced in the mid-2900s by Clan Ice Hellion, but performed poorly due to lack-luster weapon configurations. Annoyed by the constant Hellion harassment, but appreciating the potential of the new OmniMech, Clan Wolf warriors eventually began challenging for the OmniMech, and eventually won the production facility for the design. The Wolves renamed the design after the only natural predator of the Ice Hellion, the Ice Ferret, and altered the configurations to improve performance. The Ice Hellions would maintain a large number of the "Wolf Hunters" in their touman during their existence. However, in the early years of the Jihad era, the Ice Ferret's few production facilities would end up being destroyed during the chaotic fighting in Clan Homeworlds. The design would end up being phased out of use and replaced by the Viper. manufacturer:W-7 Facilities, Wolf Clan Site 3, Assault Tech Industries primaryfactory:Tranquil, Arc-Royal, Donegal systemmanufacturer:CHASSIS:Hellion Medium Gamma ES diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 4/Fenris (Ice Ferret) I.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 4/Fenris (Ice Ferret) I.mtf index b65f6290d..01195c7e2 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 4/Fenris (Ice Ferret) I.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 4/Fenris (Ice Ferret) I.mtf @@ -155,13 +155,13 @@ Clan Endo Steel -Empty- -Empty- -overview:A powerful medium scout and recon 'Mech, the Ice Ferret was regarded as something of a foreign concept when it was first encountered by Inner Sphere forces. Referred to as the Fenris by Inner Sphere forces, the Ice Ferret is a very capable medium scout OmniMech, which is well armored and fast, and can be configured as a strike/headhunter or as a fire-support 'Mech.[ +overview:A powerful medium scout and recon 'Mech, the Ice Ferret was regarded as something of a foreign concept when it was first encountered by Inner Sphere forces. Referred to as the Fenris by Inner Sphere forces, the Ice Ferret is a very capable medium scout OmniMech, which is well armored and fast, and can be configured as a strike/headhunter or as a fire-support 'Mech. capabilities:This configuration takes advantage of Inner Sphere technology. A Bloodhound Active Probe finds threats. Each arm carries an SRM-6 and an M-Pod. The SRM is equipped with a two ton ammunition bay, but once that's empty the MechWarrior only has a single ER Small Laser for weaponry. deployment:The Ice Ferret is built on a lightweight Endo Steel chassis that saves weight and is powered by a massive 360 XL engine that gives the Ice Ferret a top speed of 129.6 km/h and also accounts for one third of the 'Mech's total weight. The Ice Ferret has twelve double heat sinks mounted on the chassis and is protected by seven and a half tons of Ferro-Fibrous armor, giving the 'Mech almost the maximum amount of armor protection for its weight. -history:Deployed extensively by Clan Wolf, the Ice Ferret was actually designed to combat the pride of Clan Wolf, the Timber Wolf OmniMech. Originally named the Wolf Hunter, the Ice Ferret was first produced in the mid-2900s by Clan Ice Hellion, but performed poorly due to lack-luster weapon configurations. Annoyed by the constant Hellion harassment, but appreciating the potential of the new OmniMech, Clan Wolf warriors eventually began challenging for the OmniMech, and eventually won the production facility for the design. The Wolves renamed the design after the only natural predator of the Ice Hellion, the Ice Ferret, and altered the configurations to improve performance. The Ice Hellions would maintain a large number of the "Wolf Hunters" in their touman during their existence. However, in the early years of the Jihad era, the Ice Ferret's few production facilities would end up being destroyed during the chaotic fighting in Clan Homeworlds. The design would end up being phased out of use and replaced by the Viper. +history:Deployed extensively by Clan Wolf, the Ice Ferret was actually designed to combat the pride of Clan Wolf, the Timber Wolf OmniMech. Originally named the Wolf Hunter, the Ice Ferret was first produced in the mid-2900s by Clan Ice Hellion, but performed poorly due to lack-luster weapon configurations. Annoyed by the constant Hellion harassment, but appreciating the potential of the new OmniMech, Clan Wolf warriors eventually began challenging for the OmniMech, and eventually won the production facility for the design. The Wolves renamed the design after the only natural predator of the Ice Hellion, the Ice Ferret, and altered the configurations to improve performance. The Ice Hellions would maintain a large number of the "Wolf Hunters" in their touman during their existence. However, in the early years of the Jihad era, the Ice Ferret's few production facilities would end up being destroyed during the chaotic fighting in Clan Homeworlds. The design would end up being phased out of use and replaced by the Viper. manufacturer:W-7 Facilities, Wolf Clan Site 3, Assault Tech Industries primaryfactory:Tranquil, Arc-Royal, Donegal systemmanufacturer:CHASSIS:Hellion Medium Gamma ES diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 4/Fenris (Ice Ferret) J.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 4/Fenris (Ice Ferret) J.mtf index 0b9bd56d8..a764f63df 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 4/Fenris (Ice Ferret) J.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 4/Fenris (Ice Ferret) J.mtf @@ -162,13 +162,13 @@ Clan Endo Steel -Empty- -Empty- -overview:A powerful medium scout and recon 'Mech, the Ice Ferret was regarded as something of a foreign concept when it was first encountered by Inner Sphere forces. Referred to as the Fenris by Inner Sphere forces, the Ice Ferret is a very capable medium scout OmniMech, which is well armored and fast, and can be configured as a strike/headhunter or as a fire-support 'Mech.[ +overview:A powerful medium scout and recon 'Mech, the Ice Ferret was regarded as something of a foreign concept when it was first encountered by Inner Sphere forces. Referred to as the Fenris by Inner Sphere forces, the Ice Ferret is a very capable medium scout OmniMech, which is well armored and fast, and can be configured as a strike/headhunter or as a fire-support 'Mech. capabilities:A close range combatant, this configuration carries five ER Small Lasers and a Heavy Machine Gun in each arm. These weapons are tied into a Targeting Computer. A Supercharger allows the 'Mech to quickly approach and retreat from threat forces. deployment:The Ice Ferret is built on a lightweight Endo Steel chassis that saves weight and is powered by a massive 360 XL engine that gives the Ice Ferret a top speed of 129.6 km/h and also accounts for one third of the 'Mech's total weight. The Ice Ferret has twelve double heat sinks mounted on the chassis and is protected by seven and a half tons of Ferro-Fibrous armor, giving the 'Mech almost the maximum amount of armor protection for its weight. -history:Deployed extensively by Clan Wolf, the Ice Ferret was actually designed to combat the pride of Clan Wolf, the Timber Wolf OmniMech. Originally named the Wolf Hunter, the Ice Ferret was first produced in the mid-2900s by Clan Ice Hellion, but performed poorly due to lack-luster weapon configurations. Annoyed by the constant Hellion harassment, but appreciating the potential of the new OmniMech, Clan Wolf warriors eventually began challenging for the OmniMech, and eventually won the production facility for the design. The Wolves renamed the design after the only natural predator of the Ice Hellion, the Ice Ferret, and altered the configurations to improve performance. The Ice Hellions would maintain a large number of the "Wolf Hunters" in their touman during their existence. However, in the early years of the Jihad era, the Ice Ferret's few production facilities would end up being destroyed during the chaotic fighting in Clan Homeworlds. The design would end up being phased out of use and replaced by the Viper. +history:Deployed extensively by Clan Wolf, the Ice Ferret was actually designed to combat the pride of Clan Wolf, the Timber Wolf OmniMech. Originally named the Wolf Hunter, the Ice Ferret was first produced in the mid-2900s by Clan Ice Hellion, but performed poorly due to lack-luster weapon configurations. Annoyed by the constant Hellion harassment, but appreciating the potential of the new OmniMech, Clan Wolf warriors eventually began challenging for the OmniMech, and eventually won the production facility for the design. The Wolves renamed the design after the only natural predator of the Ice Hellion, the Ice Ferret, and altered the configurations to improve performance. The Ice Hellions would maintain a large number of the "Wolf Hunters" in their touman during their existence. However, in the early years of the Jihad era, the Ice Ferret's few production facilities would end up being destroyed during the chaotic fighting in Clan Homeworlds. The design would end up being phased out of use and replaced by the Viper. manufacturer:W-7 Facilities, Wolf Clan Site 3, Assault Tech Industries primaryfactory:Tranquil, Arc-Royal, Donegal systemmanufacturer:CHASSIS:Hellion Medium Gamma ES diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 4/Fenris (Ice Ferret) K.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 4/Fenris (Ice Ferret) K.mtf index 2ace7dcb7..728c6b5f6 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 4/Fenris (Ice Ferret) K.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 4/Fenris (Ice Ferret) K.mtf @@ -155,13 +155,13 @@ Clan Endo Steel -Empty- -Empty- -overview:A powerful medium scout and recon 'Mech, the Ice Ferret was regarded as something of a foreign concept when it was first encountered by Inner Sphere forces. Referred to as the Fenris by Inner Sphere forces, the Ice Ferret is a very capable medium scout OmniMech, which is well armored and fast, and can be configured as a strike/headhunter or as a fire-support 'Mech.[ +overview:A powerful medium scout and recon 'Mech, the Ice Ferret was regarded as something of a foreign concept when it was first encountered by Inner Sphere forces. Referred to as the Fenris by Inner Sphere forces, the Ice Ferret is a very capable medium scout OmniMech, which is well armored and fast, and can be configured as a strike/headhunter or as a fire-support 'Mech. capabilities:A Large Pulse Laser and ER Small Laser are carried in the left arm, while a pair of ER Medium Lasers are mounted in the right arm. Additional protection comes from a Laser AMS. deployment:The Ice Ferret is built on a lightweight Endo Steel chassis that saves weight and is powered by a massive 360 XL engine that gives the Ice Ferret a top speed of 129.6 km/h and also accounts for one third of the 'Mech's total weight. The Ice Ferret has twelve double heat sinks mounted on the chassis and is protected by seven and a half tons of Ferro-Fibrous armor, giving the 'Mech almost the maximum amount of armor protection for its weight. -history:Deployed extensively by Clan Wolf, the Ice Ferret was actually designed to combat the pride of Clan Wolf, the Timber Wolf OmniMech. Originally named the Wolf Hunter, the Ice Ferret was first produced in the mid-2900s by Clan Ice Hellion, but performed poorly due to lack-luster weapon configurations. Annoyed by the constant Hellion harassment, but appreciating the potential of the new OmniMech, Clan Wolf warriors eventually began challenging for the OmniMech, and eventually won the production facility for the design. The Wolves renamed the design after the only natural predator of the Ice Hellion, the Ice Ferret, and altered the configurations to improve performance. The Ice Hellions would maintain a large number of the "Wolf Hunters" in their touman during their existence. However, in the early years of the Jihad era, the Ice Ferret's few production facilities would end up being destroyed during the chaotic fighting in Clan Homeworlds. The design would end up being phased out of use and replaced by the Viper. +history:Deployed extensively by Clan Wolf, the Ice Ferret was actually designed to combat the pride of Clan Wolf, the Timber Wolf OmniMech. Originally named the Wolf Hunter, the Ice Ferret was first produced in the mid-2900s by Clan Ice Hellion, but performed poorly due to lack-luster weapon configurations. Annoyed by the constant Hellion harassment, but appreciating the potential of the new OmniMech, Clan Wolf warriors eventually began challenging for the OmniMech, and eventually won the production facility for the design. The Wolves renamed the design after the only natural predator of the Ice Hellion, the Ice Ferret, and altered the configurations to improve performance. The Ice Hellions would maintain a large number of the "Wolf Hunters" in their touman during their existence. However, in the early years of the Jihad era, the Ice Ferret's few production facilities would end up being destroyed during the chaotic fighting in Clan Homeworlds. The design would end up being phased out of use and replaced by the Viper. manufacturer:W-7 Facilities, Wolf Clan Site 3, Assault Tech Industries primaryfactory:Tranquil, Arc-Royal, Donegal systemmanufacturer:CHASSIS:Hellion Medium Gamma ES diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 4/Fenris (Ice Ferret) T.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 4/Fenris (Ice Ferret) T.mtf index 1be7fb39c..ed22467f6 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 4/Fenris (Ice Ferret) T.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 4/Fenris (Ice Ferret) T.mtf @@ -153,13 +153,13 @@ Clan Endo Steel -Empty- -Empty- -overview:A powerful medium scout and recon 'Mech, the Ice Ferret was regarded as something of a foreign concept when it was first encountered by Inner Sphere forces. Referred to as the Fenris by Inner Sphere forces, the Ice Ferret is a very capable medium scout OmniMech, which is well armored and fast, and can be configured as a strike/headhunter or as a fire-support 'Mech.[ +overview:A powerful medium scout and recon 'Mech, the Ice Ferret was regarded as something of a foreign concept when it was first encountered by Inner Sphere forces. Referred to as the Fenris by Inner Sphere forces, the Ice Ferret is a very capable medium scout OmniMech, which is well armored and fast, and can be configured as a strike/headhunter or as a fire-support 'Mech. capabilities:An Improved Heavy Large Laser and ER Medium Laser are mounted in the left arm, while the right arm carries a single SRM 2 with a ton of ammunition. An Active Probe finds hidden threats while an engine Supercharger allows the Ice Ferret to sprint at speeds of 160km/h. deployment:The Ice Ferret is built on a lightweight Endo Steel chassis that saves weight and is powered by a massive 360 XL engine that gives the Ice Ferret a top speed of 129.6 km/h and also accounts for one third of the 'Mech's total weight. The Ice Ferret has twelve double heat sinks mounted on the chassis and is protected by seven and a half tons of Ferro-Fibrous armor, giving the 'Mech almost the maximum amount of armor protection for its weight. -history:Deployed extensively by Clan Wolf, the Ice Ferret was actually designed to combat the pride of Clan Wolf, the Timber Wolf OmniMech. Originally named the Wolf Hunter, the Ice Ferret was first produced in the mid-2900s by Clan Ice Hellion, but performed poorly due to lack-luster weapon configurations. Annoyed by the constant Hellion harassment, but appreciating the potential of the new OmniMech, Clan Wolf warriors eventually began challenging for the OmniMech, and eventually won the production facility for the design. The Wolves renamed the design after the only natural predator of the Ice Hellion, the Ice Ferret, and altered the configurations to improve performance. The Ice Hellions would maintain a large number of the "Wolf Hunters" in their touman during their existence. However, in the early years of the Jihad era, the Ice Ferret's few production facilities would end up being destroyed during the chaotic fighting in Clan Homeworlds. The design would end up being phased out of use and replaced by the Viper. +history:Deployed extensively by Clan Wolf, the Ice Ferret was actually designed to combat the pride of Clan Wolf, the Timber Wolf OmniMech. Originally named the Wolf Hunter, the Ice Ferret was first produced in the mid-2900s by Clan Ice Hellion, but performed poorly due to lack-luster weapon configurations. Annoyed by the constant Hellion harassment, but appreciating the potential of the new OmniMech, Clan Wolf warriors eventually began challenging for the OmniMech, and eventually won the production facility for the design. The Wolves renamed the design after the only natural predator of the Ice Hellion, the Ice Ferret, and altered the configurations to improve performance. The Ice Hellions would maintain a large number of the "Wolf Hunters" in their touman during their existence. However, in the early years of the Jihad era, the Ice Ferret's few production facilities would end up being destroyed during the chaotic fighting in Clan Homeworlds. The design would end up being phased out of use and replaced by the Viper. manufacturer:W-7 Facilities, Wolf Clan Site 3, Assault Tech Industries primaryfactory:Tranquil, Arc-Royal, Donegal systemmanufacturer:CHASSIS:Hellion Medium Gamma ES diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 4/Trebuchet TBT-9N.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 4/Trebuchet TBT-9N.mtf index 09b30651c..1348af3d4 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 4/Trebuchet TBT-9N.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 4/Trebuchet TBT-9N.mtf @@ -168,7 +168,7 @@ deployment:This model is a lower-cost derivative of the TBT-9R. It uses an XL En history:The Trebuchet first walked off assembly lines in 2780 for the SLDF in the final years of the Star League, between the liberation of Terra from Stefan Amaris and Aleksandr Kerensky's departure. With the onset of the Succession Wars the Trebuchet would become an almost exclusive staple of the Free Worlds League since its manufacturing site on Stewart fell within their territory. However the original TBT-3C models proved to be too difficult to repair and produce with the disappearance of advanced technology, and in 2799 Corean Enterprises went back to the drawing board to create the TBT-5N using older, mass-producible technology. The Free Worlds League Military often partnered the Trebuchet with the Archer, while lances consisting of an Archer, two Trebuchets and a Centurion became a common configuration used for siege operations and by the Regulan Hussars. However the design also found its way into the hands of the other Great Houses and served with distinction during the Succession Wars in nearly every major operation, with a number of variants created to fulfill various needs. The technological renaissance which swept through the Inner Sphere during the 3030s allowed first Kali Yama and then the Irian corporations to begin producing the Trebuchet as well, culminating in upgraded designs debuting several years prior to the Clan Invasion. As late as 3071 advanced Trebuchet variants would continue to be produced and found themselves used by new actors on the galactic stage, most notoriously the Word of Blake. manufacturer:Tvastar Enterprises -primaryfactory:Regulas +primaryfactory:Regulus systemmanufacturer:CHASSIS:Corean-II Deluxe Endo Steel systemmanufacturer:ENGINE:Magna 300 XL systemmanufacturer:ARMOR:Starshield with CASE diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/Crab CRB-54.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/Crab CRB-54.mtf index 4d4cd0818..e0833ba25 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/Crab CRB-54.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/Crab CRB-54.mtf @@ -156,7 +156,7 @@ IS Heavy Ferro-Fibrous overview:Designed in 2719 during the last days of the Star League, the Crab was built as a medium-weight raider and guerrilla fighter for the Star League Defense Force. -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 +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:This Crab variant uses a Composite Structure and a 350-rated XXL Engine to reach speeds of 110km/h. A Supercharger allows it to sprint at 140km/h which is good for leaving the field when its armor is breached. Main firepower comes from a pair of Plasma Rifles supported by an ER Medium Laser and an ER Small Laser. diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/Hellhound (Conjurer) 7.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/Hellhound (Conjurer) 7.mtf index 12a2dde07..73992bddd 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/Hellhound (Conjurer) 7.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/Hellhound (Conjurer) 7.mtf @@ -156,7 +156,7 @@ Clan Endo Steel overview:The Conjurer (code-named the Hellhound by the Inner Sphere nations) is a fast, inexpensive medium BattleMech that excels at medium to short range. -capabilities:Starting as befitting its status as a second-line 'Mech, most Conjurers uses a standard engine, though it is constructed on an endo steel chassis and uses eight and a half tons of ferro-fibrous armor. Its jump jets enable it to leap up to 180 meters at a time. However Clan Nova Cat’s Conjurer program in the 3060s saw refits and various new builds at times only loosely based on the original. It is noteworthy that the Conjurer is, for all intents and purposes, the Wolverine IIC and was even reported as such by ComStar in early sightings, presumably for its obvious heritage; it was designed off the WVR-7H Wolverine II variant of the original Wolverine, taking the concept and rebuilding it with advanced technology in the fashion of a IIC rebuild. However the Clans would not retain the name of the Not-Named Clan for the redesigned 'Mech. +capabilities:Starting as befitting its status as a second-line 'Mech, most Conjurers uses a standard engine, though it is constructed on an endo steel chassis and uses eight and a half tons of ferro-fibrous armor. Its jump jets enable it to leap up to 180 meters at a time. However Clan Nova Cat’s Conjurer program in the 3060s saw refits and various new builds at times only loosely based on the original. It is noteworthy that the Conjurer is, for all intents and purposes, the Wolverine IIC and was even reported as such by ComStar in early sightings, presumably for its obvious heritage; it was designed off the WVR-7H Wolverine II variant of the original Wolverine, taking the concept and rebuilding it with advanced technology in the fashion of a IIC rebuild. However the Clans would not retain the name of the Not-Named Clan for the redesigned 'Mech. deployment:This variant trades the Streak SRM-2s of the base model for LRM-5s. diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/Hellhound (Conjurer) 8.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/Hellhound (Conjurer) 8.mtf index 5c79af92d..3befe3d6d 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/Hellhound (Conjurer) 8.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/Hellhound (Conjurer) 8.mtf @@ -155,7 +155,7 @@ Clan Endo Steel overview:The Conjurer (code-named the Hellhound by the Inner Sphere nations) is a fast, inexpensive medium BattleMech that excels at medium to short range. -capabilities:Starting as befitting its status as a second-line 'Mech, most Conjurers uses a standard engine, though it is constructed on an endo steel chassis and uses eight and a half tons of ferro-fibrous armor. Its jump jets enable it to leap up to 180 meters at a time. However Clan Nova Cat’s Conjurer program in the 3060s saw refits and various new builds at times only loosely based on the original. It is noteworthy that the Conjurer is, for all intents and purposes, the Wolverine IIC and was even reported as such by ComStar in early sightings, presumably for its obvious heritage; it was designed off the WVR-7H Wolverine II variant of the original Wolverine, taking the concept and rebuilding it with advanced technology in the fashion of a IIC rebuild. However the Clans would not retain the name of the Not-Named Clan for the redesigned 'Mech. +capabilities:Starting as befitting its status as a second-line 'Mech, most Conjurers uses a standard engine, though it is constructed on an endo steel chassis and uses eight and a half tons of ferro-fibrous armor. Its jump jets enable it to leap up to 180 meters at a time. However Clan Nova Cat’s Conjurer program in the 3060s saw refits and various new builds at times only loosely based on the original. It is noteworthy that the Conjurer is, for all intents and purposes, the Wolverine IIC and was even reported as such by ComStar in early sightings, presumably for its obvious heritage; it was designed off the WVR-7H Wolverine II variant of the original Wolverine, taking the concept and rebuilding it with advanced technology in the fashion of a IIC rebuild. However the Clans would not retain the name of the Not-Named Clan for the redesigned 'Mech. deployment:Introduced by the Wolf Empire this version was originally a stopgap solution until Clan spec weaponry could be produced in large amounts, but it proved to be very popular with warriors. It uses a smaller 250-rated XL engine and a rotary AC/5 from the Shockwave production line. Supplementing the engine is a MASC system. Additional firepower comes from a Clan Streak SRM-6 and two Clan medium pulse lasers. diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/Hellhound (Conjurer).mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/Hellhound (Conjurer).mtf index 1779bb9c3..28d2f8d7f 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/Hellhound (Conjurer).mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/Hellhound (Conjurer).mtf @@ -158,7 +158,7 @@ Clan Endo Steel overview:The Conjurer (code-named the Hellhound by the Inner Sphere nations) is a fast, inexpensive medium BattleMech that excels at medium to short range. -capabilities:Starting as befitting its status as a second-line 'Mech, most Conjurers uses a standard engine, though it is constructed on an endo steel chassis and uses eight and a half tons of ferro-fibrous armor. Its jump jets enable it to leap up to 180 meters at a time. However Clan Nova Cat’s Conjurer program in the 3060s saw refits and various new builds at times only loosely based on the original. It is noteworthy that the Conjurer is, for all intents and purposes, the Wolverine IIC and was even reported as such by ComStar in early sightings, presumably for its obvious heritage; it was designed off the WVR-7H Wolverine II variant of the original Wolverine, taking the concept and rebuilding it with advanced technology in the fashion of a IIC rebuild. However the Clans would not retain the name of the Not-Named Clan for the redesigned 'Mech. +capabilities:Starting as befitting its status as a second-line 'Mech, most Conjurers uses a standard engine, though it is constructed on an endo steel chassis and uses eight and a half tons of ferro-fibrous armor. Its jump jets enable it to leap up to 180 meters at a time. However Clan Nova Cat’s Conjurer program in the 3060s saw refits and various new builds at times only loosely based on the original. It is noteworthy that the Conjurer is, for all intents and purposes, the Wolverine IIC and was even reported as such by ComStar in early sightings, presumably for its obvious heritage; it was designed off the WVR-7H Wolverine II variant of the original Wolverine, taking the concept and rebuilding it with advanced technology in the fashion of a IIC rebuild. However the Clans would not retain the name of the Not-Named Clan for the redesigned 'Mech. deployment:The Conjurer uses a large pulse laser that is quite accurate and effective at a respectable range. To back that up, it mounts paired ER medium lasers and Streak SRM-2s. 10 double heat sinks are able to keep heat under control, though a Conjurer can summon up a heat problem if pressed too hard. diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/King Crab KGC-011.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/King Crab KGC-011.mtf index 6fcf349f7..e2e33001f 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/King Crab KGC-011.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/King Crab KGC-011.mtf @@ -156,7 +156,7 @@ IS LB 20-X Cluster Ammo overview:The King Crab has been a horror on the battlefield since its introduction just before the old Star League's demise, and it is well known for its ability to quickly kill most BattleMechs under eighty tons. -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,[6] and has been described as a "notorious hangar queen". +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:This King Crab variant is designed to break enemy strongpoints. It carries an LB 20-X in each arm, supported by a plasma rifle and a single Rocket Launcher 15. Nineteen and a half tons of armor protect a composite chassis and XXL fusion engine. The base ground speed is 64 km/h, but a Supercharger allows the King Crab to reach 86 km/h. Sixteen double heat sinks handle the heat load. However the lack of CASE and six tons of autocannon ammunition means any pilot should withdraw when the armor is punctured. diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/Mad Cat (Timber Wolf) M.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/Mad Cat (Timber Wolf) M.mtf index 332aa4e11..6f0b90467 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/Mad Cat (Timber Wolf) M.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/Mad Cat (Timber Wolf) M.mtf @@ -159,11 +159,11 @@ Clan Endo Steel -Empty- -Empty- -overview:overview:The Timber Wolf is a fast, heavy OmniMech. A signature design of the Clans' military might, it was arguably the first Clan OmniMech encountered by Inner Sphere forces (as opposed to periphery forces) on The Rock in 3049 by Phelan Kell. The Timber Wolf is vastly more powerful than either the Marauder or the Catapult. It uses its speed and firepower to engage an enemy at the range of its choosing. When first encountered by Inner Sphere forces the idea that a heavy 'Mech could move so swiftly while being as heavily armed and armored as the Timber Wolf was inconceivable. With its twelve tons of Ferro-Fibrous armor and arsenal that rivaled that of most assault 'Mechs of the era, it was completely alien to Inner Sphere military planners, commanders, and even the Precentor Martial of ComStar. Its technological secrets have since been reverse-engineered by the Inner Sphere. +overview:The Timber Wolf is a fast, heavy OmniMech. A signature design of the Clans' military might, it was arguably the first Clan OmniMech encountered by Inner Sphere forces (as opposed to periphery forces) on The Rock in 3049 by Phelan Kell. The Timber Wolf is vastly more powerful than either the Marauder or the Catapult. It uses its speed and firepower to engage an enemy at the range of its choosing. When first encountered by Inner Sphere forces the idea that a heavy 'Mech could move so swiftly while being as heavily armed and armored as the Timber Wolf was inconceivable. With its twelve tons of Ferro-Fibrous armor and arsenal that rivaled that of most assault 'Mechs of the era, it was completely alien to Inner Sphere military planners, commanders, and even the Precentor Martial of ComStar. Its technological secrets have since been reverse-engineered by the Inner Sphere. capabilities:A brawler configuration, the Timber Wolf M mounts an ER PPC in each arm, supported by a pair of LRM-5s in each side torso, a Large Pulse Laser in the left torso and a Heavy Flamer in the center torso. A combined two tons of LRM missiles and a single ton of flamer ammo sit in the torsos alongside a single extra Double Heat Sink. -deployment:First introduced in 2945, the Timber Wolf was designed by Clan Wolf as a second generation OmniMech along with the Gargoyle and the Naga to replace the aging Woodsman. While the Gargoyle may have been a very capable, fast assault OmniMech, and the Naga may have been an excellent fire-support OmniMech, Clan Wolf (and indeed every other Clan) instantly realized the value of the Timber Wolf; thus, production rights to the Timber Wolf were jealously (and successfully) defended. Only through trade, gifts and battlefield salvage has the Timber Wolf entered the armies of other Clans. Until the invasion of the Inner Sphere, production of the Timber Wolf has been limited to a single facility on Strana Mechty. Despite it's prominence among the Wolves during the Clan Invasion, Refusal War and Word of Blake Jihad, the Timber Wolf became increasingly rare following the sundering of ties with the Homeworld Clans during the Wars of Reaving and Blakist scouring of Tamar. Being built by hand at W-7 plant on Weingarten as of 3080, with some parts even being individually machined due to missing data,[1] attrition vastly outstripped supply as the Wolves looked toward other designs. When Alaric Ward forged the Wolf Empire, he left the W-7 facilities to Clan Hell's Horses and ordered the Kallon plant on Thermopolis be retooled for Timber Wolf production, restoring it's position within the Wolves touman. +deployment:First introduced in 2945, the Timber Wolf was designed by Clan Wolf as a second generation OmniMech along with the Gargoyle and the Naga to replace the aging Woodsman. While the Gargoyle may have been a very capable, fast assault OmniMech, and the Naga may have been an excellent fire-support OmniMech, Clan Wolf (and indeed every other Clan) instantly realized the value of the Timber Wolf; thus, production rights to the Timber Wolf were jealously (and successfully) defended. Only through trade, gifts and battlefield salvage has the Timber Wolf entered the armies of other Clans. Until the invasion of the Inner Sphere, production of the Timber Wolf has been limited to a single facility on Strana Mechty. Despite it's prominence among the Wolves during the Clan Invasion, Refusal War and Word of Blake Jihad, the Timber Wolf became increasingly rare following the sundering of ties with the Homeworld Clans during the Wars of Reaving and Blakist scouring of Tamar. Being built by hand at W-7 plant on Weingarten as of 3080, with some parts even being individually machined due to missing data, attrition vastly outstripped supply as the Wolves looked toward other designs. When Alaric Ward forged the Wolf Empire, he left the W-7 facilities to Clan Hell's Horses and ordered the Kallon plant on Thermopolis be retooled for Timber Wolf production, restoring it's position within the Wolves touman. history:Vaguely resembling a cross-over between the MAD (Marauder) and CAT (Catapult) series, the Timber Wolf was tagged with the Inner Sphere reporting name Mad Cat on first contact. (The targeting computer on Phelan Kell's Wolfhound switched between MAD and CAT when trying to identify it; upon analyzing the data recording from Kell's 'Mech, Precentor Martial Anastasius Focht later officially designated it "Mad Cat". diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/Mad Cat (Timber Wolf) N.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/Mad Cat (Timber Wolf) N.mtf index ddf967199..7ce26ae77 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/Mad Cat (Timber Wolf) N.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/Mad Cat (Timber Wolf) N.mtf @@ -161,11 +161,11 @@ Clan Endo Steel -Empty- -Empty- -overview:overview:The Timber Wolf is a fast, heavy OmniMech. A signature design of the Clans' military might, it was arguably the first Clan OmniMech encountered by Inner Sphere forces (as opposed to periphery forces) on The Rock in 3049 by Phelan Kell. The Timber Wolf is vastly more powerful than either the Marauder or the Catapult. It uses its speed and firepower to engage an enemy at the range of its choosing. When first encountered by Inner Sphere forces the idea that a heavy 'Mech could move so swiftly while being as heavily armed and armored as the Timber Wolf was inconceivable. With its twelve tons of Ferro-Fibrous armor and arsenal that rivaled that of most assault 'Mechs of the era, it was completely alien to Inner Sphere military planners, commanders, and even the Precentor Martial of ComStar. Its technological secrets have since been reverse-engineered by the Inner Sphere. +overview:The Timber Wolf is a fast, heavy OmniMech. A signature design of the Clans' military might, it was arguably the first Clan OmniMech encountered by Inner Sphere forces (as opposed to periphery forces) on The Rock in 3049 by Phelan Kell. The Timber Wolf is vastly more powerful than either the Marauder or the Catapult. It uses its speed and firepower to engage an enemy at the range of its choosing. When first encountered by Inner Sphere forces the idea that a heavy 'Mech could move so swiftly while being as heavily armed and armored as the Timber Wolf was inconceivable. With its twelve tons of Ferro-Fibrous armor and arsenal that rivaled that of most assault 'Mechs of the era, it was completely alien to Inner Sphere military planners, commanders, and even the Precentor Martial of ComStar. Its technological secrets have since been reverse-engineered by the Inner Sphere. capabilities:A mix of the Prime and the D configurations, alternate configuration N mounts an ER PPC in each arm alongside an LRM-15 rack in the left and right torsos. These weapons are supported at short range by paired Machine Guns and Medium Pulse Lasers in each side torso. Two tons of LRM reloads and a half ton of machine gun rounds force a focus on the energy weapons with an extra Double Heat Sink tries to assist in managing their heat. -deployment:First introduced in 2945, the Timber Wolf was designed by Clan Wolf as a second generation OmniMech along with the Gargoyle and the Naga to replace the aging Woodsman. While the Gargoyle may have been a very capable, fast assault OmniMech, and the Naga may have been an excellent fire-support OmniMech, Clan Wolf (and indeed every other Clan) instantly realized the value of the Timber Wolf; thus, production rights to the Timber Wolf were jealously (and successfully) defended. Only through trade, gifts and battlefield salvage has the Timber Wolf entered the armies of other Clans. Until the invasion of the Inner Sphere, production of the Timber Wolf has been limited to a single facility on Strana Mechty. Despite it's prominence among the Wolves during the Clan Invasion, Refusal War and Word of Blake Jihad, the Timber Wolf became increasingly rare following the sundering of ties with the Homeworld Clans during the Wars of Reaving and Blakist scouring of Tamar. Being built by hand at W-7 plant on Weingarten as of 3080, with some parts even being individually machined due to missing data,[1] attrition vastly outstripped supply as the Wolves looked toward other designs. When Alaric Ward forged the Wolf Empire, he left the W-7 facilities to Clan Hell's Horses and ordered the Kallon plant on Thermopolis be retooled for Timber Wolf production, restoring it's position within the Wolves touman. +deployment:First introduced in 2945, the Timber Wolf was designed by Clan Wolf as a second generation OmniMech along with the Gargoyle and the Naga to replace the aging Woodsman. While the Gargoyle may have been a very capable, fast assault OmniMech, and the Naga may have been an excellent fire-support OmniMech, Clan Wolf (and indeed every other Clan) instantly realized the value of the Timber Wolf; thus, production rights to the Timber Wolf were jealously (and successfully) defended. Only through trade, gifts and battlefield salvage has the Timber Wolf entered the armies of other Clans. Until the invasion of the Inner Sphere, production of the Timber Wolf has been limited to a single facility on Strana Mechty. Despite it's prominence among the Wolves during the Clan Invasion, Refusal War and Word of Blake Jihad, the Timber Wolf became increasingly rare following the sundering of ties with the Homeworld Clans during the Wars of Reaving and Blakist scouring of Tamar. Being built by hand at W-7 plant on Weingarten as of 3080, with some parts even being individually machined due to missing data, attrition vastly outstripped supply as the Wolves looked toward other designs. When Alaric Ward forged the Wolf Empire, he left the W-7 facilities to Clan Hell's Horses and ordered the Kallon plant on Thermopolis be retooled for Timber Wolf production, restoring it's position within the Wolves touman. history:Vaguely resembling a cross-over between the MAD (Marauder) and CAT (Catapult) series, the Timber Wolf was tagged with the Inner Sphere reporting name Mad Cat on first contact. (The targeting computer on Phelan Kell's Wolfhound switched between MAD and CAT when trying to identify it; upon analyzing the data recording from Kell's 'Mech, Precentor Martial Anastasius Focht later officially designated it "Mad Cat". diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/Mad Cat (Timber Wolf) T.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/Mad Cat (Timber Wolf) T.mtf index c93e31699..140129250 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/Mad Cat (Timber Wolf) T.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/Mad Cat (Timber Wolf) T.mtf @@ -160,11 +160,11 @@ Clan Endo Steel -Empty- -Empty- -overview:overview:The Timber Wolf is a fast, heavy OmniMech. A signature design of the Clans' military might, it was arguably the first Clan OmniMech encountered by Inner Sphere forces (as opposed to periphery forces) on The Rock in 3049 by Phelan Kell. The Timber Wolf is vastly more powerful than either the Marauder or the Catapult. It uses its speed and firepower to engage an enemy at the range of its choosing. When first encountered by Inner Sphere forces the idea that a heavy 'Mech could move so swiftly while being as heavily armed and armored as the Timber Wolf was inconceivable. With its twelve tons of Ferro-Fibrous armor and arsenal that rivaled that of most assault 'Mechs of the era, it was completely alien to Inner Sphere military planners, commanders, and even the Precentor Martial of ComStar. Its technological secrets have since been reverse-engineered by the Inner Sphere. +overview:The Timber Wolf is a fast, heavy OmniMech. A signature design of the Clans' military might, it was arguably the first Clan OmniMech encountered by Inner Sphere forces (as opposed to periphery forces) on The Rock in 3049 by Phelan Kell. The Timber Wolf is vastly more powerful than either the Marauder or the Catapult. It uses its speed and firepower to engage an enemy at the range of its choosing. When first encountered by Inner Sphere forces the idea that a heavy 'Mech could move so swiftly while being as heavily armed and armored as the Timber Wolf was inconceivable. With its twelve tons of Ferro-Fibrous armor and arsenal that rivaled that of most assault 'Mechs of the era, it was completely alien to Inner Sphere military planners, commanders, and even the Precentor Martial of ComStar. Its technological secrets have since been reverse-engineered by the Inner Sphere. capabilities:A missile boat configuration, the Timber Wolf T is armed with an Artemis V FCS-enhanced LRM-20 rack in each side torso, supported by a Improved Heavy Medium Laser and ER Medium Laser in each arm and a pair of ER Small Lasers and a single ER Small Pulse Laser in the torsos. Six tons of LRM rounds and two extra double heat sinks give it good field endurance. -deployment:First introduced in 2945, the Timber Wolf was designed by Clan Wolf as a second generation OmniMech along with the Gargoyle and the Naga to replace the aging Woodsman. While the Gargoyle may have been a very capable, fast assault OmniMech, and the Naga may have been an excellent fire-support OmniMech, Clan Wolf (and indeed every other Clan) instantly realized the value of the Timber Wolf; thus, production rights to the Timber Wolf were jealously (and successfully) defended. Only through trade, gifts and battlefield salvage has the Timber Wolf entered the armies of other Clans. Until the invasion of the Inner Sphere, production of the Timber Wolf has been limited to a single facility on Strana Mechty. Despite it's prominence among the Wolves during the Clan Invasion, Refusal War and Word of Blake Jihad, the Timber Wolf became increasingly rare following the sundering of ties with the Homeworld Clans during the Wars of Reaving and Blakist scouring of Tamar. Being built by hand at W-7 plant on Weingarten as of 3080, with some parts even being individually machined due to missing data,[1] attrition vastly outstripped supply as the Wolves looked toward other designs. When Alaric Ward forged the Wolf Empire, he left the W-7 facilities to Clan Hell's Horses and ordered the Kallon plant on Thermopolis be retooled for Timber Wolf production, restoring it's position within the Wolves touman. +deployment:First introduced in 2945, the Timber Wolf was designed by Clan Wolf as a second generation OmniMech along with the Gargoyle and the Naga to replace the aging Woodsman. While the Gargoyle may have been a very capable, fast assault OmniMech, and the Naga may have been an excellent fire-support OmniMech, Clan Wolf (and indeed every other Clan) instantly realized the value of the Timber Wolf; thus, production rights to the Timber Wolf were jealously (and successfully) defended. Only through trade, gifts and battlefield salvage has the Timber Wolf entered the armies of other Clans. Until the invasion of the Inner Sphere, production of the Timber Wolf has been limited to a single facility on Strana Mechty. Despite it's prominence among the Wolves during the Clan Invasion, Refusal War and Word of Blake Jihad, the Timber Wolf became increasingly rare following the sundering of ties with the Homeworld Clans during the Wars of Reaving and Blakist scouring of Tamar. Being built by hand at W-7 plant on Weingarten as of 3080, with some parts even being individually machined due to missing data, attrition vastly outstripped supply as the Wolves looked toward other designs. When Alaric Ward forged the Wolf Empire, he left the W-7 facilities to Clan Hell's Horses and ordered the Kallon plant on Thermopolis be retooled for Timber Wolf production, restoring it's position within the Wolves touman. history:Vaguely resembling a cross-over between the MAD (Marauder) and CAT (Catapult) series, the Timber Wolf was tagged with the Inner Sphere reporting name Mad Cat on first contact. (The targeting computer on Phelan Kell's Wolfhound switched between MAD and CAT when trying to identify it; upon analyzing the data recording from Kell's 'Mech, Precentor Martial Anastasius Focht later officially designated it "Mad Cat". diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/Mad Cat (Timber Wolf) W.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/Mad Cat (Timber Wolf) W.mtf index c360280a8..01c535443 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/Mad Cat (Timber Wolf) W.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/Mad Cat (Timber Wolf) W.mtf @@ -157,11 +157,11 @@ Clan Endo Steel -Empty- -Empty- -overview:overview:The Timber Wolf is a fast, heavy OmniMech. A signature design of the Clans' military might, it was arguably the first Clan OmniMech encountered by Inner Sphere forces (as opposed to periphery forces) on The Rock in 3049 by Phelan Kell. The Timber Wolf is vastly more powerful than either the Marauder or the Catapult. It uses its speed and firepower to engage an enemy at the range of its choosing. When first encountered by Inner Sphere forces the idea that a heavy 'Mech could move so swiftly while being as heavily armed and armored as the Timber Wolf was inconceivable. With its twelve tons of Ferro-Fibrous armor and arsenal that rivaled that of most assault 'Mechs of the era, it was completely alien to Inner Sphere military planners, commanders, and even the Precentor Martial of ComStar. Its technological secrets have since been reverse-engineered by the Inner Sphere. +overview:The Timber Wolf is a fast, heavy OmniMech. A signature design of the Clans' military might, it was arguably the first Clan OmniMech encountered by Inner Sphere forces (as opposed to periphery forces) on The Rock in 3049 by Phelan Kell. The Timber Wolf is vastly more powerful than either the Marauder or the Catapult. It uses its speed and firepower to engage an enemy at the range of its choosing. When first encountered by Inner Sphere forces the idea that a heavy 'Mech could move so swiftly while being as heavily armed and armored as the Timber Wolf was inconceivable. With its twelve tons of Ferro-Fibrous armor and arsenal that rivaled that of most assault 'Mechs of the era, it was completely alien to Inner Sphere military planners, commanders, and even the Precentor Martial of ComStar. Its technological secrets have since been reverse-engineered by the Inner Sphere. capabilities:A brutal short-ranged combatant, the Timber Wolf W mounts a mammoth Ultra AC/20 in the right torso, supported by a Streak SRM-6 rack in each side torso, a ER Small Laser in the left torso, and twin ER Medium Lasers in the left arm. Carrying four tons of UAC rounds and single ton of missiles for the ammo efficient Streak launchers, a Supercharger allows the W config to close within optimum range as quickly as possible. -deployment:First introduced in 2945, the Timber Wolf was designed by Clan Wolf as a second generation OmniMech along with the Gargoyle and the Naga to replace the aging Woodsman. While the Gargoyle may have been a very capable, fast assault OmniMech, and the Naga may have been an excellent fire-support OmniMech, Clan Wolf (and indeed every other Clan) instantly realized the value of the Timber Wolf; thus, production rights to the Timber Wolf were jealously (and successfully) defended. Only through trade, gifts and battlefield salvage has the Timber Wolf entered the armies of other Clans. Until the invasion of the Inner Sphere, production of the Timber Wolf has been limited to a single facility on Strana Mechty. Despite it's prominence among the Wolves during the Clan Invasion, Refusal War and Word of Blake Jihad, the Timber Wolf became increasingly rare following the sundering of ties with the Homeworld Clans during the Wars of Reaving and Blakist scouring of Tamar. Being built by hand at W-7 plant on Weingarten as of 3080, with some parts even being individually machined due to missing data,[1] attrition vastly outstripped supply as the Wolves looked toward other designs. When Alaric Ward forged the Wolf Empire, he left the W-7 facilities to Clan Hell's Horses and ordered the Kallon plant on Thermopolis be retooled for Timber Wolf production, restoring it's position within the Wolves touman. +deployment:First introduced in 2945, the Timber Wolf was designed by Clan Wolf as a second generation OmniMech along with the Gargoyle and the Naga to replace the aging Woodsman. While the Gargoyle may have been a very capable, fast assault OmniMech, and the Naga may have been an excellent fire-support OmniMech, Clan Wolf (and indeed every other Clan) instantly realized the value of the Timber Wolf; thus, production rights to the Timber Wolf were jealously (and successfully) defended. Only through trade, gifts and battlefield salvage has the Timber Wolf entered the armies of other Clans. Until the invasion of the Inner Sphere, production of the Timber Wolf has been limited to a single facility on Strana Mechty. Despite it's prominence among the Wolves during the Clan Invasion, Refusal War and Word of Blake Jihad, the Timber Wolf became increasingly rare following the sundering of ties with the Homeworld Clans during the Wars of Reaving and Blakist scouring of Tamar. Being built by hand at W-7 plant on Weingarten as of 3080, with some parts even being individually machined due to missing data, attrition vastly outstripped supply as the Wolves looked toward other designs. When Alaric Ward forged the Wolf Empire, he left the W-7 facilities to Clan Hell's Horses and ordered the Kallon plant on Thermopolis be retooled for Timber Wolf production, restoring it's position within the Wolves touman. history:Vaguely resembling a cross-over between the MAD (Marauder) and CAT (Catapult) series, the Timber Wolf was tagged with the Inner Sphere reporting name Mad Cat on first contact. (The targeting computer on Phelan Kell's Wolfhound switched between MAD and CAT when trying to identify it; upon analyzing the data recording from Kell's 'Mech, Precentor Martial Anastasius Focht later officially designated it "Mad Cat". diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/Marauder II MAD-10D.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/Marauder II MAD-10D.mtf index efe7b5b13..de1d4525a 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/Marauder II MAD-10D.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/Marauder II MAD-10D.mtf @@ -165,7 +165,7 @@ capabilities:With the Marauder already a powerful and popular 'Mech, the Dragoon deployment:Produced for the AFFS this variant uses an XL Engine, XL Gyro, and Endo-Composite skeleton to save weight. The arms mount a Clan-spec ER PPC and a Medium X-Pulse Laser, while a Large Re-Engineered Laser is fitted to the torso. Four jump jets allow it to cover 120 meters in a jump and the 'Mech can reach a top speed of 64 km/h. Twenty double heat sinks are provided, and the 'Mech carries the maximum amount of armor possible. -history:In 3010 officers of the famous Wolf's Dragoons mercenary unit contracted with Blackwell Industries of New Valencia on the project of modifying the highly successful 75-ton Marauder into a 100-ton assault 'Mech. Working from existing plans the design phase proved to be very short, the process of reinforcing the Marauder chassis turned out to be easier than expected, enhanced by the removal of the finicky and temperamental General Motors Whirlwind Autocannon for a much simpler Large Laser. First appearing with the famous Zeta Battalion before spreading to Alpha Regiment, the Dragoons' enemies soon learned to fear the appearance of Marauder IIs as foreshadowing a major advance, as for the remainder of the Third Succession War it remained the exclusive property of the mysterious Dragoons. This changed after the Fourth Succession War when Colonel Jaime Wolf authorized Blackwell to increase production and allow outside buyers access, on the provision that each sale had to be approved by the Dragoons. Now spreading in limited numbers, the largest buyer outside the Dragoons would be the Miller's Marauders mercenary unit, famed for its almost exclusive use of the Marauder chassis and the secret loan of its DropShips to Zeta Battalion for their climactic rescue of the rest of the Dragoons on Crossing. When new unit commander Major Susan Barber expressed interest in the Marauder II, Colonel Wolf gave Blackwell the go-ahead to supply her with all she needed, by the Clan Invasion the now renamed Barber's Marauder II would boast almost a regiment's worth of the fearsome assault 'Mech. Though Barber's Marauder II would help drive the considerable interest and demand for the powerful assault 'Mech, they would also damage its seeming aura of invincibility following their ignoble destruction by Clan Jade Falcon on Koniz in June 3064. Seeking to rekindle interest in their flagship 'Mech following its disastrous showing on Koniz, GM/Blackwell noted the Vicore Industries triggered refresh of "classic" designs to develop a more powerful and visually refreshed model. The resulting MAD-4S variant was the first widely available Marauder II, Wolf's Dragoons' easing of sale restrictions partly motivated by profit but also as a means to punish the Lyran Alliance for the theft of the Blackwell developed light fusion engine, as of 3067 selling the 'Mech to all interested parties save those the Dragoons were fighting against in the Chaos March; the Word of Blake and the members of Trinity Alliance. The demand for the Marauder II would only increase in the Jihad following the Blakist destruction of GM and Blackwell's production facilities for the 'Mech as part of their vendetta against the Wolf's Dragoons, with many salvaged examples in use among the nations of the Inner Sphere in a large number of variations following the Blakists' fall, the most notable being the MAD-6D developed by the Federated Suns and shared with the Republic of the Sphere. +history:In 3010 officers of the famous Wolf's Dragoons mercenary unit contracted with Blackwell Industries of New Valencia on the project of modifying the highly successful 75-ton Marauder into a 100-ton assault 'Mech. Working from existing plans the design phase proved to be very short, the process of reinforcing the Marauder chassis turned out to be easier than expected, enhanced by the removal of the finicky and temperamental General Motors Whirlwind Autocannon for a much simpler Large Laser. First appearing with the famous Zeta Battalion before spreading to Alpha Regiment, the Dragoons' enemies soon learned to fear the appearance of Marauder IIs as foreshadowing a major advance, as for the remainder of the Third Succession War it remained the exclusive property of the mysterious Dragoons. This changed after the Fourth Succession War when Colonel Jaime Wolf authorized Blackwell to increase production and allow outside buyers access, on the provision that each sale had to be approved by the Dragoons. Now spreading in limited numbers, the largest buyer outside the Dragoons would be the Miller's Marauders mercenary unit, famed for its almost exclusive use of the Marauder chassis and the secret loan of its DropShips to Zeta Battalion for their climactic rescue of the rest of the Dragoons on Crossing. When new unit commander Major Susan Barber expressed interest in the Marauder II, Colonel Wolf gave Blackwell the go-ahead to supply her with all she needed, by the Clan Invasion the now renamed Barber's Marauders would boast almost a regiment's worth of the fearsome assault 'Mech. Though Barber's Marauder II would help drive the considerable interest and demand for the powerful assault 'Mech, they would also damage its seeming aura of invincibility following their ignoble destruction by Clan Jade Falcon on Koniz in June 3064. Seeking to rekindle interest in their flagship 'Mech following its disastrous showing on Koniz, GM/Blackwell noted the Vicore Industries triggered refresh of "classic" designs to develop a more powerful and visually refreshed model. The resulting MAD-4S variant was the first widely available Marauder II, Wolf's Dragoons' easing of sale restrictions partly motivated by profit but also as a means to punish the Lyran Alliance for the theft of the Blackwell developed light fusion engine, as of 3067 selling the 'Mech to all interested parties save those the Dragoons were fighting against in the Chaos March; the Word of Blake and the members of Trinity Alliance. The demand for the Marauder II would only increase in the Jihad following the Blakist destruction of GM and Blackwell's production facilities for the 'Mech as part of their vendetta against the Wolf's Dragoons, with many salvaged examples in use among the nations of the Inner Sphere in a large number of variations following the Blakists' fall, the most notable being the MAD-6D developed by the Federated Suns and shared with the Republic of the Sphere. manufacturer:General Motors/Blackwell Corporation primaryfactory:New Valencia diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/Marauder II MAD-5A.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/Marauder II MAD-5A.mtf index de2cba55d..a90f6f888 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/Marauder II MAD-5A.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/Marauder II MAD-5A.mtf @@ -163,7 +163,7 @@ capabilities:With the Marauder already a powerful and popular 'Mech, the Dragoon deployment:Retaining only the two Magna Mk II Medium Lasers, the 5A variant of the Marauder II carries as its primary weapons a pair of Magna Firestar ER PPCs in its arms which give it a powerful long range punch compared to the 4A. The ER PPCs are backed up by a right torso-mounted Mydron Excel LB-X Autocannon/10 which gives the Marauder II the tactical flexibility of using both solid and cluster rounds. Curiously the 5A is built with CASE only in its right torso, yet its three ton LB-X Autocannon ammunition bay sits in the left torso, leading some observers to suggest another projectile weapon field kit variant was being contemplated. -history:In 3010 officers of the famous Wolf's Dragoons mercenary unit contracted with Blackwell Industries of New Valencia on the project of modifying the highly successful 75-ton Marauder into a 100-ton assault 'Mech. Working from existing plans the design phase proved to be very short, the process of reinforcing the Marauder chassis turned out to be easier than expected, enhanced by the removal of the finicky and temperamental General Motors Whirlwind Autocannon for a much simpler Large Laser. First appearing with the famous Zeta Battalion before spreading to Alpha Regiment, the Dragoons' enemies soon learned to fear the appearance of Marauder IIs as foreshadowing a major advance, as for the remainder of the Third Succession War it remained the exclusive property of the mysterious Dragoons. This changed after the Fourth Succession War when Colonel Jaime Wolf authorized Blackwell to increase production and allow outside buyers access, on the provision that each sale had to be approved by the Dragoons. Now spreading in limited numbers, the largest buyer outside the Dragoons would be the Miller's Marauders mercenary unit, famed for its almost exclusive use of the Marauder chassis and the secret loan of its DropShips to Zeta Battalion for their climactic rescue of the rest of the Dragoons on Crossing. When new unit commander Major Susan Barber expressed interest in the Marauder II, Colonel Wolf gave Blackwell the go-ahead to supply her with all she needed, by the Clan Invasion the now renamed Barber's Marauder II would boast almost a regiment's worth of the fearsome assault 'Mech. Though Barber's Marauder II would help drive the considerable interest and demand for the powerful assault 'Mech, they would also damage its seeming aura of invincibility following their ignoble destruction by Clan Jade Falcon on Koniz in June 3064. Seeking to rekindle interest in their flagship 'Mech following its disastrous showing on Koniz, GM/Blackwell noted the Vicore Industries triggered refresh of "classic" designs to develop a more powerful and visually refreshed model. The resulting MAD-4S variant was the first widely available Marauder II, Wolf's Dragoons' easing of sale restrictions partly motivated by profit but also as a means to punish the Lyran Alliance for the theft of the Blackwell developed light fusion engine, as of 3067 selling the 'Mech to all interested parties save those the Dragoons were fighting against in the Chaos March; the Word of Blake and the members of Trinity Alliance. The demand for the Marauder II would only increase in the Jihad following the Blakist destruction of GM and Blackwell's production facilities for the 'Mech as part of their vendetta against the Wolf's Dragoons, with many salvaged examples in use among the nations of the Inner Sphere in a large number of variations following the Blakists' fall, the most notable being the MAD-6D developed by the Federated Suns and shared with the Republic of the Sphere. +history:In 3010 officers of the famous Wolf's Dragoons mercenary unit contracted with Blackwell Industries of New Valencia on the project of modifying the highly successful 75-ton Marauder into a 100-ton assault 'Mech. Working from existing plans the design phase proved to be very short, the process of reinforcing the Marauder chassis turned out to be easier than expected, enhanced by the removal of the finicky and temperamental General Motors Whirlwind Autocannon for a much simpler Large Laser. First appearing with the famous Zeta Battalion before spreading to Alpha Regiment, the Dragoons' enemies soon learned to fear the appearance of Marauder IIs as foreshadowing a major advance, as for the remainder of the Third Succession War it remained the exclusive property of the mysterious Dragoons. This changed after the Fourth Succession War when Colonel Jaime Wolf authorized Blackwell to increase production and allow outside buyers access, on the provision that each sale had to be approved by the Dragoons. Now spreading in limited numbers, the largest buyer outside the Dragoons would be the Miller's Marauders mercenary unit, famed for its almost exclusive use of the Marauder chassis and the secret loan of its DropShips to Zeta Battalion for their climactic rescue of the rest of the Dragoons on Crossing. When new unit commander Major Susan Barber expressed interest in the Marauder II, Colonel Wolf gave Blackwell the go-ahead to supply her with all she needed, by the Clan Invasion the now renamed Barber's Marauders would boast almost a regiment's worth of the fearsome assault 'Mech. Though Barber's Marauder II would help drive the considerable interest and demand for the powerful assault 'Mech, they would also damage its seeming aura of invincibility following their ignoble destruction by Clan Jade Falcon on Koniz in June 3064. Seeking to rekindle interest in their flagship 'Mech following its disastrous showing on Koniz, GM/Blackwell noted the Vicore Industries triggered refresh of "classic" designs to develop a more powerful and visually refreshed model. The resulting MAD-4S variant was the first widely available Marauder II, Wolf's Dragoons' easing of sale restrictions partly motivated by profit but also as a means to punish the Lyran Alliance for the theft of the Blackwell developed light fusion engine, as of 3067 selling the 'Mech to all interested parties save those the Dragoons were fighting against in the Chaos March; the Word of Blake and the members of Trinity Alliance. The demand for the Marauder II would only increase in the Jihad following the Blakist destruction of GM and Blackwell's production facilities for the 'Mech as part of their vendetta against the Wolf's Dragoons, with many salvaged examples in use among the nations of the Inner Sphere in a large number of variations following the Blakists' fall, the most notable being the MAD-6D developed by the Federated Suns and shared with the Republic of the Sphere. manufacturer:General Motors/Blackwell Corporation primaryfactory:New Valencia diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/Marauder II MAD-5B.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/Marauder II MAD-5B.mtf index b670b706d..e69383b5f 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/Marauder II MAD-5B.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/Marauder II MAD-5B.mtf @@ -163,7 +163,7 @@ capabilities:With the Marauder already a powerful and popular 'Mech, the Dragoon deployment:This 3050 variant carries the same weaponry as the standard Marauder II, but replaces the LB 10-X autocannon with a Gauss rifle. To make room for this weapon, the MAD-5B only carries sixteen Double Heat Sinks. -history:In 3010 officers of the famous Wolf's Dragoons mercenary unit contracted with Blackwell Industries of New Valencia on the project of modifying the highly successful 75-ton Marauder into a 100-ton assault 'Mech. Working from existing plans the design phase proved to be very short, the process of reinforcing the Marauder chassis turned out to be easier than expected, enhanced by the removal of the finicky and temperamental General Motors Whirlwind Autocannon for a much simpler Large Laser. First appearing with the famous Zeta Battalion before spreading to Alpha Regiment, the Dragoons' enemies soon learned to fear the appearance of Marauder IIs as foreshadowing a major advance, as for the remainder of the Third Succession War it remained the exclusive property of the mysterious Dragoons. This changed after the Fourth Succession War when Colonel Jaime Wolf authorized Blackwell to increase production and allow outside buyers access, on the provision that each sale had to be approved by the Dragoons. Now spreading in limited numbers, the largest buyer outside the Dragoons would be the Miller's Marauders mercenary unit, famed for its almost exclusive use of the Marauder chassis and the secret loan of its DropShips to Zeta Battalion for their climactic rescue of the rest of the Dragoons on Crossing. When new unit commander Major Susan Barber expressed interest in the Marauder II, Colonel Wolf gave Blackwell the go-ahead to supply her with all she needed, by the Clan Invasion the now renamed Barber's Marauder II would boast almost a regiment's worth of the fearsome assault 'Mech. Though Barber's Marauder II would help drive the considerable interest and demand for the powerful assault 'Mech, they would also damage its seeming aura of invincibility following their ignoble destruction by Clan Jade Falcon on Koniz in June 3064. Seeking to rekindle interest in their flagship 'Mech following its disastrous showing on Koniz, GM/Blackwell noted the Vicore Industries triggered refresh of "classic" designs to develop a more powerful and visually refreshed model. The resulting MAD-4S variant was the first widely available Marauder II, Wolf's Dragoons' easing of sale restrictions partly motivated by profit but also as a means to punish the Lyran Alliance for the theft of the Blackwell developed light fusion engine, as of 3067 selling the 'Mech to all interested parties save those the Dragoons were fighting against in the Chaos March; the Word of Blake and the members of Trinity Alliance. The demand for the Marauder II would only increase in the Jihad following the Blakist destruction of GM and Blackwell's production facilities for the 'Mech as part of their vendetta against the Wolf's Dragoons, with many salvaged examples in use among the nations of the Inner Sphere in a large number of variations following the Blakists' fall, the most notable being the MAD-6D developed by the Federated Suns and shared with the Republic of the Sphere. +history:In 3010 officers of the famous Wolf's Dragoons mercenary unit contracted with Blackwell Industries of New Valencia on the project of modifying the highly successful 75-ton Marauder into a 100-ton assault 'Mech. Working from existing plans the design phase proved to be very short, the process of reinforcing the Marauder chassis turned out to be easier than expected, enhanced by the removal of the finicky and temperamental General Motors Whirlwind Autocannon for a much simpler Large Laser. First appearing with the famous Zeta Battalion before spreading to Alpha Regiment, the Dragoons' enemies soon learned to fear the appearance of Marauder IIs as foreshadowing a major advance, as for the remainder of the Third Succession War it remained the exclusive property of the mysterious Dragoons. This changed after the Fourth Succession War when Colonel Jaime Wolf authorized Blackwell to increase production and allow outside buyers access, on the provision that each sale had to be approved by the Dragoons. Now spreading in limited numbers, the largest buyer outside the Dragoons would be the Miller's Marauders mercenary unit, famed for its almost exclusive use of the Marauder chassis and the secret loan of its DropShips to Zeta Battalion for their climactic rescue of the rest of the Dragoons on Crossing. When new unit commander Major Susan Barber expressed interest in the Marauder II, Colonel Wolf gave Blackwell the go-ahead to supply her with all she needed, by the Clan Invasion the now renamed Barber's Marauders would boast almost a regiment's worth of the fearsome assault 'Mech. Though Barber's Marauder II would help drive the considerable interest and demand for the powerful assault 'Mech, they would also damage its seeming aura of invincibility following their ignoble destruction by Clan Jade Falcon on Koniz in June 3064. Seeking to rekindle interest in their flagship 'Mech following its disastrous showing on Koniz, GM/Blackwell noted the Vicore Industries triggered refresh of "classic" designs to develop a more powerful and visually refreshed model. The resulting MAD-4S variant was the first widely available Marauder II, Wolf's Dragoons' easing of sale restrictions partly motivated by profit but also as a means to punish the Lyran Alliance for the theft of the Blackwell developed light fusion engine, as of 3067 selling the 'Mech to all interested parties save those the Dragoons were fighting against in the Chaos March; the Word of Blake and the members of Trinity Alliance. The demand for the Marauder II would only increase in the Jihad following the Blakist destruction of GM and Blackwell's production facilities for the 'Mech as part of their vendetta against the Wolf's Dragoons, with many salvaged examples in use among the nations of the Inner Sphere in a large number of variations following the Blakists' fall, the most notable being the MAD-6D developed by the Federated Suns and shared with the Republic of the Sphere. manufacturer:Field Refit primaryfactory:Various diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/Marauder II MAD-5C.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/Marauder II MAD-5C.mtf index ec8a1579b..279b95196 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/Marauder II MAD-5C.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/Marauder II MAD-5C.mtf @@ -163,7 +163,7 @@ capabilities:With the Marauder already a powerful and popular 'Mech, the Dragoon deployment:This version carries 32 single heat sinks. The weapons are those of a standard Marauder II but this time an Ultra Autocannon/5 is carried instead of the LB 10-X. -history:In 3010 officers of the famous Wolf's Dragoons mercenary unit contracted with Blackwell Industries of New Valencia on the project of modifying the highly successful 75-ton Marauder into a 100-ton assault 'Mech. Working from existing plans the design phase proved to be very short, the process of reinforcing the Marauder chassis turned out to be easier than expected, enhanced by the removal of the finicky and temperamental General Motors Whirlwind Autocannon for a much simpler Large Laser. First appearing with the famous Zeta Battalion before spreading to Alpha Regiment, the Dragoons' enemies soon learned to fear the appearance of Marauder IIs as foreshadowing a major advance, as for the remainder of the Third Succession War it remained the exclusive property of the mysterious Dragoons. This changed after the Fourth Succession War when Colonel Jaime Wolf authorized Blackwell to increase production and allow outside buyers access, on the provision that each sale had to be approved by the Dragoons. Now spreading in limited numbers, the largest buyer outside the Dragoons would be the Miller's Marauders mercenary unit, famed for its almost exclusive use of the Marauder chassis and the secret loan of its DropShips to Zeta Battalion for their climactic rescue of the rest of the Dragoons on Crossing. When new unit commander Major Susan Barber expressed interest in the Marauder II, Colonel Wolf gave Blackwell the go-ahead to supply her with all she needed, by the Clan Invasion the now renamed Barber's Marauder II would boast almost a regiment's worth of the fearsome assault 'Mech. Though Barber's Marauder II would help drive the considerable interest and demand for the powerful assault 'Mech, they would also damage its seeming aura of invincibility following their ignoble destruction by Clan Jade Falcon on Koniz in June 3064. Seeking to rekindle interest in their flagship 'Mech following its disastrous showing on Koniz, GM/Blackwell noted the Vicore Industries triggered refresh of "classic" designs to develop a more powerful and visually refreshed model. The resulting MAD-4S variant was the first widely available Marauder II, Wolf's Dragoons' easing of sale restrictions partly motivated by profit but also as a means to punish the Lyran Alliance for the theft of the Blackwell developed light fusion engine, as of 3067 selling the 'Mech to all interested parties save those the Dragoons were fighting against in the Chaos March; the Word of Blake and the members of Trinity Alliance. The demand for the Marauder II would only increase in the Jihad following the Blakist destruction of GM and Blackwell's production facilities for the 'Mech as part of their vendetta against the Wolf's Dragoons, with many salvaged examples in use among the nations of the Inner Sphere in a large number of variations following the Blakists' fall, the most notable being the MAD-6D developed by the Federated Suns and shared with the Republic of the Sphere. +history:In 3010 officers of the famous Wolf's Dragoons mercenary unit contracted with Blackwell Industries of New Valencia on the project of modifying the highly successful 75-ton Marauder into a 100-ton assault 'Mech. Working from existing plans the design phase proved to be very short, the process of reinforcing the Marauder chassis turned out to be easier than expected, enhanced by the removal of the finicky and temperamental General Motors Whirlwind Autocannon for a much simpler Large Laser. First appearing with the famous Zeta Battalion before spreading to Alpha Regiment, the Dragoons' enemies soon learned to fear the appearance of Marauder IIs as foreshadowing a major advance, as for the remainder of the Third Succession War it remained the exclusive property of the mysterious Dragoons. This changed after the Fourth Succession War when Colonel Jaime Wolf authorized Blackwell to increase production and allow outside buyers access, on the provision that each sale had to be approved by the Dragoons. Now spreading in limited numbers, the largest buyer outside the Dragoons would be the Miller's Marauders mercenary unit, famed for its almost exclusive use of the Marauder chassis and the secret loan of its DropShips to Zeta Battalion for their climactic rescue of the rest of the Dragoons on Crossing. When new unit commander Major Susan Barber expressed interest in the Marauder II, Colonel Wolf gave Blackwell the go-ahead to supply her with all she needed, by the Clan Invasion the now renamed Barber's Marauders would boast almost a regiment's worth of the fearsome assault 'Mech. Though Barber's Marauder II would help drive the considerable interest and demand for the powerful assault 'Mech, they would also damage its seeming aura of invincibility following their ignoble destruction by Clan Jade Falcon on Koniz in June 3064. Seeking to rekindle interest in their flagship 'Mech following its disastrous showing on Koniz, GM/Blackwell noted the Vicore Industries triggered refresh of "classic" designs to develop a more powerful and visually refreshed model. The resulting MAD-4S variant was the first widely available Marauder II, Wolf's Dragoons' easing of sale restrictions partly motivated by profit but also as a means to punish the Lyran Alliance for the theft of the Blackwell developed light fusion engine, as of 3067 selling the 'Mech to all interested parties save those the Dragoons were fighting against in the Chaos March; the Word of Blake and the members of Trinity Alliance. The demand for the Marauder II would only increase in the Jihad following the Blakist destruction of GM and Blackwell's production facilities for the 'Mech as part of their vendetta against the Wolf's Dragoons, with many salvaged examples in use among the nations of the Inner Sphere in a large number of variations following the Blakists' fall, the most notable being the MAD-6D developed by the Federated Suns and shared with the Republic of the Sphere. manufacturer:Field Refit primaryfactory:Various diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/Marauder II MAD-6A.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/Marauder II MAD-6A.mtf index f8ac78d17..57c430598 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/Marauder II MAD-6A.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/Marauder II MAD-6A.mtf @@ -165,7 +165,7 @@ capabilities:With the Marauder already a powerful and popular 'Mech, the Dragoon deployment:Introduced during the Dark Age this variant carries an ER PPC and Medium X-Pulse Laser in each arm, while the torso weapon mount carries an Ultra AC/10 with three tons of ammunition in a CASE protected bay. Powered by a light fusion engine and equipped with a Compact Gyro, the 'Mech is protected by nineteen tons of armor and carries eighteen double heat sinks. -history:In 3010 officers of the famous Wolf's Dragoons mercenary unit contracted with Blackwell Industries of New Valencia on the project of modifying the highly successful 75-ton Marauder into a 100-ton assault 'Mech. Working from existing plans the design phase proved to be very short, the process of reinforcing the Marauder chassis turned out to be easier than expected, enhanced by the removal of the finicky and temperamental General Motors Whirlwind Autocannon for a much simpler Large Laser. First appearing with the famous Zeta Battalion before spreading to Alpha Regiment, the Dragoons' enemies soon learned to fear the appearance of Marauder IIs as foreshadowing a major advance, as for the remainder of the Third Succession War it remained the exclusive property of the mysterious Dragoons. This changed after the Fourth Succession War when Colonel Jaime Wolf authorized Blackwell to increase production and allow outside buyers access, on the provision that each sale had to be approved by the Dragoons. Now spreading in limited numbers, the largest buyer outside the Dragoons would be the Miller's Marauders mercenary unit, famed for its almost exclusive use of the Marauder chassis and the secret loan of its DropShips to Zeta Battalion for their climactic rescue of the rest of the Dragoons on Crossing. When new unit commander Major Susan Barber expressed interest in the Marauder II, Colonel Wolf gave Blackwell the go-ahead to supply her with all she needed, by the Clan Invasion the now renamed Barber's Marauder II would boast almost a regiment's worth of the fearsome assault 'Mech. Though Barber's Marauder II would help drive the considerable interest and demand for the powerful assault 'Mech, they would also damage its seeming aura of invincibility following their ignoble destruction by Clan Jade Falcon on Koniz in June 3064. Seeking to rekindle interest in their flagship 'Mech following its disastrous showing on Koniz, GM/Blackwell noted the Vicore Industries triggered refresh of "classic" designs to develop a more powerful and visually refreshed model. The resulting MAD-4S variant was the first widely available Marauder II, Wolf's Dragoons' easing of sale restrictions partly motivated by profit but also as a means to punish the Lyran Alliance for the theft of the Blackwell developed light fusion engine, as of 3067 selling the 'Mech to all interested parties save those the Dragoons were fighting against in the Chaos March; the Word of Blake and the members of Trinity Alliance. The demand for the Marauder II would only increase in the Jihad following the Blakist destruction of GM and Blackwell's production facilities for the 'Mech as part of their vendetta against the Wolf's Dragoons, with many salvaged examples in use among the nations of the Inner Sphere in a large number of variations following the Blakists' fall, the most notable being the MAD-6D developed by the Federated Suns and shared with the Republic of the Sphere. +history:In 3010 officers of the famous Wolf's Dragoons mercenary unit contracted with Blackwell Industries of New Valencia on the project of modifying the highly successful 75-ton Marauder into a 100-ton assault 'Mech. Working from existing plans the design phase proved to be very short, the process of reinforcing the Marauder chassis turned out to be easier than expected, enhanced by the removal of the finicky and temperamental General Motors Whirlwind Autocannon for a much simpler Large Laser. First appearing with the famous Zeta Battalion before spreading to Alpha Regiment, the Dragoons' enemies soon learned to fear the appearance of Marauder IIs as foreshadowing a major advance, as for the remainder of the Third Succession War it remained the exclusive property of the mysterious Dragoons. This changed after the Fourth Succession War when Colonel Jaime Wolf authorized Blackwell to increase production and allow outside buyers access, on the provision that each sale had to be approved by the Dragoons. Now spreading in limited numbers, the largest buyer outside the Dragoons would be the Miller's Marauders mercenary unit, famed for its almost exclusive use of the Marauder chassis and the secret loan of its DropShips to Zeta Battalion for their climactic rescue of the rest of the Dragoons on Crossing. When new unit commander Major Susan Barber expressed interest in the Marauder II, Colonel Wolf gave Blackwell the go-ahead to supply her with all she needed, by the Clan Invasion the now renamed Barber's Marauders would boast almost a regiment's worth of the fearsome assault 'Mech. Though Barber's Marauder II would help drive the considerable interest and demand for the powerful assault 'Mech, they would also damage its seeming aura of invincibility following their ignoble destruction by Clan Jade Falcon on Koniz in June 3064. Seeking to rekindle interest in their flagship 'Mech following its disastrous showing on Koniz, GM/Blackwell noted the Vicore Industries triggered refresh of "classic" designs to develop a more powerful and visually refreshed model. The resulting MAD-4S variant was the first widely available Marauder II, Wolf's Dragoons' easing of sale restrictions partly motivated by profit but also as a means to punish the Lyran Alliance for the theft of the Blackwell developed light fusion engine, as of 3067 selling the 'Mech to all interested parties save those the Dragoons were fighting against in the Chaos March; the Word of Blake and the members of Trinity Alliance. The demand for the Marauder II would only increase in the Jihad following the Blakist destruction of GM and Blackwell's production facilities for the 'Mech as part of their vendetta against the Wolf's Dragoons, with many salvaged examples in use among the nations of the Inner Sphere in a large number of variations following the Blakists' fall, the most notable being the MAD-6D developed by the Federated Suns and shared with the Republic of the Sphere. manufacturer:Independence Weaponry primaryfactory:Quentin diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/Marauder II MAD-6C.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/Marauder II MAD-6C.mtf index 10f3544ef..f607a4e0f 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/Marauder II MAD-6C.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/Marauder II MAD-6C.mtf @@ -165,7 +165,7 @@ capabilities:With the Marauder already a powerful and popular 'Mech, the Dragoon deployment:This Marauder II carries three ER PPCs and two ER medium lasers. What truly makes it frightening to opposing pilots is the fact it carries maximum armor and uses a Compact Gyro to carry twenty-two double heat sinks, enough to allow it to fire its main battery with very little heat buildup. -history:In 3010 officers of the famous Wolf's Dragoons mercenary unit contracted with Blackwell Industries of New Valencia on the project of modifying the highly successful 75-ton Marauder into a 100-ton assault 'Mech. Working from existing plans the design phase proved to be very short, the process of reinforcing the Marauder chassis turned out to be easier than expected, enhanced by the removal of the finicky and temperamental General Motors Whirlwind Autocannon for a much simpler Large Laser. First appearing with the famous Zeta Battalion before spreading to Alpha Regiment, the Dragoons' enemies soon learned to fear the appearance of Marauder IIs as foreshadowing a major advance, as for the remainder of the Third Succession War it remained the exclusive property of the mysterious Dragoons. This changed after the Fourth Succession War when Colonel Jaime Wolf authorized Blackwell to increase production and allow outside buyers access, on the provision that each sale had to be approved by the Dragoons. Now spreading in limited numbers, the largest buyer outside the Dragoons would be the Miller's Marauders mercenary unit, famed for its almost exclusive use of the Marauder chassis and the secret loan of its DropShips to Zeta Battalion for their climactic rescue of the rest of the Dragoons on Crossing. When new unit commander Major Susan Barber expressed interest in the Marauder II, Colonel Wolf gave Blackwell the go-ahead to supply her with all she needed, by the Clan Invasion the now renamed Barber's Marauder II would boast almost a regiment's worth of the fearsome assault 'Mech. Though Barber's Marauder II would help drive the considerable interest and demand for the powerful assault 'Mech, they would also damage its seeming aura of invincibility following their ignoble destruction by Clan Jade Falcon on Koniz in June 3064. Seeking to rekindle interest in their flagship 'Mech following its disastrous showing on Koniz, GM/Blackwell noted the Vicore Industries triggered refresh of "classic" designs to develop a more powerful and visually refreshed model. The resulting MAD-4S variant was the first widely available Marauder II, Wolf's Dragoons' easing of sale restrictions partly motivated by profit but also as a means to punish the Lyran Alliance for the theft of the Blackwell developed light fusion engine, as of 3067 selling the 'Mech to all interested parties save those the Dragoons were fighting against in the Chaos March; the Word of Blake and the members of Trinity Alliance. The demand for the Marauder II would only increase in the Jihad following the Blakist destruction of GM and Blackwell's production facilities for the 'Mech as part of their vendetta against the Wolf's Dragoons, with many salvaged examples in use among the nations of the Inner Sphere in a large number of variations following the Blakists' fall, the most notable being the MAD-6D developed by the Federated Suns and shared with the Republic of the Sphere. +history:In 3010 officers of the famous Wolf's Dragoons mercenary unit contracted with Blackwell Industries of New Valencia on the project of modifying the highly successful 75-ton Marauder into a 100-ton assault 'Mech. Working from existing plans the design phase proved to be very short, the process of reinforcing the Marauder chassis turned out to be easier than expected, enhanced by the removal of the finicky and temperamental General Motors Whirlwind Autocannon for a much simpler Large Laser. First appearing with the famous Zeta Battalion before spreading to Alpha Regiment, the Dragoons' enemies soon learned to fear the appearance of Marauder IIs as foreshadowing a major advance, as for the remainder of the Third Succession War it remained the exclusive property of the mysterious Dragoons. This changed after the Fourth Succession War when Colonel Jaime Wolf authorized Blackwell to increase production and allow outside buyers access, on the provision that each sale had to be approved by the Dragoons. Now spreading in limited numbers, the largest buyer outside the Dragoons would be the Miller's Marauders mercenary unit, famed for its almost exclusive use of the Marauder chassis and the secret loan of its DropShips to Zeta Battalion for their climactic rescue of the rest of the Dragoons on Crossing. When new unit commander Major Susan Barber expressed interest in the Marauder II, Colonel Wolf gave Blackwell the go-ahead to supply her with all she needed, by the Clan Invasion the now renamed Barber's Marauders would boast almost a regiment's worth of the fearsome assault 'Mech. Though Barber's Marauder II would help drive the considerable interest and demand for the powerful assault 'Mech, they would also damage its seeming aura of invincibility following their ignoble destruction by Clan Jade Falcon on Koniz in June 3064. Seeking to rekindle interest in their flagship 'Mech following its disastrous showing on Koniz, GM/Blackwell noted the Vicore Industries triggered refresh of "classic" designs to develop a more powerful and visually refreshed model. The resulting MAD-4S variant was the first widely available Marauder II, Wolf's Dragoons' easing of sale restrictions partly motivated by profit but also as a means to punish the Lyran Alliance for the theft of the Blackwell developed light fusion engine, as of 3067 selling the 'Mech to all interested parties save those the Dragoons were fighting against in the Chaos March; the Word of Blake and the members of Trinity Alliance. The demand for the Marauder II would only increase in the Jihad following the Blakist destruction of GM and Blackwell's production facilities for the 'Mech as part of their vendetta against the Wolf's Dragoons, with many salvaged examples in use among the nations of the Inner Sphere in a large number of variations following the Blakists' fall, the most notable being the MAD-6D developed by the Federated Suns and shared with the Republic of the Sphere. manufacturer:Independence Weaponry primaryfactory:Quentin diff --git a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/Marauder II MAD-8K.mtf b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/Marauder II MAD-8K.mtf index c3d8db5bc..498125be3 100644 --- a/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/Marauder II MAD-8K.mtf +++ b/megameklab/data/mechfiles/mechs/Rec Guides ilClan/Vol 5/Marauder II MAD-8K.mtf @@ -163,7 +163,7 @@ capabilities:With the Marauder already a powerful and popular 'Mech, the Dragoon deployment:A Draconis Combine variant produced by Independence Weaponry, this variant carries a standard PPC and a Light PPC in each arm. A Gauss rifle is in the torso mount and is protected by a CASE II system. Maximum protection is provided by twenty-five and a half tons of Ballistic-Reinforced Armor. To save weight for the armor, an XL Engine is fitted. -history:In 3010 officers of the famous Wolf's Dragoons mercenary unit contracted with Blackwell Industries of New Valencia on the project of modifying the highly successful 75-ton Marauder into a 100-ton assault 'Mech. Working from existing plans the design phase proved to be very short, the process of reinforcing the Marauder chassis turned out to be easier than expected, enhanced by the removal of the finicky and temperamental General Motors Whirlwind Autocannon for a much simpler Large Laser. First appearing with the famous Zeta Battalion before spreading to Alpha Regiment, the Dragoons' enemies soon learned to fear the appearance of Marauder IIs as foreshadowing a major advance, as for the remainder of the Third Succession War it remained the exclusive property of the mysterious Dragoons. This changed after the Fourth Succession War when Colonel Jaime Wolf authorized Blackwell to increase production and allow outside buyers access, on the provision that each sale had to be approved by the Dragoons. Now spreading in limited numbers, the largest buyer outside the Dragoons would be the Miller's Marauders mercenary unit, famed for its almost exclusive use of the Marauder chassis and the secret loan of its DropShips to Zeta Battalion for their climactic rescue of the rest of the Dragoons on Crossing. When new unit commander Major Susan Barber expressed interest in the Marauder II, Colonel Wolf gave Blackwell the go-ahead to supply her with all she needed, by the Clan Invasion the now renamed Barber's Marauder II would boast almost a regiment's worth of the fearsome assault 'Mech. Though Barber's Marauder II would help drive the considerable interest and demand for the powerful assault 'Mech, they would also damage its seeming aura of invincibility following their ignoble destruction by Clan Jade Falcon on Koniz in June 3064. Seeking to rekindle interest in their flagship 'Mech following its disastrous showing on Koniz, GM/Blackwell noted the Vicore Industries triggered refresh of "classic" designs to develop a more powerful and visually refreshed model. The resulting MAD-4S variant was the first widely available Marauder II, Wolf's Dragoons' easing of sale restrictions partly motivated by profit but also as a means to punish the Lyran Alliance for the theft of the Blackwell developed light fusion engine, as of 3067 selling the 'Mech to all interested parties save those the Dragoons were fighting against in the Chaos March; the Word of Blake and the members of Trinity Alliance. The demand for the Marauder II would only increase in the Jihad following the Blakist destruction of GM and Blackwell's production facilities for the 'Mech as part of their vendetta against the Wolf's Dragoons, with many salvaged examples in use among the nations of the Inner Sphere in a large number of variations following the Blakists' fall, the most notable being the MAD-6D developed by the Federated Suns and shared with the Republic of the Sphere. +history:In 3010 officers of the famous Wolf's Dragoons mercenary unit contracted with Blackwell Industries of New Valencia on the project of modifying the highly successful 75-ton Marauder into a 100-ton assault 'Mech. Working from existing plans the design phase proved to be very short, the process of reinforcing the Marauder chassis turned out to be easier than expected, enhanced by the removal of the finicky and temperamental General Motors Whirlwind Autocannon for a much simpler Large Laser. First appearing with the famous Zeta Battalion before spreading to Alpha Regiment, the Dragoons' enemies soon learned to fear the appearance of Marauder IIs as foreshadowing a major advance, as for the remainder of the Third Succession War it remained the exclusive property of the mysterious Dragoons. This changed after the Fourth Succession War when Colonel Jaime Wolf authorized Blackwell to increase production and allow outside buyers access, on the provision that each sale had to be approved by the Dragoons. Now spreading in limited numbers, the largest buyer outside the Dragoons would be the Miller's Marauders mercenary unit, famed for its almost exclusive use of the Marauder chassis and the secret loan of its DropShips to Zeta Battalion for their climactic rescue of the rest of the Dragoons on Crossing. When new unit commander Major Susan Barber expressed interest in the Marauder II, Colonel Wolf gave Blackwell the go-ahead to supply her with all she needed, by the Clan Invasion the now renamed Barber's Marauders would boast almost a regiment's worth of the fearsome assault 'Mech. Though Barber's Marauder II would help drive the considerable interest and demand for the powerful assault 'Mech, they would also damage its seeming aura of invincibility following their ignoble destruction by Clan Jade Falcon on Koniz in June 3064. Seeking to rekindle interest in their flagship 'Mech following its disastrous showing on Koniz, GM/Blackwell noted the Vicore Industries triggered refresh of "classic" designs to develop a more powerful and visually refreshed model. The resulting MAD-4S variant was the first widely available Marauder II, Wolf's Dragoons' easing of sale restrictions partly motivated by profit but also as a means to punish the Lyran Alliance for the theft of the Blackwell developed light fusion engine, as of 3067 selling the 'Mech to all interested parties save those the Dragoons were fighting against in the Chaos March; the Word of Blake and the members of Trinity Alliance. The demand for the Marauder II would only increase in the Jihad following the Blakist destruction of GM and Blackwell's production facilities for the 'Mech as part of their vendetta against the Wolf's Dragoons, with many salvaged examples in use among the nations of the Inner Sphere in a large number of variations following the Blakists' fall, the most notable being the MAD-6D developed by the Federated Suns and shared with the Republic of the Sphere. manufacturer:Independence Weaponry primaryfactory:Quentin diff --git a/megameklab/data/mechfiles/mechs/Shrapnel/Vol 14/Shadow Hawk SHD-3H.mtf b/megameklab/data/mechfiles/mechs/Shrapnel/Vol 14/Shadow Hawk SHD-3H.mtf index 92027540e..f46417405 100644 --- a/megameklab/data/mechfiles/mechs/Shrapnel/Vol 14/Shadow Hawk SHD-3H.mtf +++ b/megameklab/data/mechfiles/mechs/Shrapnel/Vol 14/Shadow Hawk SHD-3H.mtf @@ -158,7 +158,7 @@ Foot Actuator -Empty- overview: The Shadow Hawk, from its inception, was designed to be a multi-purpose generalist. One of the fabled "trio" of 55-ton 'Mechs, its comrades are much more specialized designs. The Griffin is a long-ranged support platform, the Wolverine a heavy scout and skirmisher. The Shadow Hawk, however, can accomplish both roles—albeit, not as well as the two other designs. This has not hampered its popularity, and it has offered sterling service from the first days it entered battle. -capabilities: Most Shadow Hawks carry a varied array of weaponry. With both short and long-ranged weapons, missiles, lasers, and autocannons, the Shadow Hawk is never on a battlefield where it cannot contribute at least some firepower. Its speed is average for a design of its size, while the jump jets give it some maneuverability even if broken terrain. If the Shadow Hawk has one limitation, it is that it has difficulty bringing forward overwhelming firepower in any specific situation, causing some to disparage it as badly designed and flawed. +capabilities: Most Shadow Hawks carry a varied array of weaponry. With both short and long-ranged weapons, missiles, lasers, and autocannons, the Shadow Hawk is never on a battlefield where it cannot contribute at least some firepower. Its speed is average for a design of its size, while the jump jets give it some maneuverability even on broken terrain. If the Shadow Hawk has one limitation, it is that it has difficulty bringing forward overwhelming firepower in any specific situation, causing some to disparage it as badly designed and flawed. deployment: The Shadow Hawk is a widespread design. Every Successor State makes good use of the BattleMech, while the factories on Dunianshire ensure that a steady number enter periphery forces every year. As such a flexible design, it has a home in nearly every type of command, and few are the commanders who cannot find a use for their Shadow Hawk. Neither the massive number of upgrade kits nor the Jihad managed to put a dent in the number of SHD-2H's in service. Even today, the militaries from the greatest house to the lowliest mercenary group still use this venerable variant. systemmanufacturer:CHASSIS:Earthwerks systemmode:CHASSIS:SHD diff --git a/megameklab/data/mechfiles/mechs/Shrapnel/Vol 14/Shadow Hawk SHD-3H2.mtf b/megameklab/data/mechfiles/mechs/Shrapnel/Vol 14/Shadow Hawk SHD-3H2.mtf index 461b84615..de6f49c01 100644 --- a/megameklab/data/mechfiles/mechs/Shrapnel/Vol 14/Shadow Hawk SHD-3H2.mtf +++ b/megameklab/data/mechfiles/mechs/Shrapnel/Vol 14/Shadow Hawk SHD-3H2.mtf @@ -166,7 +166,7 @@ IS Ferro-Fibrous -Empty- overview: The Shadow Hawk, from its inception, was designed to be a multi-purpose generalist. One of the fabled "trio" of 55-ton 'Mechs, its comrades are much more specialized designs. The Griffin is a long-ranged support platform, the Wolverine a heavy scout and skirmisher. The Shadow Hawk, however, can accomplish both roles—albeit, not as well as the two other designs. This has not hampered its popularity, and it has offered sterling service from the first days it entered battle. -capabilities: Most Shadow Hawks carry a varied array of weaponry. With both short and long-ranged weapons, missiles, lasers, and autocannons, the Shadow Hawk is never on a battlefield where it cannot contribute at least some firepower. Its speed is average for a design of its size, while the jump jets give it some maneuverability even if broken terrain. If the Shadow Hawk has one limitation, it is that it has difficulty bringing forward overwhelming firepower in any specific situation, causing some to disparage it as badly designed and flawed. +capabilities: Most Shadow Hawks carry a varied array of weaponry. With both short and long-ranged weapons, missiles, lasers, and autocannons, the Shadow Hawk is never on a battlefield where it cannot contribute at least some firepower. Its speed is average for a design of its size, while the jump jets give it some maneuverability even on broken terrain. If the Shadow Hawk has one limitation, it is that it has difficulty bringing forward overwhelming firepower in any specific situation, causing some to disparage it as badly designed and flawed. deployment: The Shadow Hawk is a widespread design. Every Successor State makes good use of the BattleMech, while the factories on Dunianshire ensure that a steady number enter periphery forces every year. As such a flexible design, it has a home in nearly every type of command, and few are the commanders who cannot find a use for their Shadow Hawk. Neither the massive number of upgrade kits nor the Jihad managed to put a dent in the number of SHD-2H's in service. Even today, the militaries from the greatest house to the lowliest mercenary group still use this venerable variant. systemmanufacturer:CHASSIS:Earthwerks systemmode:CHASSIS:SHD diff --git a/megameklab/data/mechfiles/mechs/Shrapnel/Vol 17/Wing Wraith TR4.mtf b/megameklab/data/mechfiles/mechs/Shrapnel/Vol 17/Wing Wraith TR4.mtf index 3b6af8851..6e9e07d40 100644 --- a/megameklab/data/mechfiles/mechs/Shrapnel/Vol 17/Wing Wraith TR4.mtf +++ b/megameklab/data/mechfiles/mechs/Shrapnel/Vol 17/Wing Wraith TR4.mtf @@ -1,7 +1,7 @@ generator:Mordel.Net Code Release 2.24.13 on 14-Jun-2024 chassis:'Wing' Wraith model:TR4 -source:Custom Mordel.Net Units +source:Shrapnel 17 Config:Biped TechBase:Inner Sphere diff --git a/megameklab/data/mechfiles/mechs/Shrapnel/Vol 17/Wing Wraith TR6.mtf b/megameklab/data/mechfiles/mechs/Shrapnel/Vol 17/Wing Wraith TR6.mtf index df3652701..db5afa342 100644 --- a/megameklab/data/mechfiles/mechs/Shrapnel/Vol 17/Wing Wraith TR6.mtf +++ b/megameklab/data/mechfiles/mechs/Shrapnel/Vol 17/Wing Wraith TR6.mtf @@ -1,7 +1,7 @@ generator:Mordel.Net Code Release 2.24.13 on 14-Jun-2024 chassis:'Wing' Wraith model:TR6 -source:Custom Mordel.Net Units +source:Shrapnel 17 Config:Biped TechBase:Inner Sphere diff --git a/megameklab/data/mechfiles/mechs/Shrapnel/Vol 17/Wing Wraith TR7.mtf b/megameklab/data/mechfiles/mechs/Shrapnel/Vol 17/Wing Wraith TR7.mtf index bcf279f24..d3ced13ef 100644 --- a/megameklab/data/mechfiles/mechs/Shrapnel/Vol 17/Wing Wraith TR7.mtf +++ b/megameklab/data/mechfiles/mechs/Shrapnel/Vol 17/Wing Wraith TR7.mtf @@ -1,7 +1,7 @@ generator:Mordel.Net Code Release 2.24.13 on 14-Jun-2024 chassis:'Wing' Wraith model:TR7 -source:Custom Mordel.Net Units +source:Shrapnel 17 Config:Biped TechBase:Mixed (IS Chassis) @@ -168,7 +168,7 @@ capabilities:The “Wing” Wraith enhances the base design’s accurate and amm deployment:The new TR7 combines stealth armor, Clan weaponry, and a hefty price tag to create a potent hunter-killer often paired with Raven II’s for covert ops and headhunting missions. At the request of the Death Commandos, the TR7 also features an exceptionally spacious head module. Aftermarket additions to this open cargo space are unconfirmed but can be speculated at, given the Death Commandos’ reputation. -history:The Wing Wraith project, spearheaded by Hellespont Industries, dates back to the Capellan Crusades, but it wasn’t until the 3140s that the mass-produced TR6 variant saw production. The Wraith’s assets were acquired by the Capellan Confederation after Curtiss Hydroponics, the original manufacturer, was forced to sell its military holdings to remain solvent following the Jihad. The destruction of Curtiss Militech’s homeworld, Paradise, by the Regulans during the Jihad significantly contributed to the financial distress that led to this sale. Hellespont Industries capitalized on this opportunity, integrating advanced partial-wing technology into the Wraith design to enhance its maneuverability and heat dissipation capabilities.The TR6’s first major combat deployment occurred during the Victoria Rangers’ assault on Victoria in 3144. However, the results were underwhelming due to the Wraiths being reassigned to unsuitable roles, leading to significant damage and operational issues. Despite this setback, the TR6 found its stride during House Davion’s Operation Cerberus. On Narellan, Wraiths from the Second St. Ives Cheveau-Légers conducted effective raiding operations against the Second Davion Auxiliaries, showcasing their capability in hit-and-run tactics alongside Canopian Agroteras. This success spurred increased orders from various factions, including the Sea Foxes and the Magistracy Armed Forces, solidifying the Wing Wraith’s reputation as a valuable raider and scout hunter in the Capellan Confederation's arsenal.
+history:The Wing Wraith project, spearheaded by Hellespont Industries, dates back to the Capellan Crusades, but it wasn't until the 3140s that the mass-produced TR6 variant saw production. The Wraith’s assets were acquired by the Capellan Confederation after Curtiss Hydroponics, the original manufacturer, was forced to sell its military holdings to remain solvent following the Jihad. The destruction of Curtiss Militech’s homeworld, Paradise, by the Regulans during the Jihad significantly contributed to the financial distress that led to this sale. Hellespont Industries capitalized on this opportunity, integrating advanced partial-wing technology into the Wraith design to enhance its maneuverability and heat dissipation capabilities.The TR6’s first major combat deployment occurred during the Victoria Rangers’ assault on Victoria in 3144. However, the results were underwhelming due to the Wraiths being reassigned to unsuitable roles, leading to significant damage and operational issues. Despite this setback, the TR6 found its stride during House Davion’s Operation Cerberus. On Narellan, Wraiths from the Second St. Ives Cheveau-Légers conducted effective raiding operations against the Second Davion Auxiliaries, showcasing their capability in hit-and-run tactics alongside Canopian Agroteras. This success spurred increased orders from various factions, including the Sea Foxes and the Magistracy Armed Forces, solidifying the Wing Wraith’s reputation as a valuable raider and scout hunter in the Capellan Confederation's arsenal.
manufacturer:Hellespont Industries primaryfactory:Sian diff --git a/megameklab/data/mechfiles/mechs/Shrapnel/Vol 4/SuburbanMech UM-R100.mtf b/megameklab/data/mechfiles/mechs/Shrapnel/Vol 4/SuburbanMech UM-R100.mtf index bef36cfba..e279fd92c 100644 --- a/megameklab/data/mechfiles/mechs/Shrapnel/Vol 4/SuburbanMech UM-R100.mtf +++ b/megameklab/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 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. manufacturer:Phoenix Heavy Industries,Refit primaryfactory:Ashkum,Various diff --git a/megameklab/data/mechfiles/mechs/Shrapnel/Vol 4/SuburbanMech UM-R90.mtf b/megameklab/data/mechfiles/mechs/Shrapnel/Vol 4/SuburbanMech UM-R90.mtf index 17e3e498d..ae8fa7008 100644 --- a/megameklab/data/mechfiles/mechs/Shrapnel/Vol 4/SuburbanMech UM-R90.mtf +++ b/megameklab/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 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. manufacturer:Phoenix Heavy Industries,Refit primaryfactory:Ashkum,Various diff --git a/megameklab/data/mechfiles/mechs/Shrapnel/Vol 7/Hatchetman HCT-5DT.mtf b/megameklab/data/mechfiles/mechs/Shrapnel/Vol 7/Hatchetman HCT-5DT.mtf index 6b86380c6..4dff33938 100644 --- a/megameklab/data/mechfiles/mechs/Shrapnel/Vol 7/Hatchetman HCT-5DT.mtf +++ b/megameklab/data/mechfiles/mechs/Shrapnel/Vol 7/Hatchetman HCT-5DT.mtf @@ -161,7 +161,7 @@ capabilities:As well as being the first design to carry one, the Hatchetman itse deployment:Unknown -history:s well as being the first design to carry one, the Hatchetman itself was the first totally new 'Mech produced in the Inner Sphere in over a century, and was also the first production 'Mech to use a Full-Head Ejection System. Despite being first manufactured in the Lyran Commonwealth the Hatchetman was actually designed by the enigmatic Dr. B. Banzai of Team Banzai, a mercenary unit associated with the Federated Suns' New Avalon Institute of Science. Thus the 'Mech was also a signal of the growing cooperation between these newly-allied Successor States. in the design's first combat test, when elements of the 4th Proserpina Hussars raided Sevren and were literally cut to pieces by a mostly Hatchetman-equipped battalion of the 26th Lyran Guards which lured the enemy into an industrial park. Where the Hatchetman is at a disadvantage is on open terrain, as its relatively slow speed, light armoring and general frailty leaves it vulnerable to other 'Mechs. Initially the Hatchetman's first production run was limited to garrisoning large Lyran cities, but its early successes inspired further deployments and the 'Mech soon began appearing in the arsenal of the Federated Suns, particularly among the Crucis Lancers and 1st Kathil Uhlans. In the wake of the Fourth Succession War and the formal creation of the Federated Commonwealth, the Hatchetman was selected to become one of the standard designs for the Armed Forces of the Federated Commonwealth. Demand for the 'Mech soon began to outstrip Defiance Industries' ability to supply it, even after tripling output from their Hesperus II factory, and so it contracted Johnston Industries to set up a Hatchetman line on Johnston. The recovery of lost Star League technology eventually allowed for the creation of the HCT-5S in 3049, with additional variants created in years hence. Among the other realms, the Draconis Combine managed to capture a few examples of the Hatchetman and successfully copy most of the design to produce their own following the War of 3039, however the 'Mech proved to be unpopular and the program was canceled. Hoping to salvage the project, Independence Weaponry experimented with the design and eventually created a variant more palatable to Kuritan pilots. Out in the Periphery, the introduction of the Hatchetman caused quite a stir within the Taurian Concordat when a group of mercenaries brought along their old HCT-3Fs upon integrating with the Taurian Defense Forces. Protector of the Realm Thomas Calderon ordered Taurus Territorial Industries to reverse-engineer the design, which they finally succeeded in accomplishing after much delay by 3054, only for production to be halted in 3066 when the Fighting Urukhai destroyed the Taurus Territorial Industries facility. +history:As well as being the first design to carry one, the Hatchetman itself was the first totally new 'Mech produced in the Inner Sphere in over a century, and was also the first production 'Mech to use a Full-Head Ejection System. Despite being first manufactured in the Lyran Commonwealth the Hatchetman was actually designed by the enigmatic Dr. B. Banzai of Team Banzai, a mercenary unit associated with the Federated Suns' New Avalon Institute of Science. Thus the 'Mech was also a signal of the growing cooperation between these newly-allied Successor States. In the design's first combat test, elements of the 4th Proserpina Hussars raided Sevren and were literally cut to pieces by a mostly Hatchetman-equipped battalion of the 26th Lyran Guards which lured the enemy into an industrial park. Where the Hatchetman is at a disadvantage is on open terrain, as its relatively slow speed, light armoring and general frailty leaves it vulnerable to other 'Mechs. Initially the Hatchetman's first production run was limited to garrisoning large Lyran cities, but its early successes inspired further deployments and the 'Mech soon began appearing in the arsenal of the Federated Suns, particularly among the Crucis Lancers and 1st Kathil Uhlans. In the wake of the Fourth Succession War and the formal creation of the Federated Commonwealth, the Hatchetman was selected to become one of the standard designs for the Armed Forces of the Federated Commonwealth. Demand for the 'Mech soon began to outstrip Defiance Industries' ability to supply it, even after tripling output from their Hesperus II factory, and so it contracted Johnston Industries to set up a Hatchetman line on Johnston. The recovery of lost Star League technology eventually allowed for the creation of the HCT-5S in 3049, with additional variants created in years hence. Among the other realms, the Draconis Combine managed to capture a few examples of the Hatchetman and successfully copy most of the design to produce their own following the War of 3039, however the 'Mech proved to be unpopular and the program was canceled. Hoping to salvage the project, Independence Weaponry experimented with the design and eventually created a variant more palatable to Kuritan pilots. Out in the Periphery, the introduction of the Hatchetman caused quite a stir within the Taurian Concordat when a group of mercenaries brought along their old HCT-3Fs upon integrating with the Taurian Defense Forces. Protector of the Realm Thomas Calderon ordered Taurus Territorial Industries to reverse-engineer the design, which they finally succeeded in accomplishing after much delay by 3054, only for production to be halted in 3066 when the Fighting Urukhai destroyed the Taurus Territorial Industries facility. manufacturer:Johnston Industries (Refit) primaryfactory:New Syrtis diff --git a/megameklab/data/mechfiles/mechs/Spotlight On/Hellion Keshik/Awesome C.mtf b/megameklab/data/mechfiles/mechs/Spotlight On/Hellion Keshik/Awesome C.mtf index 13a04d927..27fc60ed2 100644 --- a/megameklab/data/mechfiles/mechs/Spotlight On/Hellion Keshik/Awesome C.mtf +++ b/megameklab/data/mechfiles/mechs/Spotlight On/Hellion Keshik/Awesome C.mtf @@ -153,7 +153,7 @@ CLDoubleHeatSink -Empty- overview:The Awesome was designed in 2665 for the Star League by the Technicron Conglomorate and was based on the aging STR-2C Striker. While not as fast as its forefather, the Awesome is a strong assault 'Mech. -capabilities:The Awesome's abilities are nearly entirely dependent on its particle projection cannons. The AWS can withstand a severe and consistent onslaught from its weaponry thanks to several heat sinks. With one and a half tons more armor than the Striker, the AWS is more protected than even the BattleMaster. The Amazing, like any other BattleMech, has weaknesses. While it is lethal at range, it is less effective in close-quarters combat since its PPCs have a tougher time connecting with the victim. In that case, it just possesses a light weapon and a left fist to fall back on. Because of its limited mobility, it is vulnerable to flanking attacks from speedier opponents seeking to get past the PPCs. While they face arguably of the heaviest rear armor found on any BattleMech, the Awesome's lack of rear facing armaments or a weapon mount on its left arm has offered numerous MechWarriors a fighting chance. Formations of Awesomes (or even just a few) are incredibly effective and tough to stop or defeat when correctly placed by commanders who are knowledgeable of the AWS's limitations. +capabilities:The Awesome's abilities are nearly entirely dependent on its particle projection cannons. The AWS can withstand a severe and consistent onslaught from its weaponry thanks to several heat sinks. With one and a half tons more armor than the Striker, the AWS is more protected than even the BattleMaster. The Awesome, like any other BattleMech, has weaknesses. While it is lethal at range, it is less effective in close-quarters combat since its PPCs have a tougher time connecting with the victim. In that case, it just possesses a light weapon and a left fist to fall back on. Because of its limited mobility, it is vulnerable to flanking attacks from speedier opponents seeking to get past the PPCs. While they face arguably of the heaviest rear armor found on any BattleMech, the Awesome's lack of rear facing armaments or a weapon mount on its left arm has offered numerous MechWarriors a fighting chance. Formations of Awesomes (or even just a few) are incredibly effective and tough to stop or defeat when correctly placed by commanders who are knowledgeable of the AWS's limitations. deployment:Developed and manufactured by the Scorpion Empire, this variant uses mostly Clan technology and was introduced in 3143. By replacing the internal structure with Endo-Composite Structure and removing the small laser, this variant of the Awesome frees up the necessary tonnage but keeps enough critical space to mount four ER PPCs, one in each arm and side torso, 27 double heat sinks and 15.5 tons of armor. history:Awesomes can be found in every military House. Because the Free Worlds League has the last remaining manufacturing factories capable of generating the Awesome, it also has the most Awesomes of any of the Great Houses. Opinions on the 'Mech vary greatly within the League. Many people laud its powers, while others believe that its limited mobility is too high a price to pay for what it can do. Similar sentiments exist in the other Houses, but none of them can debate the issue beyond academics. Few commanders would turn down the opportunity to acquire an Awesome for their army. The Awesome is typically used to assault a fixed position or to breach the enemy's line of defense. They are also in demand for defensive operations. MechWarriors piloting the Awesome can expect to be involved in heavy battle and to be charged with obtaining or guarding the most crucial objectives from the adversary. manufacturer:Field Refit diff --git a/megameklab/data/mechfiles/mechs/Spotlight On/Unending Faith/Mad Cat (Timber Wolf) BLO.mtf b/megameklab/data/mechfiles/mechs/Spotlight On/Unending Faith/Mad Cat (Timber Wolf) BLO.mtf index cd1f94145..3a65dc76f 100644 --- a/megameklab/data/mechfiles/mechs/Spotlight On/Unending Faith/Mad Cat (Timber Wolf) BLO.mtf +++ b/megameklab/data/mechfiles/mechs/Spotlight On/Unending Faith/Mad Cat (Timber Wolf) BLO.mtf @@ -161,7 +161,7 @@ overview:The Timber Wolf is a fast, heavy OmniMech. A signature design of the Cl capabilities:A custom configuration used by the Blessed Order's revived First Division's Unending Faith III, the Mad Cat BLO carries a ER PPC in each arm supported by Streak SRM-6 rack in each side torso and a ER Small Laser in the center torso. Carrying two tons of Streak reloads, its combat effectiveness is enhanced by TAG in the right torso and a Light Active Probe and Inner Sphere Improved C3 Computer mounted in left torso. -deployment:First introduced in 2945, the Timber Wolf was designed by Clan Wolf as a second generation OmniMech along with the Gargoyle and the Naga to replace the aging Woodsman. While the Gargoyle may have been a very capable, fast assault OmniMech, and the Naga may have been an excellent fire-support OmniMech, Clan Wolf (and indeed every other Clan) instantly realized the value of the Timber Wolf; thus, production rights to the Timber Wolf were jealously (and successfully) defended. Only through trade, gifts and battlefield salvage has the Timber Wolf entered the armies of other Clans. Until the invasion of the Inner Sphere, production of the Timber Wolf has been limited to a single facility on Strana Mechty. Despite it's prominence among the Wolves during the Clan Invasion, Refusal War and Word of Blake Jihad, the Timber Wolf became increasingly rare following the sundering of ties with the Homeworld Clans during the Wars of Reaving and Blakist scouring of Tamar. Being built by hand at W-7 plant on Weingarten as of 3080, with some parts even being individually machined due to missing data,[1] attrition vastly outstripped supply as the Wolves looked toward other designs. When Alaric Ward forged the Wolf Empire, he left the W-7 facilities to Clan Hell's Horses and ordered the Kallon plant on Thermopolis be retooled for Timber Wolf production, restoring it's position within the Wolves touman. +deployment:First introduced in 2945, the Timber Wolf was designed by Clan Wolf as a second generation OmniMech along with the Gargoyle and the Naga to replace the aging Woodsman. While the Gargoyle may have been a very capable, fast assault OmniMech, and the Naga may have been an excellent fire-support OmniMech, Clan Wolf (and indeed every other Clan) instantly realized the value of the Timber Wolf; thus, production rights to the Timber Wolf were jealously (and successfully) defended. Only through trade, gifts and battlefield salvage has the Timber Wolf entered the armies of other Clans. Until the invasion of the Inner Sphere, production of the Timber Wolf has been limited to a single facility on Strana Mechty. Despite it's prominence among the Wolves during the Clan Invasion, Refusal War and Word of Blake Jihad, the Timber Wolf became increasingly rare following the sundering of ties with the Homeworld Clans during the Wars of Reaving and Blakist scouring of Tamar. Being built by hand at W-7 plant on Weingarten as of 3080, with some parts even being individually machined due to missing data, attrition vastly outstripped supply as the Wolves looked toward other designs. When Alaric Ward forged the Wolf Empire, he left the W-7 facilities to Clan Hell's Horses and ordered the Kallon plant on Thermopolis be retooled for Timber Wolf production, restoring it's position within the Wolves touman. history:Vaguely resembling a cross-over between the MAD (Marauder) and CAT (Catapult) series, the Timber Wolf was tagged with the Inner Sphere reporting name Mad Cat on first contact. (The targeting computer on Phelan Kell's Wolfhound switched between MAD and CAT when trying to identify it; upon analyzing the data recording from Kell's 'Mech, Precentor Martial Anastasius Focht later officially designated it "Mad Cat". diff --git a/megameklab/data/mechfiles/mechs/Starterbook Sword and Dragon/Black Knight BL-6-KNT Ian.mtf b/megameklab/data/mechfiles/mechs/Starterbook Sword and Dragon/Black Knight BL-6-KNT Ian.mtf index b6cf5d30f..f8d478ffc 100644 --- a/megameklab/data/mechfiles/mechs/Starterbook Sword and Dragon/Black Knight BL-6-KNT Ian.mtf +++ b/megameklab/data/mechfiles/mechs/Starterbook Sword and Dragon/Black Knight BL-6-KNT Ian.mtf @@ -159,7 +159,7 @@ Ferro-Fibrous Prototype 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 of them 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 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:Downgraded during the technological decline of the Succession Wars era, the personal 'Mech of the McKinnon family was selected to receive among the first experimental weapons developed from the Helm Memory Core by the New Avalon Institute of Science, thanks to the exploits of Fox's Teeth commander Ian McKinnon. When piloted by Ian during the War of 3039, the 'Mech was clad in prototype ferro-fibrous armor and the standard heat sinks outside the engine were replaced with corrosive 3039-era double heat sinks. These weight savings, along with the removal of the head-mounted small laser, allowed the 'Mech to carry a Hatchet whose damage was boosted by the addition of Triple Strength Myomer. diff --git a/megameklab/data/mechfiles/mechs/Starterbook Sword and Dragon/Hatchetman HCT-3F Austin.mtf b/megameklab/data/mechfiles/mechs/Starterbook Sword and Dragon/Hatchetman HCT-3F Austin.mtf index e24ff39d0..18849afd5 100644 --- a/megameklab/data/mechfiles/mechs/Starterbook Sword and Dragon/Hatchetman HCT-3F Austin.mtf +++ b/megameklab/data/mechfiles/mechs/Starterbook Sword and Dragon/Hatchetman HCT-3F Austin.mtf @@ -162,7 +162,7 @@ capabilities:As well as being the first design to carry one, the Hatchetman itse deployment:Originally assigned to the NAIS Training Cadres, it was selected as a NAIS technology test bed before being assigned to Fox's Teeth member Austin Vorster in the lead-up to the War of 3039. Mounting a NAIS Mk. 1 LB 10-X Autocannon prototype saved enough weight to add a third medium laser, moving all three to the left arm to avoid inhibiting use of the 'Mech's hatchet. -history:s well as being the first design to carry one, the Hatchetman itself was the first totally new 'Mech produced in the Inner Sphere in over a century, and was also the first production 'Mech to use a Full-Head Ejection System. Despite being first manufactured in the Lyran Commonwealth the Hatchetman was actually designed by the enigmatic Dr. B. Banzai of Team Banzai, a mercenary unit associated with the Federated Suns' New Avalon Institute of Science. Thus the 'Mech was also a signal of the growing cooperation between these newly-allied Successor States. in the design's first combat test, when elements of the 4th Proserpina Hussars raided Sevren and were literally cut to pieces by a mostly Hatchetman-equipped battalion of the 26th Lyran Guards which lured the enemy into an industrial park. Where the Hatchetman is at a disadvantage is on open terrain, as its relatively slow speed, light armoring and general frailty leaves it vulnerable to other 'Mechs. Initially the Hatchetman's first production run was limited to garrisoning large Lyran cities, but its early successes inspired further deployments and the 'Mech soon began appearing in the arsenal of the Federated Suns, particularly among the Crucis Lancers and 1st Kathil Uhlans. In the wake of the Fourth Succession War and the formal creation of the Federated Commonwealth, the Hatchetman was selected to become one of the standard designs for the Armed Forces of the Federated Commonwealth. Demand for the 'Mech soon began to outstrip Defiance Industries' ability to supply it, even after tripling output from their Hesperus II factory, and so it contracted Johnston Industries to set up a Hatchetman line on Johnston. The recovery of lost Star League technology eventually allowed for the creation of the HCT-5S in 3049, with additional variants created in years hence. Among the other realms, the Draconis Combine managed to capture a few examples of the Hatchetman and successfully copy most of the design to produce their own following the War of 3039, however the 'Mech proved to be unpopular and the program was canceled. Hoping to salvage the project, Independence Weaponry experimented with the design and eventually created a variant more palatable to Kuritan pilots. Out in the Periphery, the introduction of the Hatchetman caused quite a stir within the Taurian Concordat when a group of mercenaries brought along their old HCT-3Fs upon integrating with the Taurian Defense Forces. Protector of the Realm Thomas Calderon ordered Taurus Territorial Industries to reverse-engineer the design, which they finally succeeded in accomplishing after much delay by 3054, only for production to be halted in 3066 when the Fighting Urukhai destroyed the Taurus Territorial Industries facility. +history:As well as being the first design to carry one, the Hatchetman itself was the first totally new 'Mech produced in the Inner Sphere in over a century, and was also the first production 'Mech to use a Full-Head Ejection System. Despite being first manufactured in the Lyran Commonwealth the Hatchetman was actually designed by the enigmatic Dr. B. Banzai of Team Banzai, a mercenary unit associated with the Federated Suns' New Avalon Institute of Science. Thus the 'Mech was also a signal of the growing cooperation between these newly-allied Successor States. In the design's first combat test, elements of the 4th Proserpina Hussars raided Sevren and were literally cut to pieces by a mostly Hatchetman-equipped battalion of the 26th Lyran Guards which lured the enemy into an industrial park. Where the Hatchetman is at a disadvantage is on open terrain, as its relatively slow speed, light armoring and general frailty leaves it vulnerable to other 'Mechs. Initially the Hatchetman's first production run was limited to garrisoning large Lyran cities, but its early successes inspired further deployments and the 'Mech soon began appearing in the arsenal of the Federated Suns, particularly among the Crucis Lancers and 1st Kathil Uhlans. In the wake of the Fourth Succession War and the formal creation of the Federated Commonwealth, the Hatchetman was selected to become one of the standard designs for the Armed Forces of the Federated Commonwealth. Demand for the 'Mech soon began to outstrip Defiance Industries' ability to supply it, even after tripling output from their Hesperus II factory, and so it contracted Johnston Industries to set up a Hatchetman line on Johnston. The recovery of lost Star League technology eventually allowed for the creation of the HCT-5S in 3049, with additional variants created in years hence. Among the other realms, the Draconis Combine managed to capture a few examples of the Hatchetman and successfully copy most of the design to produce their own following the War of 3039, however the 'Mech proved to be unpopular and the program was canceled. Hoping to salvage the project, Independence Weaponry experimented with the design and eventually created a variant more palatable to Kuritan pilots. Out in the Periphery, the introduction of the Hatchetman caused quite a stir within the Taurian Concordat when a group of mercenaries brought along their old HCT-3Fs upon integrating with the Taurian Defense Forces. Protector of the Realm Thomas Calderon ordered Taurus Territorial Industries to reverse-engineer the design, which they finally succeeded in accomplishing after much delay by 3054, only for production to be halted in 3066 when the Fighting Urukhai destroyed the Taurus Territorial Industries facility. manufacturer:Field Refit primaryfactory:Field Refit diff --git a/megameklab/data/mechfiles/mechs/Starterpack Sword and Dragon/Black Knight BL-10-KNT Ross.mtf b/megameklab/data/mechfiles/mechs/Starterpack Sword and Dragon/Black Knight BL-10-KNT Ross.mtf index 95b029879..898f38307 100644 --- a/megameklab/data/mechfiles/mechs/Starterpack Sword and Dragon/Black Knight BL-10-KNT Ross.mtf +++ b/megameklab/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 of them 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 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: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/megameklab/data/mechfiles/mechs/Starterpack Sword and Dragon/Hatchetman HCT-5S Austin.mtf b/megameklab/data/mechfiles/mechs/Starterpack Sword and Dragon/Hatchetman HCT-5S Austin.mtf index a1b179898..48b241ec9 100644 --- a/megameklab/data/mechfiles/mechs/Starterpack Sword and Dragon/Hatchetman HCT-5S Austin.mtf +++ b/megameklab/data/mechfiles/mechs/Starterpack Sword and Dragon/Hatchetman HCT-5S Austin.mtf @@ -162,7 +162,7 @@ capabilities:As well as being the first design to carry one, the Hatchetman itse deployment:Receiving a 3050s era 5S model after the Fox's Teeth faced Clan Jade Falcon on Wotan in 3051, Austin Vorster had it refitted in the lead-up to the FedCom Civil War. Almost identical to the 6S created by the Lyran Alliance in the conflict, the only significant difference is the placement of all ER Medium Lasers in the 'Mech's left arm. -history:s well as being the first design to carry one, the Hatchetman itself was the first totally new 'Mech produced in the Inner Sphere in over a century, and was also the first production 'Mech to use a Full-Head Ejection System. Despite being first manufactured in the Lyran Commonwealth the Hatchetman was actually designed by the enigmatic Dr. B. Banzai of Team Banzai, a mercenary unit associated with the Federated Suns' New Avalon Institute of Science. Thus the 'Mech was also a signal of the growing cooperation between these newly-allied Successor States. in the design's first combat test, when elements of the 4th Proserpina Hussars raided Sevren and were literally cut to pieces by a mostly Hatchetman-equipped battalion of the 26th Lyran Guards which lured the enemy into an industrial park. Where the Hatchetman is at a disadvantage is on open terrain, as its relatively slow speed, light armoring and general frailty leaves it vulnerable to other 'Mechs. Initially the Hatchetman's first production run was limited to garrisoning large Lyran cities, but its early successes inspired further deployments and the 'Mech soon began appearing in the arsenal of the Federated Suns, particularly among the Crucis Lancers and 1st Kathil Uhlans. In the wake of the Fourth Succession War and the formal creation of the Federated Commonwealth, the Hatchetman was selected to become one of the standard designs for the Armed Forces of the Federated Commonwealth. Demand for the 'Mech soon began to outstrip Defiance Industries' ability to supply it, even after tripling output from their Hesperus II factory, and so it contracted Johnston Industries to set up a Hatchetman line on Johnston. The recovery of lost Star League technology eventually allowed for the creation of the HCT-5S in 3049, with additional variants created in years hence. Among the other realms, the Draconis Combine managed to capture a few examples of the Hatchetman and successfully copy most of the design to produce their own following the War of 3039, however the 'Mech proved to be unpopular and the program was canceled. Hoping to salvage the project, Independence Weaponry experimented with the design and eventually created a variant more palatable to Kuritan pilots. Out in the Periphery, the introduction of the Hatchetman caused quite a stir within the Taurian Concordat when a group of mercenaries brought along their old HCT-3Fs upon integrating with the Taurian Defense Forces. Protector of the Realm Thomas Calderon ordered Taurus Territorial Industries to reverse-engineer the design, which they finally succeeded in accomplishing after much delay by 3054, only for production to be halted in 3066 when the Fighting Urukhai destroyed the Taurus Territorial Industries facility. +history:As well as being the first design to carry one, the Hatchetman itself was the first totally new 'Mech produced in the Inner Sphere in over a century, and was also the first production 'Mech to use a Full-Head Ejection System. Despite being first manufactured in the Lyran Commonwealth the Hatchetman was actually designed by the enigmatic Dr. B. Banzai of Team Banzai, a mercenary unit associated with the Federated Suns' New Avalon Institute of Science. Thus the 'Mech was also a signal of the growing cooperation between these newly-allied Successor States. In the design's first combat test, elements of the 4th Proserpina Hussars raided Sevren and were literally cut to pieces by a mostly Hatchetman-equipped battalion of the 26th Lyran Guards which lured the enemy into an industrial park. Where the Hatchetman is at a disadvantage is on open terrain, as its relatively slow speed, light armoring and general frailty leaves it vulnerable to other 'Mechs. Initially the Hatchetman's first production run was limited to garrisoning large Lyran cities, but its early successes inspired further deployments and the 'Mech soon began appearing in the arsenal of the Federated Suns, particularly among the Crucis Lancers and 1st Kathil Uhlans. In the wake of the Fourth Succession War and the formal creation of the Federated Commonwealth, the Hatchetman was selected to become one of the standard designs for the Armed Forces of the Federated Commonwealth. Demand for the 'Mech soon began to outstrip Defiance Industries' ability to supply it, even after tripling output from their Hesperus II factory, and so it contracted Johnston Industries to set up a Hatchetman line on Johnston. The recovery of lost Star League technology eventually allowed for the creation of the HCT-5S in 3049, with additional variants created in years hence. Among the other realms, the Draconis Combine managed to capture a few examples of the Hatchetman and successfully copy most of the design to produce their own following the War of 3039, however the 'Mech proved to be unpopular and the program was canceled. Hoping to salvage the project, Independence Weaponry experimented with the design and eventually created a variant more palatable to Kuritan pilots. Out in the Periphery, the introduction of the Hatchetman caused quite a stir within the Taurian Concordat when a group of mercenaries brought along their old HCT-3Fs upon integrating with the Taurian Defense Forces. Protector of the Realm Thomas Calderon ordered Taurus Territorial Industries to reverse-engineer the design, which they finally succeeded in accomplishing after much delay by 3054, only for production to be halted in 3066 when the Fighting Urukhai destroyed the Taurus Territorial Industries facility. manufacturer:Field Refit primaryfactory:Field Refit diff --git a/megameklab/data/mechfiles/mechs/Starterpack Sword and Dragon/Jenner JR7-K Grace II.mtf b/megameklab/data/mechfiles/mechs/Starterpack Sword and Dragon/Jenner JR7-K Grace II.mtf index d8d0911e4..e66d75cd6 100644 --- a/megameklab/data/mechfiles/mechs/Starterpack Sword and Dragon/Jenner JR7-K Grace II.mtf +++ b/megameklab/data/mechfiles/mechs/Starterpack Sword and Dragon/Jenner JR7-K Grace II.mtf @@ -159,7 +159,7 @@ capabilities:Five Smithson Lifter jump jets, two in each side torso and one in t deployment:Refitted prior to the Jihad, the prototype chassis and armor of Grace's Jenner were swapped for now refined production grade components. While retaining the Narc Missile Beacon, dropping its ammo to a single ton along with the removal of her 'Mech's jump jets allowed it to replace the two Medium Lasers with a pair of Light PPCs and add a C3 Slave Unit to enhance her spotter role. -history:The Jenner became the standard light warhorse of the DCMS with the outbreak of the First Succession War, though its reputation would be forever tarnished following its role in the Kentares Massacre. The Jenner became the standard light warhorse of the DCMS with the outbreak of the First Succession War, though its reputation would be forever tarnished following its role in the Kentares Massacre. Construction of new Jenners continued at Diplan MechYard's factory on Ozawa until a raw mineral shortage caused a halt in 2815, though they continued to produce new chassis. In 2823 production resumed on Ozawa, with some three thousand chassis shipped to Diplan's subsidiary on Luthien for final assembly, which itself was retooling to begin full-scale production; by 2830 both production lines were producing 1,350 Jenners a year. The sheer destruction of the Succession Wars finally took their toll when the last Jenner factory was destroyed in 2848, though so many Jenners had been produced by then that nearly every DCMS battalion had at least one of these 'Mechs well into the War of 3039. While the other Successor States eventually managed to procure operational Jenners (every AFFS regiment along the Combine border had at least one), the design remained in predominant use by House Kurita. +history:Construction of new Jenners continued at Diplan MechYard's factory on Ozawa until a raw mineral shortage caused a halt in 2815, though they continued to produce new chassis. In 2823 production resumed on Ozawa, with some three thousand chassis shipped to Diplan's subsidiary on Luthien for final assembly, which itself was retooling to begin full-scale production; by 2830 both production lines were producing 1,350 Jenners a year. The sheer destruction of the Succession Wars finally took their toll when the last Jenner factory was destroyed in 2848, though so many Jenners had been produced by then that nearly every DCMS battalion had at least one of these 'Mechs well into the War of 3039. While the other Successor States eventually managed to procure operational Jenners (every AFFS regiment along the Combine border had at least one), the design remained in predominant use by House Kurita. manufacturer:Luthien Armor Works, Diplan 'Mechyards, Luthien Armor Works, Luthien Armor Works, Diplan 'Mechyards primaryfactory:Luthien, Abiy Adi, New Samarkand, Ozawa diff --git a/megameklab/data/mechfiles/mechs/TRO Irregulars/Opossum OPO-3 SalvageMech MOD.mtf b/megameklab/data/mechfiles/mechs/TRO Irregulars/Opossum OPO-3 SalvageMech MOD.mtf index cc4b1da44..ed35d3862 100644 --- a/megameklab/data/mechfiles/mechs/TRO Irregulars/Opossum OPO-3 SalvageMech MOD.mtf +++ b/megameklab/data/mechfiles/mechs/TRO Irregulars/Opossum OPO-3 SalvageMech MOD.mtf @@ -150,7 +150,7 @@ overview:DiNapoli Industries may be remembered for their licensed production of capabilities:The Opossum SalvageMech is rarely modded—Bannson’s focus on paramilitary DiNapoli equipment has largely been aimed at the Demeter. It was actually a mercenary command who came up with a standardized modification to mate the Opossum’s high-grade armor and electronics with a ballistic weapon by removing the right arm assembly. Though the addition of the light autocannon limits this SalvageMech’s ability to grab, drag, and repair damaged ’Mechs in the field, the capability for self-defense is valued by mercenaries and splinter factions which do not possess the assets to field purely non-combatant units, let alone the resources to protect them. -deployment:Though it debuted in several small actions during 3131, the Twenty-first Centauri Lancers’ MOD of the Opossum didn’t really attract much public attention until May 3132, when the Lancers deployed Rasbid’s light support lance to Ventabren to assist in a joint Oriente-Republic salvage operation of a Golden Dawn-era battlefield. Captain Chak Rasbid had lobbied heavily for the assignment when it became available, touting the proven record for both salvage retrieval and combat effectiveness displayed by lance tech Jon Roberson in the previous year’s actions as a prime advantage for his command. Roberson justified his captain’s faith when, two weeks into the assignment, the salvage site was attacked by assailants in unmarked vehicles and battle armor. Once again, Roberson proved the value of a combat-capable SalvageMech when he used his ’Mech’s autocannon to defend himself against several attackers while in the middle of a delicate extraction operation on a BattleMech with a damaged fusion reactor. His coolness under fire, as well as the capabilities of his MODded ’Mech, impressed both the Oriente and RAF on-site officials and he enjoyed a day or two as a local news item on Ventabren and nearby worlds. The successful completion of this mission and in particular the performance of Roberson’s unique MOD under such conditions convinced Lancer Colonel Richard Haskell to implement similar modifications to a significant proportion of the unit’s Opossums. +deployment:Though it debuted in several small actions during 3131, the Twenty-first Centauri Lancers’ MOD of the Opossum didn't really attract much public attention until May 3132, when the Lancers deployed Rasbid’s light support lance to Ventabren to assist in a joint Oriente-Republic salvage operation of a Golden Dawn-era battlefield. Captain Chak Rasbid had lobbied heavily for the assignment when it became available, touting the proven record for both salvage retrieval and combat effectiveness displayed by lance tech Jon Roberson in the previous year’s actions as a prime advantage for his command. Roberson justified his captain’s faith when, two weeks into the assignment, the salvage site was attacked by assailants in unmarked vehicles and battle armor. Once again, Roberson proved the value of a combat-capable SalvageMech when he used his ’Mech’s autocannon to defend himself against several attackers while in the middle of a delicate extraction operation on a BattleMech with a damaged fusion reactor. His coolness under fire, as well as the capabilities of his MODded ’Mech, impressed both the Oriente and RAF on-site officials and he enjoyed a day or two as a local news item on Ventabren and nearby worlds. The successful completion of this mission and in particular the performance of Roberson’s unique MOD under such conditions convinced Lancer Colonel Richard Haskell to implement similar modifications to a significant proportion of the unit’s Opossums. manufacturer:DiNapoli Industries primaryfactory:Ankaa diff --git a/megameklab/data/mechfiles/mechs/TRO Irregulars/St. Florian FLN-366 FireMech.mtf b/megameklab/data/mechfiles/mechs/TRO Irregulars/St. Florian FLN-366 FireMech.mtf index ff651fd4f..c575d4752 100644 --- a/megameklab/data/mechfiles/mechs/TRO Irregulars/St. Florian FLN-366 FireMech.mtf +++ b/megameklab/data/mechfiles/mechs/TRO Irregulars/St. Florian FLN-366 FireMech.mtf @@ -154,7 +154,7 @@ Environmental Sealing -Empty- -Empty- -overview:The St. Florian MOD, recently seen with the Stormhammers on Towne, is an imposing sight, towering as large as an assault BattleMech while still fielding the firepower of a heavy one. The secret to its abilities lies in its pedigree, as many of the FireMech’s components have been adapted from one of the Inner Sphere’s most famous assault ’Mechs: the Highlander. Initially a byproduct to utilize surplus single heat sink-equipped standard fusion engines after the Highlander production line was upgraded to the HGN-734 in 3062, the St. Florian quickly gained fame as the most advanced IndustrialMech introduced since the fall of the Star League. It became a bestseller amongst those parties which could afford it—and more often than not are now scrambling to equip it with weaponry. +overview:The St. Florian MOD, recently seen with the Stormhammers on Towne, is an imposing sight, towering as large as an assault BattleMech while still fielding the firepower of a heavy one. The secret to its abilities lies in its pedigree, as many of the FireMech’s components have been adapted from one of the Inner Sphere’s most famous assault ’Mechs: the Highlander. Initially a byproduct to utilize surplus single heat sink-equipped standard fusion engines after the Highlander production line was upgraded to the HGN-734 in 3062, the St. Florian quickly gained fame as the most advanced IndustrialMech introduced since the fall of the Star League. It became a bestseller amongst those parties which could afford it—and more often than not are now scrambling to equip it with weaponry. capabilities:Cynical minds fear that Star Corps themselves may be behind a military modification of the St. Florian, but closer examination of this MOD suggests little evidence to support any such theories. While it carries advanced plasma rifles, there is no structural upgrade to the FireMech whatsoever. The environmental sealing and bank of heat sinks are core components of the standard St. Florian which allow it to wade into the thick of fires instead of combating them from the outside as slighter units like the Pompier are forced to. Turning a firefighter into an incendiary combatant makes a certain amount of sense, but a lack of additional heat sinks and reliance on volatile coolant pods definitely betrays this otherwise impressive MOD as a field modification in the truest sense. deployment:While the St. Florian’s capabilities mark it as a much-desired part of any community’s public services apparatus, its cost is unfortunately prohibitive for most small to medium-sized towns. Even the Republic, with its prosperity driven by Devlin Stone’s reforms, has had difficulty in procuring large quantities of this FireMech. As a consequence, the majority of the St. Florians in service are to be found in planetary capitals and major metropolises across the Inner Sphere, while smaller settlements must make do with the Pompier or even forego specialized fire-fighting ’Mechs. However, the long service record of the St. Florian has led to a significant secondary market where used or slightly damaged examples are perennial bestsellers. Though the current scramble to militarize common IndustrialMechs has not passed the St. Florian by, the crucial role it plays in protecting the homes and businesses of the cities where it has been deployed means that a comparatively smaller percentage of these ’Mechs have been modded for combat usage. Within the Republic, such conversions seem oddly common on those worlds that have recently come under control of one of the Clan-based splinter factions. The very idea of piloting converted Industrials into combat is anathema to most Clanners but the fact that several of these factions have begun accepting Spheroid applicants is perhaps all the explanation necessary. diff --git a/megameklab/data/mechfiles/mechs/TRO Irregulars/St. Florian FLN-366-M FireMech MOD.mtf b/megameklab/data/mechfiles/mechs/TRO Irregulars/St. Florian FLN-366-M FireMech MOD.mtf index bebb7719a..3712cd2b2 100644 --- a/megameklab/data/mechfiles/mechs/TRO Irregulars/St. Florian FLN-366-M FireMech MOD.mtf +++ b/megameklab/data/mechfiles/mechs/TRO Irregulars/St. Florian FLN-366-M FireMech MOD.mtf @@ -152,7 +152,7 @@ Environmental Sealing -Empty- -Empty- -overview:The St. Florian MOD, recently seen with the Stormhammers on Towne, is an imposing sight, towering as large as an assault BattleMech while still fielding the firepower of a heavy one. The secret to its abilities lies in its pedigree, as many of the FireMech’s components have been adapted from one of the Inner Sphere’s most famous assault ’Mechs: the Highlander. Initially a byproduct to utilize surplus single heat sink-equipped standard fusion engines after the Highlander production line was upgraded to the HGN-734 in 3062, the St. Florian quickly gained fame as the most advanced IndustrialMech introduced since the fall of the Star League. It became a bestseller amongst those parties which could afford it—and more often than not are now scrambling to equip it with weaponry. +overview:The St. Florian MOD, recently seen with the Stormhammers on Towne, is an imposing sight, towering as large as an assault BattleMech while still fielding the firepower of a heavy one. The secret to its abilities lies in its pedigree, as many of the FireMech’s components have been adapted from one of the Inner Sphere’s most famous assault ’Mechs: the Highlander. Initially a byproduct to utilize surplus single heat sink-equipped standard fusion engines after the Highlander production line was upgraded to the HGN-734 in 3062, the St. Florian quickly gained fame as the most advanced IndustrialMech introduced since the fall of the Star League. It became a bestseller amongst those parties which could afford it—and more often than not are now scrambling to equip it with weaponry. capabilities:Cynical minds fear that Star Corps themselves may be behind a military modification of the St. Florian, but closer examination of this MOD suggests little evidence to support any such theories. While it carries advanced plasma rifles, there is no structural upgrade to the FireMech whatsoever. The environmental sealing and bank of heat sinks are core components of the standard St. Florian which allow it to wade into the thick of fires instead of combating them from the outside as slighter units like the Pompier are forced to. Turning a firefighter into an incendiary combatant makes a certain amount of sense, but a lack of additional heat sinks and reliance on volatile coolant pods definitely betrays this otherwise impressive MOD as a field modification in the truest sense. deployment:While the St. Florian’s capabilities mark it as a much-desired part of any community’s public services apparatus, its cost is unfortunately prohibitive for most small to medium-sized towns. Even the Republic, with its prosperity driven by Devlin Stone’s reforms, has had difficulty in procuring large quantities of this FireMech. As a consequence, the majority of the St. Florians in service are to be found in planetary capitals and major metropolises across the Inner Sphere, while smaller settlements must make do with the Pompier or even forego specialized fire-fighting ’Mechs. However, the long service record of the St. Florian has led to a significant secondary market where used or slightly damaged examples are perennial bestsellers. Though the current scramble to militarize common IndustrialMechs has not passed the St. Florian by, the crucial role it plays in protecting the homes and businesses of the cities where it has been deployed means that a comparatively smaller percentage of these ’Mechs have been modded for combat usage. Within the Republic, such conversions seem oddly common on those worlds that have recently come under control of one of the Clan-based splinter factions. The very idea of piloting converted Industrials into combat is anathema to most Clanners but the fact that several of these factions have begun accepting Spheroid applicants is perhaps all the explanation necessary. manufacturer:StarCorps Industries diff --git a/megameklab/data/mechfiles/mechs/Total Chaos/Awesome AWS-10KM (Cameron).mtf b/megameklab/data/mechfiles/mechs/Total Chaos/Awesome AWS-10KM (Cameron).mtf index eb2cf3990..3350cc7e9 100644 --- a/megameklab/data/mechfiles/mechs/Total Chaos/Awesome AWS-10KM (Cameron).mtf +++ b/megameklab/data/mechfiles/mechs/Total Chaos/Awesome AWS-10KM (Cameron).mtf @@ -158,7 +158,7 @@ IS Endo Steel overview:The Awesome was designed in 2665 for the Star League by the Technicron Conglomorate and was based on the aging STR-2C Striker. While not as fast as its forefather, the Awesome is a strong assault 'Mech. -capabilities:The Awesome's abilities are nearly entirely dependent on its particle projection cannons. The AWS can withstand a severe and consistent onslaught from its weaponry thanks to several heat sinks. With one and a half tons more armor than the Striker, the AWS is more protected than even the BattleMaster. The Amazing, like any other BattleMech, has weaknesses. While it is lethal at range, it is less effective in close-quarters combat since its PPCs have a tougher time connecting with the victim. In that case, it just possesses a light weapon and a left fist to fall back on. Because of its limited mobility, it is vulnerable to flanking attacks from speedier opponents seeking to get past the PPCs. While they face arguably of the heaviest rear armor found on any BattleMech, the Awesome's lack of rear facing armaments or a weapon mount on its left arm has offered numerous MechWarriors a fighting chance. Formations of Awesomes (or even just a few) are incredibly effective and tough to stop or defeat when correctly placed by commanders who are knowledgeable of the AWS's limitations. +capabilities:The Awesome's abilities are nearly entirely dependent on its particle projection cannons. The AWS can withstand a severe and consistent onslaught from its weaponry thanks to several heat sinks. With one and a half tons more armor than the Striker, the AWS is more protected than even the BattleMaster. The Awesome, like any other BattleMech, has weaknesses. While it is lethal at range, it is less effective in close-quarters combat since its PPCs have a tougher time connecting with the victim. In that case, it just possesses a light weapon and a left fist to fall back on. Because of its limited mobility, it is vulnerable to flanking attacks from speedier opponents seeking to get past the PPCs. While they face arguably of the heaviest rear armor found on any BattleMech, the Awesome's lack of rear facing armaments or a weapon mount on its left arm has offered numerous MechWarriors a fighting chance. Formations of Awesomes (or even just a few) are incredibly effective and tough to stop or defeat when correctly placed by commanders who are knowledgeable of the AWS's limitations. deployment:The Awesome used by Cameron St. Jamais for his last stand during Operation SCOUR mixed both Clan and Inner Sphere technology. It replaces the standard Awesome-10KM's Heavy PPCs with two Clan built ER PPCs. It also mounts an Improved C3 computer to share targeting data, and is equipped with an advanced Targeting Computer. A single ER Small Laser has been reinstalled in the head. The heat sinks have been built to Clan specifications. The compact fusion engine has been replaced with a standard fusion engine. The Guardian ECM and Snub Nosed PPC of the standard AWS-10KM remain, but to provide more protection this Awesome uses an Armored Engine, Armored Cockpit, and Armored Gyro. diff --git a/megameklab/data/mechfiles/mechs/Tukayyid/Archer ARC-5CS.mtf b/megameklab/data/mechfiles/mechs/Tukayyid/Archer ARC-5CS.mtf index 639e94419..8568ca933 100644 --- a/megameklab/data/mechfiles/mechs/Tukayyid/Archer ARC-5CS.mtf +++ b/megameklab/data/mechfiles/mechs/Tukayyid/Archer ARC-5CS.mtf @@ -162,7 +162,7 @@ IS Ammo LRM-15 Artemis-capable overview:One of the most iconic BattleMechs is the Archer, with its low-slung torso, enormous fists, and missile-bay covers. The Archer was first manufactured in 2474 for heavy-hitting, long-range brawling, and fire-support. -capabilities:Two enormous missile launchers with tons of ammo power the Archer. The missiles were formidable, but their short-range inaccuracy required four medium lasers, two rear-facing and one in each arm. Enlarged hand actuators allow the design to undertake severe physical attacks and transport captured supplies during raids. The cockpit of the Archer situated beneath the center midsection, giving the pilot a unique battlefield view. The torso armor belt above the cockpit protects the gyro and engine from the superior armor. Many pilots initially entered battle with their missile bays locked to hide the 'Mech's real capabilities, leading some to believe it was a close-combat design. As the Archer became famous, this pretext became meaningless. Archer pilots rarely learn new skills, but this hasn't tarnished the 'Mech's reputation. +capabilities:Two enormous missile launchers with tons of ammo power the Archer. The missiles were formidable, but their short-range inaccuracy required four medium lasers, two rear-facing and one in each arm. Enlarged hand actuators allow the design to undertake severe physical attacks and transport captured supplies during raids. The cockpit of the Archer is situated beneath the center midsection, giving the pilot a unique battlefield view. The torso armor belt above the cockpit protects the gyro and engine from the superior armor. Many pilots initially entered battle with their missile bays locked to hide the 'Mech's real capabilities, leading some to believe it was a close-combat design. As the Archer became famous, this pretext became meaningless. Archer pilots rarely learn new skills, but this hasn't tarnished the 'Mech's reputation. deployment:Developed by ComStar for the Battle of Tukayyid, this Archer variant uses an VOX 280 XL engine and Endo Steel skeleton to free weight, trading durability for enhanced firepower. Protected by eleven and a half tons of armor, it carries two Holly LRM-15s with Artemis IV FCS in each side torso, allowing it to outgun even the venerable Longbow. The arms carry the typical Diverse Optics Type 18 medium laser, and the rear-firing lasers are removed. The biggest drawback is the location of the missile ammunition: Though a ton of ammunition is carried in each side torso, the legs each carry two tons of ammunition. Elementals quickly learned to target the legs to disable the 'Mech. diff --git a/megameklab/data/mechfiles/mechs/Tukayyid/Black Knight BL-9-KNT.mtf b/megameklab/data/mechfiles/mechs/Tukayyid/Black Knight BL-9-KNT.mtf index 9011474d6..f572ea09a 100644 --- a/megameklab/data/mechfiles/mechs/Tukayyid/Black Knight BL-9-KNT.mtf +++ b/megameklab/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 of them 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 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: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/megameklab/data/mechfiles/mechs/Tukayyid/Loki (Hellbringer) M.mtf b/megameklab/data/mechfiles/mechs/Tukayyid/Loki (Hellbringer) M.mtf index 176562c63..686e52c49 100644 --- a/megameklab/data/mechfiles/mechs/Tukayyid/Loki (Hellbringer) M.mtf +++ b/megameklab/data/mechfiles/mechs/Tukayyid/Loki (Hellbringer) M.mtf @@ -157,7 +157,7 @@ Foot Actuator overview:The Hellbringer is a very widespread design developed by Clan Hell's Horses. However, due to its poor armor, the Hellbringer is often passed over for more robust OmniMechs. -history:The Inner Sphere first encountered the Hellbringer facing Clan Jade Falcon, which favors the design for its immense offensive potential. Earning the codename Loki by Galen Cox, an AFFC officer who declared each of the Hellbringer's various versions as an "utterly mad configuration," the 'Mech does at first glance appear to be highly unusual, mounting a spread of weapons, anti-personnel equipment and electronics. The Hellbringer utilizes a standard internal structure, and has decent mobility, with a top speed of 86.4 km/h. Though it has vast firepower at its disposal, the design is not particularly durable, mounting a mere eight tons of Standard armor, and the Hellbringer is not particularly suitable for defensive situations or extended engagements. In the aftermath of the Battle of Tokasha and the loss of Tokasha Mechworks, the Hell's Horses began developing several OmniMechs. Only the Hellbringer met with success. Development time for the Hellbringer was reduced through the use of modules used in the Summoner. Despite the poor armor, the Hellbringer devotes almost 43% of its mass to pods, allowing for great offensive potential. The design spread quickly after its introduction for two reasons: the Horses promptly lost the primary production facility, and used their remaining production to curry favor with other Clans through trade and gifts. After The Wars of Reaving in Clan Space, the Hellbringer would fall out of favor with the surviving Home Clans due in part to its association with the Inner Sphere based Clans. The design would be replaced by the Ebon Jaguar in military service of those in Clan Space, with the exception of Clan Coyote which still fields the 'Mech.[9] Even after the introduction of the updated and upgraded Loki II successor design in 3121, Clan Jade Falcon would continue to produce the cheap and easy to manufacture original version on Sudeten during the Dark Age era, with disgraced, solahma or even just overly aggressive warriors still finding its offense over defense focus desirable. +history:The Inner Sphere first encountered the Hellbringer facing Clan Jade Falcon, which favors the design for its immense offensive potential. Earning the codename Loki by Galen Cox, an AFFC officer who declared each of the Hellbringer's various versions as an "utterly mad configuration," the 'Mech does at first glance appear to be highly unusual, mounting a spread of weapons, anti-personnel equipment and electronics. The Hellbringer utilizes a standard internal structure, and has decent mobility, with a top speed of 86.4 km/h. Though it has vast firepower at its disposal, the design is not particularly durable, mounting a mere eight tons of Standard armor, and the Hellbringer is not particularly suitable for defensive situations or extended engagements. In the aftermath of the Battle of Tokasha and the loss of Tokasha Mechworks, the Hell's Horses began developing several OmniMechs. Only the Hellbringer met with success. Development time for the Hellbringer was reduced through the use of modules used in the Summoner. Despite the poor armor, the Hellbringer devotes almost 43% of its mass to pods, allowing for great offensive potential. The design spread quickly after its introduction for two reasons: the Horses promptly lost the primary production facility, and used their remaining production to curry favor with other Clans through trade and gifts. After The Wars of Reaving in Clan Space, the Hellbringer would fall out of favor with the surviving Home Clans due in part to its association with the Inner Sphere based Clans. The design would be replaced by the Ebon Jaguar in military service of those in Clan Space, with the exception of Clan Coyote which still fields the 'Mech. Even after the introduction of the updated and upgraded Loki II successor design in 3121, Clan Jade Falcon would continue to produce the cheap and easy to manufacture original version on Sudeten during the Dark Age era, with disgraced, solahma or even just overly aggressive warriors still finding its offense over defense focus desirable. manufacturer:Various, Olivetti Weaponry primaryfactory:Various, Sudeten systemmanufacturer:CHASSIS:T-E H65 Standard diff --git a/megameklab/data/mechfiles/mechs/Tukayyid/Mad Cat (Timber Wolf) TC.mtf b/megameklab/data/mechfiles/mechs/Tukayyid/Mad Cat (Timber Wolf) TC.mtf index 16799794f..207a35398 100644 --- a/megameklab/data/mechfiles/mechs/Tukayyid/Mad Cat (Timber Wolf) TC.mtf +++ b/megameklab/data/mechfiles/mechs/Tukayyid/Mad Cat (Timber Wolf) TC.mtf @@ -158,9 +158,9 @@ Clan Endo Steel -Empty- -Empty- -overview:overview:The Timber Wolf is a fast, heavy OmniMech. A signature design of the Clans' military might, it was arguably the first Clan OmniMech encountered by Inner Sphere forces (as opposed to periphery forces) on The Rock in 3049 by Phelan Kell. The Timber Wolf is vastly more powerful than either the Marauder or the Catapult. It uses its speed and firepower to engage an enemy at the range of its choosing. When first encountered by Inner Sphere forces the idea that a heavy 'Mech could move so swiftly while being as heavily armed and armored as the Timber Wolf was inconceivable. With its twelve tons of Ferro-Fibrous armor and arsenal that rivaled that of most assault 'Mechs of the era, it was completely alien to Inner Sphere military planners, commanders, and even the Precentor Martial of ComStar. Its technological secrets have since been reverse-engineered by the Inner Sphere. +overview:The Timber Wolf is a fast, heavy OmniMech. A signature design of the Clans' military might, it was arguably the first Clan OmniMech encountered by Inner Sphere forces (as opposed to periphery forces) on The Rock in 3049 by Phelan Kell. The Timber Wolf is vastly more powerful than either the Marauder or the Catapult. It uses its speed and firepower to engage an enemy at the range of its choosing. When first encountered by Inner Sphere forces the idea that a heavy 'Mech could move so swiftly while being as heavily armed and armored as the Timber Wolf was inconceivable. With its twelve tons of Ferro-Fibrous armor and arsenal that rivaled that of most assault 'Mechs of the era, it was completely alien to Inner Sphere military planners, commanders, and even the Precentor Martial of ComStar. Its technological secrets have since been reverse-engineered by the Inner Sphere. -deployment:First introduced in 2945, the Timber Wolf was designed by Clan Wolf as a second generation OmniMech along with the Gargoyle and the Naga to replace the aging Woodsman. While the Gargoyle may have been a very capable, fast assault OmniMech, and the Naga may have been an excellent fire-support OmniMech, Clan Wolf (and indeed every other Clan) instantly realized the value of the Timber Wolf; thus, production rights to the Timber Wolf were jealously (and successfully) defended. Only through trade, gifts and battlefield salvage has the Timber Wolf entered the armies of other Clans. Until the invasion of the Inner Sphere, production of the Timber Wolf has been limited to a single facility on Strana Mechty. Despite it's prominence among the Wolves during the Clan Invasion, Refusal War and Word of Blake Jihad, the Timber Wolf became increasingly rare following the sundering of ties with the Homeworld Clans during the Wars of Reaving and Blakist scouring of Tamar. Being built by hand at W-7 plant on Weingarten as of 3080, with some parts even being individually machined due to missing data,[1] attrition vastly outstripped supply as the Wolves looked toward other designs. When Alaric Ward forged the Wolf Empire, he left the W-7 facilities to Clan Hell's Horses and ordered the Kallon plant on Thermopolis be retooled for Timber Wolf production, restoring it's position within the Wolves touman. +deployment:First introduced in 2945, the Timber Wolf was designed by Clan Wolf as a second generation OmniMech along with the Gargoyle and the Naga to replace the aging Woodsman. While the Gargoyle may have been a very capable, fast assault OmniMech, and the Naga may have been an excellent fire-support OmniMech, Clan Wolf (and indeed every other Clan) instantly realized the value of the Timber Wolf; thus, production rights to the Timber Wolf were jealously (and successfully) defended. Only through trade, gifts and battlefield salvage has the Timber Wolf entered the armies of other Clans. Until the invasion of the Inner Sphere, production of the Timber Wolf has been limited to a single facility on Strana Mechty. Despite it's prominence among the Wolves during the Clan Invasion, Refusal War and Word of Blake Jihad, the Timber Wolf became increasingly rare following the sundering of ties with the Homeworld Clans during the Wars of Reaving and Blakist scouring of Tamar. Being built by hand at W-7 plant on Weingarten as of 3080, with some parts even being individually machined due to missing data, attrition vastly outstripped supply as the Wolves looked toward other designs. When Alaric Ward forged the Wolf Empire, he left the W-7 facilities to Clan Hell's Horses and ordered the Kallon plant on Thermopolis be retooled for Timber Wolf production, restoring it's position within the Wolves touman. history:Vaguely resembling a cross-over between the MAD (Marauder) and CAT (Catapult) series, the Timber Wolf was tagged with the Inner Sphere reporting name Mad Cat on first contact. (The targeting computer on Phelan Kell's Wolfhound switched between MAD and CAT when trying to identify it; upon analyzing the data recording from Kell's 'Mech, Precentor Martial Anastasius Focht later officially designated it "Mad Cat". diff --git a/megameklab/data/mechfiles/mechs/Tukayyid/Vulture (Mad Dog) S.mtf b/megameklab/data/mechfiles/mechs/Tukayyid/Vulture (Mad Dog) S.mtf index e3ee0be50..65cf926dd 100644 --- a/megameklab/data/mechfiles/mechs/Tukayyid/Vulture (Mad Dog) S.mtf +++ b/megameklab/data/mechfiles/mechs/Tukayyid/Vulture (Mad Dog) S.mtf @@ -157,8 +157,8 @@ Foot Actuator overview:The Mad Dog is a heavy Clan OmniMech used for long-range indirect fire support. With hunched shoulders, a protruding head, and reverse-jointed legs, the Mad Dog resembles a vulture, so much so that it was codenamed Vulture and Hagetaka ("Vulture" in Japanese) by the Inner Sphere forces which first encountered it. -deployment:The name also fit the battlefield role of the Mad Dog; the main role of the Mad Dog is to act as a support 'Mech, and it often holds a hill maintaining constant watch over the entire battlefield, like a vulture waiting for its prey. With its ample firepower and decent speed of 86.4 km/h, it makes a highly mobile firing platform, and as such has spread to near ubiquity among the forces deployed by the Clans, although the design is favored more by Clan Ghost Bear MechWarriors. The Mad Dog carries eight and a half tons of Ferro-Fibrous armor for decent protection, although it will not be able to stand up to heavy fire. -history:The Mad Dog was designed by Clan Smoke Jaguar as a second generation OmniMech based on the original heavy OmniMech Lupus of Clan Coyote.[7] The Mad Dog also used some of the same moulds of the Clan Wolf Timber Wolf OmniMech. However, despite using some of the same moulds (which might be viewed as high praise), the Mad Dog was named as a slur to the Lupus and Timber Wolf, and to Clans Wolf and Coyote. Because of its widespread production, most Clans maintain a large number of Mad Dogs in their toumans. +deployment:The name also fit the battlefield role of the Mad Dog; to act as a support 'Mech, and it often holds a hill maintaining constant watch over the entire battlefield, like a vulture waiting for its prey. With its ample firepower and decent speed of 86.4 km/h, it makes a highly mobile firing platform, and as such has spread to near ubiquity among the forces deployed by the Clans, although the design is favored more by Clan Ghost Bear MechWarriors. The Mad Dog carries eight and a half tons of Ferro-Fibrous armor for decent protection, although it will not be able to stand up to heavy fire. +history:The Mad Dog was designed by Clan Smoke Jaguar as a second generation OmniMech based on the original heavy OmniMech Lupus of Clan Coyote. The Mad Dog also used some of the same moulds of the Clan Wolf Timber Wolf OmniMech. However, despite using some of the same moulds (which might be viewed as high praise), the Mad Dog was named as a slur to the Lupus and Timber Wolf, and to Clans Wolf and Coyote. Because of its widespread production, most Clans maintain a large number of Mad Dogs in their toumans. manufacturer:Various,Svarstaad Industriplex Beta primaryfactory:Various,Svarstaad systemmanufacturer:CHASSIS:Eden Mk 60-OM diff --git a/megameklab/data/mechfiles/mechs/Turning Points/HTP Death to Mercenaries/Annihilator ANH-1E.mtf b/megameklab/data/mechfiles/mechs/Turning Points/HTP Death to Mercenaries/Annihilator ANH-1E.mtf index 9c7e440ec..2ca890fc3 100644 --- a/megameklab/data/mechfiles/mechs/Turning Points/HTP Death to Mercenaries/Annihilator ANH-1E.mtf +++ b/megameklab/data/mechfiles/mechs/Turning Points/HTP Death to Mercenaries/Annihilator ANH-1E.mtf @@ -160,7 +160,7 @@ Heat Sink overview:Originally developed in the final year of the Amaris Civil War as the ultimate fixed position city defense BattleMech. -capabilities:The Annihilator is armed with an arsenal that is built to instill fear in an enemy as much as damage them. The 100-ton 'Mech has a maximum speed of 32.4 km/h, making it one of the slowest 'Mechs ever designed together with the UrbanMech. It is by no means intended to use speed to outmaneuver an enemy, instead depending on its twelve and a half tons of armor to weather any fire that is directed at the 'Mech. +capabilities:The Annihilator is armed with an arsenal that is built to instill fear in an enemy as much as damage them. The 100-ton 'Mech has a maximum speed of 32.4 km/h, making it one of the slowest 'Mechs ever designed together with the UrbanMech. It is by no means intended to use speed to outmaneuver an enemy, instead depending on its twelve and a half tons of armor to weather any fire that is directed at the 'Mech. deployment:This field-expedient refit was used by the Dragoons after the Battle of Misery. All of the autocannons were removed and replaced with four PPCs and two additional Medium Lasers. The ANH-1E also carried forty-one heat sinks, enough to fire the main weapons continually. diff --git a/megameklab/data/mechfiles/mechs/Turning Points/HTP Galtor/Atlas AS7-WGS Samsonov.mtf b/megameklab/data/mechfiles/mechs/Turning Points/HTP Galtor/Atlas AS7-WGS Samsonov.mtf index 286acf422..984562545 100644 --- a/megameklab/data/mechfiles/mechs/Turning Points/HTP Galtor/Atlas AS7-WGS Samsonov.mtf +++ b/megameklab/data/mechfiles/mechs/Turning Points/HTP Galtor/Atlas AS7-WGS Samsonov.mtf @@ -141,7 +141,7 @@ Heat Sink overview:"A 'Mech as powerful as possible, as impenetrable as possible, and as ugly and foreboding as conceivable, so that fear itself will be our ally.”-Aleksandr Kerensky -capabilities:The Atlas is probably the best-known BattleMech to ever set foot on the modern battlefield. Designed with specifications from Aleksandr Kerensky himself in 2755 in the midst of the Cameron Edicts, the Atlas was originally intended to ensure SLDF superiority over the Star League member states. Carrying the largest LRM launcher, the largest autocannon, and the largest SRM launcher possible, the Atlas can deal frightening amounts of damage in short amounts of time. Often used as a command vehicle, the Atlas mounts an advanced antenna and communications array, allowing it to engage in surface-to space communications in real time. The massive 19-ton hide of armor that protects the Atlas makes it a difficult foe to take down. Indeed, most MechWarriors choose to fall back rather than face one head-one, as its lumbering gait mean it can rarely catch up to other 'Mechs that choose to flee it. A full year of development went into crafting the famous "Death's Head" of the 'Mech to achieve the perfect ratio of functionality and fear. The head is also quite roomy and allows a small satellite dish to be mounted for surface-to-space communications. During combat the pilot can easily fold up the dish and store it within a protective portion of the head. +capabilities:The Atlas is probably the best-known BattleMech to ever set foot on the modern battlefield. Designed with specifications from Aleksandr Kerensky himself in 2755 in the midst of the Cameron Edicts, the Atlas was originally intended to ensure SLDF superiority over the Star League member states. Carrying the largest LRM launcher, the largest autocannon, and the largest SRM launcher possible, the Atlas can deal frightening amounts of damage in short amounts of time. Often used as a command vehicle, the Atlas mounts an advanced antenna and communications array, allowing it to engage in surface-to-space communications in real time. The massive 19-ton hide of armor that protects the Atlas makes it a difficult foe to take down. Indeed, most MechWarriors choose to fall back rather than face one head-on, as its lumbering gait means it can rarely catch up to other 'Mechs that choose to flee it. A full year of development went into crafting the famous "Death's Head" of the 'Mech to achieve the perfect ratio of functionality and fear. The head is also quite roomy and allows a small satellite dish to be mounted for surface-to-space communications. During combat the pilot can easily fold up the dish and store it within a protective portion of the head. deployment:The personal ‘Mech of Galedon Military District commander Warlord Grieg Samsonov during the DCMS's Third Succession War invasion of Galtor III, only the massive autocannon remains, with the rest of the standard weaponry replaced with a PPC mounted in each arm. The remaining weight and space is devoted to six additional heat sinks. diff --git a/megameklab/data/mechfiles/mechs/Turning Points/HTP Glengary/Zeus (Leonidas).mtf b/megameklab/data/mechfiles/mechs/Turning Points/HTP Glengary/Zeus (Leonidas).mtf index 02d307e61..106ab37c4 100644 --- a/megameklab/data/mechfiles/mechs/Turning Points/HTP Glengary/Zeus (Leonidas).mtf +++ b/megameklab/data/mechfiles/mechs/Turning Points/HTP Glengary/Zeus (Leonidas).mtf @@ -7,7 +7,7 @@ TechBase:Inner Sphere Era:3056 Rules Level:2 role:Sniper -source:Historical Turning Points: Glengary +source:Historical Turning Points: Glengarry @@ -158,7 +158,7 @@ Ferro-Fibrous overview:The Zeus was first built by the Lyran Commonwealth in 2787, just as the First Succession War began. Built at the request of Lyran Commonwealth Armed Forces commanders for a new light-assault 'Mech designed to engage the enemy at long range and perform hit-and-run attacks. -capabilities:the Zeus is fast enough to keep up with most heavy 'Mechs, and with a sturdy frame, eleven and a half tons of standard armor and a versatile weapons array, is equally capable of defeating them. Its use of reliable, low-maintenance and easily modified systems at a time when most 'Mechs were built with cutting-edge technology also proved fortuitous, allowing the Zeus to be produced long after those advanced components had become Lostech. +capabilities:The Zeus is fast enough to keep up with most heavy 'Mechs, and with a sturdy frame, eleven and a half tons of standard armor and a versatile weapons array, is equally capable of defeating them. Its use of reliable, low-maintenance and easily modified systems at a time when most 'Mechs were built with cutting-edge technology also proved fortuitous, allowing the Zeus to be produced long after those advanced components had become Lostech. deployment:The personal 'Mech of Hauptmann-General Leonidas Brannock, commander of the 4th Skye Guards during their assault on Glengarry, the Zeus Leonidas was based on the ZEU-9S. It carried an Artemis IV enhanced LRM-20 and a Gauss rifle (each with two tons of ammunition) in place of the PPC and LRM-15. The rest of the weapons remained the same. It also carried an extra heat sink, bringing the total to twelve. To make room for this equipment the Leonidas used an XL engine. diff --git a/megameklab/data/mechfiles/mechs/Turning Points/HTP Luzerne/Cauldron-Born (Ebon Jaguar) (Samantha).mtf b/megameklab/data/mechfiles/mechs/Turning Points/HTP Luzerne/Cauldron-Born (Ebon Jaguar) (Samantha).mtf index 1894f7463..3eafe1681 100644 --- a/megameklab/data/mechfiles/mechs/Turning Points/HTP Luzerne/Cauldron-Born (Ebon Jaguar) (Samantha).mtf +++ b/megameklab/data/mechfiles/mechs/Turning Points/HTP Luzerne/Cauldron-Born (Ebon Jaguar) (Samantha).mtf @@ -160,7 +160,7 @@ overview:Introduced in 3049 to address flaws in the venerable Hellbringer, by Op capabilities:A custom configuration used by the 6th Striker Cluster CO Star Captain Samantha Kotare during the Operation Bulldog assault against Luzerne, her OmniMech was armed with an ER PPC and an Ultra AC/20 in its arms, supported by a trio of LRM-10's mounted in its right torso, and an ER Small Laser in its left. Two tons of reloads were carried for both the Ultra Autocannon and the LRM launchers. -history:Facing it for the first time when engaging the First Jaguar Guards Cluster in the Kado-Guchi Valley, the 'Mech's ability to take damage and remain operational led the Inner Sphere warriors who fought it to call it the Cauldron-Born after the unstoppable zombies of Irish myth. Paradoxically many of the other Clans also used the Inner Sphere Cauldron-Born reporting name, having first learned detailed information of the design from Inner Sphere sources. y Operation BULLDOG the Cauldron-Born made up a large proportion of the heavy 'Mechs of the rebuilding Smoke Jaguars, and following their Annihilation the design proliferated the remaining Clans, save the Jade Falcons, Wolves and Coyotes who continued to favor the Hellbringer. Following the Wars of Reaving the Ebon Jaguar had finally supplanted the Hellbringer in most Homeworld Clans, save the Coyotes who remained loyal to redeeming the honor of the design. +history:Facing it for the first time when engaging the First Jaguar Guards Cluster in the Kado-Guchi Valley, the 'Mech's ability to take damage and remain operational led the Inner Sphere warriors who fought it to call it the Cauldron-Born after the unstoppable zombies of Irish myth. Paradoxically many of the other Clans also used the Inner Sphere Cauldron-Born reporting name, having first learned detailed information of the design from Inner Sphere sources. By Operation BULLDOG the Cauldron-Born made up a large proportion of the heavy 'Mechs of the rebuilding Smoke Jaguars, and following their Annihilation the design proliferated the remaining Clans, save the Jade Falcons, Wolves and Coyotes who continued to favor the Hellbringer. Following the Wars of Reaving the Ebon Jaguar had finally supplanted the Hellbringer in most Homeworld Clans, save the Coyotes who remained loyal to redeeming the honor of the design. manufacturer:Huntress Manufacturing Plant DL-6 primaryfactory:Huntress diff --git a/megameklab/data/mechfiles/mechs/Turning Points/HTP Luzerne/Grasshopper (Reynolds).mtf b/megameklab/data/mechfiles/mechs/Turning Points/HTP Luzerne/Grasshopper (Reynolds).mtf index 23dc2e368..4ed59bc1c 100644 --- a/megameklab/data/mechfiles/mechs/Turning Points/HTP Luzerne/Grasshopper (Reynolds).mtf +++ b/megameklab/data/mechfiles/mechs/Turning Points/HTP Luzerne/Grasshopper (Reynolds).mtf @@ -163,7 +163,7 @@ capabilities:With great mobility and a predominately shorter-ranged, energy-base deployment:The customized Grasshopper used by 3rd Davion Guards Hauptmann Reynolds Allen when he commanded the Allen's Animals raiding company during Operation BIRD DOG. To help him hold out against Clan Smoke Jaguar forces on Luzerne, this 'Mech's standard weapons were replaced with a trio of Clan-Tech ER large lasers mounted in the head and center torso supported by a Clan ER Medium Laser mounted in each arm and side torso. The remaining free weight was devoted to IS-grade double heat sinks. -history:Problems integrating the original stealth systems with the chassis meant the Grasshopper missed the climactic end to the conflict. The stealth systems were ultimately removed from the final design. The untested and unorthodox 'Mech was distributed primarily to the regular army rather than the more prestigious Royal units, and within four years it could be found in most Star League regiments. Thus as the League dissolved, with the chaos of Operation EXODUS and the defection of many SLDF units to the Successor States, Grasshoppers found their way into the various House armies one way or another. Besides hunting down lighter machines to clear the way for heavier, less-mobile 'Mechs, the Grasshopper's mobility and endurance meant it often spearheaded assaults to storm fortifications, led flanking attacks to hit the enemy from the rear, and served as back-up brawler for companies of light and medium 'Mechs. Its ability to operate independently made it an excellent choice as a raider and guerrilla fighter, an attribute also prized by mercenary units in need of self-reliant 'Mechs. While popular the Grasshopper was also an uncommon sight during the Succession Wars, causing many commanders to mistakenly treat it as just another heavy 'Mech. By the time they realized their mistake it was too late, though following ComStar's publication of Technical Readout: 3025 military leaders became more familiar with the 'Mech. In the midst of the Second Succession War the Lantren Corporation's factory on Bryant was destroyed in 2843, a result of worsening global storms and damage inflicted during the conflict, causing production of the 'Mech to cease. However, the Grasshopper was usually prioritized over other 'Mechs, even a unit commander's own, when it came time to repair and rebuild after a battle. Thus most of the original production run was still in active duty even after centuries of use. Lantren Corporation would eventually introduce a new variant in 3049, the GHR-5J, which upgraded many of its original systems with superior lostech components. Yet the original model was so popular that it would still outnumber the -5J for decades to come by a ratio of three to one. Only when the Draconis Combine introduced their own C3 variant that trend began to reverse. Further variants were introduced in the years following, and the Grasshopper participated in many conflicts, including both sides of the Jihad. +history:Problems integrating the original stealth systems with the chassis meant the Grasshopper missed the climactic end to the conflict. The stealth systems were ultimately removed from the final design. The untested and unorthodox 'Mech was distributed primarily to the regular army rather than the more prestigious Royal units, and within four years it could be found in most Star League regiments. Thus as the League dissolved, with the chaos of Operation EXODUS and the defection of many SLDF units to the Successor States, Grasshoppers found their way into the various House armies one way or another. Besides hunting down lighter machines to clear the way for heavier, less-mobile 'Mechs, the Grasshopper's mobility and endurance meant it often spearheaded assaults to storm fortifications, led flanking attacks to hit the enemy from the rear, and served as back-up brawler for companies of light and medium 'Mechs. Its ability to operate independently made it an excellent choice as a raider and guerrilla fighter, an attribute also prized by mercenary units in need of self-reliant 'Mechs. While popular the Grasshopper was also an uncommon sight during the Succession Wars, causing many commanders to mistakenly treat it as just another heavy 'Mech. By the time they realized their mistake it was too late, though following ComStar's publication of Technical Readout: 3025 military leaders became more familiar with the 'Mech. In the midst of the Second Succession War the Lantren Corporation's factory on Bryant was destroyed in 2843, a result of worsening global storms and damage inflicted during the conflict, causing production of the 'Mech to cease. However, the Grasshopper was usually prioritized over other 'Mechs, even a unit commander's own, when it came time to repair and rebuild after a battle. Thus most of the original production run was still in active duty even after centuries of use. Lantren Corporation would eventually introduce a new variant in 3049, the GHR-5J, which upgraded many of its original systems with superior lostech components. Yet the original model was so popular that it would still outnumber the -5J for decades to come by a ratio of three to one. Only when the Draconis Combine introduced their own C3 variant that trend began to reverse. Further variants were introduced in the years following, and the Grasshopper participated in many conflicts, including both sides of the Jihad. manufacturer:Lantren Corporation primaryfactory:Bryant diff --git a/megameklab/data/mechfiles/mechs/Turning Points/HTP Misery/Atlas AS7-D (Danielle).mtf b/megameklab/data/mechfiles/mechs/Turning Points/HTP Misery/Atlas AS7-D (Danielle).mtf index 4f6c0a964..e190e3fbc 100644 --- a/megameklab/data/mechfiles/mechs/Turning Points/HTP Misery/Atlas AS7-D (Danielle).mtf +++ b/megameklab/data/mechfiles/mechs/Turning Points/HTP Misery/Atlas AS7-D (Danielle).mtf @@ -146,7 +146,7 @@ Heat Sink overview:"A 'Mech as powerful as possible, as impenetrable as possible, and as ugly and foreboding as conceivable, so that fear itself will be our ally.”-Aleksandr Kerensky -capabilities:The Atlas is probably the best-known BattleMech to ever set foot on the modern battlefield. Designed with specifications from Aleksandr Kerensky himself in 2755 in the midst of the Cameron Edicts, the Atlas was originally intended to ensure SLDF superiority over the Star League member states. Carrying the largest LRM launcher, the largest autocannon, and the largest SRM launcher possible, the Atlas can deal frightening amounts of damage in short amounts of time. Often used as a command vehicle, the Atlas mounts an advanced antenna and communications array, allowing it to engage in surface-to space communications in real time. The massive 19-ton hide of armor that protects the Atlas makes it a difficult foe to take down. Indeed, most MechWarriors choose to fall back rather than face one head-one, as its lumbering gait mean it can rarely catch up to other 'Mechs that choose to flee it. A full year of development went into crafting the famous "Death's Head" of the 'Mech to achieve the perfect ratio of functionality and fear. The head is also quite roomy and allows a small satellite dish to be mounted for surface-to-space communications. During combat the pilot can easily fold up the dish and store it within a protective portion of the head. +capabilities:The Atlas is probably the best-known BattleMech to ever set foot on the modern battlefield. Designed with specifications from Aleksandr Kerensky himself in 2755 in the midst of the Cameron Edicts, the Atlas was originally intended to ensure SLDF superiority over the Star League member states. Carrying the largest LRM launcher, the largest autocannon, and the largest SRM launcher possible, the Atlas can deal frightening amounts of damage in short amounts of time. Often used as a command vehicle, the Atlas mounts an advanced antenna and communications array, allowing it to engage in surface-to-space communications in real time. The massive 19-ton hide of armor that protects the Atlas makes it a difficult foe to take down. Indeed, most MechWarriors choose to fall back rather than face one head-on, as its lumbering gait means it can rarely catch up to other 'Mechs that choose to flee it. A full year of development went into crafting the famous "Death's Head" of the 'Mech to achieve the perfect ratio of functionality and fear. The head is also quite roomy and allows a small satellite dish to be mounted for surface-to-space communications. During combat the pilot can easily fold up the dish and store it within a protective portion of the head. deployment:Piloted by Wolf's Dragoons Captain Danielle Rondema, this modified Atlas carried three medium lasers in each arm, trading away the SRM rack to do so. The additional heat was dissipated by two additional heat sinks that replaced the rear-firing medium lasers. diff --git a/megameklab/data/mechfiles/mechs/Turning Points/HTP Tortuga/Awesome AWS-8Q (Buck).mtf b/megameklab/data/mechfiles/mechs/Turning Points/HTP Tortuga/Awesome AWS-8Q (Buck).mtf index a3d0daef4..e9acb594a 100644 --- a/megameklab/data/mechfiles/mechs/Turning Points/HTP Tortuga/Awesome AWS-8Q (Buck).mtf +++ b/megameklab/data/mechfiles/mechs/Turning Points/HTP Tortuga/Awesome AWS-8Q (Buck).mtf @@ -157,7 +157,7 @@ IS Ferro-Fibrous overview:The Awesome was designed in 2665 for the Star League by the Technicron Conglomorate and was based on the aging STR-2C Striker. While not as fast as its forefather, the Awesome is a strong assault 'Mech. -capabilities:The Awesome's abilities are nearly entirely dependent on its particle projection cannons. The AWS can withstand a severe and consistent onslaught from its weaponry thanks to several heat sinks. With one and a half tons more armor than the Striker, the AWS is more protected than even the BattleMaster. The Amazing, like any other BattleMech, has weaknesses. While it is lethal at range, it is less effective in close-quarters combat since its PPCs have a tougher time connecting with the victim. In that case, it just possesses a light weapon and a left fist to fall back on. Because of its limited mobility, it is vulnerable to flanking attacks from speedier opponents seeking to get past the PPCs. While they face arguably of the heaviest rear armor found on any BattleMech, the Awesome's lack of rear facing armaments or a weapon mount on its left arm has offered numerous MechWarriors a fighting chance. Formations of Awesomes (or even just a few) are incredibly effective and tough to stop or defeat when correctly placed by commanders who are knowledgeable of the AWS's limitations. +capabilities:The Awesome's abilities are nearly entirely dependent on its particle projection cannons. The AWS can withstand a severe and consistent onslaught from its weaponry thanks to several heat sinks. With one and a half tons more armor than the Striker, the AWS is more protected than even the BattleMaster. The Awesome, like any other BattleMech, has weaknesses. While it is lethal at range, it is less effective in close-quarters combat since its PPCs have a tougher time connecting with the victim. In that case, it just possesses a light weapon and a left fist to fall back on. Because of its limited mobility, it is vulnerable to flanking attacks from speedier opponents seeking to get past the PPCs. While they face arguably of the heaviest rear armor found on any BattleMech, the Awesome's lack of rear facing armaments or a weapon mount on its left arm has offered numerous MechWarriors a fighting chance. Formations of Awesomes (or even just a few) are incredibly effective and tough to stop or defeat when correctly placed by commanders who are knowledgeable of the AWS's limitations. deployment:This standard Awesome was modified by Major Buck Tripp of The Thumpers. It carries the standard three PPCs of the Awesome-8Q, but uses an XL Gyro and larger XL engine to reach a maximum speed of 84 km/h. It removes twelve heat sinks and upgrades the remaining sixteen to double strength models. It also removes the small laser and standard armor, instead using thirteen and a half tons of Ferro-Fibrous armor to provide protection. diff --git a/megameklab/data/mechfiles/mechs/Turning Points/JTP Dieron/Kodiak Cale.mtf b/megameklab/data/mechfiles/mechs/Turning Points/JTP Dieron/Kodiak Cale.mtf index 71793c43d..3949b7c3f 100644 --- a/megameklab/data/mechfiles/mechs/Turning Points/JTP Dieron/Kodiak Cale.mtf +++ b/megameklab/data/mechfiles/mechs/Turning Points/JTP Dieron/Kodiak Cale.mtf @@ -149,7 +149,7 @@ capabilities:Though not taken to the same extreme as other Clan Totem 'Mechs, th 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. -history:The vast majority of Kodiaks are used by the Ghost Bears, and indeed was exclusive to them in the first years since its introduction. Of those which are found in other toumans, Clan Snow Raven has the largest share, payment for their help in relocating to the Inner Sphere, followed by Clan Goliath Scorpion and Clan Cloud Cobra. Among the Crusader Clans though, only Clan Ice Hellion fields a handful of these 'Mechs.[3] As a interesting note, and proof of the expansion of the Kodiak, at least two of these mechs were found in a Smoke Jaguar unit on planet Asgard, during Operation Bulldog. +history:The vast majority of Kodiaks are used by the Ghost Bears, and indeed was exclusive to them in the first years since its introduction. Of those which are found in other toumans, Clan Snow Raven has the largest share, payment for their help in relocating to the Inner Sphere, followed by Clan Goliath Scorpion and Clan Cloud Cobra. Among the Crusader Clans though, only Clan Ice Hellion fields a handful of these 'Mechs. As a interesting note, and proof of the expansion of the Kodiak, at least two of these mechs were found in a Smoke Jaguar unit on planet Asgard, during Operation Bulldog. manufacturer:Field Refit primaryfactory:Field Refit diff --git a/megameklab/data/mechfiles/mechs/Turning Points/JTP Hespersus/Galahad GLH-3D Laodices.mtf b/megameklab/data/mechfiles/mechs/Turning Points/JTP Hespersus/Galahad GLH-3D Laodices.mtf index d91cc89ab..2941c107b 100644 --- a/megameklab/data/mechfiles/mechs/Turning Points/JTP Hespersus/Galahad GLH-3D Laodices.mtf +++ b/megameklab/data/mechfiles/mechs/Turning Points/JTP Hespersus/Galahad GLH-3D Laodices.mtf @@ -158,7 +158,7 @@ Endo Steel overview:Born from the Terran Hegemony's attempts to create a medium fire-support platform that would be more advanced than the RLN-1N Rifleman. capabilities:The Galahad utilizes special building materials in the form of eleven tons of Ferro-Fibrous armor and Endo Steel internals. To fit the massive weapons on the Galahad, the engine was dropped to a GM 180, giving it a maximum speed of only 54 km/h, making it difficult for the 'Mech to keep up with its companions in most cases. -deployment:This custom variant of the Galahad was used by Phantom Demi-Precentor Delta Laodices, a commander of the 40th Shadow Division.[12] It uses a Small Cockpit, an Improved C3 Computer, one Light Gauss Rifle, and a Guardian ECM Suite - just like a standard 3D Galahad. It differs, however, in that it drops the other Light Gauss Rifle and one ton of ammunition, replacing them with an ER PPC enhanced by an experimental PPC Capacitor in the right arm. In addition, a Light PPC is mounted in the center torso. These modifications allow the 'Mech to remain in combat for far longer. +deployment:This custom variant of the Galahad was used by Phantom Demi-Precentor Delta Laodices, a commander of the 40th Shadow Division. It uses a Small Cockpit, an Improved C3 Computer, one Light Gauss Rifle, and a Guardian ECM Suite - just like a standard 3D Galahad. It differs, however, in that it drops the other Light Gauss Rifle and one ton of ammunition, replacing them with an ER PPC enhanced by an experimental PPC Capacitor in the right arm. In addition, a Light PPC is mounted in the center torso. These modifications allow the 'Mech to remain in combat for far longer. history:Mitchell Vehicles unveiled the GLH-1D Galahad in 2570. Though it outgunned the earlier design and found significant acceptance within the Hegemony Armed Forces, the Galahad suffered from the same heat issues as the BattleMech it was meant to replace. With the development of the new Gauss Rifle, Mitchell Vehicles decided in 2594 to redesign the Galahad around these new weapons, changing it into a heavy design in the process. Production of the 2D Galahad continued for almost two centuries, only stopping when the Graham IV manufacturing center was destroyed during the First Succession War. While the older GLH-1D did spread to the Member State militaries, because the GLH-2D possessed so much advanced technology, the Galahad was mainly (but not exclusively) reserved for SLDF Royal Units. Most functioning GLH-2D Galahads departed the Inner Sphere during Kerensky's Exodus. Though sizable numbers of the less advanced GLH-1D remained behind, the technological decline of the Succession Wars era soon made it impossible for the Inner Sphere to maintain either variant. Outside the secret stockpiles of ComStar and patchwork examples in the Periphery or other backwaters, the Galahad was one of many designs that disappeared from the battlefield. During the Word of Blake Jihad, the Blakists put the Galahad back in production for the first time in centuries at the massive Defiance Industries plant on Hesperus II. After the factory was retaken by the Lyran Alliance and its allies, production of the 'Mech would continue for the Lyrans as of 3079. diff --git a/megameklab/data/mechfiles/mechs/Turning Points/JTP New Avalon/Griffin GRF-1E2 Sparky 2.0.mtf b/megameklab/data/mechfiles/mechs/Turning Points/JTP New Avalon/Griffin GRF-1E2 Sparky 2.0.mtf index 7ff0e1010..ef149aa34 100644 --- a/megameklab/data/mechfiles/mechs/Turning Points/JTP New Avalon/Griffin GRF-1E2 Sparky 2.0.mtf +++ b/megameklab/data/mechfiles/mechs/Turning Points/JTP New Avalon/Griffin GRF-1E2 Sparky 2.0.mtf @@ -167,7 +167,7 @@ capabilities:The massive and efficient fusion engine of the Griffin, giving it a deployment:The personal ‘Mech of Leftenant Natasha Ergen of the Fifth FedCom RCT, her stock Griffin had been refitted with ferro-fibrous armor and a light fusion engine. Fourteen double heat sinks and a targeting computer allowed Ergen to obtain maximum effect from an all-energy weapons array consisting of an ER PPC, two standard medium lasers mounted one per side torso alongside three ER medium lasers, one mounted in each torso component. -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. +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. manufacturer:Corean Enterprises (Refit) primaryfactory:New Avalon diff --git a/megameklab/data/mechfiles/mechs/Turning Points/OTP Hanseatic Crusade/Tolva.mtf b/megameklab/data/mechfiles/mechs/Turning Points/OTP Hanseatic Crusade/Tolva.mtf index d2dd65dc2..609ed14ca 100644 --- a/megameklab/data/mechfiles/mechs/Turning Points/OTP Hanseatic Crusade/Tolva.mtf +++ b/megameklab/data/mechfiles/mechs/Turning Points/OTP Hanseatic Crusade/Tolva.mtf @@ -5,7 +5,7 @@ mul id:7882 Config:Quad techbase:Clan era:3145 -source:Operational Turning Points: Hanseatic CrusaDe +source:Operational Turning Points: Hanseatic Crusade rules level:3 role:Skirmisher diff --git a/megameklab/data/mechfiles/mechs/Turning Points/OTP WidowMaker Absorption/Highlander HGN-732 (Jorgensson).mtf b/megameklab/data/mechfiles/mechs/Turning Points/OTP WidowMaker Absorption/Highlander HGN-732 (Jorgensson).mtf index f7d8a449c..134e8d577 100644 --- a/megameklab/data/mechfiles/mechs/Turning Points/OTP WidowMaker Absorption/Highlander HGN-732 (Jorgensson).mtf +++ b/megameklab/data/mechfiles/mechs/Turning Points/OTP WidowMaker Absorption/Highlander HGN-732 (Jorgensson).mtf @@ -165,7 +165,7 @@ capabilities:Initially designed as a dedicated city and installation defender, t deployment:Used by Clan Widowmaker Khan Cal Jorgensson, this Highlander uses two Clan spec ER Large Lasers and a Clan spec Gauss Rifle for its armament. It also has an Artemis IV enhanced LRM-20 and thirteen double heat sinks. The SRM is removed. Its protection is identical to the standard HGN-732 Highlander. -history:during the design's initial trial runs that pilots began using these 'Mechs in what would infamously become known as the "Highlander Burial". Leaping into the air and landing directly on their enemy, a Highlander could literally drive a light 'Mech into the ground. So successful was this maneuver that the design team re-engineered the legs to withstand repeated death-from-above attacks and turned what had been a desperation move into an art form, giving Highlander pilots an additional psychological edge. As with other Star League era designs the Highlander would suffer the loss of technology brought about by the Succession Wars, and when StarCorps' factory on Son Hoa was devastated towards the end of the Second Succession War the original HGN-732 became virtually extinct. An agreement between StarCorps and Hollis Incorporated to rebuild destroyed chassis from scratch using readily-available technology kept the line going until the mid-3030s when limited production was restarted by StarCorps on Son Hoa and Corey, producing barely a dozen new 'Mechs per year. These HGN-733 Highlanders were used in small numbers by the Capellan Confederation and Lyran Commonwealth, commonly as part of lances containing Exterminators, Victors, Grasshoppers and Catapults. Unbeknownst to many, ComStar also maintained a large stock of Highlanders left over from the Star League, some of which they gifted to the Draconis Combine during the War of 3039. The appearance of so many seemingly rare 733s, along with a few 732s whose advanced technology managed to slip through ComStar screening, had a large impact on Lyran morale during that conflict. ComStar would also use the design in their own military forces, the Com Guard, and even during the Clan Invasion a few original 732s would take to the field as part of the Clans' fighting forces. The Northwind Highlanders especially favored this namesake Battlemech. In fact, during the Succession Wars, they were the only Inner Sphere army to keep a large number of them operational, along with ComStar. The Highlanders are specially skilled in delivering the famed Highlander Burial maneuver. By 3057 StarCorps' Son Hoa line was at full production, producing brand-new original-spec Highlanders for Lyran units of the Federated Commonwealth, just in time to take part in the FedCom Civil War. Highlanders would continue to be produced all the way through to the Jihad, where advanced variants fought both for and against the Word of Blake. +history:During the design's initial trial runs pilots began using these 'Mechs in what would infamously become known as the "Highlander Burial". Leaping into the air and landing directly on their enemy, a Highlander could literally drive a light 'Mech into the ground. So successful was this maneuver that the design team re-engineered the legs to withstand repeated death-from-above attacks and turned what had been a desperation move into an art form, giving Highlander pilots an additional psychological edge. As with other Star League era designs the Highlander would suffer the loss of technology brought about by the Succession Wars, and when StarCorps' factory on Son Hoa was devastated towards the end of the Second Succession War the original HGN-732 became virtually extinct. An agreement between StarCorps and Hollis Incorporated to rebuild destroyed chassis from scratch using readily-available technology kept the line going until the mid-3030s when limited production was restarted by StarCorps on Son Hoa and Corey, producing barely a dozen new 'Mechs per year. These HGN-733 Highlanders were used in small numbers by the Capellan Confederation and Lyran Commonwealth, commonly as part of lances containing Exterminators, Victors, Grasshoppers and Catapults. Unbeknownst to many, ComStar also maintained a large stock of Highlanders left over from the Star League, some of which they gifted to the Draconis Combine during the War of 3039. The appearance of so many seemingly rare 733s, along with a few 732s whose advanced technology managed to slip through ComStar screening, had a large impact on Lyran morale during that conflict. ComStar would also use the design in their own military forces, the Com Guard, and even during the Clan Invasion a few original 732s would take to the field as part of the Clans' fighting forces. The Northwind Highlanders especially favored this namesake Battlemech. In fact, during the Succession Wars, they were the only Inner Sphere army to keep a large number of them operational, along with ComStar. The Highlanders are specially skilled in delivering the famed Highlander Burial maneuver. By 3057 StarCorps' Son Hoa line was at full production, producing brand-new original-spec Highlanders for Lyran units of the Federated Commonwealth, just in time to take part in the FedCom Civil War. Highlanders would continue to be produced all the way through to the Jihad, where advanced variants fought both for and against the Word of Blake. manufacturer:Refit primaryfactory:Refit diff --git a/megameklab/data/mechfiles/mechs/Turning Points/TP Epsilon Eridani/Dragoon AEM-05C.mtf b/megameklab/data/mechfiles/mechs/Turning Points/TP Epsilon Eridani/Dragoon AEM-05C.mtf index a69ad8003..748547c99 100644 --- a/megameklab/data/mechfiles/mechs/Turning Points/TP Epsilon Eridani/Dragoon AEM-05C.mtf +++ b/megameklab/data/mechfiles/mechs/Turning Points/TP Epsilon Eridani/Dragoon AEM-05C.mtf @@ -167,7 +167,7 @@ capabilities:Armed with only a few, but powerful weapons found only in the 'Mech deployment:The only known example piloted by Demi-Precentor Jacob Kenyon commander of the Blessed Order's revived First Division's Unending Faith III,this Dragoon variant carries an Angel ECM Suite, Improved C3 Computer, an LB-10X, Plasma Rifle, and a pair of Medium X-Pulse Lasers. It also has three jump jets for a maximum jump range of 90 meters, and is protected by fourteen and a half tons of Clan-built Ferro-Lamellor armor. Two tons of LB-X ammunition are protected by CASE II. -history:n the year following the Amaris Coup, now-Emperor Amaris would have a means to make his dream into reality, and he began swiftly issuing contracts which would lead to the creation of the Dragoon. Built by Krupp Stellar Technologies Inc. in 2771 as their second BattleMech design, the Dragoon was designed with a similar modular subsystem akin to the Mercury BattleMech. With this system, the 'Mech's maintenance loads would be eased. Its modular nature would allow repair depots and factories to be able to reconfigure the design's weapons systems and its power plant for any needed mission-specific specs. Produced in limited numbers, only the elite of Amaris's regiments and a select few of Amaris's loyal chosen would receive the design and its variants. The design would see service in the Star League Civil War, often being salvaged by the Star League Defense Force. However, after the liberation of Terra, General Kerensky would order the purging of the design and the retooling of Krupp's two Dragoon production lines. The few remaining Dragoons in service elsewhere would become extinct before the 3rd Succession War. +history:In the year following the Amaris Coup, now-Emperor Amaris would have a means to make his dream into reality, and he began swiftly issuing contracts which would lead to the creation of the Dragoon. Built by Krupp Stellar Technologies Inc. in 2771 as their second BattleMech design, the Dragoon was designed with a similar modular subsystem akin to the Mercury BattleMech. With this system, the 'Mech's maintenance loads would be eased. Its modular nature would allow repair depots and factories to be able to reconfigure the design's weapons systems and its power plant for any needed mission-specific specs. Produced in limited numbers, only the elite of Amaris's regiments and a select few of Amaris's loyal chosen would receive the design and its variants. The design would see service in the Star League Civil War, often being salvaged by the Star League Defense Force. However, after the liberation of Terra, General Kerensky would order the purging of the design and the retooling of Krupp's two Dragoon production lines. The few remaining Dragoons in service elsewhere would become extinct before the 3rd Succession War. manufacturer:Krupp Stellar Technologies, Inc. primaryfactory:Terra diff --git a/megameklab/data/mechfiles/mechs/Turning Points/TP Irian/Marauder II MAD-6S.mtf b/megameklab/data/mechfiles/mechs/Turning Points/TP Irian/Marauder II MAD-6S.mtf index 6a2352273..9c6ea124e 100644 --- a/megameklab/data/mechfiles/mechs/Turning Points/TP Irian/Marauder II MAD-6S.mtf +++ b/megameklab/data/mechfiles/mechs/Turning Points/TP Irian/Marauder II MAD-6S.mtf @@ -165,7 +165,7 @@ capabilities:With the Marauder already a powerful and popular 'Mech, the Dragoon deployment:This variant was introduced in the Dark Age. It has a top speed of 54 km/h and a 90 meter jump radius. Powered by a light fusion engine it carries an ER PPC and medium pulse laser in each arm. A Gauss rifle is carried in the right torso, and is protected by CASE. It also carries a forward facing ER small laser and a head-mounted anti-missile system that covers the 'Mech's rear. Seventeen double heat sinks deal with the heat. -history:In 3010 officers of the famous Wolf's Dragoons mercenary unit contracted with Blackwell Industries of New Valencia on the project of modifying the highly successful 75-ton Marauder into a 100-ton assault 'Mech. Working from existing plans the design phase proved to be very short, the process of reinforcing the Marauder chassis turned out to be easier than expected, enhanced by the removal of the finicky and temperamental General Motors Whirlwind Autocannon for a much simpler Large Laser. First appearing with the famous Zeta Battalion before spreading to Alpha Regiment, the Dragoons' enemies soon learned to fear the appearance of Marauder IIs as foreshadowing a major advance, as for the remainder of the Third Succession War it remained the exclusive property of the mysterious Dragoons. This changed after the Fourth Succession War when Colonel Jaime Wolf authorized Blackwell to increase production and allow outside buyers access, on the provision that each sale had to be approved by the Dragoons. Now spreading in limited numbers, the largest buyer outside the Dragoons would be the Miller's Marauders mercenary unit, famed for its almost exclusive use of the Marauder chassis and the secret loan of its DropShips to Zeta Battalion for their climactic rescue of the rest of the Dragoons on Crossing. When new unit commander Major Susan Barber expressed interest in the Marauder II, Colonel Wolf gave Blackwell the go-ahead to supply her with all she needed, by the Clan Invasion the now renamed Barber's Marauder II would boast almost a regiment's worth of the fearsome assault 'Mech. Though Barber's Marauder II would help drive the considerable interest and demand for the powerful assault 'Mech, they would also damage its seeming aura of invincibility following their ignoble destruction by Clan Jade Falcon on Koniz in June 3064. Seeking to rekindle interest in their flagship 'Mech following its disastrous showing on Koniz, GM/Blackwell noted the Vicore Industries triggered refresh of "classic" designs to develop a more powerful and visually refreshed model. The resulting MAD-4S variant was the first widely available Marauder II, Wolf's Dragoons' easing of sale restrictions partly motivated by profit but also as a means to punish the Lyran Alliance for the theft of the Blackwell developed light fusion engine, as of 3067 selling the 'Mech to all interested parties save those the Dragoons were fighting against in the Chaos March; the Word of Blake and the members of Trinity Alliance. The demand for the Marauder II would only increase in the Jihad following the Blakist destruction of GM and Blackwell's production facilities for the 'Mech as part of their vendetta against the Wolf's Dragoons, with many salvaged examples in use among the nations of the Inner Sphere in a large number of variations following the Blakists' fall, the most notable being the MAD-6D developed by the Federated Suns and shared with the Republic of the Sphere. +history:In 3010 officers of the famous Wolf's Dragoons mercenary unit contracted with Blackwell Industries of New Valencia on the project of modifying the highly successful 75-ton Marauder into a 100-ton assault 'Mech. Working from existing plans the design phase proved to be very short, the process of reinforcing the Marauder chassis turned out to be easier than expected, enhanced by the removal of the finicky and temperamental General Motors Whirlwind Autocannon for a much simpler Large Laser. First appearing with the famous Zeta Battalion before spreading to Alpha Regiment, the Dragoons' enemies soon learned to fear the appearance of Marauder IIs as foreshadowing a major advance, as for the remainder of the Third Succession War it remained the exclusive property of the mysterious Dragoons. This changed after the Fourth Succession War when Colonel Jaime Wolf authorized Blackwell to increase production and allow outside buyers access, on the provision that each sale had to be approved by the Dragoons. Now spreading in limited numbers, the largest buyer outside the Dragoons would be the Miller's Marauders mercenary unit, famed for its almost exclusive use of the Marauder chassis and the secret loan of its DropShips to Zeta Battalion for their climactic rescue of the rest of the Dragoons on Crossing. When new unit commander Major Susan Barber expressed interest in the Marauder II, Colonel Wolf gave Blackwell the go-ahead to supply her with all she needed, by the Clan Invasion the now renamed Barber's Marauders would boast almost a regiment's worth of the fearsome assault 'Mech. Though Barber's Marauder II would help drive the considerable interest and demand for the powerful assault 'Mech, they would also damage its seeming aura of invincibility following their ignoble destruction by Clan Jade Falcon on Koniz in June 3064. Seeking to rekindle interest in their flagship 'Mech following its disastrous showing on Koniz, GM/Blackwell noted the Vicore Industries triggered refresh of "classic" designs to develop a more powerful and visually refreshed model. The resulting MAD-4S variant was the first widely available Marauder II, Wolf's Dragoons' easing of sale restrictions partly motivated by profit but also as a means to punish the Lyran Alliance for the theft of the Blackwell developed light fusion engine, as of 3067 selling the 'Mech to all interested parties save those the Dragoons were fighting against in the Chaos March; the Word of Blake and the members of Trinity Alliance. The demand for the Marauder II would only increase in the Jihad following the Blakist destruction of GM and Blackwell's production facilities for the 'Mech as part of their vendetta against the Wolf's Dragoons, with many salvaged examples in use among the nations of the Inner Sphere in a large number of variations following the Blakists' fall, the most notable being the MAD-6D developed by the Federated Suns and shared with the Republic of the Sphere. manufacturer:Irian BattleMechs Unlimited primaryfactory:Irian diff --git a/megameklab/data/mechfiles/mechs/Turning Points/TP Vega 3039/Jenner JR7-F (Smith).mtf b/megameklab/data/mechfiles/mechs/Turning Points/TP Vega 3039/Jenner JR7-F (Smith).mtf index 727a18e0e..b606ace0f 100644 --- a/megameklab/data/mechfiles/mechs/Turning Points/TP Vega 3039/Jenner JR7-F (Smith).mtf +++ b/megameklab/data/mechfiles/mechs/Turning Points/TP Vega 3039/Jenner JR7-F (Smith).mtf @@ -162,7 +162,7 @@ capabilities:Five Smithson Lifter jump jets, two in each side torso and one in t deployment:Piloted by Tai-i Miki Smith of the 2nd Galedon Regulars during the 3039 battle of Vega. It drops all jump jets for 2 Medium Lasers in the torsos and an additional half ton of armor, maxing it out. -history:The Jenner became the standard light warhorse of the DCMS with the outbreak of the First Succession War, though its reputation would be forever tarnished following its role in the Kentares Massacre. The Jenner became the standard light warhorse of the DCMS with the outbreak of the First Succession War, though its reputation would be forever tarnished following its role in the Kentares Massacre. Construction of new Jenners continued at Diplan MechYard's factory on Ozawa until a raw mineral shortage caused a halt in 2815, though they continued to produce new chassis. In 2823 production resumed on Ozawa, with some three thousand chassis shipped to Diplan's subsidiary on Luthien for final assembly, which itself was retooling to begin full-scale production; by 2830 both production lines were producing 1,350 Jenners a year. The sheer destruction of the Succession Wars finally took their toll when the last Jenner factory was destroyed in 2848, though so many Jenners had been produced by then that nearly every DCMS battalion had at least one of these 'Mechs well into the War of 3039. While the other Successor States eventually managed to procure operational Jenners (every AFFS regiment along the Combine border had at least one), the design remained in predominant use by House Kurita. +history:Construction of new Jenners continued at Diplan MechYard's factory on Ozawa until a raw mineral shortage caused a halt in 2815, though they continued to produce new chassis. In 2823 production resumed on Ozawa, with some three thousand chassis shipped to Diplan's subsidiary on Luthien for final assembly, which itself was retooling to begin full-scale production; by 2830 both production lines were producing 1,350 Jenners a year. The sheer destruction of the Succession Wars finally took their toll when the last Jenner factory was destroyed in 2848, though so many Jenners had been produced by then that nearly every DCMS battalion had at least one of these 'Mechs well into the War of 3039. While the other Successor States eventually managed to procure operational Jenners (every AFFS regiment along the Combine border had at least one), the design remained in predominant use by House Kurita. manufacturer:Luthien Armor Works, Diplan 'Mechyards, Luthien Armor Works, Luthien Armor Works, Diplan 'Mechyards primaryfactory:Luthien, Abiy Adi, New Samarkand, Ozawa diff --git a/megameklab/data/mechfiles/mechs/Turning Points/TP Vega 3039/Panther PNT-9ALAG.mtf b/megameklab/data/mechfiles/mechs/Turning Points/TP Vega 3039/Panther PNT-9ALAG.mtf index 324a5f2ec..0f7f976ff 100644 --- a/megameklab/data/mechfiles/mechs/Turning Points/TP Vega 3039/Panther PNT-9ALAG.mtf +++ b/megameklab/data/mechfiles/mechs/Turning Points/TP Vega 3039/Panther PNT-9ALAG.mtf @@ -159,7 +159,7 @@ capabilities:Luckily the Panther had also proved itself to be quite hardy, sport deployment:Prizing speed, the Amphigean Light Assault Groups modify their Panthers for speed, dropping the 9R's jump jets to make room for a larger engine to attain a maximum speed of 86.4 kph. -history:The original PNT-8Z model underwent a revision after the disastrous Battle of St. John in 2759, when it was revealed that its main weapon, a Tronel Large Laser, was inefficient in both range and firepower for the immense waste heat generated. The Draconis Combine inherited Alshain Weapons' Panther factory on New Oslo when the Star League dissolved and quickly put the production line to work building new Panthers for the DCMS. Their first large-scale use by Kurita warriors came during the First Succession War in the battle for Quentin, when the 2nd Legion of Vega used their Panthers to severely maul the slower, heavier 'Mechs of the 42nd Avalon Hussars while avoiding return fire. Throughout the Succession Wars, the Combine was the only significant user of the Panther, often pairing it with the Jenner in a deadly combination of speed and firepower; though the other Successor States employed Panthers in smaller numbers, these were either the result of battlefield salvage or older League-era 8Z models. The Panther also proved itself a deadly urban combatant, using its mobility to easily navigate the more restricted space of a city environment and take out heavier opponents from rooftop sniping perches with its main weapon. Lyran MechWarriors eventually took to nicknaming the 'Mech the "Alley Cat" for its propensity to conduct dark alley-way "muggings. Demand for the Panther continued to increase, forcing Alshain to build a secondary factory on Jarett to keep up. In an ironic twist both factories fell within the borders of the Free Rasalhague Republic following its creation in 3034, transferring ownership to the new state, and soon the Panther became a mainstay of the KungsArmé. The situation did not last long however following the invasion of the Clans, and both planets were swiftly conquered by Clan Ghost Bear. While Alshain Weapons crash-built a new line on Tok Do in 3053, they could not maintain their pre-invasion production levels and focused on spare parts and refit kits instead. Eventually Wakazashi Enterprises bought the production license for the Panther and began rolling out new variants from its New Samarkand factory. These have gone on to serve in every DCMS unit since, including the bloody years of the Jihad. +history:The original PNT-8Z model underwent a revision after the disastrous Battle of St. John in 2759, when it was revealed that its main weapon, a Tronel Large Laser, was inefficient in both range and firepower for the immense waste heat generated. The Draconis Combine inherited Alshain Weapons' Panther factory on New Oslo when the Star League dissolved and quickly put the production line to work building new Panthers for the DCMS. Their first large-scale use by Kurita warriors came during the First Succession War in the battle for Quentin, when the 2nd Legion of Vega used their Panthers to severely maul the slower, heavier 'Mechs of the 42nd Avalon Hussars while avoiding return fire. Throughout the Succession Wars, the Combine was the only significant user of the Panther, often pairing it with the Jenner in a deadly combination of speed and firepower; though the other Successor States employed Panthers in smaller numbers, these were either the result of battlefield salvage or older League-era 8Z models. The Panther also proved itself a deadly urban combatant, using its mobility to easily navigate the more restricted space of a city environment and take out heavier opponents from rooftop sniping perches with its main weapon. Lyran MechWarriors eventually took to nicknaming the 'Mech the "Alley Cat" for its propensity to conduct dark alley-way "muggings. Demand for the Panther continued to increase, forcing Alshain to build a secondary factory on Jarett to keep up. In an ironic twist both factories fell within the borders of the Free Rasalhague Republic following its creation in 3034, transferring ownership to the new state, and soon the Panther became a mainstay of the KungsArmé. The situation did not last long however following the invasion of the Clans, and both planets were swiftly conquered by Clan Ghost Bear. While Alshain Weapons crash-built a new line on Tok Do in 3053, they could not maintain their pre-invasion production levels and focused on spare parts and refit kits instead. Eventually Wakazashi Enterprises bought the production license for the Panther and began rolling out new variants from its New Samarkand factory. These have gone on to serve in every DCMS unit since, including the bloody years of the Jihad. manufacturer:Alshain Weapons,Alshain Weapons(formerly GK&T owned), GK&T Enterprises primaryfactory:Alshain,Jarett,New Oslo diff --git a/megameklab/data/mechfiles/mechs/WoR Supplemental/Mad Cat (Timber Wolf) Z.mtf b/megameklab/data/mechfiles/mechs/WoR Supplemental/Mad Cat (Timber Wolf) Z.mtf index 9e07d0835..f990eb6d0 100644 --- a/megameklab/data/mechfiles/mechs/WoR Supplemental/Mad Cat (Timber Wolf) Z.mtf +++ b/megameklab/data/mechfiles/mechs/WoR Supplemental/Mad Cat (Timber Wolf) Z.mtf @@ -157,11 +157,11 @@ Clan Endo Steel -Empty- -Empty- -overview:overview:The Timber Wolf is a fast, heavy OmniMech. A signature design of the Clans' military might, it was arguably the first Clan OmniMech encountered by Inner Sphere forces (as opposed to periphery forces) on The Rock in 3049 by Phelan Kell. The Timber Wolf is vastly more powerful than either the Marauder or the Catapult. It uses its speed and firepower to engage an enemy at the range of its choosing. When first encountered by Inner Sphere forces the idea that a heavy 'Mech could move so swiftly while being as heavily armed and armored as the Timber Wolf was inconceivable. With its twelve tons of Ferro-Fibrous armor and arsenal that rivaled that of most assault 'Mechs of the era, it was completely alien to Inner Sphere military planners, commanders, and even the Precentor Martial of ComStar. Its technological secrets have since been reverse-engineered by the Inner Sphere. +overview:The Timber Wolf is a fast, heavy OmniMech. A signature design of the Clans' military might, it was arguably the first Clan OmniMech encountered by Inner Sphere forces (as opposed to periphery forces) on The Rock in 3049 by Phelan Kell. The Timber Wolf is vastly more powerful than either the Marauder or the Catapult. It uses its speed and firepower to engage an enemy at the range of its choosing. When first encountered by Inner Sphere forces the idea that a heavy 'Mech could move so swiftly while being as heavily armed and armored as the Timber Wolf was inconceivable. With its twelve tons of Ferro-Fibrous armor and arsenal that rivaled that of most assault 'Mechs of the era, it was completely alien to Inner Sphere military planners, commanders, and even the Precentor Martial of ComStar. Its technological secrets have since been reverse-engineered by the Inner Sphere. capabilities:Used by The Society's MechWarriors, this version of the Timber Wolf carries twin iATM 9 missile launchers with four tons of ammunition. Each arm carries an ER Large Laser and an ER Medium Pulse Laser. To maximize its battlefield utility it also carries a Nova CEWS in the center torso. -deployment:First introduced in 2945, the Timber Wolf was designed by Clan Wolf as a second generation OmniMech along with the Gargoyle and the Naga to replace the aging Woodsman. While the Gargoyle may have been a very capable, fast assault OmniMech, and the Naga may have been an excellent fire-support OmniMech, Clan Wolf (and indeed every other Clan) instantly realized the value of the Timber Wolf; thus, production rights to the Timber Wolf were jealously (and successfully) defended. Only through trade, gifts and battlefield salvage has the Timber Wolf entered the armies of other Clans. Until the invasion of the Inner Sphere, production of the Timber Wolf has been limited to a single facility on Strana Mechty. Despite it's prominence among the Wolves during the Clan Invasion, Refusal War and Word of Blake Jihad, the Timber Wolf became increasingly rare following the sundering of ties with the Homeworld Clans during the Wars of Reaving and Blakist scouring of Tamar. Being built by hand at W-7 plant on Weingarten as of 3080, with some parts even being individually machined due to missing data,[1] attrition vastly outstripped supply as the Wolves looked toward other designs. When Alaric Ward forged the Wolf Empire, he left the W-7 facilities to Clan Hell's Horses and ordered the Kallon plant on Thermopolis be retooled for Timber Wolf production, restoring it's position within the Wolves touman. +deployment:First introduced in 2945, the Timber Wolf was designed by Clan Wolf as a second generation OmniMech along with the Gargoyle and the Naga to replace the aging Woodsman. While the Gargoyle may have been a very capable, fast assault OmniMech, and the Naga may have been an excellent fire-support OmniMech, Clan Wolf (and indeed every other Clan) instantly realized the value of the Timber Wolf; thus, production rights to the Timber Wolf were jealously (and successfully) defended. Only through trade, gifts and battlefield salvage has the Timber Wolf entered the armies of other Clans. Until the invasion of the Inner Sphere, production of the Timber Wolf has been limited to a single facility on Strana Mechty. Despite it's prominence among the Wolves during the Clan Invasion, Refusal War and Word of Blake Jihad, the Timber Wolf became increasingly rare following the sundering of ties with the Homeworld Clans during the Wars of Reaving and Blakist scouring of Tamar. Being built by hand at W-7 plant on Weingarten as of 3080, with some parts even being individually machined due to missing data, attrition vastly outstripped supply as the Wolves looked toward other designs. When Alaric Ward forged the Wolf Empire, he left the W-7 facilities to Clan Hell's Horses and ordered the Kallon plant on Thermopolis be retooled for Timber Wolf production, restoring it's position within the Wolves touman. history:Vaguely resembling a cross-over between the MAD (Marauder) and CAT (Catapult) series, the Timber Wolf was tagged with the Inner Sphere reporting name Mad Cat on first contact. (The targeting computer on Phelan Kell's Wolfhound switched between MAD and CAT when trying to identify it; upon analyzing the data recording from Kell's 'Mech, Precentor Martial Anastasius Focht later officially designated it "Mad Cat". diff --git a/megameklab/data/mechfiles/mechs/WoR Supplemental/Pariah (Septicemia) UW.mtf b/megameklab/data/mechfiles/mechs/WoR Supplemental/Pariah (Septicemia) UW.mtf index fbd00fd6f..9c78db602 100644 --- a/megameklab/data/mechfiles/mechs/WoR Supplemental/Pariah (Septicemia) UW.mtf +++ b/megameklab/data/mechfiles/mechs/WoR Supplemental/Pariah (Septicemia) UW.mtf @@ -161,7 +161,7 @@ Clan Ammo LRTorpedo-15 (OMNIPOD) overview:The backbone of The Society's military forces, the Septicemia was a utilitarian medium-class workhorse. Devoid of the more experimental technology utilized by the Cephalus and Osteon to allow it to be built in higher volumes, the Septicemia saves weight with an XL Engine, Endo Steel chassis, and nine tons of Ferro-Fibrous armor. While the location of its weaponry in its torsos hampers its ability to carry Battle Armor, this was intentional to try and ensure hand actuators were retained to maximize its physical combat abilities. -capabilities:ntended for underwater operations, this variant is equipped with a M.A.S.S and five Underwater Maneuvering Units. To protect against hull breaches, it's also equipped with a BattleMech HarJel System. Offensively, it carries a single LRT-15 and three SRT-4 launchers in the left and right torsos. Two tons of ammunition for each launcher type can be found in the legs. +capabilities:Intended for underwater operations, this variant is equipped with a M.A.S.S and five Underwater Maneuvering Units. To protect against hull breaches, it's also equipped with a BattleMech HarJel System. Offensively, it carries a single LRT-15 and three SRT-4 launchers in the left and right torsos. Two tons of ammunition for each launcher type can be found in the legs. deployment:Planning their OmniMech forces around a single mass-produced design intended to work in concert with two rarer but cutting-edge units, the Septicemia was built using proven technology with a focus towards mutual support on the battlefield, its every aspect intended to allow it to engage the Clan toumans using methods of warfare they found dezgra. Appearing during the Wars of Reaving when Clan warriors were even more intent on an exceedingly strict adherence of zellbrigen to avoid accusations of Taint, the Septicemia would prove frighteningly effective, earning it the nickname of "Pariah" by the Clan Diamond Shark forces that first faced it on Babylon in 3072. diff --git a/megameklab/data/mechfiles/mechs/Wolf and Blake/Uziel UZL-2S Jacob II.mtf b/megameklab/data/mechfiles/mechs/Wolf and Blake/Uziel UZL-2S Jacob II.mtf index 2915af990..12306149e 100644 --- a/megameklab/data/mechfiles/mechs/Wolf and Blake/Uziel UZL-2S Jacob II.mtf +++ b/megameklab/data/mechfiles/mechs/Wolf and Blake/Uziel UZL-2S Jacob II.mtf @@ -144,7 +144,7 @@ overview:Built at Defiance Industries' Furillo plant, the Uziel is an effective capabilities:The Uziel is built on a Foundation E50 Endo Steel chassis that has a GM 300 XL engine that provides the 'Mech with a top speed of 97.2 km/h. The 'Mech's mobility is enhanced with six Rawlings 50 jump jets that allow the 'Mech to jump up to one hundred and eighty meters. The Uziel is armored with eight tons of Maximillian 100 armor that gives the Uziel adequate protection from enemy fire. To dissipate the heat produced by the 'Mech's weapons, it carries eleven double heat sinks. -deployment:Continuing to upgrade his 'Mech, when the Widows faced off against the Opacus Venatori in 3071[13], Jacob's Uziel carried experimental systems. Fitted with a Supercharger to boost its speed and mounting extra half ton of armor thanks to its use of an XL Gyro, the Rotary Autocannons are replaced with a pair of GM Whirlwind Light AC/5's linked to BL-AM-WC Actuator Enhancement Systems, while the twin small lasers and SRM rack are swapped for Defiance Industries produced paired Medium Pulse Lasers and Streak SRM-6 launcher. With a single ton of reloads for the efficient Streak Missile Launcher, four tons of reloads for the autocannons allows Jacob to carry nearly any combination of specialty munitions. +deployment:Continuing to upgrade his 'Mech, when the Widows faced off against the Opacus Venatori in 3071, Jacob's Uziel carried experimental systems. Fitted with a Supercharger to boost its speed and mounting extra half ton of armor thanks to its use of an XL Gyro, the Rotary Autocannons are replaced with a pair of GM Whirlwind Light AC/5's linked to BL-AM-WC Actuator Enhancement Systems, while the twin small lasers and SRM rack are swapped for Defiance Industries produced paired Medium Pulse Lasers and Streak SRM-6 launcher. With a single ton of reloads for the efficient Streak Missile Launcher, four tons of reloads for the autocannons allows Jacob to carry nearly any combination of specialty munitions. manufacturer:Defiance Industries primaryfactory:Furillo diff --git a/megameklab/data/mechfiles/mechs/Wolf and Blake/Uziel UZL-2S Jacob.mtf b/megameklab/data/mechfiles/mechs/Wolf and Blake/Uziel UZL-2S Jacob.mtf index 099d76570..a17fd4d61 100644 --- a/megameklab/data/mechfiles/mechs/Wolf and Blake/Uziel UZL-2S Jacob.mtf +++ b/megameklab/data/mechfiles/mechs/Wolf and Blake/Uziel UZL-2S Jacob.mtf @@ -144,7 +144,7 @@ overview:Built at Defiance Industries' Furillo plant, the Uziel is an effective capabilities:The Uziel is built on a Foundation E50 Endo Steel chassis that has a GM 300 XL engine that provides the 'Mech with a top speed of 97.2 km/h. The 'Mech's mobility is enhanced with six Rawlings 50 jump jets that allow the 'Mech to jump up to one hundred and eighty meters. The Uziel is armored with eight tons of Maximillian 100 armor that gives the Uziel adequate protection from enemy fire. To dissipate the heat produced by the 'Mech's weapons, it carries eleven double heat sinks. -deployment:Won in combat on Arc-Royal after the Wolf's Dragoons arrival, the reborn Black Widow Company's XO Jacob Kincaid set about upgrading his new 'Mech significantly. By the time of the Black Widow's return to Outreach in early 3070[11], Jacob's Uziel used a lighter 250 rated XL Engine and eight and half tons of Light Ferro-Fibrous armor to free up weight to mount a Rotary AC/5 in each arm while retaining the ER Small Lasers and SRM-6 rack. Three tons of autocannon reloads keep the rotaries firing, with a single ton carried for the SRM launcher. +deployment:Won in combat on Arc-Royal after the Wolf's Dragoons arrival, the reborn Black Widow Company's XO Jacob Kincaid set about upgrading his new 'Mech significantly. By the time of the Black Widow's return to Outreach in early 3070, Jacob's Uziel used a lighter 250 rated XL Engine and eight and half tons of Light Ferro-Fibrous armor to free up weight to mount a Rotary AC/5 in each arm while retaining the ER Small Lasers and SRM-6 rack. Three tons of autocannon reloads keep the rotaries firing, with a single ton carried for the SRM launcher. manufacturer:Defiance Industries primaryfactory:Furillo diff --git a/megameklab/data/mechfiles/mechs/Wolf and Blake/Wolfhound WLF-4WA.mtf b/megameklab/data/mechfiles/mechs/Wolf and Blake/Wolfhound WLF-4WA.mtf index 4e893e7bf..1aa08c274 100644 --- a/megameklab/data/mechfiles/mechs/Wolf and Blake/Wolfhound WLF-4WA.mtf +++ b/megameklab/data/mechfiles/mechs/Wolf and Blake/Wolfhound WLF-4WA.mtf @@ -162,7 +162,7 @@ capabilities:Archon Katrina Steiner directed TharHes Industries to create a Batt deployment:An electronic warfare variant of the WLF-4W model introduced in 3071, the 4WA retains the trio of torso-mounted Fusigon Longtooth light PPCs, but exchanges the arm-mounted lasers for a Guardian ECM suite. -history:The Kell Hounds were the first unit chosen to field-test the Wolfhound in combat because of their intense loyalty to House Steiner, followed shortly after by Wolf's Dragoons. The design was put through its paces during the Fourth Succession War, where it outperformed all expectations. This was especially true when the Wolfhound faced its intended targets, hitting the Jenner beyond its capacity to return fire while closing the distance on the Panther to get inside range of its primary armament. After the war's triumphant conclusion, the Federated Commonwealth purchased more Wolfhounds to outfit its troops, and the design was utilized again during the War of 3039. Wolfhounds sustained substantially fewer deaths than other 'Mechs during that fight, and as a result, only a few were captured by the Combine. While awed by the 'Mech, the Kuritans were too proud to replicate it, instead relying on captured examples to help create the Wolf Trap particularly to defeat the 'Mech. Arc-Royal MechWorks was eventually recruited in to construct Wolfhounds under license from TharHes, and the recovery of lostech owing to the Helm Memory Core allowed for the production of a more advanced model to combat the Clan Invasion. Sadly, it took too long for TharHes' factories to be retooled in order to build the WLF-2 model, which was introduced in 3052, before ComStar ended the invasion with the Battle of Tukayyid. These updated Wolfhounds were still created for both FedCom member states, but once the Lyran Alliance was formed, TharHes manufacturers began creating the newer WLF-3S variant. This new type was only distributed to units loyal to the Lyran state, and so fought on Katherine Steiner-side Davion's during the FedCom Civil War. During the Jihad, the Word of Blake launched a crushing attack on Tharkad, essentially shutting down TharHes' Wolfhound factory line; in response, Arc-Royal expanded production and created the WLF-4 variant to compensate for allied troops combating the Blakists' losses. +history:The Kell Hounds were the first unit chosen to field-test the Wolfhound in combat because of their intense loyalty to House Steiner, followed shortly after by Wolf's Dragoons. The design was put through its paces during the Fourth Succession War, where it outperformed all expectations. This was especially true when the Wolfhound faced its intended targets, hitting the Jenner beyond its capacity to return fire while closing the distance on the Panther to get inside range of its primary armament. After the war's triumphant conclusion, the Federated Commonwealth purchased more Wolfhounds to outfit its troops, and the design was utilized again during the War of 3039. Wolfhounds sustained substantially fewer deaths than other 'Mechs during that fight, and as a result, only a few were captured by the Combine. While awed by the 'Mech, the Kuritans were too proud to replicate it, instead relying on captured examples to help create the Wolf Trap particularly to defeat the 'Mech. Arc-Royal MechWorks was eventually recruited in to construct Wolfhounds under license from TharHes, and the recovery of lostech owing to the Helm Memory Core allowed for the production of a more advanced model to combat the Clan Invasion. Sadly, it took too long for TharHes' factories to be retooled in order to build the WLF-2 model, which was introduced in 3052, before ComStar ended the invasion with the Battle of Tukayyid. These updated Wolfhounds were still created for both FedCom member states, but once the Lyran Alliance was formed, TharHes manufacturers began creating the newer WLF-3S variant. This new type was only distributed to units loyal to the Lyran state, and so fought on Katherine Steiner-Davion's side during the FedCom Civil War. During the Jihad, the Word of Blake launched a crushing attack on Tharkad, essentially shutting down TharHes' Wolfhound factory line; in response, Arc-Royal expanded production and created the WLF-4 variant to compensate for allied troops combating the Blakists' losses. manufacturer:Arc-Royal MechWorks primaryfactory:Arc-Royal diff --git a/megameklab/data/mechfiles/mechs/XTRs/ComStar/Exterminator EXT-6CS.mtf b/megameklab/data/mechfiles/mechs/XTRs/ComStar/Exterminator EXT-6CS.mtf index baf1f9fd3..110d3281c 100644 --- a/megameklab/data/mechfiles/mechs/XTRs/ComStar/Exterminator EXT-6CS.mtf +++ b/megameklab/data/mechfiles/mechs/XTRs/ComStar/Exterminator EXT-6CS.mtf @@ -141,7 +141,7 @@ NullSignatureSystem overview:The Exterminator is a BattleMech that was designed in 2630 for the most dubious, but necessary, of purposes: Head Hunting. -capabilities:The weapons used by the Exterminator are not nearly as unique or high tech as the electronics on board. The primary weapons of the Exterminator are medium weight lasers, two of each in either arm. For long range engagements, the 'Mech also carries a missile launcher with one ton of reloads in the center torso. These weapons are backed up by a short range laser mounted in the head for when engagements close to point blank range, and, for defense against missile attacks, the Exterminator has a Anti-Missile System in the right torso with one ton of ammo. +capabilities:The weapons used by the Exterminator are not nearly as unique or high tech as the electronics on board. The primary weapons of the Exterminator are medium weight lasers, two in each arm. For long range engagements, the 'Mech also carries a missile launcher with one ton of reloads in the center torso. These weapons are backed up by a short range laser mounted in the head for when engagements close to point blank range, and, for defense against missile attacks, the Exterminator has a Anti-Missile System in the right torso with one ton of ammo. deployment:This experimental ComStar-produced variant first spotted in 3079 carries a light PPC in each arm, and a pair of medium pulse lasers as well. An MML 7 with three tons of ammunition in a CASE II–protected ammunition bay rounds out the armament. The anti-missile system is gone, but in its place are a Chameleon Light Polarization Shield and a Null-Signature System. These systems ensure that the 'Mech will be very difficult to hit. diff --git a/megameklab/data/mechfiles/mechs/XTRs/ComStar/Highlander HGN-641-X-2.mtf b/megameklab/data/mechfiles/mechs/XTRs/ComStar/Highlander HGN-641-X-2.mtf index 10cee96ec..4bbb311a1 100644 --- a/megameklab/data/mechfiles/mechs/XTRs/ComStar/Highlander HGN-641-X-2.mtf +++ b/megameklab/data/mechfiles/mechs/XTRs/ComStar/Highlander HGN-641-X-2.mtf @@ -150,7 +150,7 @@ capabilities:Initially designed as a dedicated city and installation defender, t deployment:This ComStar developed variant is equipped with a pair of Artemis IV-equipped MML-7 launchers with four tons of ammo. It keeps the Gauss Rifle of the standard Highlander and mounts a pair of ER Medium Lasers. CASE II systems protect the Gauss Rifle and missile ammunition from explosions. A C3 Slave unit allows the Highlander to share targeting data. Light Ferro-Fibrous armor and a Reinforced Structure provide protection from weapons fire. To make room for all the equipment, this Highlander uses an XL Engine and XL Gyro. -history:during the design's initial trial runs that pilots began using these 'Mechs in what would infamously become known as the "Highlander Burial". Leaping into the air and landing directly on their enemy, a Highlander could literally drive a light 'Mech into the ground. So successful was this maneuver that the design team re-engineered the legs to withstand repeated death-from-above attacks and turned what had been a desperation move into an art form, giving Highlander pilots an additional psychological edge. As with other Star League era designs the Highlander would suffer the loss of technology brought about by the Succession Wars, and when StarCorps' factory on Son Hoa was devastated towards the end of the Second Succession War the original HGN-732 became virtually extinct. An agreement between StarCorps and Hollis Incorporated to rebuild destroyed chassis from scratch using readily-available technology kept the line going until the mid-3030s when limited production was restarted by StarCorps on Son Hoa and Corey, producing barely a dozen new 'Mechs per year. These HGN-733 Highlanders were used in small numbers by the Capellan Confederation and Lyran Commonwealth, commonly as part of lances containing Exterminators, Victors, Grasshoppers and Catapults. Unbeknownst to many, ComStar also maintained a large stock of Highlanders left over from the Star League, some of which they gifted to the Draconis Combine during the War of 3039. The appearance of so many seemingly rare 733s, along with a few 732s whose advanced technology managed to slip through ComStar screening, had a large impact on Lyran morale during that conflict. ComStar would also use the design in their own military forces, the Com Guard, and even during the Clan Invasion a few original 732s would take to the field as part of the Clans' fighting forces. The Northwind Highlanders especially favored this namesake Battlemech. In fact, during the Succession Wars, they were the only Inner Sphere army to keep a large number of them operational, along with ComStar. The Highlanders are specially skilled in delivering the famed Highlander Burial maneuver. By 3057 StarCorps' Son Hoa line was at full production, producing brand-new original-spec Highlanders for Lyran units of the Federated Commonwealth, just in time to take part in the FedCom Civil War. Highlanders would continue to be produced all the way through to the Jihad, where advanced variants fought both for and against the Word of Blake. +history:During the design's initial trial runs pilots began using these 'Mechs in what would infamously become known as the "Highlander Burial". Leaping into the air and landing directly on their enemy, a Highlander could literally drive a light 'Mech into the ground. So successful was this maneuver that the design team re-engineered the legs to withstand repeated death-from-above attacks and turned what had been a desperation move into an art form, giving Highlander pilots an additional psychological edge. As with other Star League era designs the Highlander would suffer the loss of technology brought about by the Succession Wars, and when StarCorps' factory on Son Hoa was devastated towards the end of the Second Succession War the original HGN-732 became virtually extinct. An agreement between StarCorps and Hollis Incorporated to rebuild destroyed chassis from scratch using readily-available technology kept the line going until the mid-3030s when limited production was restarted by StarCorps on Son Hoa and Corey, producing barely a dozen new 'Mechs per year. These HGN-733 Highlanders were used in small numbers by the Capellan Confederation and Lyran Commonwealth, commonly as part of lances containing Exterminators, Victors, Grasshoppers and Catapults. Unbeknownst to many, ComStar also maintained a large stock of Highlanders left over from the Star League, some of which they gifted to the Draconis Combine during the War of 3039. The appearance of so many seemingly rare 733s, along with a few 732s whose advanced technology managed to slip through ComStar screening, had a large impact on Lyran morale during that conflict. ComStar would also use the design in their own military forces, the Com Guard, and even during the Clan Invasion a few original 732s would take to the field as part of the Clans' fighting forces. The Northwind Highlanders especially favored this namesake Battlemech. In fact, during the Succession Wars, they were the only Inner Sphere army to keep a large number of them operational, along with ComStar. The Highlanders are specially skilled in delivering the famed Highlander Burial maneuver. By 3057 StarCorps' Son Hoa line was at full production, producing brand-new original-spec Highlanders for Lyran units of the Federated Commonwealth, just in time to take part in the FedCom Civil War. Highlanders would continue to be produced all the way through to the Jihad, where advanced variants fought both for and against the Word of Blake. manufacturer:Refit (ComStar) primaryfactory:Various diff --git a/megameklab/data/mechfiles/mechs/XTRs/Corporations/Charger CGR-1X1.mtf b/megameklab/data/mechfiles/mechs/XTRs/Corporations/Charger CGR-1X1.mtf index 05bfda7bc..02245e6ba 100644 --- a/megameklab/data/mechfiles/mechs/XTRs/Corporations/Charger CGR-1X1.mtf +++ b/megameklab/data/mechfiles/mechs/XTRs/Corporations/Charger CGR-1X1.mtf @@ -145,7 +145,7 @@ Heavy Ferro-Fibrous overview:The Charger is seen as an example of abject failure in BattleMech design. Wells Technologies originally wanted to produce an ultra-heavy scout 'Mech for the Star League Defense Force that was not only fast but could survive contact with the enemy. -capabilities:The Charger is seen as an example of abject failure in BattleMech design. Wells Technologies originally wanted to produce an ultra-heavy scout 'Mech for the Star League Defense Force that was not only fast but could survive contact with the enemy. This was to be the 'Mech's downfall, as its popgun laser array proved to be quite laughable, capable of little more than fighting infantry and light combat vehicles. Its armoring, while respectable, could not stand up to sustained punishment, which meant if the 'Mech got too close to heavy combat or trapped by superior numbers it could be shot to pieces. +capabilities:This was to be the 'Mech's downfall, as its popgun laser array proved to be quite laughable, capable of little more than fighting infantry and light combat vehicles. Its armoring, while respectable, could not stand up to sustained punishment, which meant if the 'Mech got too close to heavy combat or trapped by superior numbers it could be shot to pieces. deployment:This experimental model was a heavily modified CGR-1A, with almost every system given a cutting-edge makeover. The ancient and massive 400-rated engine has been replaced with an XL model. A supercharger combined with MASC gives the 'Mech an astounding top speed. The old weaponry has been replaced with an ER Large Laser and a Medium X-Pulse Laser. Chaff pods and Laser Anti-Missile Systems supplement ferro-fibrous armor, and the 'Mech carries an advanced suite of electronics. diff --git a/megameklab/data/mechfiles/mechs/XTRs/Corporations/Firestarter FS9-X81.mtf b/megameklab/data/mechfiles/mechs/XTRs/Corporations/Firestarter FS9-X81.mtf index d671b25df..5556838ca 100644 --- a/megameklab/data/mechfiles/mechs/XTRs/Corporations/Firestarter FS9-X81.mtf +++ b/megameklab/data/mechfiles/mechs/XTRs/Corporations/Firestarter FS9-X81.mtf @@ -139,7 +139,7 @@ capabilities:Despite being shielded by five and a half tons of armor and capable deployment:This is an experimental prototype of the Firestarter that was created by Defiance Industries of Kwangjong-ni. Only three of these prototypes were produced as of 3074, and suffered from developmental problems with their components. Using the FS9-H as its base, the 'Mech is fitted with an XXL engine, a plasma rifle with 10 rounds as its main weapon, and a pair of medium X-Pulse lasers, both mounted in the right arm. The 'Mech retains the original base model's flamers and jump capabilities. -history:Firestarters, both ancient and contemporary, can still be found in abundance among planetary militias and House troops. Even though Blakist forces have taken over CMW's principal plant on Coventry, spare parts are still accessible from other Firestarter producers (including LAW, Ceres Metals, Defiance, and Independence Weaponry). Loki field offices near the Circinus Federation frontier are concerned about reports of a new variety using endo steel technology on Federation- occupied worlds. With its particular load-out, this new variation appears to be designed to spread chaos and destruction. Firestarters have also been seen in Level II formations with Blakist soldiers in their Protectorate, most frequently at "police demonstrations" and guarding suspected prison sites. These versions are thought to be Coventry goods. +history:Firestarters, both ancient and contemporary, can still be found in abundance among planetary militias and House troops. Even though Blakist forces have taken over CMW's principal plant on Coventry, spare parts are still accessible from other Firestarter producers (including LAW, Ceres Metals, Defiance, and Independence Weaponry). Loki field offices near the Circinus Federation frontier are concerned about reports of a new variety using endo steel technology on Federation-occupied worlds. With its particular load-out, this new variation appears to be designed to spread chaos and destruction. Firestarters have also been seen in Level II formations with Blakist soldiers in their Protectorate, most frequently at "police demonstrations" and guarding suspected prison sites. These versions are thought to be Coventry goods. manufacturer:Defiance Industries (Refit) primaryfactory:Kwangjong-ni diff --git a/megameklab/data/mechfiles/mechs/XTRs/Gladiators/Warhammer WHM-X7 The Lich.mtf b/megameklab/data/mechfiles/mechs/XTRs/Gladiators/Warhammer WHM-X7 The Lich.mtf index 225263055..b43022369 100644 --- a/megameklab/data/mechfiles/mechs/XTRs/Gladiators/Warhammer WHM-X7 The Lich.mtf +++ b/megameklab/data/mechfiles/mechs/XTRs/Gladiators/Warhammer WHM-X7 The Lich.mtf @@ -168,7 +168,7 @@ overview:The Warhammer proved to be a very capable 'Mech, and for centuries prac capabilities:The Warhammer was well-protected with strong armor for its age and weight, and the large number of heat sinks allowed it to "fire and maneuver" without fear. The most common engine arrangement propels the 'Mech to a cruising speed of 43.2 km/h and a top speed of 64.8 km/h, which is quick enough to keep up with most battles. The 'Mech's electronics, albeit antiquated by the 31st Century, were basic and functional, allowing it to assume command tasks when necessary. The targeting mechanism, in particular, made use of an unique Searchlight positioned above the 'Mech's left shoulder. The device could act as a conventional searchlight or immediately connect to the O/P 1500 ARB tracking system, transforming the 'Mech into a capable night fighter. -deployment:Piloted by Francis Indigo, this custom version used Experimental Technology to make a fearsome arena fighter. Using a Hybrid Internal Structure and light ferro-fibrous armor for baseline protection, The Lich also uses Armored Sensors, an Armored Engine and a Heavy-Duty Gyro to stay in the fight a lot longer. The arm-mounted weapons were replaced with Marauder-style weapons pods carrying a Snub-Nose PPC with PPC Capacitor and an ER medium laser. The standard SRM-6 was replaced with a Clan-tech Streak SRM-6 and the medium lasers upgraded to extended-range models. The small lasers were removed, along with the machine guns and their ammunition, while CASE II protected the Streak ammunition. The Lich would prove so successful that it resulted in the creation of the WHD-10CT, a mass-produced factory variant heavily based upon it. This is actually a Frankenmech but has been made in MM has a Warhammer Variant. The IS in MM won't match the TRO:. Unit included for completeness. +deployment:Piloted by Francis Indigo, this custom version used Experimental Technology to make a fearsome arena fighter. Using a Hybrid Internal Structure and light ferro-fibrous armor for baseline protection, The Lich also uses Armored Sensors, an Armored Engine and a Heavy-Duty Gyro to stay in the fight a lot longer. The arm-mounted weapons were replaced with Marauder-style weapons pods carrying a Snub-Nose PPC with PPC Capacitor and an ER medium laser. The standard SRM-6 was replaced with a Clan-tech Streak SRM-6 and the medium lasers upgraded to extended-range models. The small lasers were removed, along with the machine guns and their ammunition, while CASE II protected the Streak ammunition. The Lich would prove so successful that it resulted in the creation of the WHD-10CT, a mass-produced factory variant heavily based upon it. This is actually a Frankenmech but has been made in MM as a Warhammer Variant. The IS in MM won't match the TRO:. Unit included for completeness. history:StarCorps Industries introduced the Warhammer BattleMech in 2515 as "a mobile 'Mech with adequate firepower to destroy or severely damage any 'Mech of the same weight class or lower." The Warhammer continued to serve in the forces of the Great Houses throughout the Succession Wars after the Star League's demise. Despite very modest production rates, the large number of Warhammer factories dispersed over both the Inner Sphere and Periphery contributed to its endurance; Ronin Inc. was never able to construct more than five Warhammers per year from their Wallis factory. The recovery of the Helm Memory Core would prompt Inner Sphere manufacturers to create a slew of new Lostech-powered Warhammer versions, while the Periphery continued to produce original models for mercenaries and black marketeers. After the Clan Invasion, StarCorps chose to rehabilitate the ancient 'Mech with the greatest technological advancements, giving it new life. Initially, the business planned to construct only one new variety from its Crofton plant, but when word of the idea spread, other departments within StarCorps became involved and gathered on Crofton for a week-long conference to iron out the details. The conference turned out to be more jubilant than expected, and at the end of the bacchanalian "negotiations," it was determined that four new variations would be built: one for each of the Federated Suns, Capellan, Free Worlds League, and Lyran forces, employing technology unique to each realm. During the FedCom Civil War, some of these new 'Mechs were put through their paces. diff --git a/megameklab/data/mechfiles/mechs/XTRs/Gunslingers/Exterminator EXT-4DX Caine.mtf b/megameklab/data/mechfiles/mechs/XTRs/Gunslingers/Exterminator EXT-4DX Caine.mtf index 4e37dd22c..33eae5ad2 100644 --- a/megameklab/data/mechfiles/mechs/XTRs/Gunslingers/Exterminator EXT-4DX Caine.mtf +++ b/megameklab/data/mechfiles/mechs/XTRs/Gunslingers/Exterminator EXT-4DX Caine.mtf @@ -159,7 +159,7 @@ Foot Actuator overview:The Exterminator is a BattleMech that was designed in 2630 for the most dubious, but necessary, of purposes: Head Hunting. -capabilities:The weapons used by the Exterminator are not nearly as unique or high tech as the electronics on board. The primary weapons of the Exterminator are medium weight lasers, two of each in either arm. For long range engagements, the 'Mech also carries a missile launcher with one ton of reloads in the center torso. These weapons are backed up by a short range laser mounted in the head for when engagements close to point blank range, and, for defense against missile attacks, the Exterminator has a Anti-Missile System in the right torso with one ton of ammo. +capabilities:The weapons used by the Exterminator are not nearly as unique or high tech as the electronics on board. The primary weapons of the Exterminator are medium weight lasers, two in each arm. For long range engagements, the 'Mech also carries a missile launcher with one ton of reloads in the center torso. These weapons are backed up by a short range laser mounted in the head for when engagements close to point blank range, and, for defense against missile attacks, the Exterminator has a Anti-Missile System in the right torso with one ton of ammo. deployment:The personal 'Mech of Lieutenant Caine Barclay of the SLDF, this Exterminator removed the Null-Signature and Chameleon Light Polarization Shield as well as stripping out all of its weapons. In their place this version carried MASC and a supercharger, while each arm carried three medium pulse lasers. Each laser was equipped with a laser insulator to help diffuse the heat. The anti-missile system was retained, but a smaller engine dropped the cruising speed to 58 km/h. Despite the smaller engine, the MASC and supercharger allowed Barclay's 'Mech to reach burst speeds of 130 km/h. Though Barclay was successful in defeating ten DCMS MechWarriors in duels, the eleventh one destroyed his 'Mech diff --git a/megameklab/data/mechfiles/mechs/XTRs/Gunslingers/Thug THG-11ECX (Jose).mtf b/megameklab/data/mechfiles/mechs/XTRs/Gunslingers/Thug THG-11ECX (Jose).mtf index 72c628b4d..7a263058b 100644 --- a/megameklab/data/mechfiles/mechs/XTRs/Gunslingers/Thug THG-11ECX (Jose).mtf +++ b/megameklab/data/mechfiles/mechs/XTRs/Gunslingers/Thug THG-11ECX (Jose).mtf @@ -166,7 +166,7 @@ overview:The Thug was designed by Maltex Corporation as a direct competitor to t capabilities:The armament on the Thug is a very simple, yet effective, combination. Piloted by mercenary Jose Magellan during the fall of the Star League, this Thug variant replaces the standard engine with an extralight model. The PPCs are replaced by ER Large Lasers. In the space freed by the XL Engine, Magellan installed three more SRM-6 launchers, for a total of five. The cockpit adds a Command Console to allow a Rim Worlds commander to see the entire battlefield. Four jump jets allow the Thug Jose to cover 120 meters at a time. Finally, a Null Signature System interfered with SLDF targeting systems. -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. +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. manufacturer:Maltex Corporation, Earthwerks Incorporated primaryfactory:Errai, Keystone diff --git a/megameklab/data/mechfiles/mechs/XTRs/Kurita/Jenner JR10-X.mtf b/megameklab/data/mechfiles/mechs/XTRs/Kurita/Jenner JR10-X.mtf index 617124bc3..0e3c61caf 100644 --- a/megameklab/data/mechfiles/mechs/XTRs/Kurita/Jenner JR10-X.mtf +++ b/megameklab/data/mechfiles/mechs/XTRs/Kurita/Jenner JR10-X.mtf @@ -160,7 +160,7 @@ Mek Null Signature System overview:The Jenner became the standard light warhorse of the DCMS with the outbreak of the First Succession War, though its reputation would be forever tarnished following its role in the Kentares Massacre. capabilities:Five Smithson Lifter jump jets, two in each side torso and one in the center torso gave it a jumping distance of 150 meters, while its 245-rated Magna fusion engine allowed for a top speed of over 118 km/h, making it faster than most other 'Mechs. A favorite tactic of Jenner lances was to gang up on larger 'Mechs and unleash a devastating alpha strike. One or two of the 'Mechs would be equipped with inferno rounds, so even if the enemy survived the first strike they were badly damaged and running hot, allowing the Jenners to jump to safety and cool down themselves. A few seconds later the attack would be repeated until finally, the enemy was dead. It was also common practice to pair the Jenner with another Combine 'Mech, the Panther, creating a deadly combination of sheer speed and firepower with the slower Panther provided cover fire for the Jenner's flanking attack. The Jenner was such a favorite among Kurita MechWarriors that it became the benchmark against which all other newly designed Combine 'Mechs were compared. deployment:A Experimental variant of the Jenner developed during the Jihad. It was a test-bed chassis for LAW on New Samarkand in 3072. Using the JR7-K as its base, with extensive revisions. Its internal structure was changed for a Composite Internal Structure. Its engine changed out for a 245 rated XL Engine, which helps maintain the Jenner's original speed. The designer moved the forward jutting cockpit to a Torso Mounted Cockpit. Its missile weaponry was completely dropped in favor of increasing the 'Mech's medium laser armament up to six Medium Lasers. Jump Jets increased from base module to seven. For the 'Mech's protection, it has an Angel ECM and its hull has been encased with seven tons of Light Ferro-Fibrous Armor. For its stealth capacities, the 'Mech has been given an Experimental Null-Signature System. Only seven of these 'Mechs were known to have been built. -history:The Jenner became the standard light warhorse of the DCMS with the outbreak of the First Succession War, though its reputation would be forever tarnished following its role in the Kentares Massacre. The Jenner became the standard light warhorse of the DCMS with the outbreak of the First Succession War, though its reputation would be forever tarnished following its role in the Kentares Massacre. Construction of new Jenners continued at Diplan MechYard's factory on Ozawa until a raw mineral shortage caused a halt in 2815, though they continued to produce new chassis. In 2823 production resumed on Ozawa, with some three thousand chassis shipped to Diplan's subsidiary on Luthien for final assembly, which itself was retooling to begin full-scale production; by 2830 both production lines were producing 1,350 Jenners a year. The sheer destruction of the Succession Wars finally took their toll when the last Jenner factory was destroyed in 2848, though so many Jenners had been produced by then that nearly every DCMS battalion had at least one of these 'Mechs well into the War of 3039. While the other Successor States eventually managed to procure operational Jenners (every AFFS regiment along the Combine border had at least one), the design remained in predominant use by House Kurita. +history:Construction of new Jenners continued at Diplan MechYard's factory on Ozawa until a raw mineral shortage caused a halt in 2815, though they continued to produce new chassis. In 2823 production resumed on Ozawa, with some three thousand chassis shipped to Diplan's subsidiary on Luthien for final assembly, which itself was retooling to begin full-scale production; by 2830 both production lines were producing 1,350 Jenners a year. The sheer destruction of the Succession Wars finally took their toll when the last Jenner factory was destroyed in 2848, though so many Jenners had been produced by then that nearly every DCMS battalion had at least one of these 'Mechs well into the War of 3039. While the other Successor States eventually managed to procure operational Jenners (every AFFS regiment along the Combine border had at least one), the design remained in predominant use by House Kurita. manufacturer:Luthien Armor Works, Diplan 'Mechyards, Luthien Armor Works, Luthien Armor Works, Diplan 'Mechyards primaryfactory:Luthien, Abiy Adi, New Samarkand, Ozawa systemmanufacturer:CHASSIS:Alshain Class 48 diff --git a/megameklab/data/mechfiles/mechs/XTRs/Marik/Awesome AWS-11M.mtf b/megameklab/data/mechfiles/mechs/XTRs/Marik/Awesome AWS-11M.mtf index c2060eeb8..673bd5dbe 100644 --- a/megameklab/data/mechfiles/mechs/XTRs/Marik/Awesome AWS-11M.mtf +++ b/megameklab/data/mechfiles/mechs/XTRs/Marik/Awesome AWS-11M.mtf @@ -143,7 +143,7 @@ CLDouble Heat Sink overview:The Awesome was designed in 2665 for the Star League by the Technicron Conglomorate and was based on the aging STR-2C Striker. While not as fast as its forefather, the Awesome is a strong assault 'Mech. -capabilities:The Awesome's abilities are nearly entirely dependent on its particle projection cannons. The AWS can withstand a severe and consistent onslaught from its weaponry thanks to several heat sinks. With one and a half tons more armor than the Striker, the AWS is more protected than even the BattleMaster. The Amazing, like any other BattleMech, has weaknesses. While it is lethal at range, it is less effective in close-quarters combat since its PPCs have a tougher time connecting with the victim. In that case, it just possesses a light weapon and a left fist to fall back on. Because of its limited mobility, it is vulnerable to flanking attacks from speedier opponents seeking to get past the PPCs. While they face arguably of the heaviest rear armor found on any BattleMech, the Awesome's lack of rear facing armaments or a weapon mount on its left arm has offered numerous MechWarriors a fighting chance. Formations of Awesomes (or even just a few) are incredibly effective and tough to stop or defeat when correctly placed by commanders who are knowledgeable of the AWS's limitations. +capabilities:The Awesome's abilities are nearly entirely dependent on its particle projection cannons. The AWS can withstand a severe and consistent onslaught from its weaponry thanks to several heat sinks. With one and a half tons more armor than the Striker, the AWS is more protected than even the BattleMaster. The Awesome, like any other BattleMech, has weaknesses. While it is lethal at range, it is less effective in close-quarters combat since its PPCs have a tougher time connecting with the victim. In that case, it just possesses a light weapon and a left fist to fall back on. Because of its limited mobility, it is vulnerable to flanking attacks from speedier opponents seeking to get past the PPCs. While they face arguably of the heaviest rear armor found on any BattleMech, the Awesome's lack of rear facing armaments or a weapon mount on its left arm has offered numerous MechWarriors a fighting chance. Formations of Awesomes (or even just a few) are incredibly effective and tough to stop or defeat when correctly placed by commanders who are knowledgeable of the AWS's limitations. deployment:This advanced tech variant of the Awesome was introduced during the end of the Jihad in 3079, and uses eight Light PPCs as its main armament. To improve the damage potential of the 'Mech, half of those PPCs are equipped with experimental PPC Capacitors. Technicron engineers were forced to reduce the top speed of the Awesome to that of an 8Q, and to provide the room for two of the Light PPCs, they had to equip the 11M with a heavy Compact Gyro. To offset the heat caused by the eight PPCs and capacitors, the engineers used twenty Clan-spec Double Heat Sinks. diff --git a/megameklab/data/mechfiles/mechs/XTRs/Mercenaries/Annihilator ANH-2AX.mtf b/megameklab/data/mechfiles/mechs/XTRs/Mercenaries/Annihilator ANH-2AX.mtf index 8ef06a6c0..07e7f11e8 100644 --- a/megameklab/data/mechfiles/mechs/XTRs/Mercenaries/Annihilator ANH-2AX.mtf +++ b/megameklab/data/mechfiles/mechs/XTRs/Mercenaries/Annihilator ANH-2AX.mtf @@ -137,7 +137,7 @@ Reflective overview:Originally developed in the final year of the Amaris Civil War as the ultimate fixed position city defense BattleMech. -capabilities:The Annihilator is armed with an arsenal that is built to instill fear in an enemy as much as damage them. The 100-ton 'Mech has a maximum speed of 32.4 km/h, making it one of the slowest 'Mechs ever designed together with the UrbanMech. It is by no means intended to use speed to outmaneuver an enemy, instead depending on its twelve and a half tons of armor to weather any fire that is directed at the 'Mech. +capabilities:The Annihilator is armed with an arsenal that is built to instill fear in an enemy as much as damage them. The 100-ton 'Mech has a maximum speed of 32.4 km/h, making it one of the slowest 'Mechs ever designed together with the UrbanMech. It is by no means intended to use speed to outmaneuver an enemy, instead depending on its twelve and a half tons of armor to weather any fire that is directed at the 'Mech. deployment:Developed by the Arc-Royal MechWorks, the Annihilator-2AX used nineteen tons of Laser Reflective Armor as protection. It also used several Armored Components to increase battlefield longevity (Sensors, Life Support, and Cockpit). The traditional weapons have been removed and replaced by a pair of Improved Heavy Gauss Rifles. CASE was installed in each torso to protect against Gauss rifle explosion. The ammunition for the Gauss rifles was located in the Annihilator's arms. diff --git a/megameklab/data/mechfiles/mechs/XTRs/Mercenaries/Grasshopper GHR-7X.mtf b/megameklab/data/mechfiles/mechs/XTRs/Mercenaries/Grasshopper GHR-7X.mtf index cb41716e6..2b9ecd9c8 100644 --- a/megameklab/data/mechfiles/mechs/XTRs/Mercenaries/Grasshopper GHR-7X.mtf +++ b/megameklab/data/mechfiles/mechs/XTRs/Mercenaries/Grasshopper GHR-7X.mtf @@ -143,7 +143,7 @@ capabilities:With great mobility and a predominately shorter-ranged, energy-base deployment:A Jihad-era experimental prototype developed on Arc-Royal in 3075, this version used a Torso-Mounted Cockpit, Light Engine, and Endo Steel skeleton as the frame to carry six Improved Jump Jets. The standard weaponry is replaced with a head mounted Medium Pulse Laser and a Bombast Laser in each arm. To find its opponents, the head also carries a Bloodhound Active Probe. Even after the refined GHR-7P entered production, ARM still produced a small number of GHR-7X Grasshoppers in response to customer requests, though overall less than ten GHR-7X's were ever manufactured, with the two original prototypes lost on Rochelle. -history:Problems integrating the original stealth systems with the chassis meant the Grasshopper missed the climactic end to the conflict. The stealth systems were ultimately removed from the final design. The untested and unorthodox 'Mech was distributed primarily to the regular army rather than the more prestigious Royal units, and within four years it could be found in most Star League regiments. Thus as the League dissolved, with the chaos of Operation EXODUS and the defection of many SLDF units to the Successor States, Grasshoppers found their way into the various House armies one way or another. Besides hunting down lighter machines to clear the way for heavier, less-mobile 'Mechs, the Grasshopper's mobility and endurance meant it often spearheaded assaults to storm fortifications, led flanking attacks to hit the enemy from the rear, and served as back-up brawler for companies of light and medium 'Mechs. Its ability to operate independently made it an excellent choice as a raider and guerrilla fighter, an attribute also prized by mercenary units in need of self-reliant 'Mechs. While popular the Grasshopper was also an uncommon sight during the Succession Wars, causing many commanders to mistakenly treat it as just another heavy 'Mech. By the time they realized their mistake it was too late, though following ComStar's publication of Technical Readout: 3025 military leaders became more familiar with the 'Mech. In the midst of the Second Succession War the Lantren Corporation's factory on Bryant was destroyed in 2843, a result of worsening global storms and damage inflicted during the conflict, causing production of the 'Mech to cease. However, the Grasshopper was usually prioritized over other 'Mechs, even a unit commander's own, when it came time to repair and rebuild after a battle. Thus most of the original production run was still in active duty even after centuries of use. Lantren Corporation would eventually introduce a new variant in 3049, the GHR-5J, which upgraded many of its original systems with superior lostech components. Yet the original model was so popular that it would still outnumber the -5J for decades to come by a ratio of three to one. Only when the Draconis Combine introduced their own C3 variant that trend began to reverse. Further variants were introduced in the years following, and the Grasshopper participated in many conflicts, including both sides of the Jihad. +history:Problems integrating the original stealth systems with the chassis meant the Grasshopper missed the climactic end to the conflict. The stealth systems were ultimately removed from the final design. The untested and unorthodox 'Mech was distributed primarily to the regular army rather than the more prestigious Royal units, and within four years it could be found in most Star League regiments. Thus as the League dissolved, with the chaos of Operation EXODUS and the defection of many SLDF units to the Successor States, Grasshoppers found their way into the various House armies one way or another. Besides hunting down lighter machines to clear the way for heavier, less-mobile 'Mechs, the Grasshopper's mobility and endurance meant it often spearheaded assaults to storm fortifications, led flanking attacks to hit the enemy from the rear, and served as back-up brawler for companies of light and medium 'Mechs. Its ability to operate independently made it an excellent choice as a raider and guerrilla fighter, an attribute also prized by mercenary units in need of self-reliant 'Mechs. While popular the Grasshopper was also an uncommon sight during the Succession Wars, causing many commanders to mistakenly treat it as just another heavy 'Mech. By the time they realized their mistake it was too late, though following ComStar's publication of Technical Readout: 3025 military leaders became more familiar with the 'Mech. In the midst of the Second Succession War the Lantren Corporation's factory on Bryant was destroyed in 2843, a result of worsening global storms and damage inflicted during the conflict, causing production of the 'Mech to cease. However, the Grasshopper was usually prioritized over other 'Mechs, even a unit commander's own, when it came time to repair and rebuild after a battle. Thus most of the original production run was still in active duty even after centuries of use. Lantren Corporation would eventually introduce a new variant in 3049, the GHR-5J, which upgraded many of its original systems with superior lostech components. Yet the original model was so popular that it would still outnumber the -5J for decades to come by a ratio of three to one. Only when the Draconis Combine introduced their own C3 variant that trend began to reverse. Further variants were introduced in the years following, and the Grasshopper participated in many conflicts, including both sides of the Jihad. manufacturer:Arc-Royal MechWorks (Refit) primaryfactory:Arc-Royal diff --git a/megameklab/data/mechfiles/mechs/XTRs/Mercenaries/Wolfhound WLF-2X.mtf b/megameklab/data/mechfiles/mechs/XTRs/Mercenaries/Wolfhound WLF-2X.mtf index 5ccf7b142..5bf8c9b8f 100644 --- a/megameklab/data/mechfiles/mechs/XTRs/Mercenaries/Wolfhound WLF-2X.mtf +++ b/megameklab/data/mechfiles/mechs/XTRs/Mercenaries/Wolfhound WLF-2X.mtf @@ -162,7 +162,7 @@ capabilities:Archon Katrina Steiner directed TharHes Industries to create a Batt deployment:Developed by Arc-Royal MechWorks' Michael Bodien in the midst of the Jihad, the extensively modified WLF-2X variant utilizes experimental technology. Using an endo steel chassis and an extralight engine to save weight, the 2X's main weapon is a right-arm mounted heavy PPC enhanced by both a PPC capacitor and an Actuator Enhancement System. The torso-mounted weapons remain lasers - specifically, two ER medium lasers and a single ER small laser - while 10 double heat sinks allow it to keep their increased thermal output in check. Enhanced defensive protection comes in the form of supercharger-enhanced speed and cosmetically styled laser reflective armor. -history:The Kell Hounds were the first unit chosen to field-test the Wolfhound in combat because of their intense loyalty to House Steiner, followed shortly after by Wolf's Dragoons. The design was put through its paces during the Fourth Succession War, where it outperformed all expectations. This was especially true when the Wolfhound faced its intended targets, hitting the Jenner beyond its capacity to return fire while closing the distance on the Panther to get inside range of its primary armament. After the war's triumphant conclusion, the Federated Commonwealth purchased more Wolfhounds to outfit its troops, and the design was utilized again during the War of 3039. Wolfhounds sustained substantially fewer deaths than other 'Mechs during that fight, and as a result, only a few were captured by the Combine. While awed by the 'Mech, the Kuritans were too proud to replicate it, instead relying on captured examples to help create the Wolf Trap particularly to defeat the 'Mech. Arc-Royal MechWorks was eventually recruited in to construct Wolfhounds under license from TharHes, and the recovery of lostech owing to the Helm Memory Core allowed for the production of a more advanced model to combat the Clan Invasion. Sadly, it took too long for TharHes' factories to be retooled in order to build the WLF-2 model, which was introduced in 3052, before ComStar ended the invasion with the Battle of Tukayyid. These updated Wolfhounds were still created for both FedCom member states, but once the Lyran Alliance was formed, TharHes manufacturers began creating the newer WLF-3S variant. This new type was only distributed to units loyal to the Lyran state, and so fought on Katherine Steiner-side Davion's during the FedCom Civil War. During the Jihad, the Word of Blake launched a crushing attack on Tharkad, essentially shutting down TharHes' Wolfhound factory line; in response, Arc-Royal expanded production and created the WLF-4 variant to compensate for allied troops combating the Blakists' losses. +history:The Kell Hounds were the first unit chosen to field-test the Wolfhound in combat because of their intense loyalty to House Steiner, followed shortly after by Wolf's Dragoons. The design was put through its paces during the Fourth Succession War, where it outperformed all expectations. This was especially true when the Wolfhound faced its intended targets, hitting the Jenner beyond its capacity to return fire while closing the distance on the Panther to get inside range of its primary armament. After the war's triumphant conclusion, the Federated Commonwealth purchased more Wolfhounds to outfit its troops, and the design was utilized again during the War of 3039. Wolfhounds sustained substantially fewer deaths than other 'Mechs during that fight, and as a result, only a few were captured by the Combine. While awed by the 'Mech, the Kuritans were too proud to replicate it, instead relying on captured examples to help create the Wolf Trap particularly to defeat the 'Mech. Arc-Royal MechWorks was eventually recruited in to construct Wolfhounds under license from TharHes, and the recovery of lostech owing to the Helm Memory Core allowed for the production of a more advanced model to combat the Clan Invasion. Sadly, it took too long for TharHes' factories to be retooled in order to build the WLF-2 model, which was introduced in 3052, before ComStar ended the invasion with the Battle of Tukayyid. These updated Wolfhounds were still created for both FedCom member states, but once the Lyran Alliance was formed, TharHes manufacturers began creating the newer WLF-3S variant. This new type was only distributed to units loyal to the Lyran state, and so fought on Katherine Steiner-Davion's side during the FedCom Civil War. During the Jihad, the Word of Blake launched a crushing attack on Tharkad, essentially shutting down TharHes' Wolfhound factory line; in response, Arc-Royal expanded production and created the WLF-4 variant to compensate for allied troops combating the Blakists' losses. manufacturer:Arc-Royal MechWorks primaryfactory:Arc-Royal diff --git a/megameklab/data/mechfiles/mechs/XTRs/Most Wanted/Black Knight BL-X-KNT 'Red Reaper'.mtf b/megameklab/data/mechfiles/mechs/XTRs/Most Wanted/Black Knight BL-X-KNT 'Red Reaper'.mtf index f3c2c452c..95a69ee4c 100644 --- a/megameklab/data/mechfiles/mechs/XTRs/Most Wanted/Black Knight BL-X-KNT 'Red Reaper'.mtf +++ b/megameklab/data/mechfiles/mechs/XTRs/Most Wanted/Black Knight BL-X-KNT 'Red Reaper'.mtf @@ -159,7 +159,7 @@ IS Light 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 of them 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 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:Based on a BL-9-KNT chassis, this personal ride of Reginald VanJaster was created during the Word of Blake's occupation of Solaris. The standard weaponry was removed and replaced with a Large Shield and Large Vibroblade for hand to hand combat, while five Medium X-Pulse Lasers inflict huge amounts of damage in close quarter combat. For long range firepower, a single Heavy PPC paired with a PPC Capacitor are used. The whole 'Mech is protected by thirteen tons of light ferro-fibrous armor. Fifteen double heat sinks are available to dissipate heat. diff --git a/megameklab/data/mechfiles/mechs/XTRs/Periphery/Atlas AS-700 Jurn.mtf b/megameklab/data/mechfiles/mechs/XTRs/Periphery/Atlas AS-700 Jurn.mtf index e9b543229..aa5579e4d 100644 --- a/megameklab/data/mechfiles/mechs/XTRs/Periphery/Atlas AS-700 Jurn.mtf +++ b/megameklab/data/mechfiles/mechs/XTRs/Periphery/Atlas AS-700 Jurn.mtf @@ -160,7 +160,7 @@ RemoteSensorDispenser overview:"A 'Mech as powerful as possible, as impenetrable as possible, and as ugly and foreboding as conceivable, so that fear itself will be our ally.”-Aleksandr Kerensky -capabilities:The Atlas is probably the best-known BattleMech to ever set foot on the modern battlefield. Designed with specifications from Aleksandr Kerensky himself in 2755 in the midst of the Cameron Edicts, the Atlas was originally intended to ensure SLDF superiority over the Star League member states. Carrying the largest LRM launcher, the largest autocannon, and the largest SRM launcher possible, the Atlas can deal frightening amounts of damage in short amounts of time. Often used as a command vehicle, the Atlas mounts an advanced antenna and communications array, allowing it to engage in surface-to space communications in real time. The massive 19-ton hide of armor that protects the Atlas makes it a difficult foe to take down. Indeed, most MechWarriors choose to fall back rather than face one head-one, as its lumbering gait mean it can rarely catch up to other 'Mechs that choose to flee it. A full year of development went into crafting the famous "Death's Head" of the 'Mech to achieve the perfect ratio of functionality and fear. The head is also quite roomy and allows a small satellite dish to be mounted for surface-to-space communications. During combat the pilot can easily fold up the dish and store it within a protective portion of the head. +capabilities:The Atlas is probably the best-known BattleMech to ever set foot on the modern battlefield. Designed with specifications from Aleksandr Kerensky himself in 2755 in the midst of the Cameron Edicts, the Atlas was originally intended to ensure SLDF superiority over the Star League member states. Carrying the largest LRM launcher, the largest autocannon, and the largest SRM launcher possible, the Atlas can deal frightening amounts of damage in short amounts of time. Often used as a command vehicle, the Atlas mounts an advanced antenna and communications array, allowing it to engage in surface-to-space communications in real time. The massive 19-ton hide of armor that protects the Atlas makes it a difficult foe to take down. Indeed, most MechWarriors choose to fall back rather than face one head-on, as its lumbering gait means it can rarely catch up to other 'Mechs that choose to flee it. A full year of development went into crafting the famous "Death's Head" of the 'Mech to achieve the perfect ratio of functionality and fear. The head is also quite roomy and allows a small satellite dish to be mounted for surface-to-space communications. During combat the pilot can easily fold up the dish and store it within a protective portion of the head. deployment:This version of the Atlas was created by Preceptor Anton Jurn of the Outworlds Alliance. The traditional weaponry has been completely removed from an AS7-K chassis. The Atlas was then equipped with a Hypervelocity AC/10 and Snub Nose PPC in the right torso, while a Thunderbolt 15 launcher occupies the left torso and each arm carries a Light PPC. The ammunition for the AC and Thunderbolt are in a CASE II protected bay in the left torso. Jurn's refit also features a Cockpit Command Console that has been armored. To provide more intelligence to the commander, a Beagle Active Probe is mounted in the center torso, and each leg carries a Remote Sensor Dispenser system. diff --git a/megameklab/data/mechfiles/mechs/XTRs/Pirates/Victor VTR-9K2 St. James.mtf b/megameklab/data/mechfiles/mechs/XTRs/Pirates/Victor VTR-9K2 St. James.mtf index 5bf4922e5..2dacc9f5e 100644 --- a/megameklab/data/mechfiles/mechs/XTRs/Pirates/Victor VTR-9K2 St. James.mtf +++ b/megameklab/data/mechfiles/mechs/XTRs/Pirates/Victor VTR-9K2 St. James.mtf @@ -139,7 +139,7 @@ overview:The Victor was built in 2508 under contract to the Terran Hegemony as a capabilities:Standing at 14 meters tall, the Victor approaches the concept of support in an unorthodox way for a 'Mech of its weight class. While only possessing a ground speed of 64.8 km/h, the Victor achieves a high degree of mobility instead through the use of four jump jets, allowing it to jump up to one hundred and twenty meters. A Victor can therefore "support" friendly units by jumping directly into the fray and bringing its deadly close range arsenal to bear, an ability which can surprise inexperienced MechWarriors and prove advantageous in mountainous terrain. One sacrifice made for this superb mobility is the 'Mech's relatively light armor of only eleven and a half tons, while the lack of proper anti-infantry capabilities is a minor problem. -deployment:fter his son was killed in the Taurian Concordat invasion of the Federated Suns, Benedict St. James had his VTR-9K refitted with experimental weapons and equipment to allow him to take his revenge. Replacing the standard weapons with a Long Tom Cannon and two Medium X-Pulse Lasers, St. James' Victor can inflict massive amounts of damage on his prey. The 'Mech's jump jets had to be removed to make way for the weapons load, and technicians equipped it with a patchwork of Ferro-Fibrous and Standard Armor as another weight saving measure. A Supercharger mounted on the engine provides the Victor with unexpected bursts of speed. +deployment:After his son was killed in the Taurian Concordat invasion of the Federated Suns, Benedict St. James had his VTR-9K refitted with experimental weapons and equipment to allow him to take his revenge. Replacing the standard weapons with a Long Tom Cannon and two Medium X-Pulse Lasers, St. James' Victor can inflict massive amounts of damage on his prey. The 'Mech's jump jets had to be removed to make way for the weapons load, and technicians equipped it with a patchwork of Ferro-Fibrous and Standard Armor as another weight saving measure. A Supercharger mounted on the engine provides the Victor with unexpected bursts of speed. history:An estimated one thousand Victors had been produced by the time the Star League fell. Many of these left with Aleksandr Kerensky during the Exodus, and when HildCo Interplanetary's three Victor factories were destroyed during the First Succession War, the 'Mech became a prized target with all sides scrambling to salvage serviceable units. Only Independence Weaponry retained the ability to build new Victors, and with their capture by the Federated Suns during the Second Succession War it became the AFFS' primary assault 'Mech and a favorite command model for battalion and regimental commanders. Though the Draconis Combine would eventually retake the company following the War of 3039, most Kurita samurai were too proud to adopt a 'Mech now associated with their enemy, while the Davions made do with purchasing new models from the rebuilt HildCo factory in the St. Ives Compact and funding the construction of Styk's Tao MechWorks. By the time of the Clan Invasion new models of Victors were being produced which incorporated new-found lostech into their design. The formation of the Second Star League and destruction of Clan Smoke Jaguar would finally win the design acceptance by Combine warriors, while the conquest of Styk and St. Ives by the Capellan Confederation forced the Federated Commonwealth to contract General Motors to build more Victors. Though it had officially fallen out of favor, during the FedCom Civil War the Victor remained the favorite of Allied forces, with newer variants seeing use in the years afterwards diff --git a/megameklab/data/mechfiles/mechs/XTRs/Primitives III/Longbow LGB-0C.mtf b/megameklab/data/mechfiles/mechs/XTRs/Primitives III/Longbow LGB-0C.mtf index 0d457c9d8..a17b1416f 100644 --- a/megameklab/data/mechfiles/mechs/XTRs/Primitives III/Longbow LGB-0C.mtf +++ b/megameklab/data/mechfiles/mechs/XTRs/Primitives III/Longbow LGB-0C.mtf @@ -169,7 +169,7 @@ overview:The Longbow, introduced in 2480 as the LGB-0C Longbow, has seen service capabilities:The Longbow is a massive BattleMech weighing in at 85 tons and is able to move at a top speed of 54.0 km/h, thanks to a Strand 255 fusion engine. The Longbow is protected by fourteen and a half tons of armor. Some have criticized the design for its lack of CASE - making an otherwise rugged 'Mech vulnerable to a loss by an ammunition explosion. As a fire-support 'Mech though, the Longbow is a trusted and reliable machine that can be counted on to carry out the mission it is designed for. -deployment:The original Longbow built in 2480, this Free Worlds League design carried twin LRM-20s each with three tons of ammunition, supported by two Medium Lasers and a Small Laser. The Primitive Technology used limited the design's top speed to 54km/h, but this was deemed acceptable for a fire support unit. The location of the LRM launchers in the arms allowed it to fire in a wider arc, a feature prized by pilots. The Primitive Armor provided some protection, but many felt it was too thin. This design would go on to become one of the most popular and widely distributed as the manufacturer, Lockenburg-Holly Industries, merged with several other manufacturers to form StarCorps Industries.[2] +deployment:The original Longbow built in 2480, this Free Worlds League design carried twin LRM-20s each with three tons of ammunition, supported by two Medium Lasers and a Small Laser. The Primitive Technology used limited the design's top speed to 54km/h, but this was deemed acceptable for a fire support unit. The location of the LRM launchers in the arms allowed it to fire in a wider arc, a feature prized by pilots. The Primitive Armor provided some protection, but many felt it was too thin. This design would go on to become one of the most popular and widely distributed as the manufacturer, Lockenburg-Holly Industries, merged with several other manufacturers to form StarCorps Industries. manufacturer:Lockenburg-Holly Industries primaryfactory:Emris IV diff --git a/megameklab/data/mechfiles/mechs/XTRs/Primitives IV/Griffin GRF-1A.mtf b/megameklab/data/mechfiles/mechs/XTRs/Primitives IV/Griffin GRF-1A.mtf index 1b4a3a756..e2f3a5261 100644 --- a/megameklab/data/mechfiles/mechs/XTRs/Primitives IV/Griffin GRF-1A.mtf +++ b/megameklab/data/mechfiles/mechs/XTRs/Primitives IV/Griffin GRF-1A.mtf @@ -163,7 +163,7 @@ capabilities:The massive and efficient fusion engine of the Griffin, giving it a deployment:The original Griffin produced by Maxwell Manufacturing, Inc. weighed sixty tons (thus technically falling into the Heavy category of BattleMechs) and used primitive components. It could reach a top speed of 64 km/h and cover ninety meters with Prototype Jump Jets. It also carried a Prototype PPC and a single LRM-5 with a ton of ammunition. It was protected by fourteen and a half tons of Primitive Armor and equipped with eleven single heat sinks. A Primitive Cockpit was provided for the pilot -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.[5] 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. +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. manufacturer:Gienah BattleMechs Ltd.,Taurus Territorial Industries,Maxwell Manufacturing, Inc primaryfactory:Gienah,Jansen's Hold,Procyon diff --git a/megameklab/data/mechfiles/mechs/XTRs/Primitives V/Archer ARC-1A.mtf b/megameklab/data/mechfiles/mechs/XTRs/Primitives V/Archer ARC-1A.mtf index 868894872..c133177ec 100644 --- a/megameklab/data/mechfiles/mechs/XTRs/Primitives V/Archer ARC-1A.mtf +++ b/megameklab/data/mechfiles/mechs/XTRs/Primitives V/Archer ARC-1A.mtf @@ -166,7 +166,7 @@ Foot Actuator overview:One of the most iconic BattleMechs is the Archer, with its low-slung torso, enormous fists, and missile-bay covers. The Archer was first manufactured in 2474 for heavy-hitting, long-range brawling, and fire-support. -capabilities:Two enormous missile launchers with tons of ammo power the Archer. The missiles were formidable, but their short-range inaccuracy required four medium lasers, two rear-facing and one in each arm. Enlarged hand actuators allow the design to undertake severe physical attacks and transport captured supplies during raids. The cockpit of the Archer situated beneath the center midsection, giving the pilot a unique battlefield view. The torso armor belt above the cockpit protects the gyro and engine from the superior armor. Many pilots initially entered battle with their missile bays locked to hide the 'Mech's real capabilities, leading some to believe it was a close-combat design. As the Archer became famous, this pretext became meaningless. Archer pilots rarely learn new skills, but this hasn't tarnished the 'Mech's reputation. +capabilities:Two enormous missile launchers with tons of ammo power the Archer. The missiles were formidable, but their short-range inaccuracy required four medium lasers, two rear-facing and one in each arm. Enlarged hand actuators allow the design to undertake severe physical attacks and transport captured supplies during raids. The cockpit of the Archer is situated beneath the center midsection, giving the pilot a unique battlefield view. The torso armor belt above the cockpit protects the gyro and engine from the superior armor. Many pilots initially entered battle with their missile bays locked to hide the 'Mech's real capabilities, leading some to believe it was a close-combat design. As the Archer became famous, this pretext became meaningless. Archer pilots rarely learn new skills, but this hasn't tarnished the 'Mech's reputation. deployment:The original Archer prototype built for the Terran Hegemony in 2458 with Primitive Technology. It was slower than the successor ARC-2R variant with a top speed of 54 km/h with the inclusion of a 255-rated primitive engine. Its loadout was somewhat similar, with the frame housing a pair of LRM-20s and 4 tons of ammunition, but only mounted two medium lasers, one in each fully articulated arm for close-in defense. The inclusion of large armored access panels in the 'Mech's rear made reloading the limited ammunition stores easier. It was also protected by 16 tons of Primitive Armor. At the time, it was praised for its reliability and ease of maintenance, although in combat produced far more excess heat than the machine could handle if all weapons were fired - a similar issue carried over to the later Archer. diff --git a/megameklab/data/mechfiles/mechs/XTRs/Primitives V/Wolverine WVR-1R.mtf b/megameklab/data/mechfiles/mechs/XTRs/Primitives V/Wolverine WVR-1R.mtf index 96274a254..e08f1f8cb 100644 --- a/megameklab/data/mechfiles/mechs/XTRs/Primitives V/Wolverine WVR-1R.mtf +++ b/megameklab/data/mechfiles/mechs/XTRs/Primitives V/Wolverine WVR-1R.mtf @@ -164,7 +164,7 @@ capabilities:The autocannon, missile system and laser found on most Wolverines a deployment:Infamously nicknamed the "Varnay-1R", the original primitive Wolverine was introduced in 2471. It mounted an Autocannon/5 with 2 tons of ammunition in the right arm and a Medium Laser in the left to provide coverage in the "weak zone" sixty-meters inside the main gun's reach. A 265 Primitive Engine gave the 'Mech a top speed of 64 km/h with four Prototype jump jets providing enhanced mobility for a total jumping distance of 120 meters. The design was also heavily protected by 14.5 tons of armor -history:A widespread part of every major military, the Wolverine has manufacturing plants scattered throughout the entire Inner Sphere. While certain states-notable the Free Worlds League-have larger numbers of the design, only the Capellans began facing a shortage of the Wolverine after the loss of their Nanking facilities. +history:A widespread part of every major military, the Wolverine has manufacturing plants scattered throughout the entire Inner Sphere. While certain states-notably the Free Worlds League-have larger numbers of the design, only the Capellans began facing a shortage of the Wolverine after the loss of their Nanking facilities. manufacturer:Bordello Military Goods, Inc.,Nimakachi Fusion Products Limited,Norse BattleMech Works,McRae Quik Construct,Pesht Motors,Asuncion Industries primaryfactory:Antwerp,Lesnovo,Marduk,New Ivaarsen,Pesht,Sarna diff --git a/megameklab/data/mechfiles/mechs/XTRs/Primitives V/Wolverine WVR-3R.mtf b/megameklab/data/mechfiles/mechs/XTRs/Primitives V/Wolverine WVR-3R.mtf index 98f1a8472..8a2012727 100644 --- a/megameklab/data/mechfiles/mechs/XTRs/Primitives V/Wolverine WVR-3R.mtf +++ b/megameklab/data/mechfiles/mechs/XTRs/Primitives V/Wolverine WVR-3R.mtf @@ -168,7 +168,7 @@ capabilities:The autocannon, missile system and laser found on most Wolverines a deployment:Entering production in 2490, the primitive 3R was built in response to the Terran Hegemony creating new versions of the 'Mechs the Wolverine was originally based on. It traded in 3 tons of armor and a ton of autocannon ammunition for a shoulder-mounted six-pack SRM launcher with one ton of reloads - a loadout that would remain essentially unchanged for the later "modernized" 6R. -history:A widespread part of every major military, the Wolverine has manufacturing plants scattered throughout the entire Inner Sphere. While certain states-notable the Free Worlds League-have larger numbers of the design, only the Capellans began facing a shortage of the Wolverine after the loss of their Nanking facilities. +history:A widespread part of every major military, the Wolverine has manufacturing plants scattered throughout the entire Inner Sphere. While certain states-notably the Free Worlds League-have larger numbers of the design, only the Capellans began facing a shortage of the Wolverine after the loss of their Nanking facilities. manufacturer:Norse BattleMech Works primaryfactory:Marduk diff --git a/megameklab/data/mechfiles/mechs/XTRs/Republic I/Hatchetman HCT-7R.mtf b/megameklab/data/mechfiles/mechs/XTRs/Republic I/Hatchetman HCT-7R.mtf index cd65ca432..70c39b0c5 100644 --- a/megameklab/data/mechfiles/mechs/XTRs/Republic I/Hatchetman HCT-7R.mtf +++ b/megameklab/data/mechfiles/mechs/XTRs/Republic I/Hatchetman HCT-7R.mtf @@ -164,7 +164,7 @@ capabilities:As well as being the first design to carry one, the Hatchetman itse deployment:Developed for The Republic of the Sphere after the Capellan Crusades, this Hatchetman uses a Light Engine to develop a maximum ground speed of 85 km/h. It also has a jump range of 150 meters and is protected by eight and a half tons of Ferro-Fibrous Armor. Twelve double heat sinks are also installed, which dissipates the extreme heat from the single Medium X-Pulse Laser and six standard Medium Lasers mounted in the right arm. The left arm has the trademark hatchet. What makes this version so deadly is the fact that each arm has an Actuator Enhancement System, which improves targeting. -history:s well as being the first design to carry one, the Hatchetman itself was the first totally new 'Mech produced in the Inner Sphere in over a century, and was also the first production 'Mech to use a Full-Head Ejection System. Despite being first manufactured in the Lyran Commonwealth the Hatchetman was actually designed by the enigmatic Dr. B. Banzai of Team Banzai, a mercenary unit associated with the Federated Suns' New Avalon Institute of Science. Thus the 'Mech was also a signal of the growing cooperation between these newly-allied Successor States. in the design's first combat test, when elements of the 4th Proserpina Hussars raided Sevren and were literally cut to pieces by a mostly Hatchetman-equipped battalion of the 26th Lyran Guards which lured the enemy into an industrial park. Where the Hatchetman is at a disadvantage is on open terrain, as its relatively slow speed, light armoring and general frailty leaves it vulnerable to other 'Mechs. Initially the Hatchetman's first production run was limited to garrisoning large Lyran cities, but its early successes inspired further deployments and the 'Mech soon began appearing in the arsenal of the Federated Suns, particularly among the Crucis Lancers and 1st Kathil Uhlans. In the wake of the Fourth Succession War and the formal creation of the Federated Commonwealth, the Hatchetman was selected to become one of the standard designs for the Armed Forces of the Federated Commonwealth. Demand for the 'Mech soon began to outstrip Defiance Industries' ability to supply it, even after tripling output from their Hesperus II factory, and so it contracted Johnston Industries to set up a Hatchetman line on Johnston. The recovery of lost Star League technology eventually allowed for the creation of the HCT-5S in 3049, with additional variants created in years hence. Among the other realms, the Draconis Combine managed to capture a few examples of the Hatchetman and successfully copy most of the design to produce their own following the War of 3039, however the 'Mech proved to be unpopular and the program was canceled. Hoping to salvage the project, Independence Weaponry experimented with the design and eventually created a variant more palatable to Kuritan pilots. Out in the Periphery, the introduction of the Hatchetman caused quite a stir within the Taurian Concordat when a group of mercenaries brought along their old HCT-3Fs upon integrating with the Taurian Defense Forces. Protector of the Realm Thomas Calderon ordered Taurus Territorial Industries to reverse-engineer the design, which they finally succeeded in accomplishing after much delay by 3054, only for production to be halted in 3066 when the Fighting Urukhai destroyed the Taurus Territorial Industries facility. +history:As well as being the first design to carry one, the Hatchetman itself was the first totally new 'Mech produced in the Inner Sphere in over a century, and was also the first production 'Mech to use a Full-Head Ejection System. Despite being first manufactured in the Lyran Commonwealth the Hatchetman was actually designed by the enigmatic Dr. B. Banzai of Team Banzai, a mercenary unit associated with the Federated Suns' New Avalon Institute of Science. Thus the 'Mech was also a signal of the growing cooperation between these newly-allied Successor States. In the design's first combat test, elements of the 4th Proserpina Hussars raided Sevren and were literally cut to pieces by a mostly Hatchetman-equipped battalion of the 26th Lyran Guards which lured the enemy into an industrial park. Where the Hatchetman is at a disadvantage is on open terrain, as its relatively slow speed, light armoring and general frailty leaves it vulnerable to other 'Mechs. Initially the Hatchetman's first production run was limited to garrisoning large Lyran cities, but its early successes inspired further deployments and the 'Mech soon began appearing in the arsenal of the Federated Suns, particularly among the Crucis Lancers and 1st Kathil Uhlans. In the wake of the Fourth Succession War and the formal creation of the Federated Commonwealth, the Hatchetman was selected to become one of the standard designs for the Armed Forces of the Federated Commonwealth. Demand for the 'Mech soon began to outstrip Defiance Industries' ability to supply it, even after tripling output from their Hesperus II factory, and so it contracted Johnston Industries to set up a Hatchetman line on Johnston. The recovery of lost Star League technology eventually allowed for the creation of the HCT-5S in 3049, with additional variants created in years hence. Among the other realms, the Draconis Combine managed to capture a few examples of the Hatchetman and successfully copy most of the design to produce their own following the War of 3039, however the 'Mech proved to be unpopular and the program was canceled. Hoping to salvage the project, Independence Weaponry experimented with the design and eventually created a variant more palatable to Kuritan pilots. Out in the Periphery, the introduction of the Hatchetman caused quite a stir within the Taurian Concordat when a group of mercenaries brought along their old HCT-3Fs upon integrating with the Taurian Defense Forces. Protector of the Realm Thomas Calderon ordered Taurus Territorial Industries to reverse-engineer the design, which they finally succeeded in accomplishing after much delay by 3054, only for production to be halted in 3066 when the Fighting Urukhai destroyed the Taurus Territorial Industries facility. manufacturer:Johnston Industries primaryfactory:Addicks diff --git a/megameklab/data/mechfiles/mechs/XTRs/Republic II/Awesome AWS-11R.mtf b/megameklab/data/mechfiles/mechs/XTRs/Republic II/Awesome AWS-11R.mtf index 312651216..5e414baa4 100644 --- a/megameklab/data/mechfiles/mechs/XTRs/Republic II/Awesome AWS-11R.mtf +++ b/megameklab/data/mechfiles/mechs/XTRs/Republic II/Awesome AWS-11R.mtf @@ -160,7 +160,7 @@ IS Stealth overview:The Awesome was designed in 2665 for the Star League by the Technicron Conglomorate and was based on the aging STR-2C Striker. While not as fast as its forefather, the Awesome is a strong assault 'Mech. -capabilities:The Awesome's abilities are nearly entirely dependent on its particle projection cannons. The AWS can withstand a severe and consistent onslaught from its weaponry thanks to several heat sinks. With one and a half tons more armor than the Striker, the AWS is more protected than even the BattleMaster. The Amazing, like any other BattleMech, has weaknesses. While it is lethal at range, it is less effective in close-quarters combat since its PPCs have a tougher time connecting with the victim. In that case, it just possesses a light weapon and a left fist to fall back on. Because of its limited mobility, it is vulnerable to flanking attacks from speedier opponents seeking to get past the PPCs. While they face arguably of the heaviest rear armor found on any BattleMech, the Awesome's lack of rear facing armaments or a weapon mount on its left arm has offered numerous MechWarriors a fighting chance. Formations of Awesomes (or even just a few) are incredibly effective and tough to stop or defeat when correctly placed by commanders who are knowledgeable of the AWS's limitations. +capabilities:The Awesome's abilities are nearly entirely dependent on its particle projection cannons. The AWS can withstand a severe and consistent onslaught from its weaponry thanks to several heat sinks. With one and a half tons more armor than the Striker, the AWS is more protected than even the BattleMaster. The Awesome, like any other BattleMech, has weaknesses. While it is lethal at range, it is less effective in close-quarters combat since its PPCs have a tougher time connecting with the victim. In that case, it just possesses a light weapon and a left fist to fall back on. Because of its limited mobility, it is vulnerable to flanking attacks from speedier opponents seeking to get past the PPCs. While they face arguably of the heaviest rear armor found on any BattleMech, the Awesome's lack of rear facing armaments or a weapon mount on its left arm has offered numerous MechWarriors a fighting chance. Formations of Awesomes (or even just a few) are incredibly effective and tough to stop or defeat when correctly placed by commanders who are knowledgeable of the AWS's limitations. deployment:Developed in 3133 this Awesome variant is protected by thirteen tons of Stealth Armor and a Guardian ECM Suite. The weaponry has been replaced with a Light Gauss Rifle, LRM-15, Extended LRM-15, and a single ER medium laser. The ammunition and Gauss rifle are protected by CASE II systems. For emergency use, a single Coolant Pod can supplement the ten double strength heat sinks. A Compact Gyro freed enough room in the center torso to store three tons of ELRM ammunition. A 240 XL engine provides a top speed of 54 km/h, but this is supplemented by a Supercharger which allows for bursts of speed up to 64 km/h. diff --git a/megameklab/data/mechfiles/mechs/XTRs/Republic II/UrbanMech UM-R93.mtf b/megameklab/data/mechfiles/mechs/XTRs/Republic II/UrbanMech UM-R93.mtf index f910aebc7..9ae1e3115 100644 --- a/megameklab/data/mechfiles/mechs/XTRs/Republic II/UrbanMech UM-R93.mtf +++ b/megameklab/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 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. manufacturer:Hellespont Industrials primaryfactory:Betelgeuse systemmanufacturer:CHASSIS:Republic-R diff --git a/megameklab/data/mechfiles/mechs/XTRs/Succession Wars/Zeus ZEU-6Y.mtf b/megameklab/data/mechfiles/mechs/XTRs/Succession Wars/Zeus ZEU-6Y.mtf index aa0f678fc..06d25efe0 100644 --- a/megameklab/data/mechfiles/mechs/XTRs/Succession Wars/Zeus ZEU-6Y.mtf +++ b/megameklab/data/mechfiles/mechs/XTRs/Succession Wars/Zeus ZEU-6Y.mtf @@ -157,7 +157,7 @@ Foot Actuator overview:The Zeus was first built by the Lyran Commonwealth in 2787, just as the First Succession War began. Built at the request of Lyran Commonwealth Armed Forces commanders for a new light-assault 'Mech designed to engage the enemy at long range and perform hit-and-run attacks. -capabilities:the Zeus is fast enough to keep up with most heavy 'Mechs, and with a sturdy frame, eleven and a half tons of standard armor and a versatile weapons array, is equally capable of defeating them. Its use of reliable, low-maintenance and easily modified systems at a time when most 'Mechs were built with cutting-edge technology also proved fortuitous, allowing the Zeus to be produced long after those advanced components had become Lostech. +capabilities:The Zeus is fast enough to keep up with most heavy 'Mechs, and with a sturdy frame, eleven and a half tons of standard armor and a versatile weapons array, is equally capable of defeating them. Its use of reliable, low-maintenance and easily modified systems at a time when most 'Mechs were built with cutting-edge technology also proved fortuitous, allowing the Zeus to be produced long after those advanced components had become Lostech. deployment:Prototyped in 2922 as an experiment in logistical support, the 6Y kept the AC/5 in the right arm, but replaced the LRM-15 with a single LRM-10 launcher and a single Binary Laser Cannon was installed in place of the large laser. The missile downgrade was an attempt to alleviate the one problem in the Zeus' otherwise headache-free design, and indeed field refits had shown that the ten-tube launchers were easily adaptable. The addition of the little-loved binary cannon was a combination of two factors: fears that the slow-to-produce Thunderbolt laser was becoming Lostech and an attempt to give the Zeus a long-ranged and powerful energy weapon minus the side effects caused by its original PPC weapon. Unfortunately the heat produced from this weapon caused catastrophic failures in the surrounding myomer bundles. Engineers attempted to redesign the left torso to better dissipate heat, and eventually resorted to placing the cannon on an over-shoulder mount in the right torso, but in the end they couldn't solve the problem. Defiance went on to produce this variant in limited numbers before abandoning the project. diff --git a/megameklab/data/mechfiles/name_changes.txt b/megameklab/data/mechfiles/name_changes.txt index 0ac7a5653..8aa80346b 100644 --- a/megameklab/data/mechfiles/name_changes.txt +++ b/megameklab/data/mechfiles/name_changes.txt @@ -13,6 +13,8 @@ Persepolis 2 (Standard)|Persepolis 2 MechBuster|Mechbuster SeaBuster Early Strike Fighter (Standard)|Seabuster Strike Fighter (Early) +Mengqin MNG-8L|Mĕngqín MNG-8L +Yun Y-2|Yùn Y-2 #Battle Armor Achileus Light Battle Armor (WoB) [David]|Achileus Light Battle Armor [David](Sqd6) @@ -58,6 +60,9 @@ Cavalier Battle Armor [SRM]|Cavalier Battle Armor [SRM](Sqd4) Centaur Battle Armor (Standard)|Centaur Battle Armor (Sqd4) Clan Interface Armor (Standard)|Clan Interface Armor (Sqd1) Clan Medium Battle Armor (Bär)|Clan Medium Battle Armor (Naval) 'Bar' (Sqd5) +Clan Medium Battle Armor (Naval) 'Bar' (Sqd4)|Clan Medium Battle Armor (Naval) 'Bär' (Sqd4) +Clan Medium Battle Armor (Naval) 'Bar' (Sqd5)|Clan Medium Battle Armor (Naval) 'Bär' (Sqd5) +Clan Medium Battle Armor (Naval) 'Bar' (Sqd6)|Clan Medium Battle Armor (Naval) 'Bär' (Sqd6) Clan Medium Battle Armor (Rabid)|Clan Medium Battle Armor (Rabid)(Sqd5) Clan Medium Battle Armor (Rache)|Clan Medium Battle Armor (Rache)(Sqd5) Clan Medium Battle Armor (Volk)|Clan Medium Battle Armor (Laser) 'Volk' (Sqd5) @@ -551,21 +556,21 @@ Tramp JumpShip (Standard)|Tramp JumpShip (2754) Tramp JumpShip (Lithium-Fusion)|Tramp JumpShip (3071) #Mechs +Adder (Puma) A|Puma (Adder) A +Adder (Puma) B|Puma (Adder) B +Adder (Puma) C|Puma (Adder) C +Adder (Puma) D|Puma (Adder) D +Adder (Puma) Prime|Puma (Adder) Prime +Alfar AL-D1 'Dokkalfar'|Alfar AL-D1 'Dökkálfar' +Arana ARA-S-1 MilitiaMech|Araña ARA-S-1 MilitiaMech +Arctic Cheetah (Hankyu) A|Hankyu (Arctic Cheetah) A +Arctic Cheetah (Hankyu) B|Hankyu (Arctic Cheetah) B +Arctic Cheetah (Hankyu) C|Hankyu (Arctic Cheetah) C +Arctic Cheetah (Hankyu) D|Hankyu (Arctic Cheetah) D +Arctic Cheetah (Hankyu) Prime|Hankyu (Arctic Cheetah) Prime Atlas AS7-D(C)|Atlas C -Stone Rhino (Behemoth)|Behemoth (Stone Rhino) (Standard) -Stone Rhino (Behemoth) 4|Behemoth (Stone Rhino) 4 -Stone Rhino (Behemoth) 5|Behemoth (Stone Rhino) 5 -Stone Rhino (Behemoth) 6|Behemoth (Stone Rhino) 6 -Nova (Black Hawk) A|Black Hawk (Nova) A -Nova (Black Hawk) B|Black Hawk (Nova) B -Nova (Black Hawk) C|Black Hawk (Nova) C -Nova (Black Hawk) D|Black Hawk (Nova) D -Nova (Black Hawk) Prime|Black Hawk (Nova) Prime -Nova (Black Hawk) S|Black Hawk (Nova) S Black Hawk 2|Black Hawk (Standard) 2 Black Hawk 3|Black Hawk (Standard) 3 - -Blood Asp Prime|Star Adder (Blood Asp) Prime Blood Asp A|Star Adder (Blood Asp) A Blood Asp B|Star Adder (Blood Asp) B Blood Asp C|Star Adder (Blood Asp) C @@ -574,54 +579,60 @@ Blood Asp E|Star Adder (Blood Asp) E Blood Asp F|Star Adder (Blood Asp) F Blood Asp G|Star Adder (Blood Asp) G Blood Asp I|Star Adder (Blood Asp) I +Blood Asp Prime|Star Adder (Blood Asp) Prime Blood Asp T|Star Adder (Blood Asp) T - -Ebon Jaguar (Cauldron-Born) A|Cauldron-Born (Ebon Jaguar) A -Ebon Jaguar (Cauldron-Born) B|Cauldron-Born (Ebon Jaguar) B -Ebon Jaguar (Cauldron-Born) C|Cauldron-Born (Ebon Jaguar) C -Ebon Jaguar (Cauldron-Born) Prime|Cauldron-Born (Ebon Jaguar) Prime +Conjurer (Hellhound) 2|Hellhound (Conjurer) 2 +Conjurer (Hellhound)|Hellhound (Conjurer) Dire Wolf (Daishi) A|Daishi (Dire Wolf) A Dire Wolf (Daishi) B|Daishi (Dire Wolf) B Dire Wolf (Daishi) Prime|Daishi (Dire Wolf) Prime Dire Wolf (Daishi) S|Daishi (Dire Wolf) S Dire Wolf (Daishi) W|Daishi (Dire Wolf) W +Ebon Jaguar (Cauldron-Born) A|Cauldron-Born (Ebon Jaguar) A +Ebon Jaguar (Cauldron-Born) B|Cauldron-Born (Ebon Jaguar) B +Ebon Jaguar (Cauldron-Born) C|Cauldron-Born (Ebon Jaguar) C +Ebon Jaguar (Cauldron-Born) Prime|Cauldron-Born (Ebon Jaguar) Prime +Executioner (Gladiator) A|Gladiator (Executioner) A +Executioner (Gladiator) B|Gladiator (Executioner) B +Executioner (Gladiator) C|Gladiator (Executioner) C +Executioner (Gladiator) D|Gladiator (Executioner) D +Executioner (Gladiator) Prime|Gladiator (Executioner) Prime Fire Moth (Dasher) A|Dasher (Fire Moth) A Fire Moth (Dasher) B|Dasher (Fire Moth) B Fire Moth (Dasher) C|Dasher (Fire Moth) C Fire Moth (Dasher) D|Dasher (Fire Moth) D Fire Moth (Dasher) Prime|Dasher (Fire Moth) Prime -Viper (Dragonfly) A|Dragonfly (Viper) A -Viper (Dragonfly) B|Dragonfly (Viper) B -Viper (Dragonfly) C|Dragonfly (Viper) C -Viper (Dragonfly) D|Dragonfly (Viper) D -Viper (Dragonfly) Prime|Dragonfly (Viper) Prime +Gargoyle (Man O' War) A|Man O' War (Gargoyle) A +Gargoyle (Man O' War) B|Man O' War (Gargoyle) B +Gargoyle (Man O' War) C|Man O' War (Gargoyle) C +Gargoyle (Man O' War) D|Man O' War (Gargoyle) D +Gargoyle (Man O' War) Prime|Man O' War (Gargoyle) Prime +Gotterdammerung GTD-20C|Götterdämmerung GTD-20C +Gotterdammerung GTD-20S|Götterdämmerung GTD-20S +Gotterdammerung GTD-30S|Götterdämmerung GTD-30S +Gun GN-2O|Gùn GN-2O +Gun GN-2OA|Gùn GN-2OA +Gun GN-2OB|Gùn GN-2OB +Hellbringer (Loki) A|Loki (Hellbringer) A +Hellbringer (Loki) B|Loki (Hellbringer) B +Hellbringer (Loki) Prime|Loki (Hellbringer) Prime +Hellhound (Conjurer) (Standard)|Conjurer (Hellhound) +Hellhound (Conjurer) (Standard)|Hellhound (Conjurer) +Horned Owl (Peregrine) 2|Peregrine (Horned Owl) 2 +Horned Owl (Peregrine)|Peregrine (Horned Owl) +Hunchback IIC (Standard)|Hunchback IIC +Huntsman (Nobori-nin) A|Nobori-nin (Huntsman) A +Huntsman (Nobori-nin) B|Nobori-nin (Huntsman) B +Huntsman (Nobori-nin) C|Nobori-nin (Huntsman) C +Huntsman (Nobori-nin) Prime|Nobori-nin (Huntsman) Prime Ice Ferret (Fenris) A|Fenris (Ice Ferret) A Ice Ferret (Fenris) B|Fenris (Ice Ferret) B Ice Ferret (Fenris) C|Fenris (Ice Ferret) C Ice Ferret (Fenris) D|Fenris (Ice Ferret) D Ice Ferret (Fenris) Prime|Fenris (Ice Ferret) Prime -Executioner (Gladiator) A|Gladiator (Executioner) A -Executioner (Gladiator) B|Gladiator (Executioner) B -Executioner (Gladiator) C|Gladiator (Executioner) C -Executioner (Gladiator) D|Gladiator (Executioner) D -Executioner (Gladiator) Prime|Gladiator (Executioner) Prime -Vapor Eagle (Goshawk)|Goshawk (Vapor Eagle) -Vapor Eagle (Goshawk) 2|Goshawk (Vapor Eagle) 2 -Mongrel (Grendel) A|Grendel (Mongrel) A -Mongrel (Grendel) B|Grendel (Mongrel) B -Mongrel (Grendel) C|Grendel (Mongrel) C -Mongrel (Grendel) D|Grendel (Mongrel) D -Mongrel (Grendel) Prime|Grendel (Mongrel) Prime -Arctic Cheetah (Hankyu) A|Hankyu (Arctic Cheetah) A -Arctic Cheetah (Hankyu) B|Hankyu (Arctic Cheetah) B -Arctic Cheetah (Hankyu) C|Hankyu (Arctic Cheetah) C -Arctic Cheetah (Hankyu) D|Hankyu (Arctic Cheetah) D -Arctic Cheetah (Hankyu) Prime|Hankyu (Arctic Cheetah) Prime -Hellhound (Conjurer) (Standard)|Conjurer (Hellhound) -Conjurer (Hellhound)|Hellhound (Conjurer) -Hellhound (Conjurer) (Standard)|Hellhound (Conjurer) -Conjurer (Hellhound) 2|Hellhound (Conjurer) 2 -Hunchback IIC (Standard)|Hunchback IIC +Incubus (Vixen) 2|Vixen (Incubus) 2 +Incubus (Vixen) 3|Vixen (Incubus) 3 +Incubus (Vixen)|Vixen (Incubus) Iron Cheetah A-NA|Iron Cheetah A Iron Cheetah B-NA|Iron Cheetah B Iron Cheetah C-NA|Iron Cheetah C @@ -629,83 +640,82 @@ Iron Cheetah D-NA|Iron Cheetah D Iron Cheetah F-NA|Iron Cheetah L Iron Cheetah Prime-NA|Iron Cheetah Prime Jagermech JM6-DG|JagerMech JM6-DG +Kit Fox (Uller) A|Uller (Kit Fox) A +Kit Fox (Uller) B|Uller (Kit Fox) B +Kit Fox (Uller) C|Uller (Kit Fox) C +Kit Fox (Uller) D|Uller (Kit Fox) D +Kit Fox (Uller) Prime|Uller (Kit Fox) Prime +Kit Fox (Uller) S|Uller (Kit Fox) S Kodiak (Standard)|Kodiak +Koshi 2|Koshi (Standard) 2 +Koshi 3|Koshi (Standard) 3 +Mad Cat III 3 (Eve)|Mad Cat III (Eve) +Mad Dog (Vulture) A|Vulture (Mad Dog) A +Mad Dog (Vulture) B|Vulture (Mad Dog) B +Mad Dog (Vulture) C|Vulture (Mad Dog) C +Mad Dog (Vulture) Prime|Vulture (Mad Dog) Prime +Marauder IIC (Standard)|Marauder IIC Mist Lynx (Koshi) A|Koshi (Mist Lynx) A Mist Lynx (Koshi) B|Koshi (Mist Lynx) B Mist Lynx (Koshi) C|Koshi (Mist Lynx) C Mist Lynx (Koshi) D|Koshi (Mist Lynx) D Mist Lynx (Koshi) Prime|Koshi (Mist Lynx) Prime -Koshi 2|Koshi (Standard) 2 -Koshi 3|Koshi (Standard) 3 -Hellbringer (Loki) A|Loki (Hellbringer) A -Hellbringer (Loki) B|Loki (Hellbringer) B -Hellbringer (Loki) Prime|Loki (Hellbringer) Prime -Timber Wolf (Mad Cat) A|Mad Cat (Timber Wolf) A -Timber Wolf (Mad Cat) B|Mad Cat (Timber Wolf) B -Timber WOlf (Mad Cat) C|Mad Cat (Timber Wolf) C -Timber Wolf (Mad Cat) D|Mad Cat (Timber Wolf) D -Timber Wolf (Mad Cat) Prime|Mad Cat (Timber Wolf) Prime -Timber Wolf (Mad Cat) S|Mad Cat (Timber Wolf) S -Mad Cat III 3 (Eve)|Mad Cat III (Eve) -Gargoyle (Man O' War) A|Man O' War (Gargoyle) A -Gargoyle (Man O' War) B|Man O' War (Gargoyle) B -Gargoyle (Man O' War) C|Man O' War (Gargoyle) C -Gargoyle (Man O' War) D|Man O' War (Gargoyle) D -Gargoyle (Man O' War) Prime|Man O' War (Gargoyle) Prime -Marauder IIC (Standard)|Marauder IIC -Warhawk (Masakari) A|Masakari (Warhawk) A -Warhawk (Masakari) B|Masakari (Warhawk) B -Warhawk (Masakari) C|Masakari (Warhawk) C -Warhawk (Masakari) Prime|Masakari (Warhawk) Prime -Huntsman (Nobori-nin) A|Nobori-nin (Huntsman) A -Huntsman (Nobori-nin) B|Nobori-nin (Huntsman) B -Huntsman (Nobori-nin) C|Nobori-nin (Huntsman) C -Huntsman (Nobori-nin) Prime|Nobori-nin (Huntsman) Prime +Mongrel (Grendel) A|Grendel (Mongrel) A +Mongrel (Grendel) B|Grendel (Mongrel) B +Mongrel (Grendel) C|Grendel (Mongrel) C +Mongrel (Grendel) D|Grendel (Mongrel) D +Mongrel (Grendel) Prime|Grendel (Mongrel) Prime +Nova (Black Hawk) A|Black Hawk (Nova) A +Nova (Black Hawk) B|Black Hawk (Nova) B +Nova (Black Hawk) C|Black Hawk (Nova) C +Nova (Black Hawk) D|Black Hawk (Nova) D +Nova (Black Hawk) Prime|Black Hawk (Nova) Prime +Nova (Black Hawk) S|Black Hawk (Nova) S 'OMEGA' SHP-4X|Omega SHP-4X Peregrine (Horned Owl) (Standard)|Peregrine (Horned Owl) -Horned Owl (Peregrine)|Peregrine (Horned Owl) -Horned Owl (Peregrine) 2|Peregrine (Horned Owl) 2 Phoenix Hawk LAM PXH-HK2|Phoenix Hawk LAM PHX-HK2 Piranha (Standard)|Piranha -Adder (Puma) A|Puma (Adder) A -Adder (Puma) B|Puma (Adder) B -Adder (Puma) C|Puma (Adder) C -Adder (Puma) D|Puma (Adder) D -Adder (Puma) Prime|Puma (Adder) Prime Raijin RJN101-A|Raijin RJN-101-A Raijin RJN101-C|Raijin RJN-101-C +Stone Rhino (Behemoth) 4|Behemoth (Stone Rhino) 4 +Stone Rhino (Behemoth) 5|Behemoth (Stone Rhino) 5 +Stone Rhino (Behemoth) 6|Behemoth (Stone Rhino) 6 +Stone Rhino (Behemoth)|Behemoth (Stone Rhino) (Standard) Stormcrow (Ryoken) A|Ryoken (Stormcrow) A Stormcrow (Ryoken) B|Ryoken (Stormcrow) B Stormcrow (Ryoken) C|Ryoken (Stormcrow) C Stormcrow (Ryoken) D|Ryoken (Stormcrow) D Stormcrow (Ryoken) Prime|Ryoken (Stormcrow) Prime -Supernova (Standard)|Supernova Summoner (Thor) A|Thor (Summoner) A Summoner (Thor) B|Thor (Summoner) B Summoner (Thor) C|Thor (Summoner) C Summoner (Thor) D|Thor (Summoner) D Summoner (Thor) M|Thor (Summoner) M Summoner (Thor) Prime|Thor (Summoner) Prime +Supernova (Standard)|Supernova +Timber Wolf (Mad Cat) A|Mad Cat (Timber Wolf) A +Timber Wolf (Mad Cat) B|Mad Cat (Timber Wolf) B +Timber WOlf (Mad Cat) C|Mad Cat (Timber Wolf) C +Timber Wolf (Mad Cat) D|Mad Cat (Timber Wolf) D Timber Wolf (Mad Cat) M|Mad Cat (Timber Wolf) M Timber Wolf (Mad Cat) N|Mad Cat (Timber Wolf) N +Timber Wolf (Mad Cat) Prime|Mad Cat (Timber Wolf) Prime +Timber Wolf (Mad Cat) S|Mad Cat (Timber Wolf) S Timber Wolf (Mad Cat) T|Mad Cat (Timber Wolf) T Timber Wolf (Mad Cat) W|Mad Cat (Timber Wolf) W -Kit Fox (Uller) A|Uller (Kit Fox) A -Kit Fox (Uller) B|Uller (Kit Fox) B -Kit Fox (Uller) C|Uller (Kit Fox) C -Kit Fox (Uller) D|Uller (Kit Fox) D -Kit Fox (Uller) Prime|Uller (Kit Fox) Prime -Kit Fox (Uller) S|Uller (Kit Fox) S +Vapor Eagle (Goshawk) 2|Goshawk (Vapor Eagle) 2 +Vapor Eagle (Goshawk)|Goshawk (Vapor Eagle) +Viper (Dragonfly) A|Dragonfly (Viper) A +Viper (Dragonfly) B|Dragonfly (Viper) B +Viper (Dragonfly) C|Dragonfly (Viper) C +Viper (Dragonfly) D|Dragonfly (Viper) D +Viper (Dragonfly) Prime|Dragonfly (Viper) Prime Vixen (Incubus) (Standard)|Vixen (Incubus) -Incubus (Vixen)|Vixen (Incubus) -Incubus (Vixen) 2|Vixen (Incubus) 2 -Incubus (Vixen) 3|Vixen (Incubus) 3 -Mad Dog (Vulture) A|Vulture (Mad Dog) A -Mad Dog (Vulture) B|Vulture (Mad Dog) B -Mad Dog (Vulture) C|Vulture (Mad Dog) C -Mad Dog (Vulture) Prime|Vulture (Mad Dog) Prime Warhammer IIC (Standard)|Warhammer IIC - +Warhawk (Masakari) A|Masakari (Warhawk) A +Warhawk (Masakari) B|Masakari (Warhawk) B +Warhawk (Masakari) C|Masakari (Warhawk) C +Warhawk (Masakari) Prime|Masakari (Warhawk) Prime #Protomechs Boggart (Quad) 1|Boggart Ultraheavy ProtoMech (Standard) @@ -719,6 +729,10 @@ Svartalfa Ultra ProtoMech (Standard)|Svartalfa Svartalfa Ultra ProtoMech (LRM Variant)|Svartalfa (LRM Variant) Svartalfa (LRM Variant)|Svartalfa 2 +#Small Craft +Mowang Courier|Mówáng-class Courier +Mowang Courier (Clandestine)|Mówáng-class Courier (Clandestine) +Wurger Assault Craft|Würger Assault Craft #Space Stations Bastion System Defense Station (Standard)|Bastion System Defense Station (2584) @@ -740,21 +754,28 @@ Snowden Mining Station Mk I|Snowden Mining Station (MK I) #Tanks Avanti Aerospace Airliner ACL-800|Comet Airliner ACL-800 BFFL 'Buffalo'|Buffalo BFFL Hovertruck +Buffel Engineering Support Vehicle VII (Cargo)|Büffel Engineering Support Vehicle VII (Cargo) +Buffel Engineering Support Vehicle VII (Reverse)|Büffel Engineering Support Vehicle VII (Reverse) +Buffel Engineering Support Vehicle VII|Büffel Engineering Support Vehicle VII +Buffel Engineering Support Vehicle VIII|Büffel Engineering Support Vehicle VIII Cal-Boeing Swiftran RTC-215M (Passenger)|Swiftran RTC-215M Command Van (Standard)|Command Van Desert Scorpion|Desert Scorpion Light Tank Donovan-Miter Magellan Series Four|Magellan Series Four Falcon Hover Tank (Standard)|Falcon Hover Tank Federated-Boeing Longhaul FB-335|Longhaul Cargo Aircraft FB-335 +Gurteltier MBT (C3M)|Gürteltier MBT (C3M) +Gurteltier MBT|Gürteltier MBT Hover Tank (Standard)|Hawk Hover Tank (LTV-4) -LTV-4 Hover Tank|Hawk Hover Tank (LTV-4) Iveco Burro Heavy Support Truck|Burro Heavy Support Truck Iveco Burro II Super Heavy Cargo Truck|Burro II Super Heavy Cargo Truck Kressly Dillinger Police Vehicle|Dillinger Police Vehicle LTV-4 Hover Tank (Standard)|Hawk Hover Tank (LTV-4) +LTV-4 Hover Tank|Hawk Hover Tank (LTV-4) Mobile Long Tom Artillery (Unofficial) (+ Carriage)|Mobile Long Tom Artillery (+Carriages)(Unofficial) Mobile Long Tom Artillery Ammunition Trailer LT-MOB-25|Mobile Long Tom Artillery LT-MOB-25 (Ammunition Carriage) Mobile Long Tom Artillery Support Carriage LT-MOB-25|Mobile Long Tom Artillery LT-MOB-25 (Support Carriage) +Motuo Che Shang No.2|Mótuö Chë Shang No.2 O-65 'Oppie' Hazardous Materials Recovery Vehicle O-65 HMRV|HMRV (Hazardous Materials Recovery Vehicle) 'Oppie' O-65 O-66 'Oppie' Hazardous Materials Recovery Vehicle O-66 HMRV|HMRV (Hazardous Materials Recovery Vehicle) 'Oppie' O-66 'Oppie' (HMRV DeConAid Trailer) (Standard)|HMRV (Hazardous Materials Recovery Vehicle) DeConAid Trailer @@ -763,12 +784,16 @@ O-66 'Oppie' Hazardous Materials Recovery Vehicle O-66 HMRV|HMRV (Hazardous Mate 'Oppie' (HMRV Salvage Bed Trailer) |HMRV (Hazardous Materials Recovery Vehicle) Salvage Bed Pion-Laurier Cascatelle|Cascatelle Firefighting VTOL Prime Mover|Prime Mover (LRM) +Schildkröte Line Tank (HPPC)|Schildkröte Line Tank (HPPC) +Schildkröte Line Tank (Light Gauss)|Schildkröte Line Tank (Light Gauss) +Schildkröte Line Tank (Plasma)|Schildkröte Line Tank (Plasma) Schildkröte Line Tank (Standard)|Schildkröte Line Tank Schildkrote Line Tank|Schildkröte Line Tank -Sleipnir APC (SRM)|Sleipnir AP Tank (SRM) +Schildkröte Line Tank|Schildkröte Line Tank Sleipnir AP Tank (SRM)|Sleipnir APC Tank (SRM) -Sleipnir APC|Sleipnir AP Tank Sleipnir AP Tank|Sleipnir APC Tank +Sleipnir APC (SRM)|Sleipnir AP Tank (SRM) +Sleipnir APC|Sleipnir AP Tank SM1 Tank Destroyer SM1|SM Tank Destroyer SM1 SM1A Tank Destroyer SM1A|SM Tank Destroyer SM1A SM3 Tank Destroyer SM3|SM Tank Destroyer SM3 @@ -777,6 +802,7 @@ St. Christopher Cargo Lifter C1|St. Christopher Cargo Transport C2 SturmFeur "Kalki" Cruise Missile Launcher (Standard)|SturmFeur 'Kalki' Cruise Missile Launcher (Standard) Sturmfeur Heavy Tank (SRM)|SturmFeur Heavy Tank (SRM) Sturmfeur Heavy Tank (Standard)|SturmFeur Heavy Tank (Standard) +Teppo Artillery Vehicle|Teppō Artillery Vehicle Vargr APC (LRM)|Vargr APC Tank (LRM) Vargr APC|Vargr APC Tank Vector (Attack)|Vector Combat Support VTOL (Attack) @@ -785,8 +811,6 @@ Vector (Scout)|Vector Combat Support VTOL (Scout) Vector (Transport)|Vector Combat Support VTOL (Transport) Vector Combat Support VTOL (Transport)|Vector Combat Support VTOL - - #Warships Aegis Heavy Cruiser (Clan)|Aegis Heavy Cruiser (2843) Athena Cruiser (Standard)|Athena Cruiser (2569) diff --git a/megameklab/data/mechfiles/protomechs/3060/Centaur 2.blk b/megameklab/data/mechfiles/protomechs/3060/Centaur 2.blk index f02c70928..f23413335 100644 --- a/megameklab/data/mechfiles/protomechs/3060/Centaur 2.blk +++ b/megameklab/data/mechfiles/protomechs/3060/Centaur 2.blk @@ -117,7 +117,7 @@ Developed during the 3060s, this variant utilizes then-newly developed Heavy Las