Slay the Spire 2 v0.105.1 Hotfix and v0.105.0 Beta Patch: Aeonglass, Bestiary, and Bi-Weekly Patching

The biggest versioned change is not a tiny number tweak. Mega Crit explicitly replaced Doormaker with a new Act 3 boss, Aeonglass, while also adding the early Bestiary view to the Compendium.

That matters for this site because older v0.104.0 language framed Doormaker as a watchlist boss. The current beta conversation now needs to point players toward Aeonglass testing, encounter learning, and fresh boss-read guidance.

The v0.105.1 hotfix is narrow and useful: it updates the Aeonglass boss icon, fixes Aeonglass first-move intent display, fixes Aeonglass music behavior, and cleans up Ceremonial Beast music timing.

The multiplayer notes are also important because they target state divergence. Silken Tress card-reward behavior, treasure-room reward handling, and the Crystal Sphere event all get fixes, so co-op groups should retest before assuming those bugs remain live.

v0.105.0 says the team is moving from weekly beta patches toward a two-week cadence. That is a meaningful operations signal: individual beta notes may become larger, but the site should avoid panic-updating every minor hotfix into a new strategy headline.

The better rhythm is to update the patch hub quickly, publish a concise versioned read when the official note changes current decisions, then wait for player evidence before rewriting tier lists or build priorities.

Start with boss learning and multiplayer correctness rather than broad card reranking. Aeonglass replaces the old Doormaker conversation, so run notes should focus on intent reading, turn pacing, and how often old Act 3 assumptions break.

Then check the Bestiary as a reference feature. It is not yet a complete data source, but its presence means players may begin searching for monster data and encounter references sooner than before.

The safe minimum update is to make the patch hub and homepage stop presenting v0.104.0 as the current beta scope. v0.104.0 remains useful history, but the visible current patch should now be v0.105.1.

Because this is a content freshness update, not a passed SEO expansion gate, the right action is one new news analysis page, a patch-hub pointer, sitemap inclusion, and IndexNow submission. No new wiki section or batch expansion is justified from this alone.