1.0 release (v1.0.1 current) bug monitor
Live reports for the 1.0 release wave: launch crashes tied to old mods, the save-loss bug fixed in v1.0.1, Session Not Found join errors, and dedicated-server memory growth.
Primary signal
The graph will appear when players respond.
Updated 08:33 UTC. Refreshes every 60 seconds.
No hardware pattern clears the privacy threshold yet. Small groups stay hidden.
One graph per symptom
Do not report every symptom to one generic page. Pick the tracker that matches what actually happened.
Track crashes after updating to 1.0, including the UE-Pal Exception Access Violation on PC. The most common verified cause is leftover Early Access mods, which 1.0's engine changes make incompatible until the files are fully deleted.
Pocketpair's v1.0.1 hotfix on July 15 fixed a bug where save data could be unintentionally discarded after certain operations, plus a PlayStation-only repeated save error. Reports on builds older than 1.0.1 track here.
Track failures to join co-op or dedicated servers after 1.0, including the Not Found Session message. Verified causes include client and server on different versions, the host world's multiplayer toggle being off, and stale sessions on unrestarted servers.
Track dedicated-server memory that climbs over hours and is not fully released, ending in a crash at peak player counts. Community server hosts describe the pattern consistently; Pocketpair lists server-side optimization in 1.0 but has not confirmed a specific leak.
Track co-op saves migrated to dedicated servers where the world and bases arrive but a player's character and inventory do not, reported as a player-ID (GUID) mismatch between the co-op save and the dedicated server's expected structure.