Back up first, then mod

Why a backup is mandatory

Mods hook directly into the game. That is the point – but it has side effects:

• Saves with mod devices only load while the mod is active. If it is missing from the active mod pack, loading fails.
• Game updates by RocketWerkz can temporarily break mods until an update is released.
• A bug – in the mod, the game or the interplay of several mods – can damage data.
• A multiplayer server writes all changes to the save immediately. Undo only works with a backup.

Where are the saves?

On Windows every world lives in its own folder here:

%USERPROFILE%\Documents\My Games\Stationeers\saves

Tip: paste the path into the Explorer address bar and press Enter. Each subfolder (for example “Test World”) is a complete world.

Backup in five steps

1. Quit the game completely – not just to the main menu. That way everything is written.
2. Open the saves folder in Explorer (path above).
3. Copy your world folder and paste it somewhere safe, ideally outside “Documents” (second drive, USB stick, cloud).
4. Name the copy with a date, for example “Test World 2026-10-07 before Power Engineering”.
5. Only now subscribe to, update or remove mods.

%USERPROFILE%\Documents\My Games\Stationeers\profiles\my mods.xml

Restoring a backup

1. Quit the game.
2. Rename the broken world folder in saves (do not delete it – you may need it for a bug report).
3. Copy the backup back into saves and give it the original name.
4. Make sure exactly the mods that were active at backup time are active in LaunchPad. Then start the game.

Dedicated servers

On your own server the save lives in the server's data folder. Stop the server, copy the folder, then change mods on the server. Players need the same mods in the same version.

Removing a mod? Read this first.

If you want to remove a mod from a running world, deconstruct all devices of that mod first and save. Otherwise the game is missing data when loading. When in doubt: load the backup.