SEO guide
Slay the Spire 2 Meta Guide
A meta guide for Slay the Spire 2 explaining patch movement, tier-list confidence, popular builds, and why Early Access rankings change.
Quick answer
Meta pages should summarize what is broadly strong without pretending every run should draft the same way.
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.
- Track high-consistency builds separately from high-roll builds.
- Refresh rankings after major balance updates.
- Link meta claims to tier lists and patch notes.
Meta means repeatability, not highlight power
A deck that creates one spectacular run is not automatically meta. For this site, a meta claim should mean the plan appears often enough, survives enough bad starts, and has enough boss coverage to be recommended beyond a single video. High-roll builds can still be documented, but they need a lower confidence label.
- Separate consistent win paths from rare ceiling runs.
- Mention the patch version that supports the claim.
- Downgrade claims that depend on one relic, one upgrade, or one perfect draw order.
How patch notes change the meta page
Every major patch should create three editorial actions: check whether the overall tier list moved, check whether any build guide is stale, and check whether card or relic pages need new warnings. The meta page should point readers to those affected pages instead of rewriting the entire site every time.
- Refresh affected tier lists before changing broad meta language.
- Keep old claims if they are still true but add patch context.
- Use community notes to collect early counterexamples after a balance update.
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.