Jump to content

XBOX1 crash and takes almost everything on reload


Recommended Posts

Three times I have been playing in single player split screen and the game glitches and cuts off. When I try deleting console file to sync from cloud, my game is still messed up. Most of the stuff I builded and stored is gone. At this point I’m very discouraged to try again. If you make a way for us to save our own files this would solve the problem. We can have the auto save, but also a manual save file to load from if auto save becomes corrupt like it has three times already for me.

Link to comment
Share on other sites

Hi Maximus40,


I am sorry to hear your save has been effected multiple times by this issue. This issue is known as an MD5 error. Both myself and the team completely understand how frustrating and disheartening this issue is for players.


While it has been requested in the past that manual save be implemented, at the moment there is no plan to do so as it would require both changed a large chunk of core code as well as changing the overall gameplay design.


The MD5 error has multiple triggers, many of which have been resolved by the team in previous patches. The current most common trigger is the game crashing on XB1 as you mentioned occurs for you above. The team are working to resolve the remaining triggers but in the interim, while I understand it is not ideal, there are some things you can keep in mind and use as workarounds to avoid the MD5 errors.


To help avoid crashes which can lead to 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 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.


- 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.


MD5 errors themselves:


While I understand it is not an ideal method, players have discovered a way to workaround MD5s 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)


It should be noted that once you see the results of an MD5 error it is already too late. The above workaround must be performed as soon as the crash occurs - checking to see if that crash resulted in an MD5 error will cause the game to auto-save and the workaround wont work as the XB1 save feature uploads exceptionally quickly to the cloud. From your post above it sounds like you saw the error before attempting a save resync.


I hope that information helps, if you have any further questions I will do my best to answer them.



Link to comment
Share on other sites


This topic is now archived and is closed to further replies.

  • Create New...