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
Every calculator makes assumptions. This page spells out what ours do, where the models are intentionally strict, and where results can drift from a real run if the input state is incomplete.
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.
Smaller honest models versus bloated fake-precision models
The point is not to simulate every decorative edge case. The point is to model the variables that actually change the decision.
Open the Event EV Calculator
This article should hand you off cleanly. Open Open the Event EV Calculator 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.
Maintains site-build explainers, methodology notes, and articles about how the project is structured and reviewed.
Final site operator and responsible editor. Final contact for corrections, rights notices, and maintenance triage via shwuhen@gmail.com.
The visible post body, related links, and article-level metadata were checked on the article update date shown here.
This methodology note revision rechecked the page's main argument around "Our tools model the variables that most often change the decision, not every decorative edge case". It also re-read "Why assumptions belong in the open" 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.
Why This Exists
Why assumptions belong in the open
Any strategy tool that hides its assumptions is eventually going to mislead someone. The number may still look professional, but users cannot judge whether the model applies to their current run state. That is why we treat assumption disclosure as part of the tool, not as optional decoration.
In practice this means each major tool is being expanded with plain-language notes about what the inputs mean, what game state is being simplified, and which kinds of fights are most likely to produce drift.
Model Rules
What the tool layer promises and what it refuses to fake
A useful calculator explains its limits instead of pretending every variable was modeled perfectly.
- Important variables are explicit.
- Derived shortcuts are explained in plain English.
- Known blind spots are surfaced instead of buried.
- If an input state is incomplete, the output should be treated as a directional clue rather than a verdict.
Model Compare
Smaller honest models versus bloated fake-precision models
The point is not to simulate every decorative edge case. The point is to model the variables that actually change the decision.
Usage Rule
How to use the tools without lying to yourself
The easiest way to misuse a calculator is to feed it a sanitized state that your real run does not have. If your deck cycle is clunky, your relic support is partial, or your HP buffer is already under pressure, the clean result from a simplified input set may still be the wrong play in practice.
So the rule is simple. Use the tool to sharpen a decision, not to outsource judgment. If the result depends on assumptions your current run does not satisfy, treat the output as a directional clue rather than a final verdict.
Problem Definition
A calculator is only as honest as the state you described
Every tool on this site is a model. That sounds obvious, but people routinely interact with calculators as if the model had privileged access to everything that happened in the run. It does not. The tool only knows the state you fed it and the assumptions the page author chose to keep visible. If a variable was hidden, simplified, or intentionally excluded because the edge case was too unstable, the result can still be useful, but it stops being a literal replay of the game and becomes a decision aid with a boundary.
That is why assumption disclosure is not decorative legal copy. It is the difference between a trustworthy tool and a confidence theater box. We would rather state that a calculator ignores one unstable variable than pretend the number is exact. A rough answer with a clean scope helps the player think. A fake precise answer trains the player to offload judgment to a model that never had the full room state in the first place.
- Hidden variables do not disappear because the UI is clean.
- A tool should expose the variables that most often change the decision, not every decorative edge case.
- When the missing variable becomes the actual binding constraint, you stop trusting the output and go back to the run context.
Honest Model vs Fake Precision
What a good assumption boundary looks like
The tool is useful when it narrows the real question. It becomes dangerous when it pretends to answer more than the inputs can support.
Trust Test
Questions to ask before you trust a tool output
These are the questions that separate a good model use from a fake-certainty click.
- Did I enter the variables that actually change this decision, or only the variables the UI made convenient?
- Is the room loss condition really the thing this tool measures, or am I solving the wrong problem because the number looks clean?
- Would a hidden route branch, potion, relic timing, or survival constraint overturn the result?
- If the result surprises me, can I explain which assumption produced the surprise?
Boundary Rule
When the output should make you stop and think harder
A good output does not always tell you what to click. Sometimes it tells you that the current question is under-described. That is still a useful answer. In fact, one of the healthiest patterns on strategy sites is when a tool pushes the user back toward the missing context: the route, the potion stock, the survivability problem, or the shell mismatch that the model never claimed to solve cleanly.
That is the rule we try to preserve here. A calculator should either sharpen a real decision or make the missing assumption obvious enough that the player stops pretending they already know the state. The only unacceptable outcome is a polished number that encourages overconfidence while hiding the exact simplifications that made it possible.
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.