Private co-op in this game does not use a matchmaking lobby; instead, the host launches a room through a batch file with flags that pick the mode, the co-op style, and a character name. Guests run a join command, the host shares a private offer, and the two sides exchange an answer and a separate invitation before play begins. Only same-computer Chrome connections are verified so far. Links across separate machines or routers have not been confirmed and can fail, and there is no automatic matchmaking or relay server. Treat co-op as an extra experiment that you can ignore while playing solo.
Before You Start
- Use a recent experimental build; an older demo may lack the private co-op screen entirely.
- Have a current Chromium-based browser available.
- Work from the extracted game folder that contains the batch files and PRIVATE_MULTIPLAYER.md.
- The documented flow assumes Windows with a keyboard and mouse. Controller and Steam Deck use is still untested.
Host Commands
Each style of play has its own flag value. Personal adventures give every participant an individual character, separate world progress, and separate saves:
BetaEarthSovereignty.bat --private-coop --mode sovereignty --coop-style personal_adventures --coop-character YourName
To play Second Chances instead, swap the mode value:
BetaEarthSovereignty.bat --private-coop --mode second_chances --coop-style personal_adventures --coop-character YourName
In a shared campaign, all players steer the same character, so change the style flag:
BetaEarthSovereignty.bat --private-coop --mode sovereignty --coop-style shared_campaign --coop-character YourName
Guest Command
BetaEarthSovereignty.bat --private-join
Connection Sequence
- The host picks the option to connect privately to another computer.
- An offer goes out to the guest.
- The guest sends back an answer.
- The host accepts that answer, then sends a game invitation as a separate step.
- Every guest needs a new offer; do not pass one offer around a group.
- Keep offer, invitation, and recovery codes to yourself.
- If a reply never arrives, choose Resolve last action. Do not resend the original action.
- Guests exit with Leave room; the host closes the session with Save & close room.
Choosing a Co-op Style
| Style flag | How it works | What to know |
|---|---|---|
personal_adventures | Each person keeps their own character, world state, and save file. | Individual stories advance on their own. You can join eligible shared objectives for one-time rewards of no more than 10 in-game credits, but joining is optional. |
shared_campaign | The whole group controls one character. | Swap out the style flag as shown in the host command section. |
Reconnecting and Reopening Saves
PRIVATE_MULTIPLAYER.md, shipped with the game folder, describes how to reconnect and reopen saves after a drop. Follow it when a session ends unexpectedly. Since cross-machine and cross-router links are unverified, a failed join attempt may mean nothing more than an untested network setup rather than a typing mistake in your command.
Back Up Before Version Changes
Co-op uses the same save layout as solo play. In the combined Windows package, progress lives under runtime/sovereignty and runtime/second_chances inside the game directory; standalone builds from earlier releases may store it elsewhere. Shut the game down, then copy the entire runtime folder together with your installed build, and store that copy away from the one you actively use. Never drop an older executable on top of a newer save, and never point two installs at the same live save. Steam Cloud support exists, but confirm your account finished syncing, and keep the local copy regardless. Format 5 is used by newer releases. Going back to a format-4 build means restoring the database backup captured before the upgrade; leave that backup untouched, because the upgraded database serves the newer build.
If Something Goes Wrong
- Write down the mode, build version, your most recent action, what you expected, and the exact error.
- When a connection drops, review what happened before redoing any choice or resource-spending action.
- Run
BetaEarthSovereignty_Export.batto gather local support details. Read the output before you pass it on, watching for private access links or personal information. Nothing is uploaded on its own. - For a launch warning, keep the browser, Windows, and security tools running while you investigate.
Event Response Not Registering
Open JOURNAL EVENTS and confirm where the event is. Reply from that location once no enemies remain and bleeding and recovery are settled; a blocked reply stays unspent. Since reading does not freeze the action, clear any danger first.
Reloading for a Different Event
Each event that was selected, along with its decisions and consequences, is stored. Reading or reloading does not reroll it. Keep exploring and making progress to reach the next outcomes.