Soft Reset in Project Zomboid: Host Button, B41 Bugs, and Build 42 Limits
Build 42.19 Host Soft Reset · six confirmation effects · back up ResetID and ServerPlayerID
A soft reset refreshes a hosted world without deleting the whole map. In Build 42.19, the supported path is the Host → SOFT RESET button. That confirmation dialog lists what soft reset promises: keep buildings and constructions; clear container and ground items; remove corpses, zombies, and zombified players; clear blood; reset the game clock; reset building alarms.
map_t.bin, map_meta.bin, reanimated.bin, or zombie_*.bin is not the Host soft reset and is not the same action on Build 42.19.
Older -DSoftReset launch flags are also not part of the current Host Soft Reset path.
Both can leave a half-broken save or force new characters. Use a full save copy first, then prefer the Host button.
What soft reset does (Host confirmation)
On the main menu, open Host, select an existing hosted world that already has save data, and use SOFT RESET. The confirmation text in Build 42.19 lists these six effects:
| Effect listed by the game | Practical meaning | Source |
|---|---|---|
| Keeps buildings and constructions | Map structures and player-built work remain. Soft reset is not a full map regenerate. | Host confirmation |
| Removes items from containers and on the ground | World containers and floor piles are emptied. Character inventory is not listed here—plan storage before the reset. | Host confirmation |
| Removes corpses, zombies, and zombified players | Body piles and living zombie populations are cleared so the world can repopulate under current sandbox rules. | Host confirmation |
| Removes blood splatter | World blood marks are cleaned with the other world clutter. | Host confirmation |
| Resets the game clock | In-world time returns to the early calendar state after the reset finishes. | Host confirmation |
| Resets building alarms | Building alarm states return to their starting state after the reset. | Host confirmation |
The same dialog states the job can take several minutes. Treat only those six lines as Host Soft Reset behavior.
Expect to keep
- Buildings and constructions (listed by Host)
- The existing world folder identity (this is still the same save, not a brand-new map)
- Server config files unless you edit them yourself
Expect to lose
- Container and ground loot
- Corpses, zombies, and zombified players
- Blood, prior alarm state, and the previous game clock
Uncertain without your own test
- Whether every player can rejoin the same character
- Vehicle positions, keys, and fuel state
- Safehouse claims and faction/meta data
- Build 42 animal, basement, and other extended world systems
- Mod-written world data outside vanilla containers
Always do first
- Full copy of
Zomboid/Saves/Multiplayer/<server>/ - Matching files under
Zomboid/Server/(INI, sandbox, spawn regions) - Written backup of
ResetIDandServerPlayerID - Tell players offline time and what loot they will lose
Soft reset vs hard wipe vs restart
Normal restart
Stop and start the host or dedicated server. Nothing is wiped. Loot, zombies, constructions, and time continue from the last save.
Soft reset
Host SOFT RESET applies the six listed world refreshes and keeps buildings/constructions. It is maintenance on an existing world, not a new map generation.
Hard wipe / Delete World
Host also exposes Delete World and Delete Player. Delete World removes the hosted world entirely. Delete Player removes player data for that world so new characters are created while the world files remain. Neither is a soft reset.
Recommended Host procedure (Build 42.19)
This is the recommended procedure for current builds. For a shorter checklist, see the quick soft reset guide.
- Announce the maintenance window. Soft reset is not a live hot-reload; players should log off.
- Stop the host/server cleanly.
- Copy the entire multiplayer save folder and the matching
Serverconfig tree into a dated backup directory. - Open the server INI and write down the current
ResetIDandServerPlayerIDvalues. - Launch the client, open the main menu, and click Host.
- Select the world that already has save data. Soft Reset is only enabled when that world exists.
- Click SOFT RESET and read the confirmation list. Confirm only if those six outcomes match your plan.
- Wait for the soft-reset progress status to finish. The host often ends with a deliberate normal shutdown after completion.
- Start the world again through the normal Host or dedicated-server path. Do not immediately request another soft reset.
- Check on a controlled login: game clock, container loot, zombie presence, and whether existing characters can rejoin without forced recreation.
ResetID, ServerPlayerID, and character risk
Server options include ResetID and ServerPlayerID.
In-game tooltips describe them as the pair that ties soft-reset world identity to whether a client must create a new character, and they explicitly recommend backing the values up.
| Option | In-game meaning (summary) | What you should do |
|---|---|---|
ResetID |
Determines whether the server has undergone a soft reset. If this number matches the client state that requires recreation, the client must create a new character. Used with PlayerServerID. | Write it down before maintenance. Restore only after you understand the identity state you want, and retest on a copy first. |
ServerPlayerID |
Determines whether a character is from another server or single player. This value may be changed by soft resets. Matching client state can force a new character. Used with ResetID. | Back it up with ResetID. Do not promise “everyone keeps characters” until post-reset login checks succeed. |
Build 41 history: broken button and workarounds
Build 41 kept a Soft Reset control on Host screens for a long stretch of multiplayer life, but many admins reported the process failing mid-launch. Common symptoms included a stuck progress bar and a server stop during launch. Community documentation from the late B41 period also treated some soft-reset launch parameters as non-working on stable 41.78.x.
That history matters for two reasons only:
- It explains why older guides still push manual file deletion and custom launch flags.
- It is not the recommended procedure for current Build 42.19 Host soft reset.
Build 42 limits and migration
Soft reset works as a Host feature
Build 42.19 still exposes SOFT RESET on the Host options screen, with confirmation text, progress, and a finish state. Use the button and the six listed effects as what soft reset does today.
Soft reset is not a B41 → B42 upgrade
Soft reset keeps the existing world data model. Moving from Build 41 into Build 42 requires a fresh world for basements, animals, crafting changes, and other structural systems. Do not soft-reset a B41 save expecting B42 content to appear.
Build 42 also stores animal data, basements, and other systems beyond classic loot-and-zombie cleanup. Because the Host confirmation only lists the six effects above, treat every B42-only system as part of the full-save backup boundary: if something outside the listed effects is wrong after the reset, restore the whole tree rather than patching random files.
Single-player vs multiplayer
Hosted multiplayer / dedicated worlds
Soft reset is designed around hosted worlds. The Host UI button is the supported path for local/coop Host saves. Dedicated servers should still begin with a full offline backup, then either use the Host path on a controlled copy of that world or follow your host panel’s documented soft-reset control if it wraps the same process.
Solo sandbox
Classic single-player Solo saves do not expose the same Host Soft Reset workflow. Converting a Solo save into a multiplayer Host world is a structure change of its own and can affect character identity. If you only need loot refresh in Solo, sandbox loot respawn and admin/debug tools are usually safer than inventing a file-deletion soft reset.
High-risk methods that are not recommended
Older guides and host-panel folklore still circulate two shortcuts. Treat them as warnings only—not as alternatives to Host Soft Reset.
| Method | Why people used it | Status for Build 42.19 |
|---|---|---|
Host / panel -DSoftReset launch flag |
B41-era dedicated hosting guides used a one-shot launch argument when the Host button failed. | Not recommended. Use Host SOFT RESET. If a host panel still exposes a soft-reset checkbox, read that panel’s own docs and uncheck it after one use; do not treat a copy-pasted command line as safe for 42.19. |
Delete zombie_*.bin, map_t.bin, map_meta.bin, reanimated.bin |
Community approximation while the B41 button was broken. | Not the same as Host soft reset. Those files do not guarantee a complete loot wipe, utility reset, key reset, safehouse wipe, or clean character retention. Easy to over-delete or under-delete. Use only on disposable test copies, if at all. |
| Partial chunk restoration tricks | Admins tried to reset one town while restoring another town’s chunk files from backup. | Advanced and fragile. Outside what Host Soft Reset promises. If you need regional refresh, practice on backups and accept corruption risk. |
Mods, maps, and hosting panels
Mods
- Item mods usually only appear in containers that are freshly populated after the world accepts the mod’s loot tables.
- Soft reset can help restock emptied vanilla containers, but it does not automatically validate every mod’s custom world database.
- Removing a mod without a backup can leave orphaned items or broken references. Soft reset is not a guaranteed mod uninstaller.
- Vehicle-pack additions still depend on map population rules; soft reset does not advertise vehicle respawn.
Custom maps and hosting
- Map mods that add unvisited regions often do not need a soft reset for first discovery.
- Map mods that rewrite already-generated cells may not fully apply through soft reset alone.
- Host panels differ: some expose a soft-reset checkbox, some only offer full wipe folders or FTP file managers.
- If a panel only documents full wipe, do not invent a partial delete list. Use Host soft reset on a local copy, or ask the host what their control actually does.
Troubleshooting
Progress stuck / process dies mid-reset
Abort cleanly if the Host UI allows it, restore the full backup, and retry once on a copy. Large worlds can take minutes; that alone is not failure. Repeated failure after a clean backup restore means stop deleting files by hand and keep the broken attempt offline for comparison.
NormalTermination loop
One normal exit after soft reset is common. Immediate termination on every subsequent start means something is still launching in soft-reset mode or the save/config pair is invalid. Compare against the pre-reset backup instead of re-clicking Soft Reset.
Players forced to new characters
Check whether ResetID / ServerPlayerID changed from your written values.
Restore the full backup on a test copy first.
Only then decide whether identity values should be restored for the live community.
No zombies or empty loot after reset
Confirm sandbox respawn and loot settings still match what you expect. Soft reset clears current zombies and container items; it does not rewrite your sandbox choices. If the world stays empty with respawn enabled, restore the backup rather than deleting more files.
FAQ
Does soft reset delete player characters or skills?
Not as one of the six Host-listed effects.
Character retention still depends on identity IDs and how the world is restarted.
In-game tooltips warn that ResetID / ServerPlayerID can require a new character, so do not promise zero character impact without a post-reset login check.
Do I soft reset when updating from Build 41 to Build 42?
No. Soft reset is not a version migration tool. Start a fresh B42 world for B42 systems.
Is soft reset the same as loot respawn?
No. Sandbox loot respawn restocks over time under its own rules. Soft reset is a one-shot Host maintenance action that also clears zombies/corpses/blood, resets the clock, and resets alarms, while keeping buildings and constructions.
Does soft reset repair burnt houses or broken doors?
No. Kept constructions and map changes stay as they are. Soft reset is not a map regenerator.
Do player-built crates remain?
The Host prompt keeps constructions, so the crate object itself is expected to remain. Items inside containers are removed because container contents are explicitly wiped. Verify on your own backup if a specific furniture mod stores data outside normal containers.
Can I soft reset by deleting four bin files?
Not as a supported or equivalent procedure. That was a B41-era community workaround and can destroy more or less than Host Soft Reset. Use Host SOFT RESET on a backed-up world instead.
Quick checklist
- Full save + server config backup, including the whole Build 42 world tree.
- Write down
ResetIDandServerPlayerID. - Players offline → Host → SOFT RESET → confirm the six listed effects only.
- Accept a normal post-reset shutdown, then start the world normally once.
- Check loot, zombies, clock, and character login before inviting everyone back.
- Skip manual bin deletion and old launch flags unless you are deliberately testing a disposable clone.
Related server guides
Related Articles
