Hi CK724,
I am sorry to hear you were hit with an MD5 error and that it took so much from you. I completely understand how disheartening this error is for players and the feelings of frustration it can cause.
I appreciate you taking the time to let me know what happened to your save.
While it is true there is nothing that can be done for you lost items, there are some ways to help avoid MD5 errors in the future. Below is a list of some of the steps players have taken to avoid / be aware of impending crashes and MD5 errors.
- 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 the 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 erros by not digging within a few blocks of their chosen base too.
- 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 (95%) have reported success with it however if followed quickly and exactly after a crash. If you log in to check if there is an MD5 error, it is already too late to use this workaround -
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. From your brief description it sounds like lots was kept together in a small space, is this correct? 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 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 pave the way for them to fix some of the more persistent bugs still in the game. They confirmed this upgrade in this announcement:
https://7daystodie.com/forums/showthread.php?84520-06-06-Message-from-the-Team
Again I am sorry your save was hit by an MD5, if you have any further questions, I will do my best to answer them.
Clare