7 Days to Die 3.2 Update: What Changed for Servers (and 3.1)

The 7 Days to Die 3.2 update went stable on 26 August 2026, per The Fun Pimps' Steam post. It adds horn opened trader doors, a reworked Combine Station and many fixes. It follows V3.1 "Henpocalypse" (stable 27 July 2026), which split density and respawn sandbox options and can invalidate old sandbox codes, so server admins should recheck theirs.

What is the current 7 Days to Die version?

As of 3 October 2026, the default public (stable) branch is V3.2.0. V3.3 is on the latest_experimental branch for testing, covered in our V3.3 experimental guide. Here is how the V3 line has rolled out on Steam:

Dates come from the official announcements for V3.0, V3.0.1, V3.1 and V3.2. PS5 and Xbox Series X|S players are on the same V3 line as PC and can crossplay on servers that allow it.

What changed in 7 Days to Die 3.2?

V3.2 is a smaller quality of life release. The Fun Pimps say a dedicated team now ships these point updates more often, separately from the team working on V4.0.

• Honk at traders. Using a vehicle horn near a trader opens its outer doors. An on screen hint tells you when you are close enough.
• Combine Station rework. The UI now previews the result and its final stats, a plus marks combined items, and you press a button to combine.
• Auto turrets. They no longer support stability and can no longer be placed on walls. Check bases that relied on wall turrets.
• Screamers. Screamer spawns were removed from screamer scout groups in entitygroups.xml, so screamers no longer call more screamers.
• Cotton. Junk loot gives cotton when Crop Yield is set to none, and general traders can stock it.
• Custom POIs. The server now pushes a minimal metadata package for custom POIs to clients.

Server relevant fixes include trader progression getting stuck, demolition zombies not exploding from client damage, blocks collapsing during chunk resets, the "Failed to search EOS servers" popup, Loot Max Tier clamping user mods, and a player gear texture using too much memory.

What changed in V3.1 Henpocalypse?

V3.1 added chicken farming: catch chickens, carry them home and keep them in a Chicken Coop workstation for eggs and feathers. Coops take three tool slots (Brooding Lamp, Chicken Run, Nesting Box) and chickens eat Rekt's Chicken Feed made from corn and rotting flesh. There are four new chicken recipes and a Chicken Stress event that can turn a failed carry into an ambush.

It also added sandbox options that matter for every server:

V3.1 also fixed corrupted saves when converting copies of saves to V3.0, the getsandboxoptions console command not showing results to clients, and game invites not working.

Do I need a new sandbox code after V3.1?

Possibly, yes. The V3.1 notes say density and respawn options were split into day and night settings, so you should "check your preset codes to make sure they are still valid. Invalid codes may default some or all settings." The official presets were updated, but a code you made in V3.0 may not be.

To check and fix it:

1. In the game, open Sandbox Options on the new game screen and paste your old code.
2. Check every page, especially density and respawn, and set the day and night values you want.
3. Copy the new code.
4. Put it in the SandboxCode property in serverconfig.xml, or the Sandbox code setting on our panel, and restart.
5. In the server console, run getsandboxoptions to confirm the rules loaded.

If you never set a code, the server uses the Adventurer equivalent, AAAJABJACJADJARFBNC, which The Fun Pimps published in the V3.0 notes. For a walk through of every V3 setting, see how to change 7 Days to Die server settings.

What this means for your server

• Update the server and every player together. V3.1's stable post told dedicated server players to select the Default Public Version branch if they could not connect. A mixed group gets a version mismatch, fixed in our version mismatch guide.
• Recheck your sandbox code as above. A silently defaulted code is the most common "why are there so many zombies at night" complaint after V3.1.
• Check turret builds. Wall mounted auto turrets are gone in V3.2.
• Back up first. Both updates are save compatible according to the notes, but a backup costs nothing.
• Mods: XML modlets usually survive point releases. Overhauls that ship DLL code often need an update, so keep them on the branch they support.

Is 7 Days to Die V4.0 coming?

Yes, but there is no date. The V3.2 post says work on V4.0 "continues in parallel and is moving along well." Treat any V4.0 release date you see as a guess until The Fun Pimps announce one. Since March 2026 the studio has been part of Behaviour Interactive, which the developers said lets them grow the team while still leading development.

Updating on GamezServers

Our 7 Days to Die servers update themselves on every restart, so a restart after a stable patch is all it takes. Press Backup first, restart, then paste your rechecked sandbox code in Sandbox code if it changed. If you run an overhaul pinned to an older branch, leave Game version set to that branch until the mod updates. See plans on 7 Days to Die server hosting.

FAQ

When did the 7 Days to Die 3.2 update come out?

V3.2.0 went stable on Steam on 26 August 2026, after an experimental build on 19 August 2026.

What is the Henpocalypse update?

Henpocalypse is V3.1, released to stable on 27 July 2026. It added chicken catching, the Chicken Coop workstation, chicken recipes and new sandbox options such as Infection Chance and day and night density.

Why did my server settings reset after V3.1?

V3.1 split density and respawn sandbox options into day and night values, and The Fun Pimps warned that old codes may be invalid and fall back to defaults. Rebuild the code in Sandbox Options and paste it again.

Can auto turrets go on walls in 3.2?

No. V3.2 removed wall placement for auto turrets and they no longer provide stability support.

What is the default 7 Days to Die sandbox code?

AAAJABJACJADJARFBNC is the code The Fun Pimps published as the equivalent of the old Adventurer difficulty. A server with no SandboxCode set uses those defaults.