Requirements before inviting friends
Every player should complete the Prologue or Tutorial before attempting co-op. The collected guide places the multiplayer entrance at the Mysterious Door in Bunnyville after that introductory progress. A guest who has not reached the same access point may receive an invite but still be unable to enter the lobby flow.
Confirm that all players are running the same current game version through Steam. Make sure Steam Overlay and the friends interface work before creating the room. Solving those prerequisites first separates access problems from an actual lobby failure.
Create the Steam lobby
The host travels to the Mysterious Door and chooses the option to create a Steam lobby. Wait until that room exists, then send a new invitation through Steam. The order matters because an invite sent before creation may point to no active session.
Guests accept the current invitation after finishing the tutorial. Discard invites left over from an earlier lobby, especially if the host recreated the room. Once everyone appears, confirm the party before beginning the shared run.
- Finish the Prologue or Tutorial on every account.
- Host: go to Bunnyville’s Mysterious Door.
- Host: create the Steam lobby.
- Host: send a new Steam invite after creation.
- Guests: accept the newest invite and join.
- Confirm the party before entering the adventure.
What co-op supports
Official material supports online co-op for up to four players. The collected scope also describes trading items and reviving fallen teammates while exploring the tower. These systems make inventory decisions a party conversation rather than four isolated solo builds.
Trade a reward to the player whose trigger, weapon branch, or inventory can use it consistently. Before dropping or rearranging anything, confirm that the receiving player has space and that the item supports their route. A powerful piece can be weaker in the wrong inventory if it breaks an established Tablet relationship.
Revives and fight positioning
Do not stack every player on the same side of an encounter. Shared positioning can cause one pattern to hit the entire party and make a safe revive impossible. Maintain enough separation that at least one player can observe the arena and approach a fallen teammate during a recovery window.
Treat a revive like a committed attack. Identify the active pattern, move only when the route is clear, and be prepared to leave if the window closes. A failed rescue that downs another player is worse than waiting through one additional cycle.
Build coordination
Agree on broad roles without pretending Sephiria requires fixed classes. One route may control space, another maintain ranged pressure, and another take close-range punish windows. The important coordination is avoiding duplicate claims on a reward when one player has a much stronger trigger or adjacency for it.
State what the build needs before a reward screen. Name the weapon direction, core trigger, and missing support rather than only calling an item “best.” That information makes trading faster and preserves useful inventory space across the team.
Fix a failed invitation
If a guest cannot enter, the host should recreate the lobby and send a new invitation after the new room exists. Guests should ignore stale invites from the previous room. Then verify matching versions and test Steam Overlay on both machines.
Restarting the lobby is more informative than repeatedly accepting the same failed invite. If only one player fails, compare that player’s tutorial completion, game version, Overlay, and network state with a player who joined successfully. Change one variable at a time so the party knows which step resolved the issue.
| Symptom | First checks |
|---|---|
| Invite opens but no lobby appears | Confirm the host created the room before sending it |
| Old invite keeps failing | Recreate lobby and use only the newest invitation |
| One player cannot join | Confirm tutorial completion, version, and Steam Overlay |
| Party disconnects during play | Rebuild the room and check current official patch notes |
| Problems occur after an update | Verify every player has the same build before testing again |
Patch context
TEAM HORAY’s collected 1.0.23 announcement mentions fixes for a small number of connection terminations during combat and while selecting a Miracle. That confirms those failures existed in that version and received a targeted fix. It does not guarantee that every current network problem has the same cause.
When reporting a repeatable issue, record the version, host and guest roles, player count, action in progress, and whether the failure occurs in a fresh lobby. That evidence is more useful than a generic “multiplayer broken” report and avoids copying an old workaround into a later patch without testing it.