Slay the Spire 2 · builds
Slay the Spire 2 Necrobinder Sacrifice: Osty Max HP and Block Planning
On this page
Applies to: Beta v0.110.0 scaling, with main preview context. Check the installed card text before following the combination.
The beta v0.110.0 note changes Sacrifice’s Block scaling from twice to three times Osty’s maximum HP. Use Osty’s actual maximum HP, not the player’s HP or a guessed summon value. Then inspect the current preview and other consequences printed on the card before committing.
Published October 18, 2026 · Developer-source analysis
Build the useful turn, in order
- Confirm that the installed Sacrifice is the version described by the beta note. The main update’s improved preview is not itself the scaling change.
- Read Osty’s current maximum HP and distinguish it from current remaining HP. Keep the player’s health as a separate value.
- Use the final Block preview to compare the defensive contribution with the incoming turn. Include any card consequences rather than treating the multiplication as the entire effect.
- Plan how the deck functions after the play. Evaluate the next hand’s defense and damage instead of only the biggest single Block turn.
What the plan needs
This scaling offers a way for a summon-oriented resource to support a defensive turn. The deckbuilding question is whether the resource is available at the time defense is needed. Adding another expensive payoff without improving setup or access can leave the deck with several strong cards that cannot solve the immediate turn. When choosing support, test the earliest point at which the plan becomes useful.
A concrete comparison
If Osty’s maximum HP were 10 in a controlled example, three times that value is 30; at 15 it is 45. These are illustrative inputs to the documented multiplier, not claims about Osty’s default HP or complete final Block. Use the actual maximum value and the card’s displayed result, especially when modifiers are active.
When the interaction fails
I used my own maximum HP
The beta change refers to Osty’s maximum HP.
The preview and raw multiplication differ
Inspect the current card version and applicable Block modifiers before declaring a bug.
A large defensive turn leaves the deck stuck
Evaluate the state after resolution and the next turn, not only the current total.
Version and sources
Sources retrieved October 18, 2026. The stated branch is part of the mechanic, not an optional label. Main and beta may have different card text; do not combine values from both into a fictional build. Calculations and decision sequences are independent analysis, not a personal gameplay result, win-rate claim or guaranteed infinite.
Before adopting the route, compare the current card, its upgrade state and the encounter you need it to solve. If a required piece is absent, choose the next useful action from the existing deck rather than taking a risky reward solely to force this example.