Review record: 1.0.462 · 2026-08-04
4 official changes checked; No direct dependency was found in the published scope.
Released 2026-07-28. 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。
What changed
| Item | Change | What it means for your build |
|---|---|---|
| Disruption Buffed | When Disruption is triggered, monsters now take one instance of direct damage. | Lightning routes — Disruption is now a damage event, not only a status. |
| Thunder Dragon's Inverse Scale Reworked | Before: Lightning Damage Lightning Transmutation Damage | Lightning routes; the scaling category changed. |
| Thunder Dragon's Claw Nerfed | Before: Transmutation Damage +50% On Ultimate: Transmutation Damage +10% | A large flat multiplier became a conditional one. Re-evaluate before building around it. |
| Weapon part shop replacement Reworked | Fixed: with Battle Scar Lover's Betrayal, buying a Weapon Part while holding a Weapon and a Weapon Part no longer replaces the existing part. | Shop routing. The old behaviour was a bug, not a technique. |
Build routes that still fit after this patch
- Lightning and Disruption routes — Disruption became stronger, but Thunder Dragon's Claw became conditional. Check the combined effect in your next runs.
What to watch after this patch
These are the interactions worth checking in your next runs. Use the practical effects below rather than treating an exact damage number as guaranteed.
- Whether Lightning routes are net stronger or weaker after Disruption's direct damage and the Claw nerf land together.
How this patch changes build decisions
The Pass the Fear 1.0.462 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.