Review record: 1.0.491 · 2026-08-10
3 official changes checked; No direct dependency was found in the published scope.
Released 2026-08-07. Everything in the change table below is quoted from the official patch notes; the route interpretation is ours and should be checked in-game. developer announcement。
The official announcement lists three bug fixes and does not list weapon, Relic, Tarot, Hunter, Build, or damage-system balance adjustments. Build recommendations are carried forward after review; that describes the published scope, not every hidden mechanic.
What changed
| Item | Change | What it means for your build |
|---|---|---|
| Corpse Collector's Arrow Rain Fixed | Fixes an issue where players could be accidentally one-shot by Corpse Collector's Arrow Rain. | Encounter survival and bug behavior only. The announcement lists no weapon, Hunter, Relic, Tarot, route, or damage-system balance change. |
| Screen resolution black bars Fixed | Fixes an issue where black bars appeared on certain screen resolutions. | Display compatibility only. It does not change build recommendations or Planner logic. |
| Steam Deck compatibility Fixed | Fixes some compatibility issues on Steam Deck. | Platform compatibility only. It does not change item effects, Hunter skills, or route rankings. |
Build routes that still fit after this patch
- Existing Build recommendations carried forward after 1.0.491 review — Update 8.7 lists bug fixes only and no weapon, Relic, Tarot, Hunter, Build, or damage-system balance changes, so the current Build blueprints remain the working starting point.
How this patch changes build decisions
The Pass the Fear 1.0.491 patch is mainly an interaction fix, not a new route ranking. When your run touches pet backpacks, multiplayer Relic sharing, or the Legendary weapon cooldown interaction, first check whether the bug still reproduces. Do not replace a stable Hunter, element, and weapon together just because the patch title sounds important.
If the fix changes a real choice, record the Hunter, weapon, trigger condition, and game version, then return to the Planner and change one variable at a time. If it has no effect, keep the current route and mark the interaction for observation. That makes a patch page a decision entry point after an update, rather than a news summary detached from the run.
Use a simple reading order: confirm the change in the official table, read the route-impact note, and then verify the trigger in your own run. When the fix does not change the core loop, keep the stable choice from the existing guide. When it does change an interaction, isolate the affected item, route, or Planner setup and review that piece instead of rewriting every build. Keep screenshots, test notes, and the update version together so future edits can distinguish a fixed bug from a changed balance rule.
How to use this page
If a build guide anywhere — including ours — does not name the patch it was written for, it is not telling you enough to act on. Check the version stamp, then check whether anything your damage loop depends on appears in the table above.
Test a revised loadout in the build planner, which scores synergy and flags conflicts, or start from the current best build blueprints. All patch reviews are listed on the patch notes index.