Version ledger / 2026-08-27
A catalog is only useful when its boundaries are visible.
This page records the differences that can change an answer. It keeps current details, beta material, historical entries, and unresolved fields in separate lanes.
Track card version changes
Which update boundary does a card note belong to?
02 / RelicsTrack relic boundaries
Confirmed effects, starter relics, and unfinished fields.
03 / BossesCurrent roster vs history
Separate a changed encounter from an old name.
04 / AchievementsAvailability status
Playable, file-discovered, and Epoch separation.
| Boundary | Dated entry | What moved | Editorial consequence |
|---|---|---|---|
| Major Update #1 | v0.103.2 (April 17, 2026) | First large Early Access content pass on the main branch | Anything written against the launch build is historical rather than current. |
| Major Update #2 | v0.107.1 (June 19, 2026) | Multiplayer card batch, new art, and the newest boss encounter | Boss preparation and party rules need the newer label together. |
| Beta branch | v0.108.0-v0.111.0 (July 3 to August 14, 2026) | Five beta patches, then a scheduled pause for a team break | A beta version is not the build a default-branch player runs. |
| Achievement data | No public list endpoint | The stats schema requires a publisher key | Keep any achievement total unconfirmed until it names a build. |
Status vocabulary
How each entry should be handled
| Status | Meaning | Page rule |
|---|---|---|
| Current | Matches the newest dated update note | Use it, and name the version it was checked against. |
| Beta | Marked as beta or branch-specific | Keep separate from default behavior. |
| Historical | Changed or removed in an update | Retain only when it explains a player question. |
| Unresolved | Detail is not published for the current build | Do not fill the gap with an invented value. |
Using the ledger
How to use this ledger
Start from the dated entry, not the headline. Every row in the catalog names the build it was checked against, and the site-wide boundary for every page on this project is the newest dated entry: Beta Patch v0.111.0 (August 14, 2026). If you play on the default branch, beta rows do not describe your game yet. If a page quotes a number, the date that number was read should sit beside it.
There is not much to check against, and that is on purpose. Factual fields trace to the public Steam listing for appid 2868840, read through the store details and review endpoints, or to a developer-published patch note, with the read date written next to the value. Fields the store schema does not expose, such as a public achievement list, stay in the unresolved lane instead of being estimated.
Pages are reviewed when the game changes or when a catalog discrepancy affects an answer, and every article carries a visible update date at the bottom. Between reviews a page can lag the live build, which is what the boundary line is for: compare the date under the article with the newest dated entry before trusting a detail.
When a value changes, the old entry is not quietly overwritten. It moves to the historical lane with the build that removed it, so a reader anchored to an older patch can still find the number they remember and see why it stopped being current. When a value was never published, the page reports the absence. A blank that says what it checked stays useful; an invented number never does.
The first useful comparison
Card and relic pages need more than a list. They need a visible distinction between what the catalog says, what the current branch displays, and what a player can safely use during a run.
Last updated: September 7, 2026 · Version boundary: Beta Patch v0.111.0 (August 14, 2026)