Hi My_13th_jr
I am sorry to hear that your save was effected by this issue. This is know as an MD5 error. This error occurs when the save struggles to load an area and instead reverts it to the default Day 1 state.
As you mentioned it happened after a crash, I assume you play on an XB1? MD5s are most commonly triggered by crashes on the XB1. Unfortunately as the saves are maintained on the hosts console there is no way that we can roll back the save. As you are likely on XB1 the cloud syncs very rapidly which doesn't allow for maintaining backups like you would on a PS4.
The team and I both know how frustrating and disheartening this error can be for players. They have already fixed a large number of triggers for the MD5 error in previous patches and are continuing to work on removing the last remaining trigger for this error. In the mean time there are some things to keep in mind and that may help:
-
Crash indicators: There are a number of indicators your might spot that a crash is coming. A menu flickering / not displaying. Animals not spawning correctly. A sudden extreme change in weather. - Shutting down immediately and clearing the cache of the console by unplugging for 5 mins and rebooting may help prevent crashes that lead to MD5 errors, however if not done quickly they can still occur.
-
Timing: For regular crashes - if you know how long it takes, some players time and hard reset their console without a crash trigger occuring.
-
Crash Factors: Some things may cause whatever is generating the crashes to build up faster. This can include large amounts of the map explored in a single session, or large modifications made. While I'm not saying to avoid these, as they are at the core of Gameplay, it is worth noting it make have an effect when watching for crashes. Player Ignoringmywife1 mentioned a friend of theirs has avoided MD5 errors by not digging within a few blocks of their chosen base.
-
MD5 workaround: If you do experience a crash, there is a chance it will trigger an MD5 error. Aside from keeping items spread out (detailed below) players have found a way to roll back a little on XB1 to avoid the MD5. It should be noted this is not an official workaround so caution is advised when using it. A lot of players have reported success with it however if followed quickly and exactly after a crash
https://7daystodie.com/forums/showthread.php?69218-Possible-work-around-and-or-solution-to-md5-crashes(base-wipes-resets)
-
Storage and Crafting clusters: Separating out crafting stations and storage has worked for some. Multiple chests in the same area would count as a cluster, and keeping storage together near craft-stations seems to increase the chances of the area wipe for some players. It is also worth noting that players find that stations that are currently crafting / cooking when a crash occurs may be more likely to be hit. - This seems to be the most common form of MD5 error at the moment. If you have other focal points, please let me know and I will pass this information onto the team.
I understand that the workarounds are not ideal for players, but they have proven effective for some while waiting on a fix to be released. Currently the team are working on upgrading the game engine to Unity 2017, which should help them fix some of the more persistent bugs still in the game. They confirmed this upgrade a few weeks ago in this announcement:
https://7daystodie.com/forums/showth...-from-the-Team
I hope that information helps. If you have any further questions I will do my best to answer them.
Clare
