Guide sections
A deck builder is not just a place to drag cards into a list. For Slay the Spire 2, it is a thinking tool. It lets you visualize whether your deck has enough damage to clear elites, enough block to survive long fights, enough draw to find key pieces, and a sane enough energy curve to actually play the cards you drafted. This page explains how to use the STS2Tools deck builder workflow, even in its server-rendered MVP form, to make cleaner decisions.
Count roles, not just raw card totals
Players often talk about deck size first, but role coverage matters more. A twenty-card deck with weak attack density and no scaling can fail harder than a larger deck with clear combat jobs. When evaluating a deck, count frontloaded damage, durable defense, draw or selection, and long-fight scaling separately. That role view explains why a deck can “look fine” while still dying to elites or bosses.
A practical deck builder makes those roles visible. Even before interactive editing lands, the server-rendered page shows starter deck composition and energy curve data so you can see how quickly a character defaults into certain combat patterns. That baseline matters because every pickup should improve or intentionally bend the starting plan.
The goal is not to force every deck into the same balance. Some archetypes want explosive attacks, some want poison inevitability, some want orb scaling, and some want stance loops. The value of a builder is showing you what you gave up to chase that archetype.
Energy curve and dead-turn prevention
Many runs fail because the deck is technically powerful but functionally clumsy. Too many expensive cards create dead turns. Too many zero-cost or low-impact fillers create turns that do not scale. The energy curve section matters because it reveals whether your picks can actually be deployed under normal draw sequences.
When you review a curve, think about your likely draw order and relic support. A two-cost card can be excellent if your deck has energy relics, draw smoothing, or enough stall to reach it. The same card can be a trap if your hand regularly jams on turn one. That is why builder tooling should always sit next to the database and relic pages instead of being isolated.
Use the builder to sanity-check whether upgrades should reduce energy friction, improve damage efficiency, or support scaling turns. The answer changes as the deck evolves, but the curve gives you a grounded starting point.
Use builder output to improve route planning
A deck builder becomes more useful when it influences map decisions. If your list shows weak immediate damage, skip greedy elites until you patch that. If your deck has excellent short-fight output but poor scaling, path toward shops or rewards that can solve bosses. If you have strong sustain and relic support, you may be able to take more aggressive lines than usual.
This is why we keep the builder page crawlable and indexable: many players search for deck builder tools before they know what supporting data they need. Once they arrive, the server-rendered guide can teach the workflow while the tool provides structure.
Open the builder page from the call-to-action below, compare the starter shells, and use the counts as a reference point for your own drafting experiments.