Repository navigation
Seamless co-op and split screen: design draft - #701
featureJosh wants to merge 1 commit into
Conversation
The plan for seamless co-op (one story owned by the host, coop saves separate from singleplayer saves, the group connected automatically, the host's world synced to every member after a session) and for split screen on top of it. Design only; the work follows step by step. Co-Authored-By: Claude <noreply@anthropic.com>
|
Findings from the split screen work (#692) that answer some of the open questions here. Addresses are for main 2.0.1 (build 76a489f3). The session can start without the menu, and before the Link Play unlock
Host owns the story
Where a visitor arrives
What exists as code Not answered by this work Related: #700 (heap damage in the renderer with two game processes on one PC) showed up three times during these runs. |
|
Thanks, that settles the session start and the unlock: build step 5 can go, and the session can open right after character creation. Findings from the save and story side (main 2.0.1, same build): Abilities
Link Play menu
Character look is the 12-byte record at decompressed CMNDAT 0x21ff84 (sex, hair, hat, bag, upper, lower, shoes, then colours). With the UUID and the name in SYDAT, that is what to stamp back into a member's copy of the host's save. Still open: the disconnect. The session-lost event (type id 0x5393cfbd) has no direct users; subscribers go through the type registry. It needs a two-instance log, which means two PCs given #700. On who takes which step: if you open |
|
Build step 2 is open as #705 (draft, on top of #692).
The functions it calls and the steps of a visitor's arrival are in the mappings repository, |
|
The disconnect (main 2.0.1, same build). Checked with two instances: host killed while the visitor was in its world, visitor logged. What the visitor gets:
The Link Play session manager is not involved: its state stayed 0 the whole time. The trip comes from For coop mode: the waiting screen hooks |
|
I picked up build step 1 (Co-op profiles in the launcher) and opened a draft PR in #724 on top of Summary of what is included:
Note for the runtime / next steps: |
What it changes
Design draft, no code yet: the plan for seamless co-op and for split screen on top of it. Both features ship in the same release. This PR is where the design is discussed; the work lands in later commits or PRs, step by step (Build order below).
Why
Today's Story co-op runs one story per player inside the host's world. That is behind the reports: visitors do not learn abilities their host learned, and quests desync in the visitor's world. Two stories against one world need workarounds (held quests, per-visitor pickups, talk overrides), and each of them leaks.
Principles
Coop saves (launcher)
profiles.rs).pkp.ini.saveimport::copy_account.Session lifecycle
Save sync after a session
Every member's coop save becomes the host's save with that member's identity stamped back in.
pkp_save_uuid.cpp's machinery (swap_uuidin Split screen: two to four players on one PC #692). Name and appearance are more fields on the same path.Split screen on the coop setup
Split screen (#692) becomes a coop group whose members share one PC. It keeps its windows, layout and controllers; its saves follow the coop rules.
#692 lands first; coop builds on it.
Open questions
Build order
story_holdandstory_pickupsremoved.Pros
copy_account, the UUID swap, split screen's per-window roles, the game's own Link Play.Cons
For players
CHANGELOG.md## Unreleasedhas an entry (Before / Now / Still not), or this change is not player-facing: design only, no change yet🤖 Generated with Claude Code