Keep the correct Core Keeper world and Game ID after restarts

World Index selects the world slot. Game ID identifies the online session. They are independent, so an unchanged world can still need a fresh invitation if its session ID changes.

Make the change

  1. Record World Index, World Name and the current Game ID before making changes.
  2. Stop the server and take a backup of its existing save data.
  3. Keep World Index unchanged when continuing the same world.
  4. If you want a persistent Game ID, use the valid ID generated by this server in the Game ID field rather than inventing a short name.
  5. Start and read GameID.txt or Console for the active ID, then reconnect and inspect familiar structures.
Controls used in this task
Panel fieldWhat to keep in mind
World IndexSelects the Core Keeper world slot. Keep the current index when you intend to continue the same world.
World NameNames the Core Keeper world. World Index selects the save slot; changing this name is not a way to select a different saved world. Up to 100 characters.
Game IDCore Keeper’s connection identifier. Keep the existing valid ID to avoid changing the code your group uses; an empty or invalid value causes the game to generate another one.

Check the result

If the server issues a new ID despite your setting, check the field’s validation rules and whether the supplied value was accepted. Do not publish a new world seed as though it were a connection ID.

Related guides

Core Keeper server not showing up or unable to connect · Core Keeper server settings: Startup and configuration

Documentation

Server configuration reference

Was this article helpful?

Your feedback helps us improve our guides.

Written by Konnect HostingUpdated 2 min read