Skip to content

Saves and co-op

Each single-player save slot records two things about mods: which were active, at which version, and the data each stored with mod.save.

slot1/mods.json
{ "api": 1, "mods": [ { "id": "solar_flare", "version": "1.0.0" } ], "data": { "solar_flare": { "total": 3 } } }

When you load a slot with a different set of mods, the game:

  1. logs one line per difference: a mod added, a mod missing, a version changed;
  2. shows a banner, and lists the save on the MODS page;
  3. plays on. A modded save is never refused.

Data of a mod that is not running stays in the file, untouched, and is there again when the mod comes back.

The save container has checksums. They only detect damage, and the game then restores the newest good backup. A checksum never blocks a modded game.

In co-op the host runs the rules and every player runs a client (Two VMs), so every player needs the same mods.

Player joinssends its active mods: id, version, fingerprint
>
Host compareswith its own set
>
Samejoins
Differentrefused, with the list of differences

A refused player sees what differs, for example:

Mod mismatch: solar_flare 1.0.0 is missing on the other side (here = host)
  • The fingerprint is a checksum of the mod’s files. Same id and version with different files is refused.
  • A folder and a pack of the same mod have different fingerprints. Everyone should use the same .nkp.
  • A side: "server" or "client" mod still counts. Everyone needs it.
  • A player with no mods can join a host with no mods.
  • A co-op session keeps no mod data, and save_loaded does not fire.

After toggling a mod on the MODS page, hosting and joining are blocked until you restart, so the set you play with is the set you announce.