V3.0.1 Stable

Hated

Hated

Fun Pimps Staff
V3.0.1 wide banner.jpg
Hello Survivors!

V3.0.1 is now Stable with fixes for several reported bugs.

The 7 Days to Die team would like your feedback in a Player Satisfaction survey.

We encourage you to be as honest as possible in letting us know how you feel about the game in general and Version 3.0 in particular. The information and answers provided are anonymous, not shared with any third-party, and will not be used for purposes other than survey analysis.

Access the survey here: https://www.surveymonkey.com/r/NZW9KHZ



Here’s what changed since V3.0.0 b259:

Changed

  • Sign Tech error handling improvements
Fixed

  • Several issues related to the Beachwear Cosmetic
  • Several male and female outfits missing arms
  • An issue in the Sign Tech system that could cause ArgumentNullException errors when joining a game
  • Item max degradation can be reset by restarting game and rejoining a server
  • Zombie loot bag name and missing inventory action buttons
  • Dedi client Biome zombie kills with Celebrate do not count towards Kill Challenge
  • Error in console when a client kills with celebrate turned on
  • Players can take PVP damage with no killing settings under some conditions
  • Cannot pick up user-placed items at claimed trader
  • Airdrops not dropping at night when sandbox setting is set to “night”
  • Splash screen message can be seen behind main menu load
  • Localized text overlapping on player screen
  • Typing s while searching in shape menu can unintendedly favorite a shape
  • Unsaved Custom Preset Summary does not always update last changed item
  • Door frame in downtown_filler_30 cannot be damaged
  • Changing RWG preview quality after returning to the screen causes an error
  • Prefab Editor part name in POI marker editor is overlapping
  • World Editor was visible on consoles
  • NRE when receiving NetPackageLockRequest
 
Last edited:
This destroyed our dedicated server, tons of spam about files in the Saves/(World Name)/Region folder.

However, it's not a new 3.x world, so it's possible that is the cause. So not the biggest priority, just trying to report what I saw.
 

Attachments

  • Screenshot 2026-07-13 162419.png
    Screenshot 2026-07-13 162419.png
    10.2 KB · Views: 15
szalkerous said:
This destroyed our dedicated server, tons of spam about files in the Saves/(World Name)/Region folder.

However, it's not a new 3.x world, so it's possible that is the cause. So not the biggest priority, just trying to report what I saw.
Click to expand...
That's normally caused by a corrupted region file from a bad save, though it's possibly related to the update. This update seems to have some problems for me as well, though not with regions. If you have a backup of your game on the server that you could test, try loading into that backup to see if you have the same problem just to see if it was a bad save versus a problem with the update.

Also, it's a good idea to post bugs in the Bugs forum so it doesn't get missed by the devs.
 
szalkerous said:
This destroyed our dedicated server, tons of spam about files in the Saves/(World Name)/Region folder.

However, it's not a new 3.x world, so it's possible that is the cause. So not the biggest priority, just trying to report what I saw.
Click to expand...
Those are usually handled by deleting the regions files that are affected and replacing them with a copy from a working backup (if you have one available). You should make a post in Bug Reports and upload your server log since this occurred right after an update.
Post automatically merged:

Riamus said:
That's normally caused by a corrupted region file from a bad save, though it's possibly related to the update. This update seems to have some problems for me as well, though not with regions. If you have a backup of your game on the server that you could test, try loading into that backup to see if you have the same problem just to see if it was a bad save versus a problem with the update.

Also, it's a good idea to post bugs in the Bugs forum so it doesn't get missed by the devs.
Click to expand...
Ditto 😋
 
LittleNightma said:
Those are usually handled by deleting the regions files that are affected and replacing them with a copy from a working backup (if you have one available). You should make a post in Bug Reports and upload your server log since this occurred right after an update.
Post automatically merged:


Ditto 😋
Click to expand...

Yeah I normally would do that, but since it was on an old version world (whatever was just before the 3.0 drop), and frankly the server settings changes mucked a lot of stuff up and generating the "magic string" they implemented requires a game client, we might take a break from 7 days.

The server executable itself was experiencing a lot of memory leak issue even before 3.0 where it would slowly blow up to consume all 64GB of server ram over time, and constant lockups requiring server restarts. This is with a max of 6 concurrent users online at a time on very powerful hardware playing vanilla, no mods. I think it's better to let TFP figure this stuff out for now and check back in a couple months. :)

Thanks for the responses though!
 
szalkerous said:
Yeah I normally would do that, but since it was on an old version world (whatever was just before the 3.0 drop), and frankly the server settings changes mucked a lot of stuff up and generating the "magic string" they implemented requires a game client, we might take a break from 7 days.

The server executable itself was experiencing a lot of memory leak issue even before 3.0 where it would slowly blow up to consume all 64GB of server ram over time, and constant lockups requiring server restarts. This is with a max of 6 concurrent users online at a time on very powerful hardware playing vanilla, no mods. I think it's better to let TFP figure this stuff out for now and check back in a couple months. :)

Thanks for the responses though!
Click to expand...
Servers generally do need regular restarts with the game, so that's normal and probably won't change too much even when the game is complete, though perhaps not quite as often.

As far as the sandbox code, it would not be too hard to figure out how they create the code and to make a code generator utility that can be used outside of the game. Not something I really want to do since it wouldn't benefit me, but I'm sure someone will probably create one pretty soon.
 
szalkerous said:
Yeah I normally would do that, but since it was on an old version world (whatever was just before the 3.0 drop), and frankly the server settings changes mucked a lot of stuff up and generating the "magic string" they implemented requires a game client, we might take a break from 7 days.

The server executable itself was experiencing a lot of memory leak issue even before 3.0 where it would slowly blow up to consume all 64GB of server ram over time, and constant lockups requiring server restarts. This is with a max of 6 concurrent users online at a time on very powerful hardware playing vanilla, no mods. I think it's better to let TFP figure this stuff out for now and check back in a couple months. :)

Thanks for the responses though!
Click to expand...
There is generator you can use for the sandbox settings: https://hosthavoc.com/tools/7-days-to-die/sandbox-code-generator

I still suggest you make a bug report so TFP can be aware. Sorry about the rough time you're having :(
 
szalkerous said:
This destroyed our dedicated server, tons of spam about files in the Saves/(World Name)/Region folder.

However, it's not a new 3.x world, so it's possible that is the cause. So not the biggest priority, just trying to report what I saw.
Click to expand...
i had the same issue with 3.0.1 exp, which people assure is the same as this, so i rolled it back to 3.0.0 stable. it boils down to changes made that affeected mods in my case. i wont update to 3.0.1 til all my mods have been updated to address the changes.
 
You must log in or register to reply here.
Back
Top