On this page
DIRECT ANSWER
One symptom sits underneath most of these reports
Check the summary screen before you check the counter
This is the one observation worth making before anything else, because it decides which problem you have. When a chapter or match ends, note whether the screen draws at all — the rating, the score breakdown, the rewards. Players reporting lost progress consistently describe that screen coming up empty, or being skipped entirely as the game moves straight on.
If the summary is blank, the result was never committed and nothing downstream of it can be expected to save. If the summary displays normally and one specific objective still refuses to advance, you are looking at challenge tracking instead, which has its own conditions and its own page.
What players report losing
| Reported symptom | What players describe |
|---|---|
| Chapter repeats instead of advancing | A completed chapter restarts and the following chapter stays locked, including from the Prologue onward. |
| Challenges complete in-match, then do not count | The completion prompt appears during play, but the objective still reads as unfinished afterwards. |
| A Steam achievement fires while in-game credit does not | The platform achievement unlocks even though the chapter shows no stats and the challenge stays open. |
| Multiplayer wins do not raise the total | Matches won as Michael are described as not incrementing the count shown in the Graveyard. |
The two workarounds being passed around, and what they are worth
Two suggestions recur in the same threads. The first is to return to the main menu after each chapter rather than letting the game roll straight into the next one; one player reports that progress then saved correctly. The second is to play the campaign in offline mode, on the reasoning that the fault is server-side, with progress said to carry back over when you return online.
Both are single-player reports, not tested procedures. Neither has been confirmed by the developer, and the offline explanation is a player’s inference about the cause rather than a published one.
What the patches actually claim
Two patches have shipped and both touch this area without naming it. Early Access Hotfix #1 on September 5 lists fixes to several challenges that were not tracking properly. Patch 1.0.1 on September 8 lists additional fixes to challenges and achievements that were not tracking, and separately names one specific case — the achievement for completing Chapter 5 not being awarded.
Read the shape of that. The developer has repeatedly acknowledged tracking faults, has fixed named instances, and has told players it will continue identifying outliers. What no published note describes is a summary screen that fails to render and commit a result. If that is your symptom on a current build, it is not covered by an existing entry, which makes it worth reporting rather than waiting out.
What makes this report usable
Whether the summary screen drew, and what it showed if anything. The mode — story chapter or multiplayer match — and the chapter number where it applies. What you expected to be credited: chapter unlock, a named challenge, a win count. Whether a platform achievement unlocked while the in-game credit did not, since that pairing is specific and easy to verify. And whether it reproduces every time or only sometimes.
Include your platform and build. Reports go to the developer’s support address or Discord; this site does not run a support inbox and cannot restore progress.
Frequently asked questions
Will progress lost this way be restored later?
Nothing published addresses retroactive credit. Both patches describe correcting tracking going forward, not backfilling rewards that failed to record.
Is this the same as challenges not tracking?
Not usually. Challenge tracking covers a counter that will not move while the match otherwise completes normally. This page covers the case where the result screen itself comes up empty and nothing from that session is credited.
Does replaying the chapter fix it?
Players report replaying and hitting the same result, which is what makes the loop. Repeating a chapter is worth one attempt to confirm it reproduces, not several.