Roles are communication shortcuts, not proof that Sephiria has formal classes. Steam lists online co-op for up to four players, and a group can still benefit from saying who is creating space, who is dealing reliable damage, who is setting up an interaction, and who is covering recovery. Each role should have overlap so the party remains functional when a reward is missing or a player is learning.
Finish the room
Use a dependable action and avoid making the team wait for a fragile setup.
Create space
Call movement, focus pressure, or a reset so others know when to stop attacking.
Test the interaction
Reserve inventory and timing only when the team objective justifies the risk.
Cover the break
Take over when a teammate disconnects, misses a call, or loses the intended reward.
Choose jobs before items
Start with the room or chapter problem, then choose the weapon and inventory support. The Co-op Builds page defines the group objective; this page defines how to say it quickly. “I am holding space” tells the team more than a weapon name, and “I need the next reward for setup” explains a pickup without an argument about rarity.
Give every role a fallback
A control player should still have a safe attack. A damage player should know how to retreat. A setup player should be able to stop setting up when the room changes. A flexible player should know which call takes priority. This overlap prevents a party from collapsing because one person was the only holder of a hidden assumption.
Share the arena
Roles can conflict when every player chooses the same position. Agree on a retreat direction and a reset call before a difficult room. Record party size and mode because a two-player route may leave more room than a four-player route. A group result should not be silently presented as solo evidence.
Rewards and inventory
Before taking an Artifact or Tablet, state which role it supports and what space it consumes. If the item enables a team combo, test the interaction in a repeatable context and link to Combos. If the exact rule is uncertain, call it a test lead. The live game should confirm names, shapes, and visible effects.
Boss calls and review
Use one caller for a telegraph and one clear phrase for a reset. The Co-op Bosses page can hold encounter-specific notes. After the session, record which call was understood and which fallback was missing. This turns role advice into a testable improvement rather than a fixed party meta.
Make role handoffs explicit
The group should know what happens when the control player loses space, when the damage player must retreat, or when the setup reward does not appear. Write the replacement call next to the primary job. Handoffs are especially important in a four-player room, where an extra body can create both safety and crowding.
Use the Co-op page for the session review and Co-op Builds for item and inventory choices. Keep the role page focused on communication: one short call, one reset direction, one fallback, and one evidence boundary. If the role requires a specific unverified item, label the dependency as a test lead.
Measure a role by the objective
A role is successful when it solves the stated team problem, not when it produces the highest personal number. For a first clear, survival and readable movement may matter more than speed. For a boss test, a caller who preserves a safe opening may provide more value than a player who attacks during every window. State the objective before comparing roles.
Review that objective when the party size changes.
A role that works for two players may need a different fallback for four.