fleet_data_format.md

Exported fleet data format

Folder structure

There is a folder for each fleet PDF. The fleets are:

• UCM
• Scourge
• PHR
• Shaltari
• Resistance
• Bioficer

Fleet data index

Within each fleet folder is a file _fleet.json which provides an entry point to that fleet's data. This is a json format file containing the following:

• "SourceVersion": The version of the fleet PDF (taken from the PDF filename). This is a date formatted as YYMMDD.
• "Abilities": The abilities available to Fleet and Famous Admirals. This is a list of dictionaries with keys of "Cost" (string - see 'Ability cost format'), "Name" (string), and "Effect" (string).
• "FleetAdmirals": The Fleet Admirals available to the fleet. This is a list of dictionaries with keys of "Name" (string), "Level" (integer), "Cost" (integer), "FleetAbilities" (integer), and "Abilities" (list of dictionaries with content as per the "Abilities" key above).
• "LaunchAssets": A list of Launch Asset stat line dictionaries. Each dictionary has one of three sets of keys. Fighter type launch assets have keys of "Load" (string), "Thrust" (integer), and "Rerolls" (integer). All other launch assets have keys of "Load" (string), "Thrust" (integer), "Att" (integer), "Lock" (string: either "X+" where X is a number between 1 and 6, or "*"), "DMG" (integer), "Type" (string: one of "K", "E", or "C"), and "Special" (list of strings). Targeted launch assets have keys of "Load" (string), "Target" (string), and "Range" (integer).
• "Systems": A list of filenames for the data files containing ship systems lists. See 'Systems list' for more details.
• "DeployableFeatures": A list of filenames for the data files containing Deployable Feature data.
• "FamousAdmirals": A list of filenames for the data files containing Famous Admiral data.
• "Heroes": A list of filenames for the data files containing Hero ship data.
• "Ships": A list of filenames for the data files containing ship data.

Example:

{
    "SourceVersion": "260327",
    "Abilities": [
        {"Cost": "2AP", "Name": "Colonial Legions", "Effect": "After the Battalion Combat step of the Asset Phase, target a Dropsite or Feature. If any enemy Battalions completely removed any friendly Battalions from that Dropsite or Feature, place 1 Battalion on that Dropsite or Feature."}
    ],
    "FleetAdmirals": [
        {"Name": "UCM Captain", "Level": 1, "Cost": 25, "FleetAbilities": 1, "Abilities": [{"Cost": "2AP", "Name": "Dedicated Survey Teams", "Effect": "When you activate a Group of a single Ship, that Ship may Survey a Dropsite and attack with a single weapon this round (but still cannot launch Assets)."}]}
    ],
    "LaunchAssets": [
        {"Load": "Light Torpedo", "Thrust": 6, "Att": 4, "Lock": "2+", "DMG": 1, "Type": "K", "Special": ["Penetrator"]},
        {"Load": "Fighters", "Thrust": 13, "Rerolls": 1},
        {"Load": "Firefist Assault Boats", "Target": "Cities. Ships and Space stations in the same Orbital Layer.", "Range": 3}
    ],
    "Systems": [],
    "DeployableFeatures": [
        "aegis_platform.json"
    ],
    "FamousAdmirals": [
        "granite_halsey.json"
    ],
    "Heroes": [
        "rhiannon_major.json"
    ],
    "Ships": [
        "santiago.json",
        "lysander.json"
    ]
}

Deployable Feature data file

Each Deployable Feature has its own data file in json format. The file is named the same as the Deployable Feature name, in lowercase with spaces replaced by underscores and all characters that are invalid for filenames removed.

The file contains the following:

• "Profile": A dictionary containing "PTS" (integer or null), "Type" (string, the name of the Deployable Feature), "ES" (string: "X+" where X is a number), "KS" (string: "X+" where X is a number), and "Special" (list of strings).

• "AsIfSpecial": An optional list of strings, each the name of a ship Special rule (e.g. "Payload S-1") that the Deployable Feature is treated as having although it is not in the Profile's "Special". Anything that checks whether the Deployable Feature has a Special rule should check both "Special" and "AsIfSpecial". Only present when non-empty. Example: ["Payload S-1"].

• "Weapons": A list of weapon entries. Each entry is one of:

  • A single-profile weapon: a dictionary containing "Name" (string), "Scan" (integer or null), "Att" (integer), "Lock" (string: either "X+" where X is a number between 1 and 6, or "*"), "DMG" (integer), "Type" (string: one of "K", "E", or "C"), and "Special" (list of strings). Example: {"Name": "Electrowave Caster", "Scan": 8, "Att": 3, "Lock": "2+", "DMG": 1, "Type": "E", "Special": ["Close Action", "Escape Velocity", "Status"]}.
  • A multi-profile weapon: a dictionary containing "Name" (string) and "Profiles" (a list of two or more profile dictionaries). Each profile dictionary contains "Name" (string), "Scan" (integer or null), "Att" (integer), "Lock" (string), "DMG" (integer), "Type" (string), and "Special" (list of strings) as per a single-profile weapon. Example: {"Name": "Heavy Calibre Orbital Gun", "Profiles": [{"Name": "Mounted", "Scan": null, "Att": 2, "Lock": "3+", "DMG": 2, "Type": "K", "Special": ["Calibre-H/C"]}, {"Name": "Deployed", "Scan": 8, "Att": 2, "Lock": "3+", "DMG": 2, "Type": "K", "Special": ["Calibre-H/C", "Critical-2", "Escape Velocity"]}]}.

  Both forms may optionally include "Rule" (string, present when the Deployable Feature's rules include a paragraph for the weapon, beginning with the weapon's name followed by a colon).

• "Load": A list of dictionaries, each containing "Load" (string), "Launch" (integer), and "Special" (list of strings). Example: [{"Load": "Medium Torpedo", "Launch": 1, "Special": ["Limited-4"]}].

• "Rules": A string containing the additional rules for the Deployable Feature.

• "RulesExample": An optional string containing the example that illustrates the rules. Only present when the Deployable Feature's rules include an example.

Example Deployable Feature data file for the UCM Torpedo Platform:

{
    "Profile": {
        "PTS": null,
        "Type": "Torpedo Platform",
        "ES": "5+",
        "KS": "5+",
        "Special": []
    },
    "Weapons": [],
    "Load": [
        {
            "Load": "Medium Torpedo",
            "Launch": 1,
            "Special": [
                "Limited-4"
            ]
        }
    ],
    "Rules": "When an attacking Group or Asset/s attack would cause this feature to be removed, if it has any remaining Torpedoes, the attacking opponent may remove one additional Feature and any Battalions assigned to it from this Dropsite."
}

Ship data file

Each ship class has its own data file in json format. The file is named the same as the ship class name, in lowercase with spaces replaced by underscores and all characters that are invalid for filenames removed.

The file contains the following:

• "Class": String, the name of the ship class.

• "Type": String.

• "Points": Integer.

• "Tonnage": One of "L", "M", "H", "C".

• "BaseSize": Integer giving the size in mm.

• "CountsForTonnageSpend": An optional boolean. When false, this ship's points do not count towards the points spent on ships of its tonnage class when building a fleet. Assumed to be true when not present; it is only present when false.

• "CanAssignAdmiral": An optional boolean. When false, an Admiral cannot be assigned to this ship. Assumed to be true when not present; it is only present when false.

• "Profile": A dictionary containing "Thrust" (integer, unit: inches), "Scan" (integer, unit: inches), "Sig" (integer, unit: inches), "Hull" (integer), "ES" (string), "KS" (string), "BS" (string), "G" (string, "X" or "X-Y", where X and Y are integers), and "Special" (list of strings). Example: {"Thrust": 12, "Scan": 6, "Sig": 0, "Hull": 2, "ES": "6+", "KS": "6+", "BS": "-", "G": "2-4", "Special": ["Descent", "Cloak-1", "Rare", "Vanguard-6\""]}.

• "AsIfSpecial": An optional list of strings, each the name of a ship Special rule that the ship is treated as having although it is not in the Profile's "Special". Anything that checks whether the ship has a Special rule should check both "Special" and "AsIfSpecial". Only present when non-empty.

• "Weapons": A list of weapon entries. Each entry is one of:

  • A single-profile weapon: a dictionary containing "Name" (string), "Arc" (string: one or more of "F", "S", "R", "SL", "SR", "FN", "RN", and "B", separated by slashes), "Att" (integer), "Lock" (string: either "X+" where X is a number between 1 and 6, or "*"), "DMG" (integer), "Type" (string: one of "K", "E", or "C"), and "Special" (list of strings). Example: {"Name": "Barracuda Missile Bays", "Arc": "F/S/R", "Att": 2, "Lock": "4+", "DMG": 1, "Type": "K", "Special": ["Close Action"]}.
  • A multi-profile weapon: a dictionary containing "Name" (string) and "Profiles" (a list of two or more profile dictionaries). Each profile dictionary contains "Name" (string), "Arc" (string), "Att" (integer), "Lock" (string), "DMG" (integer), "Type" (string), and "Special" (list of strings) as per a single-profile weapon.

  Both forms may optionally include "Rule" (string, present when the ship has a rule named the same as the weapon), "Cost" (integer, present on optional/refit weapons), "Replaces" (list of strings, present on optional/refit weapons specifying which weapons are replaced if this one is taken), and "RuleName" (string, the name of the ship rule that grants this weapon's "Cost" and "Replaces" attributes). "Rule" and "RuleName" are independent and may both be present: "Rule" holds rule text for a rule sharing the weapon's name, whereas "RuleName" holds the name of the rule that grants the option.

• "Load": A list of dictionaries, each containing "Load" (string), "Launch" (integer), and "Special" (list of strings). Example: [{"Load": "Dropships", "Launch": 1, "Special": []}]. Load entries may optionally have "Cost" and/or "Replaces" attributes. Cost specified a cost to take that load and Replaces specifies the names of load that it replaces if taken. Where those attributes are granted by a ship rule, the entry also has "RuleName" (string) naming that rule. Example: {"Load": "Mines", "Launch": 1, "Special": ["Mine"], "Cost": 10, "Replaces": ["Fighters & Bombers"], "RuleName": "Minelayer"}.

• "Upgrades": An optional list of upgrade entries. Each entry is one of:

  • A plain upgrade item: a dictionary containing "Name" (string, the name of the ship rule that grants the upgrade), "Cost" (integer), and "Effects" (list of profile modifiers, see 'Profile modifiers'). The ship may independently choose whether to take this item.
  • A choice group: a dictionary containing "Name" (string, the name of the ship rule that grants the choice), "Min" (integer), "Max" (integer), and "Options" (list of plain upgrade item dictionaries). The ship must pick at least "Min" and at most "Max" options from the group. Example: {"Name": "Keel Refit", "Min": 0, "Max": 1, "Options": [{"Name": "Cloaking Keel", "Cost": 15, "Effects": [...]}, {"Name": "Engine Upgrade", "Cost": 25, "Effects": [...]}]} means the ship may take at most one of the listed options.

• "Rules": An optional list of dictionaries, each containing "Name" and "Text", both strings. Example: [{"Name": "Stealth Drop", "Text": "When this Group launches its Dropships, 2 Dropships are needed to place 1 Battalion. If this Group contains a single ship, each Dropship only places a Battalion on a roll of a 4+."}].

• "Systems": An optional dictionary specifying the systems list and selection constraints for this ship. Only present on ships that have purchaseable systems (e.g. Bioficer Dreadnoughts, Resistance Cruisers). See 'Systems list' for more details.

• "AdmiralAbilities": An optional list of dictionaries, each containing "Cost" (string — see 'Ability cost format'), "Name" (string), and "Effect" (string). Example: [{"Cost": "2AP", "Name": "Telemetry Link", "Effect": "When you activate another friendly Group in Orbit, that Group increases its total movement (after orders) by 4\" this round."}].

• "UsableIn": An optional list of dictionaries defining the fleets that this ship is usable in. The ship is assumed to be usable as given in the fleet the ship belong to regardless of this list, and the owning fleet will not be present in the list. Each dictionary has "Fleet" (the name of a fleet it can be used in, can also be "" to indicate all fleets) and "Modifiers" (a list of profile modifiers that apply when used in the named fleet, see 'Profile modifiers'). If the list contains a "" entry as well as entries naming specific fleets, it should be interpreted as available for all fleets with additional modifiers applicable to the named fleets. Example: [{"Fleet": "UCM, "Modifiers": [{"Target": "Special", "Type": "append", "Value": "Rare"}]}].

• "KnownShips": A list of strings.

• "Flavour": A string.

The following is an example ship data file for the Lysander class:

{
    "Class": "Lysander",
    "Type": "Stealth Lighter",
    "Points": 25,
    "Tonnage": "L",
    "BaseSize": 30,
    "Profile": {
        "Thrust": 12,
        "Scan": 6,
        "Sig": 0,
        "Hull": 2,
        "ES": "6+",
        "KS": "6+",
        "BS": "-",
        "G": "2-4",
        "Special": ["Descent", "Cloak-1", "Rare", "Vanguard-6\""]
    },
    "Weapons": [
        {"Name": "Barracuda Missile Bays", "Arc": "F/S/R", "Att": 2, "Lock": "4+", "DMG": 1, "Type": "K", "Special": ["Close Action"]}
    ],
    "Load": [
        {"Load": "Dropships", "Launch": 1, "Special": []}
    ],
    "Upgrades": [],
    "Rules": [
        {"Name": "Stealth Drop", "Text": "When this Group launches its Dropships, 2 Dropships are needed to place 1 Battalion. If this Group contains a single ship, each Dropship only places a Battalion on a roll of a 4+."}
    ],
    "AdmiralAbilities": [],
    "KnownShips": ["Hope's Spark", "Blue Shade", "Eternal Darkness", "Azure Night", "Leprechaun", "Silent Blade"],
    "Flavour": "The Lysander class Lighter has been a lynchpin in the UCM's covert ops since it entered service in 2669. It is the UCMF's first fully cloaked warship, pushing multiple 1st gen classified stealth systems to their current limits of scale. The class is equipped for extended infiltrations including limited surface landings to scout potential invasion sites and support Resistance groups.\nInitially the class was Level-6 classified and generally reserved for Marine Force Black - the UCM's most elite troops under the Office of Naval Intelligence. Rumours circulated among the admiralty, where demands for access to such a tool grew from whispers into shouts. As the Battle for Earth loomed, the Lysander's existence was confirmed and production ramped up. While still precious assets, limited numbers are now available to support regular frontline operations and first strike incursions."
}

Famous Admiral data file

Each Famous Admiral has its own data file in json format. The file is named the same as the Admiral's name, in lowercase with spaces replaced by underscores and all characters that are invalid for filenames removed.

The file is structured the same as for ships, with the following additions to the top-level dictionary:

• "Admiral": The Admiral name as a string.
• "AdmiralLevel": The Admiral's level as an integer.
• "AdmiralPoints": The cost of the Admiral (combined with the ship cost for "Points").
• "ShipPoints": The cost of the ship (combined with the Admiral cost for "Points").
• "FleetAdmiralAbilities": The number of fleet Admiral abilities the Admiral may take.

Additionally, the "KnownShips" key is not present.

The following is an example data file for the Admiral named "Granite" Halsey:

{
    "Admiral": "\"Granite\" Halsey",
    "AdmiralLevel": 5,
    "Class": "Washington",
    "Type": "Supercarrier",
    "AdmiralPoints": 105,
    "ShipPoints": 530,
    "Points": 635,
    "Tonnage": "C",
    "BaseSize": 60,
    "Profile": {
        "Thrust": 6,
        "Scan": 12,
        "Sig": 14,
        "Hull": 24,
        "ES": "3+",
        "KS": "3+",
        "BS": "5+",
        "G": "1",
        "Special": ["Aegis-6", "Command Ship-2", "Reinforced Armour"]
    },
    "Weapons": [
        {"Name": "UF-9000 Mass Driver Turret", "Arc": "F/S", "Att": 2, "Lock": "2+", "DMG": 2, "Type": "K", "Special": ["Critical-1", "Penetrator"]},
        {"Name": "UF-9000 Mass Driver Turret", "Arc": "F/S", "Att": 2, "Lock": "2+", "DMG": 2, "Type": "K", "Special": ["Critical-1", "Penetrator"]},
        {"Name": "UF-4200 Mass Driver Turret Core Battery", "Arc": "F/S", "Att": 6, "Lock": "4+", "DMG": 1, "Type": "K", "Special": ["Fusillade-3", "Volley-2"]},
        {"Name": "UF-4200 Mass Driver Turrets", "Arc": "F/S", "Att": 4, "Lock": "4+", "DMG": 1, "Type": "K", "Special": ["Fusillade-2", "Volley-2"]},
        {"Name": "Leviathan Missile Bays", "Arc": "F/S/R", "Att": 8, "Lock": "3+", "DMG": 1, "Type": "K", "Special": ["Close Action"]}
    ],
    "Load": [
        {"Load": "Fighters & Bombers", "Launch": 6, "Special": ["Alt-1"]},
        {"Load": "Heavy Bombers", "Launch": 4, "Special": ["Alt-1"]}
    ],
    "Upgrades": [],
    "Rules": [
        {"Name": "Fighter Command", "Text": "Fighters, Bombers, & Heavy Bombers launched from this ship may be placed up to 8\" away instead of 6\"."}
    ],
    "FleetAdmiralAbilities": 2,
    "AdmiralAbilities": [
        {"Cost": "4AP", "Name": "Master Tactician", "Effect": "At the end of this Group's activation, discard a Pass Token and target another friendly Group of L or M Tonnage. If you do, that Group may turn up to 45 degrees, then move up to a quarter of its Thrust, and then each Ship in it may attack with a single weapon."}
    ],
    "Flavour": "Head of the most powerful institution mankind has ever known, Supreme Admiral Jacob 'Granite' Halsey is famous for his steely, brisk, borderline-offensive, flare. His rank grants him a permanent seat on the High Council, but his record there is of extensive truancy, not that anyone dares raise that. A career-sailor, his career began as a teenage rating aboard the ageing grand battleship UCMS Virginia, which he would, thirty-two years later, captain. His remaining on the bridge to the last as the venerable ship was wrecked by Shaltari privateers earned him a promotion to commodore, along with facial scarring and a lifetime's hatred for the 'filthy rotten stinking echidnas'. After another two decade's service as the UCMF's most battlehardened, pre-Reconquest commander, he attained mastery of the entire UCMF.\nPreferring to lead from the front, Halsey was present in the opening hours of the Battle for Earth, where, for the ninth time in his career, he had his CIC destroyed around him. Forced to command from the Shield of Aurum's auxiliary CIC, he remained a pivotal force in that titanic engagement, personally scoring nineteen capital ship kills in the first forty-eight hours.\nHalsey is a fixture on whichever frontline is hottest, and although he's burst some more blood vessels on his pockmarked face, he's at the razor's edge of command."
}

Hero data file

Each Hero has its own data file in json format. The file is named the same as the Hero's name, in lowercase with spaces replaced by underscores and all characters that are invalid for filenames removed.

The file is structured the same as for ships, with the following additions to the top-level dictionary:

• "Hero": The Hero name as a string.
• "Ship": The ship name as a string.

The "Class" key is not present and is replaced by the above two keys.

The following is an example data file for the Hero named Rhiannon Major:

{
    "Hero": "Rhiannon Major",
    "Ship": "Leaden Triad",
    "Type": "Heavy Destroyer",
    "Points": 71,
    "Tonnage": "L",
    "BaseSize": 30,
    "Profile": {
        "Thrust": 8,
        "Scan": 6,
        "Sig": 4,
        "Hull": 6,
        "ES": "3+",
        "KS": "4+",
        "BS": "6+",
        "G": "1",
        "Special": [
            "Hero",
            "Unique"
        ]
    },
    "Weapons": [
        {"Name": "Artillery Cannon", "Arc": "F", "Att": 1, "Lock": "4+", "DMG": 2, "Type": "K", "Special": ["Calibre-H/C", "Fusillade-1", "Low Power"]},
        {"Name": "Artillery Cannon", "Arc": "F", "Att": 1, "Lock": "4+", "DMG": 2, "Type": "K", "Special": ["Calibre-H/C", "Fusillade-1", "Low Power"]},
        {"Name": "Artillery Cannon", "Arc": "F", "Att": 1, "Lock": "4+", "DMG": 2, "Type": "K", "Special": ["Calibre-H/C", "Fusillade-1", "Low Power"]}
    ],
    "Load": [],
    "Upgrades": [],
    "Rules": [],
    "AdmiralAbilities": [],
    "KnownShips": [
        "- Leaden Triad"
    ],
    "Flavour": "Leaden Triad is a new, experimental vessel designed and built by the restored Eden Drive Yards Corporation. This pre-war colossus was ended by the Scourge invasion, but this reincarnation is based in its recaptured shipyards, and the new corporation has all the recovered tech of its predecessor, including its work on the largest chemical guns ever built. Though they never got a chance to enter service, three prototypes were recovered and have been installed aboard a unique heavy destroyer hull.\nCaptain Rhiannon Major, already the UCM's finest naval gunnery officer at just 34 years of age, has been given command. Though not a natural leader, her icy bravery and uncanny intelligence are the natural fit to shepherd this project into combat testing. Already, she has demonstrated the devastating power of this antique technology when writ large by deftly annihilating two Bioficer battlecruisers. These guns hurl house-sized shells at vast muzzle energy with negligible power drain, allowing full manoeuvrability and systems use while firing weapons far exceeding this ship's tonnage grade. However, despite Major's calculations and brilliant heat management, frequent and ultra-costly barrel changes seem inevitable."
}

Ability cost format

The "Cost" field on ability dictionaries (in both "Abilities" and "AdmiralAbilities") is always a string. The possible forms are:

Value	Meaning
"NAP" (e.g. "2AP")	Fixed cost of N points
"NAP*" (e.g. "2AP*")	Base cost of N points with a conditional modifier described in the effect text
"*AP"	Variable cost defined in the fleet abilities table (used for abilities whose cost depends on context)

Profile modifiers

A profile modifier is a dictionary consisting of "Target" (string), "Type" (string, one of "add", "subtract", "replace", "append"), and "Value" (integer or string). "Target" is the name of a profile field ("Thrust", "Scan", "Sig", "Hull", "ES", "KS", "BS", "G", "Special"). Integer values are compatible with the "add", "subtract", and "replace" types. String values are compatible with the "replace" and "append" types.

ES, KS, and BS are treated numerically without the "+" suffix for the purpose of "add" and "subtract". Thrust, Scan, and Sig are treated numerically without the inches suffix for the purposes of "add" and "subtract". For example, if the ship has an ES stat of "5+" and a profile modifier of {"Target": "ES", "Type": "subtract", "Value": 1} then the new ES value is "4+".

The Special field should be treated as if it were a comma-separated list of values for the purpose of "append", with a value of "-" indicating an empty list. This means that if Special were "-" and an "append" is applied then the appended value would become the only value in Special. For example, given a Special of "-" and a modifier that appends "Stealth", the new Special would be "Stealth", not "-, Stealth".

Systems list

Systems list files

The fleet index gives the filenames of systems lists available to the fleet. Each file contains one list of systems (for example, Bioficer Dreadnought systems or Resistance Cruiser systems).

The file contains the following:

• "Name": The name of this list of systems. This usually indicates what general category of ship it is intended for.
• "Groups": The names of the groups of systems. The different classes of ship will indicate how many of each group they may take.
• "Systems": The systems that are available.

The "Systems" value is a dictionary that has a key for each name in "Groups" (and only those names). The content for each group is a list of system entries. Each system entry is a dictionary containing:

• "SubGroup": An optional string value giving the name of a sub-grouping. For example, the "Broadside Hardpoint" group in the Resistance Cruiser Systems list has sub-groups of "Weapons" and "Launch".
• "Pts": The points cost of the system.
• "Type": The type of system. This will be one of "Weapon", "Load", or "Structure".
• "Profile": The profile of the system. For weapon and load systems, this follows the usual stat lines associated with those (as used, for example, in the "Weapons" and "Load" entries for ships). For structure systems, this has "Name" and "Effect" keys (both with string values).
• "Effects": This is only present for structure systems. This is a list of profile modifiers (see 'Profile modifiers') in the same way as for a ship upgrade.
• "Max": An optional value. This is an integer giving the maximum number of times this system may be selected. For example, Resistance ships may only take each structure system once.

Example of file content:

{
    "Name": "Dreadnought Systems",
    "Groups": ["Secondary Hardpoint", "Tertiary Hardpoint", "Launch Hardpoint"],
    "Systems": {
        "Secondary Hardpoint": [
            {"Pts": 15, "Type": "Weapon", "Profile": {"Name": "Grand Bisector", "Arc": "FN", "Att": 5, "Lock": "3+", "DMG": 3, "Type": "E", "Special": ["Bloom-2", "Calibre-H/C", "Crippling", "Focused", "Penetrator"]}},
            {"Pts": 20, "Type": "Weapon", "Profile": {"Name": "Gravitic Hyperlance", "Arc": "FN", "Att": 6, "Lock": "3+", "DMG": 2, "Type": "C", "Special": ["Arrest-2", "Bloom-2"]}}
        ],
        "Tertiary Hardpoint": [
            {"Pts": 15, "Type": "Weapon", "Profile": {"Name": "Thermator", "Arc": "F", "Att": 3, "Lock": "4+", "DMG": 2, "Type": "E", "Special": ["Overcharge", "Scald-1"]}}
        ],
        "Launch Hardpoint": [
            {"Pts": 20, "Type": "Load", "Profile": {"Load": "Torpedo", "Launch": 2, "Special": ["Limited-4"]}}
        ]
    }
}

Systems list on ships

The "Systems" key in ship data files specifies the type of systems that can be fitted to that ship and the minimum/maximum quantities. It is a dictionary that contains the following:

• "Name": The name of the systems list to use. This must match the "Name" value in the systems list data, not the filename.
• "Min": An integer stating the minimum number of systems that must be taken across all groups.
• "Max": An integer stating the maximum number of systems that can be taken across all groups.
• "GroupLimits": A dictionary giving the limits for each group. Each entry has the name of a group (defined in the "Groups" value in the systems list), with the value being a dictionary with "Min" and "Max" keys. Min and max are both optional with a default Min of 0 and default Max of unlimited (in practice, this will be the same as the max systems). If a group is not present then the default values are assumed.

Below is an example for the Resistance Heavy Cruiser. This must take 5 systems from the "Cruiser Systems" list, with a maximum of two from the "Broadside Hardpoint" group, two from the "Structures" group, and an unlimited number from the "Turret Hardpoint" group (capping at 5 for the max number of systems that can be taken).

{
    "Name": "Cruiser Systems",
    "Min": 5,
    "Max": 5,
    "GroupLimits": {
        "Broadside Hardpoint": {"Max": 2},
        "Structures": {"Max": 2}
    }
}