Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Playing with friends? Godlike.Host runs hosted Project Zomboid servers from 10 data-center locations, with free DDoS protection.
If a Project Zomboid dedicated server ignores an edited setting or restores the old value after a restart, the file usually was not the one the running process uses, the value belongs to a different configuration layer, the change was never reloaded, or the server is running under another Linux account. Confirm the active server name and data directory first, then edit the matching INI or SandboxVars file, apply the change with a restart or reloadoptions, and verify it with showoptions and one client.
Why Project Zomboid settings appear not to save
A dedicated server does not read one universal settings file. It selects a server profile, then loads several files from the Zomboid data directory and a persistent multiplayer save. The profile name, launch arguments, operating-system user, and the type of setting you changed all determine whether your edit has any effect.
Recommended Free Tools
- Wrong profile: the server may be running as
pizzawhile you editedservertest.ini. - Wrong layer: connection and server options are in the INI, while world rules such as loot and zombie speed are in
*_SandboxVars.lua. - Change not applied: most edits require a restart; INI edits can be made live only after the administrator runs
reloadoptions. - Different user or data directory: a Linux service,
sudolaunch, or-cachediroption can make the process read another Zomboid folder. - Existing world state: generated cells, rolled loot, and completed world events are stored in the multiplayer save and may not be rewritten by a later rules change.
Work through those causes in that order. It prevents the common mistake of repeatedly editing a file that the server never opens.
Stop the server and make a usable backup
Do not troubleshoot by editing a live world without a rollback copy. Stop the dedicated server through the same service, script, or console method normally used to start it, and wait until the process has exited before copying files.
#1 Best Overall
- UPDATED CLASSIC: Dive into Zombicide: 2nd Edition, the thrilling update to the classic zombie-slaying game. Experience enhanced gameplay and new challenges in the zombie apocalypse.
- COOPERATIVE SURVIVAL: Join forces as Survivors in a world overrun by zombies. Work together to navigate through missions, complete objectives, and fight for survival.
- ADRENALINE-POWERED ACTION: With each zombie kill, increase your Adrenaline Points. Gain strength and skills but attract more zombies with your actions – a double-edged sword.
- INTENSE MISSIONS: Face a series of challenging missions, each requiring strategic planning, teamwork, and bravery. Can you accomplish your objectives while fending off the undead?
- SURVIVE OR BECOME ZOMBIE PREY: The stakes are high - will you emerge as a triumphant survivor or fall victim to the relentless zombie hordes?
Windows locations
For the default servertest profile, PZwiki lists these files under the Windows user’s Zomboid data directory:
C:UsersYourUsernameZomboidServerservertest.iniC:UsersYourUsernameZomboidServerservertest_SandboxVars.luaC:UsersYourUsernameZomboidServerservertest_spawnpoints.luaC:UsersYourUsernameZomboidServerservertest_spawnregions.luaC:UsersYourUsernameZomboidSavesMultiplayerservertest(the multiplayer world directory)
Linux locations
Linux uses the analogous paths under the account that runs the server:
~/Zomboid/Server/servertest.ini~/Zomboid/Server/servertest_SandboxVars.lua~/Zomboid/Server/servertest_spawnpoints.lua~/Zomboid/Server/servertest_spawnregions.lua~/Zomboid/Saves/Multiplayer/servertest
Copy the INI, SandboxVars file, spawn files, and the complete multiplayer save to a dated backup location. Include the profile name in the backup folder so that similarly named test worlds cannot be confused later. If the server uses a name other than servertest, substitute that name in every path.
Confirm which server profile is actually active
The launch argument -servername NAME selects the profile. A server started with -servername pizza reads pizza.ini, pizza_SandboxVars.lua, the related spawn files, and the save directory named pizza. Editing servertest.ini in that situation is a valid edit to a file, but it is irrelevant to the running world.
- Find the exact command, service definition, or startup script that launches the dedicated server.
- Record the value following
-servername. If no custom name is supplied, the default profile is commonlyservertest. - Map that name to every file in the
Zomboid/Serverdirectory and to the matching directory inZomboid/Saves/Multiplayer. - Open the matching INI and SandboxVars file, not a similarly named profile left over from an earlier test.
| Launch profile | Files the process should load | Typical error |
|---|---|---|
servertest |
servertest.ini, servertest_SandboxVars.lua, and save folder servertest |
Editing a custom profile such as pizza instead |
pizza |
pizza.ini, pizza_SandboxVars.lua, and save folder pizza |
Changing the default servertest files |
Also inspect any -cachedir option and the service’s working environment. Those settings can redirect the effective Zomboid data directory even when the profile name is correct. If a service starts the server, the path in the service definition—not the path in an interactive shell—is the one that matters.
Edit the configuration layer that owns the setting
Project Zomboid separates server behavior from sandbox rules and from state already written into the world. Use this map before changing a value.
| What you want to change | File or location | What to expect |
|---|---|---|
| Password, public listing, ports, server behavior, or connection options | Active NAME.ini |
These are server-level options. The file must match -servername NAME. |
| Loot abundance, zombie speed, time progression, water shutoff, or PVP | Active NAME_SandboxVars.lua |
These are sandbox/world-rule values, not ordinary INI fields. |
| Spawn points or spawn regions | Active profile’s spawn files | Use the files carrying the same profile name as the launch argument. |
| Existing loot rolls, explored cells, or a water system that has already shut off | Zomboid/Saves/Multiplayer/NAME |
Persistent world state may survive a later rules edit. |
| Missing mods | WorkshopItems= and Mods= in the active INI |
Both fields need the intended mod set; populating only one is insufficient. |
INI settings
Open the active profile’s NAME.ini in a plain-text editor and change only the relevant key. Preserve the key name, equals sign, and value format. Save the file to the same profile directory. Do not assume that a file inside the game installation directory is the live server configuration; the dedicated server reads its profile under the Zomboid data directory.
SandboxVars settings
World rules live in NAME_SandboxVars.lua. Loot, zombie speed, time, water shutoff, and PVP are examples of values that belong here. A syntactically damaged Lua file can prevent the intended rules from loading, so make a backup before editing and change the smallest possible value rather than reformatting the entire file.
Persistent save state
The save directory contains the world after it has been generated and played. A later SandboxVars change does not necessarily regenerate cells or undo events that already happened. For example, loot that has already been rolled, cells that players have explored, or water that has already shut off may remain as they are. Treat a rules edit as a change to future generation or future behavior unless you have a separate, documented procedure for altering the save.
Apply the edit: restart or use reloadoptions
Saving a file in an editor does not automatically make every server option live. For a normal maintenance window, use a clean stop and restart:
- Stop the dedicated server and wait for the process to close.
- Back up the active INI, SandboxVars file, spawn files, and matching multiplayer save.
- Edit the file whose profile name and layer match the setting.
- Save it without changing the filename or extension.
- Start the server with the same profile name, data directory, and service account.
- Wait for startup to complete before connecting a player.
- Use an administrator account to verify the effective options, then test with one client.
PZwiki’s dedicated-server documentation states that changes can be saved to servertest.ini while the server is running; after saving, an administrator can run reloadoptions to make those INI changes live. This is an application step, not a replacement for selecting the correct profile. The command does not turn a SandboxVars edit into an already-regenerated world, and it cannot make an inactive profile relevant.
Use showoptions after the reload or restart to inspect the server’s effective options. If the displayed value is old, stop troubleshooting gameplay and return to profile, path, and user checks. If showoptions reports the new value but players see no difference, the setting may belong to SandboxVars or to persistent world state rather than the INI.
Check Linux account, home directory, and service context
On Linux, the same filename can exist in several users’ home directories. A Steam Community support reply specifically warns that launching with sudo can place the settings file in the sudo account, causing the process to read a different servertest.ini than the one you edited. Treat this as a concrete troubleshooting lead and verify the effective account instead of assuming it.
- Identify the user that owns the running server process.
- Run the server and edit its files under that same intended account.
- Check the account’s home directory and the resulting
~/Zomboidpath. - Inspect the launch service or script for
-cachedir, which can redirect the data directory. - Confirm that the service can read and write the active profile files and save directory.
If the server is managed by a service, an interactive login as your personal account may show one Zomboid directory while the service account uses another. Compare the service’s configured user, home, working directory, -servername, and -cachedir with the files you edited. Correct the launch context first; changing permissions randomly or repeatedly copying files between accounts can create a second, harder-to-diagnose profile split.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Know when a setting cannot rewrite an existing world
Some changes affect only content that has not yet been generated. The multiplayer save records persistent state, so changing a rule after the world has been explored may produce a result that looks like a failed save even though the new value is active.
Loot
Loot rolls that already occurred are part of the save. A new loot setting generally affects future generation rather than containers that players have already opened or cells that already contain generated contents.
Water and other timed world events
If the world has already reached a water shutoff event, editing the schedule later does not automatically restore the previous state. Verify the active SandboxVars value, then distinguish that value from the event already recorded in the save.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Explored cells and generated content
Cells that players have visited can retain generated terrain, objects, and distribution results. Test a changed generation rule in an appropriate ungenerated area or a separate test profile rather than judging it only from a heavily explored location.
Do not delete or replace the multiplayer save to force a rules change unless you deliberately intend to lose that world. The save backup made before editing is the recovery point if an experiment has an unwanted result.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Fix missing mods without confusing them with profile problems
When mods do not load, check the active profile’s INI rather than a global or inactive file. The configuration map identifies WorkshopItems= and Mods= as the two fields to inspect. Both need to describe the intended mod set. A populated Workshop list without the corresponding mod identifiers, or the reverse, can leave the server running without the expected content.
- Confirm the active
NAME.inifrom-servername. - Inspect both
WorkshopItems=andMods=in that file. - Save the corrected INI.
- Restart the server, or use
reloadoptionswhen the change is an INI option that the running server can reload. - Check the effective options and connect one client before changing another setting.
A mod problem and a settings-path problem can occur together, but opening network ports or reinstalling files will not make an inactive profile load.
Free tools Windows power users keep installed
One-click scans. No signup required.
Keep connectivity checks separate
PZwiki lists UDP 16261 and UDP 16262 as the default dedicated-server connection ports (2025). Verify forwarding and firewall rules separately from configuration persistence:
- UDP 16261: the default dedicated-server port.
- UDP 16262: the additional default port listed for dedicated-server connectivity.
Correct port forwarding can make a reachable server, but it cannot correct an edited profile, wrong SandboxVars layer, stale save state, or Linux user mismatch. First establish that the server is loading the intended values locally; then troubleshoot firewall and forwarding behavior.
Use the symptom to choose the next check
| Symptom | First check | Likely explanation | Next action |
|---|---|---|---|
| A password, listing, or port value reverts | Active NAME.ini and launch profile |
The wrong INI was edited or the edit was not reloaded | Match -servername, save the INI, restart or run reloadoptions, then use showoptions |
| Loot or zombie speed appears unchanged | Active NAME_SandboxVars.lua |
The value was placed in the INI or existing cells already contain generated state | Edit SandboxVars and test behavior in suitable ungenerated content |
| Settings work manually but not from a service | Service user, home, -cachedir, and working directory |
The service reads another Zomboid data directory | Run and edit under the same account and correct the service configuration |
| Only the default profile changes | -servername |
The server is using a custom profile | Edit the files carrying the custom name and matching save folder |
| Mods are missing | WorkshopItems= and Mods= in the active INI |
One field is incomplete or the wrong INI is being read | Populate both fields for the intended set and restart or reload |
| Players cannot connect | UDP 16261 and UDP 16262 forwarding/firewall | Connectivity is separate from whether settings saved | Check network rules after confirming the local profile and options |
Verify each change and roll back cleanly
Change one related group at a time. After each application:
- Reopen the profile file and confirm the saved value is still present.
- Use the administrator
showoptionscommand for options that the server exposes there. - Connect one client and observe the actual behavior relevant to the setting.
- Record the profile name, file changed, application method, and result before making another edit.
If the file value, showoptions output, and client behavior disagree, classify the setting first: INI, SandboxVars, or persistent save. Restore the dated backup if the server becomes unstable or an experiment damages the world. Restore the matching profile files and save together; mixing a new configuration with an old save can make the result difficult to interpret.
Version and evidence limits
PZwiki’s dedicated-server page was last modified on 2025-12-21, and the settings-reference material cited for this troubleshooting map was updated on 2026-09-30. Project Zomboid build-specific behavior can change, so confirm command names and startup conventions against the documentation for the build you run. The Linux sudo explanation comes from a single Steam Community support reply; use it as a lead, then verify the actual process owner and effective data path on your host. No reliable statistic establishes how often dedicated-server settings fail to save, so frequency claims are not warranted.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
