The changes to the exported JSON between the 2.3.1-era exports and the 2.4 exports.
Breaking changes are marked (breaking). Everything else is additive or a new value in an existing field.
SourceVersionis always three parts. The rulebook calls itself2.4, and it is exported as"2.4.0".
Tonnage changes from an object keyed by tonnage to a list of limits. 2.4 adds a combined cap: Heavy and Colossal points together may not exceed Medium points. One tonnage can now be covered by more than one limit.
Before:
"Tonnage": {
"Light": {"MaxPointsFrom": ["Medium", "Heavy"], "Scope": "Fleet"},
"Heavy": {"MaxPointsFrom": ["Medium"], "Scope": "Fleet"},
"Colossal": {"MaxGroupsByGameSize": {"Skirmish": 0, "Clash": 1, "Battle": 2, "Reconquest": 3}, "Scope": "Fleet"}
}After:
"Tonnage": [
{"Tonnages": ["Light"], "MaxPointsFrom": ["Medium", "Heavy"], "Scope": "Fleet"},
{"Tonnages": ["Heavy", "Colossal"], "MaxPointsFrom": ["Medium"], "Scope": "Fleet"},
{"Tonnages": ["Colossal"], "MaxGroupsByGameSize": {"Skirmish": 0, "Clash": 1, "Battle": 2, "Reconquest": 3}, "Scope": "Fleet"}
]Tonnagesis a non-empty list. The limit applies to the combined total of all the tonnages listed. ForMaxPointsFrom, that means the summed points of Heavy and Colossal ships.- Each entry has exactly one limit form (
MaxPointsFrom,MaxGroupsByGameSizeorMaxGroups), plusScope. These forms and their meanings are unchanged. - Every limit applies independently. Colossal is covered by both the pooled points cap and its group-count limit.
_system.json gains "Features": "features.json". The file lists the five standard rulebook Features (section 11.3): Military Outpost, Orbital Defence Gun, Comms Station, Power Plant and Hangar. Each has the same layout as a fleet Deployable Feature, except there is no PTS:
{
"Profile": {"Type": "Hangar", "ES": "4+", "KS": "4+", "Hull": 5, "Special": []},
"Weapons": [],
"Load": [{"Load": "Fighters & Bombers", "Launch": 2, "Special": []}],
"Rules": "This Feature's Fighters & Bombers use the Controlling players' Fighters & Bombers."
}Hullis an integer. (Early 2.4 rulebooks printed-for the Hangar, exported asnull; it is now 5.)- Comms Station and Power Plant print a bespoke rule in the Special column. That text is in
Rules("Comms Uplink: …","Volatile: …"), andSpecialis[]. - A footnote on a Feature's table, such as the Hangar's, is added to its
Rules.
Every ship with a Feature Carrier rule gains a FeatureCarrier object, directly after Rules. It is not present on other ships.
"FeatureCarrier": {"Count": 1, "ValidDeployableFeatures": ["*"]}
"FeatureCarrier": {"Count": 2, "ValidDeployableFeatures": ["*"]}
"FeatureCarrier": {"Count": 1, "ValidDeployableFeatures": ["Gravitational Arc", "Ghost Orb Tower"]}
"FeatureCarrier": {"Count": 1, "Free": true, "ValidDeployableFeatures": ["Hangar"]}Countis how many Features the ship carries. WhereCountis 2, duplicates are allowed.Freeis only present whentrue. When it is present, the Features cost no points. When it is absent, the ship pays each Feature'sPTS.ValidDeployableFeaturesholds Feature names, matching a Feature'sProfile.Type. Look each name up in the ship's own fleet's Deployable Features first, then in the Systemfeatures.json.["*"]means any of the ship's own fleet's Deployable Features. It never includes the rulebook Features; those are only valid when named.
2.4 values:
| Ships | FeatureCarrier |
|---|---|
| PHR, Scourge, UCM carriers; Resistance Jutland, Midway, Trafalgar | 1 of * |
| Resistance Actium, Salamis; all Shaltari carriers | 2 of * |
| Bioficer Shade, Sierra, Sluice, Syntax, Synthesis | 1 of Gravitational Arc / Ghost Orb Tower |
| Civilian EX-7 Packet Runner | 1 Hangar, Free |
| Civilian M-Type Barge | 1 Military Outpost, Free |
ProfilegainsHull, directly afterKS. It is an integer.
UCM Torpedo Platform example:
"Profile": {"PTS": 20, "Type": "Torpedo Platform", "ES": "5+", "KS": "5+", "Hull": 4, "Special": []}- A fleet ability or admiral ability
Costcan now be a range, such as"1-2AP"(Shaltari Navigational Mastery). The full pattern is^(\d+(-\d+)?AP\*?|\*AP)$. The cost is exported as printed, and the ability text explains how the range is used.
- A ship can now carry several multi-profile weapons with the same
Name. Romulus has threeEnergy Glaivesweapons and Remus has two, and each one hasPulseandBeamprofiles. Treat each weapon entry as a separate weapon.
- No format change. Some Effect texts change with 2.4: Resistance Frigate
Sensor Domenow only grants Detector.
2.4 adds the ship rule Mercenary (X), which appears as a profile Special: Mercenary (All), Mercenary (UCM, PHR, Resistance) or Mercenary (Non-Scourge, Non-Bioficer).
-
Specials can contain commas inside brackets.
"Mercenary (UCM, PHR, Resistance)"is a single Special. Code that matches Special names should treatMercenary (...)as the ruleMercenary (X). -
New optional
Exceptkey on aUsableInentry:"UsableIn": [ {"Fleet": "*", "Except": ["Scourge", "Bioficer"], "Modifiers": [ {"Target": "Special", "Type": "remove", "Value": "Boardable"}, {"Target": "Special", "Type": "remove", "Value": "Civilian Transport"} ]} ]
Exceptonly appears whenFleetis"*", and it is left out rather than written as an empty list.- It holds short fleet names (
UCM,PHR,Shaltari,Scourge,Resistance,Bioficer), the same names used inFleet.
-
(All)gives one entry withFleetset to"*". A named list gives one entry per fleet. ANon-list gives a single"*"entry withExcept. -
Each entry removes
Boardableand/orCivilian Transport, whichever of them the ship has, because the Mercenary rule removes them when the ship is taken. -
Modifiersis still always present, and can be[]. -
Ships whose eligibility comes from another rule (Civilian Argonaut's "Mind of its Own", Misc Palatine's "Remnant" and Pungari Thresher's "Subservient Mercenaries") keep their existing
UsableIn. There is no change for these.
Featureschanges from an inline list of{Name, Text}to a filename:"space_station_features.json".
The Features are now a priced table, like the armaments.
[
{"Name": "Launch Control", "Pts": 5, "ES": "4+", "KS": "4+", "Hull": 5, "Effect": "When all Launch Control Features are removed from a Space Station, that Station cannot Launch Assets", "Effects": []},
{"Name": "Life Support", "Pts": 5, "ES": "5+", "KS": "5+", "Hull": 6, "Effect": "When this Feature is removed, each player removes a Battaion from this Space Station, …", "Effects": []},
{"Name": "Reactor Core", "Pts": 0, "ES": "5+", "KS": "5+", "Hull": 6, "Effect": "When this Feature or a Space Station with this feature is destroyed, it explodes with a Reactor Overload Explosion Effect with a range of D6+3\".", "Effects": []},
{"Name": "Redundant Systems", "Pts": 10, "ES": "4+", "KS": "4+", "Hull": 7, "Effect": "This Space Station gains a 6+ Backup Save.", "Effects": [{"Target": "BS", "Type": "replace", "Value": "6+"}]}
]PtsandHullare integers, andESandKSare strings, as in ship profiles.Effectsis a list of profile modifiers applied to the station that has the Feature, as on the Space Station Armaments Structures. It is always present and is[]when the Feature changes no profile stat. In 2.4, only Redundant Systems has one: it sets the station'sBSto"6+".- 2.4 has eight Features: Launch Control, Weapons Control, Life Support, Reactor Core, Redundant Systems, Firing Computer, Defensive Systems and Supercontrol Node.
- Defensive Systems has no effect: the PDF prints
Nonein its Effect cell, and itsEffectis the string"None"as printed, notnull.
Hardpoints changes shape, and now also appears on fleet stations.
Before (generic stations only):
"Hardpoints": {"Armaments": 1, "Features": 0}After:
"Hardpoints": {
"Features": [{"Name": "Life Support", "Count": 1}],
"AdditionalFeatures": {"Min": 3, "Max": 3},
"Armaments": {"Min": 0, "Max": 2}
}Features: the Features the station has automatically. They are free, and each has a count, such as two Weapons Control. EachNamematches an entry inspace_station_features.json.AdditionalFeatures: how many extra Features may be bought fromspace_station_features.json, at their listed points. "Must take three" gives 3/3, "may take one" gives 0/1, and "must take two… and may take one" gives 2/3.Armaments: how many options may be taken fromspace_station_armaments.json. "May take up to two" gives 0/2.- The shape is always complete: absent parts are
[]or{"Min": 0, "Max": 0}. - On fleet stations,
Hardpointscomes afterLoad, and theHardpointsrule is removed fromRules. If that was the only rule,Rulesis left out.
2.4 values:
| Station | Features | AdditionalFeatures | Armaments |
|---|---|---|---|
| Small Space Station | Weapons Control 1, Life Support 1 | 0/0 | 0/1 |
| Medium Space Station | Life Support 1 | 3/3 | 0/2 |
| Large Space Station | Life Support 1 | 4/4 | 0/3 |
Fleet stations vary. Most have Life Support plus two Launch Control or two Weapons Control, and some may or must take additional Features.
- It can now contain the special entry
"Space Station Features". This means "one option from the Space Station Features list", counting as one of the station'sMaxUpgrades. All three generic stations have it in 2.4. - Every other entry is still the
Nameof a station upgrade file.
The Structures group gains two entries: Defensive Garrison and Forward Operating Base. Which one can be selected depends on the scenario setup. Like the other Structures they have Max (1). They also carry two new optional keys after Max, each written only when it applies:
{
"Pts": 0,
"Type": "Structure",
"Profile": {"Name": "Defensive Garrison", "Effect": "This Structure does not cost points and can only be taken by a player that is the Defender in a scenario, …"},
"Effects": [],
"Max": 1,
"ScenarioRole": "Defender",
"ExcludesGroup": true
}ScenarioRoleis"Defender"or"Attacker". The entry can only be taken by the player in that role. The suggested presentation is to merge allScenarioRoleentries into one choice ("Defensive Garrison / Forward Operating Base") and apply whichever fits once the roles are known.ExcludesGroupset totruemeans taking this entry prevents taking any other entry in the same group (Structures).Ptsis set to0where the PDF has*.