Short answer
Patch 1.0.1 includes additional fixes for challenges and achievements that were not tracking properly. The official wording is not a promise that every objective is now reliable. If a challenge, achievement, or story chapter still fails to register, preserve the exact condition and result instead of repeating a whole run without a record.
Compare the official 1.0.1 notes with the current Steam challenge discussion and any platform-specific report. The latter is a player lead, not a universal reproduction.
Track the failure precisely
| Symptom | Current reading | Capture next |
|---|---|---|
| Challenge stays incomplete | Needs verification | Exact wording, chapter or mode, difficulty, and the action that should have completed it. |
| Achievement does not unlock | Official fix listed | Platform, result screen, account state, and whether the linked challenge registered. |
| Chapter or result restarts | Community report | Chapter, checkpoint, platform, and what appears after closing and reopening the game. |
| Progress appears after leaving | Useful lead | Whether the result was visible before leaving the chapter and whether it persisted after relaunch. |
One clean verification run
- Copy the objective exactly.“Alert nobody,” “kill,” “execute,” and “complete the chapter” are different conditions.
- Start from a clean state.Do not mix a stealth test with a full-clear test when the goals point in opposite directions.
- Finish the result flow.Watch for the completion screen before starting another chapter or closing the game.
- Record the build and platform.A post-patch PC result should not silently become a claim about PlayStation or Xbox.
Challenge tracking FAQ
Did patch 1.0.1 fix all challenge tracking?
No. The official notes say additional fixes were made and that further outliers may still be identified. Treat a repeated failure as a current, versioned report.
Why did my story challenge not count?
Possible explanations include a missed wording condition, an incomplete result flow, or a tracking problem. Preserve the exact objective and platform before choosing one explanation.
Should I restart the whole chapter?
Only after recording the failed result. A clean replay can test the condition, but repeating an unrecorded run makes it harder to tell whether anything changed.