Review record: 1.0.503 · 2026-08-24
3 official changes checked; No direct dependency was found in the published scope.
Released 2026-08-20. 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 contains three bug fixes. The Frost rework and new Pet, Seed, and damage-breakdown systems were introduced one day earlier in V1.0.499 and remain the current gameplay baseline.
What changed
| Item | Change | What it means for your build |
|---|---|---|
| Multiplayer Relic sharing with pets Fixed | Players carrying pets and players without pets can share Relics with each other again. | Co-op item routing and support decisions. It does not change Relic effects or route rankings. |
| Shop Relics and the pet backpack Fixed | Shop Relics can no longer be incorrectly placed into the pet backpack while a pet is being carried. | Inventory behavior only. Use the pet backpack as temporary storage under the current in-game rules. |
| Legendary Lightning Javelin + Legendary Air Cannon Fixed | Fully charged Lightning Javelin shots now correctly reduce the Legendary Air Cannon Battle Skill cooldown. | Restores the published weapon interaction. Lightning and Battle Skill routes should retest the fixed cooldown loop before changing their loadout. |
Build routes that still fit after this patch
- V1.0.499-adjusted Build routes — V1.0.503 lists bug fixes only. The current item data and Frost route remain based on the V1.0.499 balance baseline.
How this patch changes build decisions
The Pass the Fear 1.0.503 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.