Updates and compatibility

Check your build before following an old map or guide

Separate map coverage, game mechanics, mods, and save compatibility so an old route does not become a new problem.

Published · Updated

Identify what you are actually playing

Record the version shown by the game and, for multiplayer, the server version and required mods. Build numbers matter for map revisions, traits, crafting, loot, and interfaces. The newest article in a search result may describe a different branch from your save.

This atlas uses the map data distributed with this project. Town coordinates and building categories describe that dataset. They are not a live view of your save, and they cannot reveal current zombie positions, looted containers, or every modded addition.

Use the right source for the question

  • For a new release or branch change, read The Indie Stone's official news and build-status page.
  • For a mechanic, consult the relevant PZwiki page and check its version notes.
  • For a recipe or character requirement, inspect the interaction in your installed game.
  • For a building you plan to enter, use the atlas to scout the area and verify the final approach in the world.

Protect a long-running save before changes

Back up the relevant save and server configuration before changing branches, removing mods, or installing a significant update. Stop the game or server before copying active save data. Keep the original backup separate from the copy you use to test.

Check mod compatibility and the developer's migration notes. Do not assume that a save can move backward to an older build or that disabling a content mod will remove its effects cleanly.

Treat version claims as dated information

These guides favor durable planning advice and identify the sources for mechanics. They do not label a release as the latest indefinitely or promise a particular loot item at a coordinate.

If a location or instruction differs in your game, include the game version, coordinates, and relevant mods when emailing feedback. That makes a report actionable without collecting a player account or a save file automatically.

References

Plan your next step

Multiplayer

Coordinate a co-op run and its sandbox rules

Agree on the world settings, meeting point, shared supplies, and recovery plan before people scatter across the map.

Explore
Character builds

Choose a character for the run you want

Compare useful occupations and concrete trait tradeoffs, then match the character to an early route and a longer-term role.

Explore
Items and exploration

Plan loot routes around a specific need

Turn a map full of buildings into a short trip with one objective, a fallback, and a clear return route.

Explore