7 Days to Die 3.2 Is Now Stable: What Dedicated Server Admins Need to Know
7 Days to Die 3.2.0 is now officially Stable. The update replaces version 3.1 on the default public branch and includes several changes that directly affect dedicated servers, custom POIs, mods and multiplayer behaviour.
For server administrators, the most important changes concern custom POI metadata, screamers, sleepers, auto-turrets and several systems commonly modified by modlets.
The Fun Pimps has also announced a new development structure designed to deliver smaller updates more frequently, meaning server owners may need to keep a closer eye on compatibility between major releases.
7 Days to Die 3.2 becomes the new Stable version
Since August 26, 2026, version 3.2.0 has become the official Stable build of 7 Days to Die.
Servers configured to follow the default public branch will therefore move to 3.2 when they are updated.
The Fun Pimps also used the release to explain that a dedicated team is now working on smaller and more frequent updates, such as versions 3.1, 3.2 and future intermediate releases.
Version 4.0 is still being developed separately. For administrators, this new structure could mean more frequent updates to test against server mods and custom configurations.
Custom POIs can now send metadata from the server to clients
One of the most interesting additions in 3.2 for multiplayer communities concerns custom POIs and prefabs.
Servers can now provide connected clients with a minimal metadata package for custom POIs.
This should improve the way certain custom prefab information is handled in multiplayer and make server-side custom content easier to manage.
This is not automatic mod downloading. The patch notes specifically refer to metadata associated with custom POIs, not a system capable of automatically transferring every mod installed on the server.
Screamers can no longer trigger chains of additional screamers
Version 3.2 also changes one of the more chaotic situations that could occur around bases generating large amounts of Heat.
Screamers should no longer summon additional screamers.
The Fun Pimps modified the relevant groups inside entitygroups.xml, removing screamers from the groups used by scout screamers.
This prevents a single screamer from potentially triggering another screamer and creating an escalating chain of additional zombie spawns.
Modded server warning: if a modlet modifies or replaces entitygroups.xml, administrators should check it after updating. A mod may preserve the old behaviour or override the changes introduced by 3.2.
Sleeper spawning calculations have been optimized
The update also includes an optimization related to sleepers, the zombies pre-positioned inside buildings and POIs.
The Fun Pimps says visibility checks used during sleeper spawning have been optimized when players are located at long distances.
Administrators should not necessarily expect a dramatic performance increase from this change alone.
However, on larger multiplayer worlds where several players may be exploring different areas simultaneously, reducing unnecessary calculations is always useful for the server.
Auto-turrets may require attention after the update
Version 3.2 also changes several rules affecting auto-turrets.
No structural support
Auto-turrets no longer provide structural stability to player constructions.
No wall placement
Auto-turrets can no longer be placed directly on walls.
Existing bases that rely on wall-mounted turrets may therefore need to be adjusted.
Community server administrators may want to warn players after updating so that they can inspect their defensive setups before the next horde arrives.
Demolition Zombies also change in multiplayer
One small line in the bug fix section is particularly important for dedicated servers.
Demolition Zombies can now correctly explode after receiving damage from a client.
On a dedicated server, connected players are clients of the server, making this fix directly relevant to multiplayer combat.
Servers where players had become accustomed to Demolishers occasionally failing to trigger correctly may notice a difference during their first Blood Moon after moving to version 3.2.
Mod and prefab creators should check several technical changes
Version 3.2 includes several additional changes worth checking on servers using custom prefabs or modlets.
A new AllowDecorations property allows decorations generated inside POIs to be handled separately from the TraderArea setting.
The previous AllowTopSoilDecorations property is now obsolete and has been removed.
The update also fixes an issue involving the Loot Max Tier setting that could previously limit some user mods.
Another fix addresses situations where blocks could collapse when entities were present during certain chunk resets.
What should server admins check before updating to 3.2?
Version 3.2 does not require administrators to completely rebuild their servers, but a few precautions are recommended before updating a long-running or heavily modded world.
Back up the world
Create a backup of the world and server configuration before changing versions.
Check your mods
Verify mod and modlet compatibility, especially anything modifying entity groups or POIs.
Warn your players
Let players know about turret placement, screamer behaviour and Demolition Zombie changes.
Custom POIs should also be tested after updating, particularly on servers using large collections of community-made prefabs.
The official patch notes do not indicate that a new world is required for version 3.2.
A backup is still strongly recommended before updating, particularly on servers using custom POIs, mods or heavily modified configurations.
7 Days to Die servers may now see updates more often
The most important long-term change introduced alongside 3.2 may not actually be a gameplay feature.
By creating a team specifically responsible for smaller intermediate updates, The Fun Pimps is signalling that 7 Days to Die should receive fixes and improvements more regularly between major releases.
For players, that means issues can potentially be addressed more quickly.
For server administrators, it also means paying closer attention to patch notes and mod compatibility rather than waiting only for major updates such as version 4.0.
Version 3.2 is a good example: it may look like a relatively small release, but several of its changes directly affect how multiplayer servers behave.
Get ready to host your 7 Days to Die world with VeryGames
7 Days to Die hosting is coming soon to VeryGames, with game server management designed for persistent multiplayer worlds and communities.
Discover 7 Days to Die hosting →