STS2 / FIELD NOTESSpire Ledger

Decision lab / multiplayer

Co-op rules change when the party size changes.

Multiplayer adds shared movement, personal resources, and scaling categories that a single-player habit will not catch. This page maps what is shared, what is personal, and where the beta boundary sits.

LayerMeaningHandling
SharedMap movement and the run state the party holds togetherChanges affect the whole party at once.
PersonalMerchants, rewards, and each player's deck resourcesKeep per-player decisions separate from shared state.
ScalingEnemy, Act, health, buff, and block values that scale with party sizeLabel scaling categories instead of a single number.

Scaling

Four scaling categories to keep separate

CategoryWhat scalesPlanning rule
Enemy scalingHow enemy values change with more playersConfirm the rule for the current build before planning.
Act / healthHow Act progression and health behave in co-opSeparate from single-player progression.
Buff scalingGeneral and special buff values in a partyDistinguish general buffs from special ones.
Block scalingHow block values respond to party sizeKeep it distinct from enemy scaling.

FAQ

Multiplayer questions

Is Slay the Spire 2 multiplayer confirmed?

Yes. Co-op and online co-op are listed for the game, and multiplayer content exists with a beta boundary. Treat scaling details as subject to change while the mode is marked beta.

What is shared versus personal in co-op?

Map movement and the run state are shared by the party, while merchants, rewards, and each player's deck resources stay personal. Keeping these separate avoids misreading a co-op decision.

How does multiplayer scaling work?

Scaling applies across enemy, Act and health, general and special buffs, and block categories. Confirm the current values for your build rather than relying on a single remembered number.

Why is there a beta warning on multiplayer content?

Multiplayer mechanics are still marked beta, so scaling and rules can change between updates. Read any co-op detail as version-bounded until it matches the current build.

How should I approach a co-op run plan?

Treat shared map movement as a group decision and personal merchants, rewards, and decks as per-player decisions, then check the current scaling rules before committing resources.

Shared and personal never mix

Confusing shared movement with personal resources is the most common co-op mistake. Keep the two layers separate in every decision.

Last updated: August 27, 2026 · Multiplayer status checked August 26, 2026