On this page
DIRECT ANSWER
One hotfix so far, published September 5
Early Access Hotfix #1 — September 5, 2026
This landed during the Deluxe early access window, one day after those players got in and three days before the standard release. That timing explains its shape: it is a stability pass on the faults that surfaced the moment a real player base arrived, not a balance or content update.
- Multiple crash fixes, described only as numerous rather than itemised
- Several challenges that were failing to track correctly
- Offline play, which the login queue system had been interfering with
- A missing prompt for Michael to stand up after being knocked down
- Xbox Series S — rendering faults in Performance Mode on certain displays
Read the crash entry carefully
The note says numerous crash fixes without listing which crashes. That is a meaningful limit rather than a nitpick.
If you are still crashing after this hotfix, you are not necessarily hitting a known and fixed fault — you may be hitting an unreported one, which makes your platform, build version and any error text worth capturing before you ask for help.
The challenge tracking fix is partial by its own wording
The entry covers challenges that were failing to track, not all challenge tracking. Some challenges have conditions that are simply stricter than players assume, and those look identical to a bug from the outside.
Before reporting one as broken, it is worth confirming the condition was actually met — the progression material describes passive, progressive and single-player challenge types with different completion behaviour.
A larger patch was announced without a date
The same post says a bigger patch is in progress addressing issues raised by the player base. No date, no scope and no item list accompanied that statement.
Anything you read specifying what the next patch contains is not sourced from the developer, and no follow-up has been published since. This page is updated against the official news index rather than against community summaries.
Where to report something this list does not cover
The developer publishes a support address and community entry points, including an official Discord. Those are the developer’s routes, not this wiki’s.
A useful report names your platform and build, what you were doing, whether it reproduces, and any error text — a description at that level is far more actionable than a note that the game crashed.
Retest the named behavior, not a broader assumption
Each item in this patch has a different observable result. For the offline issue, the relevant behavior is offline entry interacting with the login queue. For Michael, it is the missing get-up prompt after being downed. For the Series S item, it is incorrect rendering in the specified mode and display conditions.
A successful retest of one does not verify the others. Likewise, seeing a related but different symptom does not prove the original correction was absent. Keep the reproduction narrow enough that another player or support team can tell which behavior you mean.
The comparison below translates the scope of the announcement into a report checklist. It is not a claim that this wiki performed these tests, and it does not add a new fix to the official list.
| Hotfix item | Useful evidence for a remaining case |
|---|---|
| Crash corrections | Exact failure point, error text, platform and build. |
| Challenge tracking | Displayed objective, eligible selection and before/after counter. |
| Offline queue interaction | Selected offline option and the stage at which a queue appears. |
| Michael get-up prompt | The downed state and whether the expected prompt is absent. |
| Series S rendering | Console model, Performance Mode, display setup and visible defect. |
Keep installed versions with before-and-after reports
A post dated after September 5 does not by itself prove the author installed this hotfix. Update availability, completion and the running game’s build are different things. Include the version actually shown by the installed game or platform when comparing reports.
If you are documenting a change, retain the original symptom and record what happened after the available update. Say whether it stopped, persisted or changed form. That is more informative than replacing the original report with “fixed” and losing the circumstances.
Do not infer a new balance value, performance gain or retroactive reward repair from a note that does not state one. This announcement contains no frame-rate measurements, patch download size, numerical balance adjustments or promise to backfill every missed challenge reward. Those would require separate evidence.
For a remaining issue, the official support route is a better next step than repeated destructive troubleshooting. Preserve saves and settings, avoid unofficial replacement files, and share the minimum information needed to reproduce the fault.
Frequently asked questions
Was there a day-one patch?
Nothing published supports one. Hotfix #1 on September 5 predates the September 8 standard release, and no separate launch-day note has appeared on the official news index.
Does the Series S fix apply to Series X?
The entry names Series S in Performance Mode on certain displays. It does not mention Series X, so do not assume it covers that hardware.
Is this the complete patch history?
It covers what the developer has published on its official news index. Nothing automated monitors that feed, so check the source link before relying on this for a current build.