Co-op

Co-op Handoff ReviewChecklistCompareField Note

Which Co-op Relics Are Actually Worth Handing Off

Players love the fantasy of perfect team optimization. Most relic handoffs fail because the team ignores the opportunity cost on the original owner and overestimates the synergy on the receiver.

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.

ReviewedMarch 21, 2026
Use This Article

Read this when the question is judgment, not raw lookup

In co-op, a relic transfer is good only when the receiving player converts it better than the sender and the team loses less tempo than it gains. Anything softer than that is sentimentality.

Where It Drifts

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.

Real Example

What separates a real handoff from co-op sentimentality

Good transfers are usually obvious because role fit is lopsided. Bad transfers need a speech to justify them.

Open Next

Use the Co-op Synergy Planner

This article should hand you off cleanly. Open Use the Co-op Synergy Planner 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.

Maintained bySTS2 Calculator Co-op Notes Desk

Handles co-op coverage where ownership, shared debuffs, and timing windows matter more than solo heuristics.

Responsible editorSTS2 Calculator Site Operator

Final site operator and responsible editor. Final contact for corrections, rights notices, and maintenance triage via [email protected].

Last reviewedMarch 21, 2026

The visible post body, related links, and article-level metadata were checked on the article update date shown here.

Revision noteVisible update

This co-op handoff review revision rechecked the page's main argument around "A good handoff creates a larger total team gain than keeping the relic in place". It also re-read "Three conditions that must all hold before a relic moves" 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.

Patch verifiedCurrent Early Access editorial cycle

If a patch breaks a claim in this article, the post should be revised, narrowed, or replaced instead of silently drifting.

Applies toCo-op article for the Slay the Spire 2 Early Access rules and assumptions discussed in this post.

Use the linked tools, detail pages, and databases when you need the live underlying numbers behind the argument.

DisclaimerEditorial analysis, not an official game statement.

Good judgment pages still carry opinions. When the page links to a calculator or database, that linked page owns the raw reference surface.

Handoff Test

Three conditions that must all hold before a relic moves

The test is strict because transferring a relic is not free just because the other class has a fun interaction.

  • The receiver gains materially more from the relic than the sender currently does.
  • The sender does not become meaningfully worse at its present job.
  • The timing of the handoff does not create a short-term weakness that outweighs the future gain.

Transfer Compare

What separates a real handoff from co-op sentimentality

Good transfers are usually obvious because role fit is lopsided. Bad transfers need a speech to justify them.

Situation
Line A
Line B
Judgment
Receiver clearly converts the relic better now
Move it because team output and role fit both improve immediately.
Keep it for symmetry or sentiment even though the gain is obviously larger elsewhere.
Move it when the current conversion gap is real and immediate.
Sender still needs the relic for the next fights
Transfer for theoretical future synergy.
Wait because the current owner is still using it to stay ahead right now.
Timing matters more than the prettiness of the eventual team story.
Marginal upgrade for the receiver
Trade for style points and call it optimization.
Leave the relic in place because the team gain is too soft to justify the disruption.
Do not pay real tempo to purchase novelty.

Why Tools Matter

Why calculators still matter in co-op

Co-op decisions are hard because they are relational. You are not evaluating one deck in isolation; you are evaluating how one deck gets weaker, how another gets stronger, and how that changes the next room. That is exactly where ad-lib intuition often overstates the upside.

Tools like the co-op planner and HP calculator help because they keep the team honest about what each player is actually doing in the current state, not what everyone hopes the final composition will eventually look like.

Team Economy

The team resource economy that co-op relic decisions live inside

A co-op team is not four solo runs running alongside each other. It is a shared resource pool where one player tempo loss is the team tempo loss. That framing changes how relic transfers should be evaluated, because the cost of a bad handoff is not just felt by the player who gave up the relic. The cost propagates to every fight where the sender is now weaker than it needed to be.

Good co-op relic decisions treat the team total combat output as the number to maximize, not any individual player highlight potential. A relic that moves from a player who was already stable to a player who is currently struggling to close fights is a real team gain. A relic that moves from a stable player to another stable player for a marginal upgrade is often just shuffling resources between comfort zones.

The timing question matters at the room level, not the run level. A relic that will be transformative for the receiving player in three fights is not worth transferring if it costs the sending player two fights of meaningful coverage getting there. Evaluate the handoff window against the next room, not the ideal future state.

Common Patterns

Relic types that consistently transfer well versus relic types that rarely do

Relics that consistently transfer well have two properties: they synergize sharply with a specific character archetype, and the current holder is running a different archetype that barely uses the synergy. When the role fit gap is that clear, the transfer math is simple. The team wins now, not eventually.

Relics that rarely transfer well are the ones whose value feels high to the sender primarily because of familiarity rather than actual current use. A relic that has been in the inventory since Act 1 and has been quietly contributing to every fight may seem less glamorous than the shiny new option, but removing it often reveals how much structural load it was carrying.

When in doubt, run the co-op synergy planner before committing to a transfer. The planner makes the shared debuff windows and role handoffs explicit instead of relying on remembered impressions from past runs.

Timing Rules

Three timing rules that prevent most bad relic transfers in practice

The first timing rule is to never transfer a relic during an elite room. The fight is already in progress. Both players are managing their hands and health totals. Adding a relic to one player inventory and removing it from another during active combat introduces decision lag at exactly the moment when clean decisions matter most. Discuss transfers between rooms.

The second rule is to never transfer a relic within the first five fights unless the role fit gap is completely obvious. Early in a run, both players are still discovering what the deck actually needs. A relic that seems misallocated on floor 4 may be doing structural work that is not visible yet. The value of a relic in the early game is often in its defensive or consistency contribution, not its peak output contribution, and those contributions are easy to underweight.

The third rule is to treat the co-op synergy planner result as advisory, not prescriptive. The planner surfaces shared windows and role overlaps that verbal discussion often misses, but it does not know your current run state, your remaining route, or how close either player is to a natural power spike. Use the planner to identify the theoretical fit, then apply your own judgment about whether the timing is actually right.

Team Economics

Why sender cost is the whole argument

Co-op players love talking about receiver upside because that part is fun. The harder, more important question is what the sender loses during the exact fights that happen before the new synergy is fully online. A transfer that makes one deck prettier but removes the other deck's clean opener, safety valve, or scaling bridge can reduce the team's real win rate even when the receiving class has the cuter interaction on paper.

That is why the best handoffs feel boringly lopsided. One teammate clearly gets much more immediate conversion, while the original owner barely notices the loss. Anything that requires long speeches about future harmony is usually a sign that the team is trying to buy a narrative rather than solve the current state. Co-op optimization is not a friendship test. It is a timing and ownership test.

Timing Compare

Handoff now, later, or never

A relic can be a correct transfer target and still be wrong to move immediately.

Situation
Line A
Line B
Judgment
Receiver spike is immediate and sender cost is low
Move now and let the team cash the stronger role fit in the next serious rooms.
Delay for no reason and keep splitting the value across two mediocre homes.
Immediate handoff is correct when both timing and ownership lines are clean.
Receiver wants it later, sender still needs it now
Move it immediately because the eventual destination is obvious.
Wait until the sender can spare it without opening a real weakness.
Correct destination does not erase incorrect timing.
Receiver gain is marginal and sender loss is real
Trade anyway because the combo story sounds elegant.
Leave it where it is and stop paying tempo for sentiment.
Never transfer a relic just to make the team story feel smarter.

Counterexample

When the sender should still give it up

There are cases where the sender genuinely likes the relic and should still move it because the receiver turns it from merely good into central infrastructure. In those spots, clinging to the relic is just selfish play wearing the costume of caution. The team question always wins if the total gain is large enough and arrives soon enough.

The discipline is to demand proof. Name the current role on both sides, name the timing window, and name the next few fights that get easier. If the transfer meaningfully sharpens those answers, move the relic and move on. If the answers stay foggy, the relic is probably not “actually worth handing off” yet.

More From The Blog

Next Articles

Tool Tutorial

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.

March 28, 20267 min readSTS2 Calculator Tools Desk
  • 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.
WalkthroughChart
Read article
Editorial MethodBuild NotesFeatured

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.

March 28, 20266 min readSTS2 Calculator Editorial Desk
  • 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.
Field NoteChecklist
Read article
Editorial MethodVerification WorkflowFeatured

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.

March 28, 20267 min readSTS2 Calculator Editorial Desk
  • 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.
Field NoteWalkthrough
Read article