Skip to content

Corrects size of Drone Carrier Control System on Fury CX-17 #310

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
HammerGS merged 1 commit into from
Apr 1, 2026
+15 −15
Merged

Corrects size of Drone Carrier Control System on Fury CX-17 #310

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
30 changes: 15 additions & 15 deletions data/mekfiles/vehicles/XTRs/Comstar/Fury CX-17.blk
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
# MegaMek Data (C) 2025-2026 by The MegaMek Team is licensed under CC BY-NC-SA 4.0.
# MegaMek Data (C) 2026 by The MegaMek Team is licensed under CC BY-NC-SA 4.0.
# To view a copy of this license, visit https://creativecommons.org/licenses/by-nc-sa/4.0/
#
# NOTICE: The MegaMek organization is a non-profit group of volunteers
Expand All @@ -15,7 +15,7 @@
# <https://www.xbox.com/en-US/developers/rules> and it is not endorsed by or
# affiliated with Microsoft.

#Saved from version 0.50.12 on 2026-02-26
#Saved from version 0.50.12-nightly-2026-03-28 on 2026-03-31
<UnitType>
Tank
</UnitType>
Expand Down Expand Up @@ -89,8 +89,8 @@ Tracked
<Body Equipment>
ISTankCockpitCommandConsole
ISAngelECMSuite
ISDroneCarrierControlSystem:SIZE:0.0
IS LB 5-X AC Ammo
ISDroneCarrierControlSystem:SIZE:5.0
</Body Equipment>

<Front Equipment>
Expand All @@ -111,23 +111,14 @@ ISLBXAC5
ISLBXAC5
</Turret Equipment>

<source>
XTR:Comstar
</source>

<tonnage>
80.0
</tonnage>
<capabilities>
<p>The Fury's primary weapon is a turret-mounted Gauss rifle, offering exceptional range and hitting power for a vehicle of its size and role. The original M-9 variant was replaced in the modern revival by the Poland Main Model C, providing equivalent firepower with improved parts availability across the Federated Suns supply chain. Two tons of ammunition give the crew reasonable endurance for extended operations. The weapon's minimum effective range is a meaningful drawback: the Fury is poorly suited to close-quarters engagements, and crews must rely on supporting infantry or armor to guard against threats that close inside the rifle's dead zone. The vehicle is not intended to absorb punishment like a dedicated assault tank, and commanders who misuse it as a line vehicle accept disproportionate risk.</p><p>Fifteen tons of PyroTec ArmorSlab Standard plate provide solid protection appropriate to a command vehicle, and the Pitban 320 fusion engine delivers a road speed that keeps the Fury competitive with the mechanized formations it typically accompanies. The design's true strength lies in its command and control suite. The original Nirasaki-400X command computer gave SLDF commanders a battlefield information advantage measured in seconds per targeting solution, functioning as a primitive distributed fire control network. The Terran Hegemony's decision to restrict this system to Royal units prompted Jolassa to develop the stripped Fury II, which traded the computer for an additional forward-facing medium laser and modestly heavier side armor. Both versions retained the core vehicle platform and were tactically interchangeable in mixed formations, though unit commanders quickly learned to keep the two variants segregated to avoid coordination confusion under fire.</p>
</capabilities>

# Fluff Date: 2026-03-07 11:22:50
<overview>
<p>The Fury Command Tank originated in 2637 as a purpose-built command and control vehicle for Star League Defense Force armor and infantry regiments. Produced by Jolassa Armored Vehicles on Tybalt under Terran Hegemony patronage, it was designed to serve as a mobile tactical hub rather than a frontline combatant, though its weaponry gave it the ability to contribute meaningfully to any engagement it supported. The design's defining characteristic was an advanced battlefield computer that processed and distributed tactical data at speeds previously unseen in field operations, functioning as a primitive networked fire-control system decades before such technology became common across the Inner Sphere. This capability made the Fury a coveted command asset, and it was produced in both a restricted high-capability version for SLDF Royal units and a more widely distributed variant that omitted the classified computer. Solidly built for its role, the Fury balanced reasonable protection and speed with long-range armament well suited to a command vehicle operating from the second echelon.</p>
</overview>

<capabilities>
<p>The Fury's primary weapon is a turret-mounted Gauss rifle, offering exceptional range and hitting power for a vehicle of its size and role. The original M-9 variant was replaced in the modern revival by the Poland Main Model C, providing equivalent firepower with improved parts availability across the Federated Suns supply chain. Two tons of ammunition give the crew reasonable endurance for extended operations. The weapon's minimum effective range is a meaningful drawback: the Fury is poorly suited to close-quarters engagements, and crews must rely on supporting infantry or armor to guard against threats that close inside the rifle's dead zone. The vehicle is not intended to absorb punishment like a dedicated assault tank, and commanders who misuse it as a line vehicle accept disproportionate risk.</p><p>Fifteen tons of PyroTec ArmorSlab Standard plate provide solid protection appropriate to a command vehicle, and the Pitban 320 fusion engine delivers a road speed that keeps the Fury competitive with the mechanized formations it typically accompanies. The design's true strength lies in its command and control suite. The original Nirasaki-400X command computer gave SLDF commanders a battlefield information advantage measured in seconds per targeting solution, functioning as a primitive distributed fire control network. The Terran Hegemony's decision to restrict this system to Royal units prompted Jolassa to develop the stripped Fury II, which traded the computer for an additional forward-facing medium laser and modestly heavier side armor. Both versions retained the core vehicle platform and were tactically interchangeable in mixed formations, though unit commanders quickly learned to keep the two variants segregated to avoid coordination confusion under fire.</p>
</capabilities>

<deployment>
<p>Developed by ComStar from surviving Fury hulls after Tukayyid under Precentor Ashok Sethi, the CX-17 prototype was designed as a drone command vehicle. Only a small number of prototypes were completed. The design carried a cockpit command console and drone carrier control system to coordinate remotely operated units, with reactive armor and paired LB 5-X autocannons providing self-defense against the airstrikes that historically targeted Fury command tanks. The CX-17 remained exclusive to ComStar's experimental drone program and was never offered outside the organization.</p>
</deployment>
Expand Down Expand Up @@ -160,3 +151,12 @@ COMMUNICATIONS:Unknown
TARGETING:Unknown
</systemModels>

<source>
XTR:Comstar
</source>

<tonnage>
80.0
</tonnage>