# Multiplayer Connection Checklist > Source: https://indiegameswiki.com/wiki/core-keeper/multiplayer-connection-checklist > Part of the Core Keeper wiki on Indie Games Wiki. License: CC BY-SA 4.0. > Last updated: 2026-10-17T21:42:18.619Z The multiplayer connection checklist is a way to check platform compatibility, join a friend's Core Keeper world, and collect useful evidence when the connection fails. ## Check the group before sharing a code For a normal player-hosted session, compare the group's platforms with this table compiled from the publisher's support FAQ. A Game ID does not remove platform restrictions. [Publisher multiplayer FAQ](https://fireshinegames.co.uk/customer_support/core-keeper/) | Group | Compatibility check | | --- | --- | | Steam, GOG, Epic Games Store or Microsoft Store on PC | Enable cross-play in gameplay settings when mixing PC storefronts | | PlayStation 4 and PlayStation 5 | The publisher supports play within the PlayStation family | | Xbox One and Xbox Series X or S | The publisher supports play within the Xbox family | | PC and a console | The publisher does not support this combination | The FAQ lists up to eight players for PC, PlayStation and Xbox, and four for Nintendo Switch. These are player-hosted limits, not a promise about custom dedicated-server configurations. [[Common Questions]] distinguishes ordinary hosting from running a separate server. ## Join the host's current world The host enters a world with a character, opens the pause menu with Escape on PC, and uses Copy game ID. Send that code privately. The joining player selects Join Game, pastes it into Enter Game ID, and joins. Use a freshly copied code when checking a failed attempt. [Publisher joining instructions](https://fireshinegames.co.uk/customer_support/core-keeper/) ## Work through a failed connection This is a diagnostic order, not a claim that each check fixes every network error. Change one condition at a time and record the result. | Check | Evidence to collect before the next attempt | | --- | --- | | Group matches the compatibility table | Each player's platform and PC storefront | | Everyone is using the same release | The displayed game versions, after checking for updates | | The host is in the intended world | Confirmation from the host, followed by a freshly copied Game ID | | Mixed PC storefronts have cross-play enabled | The gameplay setting checked by each player | | The failure can be repeated | The exact message, who hosted, who joined and when the error appeared | Checking versions has a documented reason: the publisher's earlier stability notes fixed a session-ending problem involving an outdated client joining a newer host. The notes also describe fixes for hidden network errors and interrupted cross-play sessions. They are historical bug fixes, not evidence that a current failure has the same cause. [Post-launch stability notes, pages 1 and 6-7](https://fireshinegames.co.uk/wp-content/uploads/Core-Keeper-Patch-notes-Post-1.0-1.0.0.16.pdf) ## Send a useful bug report If the checklist does not isolate the problem, report the exact sequence rather than only "multiplayer is broken." Include the platform/storefront list, versions, host and joining roles, full error message, and whether the same pair can connect with their roles reversed. Keep Game IDs and personal account information out of public screenshots. The publisher links its bug-report form from the [Core Keeper support page](https://fireshinegames.co.uk/customer_support/core-keeper/). For a new group's first expedition after connecting, use [[Tips for Beginners]] and agree which characters and world to use before gathering resources.