Decision lab / map
Read the map by what it guarantees.
A map is a decision surface rather than a screenshot. This page separates the fixed layout from the inferences and the unknowns so a route choice stays honest.
| Certainty | Meaning | Planning rule |
|---|---|---|
| Guaranteed | What the map always shows for the current Act and route | Use it as a fixed input for planning. |
| Inferable | What you can reason about from node types and layout | Treat it as a judgment rather than a guarantee. |
| Unpredictable | What is only known after you reveal or enter the node | Do not build a plan on a guess. |
Route reading
Four inputs for a route decision
| Input | What to read | How to use it |
|---|---|---|
| Boss icon | The Act's end target | Work backward from the Boss to the route. |
| Node mix | Reward, elite, rest, and event nodes available | Balance reward against the risk you still need to answer. |
| Rest access | How many rest sites the route reaches | A route with no recovery spends future resources early. |
| Deck gap | The specific answer your deck still lacks | Choose nodes that can close the gap before the next threat. |
The endpoint moved
A route plan inherits its date from the Boss it aims at
Route reading starts at the Boss icon and works backward, so the roster boundary is also a map boundary. The roster detail lives on the boss page; what follows is only what it does to a route.
| When | What the record shows | Consequence for the route |
|---|---|---|
| Before v0.107.1 | Route guides written against the launch build and Major Update #1 name the earlier Act 3 fight | That plan targets an encounter the updated build does not necessarily give you. |
| From v0.107.1 (19 June 2026) | Major Update #2 brought Aeonglass in as the newest boss encounter | Work backward from the current roster, then re-read any node priority that assumed the old endpoint. |
| Any route note with no date | Nothing in the note shows which side of that boundary it sits on | Treat the whole plan as a hypothesis rather than a shortcut. |
Co-op routing
The map is shared. What it hands you is not.
The shared and personal layers are defined on the multiplayer page. Read against a map, they split route decisions into three kinds, and a fourth that nobody should trust yet.
| Route element | Layer | How to handle it in a party |
|---|---|---|
| Choosing the path | Shared: map movement and the run state the party holds together | A route is a group decision. Propose it, do not assume it. |
| What a node pays out | Personal: merchants, rewards, and each player’s deck resources | Two players can want opposite things from the same node, and both be right. |
| How hard the node is | Scaling: enemy, Act and health, buff, and block values move with party size | The risk side of the route calculation is a different number in co-op than in solo. |
| What is still unsettled | Beta: multiplayer mechanics are still marked beta | Re-read a party route rule against the version everyone is running rather than against habit. |
FAQ
Map and route questions
What does Slay the Spire 2 map generation actually guarantee?
The map shows the Act structure, node types, and the route choices available. Specific node contents are not fully known until you reveal or enter them, so keep guaranteed layout separate from what you can only infer.
How do I read a map for a route decision?
Start at the Boss icon and work backward. Count the reward nodes against the elite risk, check how many rest sites the route reaches, and pick the path that closes your deck's current gap.
Can I predict what a node contains from the map?
Only partly. Node type tells you the category rather than the exact reward, elite, or event. Treat anything you have not revealed as an inference rather than a fixed fact.
Why is map advice often missing the generation rules?
Detailed map-generation explanations are frequently incomplete or absent, which is why this page separates what is guaranteed from what is inferred instead of repeating a screenshot.
What should I never plan around on the map?
Do not plan around an unrevealed reward or a guessed elite. Only commit to what the map guarantees, and keep the rest as risk you are choosing to accept.
Does a route guide written before June 2026 still apply?
Check what it plans toward. Major Update #2 (v0.107.1, 19 June 2026) is the boundary this site records for the boss roster, and the Act endpoint is the one map input a route plan leans on hardest. A guide from before that date may be optimizing a path to a fight the current build does not place there.
Is map routing shared in multiplayer?
The path is shared, the payout is not. Map movement and the run state belong to the party, while merchants, rewards, and each player’s deck resources stay personal, so a route that is efficient for one player can be wrong for another.
The route answers the next threat
A good route closes the gap your deck still has before the Boss. Map reading is risk management rather than memorization, and the certainty it deserves is the same four-lane sort the version ledger applies to everything else.
Last updated: 4 September 2026 · Version boundary: Beta Patch v0.111.0 (August 14, 2026)