Article Scope
How To Use This Article
Good articles frame judgment and failure patterns. They should not pretend to replace the live database, calculator, or detail page once the question becomes exact.
Read this when the question is judgment, not raw lookup
The map can tell you the right campfire decision before you ever click the node. Players miss that because they treat rest-versus-smith as a deck-only question when it is really a route question.
Longform still has a boundary
Once the question becomes exact card text, room totals, or calculator inputs, stop forcing one article to own live data and open the linked page that carries the current surface.
Read the branch before you click the fire
This is the shortest route check that still keeps the campfire decision tied to reality.
Use the Rest Site Optimizer
This article should hand you off cleanly. Open Use the Rest Site Optimizer when the argument needs a live tool, database, or narrower follow-up page.
Maintenance Signals
Who Maintains This Page
This block keeps article ownership and scope visible without forcing the whole page to repeat the same trust speech.
Owns pathing pieces that explain when route shape changes campfires, elite tolerance, and future card value.
Final site operator and responsible editor. Final contact for corrections, rights notices, and maintenance triage via [email protected].
The visible post body, related links, and article-level metadata were checked on the article update date shown here.
This route review revision rechecked the page's main argument around "Rest site choices should change when the branch changes, even if the deck list does not". It also re-read "Read the branch before you click the fire" so the visible examples still support the same decision line. The linked live pages were verified again so the article still hands the reader off cleanly when the question turns exact.
If a patch breaks a claim in this article, the post should be revised, narrowed, or replaced instead of silently drifting.
Use the linked tools, detail pages, and databases when you need the live underlying numbers behind the argument.
Good judgment pages still carry opinions. When the page links to a calculator or database, that linked page owns the raw reference surface.
Map Workflow
Read the branch before you click the fire
This is the shortest route check that still keeps the campfire decision tied to reality.
- Count the pressure nodes immediately ahead
Two fights and a shop is not the same exam as elite into elite into unknown. Start by admitting what the branch is asking.
- Ask what failure would end the branch fastest
If the answer is low HP, rest matters. If the answer is missing one exact breakpoint, smith may matter more.
- Check whether the branch offers recovery later
A branch with a safe shop or extra rest site lets you spend risk now. A dry branch does not.
- Only then compare the campfire options
The deck is still important, but it should answer the branch instead of pretending every branch is the same.
Branch Compare
Three branches, three correct fire choices
Problem Definition
Campfires are route questions disguised as deck questions
Players love treating rest-versus-smith like a static deck optimization puzzle. The deck matters, of course, but that framing is still incomplete. A campfire decision lives between the rooms behind you and the rooms in front of you. The same deck should give different answers when one branch leads into stacked elites, another leads into a store plus hallway buffer, and a third leads into a boss corridor that punishes low HP less than low damage. If the route branch changes the failure condition, the campfire choice should change with it.
That is the core argument of this article. Rest sites are not abstract value nodes. They are timing nodes. What matters is not only how much HP you have or how strong the upgrade looks. What matters is whether the next branch turns HP into access, turns damage into safety, or turns one extra smith into a disguised debt instrument that has to be repaid before the map gives you room to breathe again.
- Campfire value is downstream of the branch you are about to walk.
- The same deck can produce different campfire answers on two adjacent branches.
- A route-aware smith is strong; a route-blind smith is often vanity.
Branch Compare
Three route shapes that should alter the same deck decision
These are the branch patterns that most often invalidate a lazy one-size-fits-all campfire answer.
Route Questions
What to ask before clicking rest or smith
These questions are more useful than a generic "am I low?" check.
- Which exact branch am I taking after this fire, and what pressure shape does it create?
- Does the smith change the next dangerous room, or only a later room that I may not reach cleanly?
- If I rest now, what future campfire or store becomes available because I preserved access rather than raw HP?
- If I smith now, what debt am I taking on before the map gives me a recovery window?
Counterexample
Route context matters a lot, but it still cannot rescue a broken shell
This article is not arguing that map shape overrules everything. There are decks so unstable that no elite branch can justify a greed smith, and there are smith targets so powerful that a buffered branch does not meaningfully weaken the argument for taking them. Route context is a multiplier on the deck state, not a replacement for it.
The practical lesson is to stop flattening campfires into one permanent preference. Route shape changes the payback schedule. The deck still sets the ceiling on what can be afforded. Good rest-site planning happens when those two facts are read together rather than when one of them gets promoted into a universal law.
More From The Blog
Next Articles
How to Use the Event EV Calculator Without Faking Precision
An EV tool is useful when it sharpens a close decision. It becomes dangerous the moment you feed it fake confidence, bad route assumptions, or a run state you have not described honestly.
- The tool helps when the input state is concrete and the next decision is real.
- It lies when the player buries route risk, survivability, or hidden preferences under fake neutral numbers.
How We Built the Slay the Spire 2 Early Access Data Station
A practical look at how STS2 Calculator turns early-access patch churn into usable tools, cleaner reference pages, and original editorial work instead of recycled database sludge.
- We design tools around decisions, not around showing off raw tables.
- Every reference page is tied back to a real route, combat, or deck-building question.
How We Verify STS2 Data After Every Patch
Our patch workflow for Slay the Spire 2: find what changed, isolate the assumptions those changes break, update the source data, and only then refresh the editorial layers and tools.
- We verify the rule first, then the data row, then every tool or guide derived from it.
- Patch notes are a lead, not a final source of truth.