After upgrading from 1.14 to 1.14.1-pre1 to check for performance improvements on my server, several chunks appear to have been reset or reverted to an earlier state. Will attach screenshots when I am in a place to do so, but that is definitely a bug that will need to get addressed before the actual release.
Comments 4
I can confirm that this happened as well in the 1.14.2 Pre-release 1 on a server I play on. Built a large amount of stuff in some chunks. Those chunks then randomly reset to their initial state. Also, this doesn't have to do with upgrading from one version to another, it happened after several days running on 1.14.2. It's not a problem with upgrading, it's a problem with 1.14 versions themselves.
@unknown or anyone else can you post server / game logs? It's very important to know why the chunks couldn't be read.
After doing some digging I found that my server host (Minecraft-hosting.pro - save yourself the headache, and don't use them), not only has a script that disables the default Minecraft autosave feature, but then only issues a manual save once every 24 hours so if your server crashed or reboots between those times, you will lose any progress that has been done between those two points, making it look like chunks have reverted back to earlier states of development.
I have yet to find any documentation that shows how often the Java server saves when autosave is enabled, but it's not very frequent (though this REALLY needs to be documented). Your best bet is to force a save yourself every once in a while (/save-all), and if you have access to the host that the server is running on, set up a cron job to force a save on a timer.
So I cannot correlate the behavior I observed and originally opened this ticket for with a bug in Minecraft.
I cannot validate this against the conditions I described above (being tied to upgrading from 1.14 to 1.14.1-pre1.
Please close this ticket.