7 Days To Die Console Update: V3.0 "Dead Hot Summer" Is Stable Now (June 29). Here Is Everything in It.

7 Days to Die console update: V3.0 is live on Xbox and PlayStation (June 29)

The 7 Days to Die console update is V3.0 "Dead Hot Summer", and console players get it the same day as PC: stable launched June 29, 2026 on Xbox Series X|S and PlayStation 5 (with console crossplay), alongside the Steam stable launch. There is no separate, later console patch this cycle - console and PC shipped together. Everything in the feature list below (150 sandbox options, 11 presets, Item Magnitude loot, the Combine Station, Sign-Tech, 60+ new POIs, the UI overhaul) lands on console on day one. The previous console build was V2.6.

What's confirmed in V3.0 (from the June 11 release notes)

The sandbox layer - 150 options + 11 presets

There are 150 sandbox customization options, each with at least two values, spanning categories such as Player, Entity, World, Resources, Crafting, Traders, Tasks, and Miscellaneous. You tune them in-game, then everything compiles into a single sharable code (see SandboxCode below). The 11 official presets are:

• Undead Matinee - the default-style experience

• Madmole's Mayhem - the studio head's harder tuning

• Almost Creative Mode - near-sandbox building

• Bite Club - hardcore permadeath

• Legacy Survival - older-feel rules

• 7 Days Later - faster horde cadence

• Caveman's Life - stripped-down primitive run

• Dumpster Diver - scavenger economy

• Dying World - harsher resource scarcity

• Disaster Film - cinematic chaos tuning

• Chibi Mode - tiny zombies, big heads, low-gravity silliness

Item Magnitude - boosted loot

Looted weapons and tools can now roll Magnitude variants with boosted stats, flagged with an orange star and a teal percentage (for example, a pickaxe with bonus block damage). Mods gain progressive quality levels, with higher qualities giving stronger bonuses. Paired with this is an optional Repair & Degradation system: repair method can be set to no repair, repair kits only, combine repair, or both, and permanent degradation can take 5, 10, 15, 20, or 25% of an item's max durability per repair - a real "gear wears out" survival lever if you want it.

The Combine Station is the new workstation that pairs with Magnitude. You merge two similar items and the highest percentage stats move to the combined item regardless of quality, so you can incrementally push a weapon, tool, or mod toward its full potential instead of waiting on lucky loot. It also doubles as an alternative repair method - the "combine repair" option above - letting you top up a worn high-Magnitude item by merging it with a spare rather than spending repair kits.

Sign-Tech, new POIs, and more

• Sign-Tech - a full POI signage overhaul adding thousands of in-world signs with canvas and decal variants, supporting text, shapes, color picking, and layer warping.

• 60+ new POIs - bunkers, factories, farms and more (around ten named, mostly Tier 4 with one Tier 5). Players have already spotted a "Regional Paper Company" location modeled on The Office's Dunder Mifflin building.

• M60 turret, a substantial UI (XUi) overhaul, a redesigned main menu, and a customizable crosshair round out the combat and interface changes.

SandboxCode - the migration every server admin must do

This is the breaking change. More than two dozen legacy serverconfig.xml properties (GameDifficulty, XPMultiplier, BloodMoonFrequency and friends) are removed in favor of a single SandboxCode property: you configure the sandbox in-game, copy the generated code, and paste it as that one value. Existing V2.6 saves carry forward, but your old per-property config will not - budget time for this before you update a live server to 3.0. We walk through it in the SandboxCode server guide, and you can build, encode and decode the value right in your browser - no need to launch the game just to produce a code - with our 7 Days to Die SandboxCode generator. Migrating an existing V2.6 server? Paste your old serverconfig.xml into the free 2.6 → 3.0 migration doctor - it shows, property by property, what still works, what moved into the SandboxCode (and which sandbox option to set), what is dead, and hands back a cleaned 3.0-ready config.

What is NOT in 3.0

Set expectations with your players up front:

• No bandits. The long-awaited human enemies are still in active development as a separate work-stream and did not make 3.0. This remains the update's most-cited disappointment - PCGamesN's verdict was that 3.0 "puts complete control in your hands" but "bandits are still nowhere to be seen." About the viral clip: a streamer was filmed fighting bandits during streamer weekend and "Bandits Found in 3.0" became the community's top talking point - but that was a misdistributed internal build sent by mistake, not the public release. The bandits you can actually opt into are still none, and there is no committed version for them. For where bandits stand for the next major, see V4.0: what we know.

• No story mode.

• No "learn by doing" toggle. Despite being a common request, the older progression mechanic is not a sandbox option.

• Overhaul mods need recertification. Big overhauls (Darkness Falls, Undead Legacy, Ravenhearst) and many modlets will not run on 3.0 until their authors update them for the SandboxCode migration, Sign-Tech, and the UI overhaul. If your community depends on one, keep it on V2.6 until that mod is certified for 3.0.

Community reaction from the streamer weekend was broadly positive on the depth but split on scope - a sentiment captured by one streamer's take that the additions are "cool, but not enough to call it a 3.0," with the roadmap running about a year behind. The sandbox layer is a big replayability win; whether it earns the major-version number is the live debate, with some players arguing it should have shipped as a 2.7 point release. Worth the backdrop: V2.0 was the worst-received update in recent memory (player drop-off and Steam review-bombing), so 3.0's player-agency focus reads partly as a course-correction - and that correction is showing up in the numbers: the game has climbed back to "Mostly Positive" over the last 30 days on Steam (around 79% of ~1,300 recent reviews positive) against a "Very Positive" lifetime score, per Steambase. Post-release, the loudest community threads are the missing bandits, the sandbox sliders, and the new POIs - not the bugs - and the strongest engagement is on TikTok and YouTube rather than X. There is also a roadmap reason for optimism on pace: V3.0 and V4.0 are being developed concurrently on separate teams following Behaviour Interactive's 2026 acquisition of The Fun Pimps, with V4.0 targeted later this year - see V4.0: what we actually know.

A week into stable, the post-launch threads show a clear pattern: players are using the sandbox layer to put the old game back. The most-upvoted feature rundown on r/7daystodie since stable (757 upvotes) has as its top comment "half of the 'new' features are a regression of previous ones" - and the replies treat that as the good news, trading favorite settings like quest counts restored to 7 per tier and trader zones made claimable again. The 150 options are being embraced precisely because they un-ship contested balance decisions from the 2.x era. The Fun Pimps, meanwhile, have opened an official V3.0 Dead Hot Summer player survey on Steam - the same feedback loop that produced the community-requested 2.2 and 2.3 changes - so expect the V3.1+ point releases to be shaped by its results. And while the big overhauls recertify, the first 3.0-native mods are already appearing: a Create-style automation mod ("Overengineered") shipped a working alpha within the first week of stable.

Known issues at launch

V3.0 just went stable, and some rough edges from the experimental cycle may carry into the early stable build. The Fun Pimps' tracked issues during the experimental cycle included:

• Abundance categories not working well for single items, books, and magazines - this touches the new loot-abundance sandbox sliders, so loot-scarcity rulesets may not behave exactly as set yet.

• Some sandbox selections do not show up localized.

• The sandbox crafting-yield option resetting its amount when you close the inventory.

• Trader hours: the "BM Closed" setting closing the trader during the morning of Blood Moon day.

• Switching between an item's stat view and its description not updating.

None of these are save-destroying, and TFP shipped hotfixes through the experimental cycle into the June 29 stable - check the latest patch notes for what is already resolved. If you are tuning a loot-scarcity ruleset, the abundance-category behavior is the one to verify.

Beyond TFP's official list, players on the Steam bug-report forums flagged a few more rough edges during the experimental build: zombies pathing or digging through built defenses to reach players, errors thrown in the in-game console log when upgrading wood storage crates to iron or steel (every time items are added or removed), and intermittent 5-15 second FPS dips, with the occasional crash or controller-recognition hiccup on console. These are community-reported rather than on the confirmed list, none are save-destroying, and they are exactly the class of issue the hotfixes target - check the latest stable patch notes before you flip a production server to 3.0.

V3.0.1 - now stable (July 13, 2026)

V3.0.1 is now the stable build. The Fun Pimps shipped it to the experimental branch on July 9 and promoted it to the default branch on July 13, 2026 - the first fix batch since V3.0.0 stable (changes are measured against V3.0.0 b259). Steam updates you automatically; no opt-in needed anymore. Server owners: update the server and all clients together - a version mismatch is the usual cause of "my server vanished from the list" reports after a patch day. Saves carry over.

Several fixes matter directly for dedicated-server admins:

• PVP damage could leak through "no killing" settings under some conditions - now fixed. If you run a PvE ruleset, this is the one to care about.

• Item max degradation could be reset by restarting the game and rejoining a server - that exploit is now closed.

• Airdrops were not dropping at night when the sandbox airdrop setting was "night" - fixed, so air-drop timing behaves as configured.

• Dedicated-client fixes: biome zombie kills with Celebrate now count toward the Kill Challenge, and a console error when a client killed with Celebrate on is resolved.

• Multiplayer stability: a null-reference error when receiving NetPackageLockRequest (a join/lock network packet) is fixed.

• Cannot pick up user-placed items at a claimed trader - fixed.

The rest of the batch is client/cosmetic: Sign-Tech error handling plus an ArgumentNullException on join, Beachwear-cosmetic and outfits-missing-arms fixes, zombie loot-bag naming and missing inventory buttons, shape-menu and custom-preset-summary UI bugs, an undamageable door frame in downtown_filler_30, RWG-preview and Prefab/POI-editor fixes, and hiding the World Editor on consoles. Now that the batch is stable, the remaining caution is just the usual one: back up your world before patch day, and update server and clients in one sitting.

Two patch-day gotchas players are reporting (both avoidable)

The first days on 3.0.1 stable surfaced two loss patterns worth a warning before you flip a live server:

• Empty workstations before updating. The most-reported 3.0.0 → 3.0.1 loss is anything sitting in a crafting queue or workstation when the update lands - forges, cement mixers, workbenches, including input and fuel slots (some players also report placed items, and in one case a loaded gyrocopter, going with them). Not everyone is affected, but having everyone collect queues and inventories before the restart costs a minute and removes the risk entirely.

• Do not roll back to 3.0.0 after playing on 3.0.1. A save written under the newer build does not read cleanly under the older one - players who reverted report their character dropping to level 1 with game stage reset. If you must roll back, restore a pre-update backup of the whole save folder together with the older version; rolling back the game alone is what causes the reset. On console this is not an option at all - Xbox and PlayStation force updates and give you no way to install an older build, so the only real protection is a cloud backup before patch day. The most-shared cautionary story this month was exactly this: a player skipped ~two months, returned after a couple of updates, and the console save was corrupt with no way back.

• Crash-loop right after updating? Empty the crafting queue. Some players report a NullReferenceException in TileEntityWorkstation.HandleRecipeQueue immediately after 3.0.0 → 3.0.1: the in-game console auto-opens every tick and steals input so you cannot move. The cause is a workstation whose crafting queue survived the update in a broken state; clearing that queue fixes it with no reinstall and no wiped world. If the popups block movement, install a "No Console On Error" mod first, then empty the queue. This is the same queue-corruption class as the loss above, escalated to a hard crash.

Watch it: dev stream and first-look coverage

The June 10-14 window produced a wave of footage. A few worth your time:

• The BIGGEST Update of the Year is HERE! - 7 Days to Die 3.0 Review (Guns, Nerds, and Steel) - the most-watched early review.

• Everything about 3.0 - 7 Days to Die You need to know! (Vedui42) - a tight feature rundown.

• 7 Days To Die 3.0 UPDATE - Here's What's Coming! - pre-release overview.

• Update 3.0 Streamer Weekend - Building at Bedrock (Guns, Nerds, and Steel) - hands-on streamer-weekend gameplay.

The June 12-14 streamer weekend pulled in 500+ creators across English, German, Spanish, Polish, Dutch and Japanese channels, so there is deep first-look coverage in most languages on Twitch and YouTube right now.

What server admins should do now

V3.0 is stable, so you can update production - but do it deliberately:

1. Back up your world first. The 7 Days to Die dedicated server save file locations guide shows exactly where saves live on Linux, Windows, and console so you can copy them before you update.

2. Do the SandboxCode migration before you start the server. Two dozen legacy serverconfig.xml properties are gone - build your ruleset and generate the code with our SandboxCode generator (no need to launch the game), then paste it as the single SandboxCode value. Full walkthrough in the SandboxCode server guide. Coming from a live 2.6 config? The 2.6 → 3.0 migration doctor converts your existing serverconfig.xml property by property.

3. Plan a fresh world. V3.0 changes world generation; players historically reset on RWG-touching updates. Generate a clean 3.0-ready world with xegen.

4. Audit your mods before you flip. Sign-Tech, Item Magnitude, the UI overhaul, and the serverconfig migration mean modlets and overhauls (Darkness Falls, Undead Legacy, Ravenhearst) need recertification. Check the 2026 Mod Status Tracker for what is updated for the current line - and if an overhaul you depend on is not 3.0-ready, stay on V2.6 until it is.

5. Test on a throwaway server first. Comparing 7 Days to Die hosting plans lets you stand up a 3.0 test world, learn the new sandbox UI, and confirm your SandboxCode and mods before you touch your main community.

Frequently asked

Is 7 Days to Die V3.0 out?

Yes - V3.0 "Dead Hot Summer" is stable and live on Steam now (released June 29, 2026), and it is the default branch, so there is no opt-in needed. It launched the same day on Xbox Series X|S and PlayStation 5 with crossplay. The experimental branch had been available since June 15; the stable build is what you get on a normal install today.

What is the difference between "Dead Hot Summer" and "Sandbox Siege"?

Same update. "Dead Hot Summer" is the final, official name revealed with the June 11 release notes; "Sandbox Siege" was the dev-diary working title used during development.

Will V3.0 have bandits?

No. Bandits remain in active development as a separate work-stream and are not in V3.0. There is no committed version for them yet - V4.0 is the most likely future home but has not been promised. See where bandits stand for V4.0.

Is V3.0 a paid expansion or DLC?

There is no statement from The Fun Pimps that V3.0 is paid. The historical pattern for 7 Days to Die has been free updates rather than paid DLC.

Does the Behaviour Interactive acquisition affect V3.0?

Behaviour Interactive acquired The Fun Pimps in March 2026 (announced March 24). The 3.0 work-stream shipped on schedule; The Fun Pimps continue to lead all 7 Days to Die development, with Behaviour providing additional production capacity.

What's the current stable version of 7 Days to Die?

V3.1.0 "Henpocalypse" (July 27, 2026) is the current stable build, live on PC, PlayStation and Xbox - see the full V3.1.0 breakdown. It is a content update on top of this page's V3.0 line; everything below still applies. The previous stable was V3.0.1 (July 13, 2026), the first fix batch on V3.0 "Dead Hot Summer" (stable June 29, 2026). Before that, V2.6 (April 2026) remains the safe fallback if a mod or overhaul you need has not yet been recertified.

What comes after 3.0?

V3.1.0 "Henpocalypse" already shipped, going stable on July 27, 2026 with chicken farming, the Chicken Coop workstation and ten new sandbox options - read the V3.1.0 breakdown. Beyond that, V4.0 and V4.1+ remain on the roadmap, with V4.0 in concurrent development on a separate team. V3.0 is one major release inside a multi-version plan, not the endgame.

Related

• V3.1 Henpocalypse - the current stable, and why an old 3.0 preset code can quietly apply different settings on it

• V2.6 Stable patch notes - the previous stable build and the fallback while overhauls recertify

• V2.5 Survival Revival update - context on the prior major update

• V3.0 Dead Hot Summer release-notes breakdown - the full feature deep-dive

• V3.0 new POIs - the 60+ locations, bunkers and factories

• SandboxCode server guide - the serverconfig.xml migration step-by-step

• 7 Days to Die SandboxCode generator - build, encode and decode your V3.0 SandboxCode in the browser

• 7 Days to Die Mod Launcher - install Darkness Falls, Undead Legacy, Ravenhearst on V2.6 while overhauls recertify for 3.0

• 7 Days to Die Roadmap 2026 - the broader release-watch beyond V3.0

• 7 Days to Die crossplay setup guide - PC + PS5 + Xbox on one server (still vanilla + EAC in V3.0)