Difference between revisions of "Nexus (Star Python)"
Line 32: Line 32:
 
Despite early promising action reports from the [[366th Division (ComStar)|366th Division]],<ref name=CSp98/> <ref name=TRO3058p96/> the brutal fighting during [[Operation ODYSSEUS]] in [[3058]] showed that the ''Nexus''<nowiki>'</nowiki>s light armor and short-ranged firepower led to excessive combat losses if targeted by more mobile and longer ranged opponents. With the Skobel line falling to the [[Word of Blake]], the Blakist Precentor Martial [[Cameron St. Jamais]] responded to pilot complaints  about these flaws by promising a complete overhaul when time allowed. Thanks to technology exchange agreements with [[Archon-Princess]] [[Katherine Steiner-Davion]] that provided access to the [[Lyran Alliance]]'s new [[light fusion engine]], a visually reworked and extensively modified version dubbed the '''''Nexus II''''' started rolling off the production lines and into the [[Word of Blake Militia]] in [[3066]] in time for the [[Jihad]].<ref name=TRO3055Up96>''Technical Readout: 3055 Upgrade'', p. 96 "NXS2-A Nexus II"</ref>
 
Despite early promising action reports from the [[366th Division (ComStar)|366th Division]],<ref name=CSp98/> <ref name=TRO3058p96/> the brutal fighting during [[Operation ODYSSEUS]] in [[3058]] showed that the ''Nexus''<nowiki>'</nowiki>s light armor and short-ranged firepower led to excessive combat losses if targeted by more mobile and longer ranged opponents. With the Skobel line falling to the [[Word of Blake]], the Blakist Precentor Martial [[Cameron St. Jamais]] responded to pilot complaints  about these flaws by promising a complete overhaul when time allowed. Thanks to technology exchange agreements with [[Archon-Princess]] [[Katherine Steiner-Davion]] that provided access to the [[Lyran Alliance]]'s new [[light fusion engine]], a visually reworked and extensively modified version dubbed the '''''Nexus II''''' started rolling off the production lines and into the [[Word of Blake Militia]] in [[3066]] in time for the [[Jihad]].<ref name=TRO3055Up96>''Technical Readout: 3055 Upgrade'', p. 96 "NXS2-A Nexus II"</ref>
  
−
In [[3152]], the [[Scorpion Empire]] started full-scale production of an advanced version of the ''Nexus'' using recovered blueprints from [[Word of Blake]] archives which the [[Hanseatic League]] kept on planet [[Braunschweig]]. The blueprints were damaged but after successful data recovery the new version, designated the '''''Star Python''''', was developed and put into service with the [[Imperio Militar del Escorpión]].<ref>''Shrapnel'', Issue #6: ''Moving Forward''</ref> This version uses advanced [[Clan]] weaponry and [[reflective armor]], while its rugged [[Antwerp 175]] engine gives it greater staying power than that of many modern light ’Mechs. Considering its connection to the old ''Jackrabbit'' of the [[Rim Worlds Army]] and later the ''Nexus'' of the ComStar, the ''Star Python''<nowiki>'</nowiki>s continued development is seen as quite surprising but also as a sign of the removal of many traditional Clan stigmas within the Empire under the specter of an external threat from the Clan Homeworlds. Named after an indigenous pack-hunting reptile on the planet Holdout, Clan Sea Fox has observed that the Empire has begun organizing Trinaries of the BattleMech for wolf-pack tactics to offset their light combat capabilities.<ref>''Recognition Guide: ilClan, vol. 23'', p. 4 ''Star Python''</ref>
+
In [[3152]], the [[Scorpion Empire]] started full-scale production of an advanced version of the ''Nexus'' using recovered blueprints from [[Word of Blake]] archives which the [[Hanseatic League]] kept on planet [[Braunschweig]]. The blueprints were damaged but after successful data recovery the new version, designated the '''''Star Python''''', was developed and put into service with the [[Imperio Militar del Escorpión]].<ref>''Shrapnel'', Issue #6: ''Moving Forward''</ref> This version uses advanced [[Clan]] weaponry and [[reflective armor]], while its rugged [[Antwerp 175]] engine gives it greater staying power than that of many modern light ’Mechs. Considering its connection to the old ''Jackrabbit'' of the [[Rim Worlds Army]] and later the ''Nexus'' of the ComStar, the ''Star Python''<nowiki>'</nowiki>s continued development is seen as quite surprising but also as a sign of the removal of many traditional Clan stigmas within the Empire under the specter of an external threat from the Clan Homeworlds. Named after an indigenous pack-hunting reptile on the planet Holdout, Clan Sea Fox has observed that the Empire has begun organizing BattleMech into Trinaries trained in wolf-pack swarming tactics to offset the design's lighter durability and firepower.<ref>''Recognition Guide: ilClan, vol. 23'', p. 4 ''Star Python''</ref>
  
 
==Weapons and Equipment==
 
==Weapons and Equipment==

Revision as of 14:21, 7 November 2022

Nexus (Star Python)
Nexus
Production information
Manufacturer Skobel MechWorks

Imperial BattleMechs (Star Python)

Production Year 3055[1]
Model NXS1-A
Class Light
Cost 2,226,458 C-bills
Technical specifications
'Mech type Inner Sphere BattleMech
Mass 25 tons
Chassis Skobel 100-ROB Endo Steel
Armor Krupp 200 ferro-fibrous
Engine Nissan 175
Communications System Exeter Longscan 200 with C3i Computer
Speed 118.8 km/h
Jump Jets Rawlings 55
Armament
BV (1.0) 626[2]
BV (2.0) 643[3]


Description

The BattleMech known as the Nexus was originally based on the Jackrabbit, a light scout and combat vehicle and infantry support 'Mech built for the Star League Defense Force by Skobel MechWorks. Ironically, the Jackrabbit ended testing two weeks before Stefan Amaris seized power on Terra and was instead primarily used by units loyal to Amaris against the SLDF in General Kerensky's drive to liberate the Terran Hegemony. Though the SLDF captured Skobel's plant relatively intact, thanks to the stigma of being used against his forces Kerensky ordered it shut down and the unloved Jackrabbit disappeared into history outside of ComStar's records. With the Com Guards looking to recoup their grievous losses in the wake of the Battle of Tukayyid, in 3054 Precentor Martial Anastasius Focht ordered the Skobel plant reactivated, reworking the slower Jackrabbit into a fast and highly mobile recon striker 'Mech he renamed the Nexus.[1][4] [5]

Despite early promising action reports from the 366th Division,[4] [5] the brutal fighting during Operation ODYSSEUS in 3058 showed that the Nexus's light armor and short-ranged firepower led to excessive combat losses if targeted by more mobile and longer ranged opponents. With the Skobel line falling to the Word of Blake, the Blakist Precentor Martial Cameron St. Jamais responded to pilot complaints about these flaws by promising a complete overhaul when time allowed. Thanks to technology exchange agreements with Archon-Princess Katherine Steiner-Davion that provided access to the Lyran Alliance's new light fusion engine, a visually reworked and extensively modified version dubbed the Nexus II started rolling off the production lines and into the Word of Blake Militia in 3066 in time for the Jihad.[6]

In 3152, the Scorpion Empire started full-scale production of an advanced version of the Nexus using recovered blueprints from Word of Blake archives which the Hanseatic League kept on planet Braunschweig. The blueprints were damaged but after successful data recovery the new version, designated the Star Python, was developed and put into service with the Imperio Militar del Escorpión.[7] This version uses advanced Clan weaponry and reflective armor, while its rugged Antwerp 175 engine gives it greater staying power than that of many modern light ’Mechs. Considering its connection to the old Jackrabbit of the Rim Worlds Army and later the Nexus of the ComStar, the Star Python's continued development is seen as quite surprising but also as a sign of the removal of many traditional Clan stigmas within the Empire under the specter of an external threat from the Clan Homeworlds. Named after an indigenous pack-hunting reptile on the planet Holdout, Clan Sea Fox has observed that the Empire has begun organizing BattleMech into Trinaries trained in wolf-pack swarming tactics to offset the design's lighter durability and firepower.[8]

Weapons and Equipment

As a recon 'Mech intended to rarely engage an enemy in a pitched battle, the Nexus is armed with a Blankenburg Technologies medium laser backed up by two highly accurate Blankenburg Technologies medium pulse lasers. As a weapon of last resort, the Nexus has two Intek small lasers. For added protection against missile attacks, the Nexus had a McArthur anti-missile system.[4] [5]

The Nexus has a top speed of 119 km/h and is powered by a Nissan 175 fusion engine, which is both light and rugged. To save weight without the vulnerability of an extralight engine, the Nexus is built on a Skobel 100-ROB endo steel chassis. For protection, the 'Mech carries a two tons of Krupp 200 ferro-fibrous armor, relying on its speed and maneuverability, which is enhanced with a jumping capability of up to 120 meters. Finally, to handle the heat from the arsenal of energy weapons, the Nexus carries 10 double heat sinks.[4] [5] Star Python

Variants

  • NXS1-B 
    Considered the progenitor of the Nexus II, the NXS1-B variant of the standard NXS1-A intended to make the 'Mech more capable as a recon unit, the B variant completely restructures the 'Mechs arsenal and reworks the Nexus into a powerful scout 'Mech. Clad in four tons of ferro-fibrous armor, the NXS1-B is capable of jumping up to 150 meters and carries two ER medium lasers as its primary weapons, backed up by an ER small laser. What makes this Nexus variant so effective as a recon 'Mech is its improved C3 unit that allows it to share targeting data with up to five allied units.[6] BV (1.0) = 671[9], BV (2.0) = 715[10]
  • NXS2-B 
    Another version of the Nexus II, the NXS2-B is geared more towards electronic warfare, removing all six of the jump jets of the NXS2-A and replaces them with a Guardian ECM suite and a Beagle active probe. Featuring stealth armor to enhance its reconnaissance abilities, the two ER small lasers have been replaced with a TAG target designation laser to provide spotting capabilities.[6] BV (1.0) = 620, BV (2.0) = 717[12]
  • Star Python 
    A thoroughly upgraded Clan version of the original Nexus, it is powered by a durable Antwerp 175 engine and is equipped with 4 Rawlings 55 jump jets, which allow it to jump up to 120 meters. It's armed with 1 ER medium laser, 2 improved heavy medium lasers, 2 ER micro lasers and a CGS-AMA anti-missile system. It is cooled by 10 double heat sinks while four and a half tons of Compound Rho reflective armor provide ample protection for its size. BV (2.0) = 1,234 [13]

Design Quirks

The Nexus has the following Design Quirks:[14]

The Nexus II has the following Design Quirks:[15]

Related BattleMechs

  • Jackrabbit - The Nexus was based upon the Jackrabbit, a 'Mech designed for the original SLDF that was produced in large numbers for Stefan Amaris' forces. Because of this, the design was largely shunned for centuries after the Amaris Civil War.[1]

Notes

  • The color plate of VMI art included in the ComStar sourcebook for the Nexus, Raijin and Grand Crusader referred to the Nexus as the Star Python and the Raijin as the Galahad (a name already elsewhere) in conflict with the rest of the written text and later Technical Readouts. When queried decades later the Line Developer at the time would clarify the Star Python existed only in error and the correct name was the Nexus, until Moving Forward would repurpose the Star Python name for the Clan Goliath Scorpion version of the 'Mech.

Gallery

References

  1. ↑ 1.0 1.1 1.2 Technical Readout: 3075, pp. 176-177, "Jackrabbit 'Mech Profile"
  2. ↑ Combat Operations, p. 123
  3. ↑ Record Sheets: 3055 Upgrades Unabridged, p. 156
  4. ↑ 4.0 4.1 4.2 4.3 ComStar, p. 98 "New BattleMechs - ComStar Nexus"
  5. ↑ 5.0 5.1 5.2 5.3 Technical Readout: 3058, p. 96 "NXS1-A Nexus"
  6. ↑ 6.0 6.1 6.2 6.3 Technical Readout: 3055 Upgrade, p. 96 "NXS2-A Nexus II"
  7. ↑ Shrapnel, Issue #6: Moving Forward
  8. ↑ Recognition Guide: ilClan, vol. 23, p. 4 Star Python
  9. ↑ Record Sheets: Upgrades, p. 40
  10. ↑ Record Sheets: 3055 Upgrades Unabridged, p. 157
  11. ↑ Record Sheets: 3055 Upgrades Unabridged, p. 158
  12. ↑ Record Sheets: 3055 Upgrades Unabridged, p. 159
  13. ↑ Recognition Guide: ilClan, vol. 23, p. 4, p. 5 Star Python
  14. ↑ BattleMech Manual, p. 93 BattleMech Quirk Table - Nexus Entry.
  15. ↑ BattleMech Manual, p. 93 BattleMech Quirk Table - Nexus II Entry.

Bibliography

Retrieved from "https://www.sarna.net/wiki/index.php?title=Nexus_(Star_Python)&oldid=899817"