What changed
What to do now
Hotfix 1 fixed launch-week startup, crash, analytics, and backend-data issues rather than adding new content.
- Who should care
- Players blocked by startup problems, Ping crashes, analytics concerns, or unclear backend-data behavior.
- What to do now
- Check the official hotfix note first if the game fails before the menu or if analytics consent is your main concern.
- What to test again
- Startup troubleshooting and privacy explanations should point forward to Hotfix 2 when discussing later policy wording.
Terms of Service follow-up was promised in Hotfix 1 and later partly handled by Hotfix 2.
- Who should care
- Players, creators, streamers, and fan-site operators reading older launch-week policy discussion.
- What to do now
- Use Hotfix 1 for the first analytics-consent change, but use Hotfix 2 and the policy FAQ for the newer policy state.
- What to test again
- Any policy page should avoid stopping at Hotfix 1, because the official follow-up changed the context.
Xbox certification can make hotfix rollout timing differ from PC.
- Who should care
- Cross-platform groups comparing fixes across Steam, Epic, Microsoft Store, Xbox, or Game Pass.
- What to do now
- Confirm everyone is on the same patch before treating a crash fix or workaround as universal.
- What to test again
- Co-op and platform-specific advice should keep rollout timing caveats visible.
What Hotfix 1 changed
Hotfix 1 does not add new areas, tools, or story. It deals with launch-week problems that can stop players before normal play: startup guidance, a Ping-related crash, analytics consent, and backend data volume.
If the game will not launch, the error message is unclear, or data collection is your main concern, start with this hotfix note before looking at the wider Early Access roadmap.
Current status: Hotfix 2 has now handled part of the policy follow-up that Hotfix 1 promised. Read this note for the first analytics and crash fixes, then use the Hotfix 2 and policy FAQ pages for the newer Terms of Service, Privacy Policy, and telemetry-callout context.
If the game would not start, this is the part to read
Unknown Worlds updated the crash-on-startup error pop-up for AMD graphics cards and DirectX 12 issues. Steam discussions around launch show why that matters: players were seeing startup crash messages, DirectX 12 confusion, driver and hardware-support questions, and repeated launch attempts before reaching the menu.
Some startup issues can still remain. Check the store requirements, GPU support, driver state, and any platform-specific notes before assuming a save or install is broken.
Ping crash, analytics, and backend traffic
The concrete fix list is short:
- An infrequent crash related to the Ping feature was fixed.
- Analytics now turn on only after Terms of Service acceptance.
- The amount of data sent to backend services was reduced.
- Analytics can still be disabled from the settings menu.
The analytics change is worth separating from the crash fix. Launch-week Steam reviews and discussions included concern about EULA and data handling, so this hotfix is partly a stability patch and partly a communication patch.
Xbox may not update at the same moment
Unknown Worlds says the hotfix may take time to appear globally and will reach Xbox after certification. Co-op groups should confirm every platform has the same fix before comparing crashes or workarounds.
If a workaround or co-op note depends on Hotfix 1, check platform version before treating it as universal.
What still needs follow-up
The official post says Terms of Service adjustments and a FAQ are planned. Until those land, any privacy or EULA explanation should stay conservative: record what Hotfix 1 changed, but do not imply that all player concerns have been answered.