Core Keeper Co-op Save Owner Guide

#Direct Answer

Core Keeper co-op progress belongs to the world save being hosted. If a player opens a different local copy, the connection can work while the base, bosses, and unlocked areas look wrong. Pick one save as the team's source of truth, have that player host, and verify it with one harmless change before doing a long session.

This is the page for the common co-op problem where the session works but the state looks off. If the connection itself is failing, the fix is somewhere else.

#Pick the Authoritative World

Use the save that contains the team's latest shared work, not the save on the fastest computer. Ask the likely host:

1. Which world has the latest boss defeat or base rebuild?
2. Which world contains the current storage and portals?
3. Who normally starts the session?

Write that answer in the group's chat. A clear owner prevents two almost-identical worlds from drifting apart.

If the team has rotated hosts before, settle that question before anyone tries to reload a backup copy.

#What to check before anyone joins

Before the invite goes out, write down:

• world name
• host name
• last boss defeated
• last base change
• where the latest portal or storage room sits

That small note is useful when the session feels wrong later. It gives the group one shared reference instead of three different memories.

#Run a Two-Minute Join Test

Before farming or fighting, perform a reversible test:

1. The save owner starts the world.
2. Other players join through the same invite method used for the real session.
3. Place one cheap torch or dirt wall near the core.
4. Leave and rejoin once.
5. Confirm the test tile is still present.

If the tile survives, you are in the expected world. Remove it and begin the planned route.

The test matters more than memory. A group can remember the right base and still join the wrong world file.

#When the save still looks wrong

If the test tile is correct but progress still looks off, check the kind of difference before changing anything:

• missing base rooms usually means the wrong host or an older save copy
• missing boss progress usually means a different world branch
• missing items but correct rooms usually means someone joined the wrong session or brought stale expectations from a different backup
• mismatched portals usually means the world file is correct, but the host's latest changes were never saved cleanly

If the group cannot agree after one test, stop and compare the actual save file path instead of guessing from screenshots alone.

#When Progress Looks Missing

Do not immediately repeat a boss or rebuild a room. First compare:

• world name and host
• last known base layout
• portal destinations
• boss trophies or dropped summon items
• the test tile from the previous section

If only one player cannot see the change, they are likely in a different session or looking at a stale local expectation. Rejoin the owner's world before changing anything permanent.

If everyone sees a different version of the same save, stop and recheck the host's world file before anyone overwrites progress.

#Keep the Shared Save Healthy

At the end of a session, let the host finish the save and close the world normally. Keep a single naming convention for the world and avoid passing copies around unless you are deliberately making a backup. In a group with rotating hosts, choose one primary host and one backup rather than letting every player create a competing main world.

Good co-op habits are boring on purpose. The less ambiguity there is around the host, the less often the group has to recover a lost room or duplicate boss state.

#Common mistakes

1. Letting every player keep a different “main” copy.
2. Naming the world differently on different machines.
3. Testing with a major base rebuild instead of one harmless change.
4. Assuming the newest-looking save is the correct one.
5. Starting a long session before the host is identified.

#Stop Conditions and Next Step

Stop co-op troubleshooting when the two-minute test passes. The next problem is then specific:

• route or storage friction: open the base automation baseline
• a returning player's missing context: use the returning player route audit
• a patch-related mismatch: check the co-op server after update checklist
• travel confusion after a rebuild: open the portal network guide

#FAQ

#Does every player need the same world save?

No. The host's world is the authoritative state for that session; other players need to join that world to see its progress.

#Why can I connect but see an old base?

You may have joined a different copy or a different host's world. Run the test-tile check before making changes.

#Should we rotate hosts every session?

Only if the group deliberately maintains a backup. One primary save owner is less error-prone.