mojira.dev
MC-147800

Chunks nearby getting a full reset if load with 1.14pre1

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!

Related issues

Attachments

Comments

migrated
[media][media]
migrated

Same 

1LotS

Can comfirm

migrated

I have the same issue

migrated

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.

migrated

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

migrated

Confirmed. Now I have to stay on 19w14b until Mojang fixes the **** bug! Please release 1.14 pre-2 ASAP! But, keep up the good work. Trust me, this bug is much, much worse than a world generating issue in 18w19a last year.

migrated

Same here, overwritten chunk has whole magazine 😞 and i forgot to make backup copy 

Johnibur

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.

migrated

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! 👍

DanTheMystFan

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.

migrated

I can confirm that this happened to me on 14.2 pre release 3 an entire chuck changed back to its original way.

migrated

(Unassigned)

Community Consensus

Minecraft 1.14 Pre-Release 1

Minecraft 1.14 Pre-Release 2

Retrieved