Keyword Guide
Sephiria supports four-player multiplayer in the collected 1.0 material, and the strongest documented approach is to split combat roles instead of making every player chase the same Weapon plan.
Direct Answer
The supplied 1.0 gameplay transcript explicitly describes four-player multiplayer and says different players can use different playstyles, including support. The broader researched game summary also describes online co-op for up to four players. This page does not claim local co-op, cross-play, or console multiplayer because those details do not appear in the supplied keyword sources.
Exact host and join steps are To be confirmed. The materials mention a co-op mode and multiplayer roles but do not show a complete lobby flow, invitation menu, connection requirements, or region settings. Use the current in-game interface and official channels for those version-sensitive details.
Practical setup
The flow below is a community-reported route, not an in-client test. A competitor guide reports that multiplayer becomes available after the first death event, the host creates a Steam lobby from Bunnyville, and guests join through a Steam invitation or a room code. It also reports public, private, and invite-only privacy options. Keep those labels provisional until the same steps are observed in the current client.
Community reports say a fresh save does not immediately expose multiplayer and that the first death event is the unlock point. This timing is pending direct verification.
The reported route starts in Bunnyville: open the Mysterious Door, choose Multiplayer, then create a Steam lobby. Menu names and location are pending direct verification.
The same report lists public, private, and invite-only rooms. For a fixed group, invite-only is the reported option; the current menu wording is pending verification.
Use a Steam invite or let guests enter the room code, according to community documentation. Confirm that everybody appears in the lobby before starting.
The four-player ceiling is supported by the collected game material. Assign range, room clear, defense, and elemental-control priorities before the first reward screen.
Evidence used for the provisional flow: community co-op reference. The source reports lobby behavior, but it is not an official test record.
Status table
| Item | Current evidence | Status | | --- | --- | --- | | Maximum party size | Collected 1.0 material and Steam-facing summaries describe online co-op for up to four players. | Confirmed: up to 4 | | Room creation | Community source reports a host-created Steam lobby from Bunnyville. | Community report · test needed | | Steam invitation / room code | Community source reports both routes. | Community report · test needed | | Reviving a fallen teammate | Store/community descriptions mention reviving fallen companions, but they do not document the button, timer, range, or failure state. | Feature reported · procedure unconfirmed | | Dropout and rejoin | No reliable source in the collected material documents reconnect, host migration, or whether a returning player keeps run progress. | To be confirmed | | Cross-platform play | No source confirms cross-platform play; the documented platform scope is Steam PC/macOS. | To be confirmed | | Guest rewards and permanent progress | The collected sources do not prove how unlocks, currency, or saves are assigned after a guest leaves. | To be confirmed |
This separation is intentional: a four-player cap does not itself prove lobby creation, cross-play, reconnect, or guest-save behavior. The community multiplayer reference is useful for planning, but version-sensitive details should be rechecked in-game.
Role Split
The Weapons research recommends a simple division: one player on Crossbow or Staff for safer damage, with another on Greatsword for room clear. Sword and Shield or a sustain-leaning Staff is listed as a reasonable support direction, while a fragile Dagger plan without a reviver is identified as a risk. These are community recommendations rather than mandatory classes.
Each Weapon still has its own normal, dash, and special actions plus branching Anvil routes. A team can cover range, stagger, elemental pressure, blocking, and mobility without forcing identical builds. The sources do not define fixed tank, healer, or damage roles, so treat those labels as practical coordination rather than official matchmaking categories.
Shared Planning
The Weapons source advises trading Anvil priority so two players do not starve the same upgrade pool. It also suggests that players choose a Weapon spine based on the job they can perform safely, then match elemental offers to the Artifacts and Tablets already on their boards. The exact way Anvil choices are shared or separated in current co-op is To be confirmed.
Build research supports the same coordination principle. Frozen Smelt needs a specific Glacier core, Formless Dance variants depend on different starting conditions, and Minigun routes need MP support after documented changes. If every player forces a core-heavy recipe, the group has fewer safe pivots when pieces fail to appear.
Support
The materials do not provide an official support skill list, but they do identify Weapon and inventory directions that can reduce pressure. Sword and Shield provides blocking and defensive tools, Staff can contribute elemental area control, and Greatsword can clear packed rooms. Artifact-created Companions such as Collin and Mini Ballista are allied units rather than selectable players.
Support should not be confused with guaranteed healing. The older guide mentions recruiting Colin against a difficult final boss and describes lifesteal, MP management, defense, and revival-like effects in specific builds, but these are not universal co-op abilities. Current teammate revive rules and any shared healing behavior are To be confirmed in the supplied sources.
Build Examples
The build library labels its six featured setups by evidence and recorded version. Some routes have community clear claims, while Formless Dance and Minigun include variants with video proof and importable presets. The Biryuu Katana source is described as having co-op support, but that label does not prove that every component behaves identically for all party members.
Keep evidence attached to the exact variant. The White Rabbit Minigun video shows a Hard 35 run, while the Scholar Lizard tank version is a different 1.0.23 recipe with no attached same-run clear video. In co-op, a proven solo setup can be a starting point, not proof of party-wide balance or compatibility.
Connection Limits
The seven research files do not document ports, NAT behavior, reconnects, host migration, input-device mixing, latency compensation, or save ownership. They also do not verify whether a guest keeps every unlock or currency gain after leaving. Each of these details is To be confirmed and should not be inferred from the existence of four-player multiplayer.
Mod compatibility online is also unconfirmed. SephiriaMod changes Weapons, stats, currency, Costumes, and other progression, but its source does not provide a verified multiplayer safety statement in the collected text. Do not assume a client-side tool is harmless to other players or accepted in an online session.
Official troubleshooting
TEAM HORAY's technical-support FAQ describes a specific multiplayer failure: the room name shows ERR, or the Create Room and Enter Code buttons do not respond because the game could not read the Steam account at launch. The FAQ recommends fully closing Steam, confirming no steam.exe process remains, removing a steam.cfg file that blocks Steam updates, launching steam.exe directly to finish the update, and then starting Sephiria from the Steam Library.
It also recommends avoiding a network accelerator or VPN for the first Steam launch and keeping Steam and the game at the same privilege level. These are official connection-recovery steps, not proof of a particular Host, Invite, Join by Code, Mysterious Door, save-ownership, or reconnect flow. Those in-game steps remain To be confirmed until directly observed in the current client. Read the official multiplayer troubleshooting section for the source wording.
Practical Checklist
Before descending, agree on Weapon roles and decide which player will prioritize range, room clear, defense, or elemental control. During the run, communicate when a core build piece appears and be willing to pivot rather than contest every reward. Keep enough MP and movement for boss patterns instead of relying on teammates to rescue an unstable damage loop.
After the run, use Destiny Inscription and village progress to strengthen the next attempt, but verify current unlock behavior in game. If the lobby or invitation flow differs from older footage, use the current interface rather than an unverified step list. The verified scope is four-player multiplayer; the detailed setup procedure remains To be confirmed.
Related guides
Compare the six Weapon roles before assigning range, defense, or room-clear jobs. Use the Sephiria build library for adaptable Artifact routes, and check Artifacts and Tablets when planning each player's inventory pressure.
Verification note
Last verified against the supplied Sephiria research set. Version-sensitive claims retain their source version; missing paths, compatibility details, and current balance values are marked To be confirmed rather than guessed. See the site's research sources for the full method.
