How to Host a Co-op Campaign in Solasta: Crown of the Magister

Choose the original game’s campaign

These instructions concern Solasta: Crown of the Magister on PC. The later Palace of Ice release confirms online co-op across Crown of the Magister, Lost Valley and Palace of Ice. The menu procedure below comes from Tactical Adventures’ original co-op walkthrough; its old beta-branch enrollment steps are not needed to explain the session workflow. [1] [2]

Create the room and decide who may join

Steps

1. Open Multiplayer. The developer’s walkthrough starts on Create Game; enter a session name your friends can recognize. Set a password if you want to limit access to people who know it. The password is case sensitive. [2]
2. Choose whether the room should be visible. With no password, a public room can be joined by anyone. A private room is hidden from the lobby browser even for someone who knows its password; the Steam walkthrough uses invitations or joining through Steam Friends for that case. [2]

Choose New Adventure or Load Game

New Adventure starts a campaign chosen by the host, including its difficulty. Each player can select or create a character in the room. Load Game instead continues the saved party: players use characters already in that save rather than creating replacements for the existing campaign. [2]

Steps

1. For a loaded campaign, assign the saved characters to players. One player may control more than one character. Once everyone is ready, start the game from the host’s room. [2]

Have friends join the correct session

Steps

1. The joining player opens Multiplayer, chooses JOIN GAME and selects the host’s Server Region. Refresh the list if needed, then select the room and enter its password when required. A private room will not appear in that browser. [2]
2. For a new adventure, have every player click Ready before the host starts. For an existing campaign, wait for the host to assign the saved characters, then click Ready. Agree who will keep the continuing campaign save; Tactical Adventures expects the host to make saves even though everyone can save. [2]