7.1.0 mission-generation changes
Game version 7.1.0 changed several mission-generation profiles. The clearest changes affect Hive World missions, faction-specific optional objectives, and the addition of Horde Defend.
- Introduced in
- 7.1.0
- Changed generation profiles
- 71
- Hive World profiles changed
- 3
Profile changes
Destroy Spore Lung now permits two Lung objectives.
The same patch reduces the Spore Lung entity's health from 30,000 to 5,000. Extract E-711 also replaces its embedded Raise Flag objective with Restart Pumps, while the standalone Restart Pumps profile has a smaller objective pool.
| Mission | Before | After | Additional change |
|---|---|---|---|
| Destroy Spore Lung | 1 Spore Lung allowed | 2 Spore Lungs allowed | The mission profile limit changes from 1 to 2. The optional-objective pool also drops from 16 entries to 10. |
| Extract E-711 | Raise Flag · up to 2 | Restart Pumps · up to 3 | The embedded Hive World objective changes from Raise Flag to Restart Pumps. |
| Restart Pumps | 14 objective-pool entries | 10 objective-pool entries | The profile remains present, but its optional-objective composition changes. |
Destroy Spore Lung's primary Lung candidate keeps the same identity and weighting, but its mission-profile maximum changes from 1 to 2. The mission's candidate pool also drops from 16 entries to 10 and no longer includes its previous Purge Hatchery and Destroy Spawners entries.
The global Spore Lung objective metadata is separate from this mission-profile limit. Its duplicate cap remains 3, so that global value is not what changed the mission from one Lung to two.
Extract E-711 changes its embedded Hive World objective from Raise Flag, up to two to Restart Pumps, up to three. This is direct profile data and does not depend on inferring the change from observed mission layouts.
The Restart Pumps generation profile still exists after the patch, but that alone does not prove that it remains independently selectable on the Galactic map. Mission-profile construction and top-level mission selection are separate layers.
Spore Lung
| Field | Before | After | Status |
|---|---|---|---|
| Health | 30,000 | 5,000 | Confirmed |
| Other entity metadata | Changed | Changed | Gameplay meaning unresolved |
The health change is separate from the mission-generation profile. Several behavior- and fog-related values also changed, but their gameplay meaning is not established.
Extraction objective pools
| Change | Affected profiles | Result |
|---|---|---|
| Automaton optional extraction | 34 Automaton/general profiles | Automaton-specific optional extraction objective added |
| Illuminate optional extraction | 22 Illuminate/general profiles | Generic optional extraction replaced by Illuminate-specific optional extraction |
| Purge Illuminates | 6 Illuminate profiles | Removed from the candidate pool |
| Convoy Assault | 6 Automaton profiles | Removed from the candidate pool |
The broadest repeated change is to optional extraction objectives. Thirty-four Automaton/general profiles gain the Automaton-specific extraction objective. Twenty-two Illuminate/general profiles replace the previous generic extraction objective with the Illuminate-specific version.
Six Illuminate profiles also lose Purge Illuminates from their candidate pool, and six Automaton profiles lose Convoy Assault.
Horde Defend
Version 7.1.0 adds a new Horde Defend generation profile containing one primary objective. Retained runtime mission-selection data independently shows Horde Defend being selected for Illuminate operations from difficulty 5 through difficulty 10.
This is the only newly added generation profile in the retained build comparison used to identify the 7.1.0 changes.
Unmapped changes
| Subject | Change | Interpretation |
|---|---|---|
| Shoot Down Mothership | Mission metadata changed | Gameplay meaning unresolved |
| Fog Generator | Mission metadata changed | Gameplay meaning unresolved |
| SEAF Artillery | Mission metadata changed | Gameplay meaning unresolved |
| Radar Station | Mission metadata changed | Gameplay meaning unresolved |
| Scenario settings | Scenario metadata changed | Gameplay meaning unresolved |
These differences are consistent across the build comparison, but their gameplay meaning is not established. The page records that the affected mission data changed without publishing uninterpreted raw values.
Evidence standard
How the OTL separates code confirmation, controlled live testing, and behavior that remains unresolved.
How the OTL rates evidence
The OTL rates code evidence and live-game evidence separately. A mechanic can be clear in code but still need a controlled gameplay check for hidden state, ordering, or another runtime factor.
Live confirmation means controlled gameplay or instrumented runtime observation, not player impression alone.