If I load my world in 1.14pre1 (with or without "optimization") chunks nearby get a full reset. Restoring from a backup the world loads normal in 19w14b... See pics!
Environment
Windows 10 64bit, old Core i5, Java Edition Vanila, no mods, no shader, my Minecraft World converted from 1.13.2 via 19w07a an all snapshots after that
Linked issues
is duplicated by 13
Attachments
Comments 11
Have the same issue. And when I quit out and reloaded, yet another chunk was affected. I didn't use optimize world or anything similar.
Meanwhile I tested it on two computers. One with an old Core i5 (1st gen) computer with Windows 10 64bit and with a Core i7 (6th gen) with Windows 7 (64bit). For this saved world it is always the same chunk who ist reseted in 1.14pre1. Even if I got in 19w14b in the middle of this chunk, save, an reload in 1.14pre1 (with and without "optimizing") I start in a reseted / respawned Chunk in the middle of stone...
This is actually caused by [MC-147754]. The POI already registered error does not crash the game everytime, but displays an error in the logs, such as:
[19:48:29] [Server thread/ERROR]: Couldn't load chunk
java.lang.IllegalStateException: POI data mismatch: already registered at ev{x=15, y=79, z=-1}If you go the aforesaid location, you will see that the chunk containing the POI data mismatched has been regenerated.
I tested my world as a backup from the 19w14b on both computers with the new 1.14pre2 and the problem seems to be resolved! 👍
Not sure if this should count as a different issue, but I'm observing the same behavior on a world I just created in 1.13.2 when loading in 1.14-pre2.
UPDATE: I tested this again in 1.14-pre3 and it was not an issue.
Same