Project Zomboid Server World Reset After Restart? How to Fix It

When a Project Zomboid server restarts into a brand new world, the old world is almost never deleted. The server simply started under a different server name or a different data folder, could not find the old save, and made a new one with default settings next to it. Find which name or folder the old save lives under, point the server back at it, and everything returns. The other common case is a rollback of a few hours after a crash, which is a saving problem, not a reset.

First, what exactly reset?

Look at what changed before touching anything:

Each one has a different fix below.

Cause 1: A different server name

Everything a server has is tied to its name. With the default name servertest, the files are:

Zomboid/Server/servertest.ini
Zomboid/Server/servertest_SandboxVars.lua
Zomboid/Server/servertest_spawnregions.lua
Zomboid/Saves/Multiplayer/servertest/
Zomboid/db/servertest.db

If the server starts with -servername MyServer one day and without it the next, it looks for MyServer files, finds none, and creates a new set with defaults. Your old world is still sitting in Saves/Multiplayer/servertest/.

Fix:

1. Open Zomboid/Saves/Multiplayer/ and list the folders. Each one is a world. The one with the most files and the oldest date is usually yours.
2. Check the matching .ini in Zomboid/Server/ has your settings and mods.
3. Start the server with that name again. On a home server that means the -servername value in your start script. On a GamezServers server it is the Save name setting in the panel.

The extra empty world can be deleted once you have the old one back, or left alone.

Cause 2: A different data folder

By default the server keeps everything in a Zomboid folder in the home directory of the user running it. Anything that changes the user or the path makes the server look somewhere else:

• Running as another user. On Windows, starting the server once from your account and once as a service or another account gives two separate Zomboid folders, one under each user. On Linux, running once as root and once as a normal user does the same.
• The -cachedir= option. It moves the whole data folder. Adding or removing it from the start line switches between two worlds.
• Moving the server files. The game files can move freely, but the data folder does not move with them.

Search the machine for servertest.ini (or your server name) to find every copy. The one with the right world is where the server should point.

Cause 3: A crash before saving

If the world is the same but the last hour or two is gone, the server stopped without saving. Project Zomboid writes the world to disk as players move around and on a clean shutdown, but a crash, a power cut or killing the process can lose recent changes.

To reduce the loss:

• Stop the server cleanly with the quit command in the console, which saves first, instead of closing the window.
• Set SaveWorldEveryMinutes in the .ini to force regular saves. A value of 15 to 30 is a sensible middle ground. Very short intervals cause small hitches on big servers.
• Find out why it crashed. Running out of memory is the usual reason on modded servers, covered in the lag and rubberbanding guide.

Cause 4: One player has a new character

When only one person is back at character creation, the world did not reset. Characters belong to a username, so a typo or a different capital letter in the username creates a new account and a new character on an open server. Ask the player to join with exactly the old username. If their old character really is gone, see resetting a player's character for how characters are stored and how to inspect them.

Cause 5: Sandbox settings back to default

If the world and players are fine but zombie and loot settings changed, the save is using its stored sandbox copy, not your Lua file. That is the map_sand.bin problem, with the full fix in changing sandbox settings on an existing world.

Cause 6: Build 41 and Build 42

Build 42 cannot continue a Build 41 multiplayer world, and the reverse does not work either. If the server updated or switched branches and the world now loads broken or as new, check which build it is on. Put it back on the branch the world was made on, restore a backup from before the switch, and plan a fresh world for the new build. The build switch guide covers doing this safely.

Getting the world back safely

Whatever the cause, before you start moving folders:

1. Stop the server.
2. Copy the entire Zomboid folder somewhere safe.
3. Make one change at a time and start the server to check.

Never copy a world folder into another while the server runs, and do not mix files from two different worlds.

Avoiding it on a hosted server

On a GamezServers Project Zomboid server, the save name is one setting in the panel, the data folder never moves, and the server always starts the same way, so causes 1 and 2 do not come up unless you change the Save name yourself (the old world stays on disk if you do). One click backups cover the save, settings and account database together. To set one up for your group, see the Project Zomboid game page.

FAQ

Did my Project Zomboid server delete my world?

Almost certainly not. Look in Zomboid/Saves/Multiplayer/ for a folder with your old server name. Start the server with that name to load it.

Why are my server settings back to default after a restart?

The server started under a new name and created a fresh .ini. Your old settings are in the .ini with the old name in Zomboid/Server/.

How often does a Project Zomboid server save?

It saves as players play and on a clean shutdown. Set SaveWorldEveryMinutes to force regular full saves, for example every 15 or 30 minutes.

Can I merge two Project Zomboid worlds?

No. Pick one world and use it. Copying chunk files between worlds causes broken areas and duplicated items.