← Project Zomboid guides

Project Zomboid · updated 14 November 2026

Project Zomboid server settings not saving or not applying

You raised the loot, lowered the zombies or turned PvP off, you restart the server and everything is the same. Or worse: you open the file and your change is gone. It's almost never a game bug: it's one of six things, and each one takes a minute to spot. Here they are in order, from most to least common.

Different case? Ask with this guide inChatGPTClaude

First: which setting did you change?

A Project Zomboid server keeps its settings in two files, and each one fails in its own way. The .ini holds the server's: password, players, PvP, whether it shows in the public list, the mods. The SandboxVars.lua holds the game's: zombies, loot, when power and water shut off, XP.

What's in the .ini changes as soon as the server starts again. The SandboxVars is also read at startup, but many of its settings only count for what gets generated from that moment on, and that explains half of the “it does nothing” cases. What each .ini option does and the sandbox settings go through them one by one.

Rather not set it up yourself? Project Zomboid servers from €12 a month, no contract and a full refund within 72 hours. Or create a free Project Zomboid server, no card needed.

You changed it with the server running

This is the most common cause when the change disappears from the file. The server has its settings loaded in memory and, when it saves or shuts down, it can write its files again with what it had, on top of what you just edited. Almost every hosting company's guide and plenty of Steam threads agree on this.

The fix: stop the server, edit, save and start it again. If your change is already lost, make it again with the server stopped.

You edited a different file

The files carry the server's name: one called servertest reads servertest.ini and servertest_SandboxVars.lua, and one with another name reads its own. If you upload the servertest.ini from your PC to a server with a different name, the server doesn't even look at it.

It also happens the other way round: on your PC there's a Server folder with several .ini files (one for each server you've created from the “Host” menu) and it's easy to open the wrong one. The right one has the name you chose when hosting.

The save goes by that name too: if you rename the server so it reads another file, it starts with a different save. If what you want is to use your PC settings, copy their values into the file the server already uses, don't rename it.

A badly written value

If the server doesn't understand a value, it usually doesn't warn you and keeps the default. The classics are writing “yes” or “1” where true goes, a decimal comma where a point goes (1.5, not 1,5), extra quotes or a space before the equals sign.

In SandboxVars.lua it's more delicate, because it's a code file: one missing comma or brace can stop everything after it from being read. If after editing it by hand everything goes back to default, compare your file with an earlier copy. The Project Zomboid settings editor opens both files in your browser and lets you change each option without typing by hand.

It's one of the settings that only apply to a new world

Some game settings are only used when the world is created: the starting zombie population, the map, the start month and day. Changing them in a game that's already running doesn't move what already exists.

Others count from then on, but don't touch what's already generated: more loot or more cars show up in areas you haven't been to yet, not in the houses you already visited. If the whole world has to change, you need a new world, without deleting the old one.

You changed it with /changeoption

With the server running, an admin can change a .ini option with /changeoption PVP "false" and send it to the players with /reloadoptions. It works for the .ini, not for sandbox settings.

If the old value came back after restarting, open the .ini and check the change is written there. If it isn't, put it in the file with the server stopped: that way it sticks. The admin command generator writes the command with its quotes.

If none of that fits: the save's own copy

Several hosting guides and forum threads say the save also keeps its own copy of the sandbox settings (a map_sandbox.bin file, in the save folder) and that, if a SandboxVars change never gets in, moving that file aside makes the server read the .lua again. We haven't tested it ourselves and it isn't in the game's documentation.

If you try it: stop the server, first make a copy of the whole save, rename the file instead of deleting it and start the server. If anything gets worse, give it its name back or restore the copy.

With NapNodes

On NapNodes the server is called napnodes, so its files are .cache/Server/napnodes.ini and napnodes_SandboxVars.lua, in “Files”. You don't need to open them: “Settings” reads them and shows every setting with a search box and its explanation, and each change saves itself, with no “Save” button. It applies when you restart with “Restart”, and the screen itself warns that some world settings only change in a new world.

If you'd rather edit the files by hand in “Files”, do it with the server “Offline” and make a copy in “Backups” first. To try it all without paying anything, the free Project Zomboid server has “Settings” with the same options, 6 GB and Workshop mods, no card. It switches off when nobody's on; for a long game, the 7-day pass keeps it on.

Frequently asked questions

Why do my servertest.ini changes get erased?

Almost always because it was edited with the server running: when it saves or shuts down, the server can write the file again with what it had in memory. Stop it, edit and start it again.

Why don't the zombies change even though I changed SandboxVars?

The starting population is only used when the world is created, and what's already generated doesn't change. Changes show in new areas; for the whole map, you need a new world.

Which settings file does my Project Zomboid server read?

The one with its name: a server called servertest reads servertest.ini and servertest_SandboxVars.lua. On NapNodes it's called napnodes and its files are in .cache/Server.

Does /changeoption get saved?

It changes the .ini option with the server running. To be sure it stays after a restart, check it's written in the .ini and, if not, put it there with the server stopped.

Do I have to restart for settings to apply?

Yes: both files are read at startup. Some game settings, on top of that, only count for what gets generated afterwards or in a new world.

Shall we set it up for you?

Project Zomboid servers from €12 a month, never oversold: your RAM is yours alone. And if you'd rather start without paying, there's a free Project Zomboid server, no card needed.

Not sure whether your server is online? Check it in a second with the Project Zomboid server status checker: players, version and password, free.

Keep reading

All Project Zomboid guides, sorted →