On this page
DIRECT ANSWER
Developer-listed fixes and current player reports are different records
Read this table before troubleshooting anything
| Issue | Status | What the source actually says |
|---|---|---|
| Offline play blocked by the login queue | Developer reports fixed Sep 5 | Named directly and described as corrected. |
| Michael missing the prompt to stand up after a knockdown | Developer reports fixed Sep 5 | Named directly and described as corrected. |
| Xbox Series S rendering in Performance Mode | Developer reports fixed Sep 5 | Scoped to certain displays; Series X is not mentioned. |
| Challenges failing to track | Several fixes reported | Covers several challenges, not all challenge tracking. |
| Crashes | Several fixes reported | Described only as numerous crash fixes, with no list. |
Offline play and the login queue
This one is worth understanding because the symptom looks nothing like the cause. A login queue is an online-service mechanism, and it was interfering with a mode that should not need the service at all — so players who chose offline specifically to avoid server problems were being held up by a server problem anyway. The hotfix named it and described it as corrected. If offline play still stalls for you after that patch, you are outside what the fix covered and the detail is worth reporting.
The Series S entry is narrower than it looks
The fix names the Xbox Series S in Performance Mode on certain displays. Three qualifiers, each of which matters. It does not mention the Series X, it does not cover other graphics modes, and it does not claim every display was affected. Rendering faults on Series X, or on Series S outside Performance Mode, are not covered by this entry and should be treated as unacknowledged.
Current community reports to compare with your symptom
| Reported symptom | Evidence and next step |
|---|---|
| PC–Xbox friends kicked during matchmaking | Repeated in the crossplay discussions. Compare party invitations with direct game invitations using the dedicated crossplay guide. |
| Prologue Challenge 6 does not complete | Repeated in the challenge-specific thread and issue roundup. Record the exact objective and counter; difficulty-change suggestions have mixed results. |
| Story progress lost after a crash or exit | Reported in the early-access issue roundup. Capture chapter, checkpoint, exit method and build; do not delete saves as a proposed repair. |
| Resident does not obey an escape command | Reported in the issue roundup. Check the active exit and resident prompt, then capture a short reproduction if the command still fails. |
Reporting something that is not here
The developer publishes a support address and an official Discord — those are IllFonic’s channels, not this site’s, and a report there reaches people who can act on it. What makes a report usable is specificity: the platform and build you are on, what you were doing when it happened, whether it reproduces, and any error text verbatim. A report at that level is worth more than a dozen saying the game is broken.
Frequently asked questions
Is there a bigger patch coming?
Hotfix #1 says a larger patch is being worked on, but that announcement supplies no date or item list. Check the current official announcements before relying on a community launch-day prediction.
Why is the crash entry so vague?
Because the hotfix itself is. It says numerous crash fixes without listing them, which is a real limit on what anyone can tell you about whether your specific crash is covered.