
Multiplayer in Slay the Spire 2 is built around a single online save owned by one Host, up to four players connected via Steam friends, and fully separate decks and rewards for each player. You move on one shared map, fight the same enemies, but keep your own cards, relics, gold, and energy.
Once I understood that core idea-shared run, individual progression-the whole system finally clicked. This guide walks through exactly how to host and join, what the save rules do (and don’t) allow, how combat and loot change in co-op, and how Ascension works so you can start runs without wrecking a good save by accident.
All multiplayer is online-only through Steam. There’s no local co-op, matchmaking, or password lobbies right now, so every player has to be on your Steam friends list.
Here’s the exact setup flow I use:
Multiplayer.Host and creates the lobby.Join and connects via the Steam friends list popup.One thing I learned early: your chosen profile matters. New profiles only have Ironclad unlocked. If you want to play a different character, make sure you pick a profile where you’ve already unlocked them before you hit Multiplayer.
This is the part that caused the most confusion in my group. Slay the Spire 2 treats multiplayer campaigns as tied to the Host’s profile, with some strict rules about who can play and when.
In practice, this means you should think of a multiplayer campaign as “this exact group’s long-term run.” On one of my early attempts, a friend dropped the game for a few weeks; because we couldn’t sub in anyone else, that whole campaign was effectively frozen unless we all got back together.
If you want flexibility, I recommend:
Once you’re in a fight, Slay the Spire 2 feels familiar, but multiplayer adds a few important twists that change how you build decks and how risky you can be.

Every player has their own hand, draw pile, discard pile, and energy pool. Nothing about your cards or resources is shared directly.
On our first runs we kept accidentally stalling turns because one person was still thinking while everyone else had ended. Now we always call out “I’m done” or “give me a second” in voice chat so no one rushes their plays or ends too early.
Co-op isn’t just four players stomping singleplayer encounters. The game scales enemies based on how many people you bring:
The practical impact: if one person is under-defended, everyone feels it. In singleplayer you can tank a hit and recover later; in co-op, big AoE turns punish the whole team. I found we survived more consistently when at least one player leaned into block / mitigation instead of everyone going pure damage.
If you hit 0 HP during a fight:
This creates a nice dynamic where the last surviving player can clutch out a win and save the run. We had multiple fights where three of us were down and one carefully blocked and chipped away to turn disaster into a victory.
This creates a nice dynamic where the last surviving player can clutch out a win and save the run. We had multiple fights where three of us were down and one carefully blocked and chipped away to turn disaster into a victory.
Compare prices instantly and save up to 80% on Steam keys with Kinguin — trusted by 15+ million gamers worldwide.
*Affiliate link — supports our independent coverage at no extra cost to you

Even though you’re on one map, your loot and build are completely your own:
On top of that, co-op introduces multiplayer-only support cards for each class. Examples I’ve seen include:
The most important detail is that debuffs like Vulnerable or Weak are party-wide. If one player sticks Vulnerable on an enemy, everyone’s physical damage benefits. That pushed our group into clear roles: one dedicated debuffer, one tank, one heavy damage, one flexible hybrid.
Outside of combat, you share a single map and node progression, but decisions inside those nodes are often personal.
When you move between nodes:
This is where communication really matters. In one disastrous run, half of us wanted elites for relics, the other half wanted safe fights to heal. RNG kept siding with the greedy path and we wiped. Now we talk through the next 2-3 nodes together instead of spam-clicking a direction.
Most node types respect your individuality:
This keeps the co-op flow close to singleplayer in terms of “my deck, my decisions”, even though the path itself is shared.

Campfires add a few extra tools for team survival:
Our early mistake was everyone resting all the time “just to be safe,” which left us under-upgraded and weak. What’s worked better is assigning roles at fires: one player Mend-heals the squishiest ally, someone upgrades a key scaling card, and only the person in real danger uses a full Rest.
Multiplayer uses its own Ascension ladder, separate from your singleplayer progress. Unlocks don’t carry over between the two modes.
That last point is crucial: if one friend has multiplayer Ascension 5 and another only has Ascension 2, the run can only be set to 2. In my group we solved this by doing a few “catch-up” runs with our least progressed player so everyone could climb the ladder together.
Practically, if you want to run something like Ascension 4 co-op:
Once my friends and I stopped treating co-op like four parallel solo runs and more like a coordinated party, our success rate shot up. These are the habits that made the biggest difference:
Once your group internalizes these systems-host-owned saves, scaled enemies, shared map decisions but separate loot—multiplayer starts to feel like a natural extension of singleplayer rather than a bolt-on mode. The game stays true to its deckbuilding core, it just forces you to think about how your build fits into a team instead of only your own survival.
Get access to exclusive strategies, hidden tips, and pro-level insights that we don't share publicly.
Ultimate Guide Strategy Guide + Weekly Pro Tips