Halloween: The Game known issues and safe checks

Install Patch 1.1.1 for newly named crashes involving Quick Resume, Series X Performance Mode shaders, grabs, and DLSS/FSR frame generation. For missing challenge progress, check the action, challenge owner, and saved result instead: this hotfix does not announce new counter fixes. Use the symptom table to choose your next step.

Start with the problem blocking your session

New crash fixes in 1.1.1

The October 16 Steam announcement names Xbox Series X|S Quick Resume, a Series X Performance Mode shader crash, a crash while Grabbing, and crashes with DLSS/FSR frame generation. It also lists certain gameplay-interaction crashes and additional unspecified fixes across Xbox, PS5, and PC.

After updating, retry the same action once. On PC, if frame generation is involved, compare with only that option disabled. For an Xbox resume problem, quit fully and relaunch so the next check starts from a fresh session. These are our diagnostic steps based on the named triggers; keep the original setting and on/off result if you report a recurrence.

Earlier performance and crash fixes

The full release notes identify these additions:

• Specific AMD hardware, Story Mode, and execution-cinematic crashes: several cases fixed in 1.1.0; not every historical AAR report is individually named.
• Xbox Series X|S Quick Resume crashes: fixed for the named resume condition. Series S also receives stability improvements and volumetric fog.
• PC startup: shaders now precompile, DLSS-G support is added, and DLSS/FSR/XeSS performance improves. The notes do not establish device-specific FPS or universal GPU support.

Historically, 1.0.4 addressed Loomis reinforcement performance, Story Mission completion and match-loading crashes, and Xbox memory/GPU cases. Its Series S single-profile 30 FPS setting is historical graphics context; 1.1.0 does not announce a new frame-rate cap.

For a recurrence, retain device specifications, settings, and the transition immediately before the crash. Send the focused report to IllFonic's published contact, [email protected]. See platforms and PC requirements for the dated requirements.

Challenges, achievements, and progression

Patch 1.1.0 fixes Purely and Simply Evil trophy tracking. Pumpkin Smasher and Heavy Handed were reported in the September 17 post but have no named 1.1.0 fix. Do not label all achievements fixed or change platform conditions without evidence.

Passive Challenges no longer appear locked after Prestige in 1.1.0. This updates the display issue remaining after 1.0.3's progress fix. The new patch also fixes several Progressive tracking cases and improves Passive, Progressive, and Story difficulty; it does not list every affected goal or replacement count. Selected numeric targets remain sourced to 1.0.3.

The September 17 concerns included Chapter 2 Challenge 6, Chapter 4 Challenges 5–6, Chapter 5 Challenge 6, and named character Progressive tasks. Treat them as earlier reports covered only by broad improvements until the exact route is retested. Story Challenges now show a failure notification: save that notice and the final result.

Earlier named Story fixes in 1.0.2 and the Private Match host award fix in 1.0.3 remain historical context. Use story challenges and achievements for focused retries.

Gameplay and map fixes by patch

The September 17 status post identified the first three issues below; the 1.0.3 notes now give them specific fix lines:

• Shape Jump or Killer Sense becoming stuck on cooldown for the remainder of a match: fixed in 1.0.3.
• A Civilian losing movement after breaking free, or while trying to enter a vehicle or ride a bicycle during a grab: fixed in 1.0.3 for the named cases.
• A Civilian apparently breaking free but still being executed: several causes fixed in 1.0.3.
• A Bloodthirst Level 3 grab being much harder to escape than intended, or fall damage after breaking free on uneven ground: fixed for these named cases in 1.0.4.
• Cop respawn unable to interact with Residents: fixed in 1.1.0.
• Stalk marker duration scaling, East Haddonfield CB Radio randomization, certain item pickups, escape collisions, and Gate Overgrowth remaining after clearing: named 1.1.0 fixes.
• Residents appearing on rooftops: previously acknowledged; no specific 1.1.0 fix. General NPC navigation improvements are not confirmation for that exact case.

If one happens, record the smallest useful sequence: role, map or chapter, nearby landmark, interaction, result, platform, and patch shown by the client. Avoid presenting a one-time workaround as a permanent fix. For an objective-related route, the maps hub and escape guide explain what to check after the match is stable again.

A five-minute report that helps

1. Check the official news index for a newer patch or status post.
2. Record the date, platform, device details, mode, map or chapter, and the client patch if visible.
3. Repeat only the named interaction once if it is safe to do so; do not change several settings and variables at once.
4. Save a short clip or screenshots showing the action and result.
5. Send the smallest reproducible report to the official helpdesk, or retain it for the next patch retest.

The 1.1.1 bulletin was checked October 19, 2026. Earlier sections retain their explicit 1.1.0 and historical patch scope; 1.1.1 does not add a named achievement or Story tracking correction. These are announcement statuses and suggested checks, not wiki client-test results.