Version ledger / cards
A card note is only as good as its version label.
Card data moves during Early Access. This page keeps the dated boundaries in one place: what each update touched, what to verify on any card, and where a note stops describing the build you are playing.
| Version boundary | Dated | What it does to card advice |
|---|---|---|
| Major Update #1 | April 17, 2026 (v0.103.2) | The first large Early Access pass on the main branch. Anything written against the launch build predates it. |
| Major Update #2 | June 19, 2026 (v0.107.1) | Shipped a batch of new multiplayer cards plus new art, so the pool and each card role both moved. |
| Beta v0.108.0-v0.111.0 | July 3-August 14, 2026 | Five beta patches inside six weeks. A card note can age out within a single month of being written. |
Checklist
Five fields to verify on any card
| Field | What to confirm |
|---|---|
| Name | Does the name match the in-game card exactly? |
| Energy cost | Is the cost current for the build you are playing? |
| Effect text | Has the effect changed since the entry was written? |
| Rarity / origin | Is it a starter, reward, shop, or event card? |
| Version flag | Is the entry marked beta, default, or unresolved? |
Status lanes
Which lane a card note belongs in
The version ledger sorts every entry into four statuses. Applied to cards, the sort is what stops one page from arguing with another about a card that is not the same card.
| Status | Test | What to do with the note |
|---|---|---|
| Current | Matches the newest dated update note this site records (Beta v0.111.0, 14 August 2026) | Use it, and carry the version label with the card name when you repeat it. |
| Beta | Recorded on a branch build rather than the default one | Keep it out of advice for players who never opt into the branch. |
| Historical | Changed or undone by a later update; v0.110.0 undid earlier reworks and added new ones | Keep it only when it explains why two guides disagree. |
| Unresolved | No dated note covers the card in the current build | Leave the field blank. A plausible invented cost or effect is worse than the gap. |
The full definitions, including what the ledger refuses to fill in, are on the version ledger.
Card names in other languages
A translated card name has its own version
Card advice is a name plus an effect string. The name is a translation, and translations moved on their own schedule during the beta run, so the wording you quote can be older than the numbers beside it.
| Dated entry | What the note says | Consequence for a card name |
|---|---|---|
| Beta v0.109.0 (17 July 2026) | A beta pass that paired translation work with balance changes | A non-English card term can describe an older build than the English text next to it. |
| Beta v0.109.1 (26 July 2026) | A hotfix scoped to one localization issue | A version bump this small is a wording fix rather than a rework, so do not read balance into it. |
| Reading rule | Match the language of the term to the version that shipped it | If you cite a translated card name, cite the patch that set the wording. |
Worked example
What an unlabeled name costs you
The boss roster on this site carries one dated swap: Aeonglass arrives with Major Update #2, v0.107.1, on 19 June 2026, and the earlier Act 3 name stays on the page labeled as history. Nothing about that entry is a card, and it is still the pattern to copy: the old label did not disappear, it kept being repeated, and the only thing that made it wrong was the absence of a date. A card note without a version label fails the same way; it looks precise, it cites a real name, and it describes a build you may not be running.
FAQ
Card data questions
Why does the Slay the Spire 2 card pool keep moving?
Because the game is in Early Access and content arrives in dated batches. A major update shipped a full set of multiplayer cards; later beta patches reworked cards again. The pool you meet this month is not the pool a guide was written against.
Are beta-branch cards in the game I am playing?
Not necessarily. The beta branch receives patches first (the newest dated beta entry is v0.111.0, from August 14, 2026), and a card can exist there before it reaches the default build. Keep beta cards separate when you plan a run on the branch you actually use.
How do I verify a card's current effect?
Check the card in your current build against the entry you are reading. If the cost or effect text differs, the entry is for an older version. Treat any card detail as version-bounded until it matches what the game currently shows.
Why does the version label matter for card advice?
Early Access updates change cards. Advice written against an old version can send you toward a card that no longer works the same way. Match advice to the version you are actually playing.
Are Early Access card details stable?
No. Cards change between updates, and one rework was undone and then redone inside a single month. Prefer advice that names the version it was written against, and re-check a card before you build a whole run around it.
Can a card name go stale the way a Boss name does?
Yes, and the boss roster is the clearest case this site documents: Major Update #2 (v0.107.1, 19 June 2026) brought Aeonglass in and left the earlier Act 3 name as history. A card note carries the same risk in a smaller form: the name survives an update while the number under it does not.
Keep the version visible
Card advice, relic effects, and Boss rosters all move with Early Access updates. The ledger exists so a stale entry never masquerades as current truth.
Last updated: 4 September 2026 · Version boundary: Beta Patch v0.111.0 (August 14, 2026)