Decision lab / patches
A change list is not a decision.
Patches describe what changed. Players need to know what to do differently. This page keeps the dated entries and the run decision each one actually alters.
| Version | What the note says it touched | Player consequence |
|---|---|---|
| Major Update #2, v0.107.1 (June 19, 2026) | A batch of new multiplayer cards, new art, and animations for the newest boss | Re-check party rules and boss preparation together; the same note covers both. |
| Beta v0.109.0 (July 17, 2026) | Translation work began alongside balance changes | Localized terms can lag the build; re-check any non-English card name. |
| Beta v0.109.1 (July 26, 2026) | One hotfix aimed at a specific localization issue | A small version bump can be one narrow fix rather than a rebalance. |
| Beta v0.110.0 (July 31, 2026) | Earlier card reworks were undone and new reworks added | Card advice can flip twice inside a month, so date every note you keep. |
| Beta v0.111.0 (August 14, 2026) | Newest dated beta entry at the time of writing | Past this label, treat a change claim as unverified until a note exists. |
Impact model
Three steps from patch to decision
| Step | Question | Output |
|---|---|---|
| Changed system | Which system the patch touched | Start here to find what to re-check. |
| Affected content | Cards, relics, Bosses, events, or multiplayer touched | Narrow the change to what you actually use. |
| Run decision | The practical choice the change alters | Rewrite only the decision that changed. |
Dated index
Which page owns which consequence
A patch note is one line; its consequences are spread across the site. This is the routing table, so a dated entry can be followed to the page that works the decision out. The status vocabulary behind it lives on the version ledger.
| Dated entry | What the note covers | Where the consequence lands | Worked out on |
|---|---|---|---|
| Major Update #1 (v0.103.2, 17 April 2026) | The first large content pass on the main branch | Card and relic notes written against the launch build are historical | /cards -> |
| Major Update #2 (v0.107.1, 19 June 2026) | Multiplayer card batch, new art, the newest boss encounter, Workshop and Bestiary additions, enemies, balance | Boss preparation and party rules move together | /bosses -> |
| Beta v0.109.0 (17 July 2026) | Translation work alongside balance changes | Localized card and event terms can lag the numbers beside them | /events -> |
| Beta v0.110.0 (31 July 2026) | Earlier card reworks undone, new reworks added | A card note can be wrong twice inside a month | /relics -> |
| Beta v0.111.0 (14 August 2026) | Newest dated entry in this record | Beyond this label, a change claim is unverified here | /version-ledger -> |
Cadence, measured
How far apart the entries actually are
Intervals below are arithmetic on the dates already in this record rather than new observations. They matter because a guide’s shelf life is set by the gap between passes rather than by how confident it sounds.
| Interval | Elapsed | What it says about advice age |
|---|---|---|
| Launch 5 March → Major Update #1 | 43 days | The launch build was the reference point for six weeks of advice before it was superseded. |
| Major Update #1 → Major Update #2 | 63 days | The two major passes are the boundaries most guides actually need. |
| Major Update #2 → beta window opens | 14 days | A two-week gap between a major update and the first beta patch of the run. |
| v0.109.0 → v0.109.1 → v0.110.0 | 9 days, then 5 | Two of the five beta patches landed inside a fortnight of each other. |
| v0.110.0 → v0.111.0 | 14 days | Five beta patches across 42 days (six weeks), counted from v0.108.0 on 3 July. |
| After v0.111.0 | A scheduled pause for a team break | This record stops at 14 August 2026. Nothing later is dated here, and this page does not claim nothing later exists. |
What a note does not say
Four gaps a change list leaves open
| Gap | What is missing from the note | How to handle it |
|---|---|---|
| Which branch | Notes are dated but seldom labelled by branch | Take the newest dated beta entry as the boundary of what any page here can claim. |
| What a fix is | A one-line bump can be a single localization hotfix rather than a rebalance | Read v0.109.1 as an example: small version delta, narrow change. |
| Whether a system is finished | The store listing still carries the Early Access genre tag | Unsettled status is part of the patch record rather than a caveat bolted onto it. |
| Achievement changes | No public achievement list is exposed to the store endpoint | A patch cannot be checked against an achievement roster from outside; see the achievement status page |
FAQ
Patch impact questions
How do I read a patch as a player rather than as a change list?
Map each change to the system it touched, the content it affected, and the run decision it alters. A raw change list is not the same as knowing what to do differently.
Has the patch pace changed?
It slowed after mid-August. Beta patches earlier in the run were close together (v0.109.0 on July 17, v0.109.1 on July 26, v0.110.0 on July 31), and v0.111.0 on August 14 is the newest dated entry, followed by a scheduled pause for a team break rather than a quiet week. A slower cadence does not mean the data settled; it means each patch carries more.
Does a patch note tell me which branch I am on?
Rarely. Notes are dated but seldom labelled by branch, so take the newest dated beta entry, v0.111.0 from August 14, 2026, as the boundary of what this page can claim.
Does a patch invalidate old card and relic rankings?
When a patch adjusts balance values, an old ranking no longer matches current value. Re-check card and relic advice against the version you are playing.
Which systems did the major update touch?
The update covered Workshop and Bestiary additions, the Boss replacement, enemies, multiplayer, and balance changes. Each of those changes a different run decision.
How do I stay current between updates?
Track the version label on any advice you use, and re-check a system after each update rather than trusting a summary written against an older build.
What came after Beta v0.111.0?
Nothing dated in this record. The entry after 14 August 2026 is the scheduled pause for a team break, and this page stops there rather than guessing what a later patch did. If a guide claims a change past this label, it is not citing this site.
The ledger keeps it current
Version changes touch cards, relics, Bosses, and multiplayer together. Read the ledger to keep a patch from turning into stale advice.
Last updated: 4 September 2026 · Version boundary: Beta Patch v0.111.0 (August 14, 2026)