Most Core Keeper connection problems have one of four causes: the host or dedicated server is not ready, players are on different game or mod versions, the platform combination is unsupported, or the delay comes from a client, network path, or overloaded server. Start by identifying whether one player has low frame rate, everyone sees delayed actions, joining fails, or the server process stops. Then verify the current Game ID, match builds and mods, and test client performance separately from server load. Do not delete the world while troubleshooting; make a dated backup and preserve the console logs first.
The steps below cover hosted worlds and official dedicated servers, including cross-play limits, Game ID handling, simulation-load fixes, safe recovery, and the information support will need if the problem continues.
What kind of Core Keeper problem are you seeing?
The symptom determines the first test. Low frame rate on one computer is usually a client-rendering issue; delayed movement or actions for everyone points to networking or server simulation; a failed join often comes from readiness, Game ID, platform, version, or mod mismatches.
| Symptom | Most likely area | First check |
|---|---|---|
| One player has low FPS while others play normally | That player’s graphics settings, background load, or local connection | Restart the game and Steam, then test that computer on wired Ethernet if possible |
| Everyone sees rubber-banding, delayed mining, or doors opening late | Network path or server simulation load | Check the server console, CPU/RAM use, world activity, and player distribution |
| “Game not found” or no join result | Stale Game ID, server not ready, unsupported platform path, or a version/mod mismatch | Wait for loading to finish and copy the newly displayed Game ID |
| Disconnect during loading | Different builds or mod sets, unstable route, or a server process that is stopping | Reproduce once with matching, unmodded clients and inspect the final console lines |
| The dedicated-server window closes or stops responding | Process, resource, configuration, or world-data problem | Stop cleanly, preserve logs and a world backup, then test the newest known-good copy |
How do I join a hosted Core Keeper world correctly?
For in-game player hosting, the host must already be inside the world. The Game ID is useful only after that world has finished loading, so an ID copied during startup or before a restart can fail.
- Have the host launch Core Keeper, select the intended world, and wait until the character can move normally.
- Open the multiplayer or hosting screen and copy the Game ID that is currently displayed. Do not reuse an ID saved from an earlier session.
- Send that newly printed ID to the other players through a private message or voice channel.
- Each joining player selects Join Game, enters the ID exactly, and waits for the connection process to complete.
- If the ID is rejected, have the host leave the world, restart the game and Steam, load the world again, and distribute the fresh ID.
Player-hosted multiplayer uses Steam’s networking back end. The host’s game must remain in the world for the session; if the host exits, the hosted session is no longer available.
Why does Core Keeper say “game not found”?
“Game not found” is commonly a readiness or identity problem rather than proof that the world is damaged. A dedicated server must finish loading before its Game ID is copied, and an ID from before a restart is no longer the correct one.
Check the host or server state
- For a hosted world, confirm that the host is fully inside the world, not still at a loading screen or menu.
- For a dedicated server, wait for the process to finish initialization and use the Game ID printed by the current process or recorded in
GameID.txt. - Copy the complete ID without added spaces or line breaks. Dedicated-server IDs are documented as 15–28 alphanumeric characters, with character restrictions listed by the Core Keeper Codex.
- After every stop and restart, obtain a new ID. Never keep using the value from the previous process.
Eliminate platform and build causes
PC storefronts can cross-play through PlayFab, and PlayFab Party does not require a separate PlayFab account or external registration. Console-to-PC cross-play is not supported; cross-play is available within compatible device families. If a PC player is trying to join a console player, or vice versa, no amount of port configuration will make that path work.
Are your Core Keeper versions and mods identical?
Every participant and the server must run compatible builds. A game update can change connection behavior, so update the game and the dedicated-server tool together, then perform a complete restart rather than leaving an old process running.
- Close Core Keeper, Steam, and the dedicated-server process.
- Install all pending updates for Core Keeper and the dedicated-server application.
- Restart Steam, launch the game, and check that every player is on the same current build.
- For a modded world, compare the complete mod list and each mod’s version on every client and on the server.
- Try one connection with all mods disabled. If the unmodded session works, re-enable mods in a controlled group until the incompatible item is identified.
A mismatch can appear as “Game version mismatch,” a loading disconnect, or a join that never completes. The official patch history includes fixes for connection cancellation, IPv6 dedicated-server joining, and several lag-spike cases, so an issue that began immediately after an update may be version-specific rather than a damaged save.
Does Core Keeper support cross-play between your devices?
Cross-play is limited by platform family. Fireshine Games states that Core Keeper supports cross-play between PC platforms through PlayFab; PlayFab Party does not require a separate account. Console-to-PC cross-play is not supported.
| Players’ devices | Supported path | Important limit |
|---|---|---|
| Different PC storefronts | Supported through PlayFab | All players still need matching game and mod versions |
| PlayStation 4 and PlayStation 5 | Cross-play within the supported console family | Cannot use the console-to-PC path |
| Xbox One and Xbox Series | Cross-play within the supported console family | Cannot use the console-to-PC path |
| Nintendo Switch systems | Within the supported Switch player group | The current support FAQ lists a smaller player limit |
The current support FAQ lists a maximum of 1–8 players on PC, PlayStation 4/5, and Xbox One/Series, and 1–4 players on Nintendo Switch. A failed join caused by an unsupported device combination cannot be repaired by changing the Game ID, router, or server files.
How can I tell whether lag is local, network-related, or server-side?
Separate the three layers before changing settings. The same “lag” label can describe a low-FPS client, packet delay between players and the server, or a simulation that cannot process the world quickly enough.
When only one player is affected
Restart that player’s game and Steam first. Close unnecessary background applications, lower demanding graphics options, and check whether the frame rate improves while standing in a quiet area. A single-player Ethernet test is useful because it removes Wi-Fi variability from the diagnosis; a Cat6 Ethernet cable is an isolation tool, not a cure for server simulation lag.
If the player’s movement is smooth but actions arrive late only on Wi-Fi, test closer to the access point or on wired Ethernet. If frame rate remains low even offline or in an empty area, continue with client-performance checks rather than editing server files.
When everyone is delayed
Ask each player whether mining, opening containers, enemy movement, and doors are delayed at the same time. Shared delay suggests the network route or the server’s simulation workload. Watch the dedicated-server console while reproducing the problem and note CPU, memory, player count, and the last lines printed.
When the delay appears only in one region
Players spread across distant parts of a heavily explored world can increase simulation work. Have everyone meet in one area for a short test. If the delay falls when the group is together, world activity and simulation load are more likely than an individual graphics problem.
What causes dedicated-server lag, and how do I reduce it?
Dedicated-server lag often comes from cumulative simulation work rather than one defective setting. Reduce the load in small, reversible changes and observe the console after each change.
World and player activity
- A heavily explored or advanced world contains more active areas and entities to process than a new test world.
- Players operating in separate regions can keep more areas active simultaneously. Test with the group in one region before changing the world.
- Large conveyor, drill, and farm automation systems can create continuous work. Temporarily stop or simplify the busiest systems to see whether tick responsiveness returns.
- A player cap above the default increases the worst-case workload. Set the cap to the number of people who actually need access.
Mods and restarts
Remove unnecessary mods while diagnosing. Even a mod that appears cosmetic can add processing or produce incompatibilities after an update. Once the unmodded server is stable, add required mods back one at a time.
Schedule clean restarts for a long-running world, especially after major updates or periods of heavy automation. A restart is not a substitute for correcting a load source, but it gives you a consistent baseline and clears an overloaded process without touching world data.
Resource monitoring
Record CPU and RAM usage during a lag spike, not only when the server is idle. A server that has free memory but one saturated CPU core may still simulate slowly. Conversely, memory pressure or an operating-system kill can explain a process that stops rather than a gradual delay.
Do I need to port-forward a Core Keeper dedicated server?
No, not for the official dedicated-server application. The dedicated-server announcement says player-hosted multiplayer uses Steam’s networking back end and that port forwarding is no longer necessary for the official setup. Adding router rules can complicate troubleshooting and does not fix an unsupported platform combination, stale Game ID, or version mismatch.
The official reference documents command-line options including -gameid, -port, -ip, and -maxplayers. Use them only when your deployment requires a specific binding, port, address, or player limit. Keep the default networking path while diagnosing a normal installation, and change one option at a time so a new configuration error is not confused with the original problem.
Should you use a hosted world or a dedicated server?
A hosted world is the quickest route for a small group when one player can stay online. A dedicated server is better when the world must remain available without that player, but it adds operational work.
| Consideration | Player-hosted world | Official dedicated server |
|---|---|---|
| Host availability | The host must be inside the world | Runs independently of any player being in-game |
| Always-on access | Ends when the host leaves | Can remain online as a separate process |
| Setup | Load the world and share the current Game ID | Install, configure, monitor, and update the server process |
| Networking | Uses Steam’s networking back end | Official setup does not require port forwarding |
| Backups | The host is responsible for world copies | Operator must back up world, configuration, and logs |
| Mods | Host and players must keep sets compatible | Server and every connecting player must keep sets compatible |
| Monitoring | Mostly limited to in-game symptoms | Console, CPU/RAM, player cap, and restart schedule can be monitored |
| Recovery | Restart the host and generate a new Game ID | Stop cleanly, preserve logs, and restore a known-good world copy if necessary |
How do I change dedicated-server settings without making recovery harder?
Back up first, then make a single, documented change. Keep the original command line and configuration so you can undo the change if the server stops accepting connections.
- Stop the server cleanly and wait for the process to exit.
- Copy the world, configuration, and current logs to a dated backup directory.
- Write down the existing values for
-gameid,-port,-ip, and-maxplayers, if present. - Change only the option required by your deployment. For example, adjust
-maxplayersto a realistic cap rather than raising it as a test. - Start the server and wait until loading is complete.
- Copy the newly printed Game ID and run a join test with one unmodded client before inviting the full group.
Do not move or delete world files while investigating a connection symptom. A path mistake can look like data loss even when the original world is intact.
How do I recover a world safely after crashes or repeated disconnects?
Recovery should preserve evidence and give you a rollback point. Deleting the world first removes the information needed to identify whether the problem was a process failure, a mod, or a damaged save.
- Stop the server cleanly. If it is unresponsive, record the visible error and the last console lines before force-closing it.
- Copy the world and configuration to a dated backup, and preserve the complete server log.
- Record the Core Keeper and dedicated-server build numbers, player count, world progression, enabled mods, exact symptom, and time of the failure.
- Start the newest known-good world copy with the same build and no mods.
- Run a short join and movement test. If it is stable, add required mods back one at a time.
- If the known-good copy also fails, compare the console output with the original and test a temporary new world to separate installation or networking faults from world-specific data.
If the problem continues across a clean test, use Fireshine Games’ official bug-report route and include the build, platform combination, fresh Game ID behavior, logs, reproduction steps, and backup status. Do not upload private account information or an unredacted file containing personal paths.
What should you check after a Core Keeper update?
Updates can change networking and performance behavior, so use a short post-update checklist before assuming the world is broken.
- Update the game and dedicated-server tool together.
- Restart Steam, the game, and the server process completely.
- Confirm every player’s build and mod versions.
- Generate and distribute a fresh Game ID after the server finishes loading.
- Run one unmodded join test before restoring the full mod set.
- Check the console for connection-cancellation, IPv6-join, or lag-spike errors.
- Make a dated world backup before changing settings or data paths.
Frequently Asked Questions
Can a Core Keeper server keep running when the host logs out?
Yes, an official dedicated server runs as a separate process and can remain available without the host’s game being open. A normal player-hosted world is different: the host must stay in the world for others to play.
Why does my new Game ID stop working after I restart the server?
The ID shown by the old process should be treated as expired for troubleshooting purposes. Wait for the new process to finish loading, then copy the value it prints or writes to its current GameID.txt file.
Will reinstalling Core Keeper fix a loading disconnect?
Only if the installation itself is damaged. First test matching builds, identical mods, the supported platform path, and a clean unmodded connection; reinstalling cannot correct an unsupported console-to-PC combination or an overloaded simulation.
What information does support need for a server bug report?
Provide the game and server build, platforms, player count, world progression, mod list, exact symptom, reproduction steps, timestamp, and the final console lines. Keep a backup of the world and configuration before changing files.