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.
| Layer | Meaning | Handling |
|---|---|---|
| Shared | Map movement and the run state the party holds together | Changes affect the whole party at once. |
| Personal | Merchants, rewards, and each player's deck resources | Keep individual-player decisions separate from shared state. |
| Scaling | Enemy, Act, health, buff, and block values that scale with party size | Label scaling categories instead of a single number. |
Scaling
Four scaling categories to keep separate
| Category | What scales | Planning rule |
|---|---|---|
| Enemy scaling | How enemy values change with more players | Confirm the rule for the current build before planning. |
| Act / health | How Act progression and health behave in co-op | Separate from single-player progression. |
| Buff scaling | General and special buff values in a party | Distinguish general buffs from special ones. |
| Block scaling | How block values respond to party size | Keep it distinct from enemy scaling. |
The June boundary
What one update moved for co-op
Major Update #2 is the dated entry this site ties the multiplayer card batch to. Its full note is on the patch page; the table is what it reaches on this one.
| What the update covered | Dated | Consequence for a party rule |
|---|---|---|
| A batch of new multiplayer cards | v0.107.1, 19 June 2026 | Party card advice moves with it. A deck plan copied from before June is a plan about a different pool. |
| New art and animations for the newest boss | v0.107.1, 19 June 2026 | The encounter a party prepares for is set by the same update, so read the roster and the party rules together. |
| Multiplayer listed among the systems it covered | v0.107.1, 19 June 2026 | One note, several systems. Do not assume a co-op rule was left alone just because the headline was about content. |
| Balance changes in the same update | v0.107.1, 19 June 2026 | Scaling values and card values were rebalanced in the same window, which is why neither gets a standing number on this site. |
Layer by layer
Shared or personal, and which scaling reaches it
Crossing the two vocabularies on this page is what makes a co-op decision checkable: the layer tells you whose call it is, the scaling category tells you which numbers moved.
| Element | Layer | Scaling category | How to run it |
|---|---|---|---|
| Map movement | Shared | Act / health | A path choice is a party choice; the health cost of that path is scaled rather than solo. |
| Merchants and rewards | Personal | None | Each player transacts for themselves. Do not average two people’s gold into one plan. |
| Deck resources | Personal | Buff scaling | General and special buff values matter for each deck, and a party can hold four different answers to the same scaling question. |
| The boss encounter | Shared state, personal decks | Enemy scaling, block scaling | The fight each player must answer is sized by party size, so block and damage plans are group arithmetic. |
The beta window, dated
Why a co-op rule needs a date more than most
| Window | Dated | What it means for a party |
|---|---|---|
| Beta v0.108.0-v0.111.0 | 3 July-14 August 2026 | Five beta patches inside six weeks. A co-op rule written in July is a claim about one of them rather than about all of them. |
| After v0.111.0 | 14 August 2026 onward | The record notes a scheduled pause for a team break rather than a quiet week. Slower cadence is not settled data. |
| Default branch players | No dated entry to cite | A card or rule that exists on the beta branch can be absent from the build your party actually runs. |
FAQ
Multiplayer questions
Is Slay the Spire 2 multiplayer confirmed?
Yes. Co-op and Online Co-op are part of the game, and Major Update #2 (v0.107.1, June 19, 2026) added a batch of multiplayer cards. Scaling rules still move while the game is in Early Access, so re-read a party rule against the version you both run.
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 individual-player decisions, then check the current scaling rules before committing resources.
Does the whole party see the same fight?
The encounter is shared state; the decks answering it are personal. Enemy, Act and health, buff, and block values scale with party size, so the fight is one set of numbers and each player’s answer to it is another.
Is multiplayer still officially beta?
That is how this site records it, and the boundary is dated: the newest entry in the patch record is Beta v0.111.0 from 14 August 2026, followed by a scheduled pause. Read a co-op number as version-bounded until it matches what your party’s build shows.
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, and keep the version label beside them; the ledger is where current, beta, historical, and unresolved are defined.
Last updated: 4 September 2026 · Version boundary: Beta Patch v0.111.0 (August 14, 2026)