Update first if Space Resources blocks the first expedition: the old tutorial-order softlock had an expedition-restart workaround, but the official July 29 build shipped a flow fix for that sequence.
Identify the historical symptom
The official July 27 Known Issues notice said the first expedition could softlock when Space Resources was completed out of tutorial order—for example, entering combat before finishing mining. The symptom was not merely a difficult objective: the later mission flow could stop advancing.
That trigger belongs to the documented old build. It is useful for recognizing a report, but it should not be presented as a current requirement after the shipped fix.
Use the old workaround only on the old branch
On July 27, official guidance was to follow the tutorial sequence. If the expedition was already stuck, the temporary workaround was to restart that expedition and complete the guided mining step before moving into combat.
On July 29, an official update changed the Space Resources and Engage the Scourgeborn flow so completing Space Resources outside the tutorial guidance would no longer block the subsequent mission. Current players should therefore update first rather than immediately repeat the old sequence.
Diagnose the current build safely
If the same symptom appears after updating, do not assume the historical cause survived unchanged. Confirm the active build, objective text, and the last completed tutorial action. Then restart only the affected expedition if that remains safe in the current interface.
Do not delete the whole save or LocalLow directory. A post-fix recurrence may involve a different mission-state or content problem and should be preserved for a useful report.
After confirming the latest build, use Steam's file verification if the flow remains inconsistent. The developer's broader technical notice supports verification as the first file-integrity step; it does not reclassify every mission-state issue as corrupt files.
Capture a useful recurrence report
Record:
- the game build and platform;
- whether this is the first expedition;
- the visible Space Resources objective;
- whether mining or combat was completed first;
- the next mission that failed to appear;
- whether an expedition restart changed the result; and
- whether Steam file verification found a problem.
This distinguishes the confirmed old sequence from a current recurrence. It also avoids destructive troubleshooting before the mission state can be inspected.
Keep the two timelines separate
The historical branch is: July 27 known issue, tutorial order, restart the affected expedition. The shipped-fix branch is: July 29 flow change, update first, then report a reproducible current-build failure if it continues.
For a crash or freeze during loading rather than a mission objective that stops advancing, use the mission-load crash guide. For broader stability testing, follow the performance guide.