This page collects official patch notes alongside player reports. A report is a lead for testing, not proof that every player will see the same result. Include your platform, build, mode, and steps when you report a problem.

Start here

If a problem blocks a match, save the exact wording on screen before restarting. Then check the Patch Index and compare the issue with the current build.

A useful report includes:

  • Platform and input method
  • Patch or build number
  • Story chapter or multiplayer mode
  • Map, role, and objective state
  • The exact action that caused the problem
  • What you expected and what happened
  • Whether it happened again

Official fixes in Patch 1.0.1

The Day One patch lists fixes for party members entering a matchmade lobby, Police NPC pathing, Residents reaching Escapes, challenge and achievement tracking, and several Michael-related interactions. Read the Patch Index for the full change list.

A patch note tells us what the developer changed. It does not guarantee that every related symptom is fixed on every platform.

Story and challenge tracking

Players have reported chapters, challenges, scores, or rewards failing to save or register. Treat these as open reproduction leads until they can be repeated on a named build.

If a challenge fails to complete:

  1. Record the chapter, objective text, and difficulty or mode.
  2. Note whether you restarted the chapter or left after dying.
  3. Capture the end-screen result if it appears.
  4. Try the same objective again without changing the route.
  5. Add the result to the Story Mode Challenges page.

Matchmaking and party problems

Queue length, party transfer, and cross-play reports belong together because the first useful detail is whether the problem happens before or after the lobby forms. Check Cross-Play and Party Help for party setup, then record the queue state separately from any in-match problem.

What still needs confirmation

These labels keep the page readable:

  • Officially fixed: named in a developer patch note.
  • Player report: described by a player but not reproduced here.
  • Tested by the wiki: repeated on a named build with steps recorded.
  • Open question: reports conflict or do not contain enough detail.

Do not turn a single crash, missing reward, or strange NPC route into a universal rule. Add the report, the build, and the result of a second test instead.