Core Keeper Co-op Guide: 1-8 Players, World Saves and Boss Scaling

Core Keeper keeps two separate save files for every explorer. The world save holds everything fixed in place: dug-out terrain, the base around the Core, lit statues, defeated bosses and the uncovered map. The character save holds everything personal: your 12 skill levels, your gear, your inventory and your character type. Neither file contains the other, and that separation drives every co-op habit in this guide.

Because the files are separate, a single character can enter any number of worlds, local or remote. Keep a settled solo world of your own, take the same character into a friend's fresh world on Friday night, and come home on Sunday with new gear and higher skills, with no progress lost on either side. A visiting character arrives with its own equipment and levels, which cuts both ways: a veteran makes an enormous difference in a young world, so crews who want a shared fresh start should roll new characters together, while crews who want help can invite a geared friend in as heavy support.

Practical housekeeping follows from the split. Back up both files before experimenting: a world backup protects the shared base, a character backup your personal progress. Hosts should treat the world file as the crew's shared property: it is the one file nobody can reconstruct from their own save if it is lost. Agree on one main crew world early, because boss kills, statue progress and base building all live in the world file, and scattering sessions across four half-finished worlds means four sets of early bosses to redo. The character side needs no such discipline: one well-kept character can serve every world you will ever join.

Boss health in Core Keeper is calculated from the players present, and three rules describe the whole system.

The count that matters is who is in the world when the fight happens. When a player joins or leaves, boss health is recalculated automatically, so a boss engaged by a duo and finished by a trio changes strength mid-session without anyone touching a setting. A crew member idling at base still counts: presence in the world is the input, wherever on the map that player is standing.

The scaling has diminishing returns built in. Moving from one player to two raises boss health by a noticeable step, while moving from seven to eight adds a smaller step on top. Large crews stay viable: eight players face a much tougher boss than a solo player does, and the fight still ends faster, because eight sets of damage land at once. The practical reading for crew planning is simple: a boss attempt is a crew appointment, and a short-handed attempt is still real progress, since the kill counts in the world whoever was present for it.

There is no single multiplier and no universal percentage to memorise. Each boss scales by its own amounts, so a rule of thumb learned on an early slime will mislead you on a late Titan. Treat every boss as its own case, gear for its tier, and expect the fight to lengthen with crew size rather than transform.

One neighbouring system is worth separating from boss scaling, because groups routinely confuse the two. Regular enemies do not scale at all: a slime in an eight-player world has the same health and damage as in a solo world. What changes is quantity. Enemies spawn around each player, so more players spread across the map means more spawns in total, and a split crew each meets its own local crowds.

Two separate choices shape a co-op run, set in two separate places. World difficulty (Normal or Hard) is chosen when the world is created and belongs to the host's world file. Character type (Normal or Hardcore) is chosen when each character is created and belongs to that player alone. One world can therefore host a mixed crew, Hardcore and Normal characters digging side by side. Neither choice can be changed in game afterwards.

Two clarifications save arguments later. First, the Hard world's only compensation is the larger boss chest: the extra loot slots are real, and no Hard-exclusive items hide behind the difficulty. Second, Hardcore offers nothing in return: it is a pure challenge rule, and its cost lands unevenly in a crew, since one Hardcore death removes that player's character, skills and gear while everyone else plays on. Mixed crews should say the quiet part out loud before the first boss: the Hardcore player is volunteering for stakes the rest of the crew does not share.

Nothing in Core Keeper assigns roles, and every character can train all 12 skills. Crews still fall into a natural division within a few sessions, because skills level by doing: the player who farms levels Gardening and Cooking fastest, the player who digs pulls ahead in Mining, and specialisation compounds on its own. Four loose jobs cover most of a shared world's needs, and most players rotate through two of them.

One player tends the crop plots, keeps the cooking pots running and stocks the food chest before expeditions. The crew eats better buffs, hunger stops interrupting boss attempts, and the group's Gardening and Cooking levels concentrate where they do the most good.

One player pushes the digging frontier, opens tunnels and ore routes, and owns the base layout: workbenches, furnaces, storage and rail lines. A single builder keeps the shared base coherent, and everyone benefits from shorter trips home.

Two or more players gear first for combat and take point on boss attempts and dangerous biomes. Since boss health rewards attendance, the fighters' real job is scheduling: getting the full crew online and into the arena together.

One player tracks the unglamorous supplies: torches, food, spare gear, scanner parts and boat or rail materials. Crews rarely appoint this role, and feel its absence on every expedition that stalls for a missing stack of bridges.

Rotation matters more than assignment. The farmer who never fights will stall in combat skills, and the fighters who never dig will stall in Mining, so healthy crews swap jobs between expeditions and let the levels even out.

Shared bases run on agreements, so make them early and keep them simple. One chest row per category, a food chest refilled before it is emptied, and Titan expeditions that wait for a full crew will prevent most co-op friction. The game enforces none of these house rules, which is exactly why stating them once beats arguing about them at the third boss.

Crossplay is the word that causes the most confusion in Core Keeper co-op, because the in-game option of that name covers less than most players assume. The official position draws one hard line and one open door.

The open door is on PC. The game's Crossplay setting exists so that PC players who bought the game on different storefronts can play together, and it runs through PlayFab. Both sides need the setting enabled, and once it is on, a Steam copy and a copy from another PC storefront share a world like any other crew.

The hard line separates PC from consoles. PC and console players cannot share a server. A friend on Switch, PlayStation or Xbox cannot join your PC world, and your PC character cannot visit theirs. Console play stays inside each family: PlayStation 5 and PlayStation 4 players connect to each other, as do Xbox Series X|S and Xbox One players, per the publisher's account of the feature as reported in the press. Plan purchases around this: the platform split is decided at the till, and no setting changes it later.

Mixed-platform groups still have a workable pattern: run one campaign per platform family, and let a shared voice call carry the social side of the evening.

A final session note for PC crews: update 1.3 was followed by a line of stability patches (the 1.3.0.x series, running to 1.3.0.6 in October 2026), so keeping every copy on the same current version is the first fix to try when a session misbehaves. Keep expectations accurate here: those patches are general stability work, and the practical co-op rules in this guide, host-based worlds and per-platform servers, are the ones to plan around.

Up to 8 players in one world. That is the official figure for Core Keeper co-op, and a full eight-player crew is a complete, ordinary way to run a world, as the crew photo at the top of this guide shows.

Plan around the host needing to be there. Native multiplayer is host-based with no dedicated server in the standard setup, so the crew world lives in the host's save and sessions happen while the host is running it. Groups on different schedules should agree on hosting hours, or rotate the campaign world to whoever hosts that week.

Yes. Characters and worlds are saved separately, and a character can enter multiple worlds, local or remote, carrying its own levels, gear and inventory. Progress you make as a guest stays on your character, and your own world at home is untouched by the visit.

Boss health is recalculated from the players present, so a join or a departure during an expedition changes the health of bosses you engage from that point on. Regular enemies are unaffected in strength; you will simply meet more spawns in total as more players spread across the map.