John B. McCarthy

On my PC I believe these problems are quite recent, and are certainly present in version 1.10.1.

Villagers started doing this in the last week or two on Windows 10 Bedrock. Around the same time the Drowned mostly started ignoring me when i go into the water.

This has happened to essentially every world I've created on Windows 10. At first I lost everything, so I started saving a back-up of each world every time I save and quit. Unfortunately most of the time when this bug occurs it seems to occur when the game is doing it's save and exit, so a) you don't know you've lost everything till the next time you go to play, and b) the back-up save will also be of a "reset to spawn" world.

If it only happened once in a blue moon I could live with it, but if I play for an hour or so every night, this bug will probably reset my worlds two or three times a week.

I've uninstalled and reinstalled the game twice with no change to the prevalence of the bug (and thanks, Minecraft for wiping out ALL my saved games without warning the first time I uninstalled the game).

I believe the "reset" to spawn can happen both when a game is "saved and exited" and when a game fails to open properly (though I'm not sure whether that in itself causes MC to "save" the game again).

If I open a saved game and it has reset to the original world spawn, then any copy I made of that particular save will always reset to the spawn conditions too.

If I open a save, and I get the 'There was a problem loading this world' message, then sometimes when I subsequently get the world to re-open successfully the "reset to spawn conditions" will occur, but in that case a copy of that particular saved game is usually fine.

And today I experienced the bug on a new survival world I'd only played for two days, and where my save file was smaller than 9 MB. It was a vanilla survival game using the ChromaHills texture pack.

The fact that both the main save file and the most recent back-up copy of it were both corrupted suggests that the bug occurs during the exit and save process.

Okay, on my most recent game I experienced this bug after about 10 days pay, when my save file was approximately 14 MB in size. At that point I'd built a multi-level tower/base near my spawn point, and explored another nearby island and started to build a house there as well.

I found that my main game file, and the copy I'd made of it both were effected identically by the bug.

I think the problem seems to become more frequent the more you've played in a world. Smallish save files don't seem to "reset to spawn conditions", but once you get a file in the 30-40 MB+ range (after a week or two of daily play) this bug seems to crop up more often, but even at 40+ MB most worlds have only barely begun to be explored, so it's a truly annoying flaw.