Hi DracoLadon,
I am sorry to hear this has happened to your save. This is know as an MD5 error. I'm afraid due to the way the game saves on XB1 it is not possible to restore to a previous version of your save (on PS4 the cloud is not instantly synced and you can save to external device).
This error occurs when the game struggles to load an area when booting the save (usually after a crash has occurred). This is an issue the team are aware of and have been working on for some time. While it may not be of great comfort to you now, the team have fixed a large number of triggers for the MD5 error and the analytics system in place shows that the numbers of MD5s have reduced greatly. The remaining triggers - like the one you experienced - are a little more difficult to resolve but the team are continuing to work on them.
In the mean time, players have discovered a way to workaround the XB1 issue after a crash. This is an unofficial workaround, so caution is advised but players have found it to be quiet successful if done immediately after a crash -
https://7daystodie.com/forums/showthread.php?69218-Possible-work-around-and-or-solution-to-md5-crashes(base-wipes-resets)
If your error did occur after a crash, there are some things it is worth being aware of that may help you avoid or simple prepare for them in future.
- Crash indicators: There are a number of indicators your might spot that a crash is coming. A menu flickering / not displaying (you may have noticed this in your inventory before a crash?) 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 once you see an indicator, you may still experience a crash.
- Timing: If you know how long it takes for a crash to build up, some players time and reset without a crash trigger occurring. (You mentioned you crash often, but is it after roughly the same amount of time for each crash?)
- 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 too.
- Storage and Crafting clusters: Separating out crafting stations and storage has worked for some. 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 believe something else could have been the focal point please let me know.
I understand that this is not ideal for players, but it is the best advice that I can give at this moment in time while the team works to find a solution to these issues. If you have any further questions, I will do my best to answer them.
Clare
