7 Days To Die Dev Tracker

The game has to allocate the world storage estimate up front due to how the console file systems work. The size is based on the Chunk Persistence setting. Lower the value to use less save space. You can also archive worlds which converts it to the basic files without the padding, so it is much smaller. It is very fast as these consoles have SSD storage.

That does not sound like the same issue with empty storage chests as the only thing changes with that bug is the loss of what was inside the chests. That sounds like chunks being reset. Chunks reset based on the Chunk Persistence setting unless there is a bed roll, land claim or players being in the area more often than the timer. Did you have any bedrolls or land claims near them? Did you place bed rolls in another area (there can be only one active)? What is persistence set to? Were both of you away from the area for an extended amount of time?

Should be fixed.

We have spent many hours looking at this and have yet to determine why it happens on Xbox. PC/Mac/Linux and PS5 seem fine. Consoles have profanity filter code as required by MS/Sony that adjusts the text. XBox does it very differently from PS5. I think it is a timing issue with tile read/write vs profanity threads, but have yet to see it fail for me. If the name is blank, then no filtering, so if the bug does not happen in that case, then we know it is the filter, else it is something with the read/write code.

Yes, we have cross play working in testing. Due to the additional time required for testing and fixes and getting the required permissions from MS and Sony, it was delayed until after the 1.0 release.

I have heard of no plans for new weapons or ammo or books, but it is possible. No plans for fishing, but someday I could see the game or a sequel having some water based creatures. Paid DLC has been talked about, but nothing specific that I know of yet.

Correct. The current roadmap for biome progression, bandits and story are normal free updates to the game. I saw someone on Steam shouting that it was all paid DLC. Clearly they could not read.

Any feature we release should be seen in an experimental beforehand. I believe I said before that I was not doing it for 1.0. I have had way too many other things to deal with. Possibly for a 1.5 or 2.0 version.

b333 was experimental and since it tested fine, was switched to stable. As far as I recall, every stable update we have done in many years is preceded by experimental versions, which once we are done and the final one tests fine, it then turns into the new stable.

Testing experimentals tells us that those exact builds, for all 3 platforms, each with client/dedi versions, tested well for a variety of people.