Current official status at verification
The source review checked the official Steam store, Steam Community hub, and official announcement feed before the Early Access unlock. It did not locate a present official known-issues list for the Early Access build. Therefore this guide has no verified issue entries to publish at that timestamp. Absence from this page is not evidence that every system works on every configuration.
Check the visible last-verified time against the current date and visit the linked official channels before troubleshooting. If the developer publishes a notice, this page should record its wording conservatively, source, affected build context, and resolution status. Until that happens, a community observation remains a report, not a confirmed official issue.
Triage an unexpected result safely
First separate launch or performance problems from gameplay misunderstanding. Record operating system, hardware, build or update time, mode, party size, reproduction steps, and visible message. Restart only after saving what can be observed. Avoid deleting saves, configuration, or system files as an early step. This guide does not authorize destructive recovery actions.
Compare the live English system requirements with the machine, then check official announcements. If the behavior occurs during a spell, generator, or bunker interaction, verify the current in-game description and repeat only when repetition is safe. One surprising result may reflect procedural context, connection conditions, or misunderstood feedback rather than a defect.
- Record the verification date and current build context.
- Capture the exact visible message without paraphrasing it.
- Write minimal reproduction steps and whether solo or co-op was used.
- Check official Steam announcements before relying on reposts.
- Prefer reversible tests and preserve local data.
Keep community reports in their own category
Community reports can identify patterns worth checking, but this page does not convert them into established present status without current official confirmation. Look for matching build context, reproduction steps, and multiple independent observations. A popular post can still describe an old demo, a different configuration, or a resolved state.
When discussing a report, use language such as ‘community-reported’ and link its origin if publication policy later allows it. Do not rewrite the report as a fact. At the verification time, this official-only guide has no current community list captured for publication; readers should use the Steam Community hub as a discovery channel and verify carefully.
Historical demo note — not assumed to describe the current Early Access build
The official developer-authored demo patch v0228 from February 28, 2025 discussed then-current demo work involving critical client crashes, client chopper behavior, doors, and improvements to solo monster behavior and economy. Those notes document a historical demo state. They are not a present Early Access issue list and must not be copied into one.
Historical notes are useful for explaining why old searches and discussions mention particular problems. They can also show that demo behavior changed. They cannot establish that the same condition exists now. Always compare the note’s date and demo label with the present build, then seek a current official source before treating any item as active.
Check the live English requirements accurately
The verified English minimum set lists an Intel i5 or newer-generation i3 / AMD equivalent, GTX 1060 6 GB, and DirectX 11. Recommended lists an Intel i7 or AMD equivalent, including AMD FX 9500+ Series in the checked copy, RTX 3060, and DirectX 12. Both list Windows 10 64-bit, 16 GB RAM, broadband, and 15 GB available storage. Requirements do not guarantee identical performance.
If the system is below a listed requirement, record that context before interpreting the behavior. If it meets the requirements, continue gathering reproducible evidence rather than assuming hardware is irrelevant. Connection issues in co-op and local behavior in solo may require different reproduction paths, but neither should be diagnosed here without evidence.
Prepare a useful official report
A useful report is concise and reproducible: build context, platform details, mode and party size, location or system, steps, observed outcome, expected outcome, frequency, and non-sensitive media if appropriate. Remove personal information. Check the official developer or Steam channels for the preferred reporting route rather than sending private data to an unofficial guide.
Return to this page’s sources after updates. If an issue receives an official notice or resolution, the entry should retain its verification history so readers can distinguish active, resolved, and historical states. Until then, the honest status is limited: no present official list was captured at the stated check.