- Pick the host and the shared goal first.
- Assign route, gather, and storage roles before leaving.
- Keep shared progress visible so nobody crafts the same thing twice.
Shelf-style database
Co-op pages should answer how the team should behave, not just what multiplayer exists.
Use this shelf when the co-op topic is named and the next question is host rules, shared progress, role split, or first-session structure.
Co-op entries
Use the row that matches the team problem.
| Co-op topic | Main value | When it matters most | Best next page |
|---|---|---|---|
| First-session roles | Stops duplicated work from the start | When the team is busy but nobody owns the next goal | First-session roles |
| Hosting rules | Clarifies who controls progress and saves | When players are unsure what the host is actually deciding | Hosting |
| Shared progress | Prevents mismatched expectations after reconnecting | When the session continues across different players and timings | Shared progress |
| Co-op progression | Keeps the team moving toward one practical goal | When the session exists, but the save still is not advancing cleanly | Co-op progression |
Co-op shelf notes
What this co-op shelf should answer before the team starts another run.
Co-op pages should keep the group from repeating the same work in parallel. The best shelf makes the host, role split, and handoff rule obvious before the session begins.
- Starting the session without a handoff note.
- Letting every player solve the same blocker separately.
- Mixing solo route habits with team progress rules.
- Open Co-op Center for the broader team workflow.
- Open First-session roles if the team still needs a split.
- Open Tools if the session needs a cleaner checklist first.
Co-op value check
What the shelf should decide once the team topic is named.
When the co-op question is already clear, the page should explain how the team should split work, how progress stays visible, and what the next support page is if the session still feels messy.
- Assign the host and the run goal first.
- Keep one player on the route and one on the support loop.
- Use shared progress notes so the next session starts cleanly.
- Starting without a plan for who owns what.
- Letting everyone solve the same blocker twice.
- Forgetting that the host and the session flow are part of the answer.
- Open Co-op Center for the broader team workflow.
- Open Co-op progression if the team already has roles but not momentum.
- Open Tools if a cleaner checklist is still needed.
Co-op depth
What the co-op shelf should tell the team before they start.
Co-op pages should make the team easier to run, not just prove multiplayer exists. The useful answer is who hosts, what each player handles, and what progress should be expected to carry over.
- Decide host rules and role split before the session starts.
- Use the page to stop duplicate work, not just to explain multiplayer.
- Hand off to the co-op guide when the team needs a practical first session plan.
- Treating co-op as a yes-or-no feature page.
- Leaving session roles vague until the run is already noisy.
- Ignoring how save ownership or progress carry-over affects the whole session.
- Open Co-op Center for the broader team hub.
- Open Co-op progression for the session plan.
- Open Troubleshooting if the session behavior looks wrong.
Team triage
Which co-op problem should the group solve before diving again.
Co-op content becomes useful when it reduces repeated team confusion. The shelf should help the group decide whether the blocker is hosting, role split, shared progress, or a stale update-sensitive rule.
| Team problem | Fix before launch | Open next |
|---|---|---|
| Everyone gathers the same items | Split gather, route, and storage roles | First-session roles |
| Progress feels unclear after a session | Write a shared handoff note | Shared progress |
| Host or save ownership is confusing | Decide host rules before the run | Co-op progression |
| A multiplayer answer may have changed | Check update-sensitive notes first | Updates |