Project Zomboid Reset Map: Fix Glitched Chunks Without Wiping Project Zomboid Reset Map Reset-type picker + checklists + full guide Filter Clear Guide # Project Zomboid Reset Map: Refresh Broken Chunks, Fix Mod Mishaps, Keep Your Survivor If your “new” Project Zomboid world still has your old base in one spot, or a map mod left the town scrambled, you usually don’t need to delete your survivor—you need to reset the *right* map data. Back up the save first, then either (1) delete the `map_###_###.bin` chunk files for the affected area to revert it to default, or (2) swap `map_ver.bin` to fix a bad map-mod roster. On multiplayer, delete chunk files in the **server** save (not the `_player` folder) and restart. Jump to [Quick-Start](#quick-start). ## Quick-Start ### Pick the reset you actually mean (90% of the confusion lives here) | What you mean by “reset map” | What changes | What stays | Risk level | | --- | --- | --- | --- | |  “This one area is wrong / looted / glitched” | That area’s world-state reverts (walls/loot/doors go back to default) | Your character, inventory, the rest of the world | High (you can delete your base) | |  “I removed/added a map mod and the world is scrambled” | The save’s map-mod roster/version reference is corrected | Your character and most of the save | Medium (still backup first) | |  “I only want to clear explored map / names / discovered buildings” | Your map knowledge changes (behavior can vary by build) | World state stays the same | Low–Medium | |  “Server needs a partial wipe, keep players” | Server world chunks reset in the wiped area | Player characters/accounts | High (easy to delete the wrong folder) | ### The shortest safe checklist 1.  **Back up the save** (copy the whole save folder somewhere else). Do not skip this. 2.  **Confirm what you’re resetting**: chunk/world-state vs map-mod roster vs map knowledge. 3.  **Do the smallest reset that solves the problem**: -  Chunk/world-state: delete the specific `map_###_###.bin` files for the affected area. -  Map-mod roster: replace `map_ver.bin` from a fresh save that has the correct map mods enabled. -  MP: do it in the server save folder, not `_player`. 4.  **Boot the game and verify** before you delete anything else. ## Before You Touch Anything: Make a Backup You Can Roll Back To Here’s the veteran-Zomboid truth: a “map reset” is one of the few fixes that can *quietly* delete dozens of hours of carpentry, loot sorting, and base decorating in a single moment. Backups are the seatbelt; you won’t miss it until the crash. ```text Info Card: What to back up - Singleplayer saves: .../Zomboid/Saves/<mode>/<save name>/ - Multiplayer server saves: .../Zomboid/Saves/Multiplayer/<servername>/ (Do NOT confuse this with any folder ending in "_player") ``` Example quick backups (edit the paths to match your save name): ```powershell # Windows (PowerShell) example: copy your save to Desktop with a date suffix $src = "$env:USERPROFILE\\Zomboid\\Saves\\Sandbox\\MySave" $dst = "$env:USERPROFILE\\Desktop\\MySave-backup-2026-01" Copy-Item -Recurse -Force $src $dst ``` ```bash # macOS/Linux example cp -a "$HOME/Zomboid/Saves/Sandbox/MySave" "$HOME/Desktop/MySave-backup-2026-01" ``` ## Reset Type 1: Refresh a Broken/Looted Area (Chunk Reset) This is the classic “why is my old base still here?” fix. When you delete the right `map_###_###.bin` files, that area’s world-state snaps back to its original, untouched version. If you knocked down walls, barricaded windows, moved furniture, or cleaned out every can of oats, those changes can vanish—because you’re telling the save, “forget what happened here.” ### Step-by-step (manual method) 1. **Close the game** (and stop the server, if applicable). 2. **Back up** the entire save folder. 3. **Open the save folder** and look for files named like `map_123_456.bin`. 4. **Delete only the files for the area you want to refresh**. 5. **Start the game and travel to the area** to force it to regenerate. If you’re not sure which `map_###_###.bin` matches the neighborhood you want to reset, don’t guess. ### How to figure out “which chunk is my base?” You have three practical options: -  **Use a helper tool** that lets you select an area and tells you which chunk files to remove. (This is the least error-prone approach.) -  **Use an online map to name the area** precisely before you delete anything. The [pzfans online minimap](https://pzfans.com/en/Studio_map_in_KY_with_built-in_minimap_online_map/) is handy for quickly identifying landmarks and planning the “blast radius.” -  **Reset a bigger area than you think you need** (safer than playing chunk roulette), but only if you’re okay with losing player-made changes in that whole region. ### “Can I reset *the whole world*?” Yes—by deleting *all* the `map_*.bin` files in that save. But that’s the nuclear option. It’s basically telling the save: “everywhere I’ve been, forget it.” If your goal is “make loot respawn in this one strip mall,” a whole-world wipe is like burning down your safehouse because you found a single roach. ## Reset Type 2: Fix a Wrong/Removed Map Mod (The `map_ver.bin` Roster Fix) If you changed map mods mid-save and suddenly your world looks like it was shuffled in a deck of cards—roads misaligned, buildings overlapping, invisible walls—you’re usually dealing with a mismatch between: - what your save thinks the map roster is, and - what mods you actually have enabled now. Players have reported a workable fix: generate a fresh save with the *correct…162 chars truncated…reate a new save** with the map mods you *intend* to use (the “correct” roster). 3. **Close the game.** 4. In the **new** save folder, copy `map_ver.bin`. 5. In the **broken** save folder, replace `map_ver.bin` with the copied one. 6. Launch the game and load the old save to see if the map aligns again. If the save is still busted after the roster fix, you might need a *chunk reset* (Reset Type 1) in the specific cells that were already generated with the wrong map roster. ## Reset Type 3: Reset Only Your Map Knowledge (Fog-of-War / Names / Discovered Buildings) Sometimes you don’t want the world to change—you just want your survivor to “forget” what they’ve charted. That’s a different kind of reset. One wrinkle: in some Build 42 patch notes, the “Forget map knowledge” behavior is called out as affecting map names/discovered buildings for certain cells—not just a simple fog-of-war wipe. Translation: treat it as a meaningful reset, not a cosmetic toggle. ### Practical advice before you hit “forget” - **Screenshot your important notes** (base grid, safe routes, generator houses). - **Back up the save** if you care about your cartography. - **Test on a copy** if you’re playing unstable builds and don’t know exactly what the button will wipe in your version. ## Multiplayer Server Reset: Don’t Touch `_player` If you’re hosting or admin’ing a multiplayer world, there’s one mistake that shows up again and again: Deleting/resetting files in the wrong place. Recent player-to-player advice emphasizes this point: if you’re trying to reset the **world**, do it in the server save directory (for example, `Zomboid/Saves/Multiplayer/<servername>`), and **do not** do it in a folder ending in `_player`. ### MP “partial wipe” checklist -  Stop the server cleanly. -  Back up the full server save folder. -  Delete the targeted `map_###_###.bin` files in the **server** save folder. -  Start the server and verify the region regenerated. -  Only then consider additional cleanup (mods, config changes, etc.). ## Build 42 Gotchas (Why Your Old Reset Tricks Might Feel “Wrong”) Build 42 has been moving fast, and players have noted that B42 save folder structure can differ from what older chunk cleaners/tools expect (for example, assumptions about `map`, `zpop`, and `chunkdata` folders may not line up). If your favorite reset tool suddenly can’t “see” the files it expects, that’s not necessarily user error—it can be version reality. Two big takeaways: 1. **Test resets on a copied save first.** Always. 2. **Keep an eye on version compatibility.** Some patch notes include explicit save-compatibility warnings—meaning a “map reset” won’t fix a save that the new build won’t load. ## Troubleshooting: When the Reset Didn’t “Take” - **“The area didn’t change.”** You probably deleted the wrong `map_###_###.bin` files (or none at all). Use a helper tool or widen the reset area. - **“My base vanished.”** That’s expected if your base was inside the reset region. Restore your backup. - **“The world is still scrambled after removing a map mod.”** Do the `map_ver.bin` roster fix first, then reset only the cells that were generated under the wrong roster. - **“MP players lost progress.”** You may have deleted something inside `_player` or otherwise targeted player data. Restore the backup and re-try the reset in the server save directory. - **“Tool X doesn’t work on B42.”** Assume it’s a version mismatch, not you. Use the backup-first workflow and fall back to manual, minimal deletes. ## Quick FAQ **Q: Will resetting the map respawn loot?** A: In the reset region, yes—because you’re reverting the cell/chunk back to its untouched state. But it also reverts *everything else* in that region. **Q: Can I reset only a single building?** A: Sometimes, depending on how the building spans chunk/cell boundaries. Practically, you reset the smallest area you can target safely. **Q: Is there a “one button” reset?** A: Not reliably across versions/mod setups. Zomboid’s strength is persistence; the tradeoff is that persistence sometimes requires file-level “surgery.” **Q: What’s the safest way to experiment?** A: Copy your save, try the reset on the copy, verify in-game, then repeat on the real save once you know exactly what it changes. ## The Veteran Take Think of your Zomboid save like a battered road atlas stuffed with receipts and handwritten notes. “Reset map” isn’t one action—it’s you deciding which pages you’re willing to tear out and reprint. Do the smallest reset that solves the problem, and you’ll keep the story of your survivor intact without erasing the neighborhood you built that story in. **Action Steps Recap:** Back up → choose the smallest reset type → delete/replace only what you intend → verify → only then commit. ## Patch-History (Collapsible) <details> <summary>Patch history (Build 42 era context)</summary> | Date | Change Note | Impact on early-game priorities | | --- | --- | --- | | 2024-12-17 | Build 42.0 Unstable released (major unstable baseline) | Treat long saves as “experimental”; backups matter more than loot routes. | | 2025-06-30 | 42.10 UNSTABLE released | Expect ongoing systems/UI changes; test your mod stack and save behavior after updates. | | 2025-09-25 | 42.12.0 UNSTABLE released (notes about “Forget map knowledge”) | If you rely on mapped names/buildings, snapshot your info before using any “forget” reset. | | 2025-12-11 | Unstable 42 MP released (includes save-compatibility warning) | Sometimes your priority shifts from “reset this area” to “start fresh on the new build.” | | 2025-12-20 | Build 42.13 Unstable released with MP | MP worlds benefit from rehearsed reset procedures (stop server → backup → minimal deletes). | </details> Related Articles Map Update Log Tools Zomboid Water Woes: Boil Without the Drama Zomboid Respawn Nightmares? Here’s How to Stop Them Zomboid Power Cuts? Grab These 36+ Generator Spawn Spots Zomboid Soft Resets: B41 Pitfalls & B42 Solutions