Slay the Spire 2 Update Tracker

Quick answer

Update pages should route readers into patch notes, changed tier lists, and newly affected card or relic pages.

What to check first

Use this page as a practical search-intent answer first, then follow the related database links for deeper card, relic, character, boss, and patch context.

• Summarize what changed in plain English.
• Link to affected tier lists and database entries.
• Mark pages that still need retesting.

What an update page should do

An update tracker is not a duplicate of patch notes. It translates changes into site work: which card pages need new warnings, which relics moved, which boss-prep checks changed, and which tier list entries should be marked provisional.

• Add changed items to the top of affected tier lists.
• Flag stale screenshots or video notes when a patch changes UI or behavior.
• Use community notes to collect early run evidence before changing rankings.

Turn broad update news into page actions

Update videos often mix release timing, balance commentary, strategy news, and community reaction. The page should split those into actions a returning player can use: read the changed system, check the affected tier list, and watch for pages that are still waiting on run evidence.

• Use update news to refresh internal links between patch notes, roadmap, and tier lists.
• Add review-needed labels when a video raises a question without enough current proof.
• Keep old screenshots only when they are clearly labeled as historical footage.

Newsletter clips belong beside roadmap caveats

Developer-letter and newsletter coverage is helpful for readers who search updates, but it needs caveats. When the source points toward future content, the update page should explain what is known now, what is only being watched, and which guide pages will change if the official build confirms it.

• Point confirmed changes to patch notes first, then affected database pages.
• Point speculative content to roadmap and FAQ pages with a visible caveat.
• Use discussion submissions to collect timestamped evidence after the update lands.

Quick answer

Use the update tracker as the bridge between patch notes and decisions. A new patch should tell readers which cards, relics, bosses, characters, tier lists, and guides changed, which claims are still needs verification, and what to check before trusting an older recommendation.

Common mistake

The common mistake is treating patch notes as strategy by themselves. A numerical or text change only matters after it changes a draft pick, boss-prep check, route choice, relic value, or tier-list position. The update page should translate changes into those follow-up actions.

Evidence to collect next

The next update pass should record the patch date, changed system, affected pages, old claim, new claim, evidence status, and whether a page needs a full rewrite or only a caution label. If a change is only reported by a creator or community post, keep it needs verification until official notes or current footage support it.

Current affected-page queue

Use this queue when a new Slay the Spire 2 update lands. It points update-search visitors to the exact pages most likely to need review, while keeping unverified mechanics out of hard recommendations.

• Card pages: Fasten, Crash Landing, Neow's Fury, and Perfect Souls need current-patch pick conditions before tier movement becomes confident.
• Character page: Regent should change broad recommendations only after the affected Regent card pages are updated first.
• Relic pages: Wax Seal and Nonupeipe Relics need tooltip, trigger, support-density, and matchup proof before family-level rankings move.
• Boss-prep pages: update Act boss prep when changed card speed, relic defense, or setup timing changes the next danger window.

Editorial note

This page is part of the first English-only content batch. It is written conservatively for Early Access and should be tightened whenever a major patch changes public information or run data.