My friend and I have encountered a severe issue with a long-running world of ours. We were playing splitscreen today, constructing an iron generator that followed the design in this video almost exactly:
Upon finishing it, we saved, and then decided to leave it running while we went out for food, so we could give the villagers time to breed and hopefully get some iron out of it. Upon returning, we found that I had been killed, and the villagers hadn't done much breeding anyway, so we decided to quit without saving. We immediately reloaded the world; the screen froze for a moment, and then it just showed the scrolling background, with nothing displayed except for "(A) Select (B) Back" in the lower left corner. It has done this every time since, on two different consoles. We tried copying it to a flash drive and were greeted with "There was a problem performing that action."
That last thing has us pretty convinced that the file is corrupted, but we're hopeful there's a fix. We do have a slightly out-of-date backup that we're willing to revert to if necessary, but obviously this isn't preferable. Any help, even if it's just a confirmation that we're screwed, would be greatly appreciated.
Well that's disappointing, but the backup is only a couple days behind, so we'll be fine. Any idea what could have done it? Are any of the features of that iron generator bugged at the moment? We've never used hoppers, comparators, or trapped chests on the world before, nor have we ever really made any sort of grinder, so we're suspicious. The only other thing out of the ordinary that happened during the play session was we noticed an Enderman had put a cactus on cobblestone. If that's what did it... honestly, that'd be hilarious.
Well that's disappointing, but the backup is only a couple days behind, so we'll be fine. Any idea what could have done it? Are any of the features of that iron generator bugged at the moment? We've never used hoppers, comparators, or trapped chests on the world before, nor have we ever really made any sort of grinder, so we're suspicious. The only other thing out of the ordinary that happened during the play session was we noticed an Enderman had put a cactus on cobblestone. If that's what did it... honestly, that'd be hilarious.
People have been sporadically reporting this sort of sudden file corruption almost ever since I joined this site in 2012... so, I honestly don't know has it can be narrowed down to specific triggers... aside from the more obvious ones (e.g. power fluxuations while the game is saving). Since you left the game running for an extended period unattended, it is possible that your system experienced a power flux while you were gone just as the game was saving player data (i.e. when the small chest icon appears in the right upper corner). It is unfortunate that there is no file recovery system embedded in the Xbox OS.
Other theories I have - 1) That it results from the cumulation of small bits of data lost every time the file is saved (I'm saying this because it seems to happen more frequently to older, more built up worlds - but it may also be that people just tend to report it when they feel a greater loss); or 2) That as the game is updated and the terrain generation has gotten progressively more complex, a small percentage of older seed strings become "invalid" mathematically (might explain the file corruption that occurs immediately following the download of an update, but not ones that occur sometime after the world has been loaded successfully after an update).
Definitely not the last one; we've played several times since the last update. Power fluctuation, maybe, but it would have been a weird time for it. Clear weather, not much snow on the ground, plus we were only gone for like an hour. The data loss one is scary, though. Would that mean even our backup is a ticking time bomb? I realize there probably isn't enough data to really know. I'll report back here if anything interesting happens, though. Thanks for the help, man.
Upon finishing it, we saved, and then decided to leave it running while we went out for food, so we could give the villagers time to breed and hopefully get some iron out of it. Upon returning, we found that I had been killed, and the villagers hadn't done much breeding anyway, so we decided to quit without saving. We immediately reloaded the world; the screen froze for a moment, and then it just showed the scrolling background, with nothing displayed except for "(A) Select (B) Back" in the lower left corner. It has done this every time since, on two different consoles. We tried copying it to a flash drive and were greeted with "There was a problem performing that action."
That last thing has us pretty convinced that the file is corrupted, but we're hopeful there's a fix. We do have a slightly out-of-date backup that we're willing to revert to if necessary, but obviously this isn't preferable. Any help, even if it's just a confirmation that we're screwed, would be greatly appreciated.
People have been sporadically reporting this sort of sudden file corruption almost ever since I joined this site in 2012... so, I honestly don't know has it can be narrowed down to specific triggers... aside from the more obvious ones (e.g. power fluxuations while the game is saving). Since you left the game running for an extended period unattended, it is possible that your system experienced a power flux while you were gone just as the game was saving player data (i.e. when the small chest icon appears in the right upper corner). It is unfortunate that there is no file recovery system embedded in the Xbox OS.
Other theories I have - 1) That it results from the cumulation of small bits of data lost every time the file is saved (I'm saying this because it seems to happen more frequently to older, more built up worlds - but it may also be that people just tend to report it when they feel a greater loss); or 2) That as the game is updated and the terrain generation has gotten progressively more complex, a small percentage of older seed strings become "invalid" mathematically (might explain the file corruption that occurs immediately following the download of an update, but not ones that occur sometime after the world has been loaded successfully after an update).
We haven't played much on the backup yet; probably won't be doing much of anything on it until we get around to transferring it to One.