You are viewing a potentially older version of this package. View all versions.
Ghostin-GK2_Coop-1.2.2 icon

GK2 Coop

Online co-op for Graveyard Keeper 2: host your world and Steam friends join with their own characters (or join by IP). Shared world, crafting, fights, story scenes and sleep. Version 1.0: back up your saves.

Date uploaded 3 days ago
Version 1.2.2
Download link Ghostin-GK2_Coop-1.2.2.zip
Downloads 13
Dependency string Ghostin-GK2_Coop-1.2.2

This mod requires the following mods to function

BepInEx-BepInExPack-5.4.2305 icon
BepInEx-BepInExPack

BepInEx pack for Mono Unity games. Preconfigured and ready to use.

Preferred version: 5.4.2305

README

GK2 Co-op

Online co-op for Graveyard Keeper 2. One player hosts their world, and friends join it with characters of their own.

Version 1.0. Out of beta: players have finished the whole game together with it. Back up your saves before playing all the same; they live in %USERPROFILE%\AppData\LocalLow\Lazy Bear Games\Graveyard Keeper 2. Bugs found from here on still get fixed.

Discord: join the GK2 Co-op server to find people to play with, ask questions, report bugs and hear about updates first.

Languages: the mod's menus, settings, tips and messages follow the game's language: English, German, Spanish, French, Brazilian Portuguese, Polish, Russian, Turkish, Japanese, Korean or Simplified Chinese (machine translations: tell us on the Discord if a line reads wrong).

Requirements

  • Everyone needs the same game version (built for Graveyard Keeper 2 1.012.7) and the same mod version (the host checks both).
  • BepInEx (BepInExPack 5.4.2305). The mod manager installs it for you.

Install

Install with r2modman or the Thunderstore Mod Manager and start the game modded. Every player installs it. The main menu then has a Co-op button (F8 opens the same menu, F9 its settings): if it's there, the mod is loaded.

Playing together (Steam)

Steam friends can play together with no addresses or port forwarding: the connection goes through Steam. Start the game modded (from the mod manager) with Steam running.

  1. Everyone: click Co-op at the main menu. Your name starts as your Steam name: it's what the others see. Your character (inventory, money, look) is kept in the host's save under your Steam account. Connect through is set to Steam friends.
  2. Host: under Host, click Host from here.
  3. Partners: the host shows up under Friends hosting. Click Join <host>'s world. You wait in the host's lobby; your menu buttons stay locked meanwhile. You can also accept the host's Steam invite (host: Invite Steam friends in the Co-op menu) or use Join Game on the host's Steam profile, while your game is open at the main menu.
  4. Host: start a new game or load a save. Everyone loads in together.

Or the host loads into their world first, opens Co-op from the pause menu, clicks Host this world on Steam, and partners join from their menu.

Public games, passwords and bans

Hosting options (in the Co-op menu, also while you host) decide who can join:

  • Who can join: Friends (your Steam friends see your game under Friends hosting), Public (anyone with the mod finds it under Browse public games) or Invite only (only people you invite through Steam).
  • Players: 2 to 8, you included.
  • Ask me first: you get a yes or no question before someone comes in: for people who aren't your Steam friends (the default), for everyone, or for nobody.
  • Game name, for the game browser, and an optional password. The password never leaves your PC: only a check made from it is sent.
  • Other mods: which other mods joining players may run: Any, Same as mine, Approved (approve them on the Mods page) or None. Mods that change the world run in one player's game only, so the worlds drift apart. Client-side mods (what they change stays in their own player's game: HUDs, journals, trackers, frame rate) always pass, and a few mods are host-only (villagers' days, station and zombie automation): the host's copy runs them for everyone, and a player can't join with them on. The Mods page lists both.
  • Non-friends may: what players who aren't your Steam friends may do: Do anything, Build, not take (no taking down buildings or taking from chests) or Only look. Trust in the Players list lifts it for a player until they leave.
  • Sanity limits (on by default): other players' games only change things near their own character, earn, spend or learn no more a minute than play can, hit no harder than the game's best weapon, and can't flood your game or the chat. What's refused is undone, and you hear about it in the chat.
  • Back up my save: a copy of your save before other players come in, in GK2Coop backups in the game's save folder: Before non-friends (the default), Before anyone or Never. The newest 10 are kept.
  • Players may teleport: whether players may go to each other and to you: Everyone, Friends only or Nobody.

Browse public games lists public games from everywhere, with the day, players and whether there's a password. Pick one and click Join (and type its password if it has one).

To keep someone out, use Ban next to their name in the Co-op menu (unban in Settings). Bans go by Steam account, and your games no longer show up for that player. Activity in chat (Settings) shows what the others build, take down and take from chests in your world, for everyone, only you, or no one. Public games let people you don't know into your save: the mod backs it up before they come in (Back up my save), but keep your own copy too.

Over Steam, each player's character is kept in the host's save under their Steam account, so it stays theirs even if they change their name.

Playing together (IP address)

For a LAN, a virtual LAN (Tailscale, ZeroTier, Radmin VPN), or a forwarded port. Set Connect through to IP address in the Co-op menu.

  1. Everyone: click Co-op at the main menu and type your name. Over an IP address your character is kept in the host's save under that name, so use the same one every time.
  2. Host: under Host, click Host from here.
  3. Partners: type the host's address under Join and click Join.
  4. Host: start a new game or load a save.

The mod uses UDP port 8889 (you can change it in the menu). Over the internet, join the host's address on the virtual LAN, or the host forwards UDP 8889 on their router and partners join the host's public IP. Allow the game through Windows Firewall when it asks.

What co-op does

  • One world, the host's. Objects, buildings, crafting stations, chests and stockpiles, graves and bodies, villagers and zombies, time and weather are all the host's, and everyone sees the same thing.
  • Shared progress. Money, tech points, reputation, the tech tree, talents and inspirations, and the village's sermon buffs.
  • Your own character. Inventory, carried items, energy, look and achievements are yours, kept in the host's save. Only the host's game saves.
  • The story is the host's. Partners watch the host's cutscenes and scenes: from where they stand when they're close, otherwise in the host's place, and they're brought back afterwards. Story steps (talks, story objects) are the host's to do, and quest item rewards go to the host. In the intro, everyone gets their own tools.
  • Work stations: one player at a time. What you make by hand goes into your bag.
  • Building: partners build, take down and use the game's Move as the host does. A partner's Move shows on their screen at once, and the host's game follows when they place it.
  • Fights: partners fight in the host's fight, with their HP and stamina bars and the host's wave timeline. They can carry and plant troop flags.
  • Sleep: the host's bed puts everyone to sleep, and the sleep screen shows everyone's energy. A tired partner's bed asks the host. Everyone wakes once all are rested.
  • Resting: sitting on a bench speeds time up only while everyone rests. Resting alone, the clock keeps its pace and your energy comes back at that pace.
  • The panic reduction machine: partners load and upgrade it too; it happens in the host's world, for everyone.
  • The map shows everyone, and areas anyone finds are found for all.
  • Shops: a partner talking to a shopkeeper gets their own shop. Vendors' stock and money are shared.
  • Chat: press Enter to talk. The chat box sits in the bottom left, in the game's own style; what's said shows over the speaker's head in the game's speech bubbles, with a thought bubble while someone types. Joins and the mod's other notices show there too, and, as you like, the answers picked in conversations or every line of the story.
  • The Co-op menu looks like the game's own menus. It lists everyone with their ping, lets the host remove or ban a player, bring players to them, and lets players go to each other (Teleport, if the host allows it), and has a Settings page.
  • Giving things: right-click an item in your inventory and pick Give to a player near you (8 units). It goes straight into their bag; a stack asks how many with the game's count window. Quest and story items stay yours.
  • Unstuck (the pause menu, under Co-op): stuck, or fell through the map? After a yes it takes you home to the bed in your house. Falling through the map is also caught by itself: partners go back where they stood or beside the host, the host goes home.

Bugs and feedback

Report bugs in the Bugs tab of the mod's Nexus Mods page: https://www.nexusmods.com/graveyardkeeper2/mods/408?tab=bugs, or on the Discord server. Say when it happened and who was hosting, and attach both players' logs (below).

Settings and logs

  • Settings: the Settings page of the Co-op menu (connection, rejoining where you left, story scene options, what new partners start with). Hover a setting's ? to see what it does. Everything else is in BepInEx/config/com.gk2coop.prototype.cfg (the file keeps its early name).
  • Logs: the mod writes a detailed log to BepInEx/GK2Coop-logs. When reporting a bug, send the newest coop_*.log and BepInEx/LogOutput.log from both players, with the time it happened.

CHANGELOG

Changelog

1.2.3

  • Hired mercenaries no longer lose their arms and legs on a partner's screen in a fight, nor flicker. In a partner's game they went on training as at the barracks, lunging at a dummy that wasn't there: that animation draws no legs and holds the arms mid-swing, and it fought with the fighting poses the host sends. The fighters of the host's fight now count as fighters in a partner's game too.
  • Partners walk through their own side's fighters (squad zombies and mercenaries) during a fight, as the host does. The host's game moves them aside only for the host's character, so in a partner's game they stood in the way like walls.
  • After a fight, a partner's game no longer keeps putting the fight's weapons and armor on its fighters.
  • 1.2.0 to 1.2.3 still play together (protocol 48), but update everyone: the fixes are in the partners' games, with a small part in the host's.

1.2.2

  • A partner no longer sees rain falling indoors, in the morgue for instance. A partner taken back to their own spot after one of the host's cutscenes was lit like the host, so with the host outside they stood in the outdoor light, and the game shows the weather in it. Their own spot keeps its own light now, and their character keeps that light, with the spot, for the next time they join.
  • Other players' sounds are heard only near your own character, within 25 units. The host heard partners pick up and put down zombies and bodies anywhere on the map, and everyone heard other players' sermons from anywhere.
  • 1.2.0, 1.2.1 and 1.2.2 still play together (protocol 48), but update everyone: both fixes are partly in the host's game and partly in the partners'.

1.2.1

  • A partner who joins while the host plays on gets the host's chests and stations as they are when they arrive. What the host emptied during their load stayed full in their game: resurrection tables kept zombies the host had already taken off them. The partner heard the resurrection sound on a loop each time they walked into the room, and the zombies they took off those tables were white blocks that no station would take, since the host's game no longer had them. The same goes for an area a partner comes back to after the host emptied something there.
  • A zombie a partner puts down that the host's game doesn't have goes from their ground too, instead of lying there as a white block.
  • A body you pick up no longer stays on the ground as well, handing you the same body again at every pickup. That happened when one body was in two places at once, as in two graves of an older save: digging both up left a copy behind. A save like that is mended as the host loads it, each body on the ground is a body of its own, and a copy left behind goes away instead of being picked up.
  • A body can no longer get stuck over your head. One carried twice by mistake went into a pallet or a grave once, and the other copy stayed in your hands, empty, and couldn't be put down. The same body is never carried twice now, and an empty one goes away when you put it down.
  • 1.2.0 and 1.2.1 still play together (protocol 48), but update everyone: the host's game holds most of these fixes, and everyone's game the ones for what you carry.

1.2.0

  • For Graveyard Keeper 2 1.012.7. 1.1.0 doesn't work with it: everyone needs 1.2.0 (protocol 48) and the same game version.
  • Other players' characters wear their own clothes and colours again. With 1.1.0 on game 1.012.7 they showed in bright, mismatched colours, and parts of their bodies went invisible depending on the way they faced.
  • A partner can again press a station a zombie works to hand over what it's waiting for or take what it made. On 1.012.7 that failed in the host's game.
  • The panic reduction machine works for partners. Since 1.012 it isn't a craft: its window loads Hypno-devices and newspapers (on Gluttony) and upgrades the machine with graveyard quality. A partner's load and upgrade now happen in the host's world, for everyone, and what can't be used there comes back to them. Partners also get the machine's "almost stopped" and "stopped" notices.
  • Resting on a bench (new in 1.012) speeds time up only while everyone rests. Resting alone, the clock keeps its pace for everyone and your energy comes back at that pace; a notice says so. A shared sleep stands up anyone still sitting on a bench.
  • After a partner's sermon, its parishioners walk out of the church on the partner's screen too. They stayed inside and blocked the door, and only Unstuck got the partner out.
  • Items moved between chests, or between your bag and a chest, just as a cutscene starts are no longer lost. A partner's change could be dropped when the scene closed the window or took them to the host, and the host's copy of the chest then replaced it.
  • A grave's decoration no longer goes missing on a partner's side only, which left the grave stuck until the host replaced it. Opening a grave shows a partner what's on it in the host's world, and new containers the story or a craft makes reach partners already standing beside them.
  • A scene a partner sets off where the host isn't, such as destroying the blockage to the resurrection room, no longer walks the host's character across the map and through the dark beyond it for minutes. The host is brought to the scene with the game's fade, in the light of the place where it happens.
  • The mercenaries' new "pay with items" answer shows its own text in the chat.

1.1.0

  • Give things to each other. Right-click an item in your inventory: the game's own menu has a "Give to" line for each other player. A stack asks how many with the game's count window. It goes straight into their bag (at their feet if it's full). You need to be near them (8 units); farther away the line is greyed out. Quest and story items can't be given. Everyone needs 1.1.0.

1.0.0

  • GK2 Co-op is out of beta: 1.0. Players have finished the whole game together with it. Bugs found from here on still get fixed.
  • A partner can skip the end credits. The Back button shows for them when it shows for the host.
  • In a fight, every fighter's HP bar is the fight's small one. In the final battle a squad's zombie could get the bar trees and rocks have instead, one cell per HP point, across half the screen.
  • Town orders and sermons count toward everyone's achievements, whoever did them. They used to count only for the player who did them, and the town has one board of orders and one church, so an order a partner turned in was one the host could never do. Fish stay each player's own.
  • Everyone needs 1.0.0 (protocol 46).

0.33.4

  • The repair for a zombie placed twice now finishes the job. The copies of it lying on the ground or held twice are cleared as the save loads, and villagers and zombies work again: after the repair in 0.33.2 they stayed stopped.
  • Picking up a stray copy of a zombie you're already carrying adds nothing, so a pile left in a running game goes away as you pick it up.

0.33.3

  • A store a partner builds in the town gets built. The build failed in the host's game: the materials were spent and the store was marked as built, with no store, no shopkeeper and no orders from it.
  • A store stuck that way is freed as the save loads, so it can be built again. The materials already spent don't come back.

0.33.2

  • A save that loads into an empty world is repaired as it loads. A partner carrying more than one zombie could place one twice, and the copies left in the save stopped the world's objects from appearing. That can no longer happen.
  • A partner carrying several zombies keeps them all. Taking another threw the first on the ground and lost track of the new one.
  • What a zombie makes at a station no longer goes into the host's bag, wherever the host is.
  • Each player hears the music of where they are, not where the other player is.
  • The fight's top bar shows for a partner during the preparation phase too.
  • The Bishop, the woodcarver and the workshop foreman talk to a partner again. A partner got a trading window of odd items instead, with no way to buy steel or wood. As with every talk, the host has to be there.
  • A partner can skip their own lines, like the one saying when sermons can be held. They had to stand and wait them out.
  • Merchants in town stand still for a partner, instead of walking on the spot behind their stalls.
  • Working zombies walk when they move for a partner. Farmers no longer cross the plot tilling, and porters no longer slide along sitting down.
  • A carousel's conveyor strength updates for a partner as soon as a zombie goes on it.
  • Quick presses on a queued craft's count no longer jump back by one for a partner.

0.33.1

  • A partner's fertilizer now shows on the garden bed. It reached the host's game, but its box stayed empty for both players: the bed's slot was wiped a moment later. It now goes in the box the partner picked, and an open bed window shows it without reopening.
  • What a partner changes on an object now reaches the host as just that change. Before, their whole copy of the object's values went, and a copy a moment out of date could undo what the host had just done.

0.33.0

  • Partners can move buildings with the game's Move, as the host can. It's in their build window, works wherever the host is, and takes along what's fixed to a building: extensions, a workbench's output belt, its zombies. While a partner carries something, nobody else can take it down or move it, and it goes on working where it stands until it's placed. If the host is carrying something at that moment, the partner's Move waits for them to put it down.
  • A partner's filters on factory chests work. What each slot of a conveyor chest, wine chest or vegetable storage gives out changed only on the partner's own screen, and the host's game, which runs the belts, kept its old choice. A filter now goes through the host both ways.
  • Belts join what a partner finishes building while the host is elsewhere. A conveyor chest, furnace, kitchen or workbench built from a site turns into the finished piece in the host's game, which could only link it to what was loaded there. With the host away from the factory, it came out unlinked in both games, and nothing moved until it was built again with the host nearby. The partner's game now links it. Pieces already standing unlinked stay that way until they're taken down and built again.
  • A partner can take a zombie off a station with a hand craft running. It failed with an error about energy and left the zombie half attached, so pressing again couldn't take it either.
  • A partner's late press at a station no longer opens a craft window on the host's screen.
  • Taking down a belt beside a workbench with the host just off screen no longer leaves the bench naming a belt that's gone.

0.32.2

  • Full chests no longer stop a supplier. When no chest in the area had room for a finished craft, the supplier took it anyway and stood holding it, and everything else it served stopped, the next craft in the queue included. This was a game bug, with or without a partner. The supplier now leaves the finished craft at the station, goes on with other work, and collects it by itself once a chest has room.
  • That station's queue still waits until a chest has room, and a supplier already holding something it can't store waits too. Neither needs a restart: make room and it goes on.
  • It works alongside Unofficial Patch, which has its own fix for part of this.

0.32.1

  • With Autopsy Assistant, a partner's batches run all the way through. Its Optimize and Loot buttons stopped after the first organ for a partner, because the mod checked the queue before the host had answered. It also goes on to the next stage now, which it waited for from a game that doesn't finish crafts on a partner's side.
  • With the co-op Day length above normal, the panic reduction machine lasts the week. It can only be started on Gluttony, but it ran on real time, so at twice the length it ended on Envy and couldn't be started again until the next Gluttony. That brought the debuff for too many zombies back in time for every sermon.
  • GK2 Longer Days 1.6 is checked and known, so it no longer shows the notice about a different version.

0.32.0

From a review of the whole mod against Graveyard Keeper 2 1.011.

Stations run by a zombie (furnaces, kilns, ovens, barrels, the distillation cube, compost piles)

  • A partner can add crafts to the queue there without holding the materials, as the host can: the caretaker or gardener brings them from the chests. The materials used to be taken from the partner when they queued, and the craft then sat waiting, or the zombie brought a second set.
  • A partner pressing "work" there with the materials in their own bag now starts the craft, and pays for it from that bag. Before, nothing happened, or the host's bag paid if the host stood nearby.
  • A partner's craft of two or more there starts each next one on what they paid for, with no delivery and no press to start it. Each finished one is still collected as usual, by a zombie or a press.
  • These stations use what the zombie brought first, as in the game. In co-op they took a second set from the chests and left what was brought in the station, so a zombie then carried that away before the finished item.
  • A station upgraded or moved during play, like a kitchen oven going to its second tier or a building moved with GK2 Move Buildings, keeps getting its deliveries. A bug in the game stopped the station's orders to its zombie until the game was restarted, so it went on saying it lacked materials however many you supplied. This also helps a host playing alone with the mod installed.
  • A partner opening the window at one of these stations starts a craft that's ready, as the host's own window does. The host's station went on waiting for its zombie.
  • A partner sees the same status icon at these stations as the host: waiting for a delivery, ready to start, ready to collect. It could be missing, or stay stuck on an old one.

Crafting for partners

  • A partner can queue more of a craft than they can pay for, as in the game, with Add to queue or Craft. What they can pay is paid, and the rest starts when the chests have it or when they work it with the materials in their bag. It used to cut the count down, or say there weren't enough materials. A guest who may not take from chests stays limited to what they can pay.
  • A queued craft no longer shows as missing items in a partner's window when it has what it needs. The window worked that out from the partner's own copies, and it stayed wrong until a rejoin.
  • A partner working a craft the host's game can't pay, with the materials in their own bag, pays from that bag. Moving them to a chest used to be the only way.
  • The plus, minus and endless buttons on a partner's queued craft reach the host's queue. They only changed the number on the partner's screen. Lowering the count gives back what was paid for the rest.
  • A partner's craft can't take materials from the host's bag.
  • The "+ item" notice for materials that come back to a partner shows once, with its icon. It came twice, the second time with a name and no icon.

Zombies

  • Porters and belt carriers walk and work on partners' screens. They stayed in their sitting pose and slid about.
  • A zombie put on a bench during the session shows its orders in partners' games, so they can hand it materials straight away. Before, that took a rejoin.
  • A partner's second action at a working zombie's station clears a pickup with nothing left to pick up, as the host's does. The zombie stayed waiting on it, and its next craft didn't start until the host pressed.
  • A partner standing near a garden bed the host's gardener is working no longer frees that bed in their own game. They could end up harvesting alongside the gardener.
  • A tool a partner gives a quarry worker takes effect at once in the host's game. The quarry's status could stay out of date before.
  • Partners see the "no storage" icon over quarry workers and gardeners whose storage is full, and it goes away when they carry on.
  • A porter or belt carrier with nowhere to put its load no longer sends partners a stream of messages, each one a line in their log, for as long as it stands there. It still goes back to work on their screens once there's room.
  • Taking a fighter off its container frees the spot in partners' games right away, so they get the hint for putting a zombie there.
  • Pressing twice to take a zombie off a bench, conveyor workbenches included, just gives you the zombie. A second press before the host's answer used to say the host had to be in the same area, though the zombie had already come off.
  • A press right after picking up a zombie can't take it out of your hands. The host's game could answer before it had heard about the pickup, and the zombie was gone.
  • A zombie that's gone from the host's world can't stay stuck in a partner's. Trying to take it now says it isn't there in the host's game, and it disappears. Before, every try said the host had to be in the same area, until a rejoin.
  • A partner can take a zombie the host's game hadn't finished drawing. That press used to say the object works differently in the host's game, and only the next one worked.
  • The zombie window follows along on a partner's screen. When a perk is bought or the zombie earns points, the perk tree, the red, green and purple points and the perk count update by themselves. The tree used to wait for a change of tab, and the points for reopening the window. The host's open window now shows a partner's purchase in its perk tree too.
  • A partner can level up a zombie lying on the floor wherever it was carried to. If it had last stood or been raised far from there, the purchase was refused and nothing told the partner.
  • Partners now get the points, perks and body of zombies that aren't standing in the world: lying down, carried or on a table. Their copy could stay out of date, so a perk looked out of reach and pressing it did nothing, even after reopening the window.
  • A zombie perk the host's game refuses no longer looks bought. You get a thought bubble saying why, or your window puts itself right if the zombie already has the perk. It used to play the coin sound, and then nothing happened. A zombie's points can't go below zero that way any more either.

Zombie Chores

  • A partner putting a zombie down to fish works, in Zombie Chores 1.2.10. It only happened in the partner's game, which took the zombie out of the host's world for good, and the next press said the host had to be in the same area. A zombie lost that way on an older version only comes back from the save backup made as the partner joined.
  • Zombie Chores' fishers show on partners' screens with their rod, line and bob.
  • A partner taking a fisher gets its fish and bait. They were lost.

Day length and characters

  • The Day length setting works. The host's clock ignored it while partners were told the longer day, so a partner's clock ran at half speed and jumped forward every few seconds, and the host's day stayed as short as ever.
  • A character who joined in the middle of a fight no longer loses their hair and beard on the other player's screen when their armor comes off. The check for this looks at hair as well now, and its repair works: it never had.

Crematorium

  • A partner cremating a worker zombie counts as a zombie in the host's game. It took a body off the morgue's count instead, and the zombie's place was never given back: the count stayed one too high for good, and with it the x/y at the resurrection table and the debuff for too many zombies.

Belts

  • Belts the host lays are linked in partners' games straight away, so a partner's build mode shows the right free connections on them. Before, those links only arrived on a rejoin.
  • A belt a partner lays into a workbench now works. It looked connected in the partner's game, but the host's game didn't know of it, so items stopped at the end of the belt and the workbench never took them.
  • A new belt shows moving for the other player straight away. A belt laid by a partner, or by the host, could stand still in the other game, with no items travelling along it, until its area had been left and loaded again.

Moving buildings

  • What the host moves with Move in build mode now moves in every partner's game, wherever they are, along with the extensions, output belt and zombies that go with it. Before, a partner saw it slide after the host's cursor, could lose sight of it at the new spot, or kept the old spot until they rejoined if they hadn't been in that area yet.
  • Partners can't use Move for now, so it's gone from their build menu. A partner's move only happened in their own game and was gone after a rejoin, while the building in the host's game lost its links to its extensions, or could end up unusable.
  • A player the host doesn't let build can no longer change the host's buildings from build mode. Their change is refused and undone in their game, and the host is told.
  • A player the host doesn't let take down buildings can't mark one for tear-down either, and one the host doesn't let build can't call a tear-down off. The building stays as it was, and the host is told. A mark used to go straight through, with no word to anyone.
  • A player the host doesn't let take down buildings can no longer wipe the craft running at a station by trying to take the station down. The take-down was refused and the station stayed, but the craft was gone, and what it was made from went to that player. The craft now carries on.
  • The lines saying a build was refused are whole sentences now, so they can be translated. In other languages they had the English word "build" in the middle.
  • A partner's changes to something already built, like adding an extension to a workbench, work as far from their character as placing a building does. Past 30 units they were refused, so an extension across the yard stayed in the partner's game alone, and crafts that needed it were thrown out of the host's queue. Anything further off is put back in their game.
  • With "Build, not take" or "Only look", a guest no longer pays for a craft queued or started at a station out of the area's chests: what they pay comes from their own bag and the station, and with nothing there they get "Not enough materials for that." Their game used to take from the chests. The host put the chests back but ran the craft anyway, and taking the craft back out of the queue gave the guest the items. A station run by a zombie still gets its own materials from the chests. Other things a guest pays for, such as building, town repairs, the resurrection table and the alchemy, embalming and autopsy windows, still take items from the chests in the guest's own game: the host puts those back, and the work goes ahead unless the host's rule forbids it ("Only look" still refuses a build).
  • A partner can't take down something the host is carrying.
  • If someone joins while the host is carrying something, it goes back where it was first. The joiner used to get it half moved.
  • After the host moves a belt, a partner placing a belt beside one of its old neighbours no longer brings the old link back, which could stall that line.
  • A belt a partner lays against one the host is carrying now waits for the host to put it down, however long that takes, and then joins the belts beside it. After 4 seconds it used to be left out of the conveyors until someone took it down and placed it again, and the belt feeding it could stop too.
  • A belt a partner lays into the side of the one before a belt the host is carrying shows joined in the partner's game once the host puts it down. It looked unconnected there until a rejoin.
  • A belt a partner lays and takes back down while the host is carrying something beside it no longer leaves the belts next to it linked to a piece that isn't there, which could stop all the host's belts.
  • Being sent to the main menu while in build mode, by a lost connection for example, no longer carries build mode or an unfinished move into the next game you load.

Carrying

  • What a partner puts down always reaches the host's world. In a tight spot (against a wall, a bed or a bench) the game places it differently, and it stayed in the partner's game alone, so a body put down there was lost. Since 1.011 every bed makes you put down what you carry, so this came up more often.

Sleep

  • A partner's bed asks the host to sleep again. Every bed counted as the story putting you to bed, so the host heard nothing and the partner got no answer, and since 1.011 they had also dropped what they carried (that part is the game's: a host's bed does it too). Tired, they get the "Sleep request sent" notice. Rested, they get the game's "no need to sleep" line.

Joining

  • Closing the game's Mods or Settings window after the host's world has arrived takes you back to that world. A window left open while it arrived opened the main menu over the game, with New Game and Continue working, and the only way out was to leave the session.
  • What gets built, removed or changed in the world while you're on the loading screen reaches you once you're in, and so does what's put down on the ground or picked up off it. It used to be missing all session: a zombie the host took off a bench then still stood there in your game, one put down then never showed, and a body picked up then still lay there for you to take as a second copy.
  • Perks, inspirations, tech, recipes and map icons the host gets while you're on the loading screen are there once you're in. They could stay missing until a rejoin, so a perk bought then showed as not bought on your page. A zombie made then is a zombie in your game too, not a blank white block until it was put to work.
  • Doors, paths and bridges the story opens or closes while you're loading, or in an area you haven't been to yet, are right when you get there. They could stay as they were until a rejoin.
  • A quest that changes just as another partner finishes loading now reaches the partners already in the world. It could be missed, so their journal kept a finished quest open until they rejoined.

Town orders

  • The delivered and required rows over the warehouse crates (new in 1.011) update when the other player changes them. A partner watching deliveries, or a host whose partner changed the board, saw old numbers until the crates next came into view.

Map

  • The day activity icons on the map (new in 1.011) appear for partners when the host's quests unlock them. They stayed hidden until a rejoin.

Other mods

  • The host's Other mods rule and the Mods page now see native mods run from the game's own Mods\Code folder, as they do Workshop ones. A partner's mod from that folder got past the rule.

Morgue

  • The morgue's count after a load includes bodies a partner was carrying when the game saved. It came out one short, and one shorter when that body was buried, until the next load.

Perks

  • Clicking a perk twice before the host's game answers buys it once. With enough points, the second click paid for it again.

Tech tree

  • The red, green and purple totals on the tech page, and the prices on its cards, follow the shared points while the page is open, for both players. A partner's totals stayed one purchase behind until their next unlock or until they left the page, and the host's didn't show what partners earned.
  • A tech's price reaches partners together with the tech. Until it arrived, they could press Unlock on a second tech they could no longer afford, and the host then refused it.

Thought bubbles

  • Your character's thought bubble shows over an open window. The reason a zombie perk or a tech was refused was drawn behind the zombie window or the tech page, so all you saw was that nothing had happened.

Story

  • A partner picking the host's answer with stand-ins or scene watching turned off in the config keeps their controls afterwards. They were held until the next window closed, and left free while picking.

The other player's character

  • Trees in front of your character fade as they should with someone else in the game. The other player's character ran the same check and could keep them solid.
  • The other player's character doesn't blink under a helmet, as your own doesn't.

Fights

  • Arenas change in a partner's game when they change in the host's. Rubble, fences, green fog and the walls of an earlier battle stayed for partners, solid enough to stop them while the host walked through, until they rejoined or teleported to the host. What the end of a fight or a later quest clears or closes now reaches partners wherever they are.
  • Arenas the story adds or takes away reach partners during the session. A new arena's camps, guards, waystones and repair signs were missing for them until a rejoin, and one the host's game had removed stayed in their way.
  • A partner who walks into a fight already under way, or leaves and comes back, finds the flags and the fog as the host has them, even fog a flag cleared before the zombies took it back. They used to find the arena as it was at the start, and fog could wall them off from sectors the host had already cleared.
  • A partner comes out of the arena with the host after a won fight whose way back is outside it, not only after a lost one. Those wins left them on the battlefield: in the sewers that meant no way out but Go to or Unstuck, and on the surface they were left standing where they fought. Where the way back is inside the arena, they walk out from where they stand.
  • A scene right after a won fight no longer puts a partner back on the battlefield when it ends. They watch it from the way out and stay there.
  • A partner in another area or in a long scene when a fight starts goes to it as soon as they can, at any point in the fight. They used to be left behind its walls, with no way in but teleporting to the host. Teleporting to someone in that area still works, and leaves them beside that person.
  • A partner who leaves a fight and rejoins it goes back to its start point. Without restarting the game they stayed where they joined.
  • A partner standing with the host at a battle camp right next to its fight goes to the start point too. At a few camps they stayed behind, outside the fight's walls. Anyone not at the start point now goes there, with a short fade, even from inside the arena.
  • A door or waystone the host uses in the minutes after a fight no longer pulls along a partner still in the arena.
  • A partner who leaves or drops out inside a fight's arena and rejoins after the fight lands beside the host. They landed alone in the emptied arena, which in the sewers meant no way out but Go to or Unstuck. A partner who left from elsewhere keeps their saved spot.
  • You can't start hosting in the middle of a fight: the Co-op menu says "Not during a fight." A partner who joined then got none of the fight but its enemies, with no weapon, armor, flags or fight music.
  • Losing the palace battle, or backing out of it, takes a partner back with the host. They stayed behind alone in that area.
  • A partner leaving in the middle of a fight no longer breaks it for the host. Their character stayed on the fight's list after it was gone, so enemies stopped working properly until the fight ended, and rejoining didn't clear it.
  • A partner who leaves or drops out with zombies coming at them, or a host ending the session like that, no longer freezes the fight. Many enemies stopped getting orders, killed ones could stay on their feet at no health, new waves stood idle, and the host's stamina and the flags stopped updating, until the fight's time ran out. The zombies now turn to the next target.
  • The hit flash lands on the character that was hit. With a partner in the game, a zombie hitting the host flashed the partner's character wherever it stood, and a zombie hitting the partner flashed nothing on the host's screen. After a partner left, the host's own character showed no hits until the game was reloaded.
  • A partner sees and hears zombies hitting the host, and sees their hits on barricades and allies. Zombies swung at them with no sound or flash, so it looked as if they weren't hurting anything.
  • A partner's armor counts. Zombie hits and spit took the same off them whatever they wore, so better armor changed nothing but the look, and they went down well before the host.
  • A partner's flag count at the top of the screen and the flags on the wave lines follow the fight. They stayed as they were first drawn while the fog and flags in the world changed.
  • A partner in the fight now gets the win or defeat window with the host. They only heard the jingle. Rewards still go to the host, and the window closes by itself when the host moves on.
  • A knocked out partner falls down and stays down until the fight ends, in their armor, with the fight still on their screen. They used to stay standing in everyday clothes with an empty health bar, free to walk around, as if the fight had ended for them only.
  • A knocked out partner gets back up for the next of a chained fight. They stayed out of it, and their hits did nothing.
  • A dying stinker's blast on a partner low on health knocks them out, as any other hit does. It ran the solo game's death in the middle of the fight, with "You're dead", and they stood up afterwards on no health while the host still counted them in.
  • A squad's flag stays in the fight when the partner carrying it is knocked out or leaves. It goes on a flag stand where they were, and the host or any partner can take it from there. It used to lie where nobody could pick it up, and that squad couldn't be sent anywhere until the fight ended.
  • A partner can drink battle potions. Heal, damage, rage and motivation potions stayed greyed out on their hotbar and in their inventory all fight long, and the hotbar key did nothing.
  • Damage and rage potions work only for the player who drank them. The host's also changed a partner's hits until they wore off.
  • A beer's effect stays with whoever drank it, too.
  • A motivation potion drunk by a partner speeds up allied troops, as the host's does. Both players see its icon until it wears off.
  • A partner using a battle camp starts it in the host's game, with the host there, and the host gets the pre-fight window. It used to start a fight in the partner's game alone, which the host knew nothing about. During a fight, a camp just says "Not during a fight."
  • Unstuck says "Not during a fight." to a partner in the host's fight too. It sent them home with the fight still running, and nothing brought them back to it.
  • A fight's build table follows the fight for a partner too: no barricades or towers in a fight that forbids them, and no Remove once it's running.
  • Allied troops keep their armor on a partner's screen. A partner who reached the fight late, or who left the troops off screen and came back, saw plain zombies that looked like the enemy.
  • The squad panel on a partner's fight screen shows each squad's banner and every soldier's weapon and health, as the host's does. It was empty.
  • The capture banners at the edges of a partner's screen follow the flags. A flag taken during the fight gets one, and a flag lost loses it. They used to stay on the flags held when the partner joined the fight.
  • A partner sent to a fight's start lands beside the host, so you see both characters. They landed on the same spot and looked like one, with the other's name over it.

Languages

  • The box showing who a talk is waiting for and the message that someone is a guest again are translated now.

Town repairs

  • A street repaired in the lower city changes for partners straight away, wherever they are. The ruins stayed in their game, often in the way, and the repaired pieces didn't appear until a rejoin.

  • Needs Graveyard Keeper 2 1.011, and everyone needs 0.32.0 (protocol 42). Back up your saves.

0.31.8

For Graveyard Keeper 2 1.011.

Crafting on 1.011

  • Crafting works again for partners. 1.011 changed two of the game's methods GK2 Co-op calls, so 0.31.7 failed on every craft message: a partner's materials were taken, but the craft never joined the queue. (Reported by a player, thank you.)
  • A partner's craft starts at a station with a zombie assistant. Since 1.011 an automatic craft there waits for the assistant unless a player starts it, and a partner now counts as a player.

Morgue

  • The morgue's unburied body count is put right each time a save loads. The game keeps it as a running total rather than counting the bodies, and once it drifts (up or down) nothing in the game corrects it: when it says the morgue is full, the donkey stops delivering. The host's game now counts the bodies really there (on the ground, in open graves, on pallets and tables, and the one being carried) and sets the number to that. The log says what it changed. Save once to keep it. (World, RecountBodies in the config.)

  • A body near you that fell under the map is dropped again outside the morgue, where the donkey leaves bodies. Before, it fell with nothing to land on and stayed counted, for good if it was one the donkey left at the crossroads (those never rot). The host's game does it, or yours when you play alone. (World, RescueBodies.)

  • Both also come as a mod of their own, GK2 Body Count Fix, on the Steam Workshop. With both installed, GK2 Co-op leaves the job to it.

  • Needs Graveyard Keeper 2 1.011, and everyone needs 0.31.8 (protocol 41: it won't connect to 0.31.7 or older). Back up your saves.

0.31.7

Fixes from a player's reports (thank you), and the gaps left in the review of every game system.

Fixes

  • Other players' characters keep their arms (and beards). Facing up, the game switches those parts off; the side and front poses leave them as the character's animation remembers them, and another player's character on your screen could remember them as off, so it drew no arms until it carried something to the side. It now remembers them on. (Reported on the Discord, thank you.)
  • What a partner puts into the stone, clay and ore stockpiles shows in the host's game. A partner's game only sent containers right beside them, and a stockpile is used from its top, a few steps from the stockpile itself. Anything changed through an open chest window now goes to the host, however far. (Reported on the Discord, thank you.)

Sounds

  • You hear the other players place buildings, plant (with the puff of earth), finish a sermon, and place or take troop flags, at their character. Partners also hear zombie porters rummaging in chests.

Languages

  • GK2 Co-op now speaks the game's languages: German, Spanish, French, Brazilian Portuguese, Polish, Russian, Turkish, Japanese, Korean and Simplified Chinese, whichever the game is set to. That's the Co-op menu, its settings and tips, the pause menu's Unstuck button, the chat's notices, the bubbles and the questions it asks. The translations are new and machine-made: if a line reads wrong, tell us on the Discord.
  • In Japanese, Korean and Chinese, the in-game chat, the player names on the map and the names on the sleep screen now draw in the game's font for that language, so typed chat and names in those languages no longer show as boxes.

Chat

  • The chat box is at the main menu too. The mod's messages show there (why a host turned you away, who joined your lobby, version differences) instead of plain boxes at the top of the screen. Once you host, or wait in a host's lobby, you can talk to the lobby: click the box to type.
  • With a gamepad, press both sticks in to open the chat. Steam's keyboard comes up to type with in Big Picture and on a Steam Deck. B closes the chat. The buttons are set in the config file (Chat, GamepadButtons).

Story

  • A partner who picks the host's answer away from the scene gets the game's own answer list over their character, instead of the mod's panel at the bottom of the screen.

  • The bag slot the story gives near the end comes to partners too, and goes again when the story takes it back.

  • Works with 0.31.6 (protocol 40), but everyone needs 0.31.7 for all of the fixes. Back up your saves.

0.31.6

Fixes from a player's reports (thank you), and from a review of the game's code.

Crafting as a partner

  • A partner can queue crafts at stations that get their own materials: a zombie's station (its porters bring them) and the factory's workbenches (fed by belts). The materials were paid when the craft was queued, so a partner could only queue what they held right then, and factory workbenches took nothing. Now the host's game takes the materials as each craft starts, as for the host's own queue.
  • A zombie no longer waits forever for a porter after a partner queued a craft: paying up front took the zone's last logs, and the zombie waited for porters to bring materials that were already paid. A zombie's station also uses up what its porters brought before taking more from the chests.
  • Materials a partner paid for crafts that haven't started yet (a furnace's next bronze bars) are kept in the host's save. A reload or a new session lost them while the crafts stayed queued, and the station then said it had no materials.
  • Handing materials to a zombie at its station, or taking what it made, works for a partner: the host's zombie now gets them. Before, the materials went into the station but the zombie went on waiting for its delivery, so a porter brought them again.
  • Studying an item at the desk no longer uses the item up (only decomposing it for science does, as in the game).

Conveyors

  • Belts and other conveyor pieces a partner places work: they joined the conveyors only in the partner's game, so nothing they built moved anything.
  • A station with an output belt taken down while the host is far away takes its output belt with it. The belt stayed, and couldn't be taken down by itself; one left that way can now be taken down once no workbench is beside it.

Gathering, building and rewards

  • Digging sand, clay or copper, or drawing water from a well, gives a load every time. A spot that comes back after each load could only give one every 3 seconds when a partner worked it, so every other load was lost.
  • Gratitude from selling to a vendor, and tech points picked up in a quick burst, all count for a partner. The host's answer to the first points arrived before the rest had landed and set the counter back, so of 25 points only 2 might count.
  • A partner can mark and unmark buildings for take-down anywhere build mode reaches, not only within a few steps of their character (one of four church benches refused).
  • A tool given to a zombie lying on the ground stays with it when it's picked up or put to work.
  • What the host takes down in build mode is the host's to pick up for half a minute: a partner standing by got it instead.

Characters

  • While another player plants a tree, you can still move. Their planting pose took your controls, and kept them if their character left before it ended.
  • When another player falls in a fight, you no longer get "You're dead".
  • The sermon icon no longer stays over another player's head after their sermon.

New

  • Day length (host setting, under Hosting): days can last 1.5, 2 or 3 times as long while others are in your world. Alone, an open window pauses the game; in co-op it doesn't, so days go by faster. It stretches the day another mod sets too (GK2 Longer Days), and sleep is as fast as ever.

  • Everyone needs 0.31.6 (protocol 40: it won't connect to 0.31.5 or older). Back up your saves.

0.31.5

  • Two players working at the same time no longer speed each other up. The game hands each stroke of a character's work animation to "the player", which it takes to be your own character, so the other player's swings on your screen also counted on your job, and used your energy and wore your tool. (Reported on the Discord, thank you.)
  • Quest rewards (town gratitude, story items and the like) go to whoever talked the quest through. The host's talks brought the partner over to watch from the host's spot, where the game drops the rewards, so the partner's character picked them up; watching from there, a partner now picks nothing up. A talk a partner starts runs in the host's game and dropped its rewards at the host's feet; they now go straight into the partner's bag. (Reported on the Discord, thank you.)
  • The other players' characters on your screen no longer react to your own windows and scenes: each time your controls were taken or given back, they switched their interaction area back on and looked for things to use around them. Nor can their drop pick-up put anything into your bag.
  • What your work drops is yours for a few seconds: a harvest, something you take down, what you collect at a station, a craft's output that lands on the ground. Another player standing by no longer pulls it in or picks it up first. It's free for anyone once those seconds are up, or right away if your bag has no room for it. (Before, only the host held back, and only from a partner's harvest.)
  • A zombie a partner puts to work and anyone takes out again stays a zombie. It turned into a white block that no station would take: the first time a zombie goes to work the game gives it a new id, and the host's game gave that id to its own copy of the zombie while the station got the partner's, with the old one. Saves where that happened get their zombies back when the host loads them (the white block is the zombie again). (Reported on the Discord, thank you.)
  • A zombie fresh off the resurrection table no longer shows as a white block on a partner's screen until it's put to work: the partner's game now gets it straight away.
  • A partner's character showing without arms (seen again on 0.31.4): the log now says more about it. If it happens to you, please send both players' logs.
  • Plays with 0.31.4, 0.31.3, 0.31.2, 0.31.1, 0.31.0 and 0.30.0 (same protocol). The partner's talk rewards, whose work a drop is and the zombie fixes need the host on 0.31.5, and a partner on 0.31.5 to leave the host's drops alone and see new zombies; the rest is in each player's own game, so everyone should update.

0.31.4

  • A building two players work on together no longer vanishes when it's done. A build site turns into its building when the work is done, keeping its place in the world. The partner's game, which also saw the work finish, then asked the host's to finish the site again, and the host's game did that to the new building, which has nothing to turn into, so it was removed for everyone (the materials were already used). A partner's hit that arrives after the change no longer lands on the new building either. (Reported on the Discord, thank you.)
  • Plays with 0.31.3, 0.31.2, 0.31.1, 0.31.0 and 0.30.0 (same protocol). The fix is in the host's game; the tables of 0.31.3 need both games on 0.31.3 or later, so everyone should update.

0.31.3

Fixes

  • Only one player at a time can use the autopsy table, the embalming table, a grave, the resurrection table or the crow's nest, as with chests: two players extracting from the same body at once each got the organ, and taking the body at once gave two bodies. The other player is told who's using it. (Reported on the Discord, thank you.)
  • A story step a partner does before the host's quest for it opens now counts. Clearing the basement debris before the host had met the plague doctor left the host's "clear the path" waiting for debris that was gone: the game counts such a step (debris, a locked door, a hatch) only while its quest is open, and alone you can't get there first. During co-op the host's game now notes such a step when it's done, and counts it when its quest opens, once the scene there is over. A save already stuck on the plague doctor's path picks it up when the host walks to where the debris was, by the doctor's door.
  • A partner's sermon counts for the host's church quests (the first sermon, the organ's, the choir's, the old god's, the printing press's). It played in the partner's game and used up the week's sermon for everyone, while the host's quest waited for a sermon of its own, so the story stalled for a week.
  • Upgrades a partner builds count in the host's game: the garden's and the vineyard's upgrade levels (farming, fertilizer slots), the church's upgrade steps, and the old god's sermon. The partner's game set them only for itself, so the host's game and save never had them, while the upgrade itself was used up for everyone.
  • A partner's build window counts graveyard modules right: the number built, which each module's limit counts, stayed as it was when they joined, so they could build past the limit.
  • A partner's graveyard and church quality follow the host's: new graveyard plots and other extra quality only reached the host's game, so the partner's zone panel and what their sermons collect used a lower quality.
  • Church and graveyard quality inspiration counts once: a partner's game gave it too whenever the quality rose and passed it on, so the host got it once per player.
  • A partner taking from a chest far across their work zone, or building and crafting with what's in it, is no longer refused. The game pools every chest of the zone you're in (a chest's window shows them all, the character page too, and building takes from them), and the sanity limits (0.31.0) only allowed chests near the partner: the far chest's change was undone and its old contents sent back, so the partner kept what they took as well, and the host's chat called it refused.
  • Partners learn the alchemy mixes the host discovers. Their game looked the mix up where the game never keeps mixes, so it never learned one ("Alchemy mix ... isn't known here" in every partner log with alchemy).
  • Hauling carried items into containers no longer counts as sending story triggers too fast: picking up a log and putting it in a container are a trigger each, and a minute of hauling went past the limit of 60. Now 240 a minute.
  • Browse public games no longer seems stuck on "Looking for games..." when there are none: every refresh put it back to "Looking" for the seconds Steam takes to search worldwide. It says it's looking only until the first answer, and an empty list says it checks again every 15 seconds.
  • Over Steam, a partner whose game dropped can rejoin at once: until Steam timed out their old connection (10 to 20 seconds), the host turned them away as "someone called ... is already playing".
  • A failed send (to a player who just left, say) no longer breaks off what the game was doing when it changed something, nor skips the players after them.
  • The host's tent upgrade can't be stopped by the town link sync (0.31.0) failing: it catches its own errors now.
  • New objects or station work not yet sent when a session ends no longer go out at the start of the next one.
  • A partner whose session ends while their clock is waiting for the host's no longer keeps a stopped clock, or the host's day length, in their own game afterwards.

New

  • Arrows and spit fly on everyone's screen: the host's spitters' spit and other players' arrows only flew in the game that shot them. The copies only show; the hit is the shooter's.

Public games

  • Data from another player's game can no longer make types that reach processes, files, the network or reflection (items, crafts, zombie sheets and the joining save are read with a restricted type list).
  • A message claiming more data than it holds is refused before anything is set aside for it, and a message sent in parts stops at 16 MB.
  • The host runs only the game's own scripts for players who aren't friends: a partner's item and building scripts that change the shared world run in the host's game, and a changed game could have sent any script there. Story values a partner's scripts change are checked the same way.

Speed (the host, big saves)

  • Less work every second for the objects around partners: objects that don't move cost one lookup instead of six, views are found without parsing ids again, and two passes stopped copying the whole area's object list.

Who needs it

  • Plays with 0.31.2, 0.31.1, 0.31.0 and 0.30.0 (same protocol), but most fixes need both games on 0.31.3 (one game sends or checks, the other applies), so everyone should update. 0.31.2 is 0.31.3 without the first fix.

0.31.2

  • 0.31.3 without its first fix (the one-player-at-a-time tables).

0.31.1

  • A partner's energy fills at the same speed as the host's again while everyone sleeps. Since 0.31.0 a partner's clock waited for the host's whenever it got a moment ahead, and asleep, when the clock runs 50 times as fast, it was waiting nearly all the time; energy only fills as the clock moves, so the partner filled at a thirtieth of the speed, and the host's sleep went on for days until they were rested. (Reported on the Discord with both logs, thank you.)
  • Plays with 0.31.0 and 0.30.0 (same protocol), but the fix is in the partner's game: partners need 0.31.1.

0.31.0

Your world, with players you don't know

  • Other mods: the host decides which other mods joining players may run (Hosting options > Other mods): Any (as before), Same as mine (the host's mods, same versions), Approved (only mods the host approved), or None. Mods that change the world run in one player's game only, so the worlds drift apart. Client-side mods, which only change their own player's game, always pass (see below). Each player's game reports its own mods, so this stops mistakes, not someone who changes the mod to lie.
  • A Mods page in the Co-op menu (from Hosting options): your mods, the mods seen on players who joined or tried to, Approve beside each, and the client-side and host-only mods.
  • A player turned away for their mods is told which to add, turn off or update, and the host hears about it in the chat. Browse games shows a game's rule ("no other mods", "host's mods only", "approved mods only"). Both players' co-op logs list the other mods each one runs, for bug reports.
  • Non-friends may (Hosting options): what players who aren't your Steam friends may do in your world (over an IP address, everyone counts as one): Do anything (as before), Build, not take (no taking down buildings or taking from chests and stockpiles), or Only look. A guest shows as one in the Players list, with Trust to let them do anything a friend may until they leave. What a guest may not do is undone in their game, and both of you hear why.
  • Sanity limits (Hosting options, on by default), against a game changed to cheat in your world: other players' changes count only near their own character (build mode a fair way off); shared money, tech points and reputation change by no more a minute than play can earn or spend; a hit does no more than twice the game's best weapon, and comes no faster than swinging; recipes, tech and buildings unlock only if the game has them, no faster than play; story triggers, village buffs, sleep and cremations come no faster than play; crafting stations, graves, zombies, resurrection tables, troop flags and dropped items change only near the player; zombie talents are always paid for; a vendor's money moves by no more than a trade can; the town orders board comes only from the host; a flood of messages gets the player removed; chat lines come no faster than typing. What's refused is undone in their game, and you hear about it in the chat.
  • Back up my save (Hosting options): a copy of your save slot before other players come in, in "GK2Coop backups" in the game's save folder: Before non-friends (the default; over an IP address, anyone), Before anyone, or Never. At most one every 10 minutes, the newest 10 kept, and the chat says when it's done.
  • Same game version: a player on a different version of Graveyard Keeper 2 than the host is turned away and told both versions. Browse games shows a game on another version.
  • Only players you let in are heard: a game that skipped the hello, or was turned away (password, ban, Ask me first), could still have said it was ready and been treated as a player. Not any more.

Teleport and Unstuck

  • Teleport (Co-op menu, asked for by a player): the host has Bring everyone here, and for each player Bring here or Go to; every player has Go to for the others, if the host lets them (Players may teleport, Hosting options: Everyone, Friends only, or Nobody). The Co-op menu closes as you go. Anyone who teleports is watched for a few seconds: if they drop through the map, a player the host brought is put back beside the host, and anyone who went to someone goes back where they were.
  • The host's fall rescue: if you fall through the map (no floor, far below where you stood), you go home to your house. During the guided intro you go back where you last stood instead. (Partners already had one.)
  • Unstuck (the pause menu, under Co-op): after a yes, home to the bed in your house, for when you're stuck or fell through the map. During the guided intro a partner goes to the host, and the host back where they last stood. Not during a scene, a fight, or on the way somewhere.

Other mods in co-op (from a review of more than 150 public mods)

  • Client-side mods always pass the Other mods rule: GK2 Performance, GK2 Mod Framework, GK2 HUD Numbers, Smart Inventory Filter, What Time Is It, Who Buys This?, Map Markers, Pin My Recipe, GK2 Codex, GK2 Shopping List, GK2 Thoughtful Week, Craft Max, GK2 Known Formula Helper, GK2 Queue Count, Storage Filter, Mod Settings Menu, the GK2 Localization API, Always Show Tech Points, GK2 Alchemy Recipe Book, GK2 Corpse Inspector, Quest Tracker, Rune Research Tracker, Vanilla Quest Journal, Weekly Overview, Keeper's Daily Reminders, GK2 Ultrawide Fix, Skip Autopsy Confirmation, GK2 Performance (gk2.performance), Jc0de FPS Boost, Instant Transitions and GK2 Faster Doors, each checked against GK2 Co-op and GK2 Performance.
  • Host-only mods run in the host's game for everyone, so a player can't join with them on (they're told to turn them off): Timbn Living Town, Auto Station Service, Zombie Compost Gardener, Zombie Care, Clerk Desk and Reporter Desk. A partner's copy did the host's work a second time (villagers spawned, stations worked, zombies trained, rewards paid twice).
  • The Other mods rule also sees mods that aren't BepInEx plugins: mods only the GK2 Mod Framework loads, Kebo mods, and mods dropped into the game's own folder (Cheat Menu, Zombie Automation) or run from the Steam Workshop.
  • Other mods' work on the host's systems no longer runs twice: in a partner's game the zombies, crafts, conveyors, villagers and timers the host runs aren't updated at all, so mods hooked to them (Zombie Chores, Graveyard Automation, Keeper's Longer Days, Zombie++) stay idle there instead of redoing the host's work.
  • A partner's clock runs at the host's speed (Keeper's Longer Days and cheat menus change how long a day lasts) and waits for the host's instead of running ahead and being put back, which ran the day's timed events again (No Sleep, No Tomorrow holds the host's clock until sleep).
  • Stack sizes follow the host's: with Better Item Stacks, Bigger Storage or GK2+'s bigger stacks on one side only, or set differently, the two games split items differently and a chest's stacks didn't fit a partner's slots. A partner's game now uses the host's sizes in the host's world and gets its own back on leaving.
  • Moved buildings move for everyone: a station GK2 Move Buildings carried with its crafts, any station Keeper's Relocation Service moves, and graves and benches A Grave Move moves stayed in their old place for the other players until they rejoined.
  • GK2 Move Buildings' upgrade in place works in co-op: the player who places the better building replaces the old one, once, for everyone (a partner's game did it only for itself, or a second time with a second refund).
  • Pin My Recipe counts a partner's crafts again; GK2 Baby Pets' pet follows its owner, not the other players; Zombie Rename's new names reach everyone; GK2 Donkey Cart Expanded's "no corpse" ending no longer runs twice in a partner's game; Craft Max's Science MAX on a partner sends at most 40 studies a press (a big stack went past the host's flood limit, which dropped the rest after they were paid for).
  • Where GK2 Co-op works with another mod (Pin My Recipe, GK2 Move Buildings, Keeper's Relocation Service, GK2 Baby Pets, GK2 Longer Days, A Grave Move), it's made for one version of it: with another version you're told once you're in a world, and the Mods page says which.

Fixes

  • Villagers in a partner's game no longer break after the host upgrades a villager's home. The upgrade moves the villager to its new tent with a change partners never got, so their game kept the villager tied to a tent that was gone and its walk home failed on every tick. From then on the partner's clock ran about 2.4 times too fast (pulled back to the host's every 2 seconds), and the partner's game stopped running villagers, zombies and timed events for the rest of the session. The host now sends the new link, and a timed script that fails in the game's own code no longer repeats every tick. (Found in a player's two-hour log, thank you.)
  • Craft bubbles in a partner's game no longer show queued items and stars twice. A zombie farming a bed points itself at that bed in the host's game only, so in the partner's the bed's bubble asked the zombie about a craft it didn't have, failed halfway through drawing, and left the half-drawn parts behind; the game reuses its bubbles, so they showed over other stations too. (From 0.30.0.)
  • The host's talk with a town building (the apothecary's trade and upgrade menu) is the host's own, like a shopkeeper's: partners were pulled over to watch the host pick through it, without control.
  • The chat box keeps the HUD's size when the UI scale changes (the game's UI scale setting, a new resolution, GK2 Ultrawide Fix); it kept the size it started with.
  • Plays with 0.30.0 (same protocol), but a 0.30.0 player can't join a host who checks mods, and the fixes above need everyone on 0.31.0.

0.30.0

Public games

  • Public games: the host chooses who can join (Hosting options, also while hosting): Friends (as before), Public (anyone with the mod finds the game under Browse games) or Invite only (only people invited through Steam).
  • Browse games: a page in the Co-op menu that lists public games from everywhere, with their name, host, day, players, and whether they have a password or ask first. Games for another mod version or full ones say so. Refreshes every 15 seconds, or with Refresh.
  • A password for your game (optional), over Steam or an IP address: joiners type it in the Co-op menu. The password itself never leaves your PC: only a check made from it is sent. Over Steam, three wrong tries and that account waits a minute.
  • Ask me first: you're asked (a yes or no question, or buttons in the Co-op menu) before someone comes in. Your choice: for non-friends (the default; someone joining by IP address counts as one), for everyone, or off. No answer in a minute is a no; during your own scenes the question waits.
  • A player limit (2 to 8, 4 by default): the game shows as full and turns away anyone past it.
  • Ban: next to Remove in the Co-op menu, by Steam account (a new name doesn't get them back in). A banned player can't connect to your games, and your games don't show up for them under Friends hosting or Browse games. Unban on the Banned players page.
  • Activity in chat: what the other players build, take down and take from chests in your world shows in the chat ("Sam built 3 fences", "Sam took 5 logs from a chest"), so everyone knows who did what. The host picks: everyone sees it, only the host, or off. It's always in the co-op log.
  • Characters of players who join over Steam are kept under their Steam account instead of their name: they keep it if they change their name, and nobody gets it by taking that name. A character kept under a name from before moves to its owner's account the first time they join (if they're the host's Steam friend). Joining by IP address works as before, by name.
  • A game name for the browser (else "<your name>'s world"). The game name and password are rows like the other settings, with their box where a setting's value goes.
  • The Menu style setting is gone: the game-style Co-op menu is the only one. (The plain window only opens if a game update ever stops the menu being made.)
  • The Co-op menu's scrolling pages have a scroll bar.
  • The Co-op menu lists the players as a list: a row each (you too) with where they are and their ping, and for the host Remove and Ban on the same row. Players in the lobby and those asking to join are rows too.
  • Banned players: a page of its own (Co-op menu while hosting, or Settings), with Unban beside each, and everyone who played with you since the game started, to ban someone after they've left.
  • Another player's new clothes show in their own colors: a costume you don't wear came out in the colors meant for yours (dark instead of green) after "Change my look".
  • The chat box is smaller and fits small screens and windows: at most about a third of the screen's width and a fifth of its height (it covered most of a small window before), and it fits again when the window's size changes.
  • The "..." bubble while someone types is wider, centered over their head and above their name (it was a sliver to one side, on top of the name). What they say shows above the name too.
  • On the map, every player's icon is smaller during co-op (yours too: 60%, MapMarkerScale in the config file), with names as big as before. Another player's icon no longer goes missing with only their name showing.
  • Another player's character gets its outfit put on again a moment after it appears, and if its arms or beard still don't show, it's put on again and the log says in detail what the character looked like (for the missing arms some players have seen).
  • Joiners turned away by a host see why (full, wrong password, banned, the host said no) instead of just "couldn't connect".

Chat (from the 0.29.0 test version, never posted on its own)

  • Chat: press Enter in a co-op game to talk to everyone. The chat box sits in the bottom left, made from the game's own text and text box. While someone types, a thought bubble with "..." shows over their head, and what they say shows there in the game's own speech bubble (not during story scenes). New lines fade after a few seconds; hover over the box to bring it back and scroll the history with the mouse wheel or Page Up/Down. Up and Down bring back what you sent; Esc closes it.
  • The mod's notices are chat lines now, instead of pop-ups and the game's notifications: who joined or left, talk requests, the waits. They show during the host's cutscenes too.
  • The story in the chat, a setting with four choices: Off; Choices (the answers picked in conversations, by anyone); When away (those, and the host's lines while you aren't watching their scene); Always (every line of every scene and conversation, your own too).
  • F9 opens the co-op settings (F8 still opens the Co-op menu).
  • Settings: a Chat section (chat on or off, messages over heads, how long new lines stay, hidden or faint when faded, story lines). The Settings page scrolls when it's taller than the screen.
  • The names over the other players are in the game's own text now.
  • The Co-op menu's message box is gone: the chat has it.

Fixes

  • In a fight, the other players' swings no longer use up your stamina. The game spends stamina in the attack animation, and it spent the stamina of whoever's screen it played on, so a partner couldn't swing while the host was attacking (and the other way round).

  • A partner sees the zombies in the host's fights in the sewer: every fighter stays drawn wherever it is, as in the host's game.

  • After a fight in the sewer (or any closed arena), partners still in it come out with the host instead of being left behind (they had to jump into the void to get back). Partners watching a scene there come out after it.

  • NPCs no longer disappear for a partner who is away from the host. The host's game counted villagers off its own screen as gone, and partners near them stopped drawing them.

  • Everyone needs 0.30.0 (protocol 39: it won't connect to 0.28).

0.28.4

  • Fixes a possible crash in a partner's game when NPCs talk. 0.28.3 kept NPCs' speech bubbles above their heads by changing a game function that crashed the game when it was changed the same way in an early version; the bubbles are now placed another way.
  • The co-op debug log is about a quarter of the size (a few-hour session was 6 MB, too big to post on Discord): the state snapshot comes every 10 s and whenever something important changes, instead of every 2 s. (Meant for 0.28.3, but it missed that upload.)
  • Works with 0.28.2 and 0.28.3 (same protocol). The crash fix is in the partner's game, so partners should update.

0.28.3

  • A partner near the host watches the host's scenes from where they stand again, by default. (0.28.2 had them take the host's place for every scene of the intro, a step away.) The setting is now called "When near the host": Watch from here, or Take their place.
  • A partner standing in for the host wears the host's armor too (it showed the host's bare head and body before the intro's fight).
  • A partner sees the notes the host reads nearby (the intro's note on the table was missed).
  • A partner's sword, spear and bow hits play their sound and the enemy's hit effect at once, instead of after the host's game had the hit.
  • NPCs' speech bubbles no longer come out of their feet in a partner's game.
  • Joining a lobby from the Co-op menu shows it in the menu instead of a pop-up, and the menus close when the host starts the game.
  • In the host's fights everyone hears and sees every hit, the other players' and the soldiers' and enemies': its sound, and the flash on whoever was hit. A partner who gets hit hears and sees it too.
  • A partner hears the fight music, and the start, win and lose jingles.
  • You hear the other players pick up bodies, zombies and logs, and the bite, the hook, the catch and the fail when they fish.
  • What a partner harvests next to the host is theirs to pick up: for a few seconds its drops are left for them, where the host's character used to pull them in first.
  • Harvesting, fighting and walking side by side no longer cuts out each other's sounds. (The game skips a sound that started a moment before the same one, which dropped one of two players' chops and steps.)
  • A partner working at a station (or on a tree) when the host's scene starts no longer comes back stuck there, unable to stop working or walk away.
  • Joining a host whose save has a morning scene waiting (the foreman waking you up) no longer plays that scene in the partner's own game, wherever they stood, with the host's lines over the partner and no control after it: the host's game plays it, and the partner watches.
  • NPC talks: while the host picks through an NPC's talk menu, trades or says goodbye, partners keep playing. They are brought in only when an answer plays out as a scene.
  • When one of the host's scenes follows straight after another (the brothers in the village), a partner no longer goes home for a moment and comes back late.
  • NPCs a scene puts in place face the way the scene turns them on a partner's screen (the village merchant faced right).
  • The co-op menu no longer stays open behind the main menu after leaving a game.
  • Steam: "Friends hosting" finds friends' worlds more reliably (the host's lobby is also in its Steam status), and shows a world while its version is still being looked up.
  • If another player's character loses its arms on your screen, its outfit is put back on after a couple of seconds, and the log says what the character was doing (to find the cause).
  • Fights no longer fill the game's log with thousands of "Invalid Layer Index" warnings.
  • Works with 0.28.2 (same protocol), but update everyone: the drops fix is in the host's game, most other fixes in the partner's, and the new sounds need everyone on 0.28.3.

0.28.2

  • The map shows the other players: each one's icon with their name, outdoors where they stand and indoors at their building, moving while the map is open.
  • Areas anyone finds show on everyone's map and stay found. A partner's discoveries used to stay in their own game, and were forgotten when they joined again.
  • Spitting zombies' spit hits partners in the host's fight (it flew through them).
  • Everyone's wisp follows their own character on the others' screens too, as a fairy when yours is one.
  • The Co-op menu is now in the game's own style, made from its windows: a player list with pings, buttons for hosting, joining and leaving, a message box, and a Settings page (connection, rejoining where you left, story scene options, what new partners start with). Each setting explains itself when you hover its ?. The plain window is still there (Settings > Menu style).
  • A Co-op button in the main menu (under Load) and the pause menu opens it; F8 opens and closes it too.
  • Short messages typed in the Co-op menu show in everyone's game notifications. The host can remove a player (the game's yes/no question asks first).
  • Story talks no longer need every partner nearby, by default (Settings > Story talks need everyone).
  • By default a partner near the host takes part in the host's scenes in the host's place, instead of watching from where they stand (Settings > Watch from where I stand).
  • After a scene, a partner who was brought over always goes back where they were, unless the scene led into a fight or took the host to another area. (It was a setting.)
  • GK2 Co-op is now a beta.
  • Both players need 0.28.2 (protocol 37).

0.28.1

  • Much less network traffic from the host. A crafting station's progress goes out as a small update instead of its whole queue four times a second, which was most of what the host sent while stations ran. Play is smoother on slower or distant connections, and a partner's game does less work for each station.
  • A partner's actions at things the host can't see on their screen work: putting a zombie on a station, a carrier, a mine or a sawmill, and other object actions, while the host is elsewhere or looking another way.
  • A partner who takes the last craft out of a station sees it empty right away.
  • In the host's fight, a partner sees the soldiers and enemies with their weapons and armor, and every swing and shot as it happens (quick attacks were often missed).
  • Everyone sees the other players' sword swings and bow shots, their aiming stance, and a knocked-out player getting back up.
  • A partner's alchemy mixes no longer use up their ingredients twice, and boosting a mix works (the host's alchemy table kept the boost running, and the mix waited behind it).
  • A partner can decompose items for science at the study desk (it did nothing, and left the host's desk busy).
  • Zombies' equipment, collars, organs and pockets, their level-ups and the tech points they earn are the same for everyone. A partner equipping a zombie or buying it a level-up changed only their own copy, and partners never saw the points zombies earned.
  • In the host's fight, a partner sees the zombie fog roll in or clear and the arena change as flags are taken.
  • Notices about talking to NPCs together (who wants to talk to whom, who has to come over) and a partner's sermon collection show as your character's thought, like the game's own messages, instead of a pop-up.
  • In conversations, the others see what you answered in the game's own notifications ("Sam said "…""), also during cutscenes, and "… is choosing the answer." shows there instead of a pop-up.
  • Falling asleep no longer counts the coins and tech points lying around twice (every game gathered them, and they're shared). Tech points left lying in the host's areas no longer come twice for a partner who joins either.
  • The host's save on waking has its partners rested. Their character could reach it from before they went to bed, so after loading that save they were tired again (and missing what they did just before sleeping).
  • A partner who isn't tired gets the game's own answer from a bed, instead of sending the host a sleep request.
  • A partner who joins, or uses a bed, while everyone sleeps falls asleep with them. Before, they stayed up while the world sped by, or lay in bed until everyone woke.
  • In a shared sleep, a partner's lack of sleep goes with their own sleep and takes insanity off once, as in the game. It came back every second while the host slept on, or went without the insanity relief.
  • If waking ever leaves a black screen with no controls, it finishes after a few seconds.
  • Both players need 0.28.1 (protocol 36).

0.28.0

  • Sermon buffs are village-wide: whoever gives the sermon, everyone gets the buff and it works for the whole world. Everyone sees the village's buffs and the zombie debuff with their time left.
  • Partners no longer start with the host's own buffs (a beer the host drank).
  • Partners earn achievements for themselves: their progress is kept with their character in the host's save, achievements the host already had no longer count as done for them (or get handed to them), and story and world achievements reached together unlock for everyone in the world.
  • A partner's crafts no longer get stuck in the queue when the host's own character couldn't make them (a fishing rod needing woodworking skill the host doesn't have): the host checked its own character's tools and skills instead of the partner's.
  • When the host's fight starts, a partner in the same area goes to the fight's start point with the host instead of being left outside the arena's borders.
  • When a partner's game crashes or freezes, the host can talk to NPCs again after a few seconds, instead of waiting for the partner to come over until their connection times out a minute later.
  • Another player's character that lost its arms (seen after joining while the host was inside a house) gets them back within half a second; each time is noted in the co-op log.
  • A partner in the host's fight sees the flags being captured: the capture banners at the screen's edges and the spinning ring on a flag being taken, not only the flag's height.
  • Enemies in the host's fight only go after a partner who's inside the arena (a partner elsewhere in the area was a target too, out of the enemies' reach).
  • Zombies killed in a fight leave their death puff, blood and stains in a partner's game instead of just vanishing.
  • Soldiers and other moving characters no longer get their attack or work animations replaced by walking in a partner's game.
  • Studying an item for the first time (mushrooms at the study desk) counts for everyone right away: the repeat studies and alchemy open up in a partner's game too, not only after rejoining.
  • A partner collecting bread from an oven or bars from a furnace gets them (they stayed inside the station while the next batch started; the next collect hands those out too).
  • A partner who just planted, or watches the host plant, no longer sees a grown plant for a moment first.
  • Furnaces and other stations no longer restart their sound over and over in a partner's game.
  • Porter zombies walk in a partner's game instead of sliding along sitting down (also the ones the host's game moves outside its usual list of moving things).
  • A partner can put a zombie on a station while the host is elsewhere or not looking at it (it was refused until the host came over).
  • A zombie working a station shows its work in a partner's game: the station's working look and progress, and the zombie's work pose.
  • The host talking to a shopkeeper (or anyone) no longer opens a story panel at the bottom of a partner's screen; it only comes up when the partner picks an answer.
  • Partners get the first tier of the shovel and hammer the story gave the host, not the host's upgraded ones.
  • A partner can fish: the walk to the fishing spot froze them in place, spinning, and fishing never began. Their catch takes the fish from the pond in the host's world too.
  • Other players see you fish: your line and bob as you cast, wait and reel in, the "!" when a fish bites and the fish under the water. Your line no longer stays out on your character in their game after you stop.
  • A zombie carrying things (a caretaker taking logs from the chests to a station) shows its load in a partner's game as it picks it up, and hands it in instead of seeming to leave it lying on the ground.
  • After a partner's sermon its parishioners walk out of the church in the partner's game, instead of standing there and vanishing one by one.
  • A partner can take the collection from the church's donation box after their sermon (and the trading money from the town chalk board): it goes into everyone's money. It was refused as part of the host's story.
  • A partner who falls out of the world (joining on a spot whose floor wasn't there yet) is put back where they last stood, or next to the host. The spot kept with their character is always one they stood on, so they don't join into a fall again.
  • Both players need 0.28.0 (protocol 34).

0.27.3

  • Partners are no longer pulled to the host on every door and waystone in saves where an intro quest was left open (a branch not taken in the prison). It also works in saves that finished the intro before co-op.
  • A partner's village buildings and repairs, garden fertilizer and instant recipes happen in the host's world.
  • Defences a partner builds at the military base count in the host's battle preparation and come back after a battle.
  • Town orders (the chalk board) are shared: everyone sees the same orders, and a partner's picks and collected rewards reach the host. Deliveries onto the warehouse palettes count for the host's orders.
  • Fertilizer on garden beds shows for everyone.
  • Taking an item off a conveyor no longer gives the partner a second copy.
  • A partner's cremation lowers the host's body count. A partner's resurrection makes the zombie in the host's world.
  • The choir's zombies are put in through the host, like other zombie work.
  • Both players need 0.27.3 (protocol 32).

0.27.2

  • Partners are no longer pulled along whenever the host goes into a building or uses a waystone. Only the guided start of the story (the prison, the scout, the defence) and story scenes a partner is watching take them along.
  • Works with 0.27.1 (same protocol); update both when you can.

0.27.1

  • Crafted supplies and other big items land by the station again instead of getting stuck in the bag. Any already stuck in a bag are put on the ground at your feet when you load the game.
  • A partner collecting a furnace's or crematorium's finished batch collects it once; the station is free again.
  • A partner's buildings work in the host's world: the crematorium, composter and porter station appear for the host, and graveyard plots a partner places count toward the graveyard's quality.
  • Partners see the battle flags rise and turn blue when they're captured.
  • Shared sleep no longer runs on forever when a partner's game can't fall asleep.
  • Both players need 0.27.1 (protocol 31).

0.27.0

  • Host and join through Steam: friends who host show up in the co-op window (F8), with Steam invites and "Join Game" too. No addresses or port forwarding; the connection goes through Steam's relays.
  • Joining by IP address still works (Connect: IP address in the F8 window).

0.26.1

  • Partners can no longer take the story's quest items or work the intro's quest objects (a partner picking the prison's mushrooms left the host stuck).

0.26.0

  • Updated for Graveyard Keeper 2 1.010 (crow nest, tech reveals, story animation states).
  • Partners see the host's fight wave timeline on the HUD.

0.25.x

  • Following the host through the guided intro (doors, scenes that walk the host away).
  • Partners can keep attacking in fights (stamina refills) and see their HP and stamina bars.
  • Burials, harvests and stockpiles fixed for partners; story camera pans match the host's.
  • Sleep is the host's call; partners send a sleep request. The sleep screen shows everyone's energy.

0.24.x

  • No more doubled items; one player per work station, and hand-made items go to whoever made them.
  • Partners' tech points fly into their counter; messages use the game's own notifications.
  • The first shovel, hammer, axe and pickaxe reach partners who don't have them.