Slay the Spire 2 v0.106.0 Beta Patch and v0.106.1 Hotfix: Enemy Reworks, Aeonglass Fixes, and Bestiary Follow-Through
Official v0.106.0 beta notes rework Infested Prism, continue Skulking Colony and Aeonglass tuning, and move several class cards and relics, while v0.106.1 follows with a very small Aeonglass-related hotfix.
One-line conclusion
v0.106.0 is the new current beta anchor. Mega Crit pushed enemy balance much harder here: Infested Prism is reworked, Skulking Colony gets another round of changes, Aeonglass gets move and Wither adjustments, and multiple class cards move enough that old build assumptions need a fresh pass.
3 actions to do now
- Current beta scope: v0.106.1 hotfix on top of v0.106.0 beta
- Enemy focus: Infested Prism rework, Skulking Colony follow-up, Aeonglass move and Wither changes
- Decision focus: retest cards, builds, and encounter reads before carrying v0.105 assumptions forward
Next questions to open
v0.106.0 is the new current beta anchor. Mega Crit pushed enemy balance much harder here: Infested Prism is reworked, Skulking Colony gets another round of changes, Aeonglass gets move and Wither adjustments, and multiple class cards move enough that old build assumptions need a fresh pass.
v0.106.1 is a true hotfix, not a separate strategy reset. Its practical role is to clean up Aeonglass and Wither-state issues, plus a small localization update. Read it as stability follow-through on top of v0.106.0 rather than as a second major patch.
Official source of truth: v0.106.0 is the live beta conversation now
The big shift is not a single buff or nerf. Mega Crit kept pushing on encounter readability and enemy pacing: Infested Prism is reworked, Aeonglass gets another set of changes, Skulking Colony keeps evolving, and several class tools move enough that current build language should stop centering v0.105.x.
That matters for the site because players searching patch notes, build guides, and card context now need the current beta scope to start at v0.106.0 with the tiny v0.106.1 hotfix layered on top.
- Current beta scope: v0.106.1 hotfix on top of v0.106.0 beta
- Enemy focus: Infested Prism rework, Skulking Colony follow-up, Aeonglass move and Wither changes
- Decision focus: retest cards, builds, and encounter reads before carrying v0.105 assumptions forward
What changed enough to matter in v0.106.0
The most actionable official changes are spread across enemies and class toolkits. Silent gets the Follow Through -> Scare rename/rework plus Predator and Pounce movement. Regent gets Furnace, Minion Sacrifice, Sealed Throne, and Astral Pulse changes. Defect sees Fusion, Synthesis, and Shatter adjustments. Ironclad also gets meaningful touch-ups like Drum of Battle, Howl From Beyond, Entrench, and Unrelenting.
On the encounter side, Aeonglass is not frozen yet. Official notes call out adjusted moveset work plus a reworked Wither status and Withering Presence power. That means boss-read advice should stay cautious while players absorb the new timings.
- Silent: Scare, Predator, and Pounce are the quickest re-check points
- Regent: Furnace, Minion Sacrifice, Sealed Throne, and Astral Pulse need fresh context
- Defect: Fusion, Synthesis, and Shatter are not safe to leave on old ratings
What v0.106.1 actually does
v0.106.1 is intentionally small. Official notes describe it as a quick hotfix with a couple of Aeonglass-related fixes and some localization updates.
The practical read is straightforward: if you are writing build or tier guidance, v0.106.1 should not become a dramatic new meta headline. It does, however, matter for any advice touching Aeonglass or Wither-state edge cases.
- Player can no longer upgrade Wither status cards
- Wither status cards no longer stick in hand after unusual Retain interactions
- Treat this as correctness cleanup, not a second full patch cycle
Why Bestiary and roadmap language still matter here
v0.106.0 keeps building on the same broader direction called out in the May newsletter: slower beta cadence, more time for testers to absorb changes, and continued Bestiary expansion as a practical player reference.
That means the site should update fast on version facts, but keep strategy claims conservative until repeated runs confirm what the new enemy and card timings actually feel like.
- Patch hub should move immediately to v0.106.x language
- Build guides should be re-checked where official cards actually changed
- Tier calls should stay watchlist-first while encounter evidence catches up
What this site should update now
The safe minimum update is to move homepage, patch hub, and news priority routing onto v0.106.0 / v0.106.1. The goal is freshness and correct decision routing, not a sweeping content rewrite.
Because this is still a controlled freshness sync rather than a new expansion phase, the right move is one current patch analysis page, one bug-fix page, one newsletter context page, and the smallest possible routing updates around them.
- Publish one current v0.106.0 / v0.106.1 patch analysis page
- Update homepage, news hub, builds hub, and patch hub current-version language
- Keep deeper build and tier conclusions conservative until more run evidence lands
This page is a quick-reference guide for players checking launch-week status, practical next steps, and the most useful follow-up links after release.