01
Label the build
Write the version the note was checked against before you write the effect. If no version can be named, the entry is a lead rather than a reference.
Version ledger / relics
A relic list is only honest when the unresolved stays blank.
Relic detail moves during Early Access, and part of it stays unfinished on purpose. This page separates confirmed effects, starter relics, beta-only behavior, and blank fields, so you know which relic note you can act on.
| Relic data problem | Why it exists | How to handle it |
|---|---|---|
| Balance passes | Relic values move with the same updates that rework cards | Re-read a relic note after each dated update rather than once at the start of a run. |
| Starter relics | Granted when a run starts, so they never appear as a reward node | Judge them as part of the character instead of as a pick. |
| Unfinished fields | Some relic detail has no published effect text for the current build | Leave the gap empty. A plausible invented effect is worse for you than a blank. |
Categories
Four ways a relic entry should be handled
| Category | Meaning | Page rule |
|---|---|---|
| Confirmed effect | The effect is stated in full for the current build. | Usable as a run reference. |
| Starter relic | Tied to a character or starting loadout. | Keep separate from reward relics. |
| Beta or branch | Behavior belongs to a beta or branch-specific build. | Do not assume it matches the default game. |
| Unresolved entry | No effect text is published for the current build. | Leave the field empty; do not guess it. |
Where Relics Come From
What each relic origin can actually prove
Most relic arguments are two people citing different kinds of evidence as if they were the same kind. This table separates them before anyone ranks anything.
| Evidence type | What it contains | What it can prove |
|---|---|---|
| The pickup text in your current build | The effect string the game shows you when the relic enters your run | Proves the effect for that build only. Name the build with it. |
| A dated update note | That something moved on a stated day | Proves a change happened. It does not settle the value the change left behind. |
| A community list with no date | Someone saw a relic at some point | Proves nothing about your build. Treat it as a lead to check rather than a reference. |
| An unresolved entry | Nothing published for the current build | Proves nothing. The correct output is a blank cell rather than a guess. |
Reconciliation
Four steps, in order, for any relic note
02
Classify it
Put it in one of the four categories below: confirmed, starter, beta or branch, unresolved. A relic that spans two of them gets two lines rather than one blended sentence.
03
Split starter from reward
A starter relic arrives with the character and never appears as a reward node. Judge it as part of the loadout, then judge reward relics against the route that offers them.
04
Re-read after a dated update
Balance passes land with the same updates that rework cards, so a note that was true in April is a claim about June. Re-check the line the patch touched rather than the whole page.
The June boundary
What one major update moves under a relic note
Major Update #2 (v0.107.1, 19 June 2026) is a single dated entry that touched four systems at once. The roster of what it covered is recorded on the patch page; what follows is which part of a relic note each part of it reaches.
| System it touched | What the patch record says | Effect on a relic note |
|---|---|---|
| Balance changes | Yes, a value pass | Re-read every relic note written against the launch build; anything before v0.103.2 is historical. |
| Multiplayer card batch | Yes, plus new art and animations | A relic that only matters in co-op inherits the beta label of that content. |
| Boss replacement | Aeonglass arrives at v0.107.1 | Relic value against an encounter is a claim about that encounter rather than about relic power. |
| Workshop and Bestiary additions | Added with the same update | Additions are not adjustments. A new entry does not make an old one current. |
FAQ
Relic data questions
Why does relic advice go stale so quickly?
Relic value is tied to the balance pass that last touched it, and those passes land with the same updates that rework cards. Advice that carries no version label gives you no way to tell which side of that boundary it sits on.
What is an unresolved relic entry?
An entry whose effect text is not yet fully revealed or confirmed for the current build. It should stay blank rather than be filled with an invented effect.
Should I treat starter relics like reward relics?
No. A starter relic is part of a character's starting loadout and behaves differently from a relic you find mid-run. Keeping them separate makes relic advice clearer.
How do I know if a relic effect changed?
Compare the entry against what the current build shows when you pick the relic up. A mismatch means the entry is for an older version.
Why does relic advice need a version boundary?
Early Access balance changes move relic value. A relic that was strong in one update may behave differently in the next, so advice must be tied to a version.
Value depends on the situation
A relic’s usefulness depends on your character, deck, and route. The ledger keeps the facts separate so a value judgment never masquerades as a confirmed stat, the same discipline that keeps the current boss roster apart from a historical name.
Last updated: 4 September 2026 · Version boundary: Beta Patch v0.111.0 (August 14, 2026)