Start by recording the exact symptom and installed build. Compare it with the developer’s dated fix before repeating a long match or Story Mode run.

Hotfixes 1.2.1 to 1.2.3 — October 28 to November 2

If your Scythe challenge was unreachable, DLSS-G dropped frames, or a controller could not reach the PC graphics performance settings, IllFonic lists those as fixed in Hotfix 1.2.1. If Laurie gained no XP, Eugene’s or Michelle’s loadout reset at login, or the Kitchen Knife level was missing from the challenge menu, it lists those as fixed in Hotfix 1.2.2, along with unnamed crash fixes. If DLC you bought was missing in Offline Mode, or the game kept crashing after 1.2.2, Hotfix 1.2.3 (November 2) lists purchased DLC in Offline Mode and more unnamed crashes as fixed. Restart the client so the update applies. Neither note says lost XP or reset loadouts are restored, and Kingy has not tested them. If it still happens, record the hotfix number and the character.

Patch 1.1.1 — October 16

IllFonic’s October 16 Patch 1.1.1 notes, checked October 18, 2026 UTC, report crash fixes on Xbox Series X|S, PS5 and PC: Xbox Quick Resume, Series X Performance Mode shaders, Grabbing, certain gameplay interactions, and DLSS/FSR frame generation. These are developer-reported fixes; Kingy has not reproduced them, and the note does not promise that every crash is resolved. Record whether the failure involved Quick Resume, Performance Mode, a grab or frame generation when reporting a continuing crash.

Quick triage

  1. Read the exact prompt or error before restarting.
  2. Note your platform, patch, mode, chapter, map, and role.
  3. Try the smallest repeatable version of the problem once more.
  4. Check the related guide before assuming the whole system is broken.
  5. If it still happens, keep the steps and result together when you report it.

A useful report is short: what you did, what you expected, what happened, and whether it happened again.

Patch 1.1.0 follow-up — October 6

1.1.0 reports PC shader precompilation and AMD, Story Mode, Execution and Xbox Quick Resume crash fixes, plus Series S stability work. These reports do not prove that every crash or performance issue is resolved. IllFonic’s October 6 Patch 1.1.0 notes. Kingy has not independently playtested these changes. Patch summary.

Official fixes in Patch 1.0.1

The Day One patch lists fixes for matchmade party members being dropped, Police NPC pathing, Residents reaching Escapes, challenge and achievement tracking, and several Michael interactions. It also includes stamina, map rotation, Repair Kit, interaction, crash, and scoring changes.

Read the Patch Index for the dated summary. A patch note tells us what the developer changed; it is not an independent test of every platform or symptom.

Reports worth reproducing

Story and challenge progress

Launch-week discussions describe chapters, challenges, scores, or rewards failing to save or register. Treat these as reproduction leads, not universal behavior. Start with the Story Mode Challenges checklist and record the exact objective text.

If a challenge fails to complete:

  1. Record the chapter, objective, platform, and patch.
  2. Note whether you restarted, died, or left before the end screen.
  3. Capture whether the main chapter completion, optional challenge, or neither appeared.
  4. Repeat once while changing only one variable.
  5. Add the result to the challenge guide.

Matchmaking and party problems

Separate the queue problem from the match problem. Note whether the party fails before the lobby forms, when the match begins, or after a player joins. The Cross-Play and Party Help page covers setup; this page is for the symptom and its repeat steps.

Crashes or missing interactions

Save the location, role, objective, nearby players, and the action that stopped working. A single missing prompt can be a local interaction state; a repeatable crash needs its own platform and reproduction details. Check Single-Player Story for chapter context and FAQ for the common setup questions.

Report template

Copy this when you need to describe a problem:

  • Platform and input:
  • Patch or build:
  • Mode, chapter, map, and role:
  • Steps:
  • Expected result:
  • Actual result:
  • Repeated: yes / no

What the labels mean

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

Do not turn one crash, missing reward, or strange NPC route into a universal rule. Keep the build, the steps, and the second result with the claim.

Patch 1.0.2: check before repeating a failed run

At the 1.0.2 publication, Xbox Series S optimization remained open; 1.0.4 later reports crash fixes and a graphics-mode change in its dated section below. This earlier patch also targets missing interaction prompts; compare your exact trigger with the official notes. Record a continuing failure on 1.0.2 separately from the launch-week reports above.

Patch 1.0.4: Xbox crashes, Loomis and graphics settings

IllFonic reports memory- and GPU-related crash fixes for Xbox Series X|S, a Performance Mode adjustment on Series X, and removal of the Quality/Performance toggle on Series S. Series S now has one graphics mode capped at 30 FPS. It also reports a fix for the performance hit or crash when Loomis spawns, plus fixes for some crashes after Story Missions or while loading into matches across platforms. More optimization is planned; the notes do not say every crash is fixed.

If a crash continues, check the installed version and record platform, Series X or S model, graphics mode where available, whether Loomis spawned, and whether the crash followed a Story Mission or match load. Preserve the exact symptom for support; Kingy has not reproduced these fixes on an installed build. The same patch addresses the 1.0.3 grab regressions; see the Patch Index.

Fixes and remaining limits in patch 1.0.3

The developer reports crash/optimization fixes, restored trophy and achievement unlocks for private-match hosts, and continued Passive Challenge progress after Prestige. The locked Passive Challenge appearance was still open in 1.0.3; 1.1.0 now reports a fix. Kingy has not tested individual account tracking.

The patch also lists fixes for executions after an apparent grab escape, low-durability Bolt Cutters failing on containers, movement loss after certain grab interactions, and Shape Jump or Killer Sense remaining on cooldown. Record your patch and reproduction steps if a symptom remains. A listed fix does not prove every similar report has the same cause.