Reviewed patches
- 1.0.466 — Update 7.30 (2026-07-30) — Trigger caps arrive, and Physical builds get a damage multiplier of their own.
- 1.0.462 — Update 7.28 (2026-07-28) — Disruption gains direct damage; two Thunder Dragon relics change.
The August 1 developer letter: what is coming for builds
On August 1 the developers posted "A Letter to Our Players" — a roadmap letter rather than a patch. Four of its announcements matter directly for build content:
- A Training Range is in development, with damage dummies shown in work-in-progress footage. This is the single biggest item on the list: the game currently ships no way to measure damage, which is why no site — including this one — can honestly rank builds by DPS. When the range ships, measured comparisons become possible for the first time, and we will retest the blueprints against it.
- Blood Moon difficulty content is expected within a week, with some boss abilities behaving differently and Golden Skin rewards for carried weapons and parts. The 1.0.450 notes already listed a Blood Moon difficulty, so this may be a rework or staged rollout — we will confirm exactly what changed when it ships rather than guess now.
- A Pet system is planned after the Blood Moon work completes. The letter frames it as the answer to temporary inventory requests: pets add carrying space and are collectible during runs.
- Relic balance adjustments will continue, alongside a free DLC and smaller updates adding new weapons, relics, and playable characters. Translation for build guides: the tier list and route pages will keep moving, and anything written this month should be treated as this month's answer.
The update cadence, and why it matters
This game is not on a monthly patch schedule. In the week following launch the developers shipped 1.0.457, 1.0.462, and 1.0.466 — three updates in roughly four days, two of which changed how damage loops resolve. That pace is unusually fast, and it is the single biggest reason most build content about this game is already stale.
It also tells you something about the team. The 1.0.466 notes open with an apology: they state that they assumed infinite stacking would always be satisfying, that this assumption was wrong, and that extreme builds were causing crashes and lost saves. Developers who correct a design assumption in public tend to keep correcting it, so expect more balance passes rather than a settled meta.
How to tell if a patch broke your build
Work backwards from your damage loop rather than reading the whole changelog. Identify the two or three things your run actually depends on — the relic that multiplies, the Tarot that re-triggers, the Transmutation you have been stacking — then search the change table for those names. Most patch lines will be irrelevant to you, and the one that matters is usually a category change rather than a number change.
Category changes are the dangerous ones. When 1.0.466 turned War Horn from "Fire Rate and Reload Speed for 20 seconds" into "permanent Bullet Attack increase", the relic did not get weaker or stronger in a way you could express as a percentage — it stopped being a burst uptime relic entirely. Any guide recommending it for Fire Rate became wrong, not merely outdated.
Why this page exists
A build guide without a version stamp is not actionable. The developers shipped three updates in the week after launch, and at least two of them changed how damage loops behave — trigger caps in one, a Transmutation scaling category in another. A guide written before those changes can be confidently, specifically wrong.
Every build page here names the patch it was reviewed for. When a patch touches something a route depends on, the route gets re-checked rather than quietly left up.
What we do not do here
We do not translate a patch line into a damage ranking. When the developers change a relic from a flat multiplier to a conditional one, that tells you the shape of the change, not its size — and the game ships no damage-testing dummy, so nobody can measure the size in public yet. The August 1 letter announces a Training Range in development; once it ships, measured claims become possible and the blueprints here will be retested. Until then, where the direction is clear we say so; where it is not, the change lands in the "not calling yet" list.
Start from the current best build blueprints, or test a revised loadout in the build planner, which scores synergy and flags conflicts.