MC-147768Converting world to 1.14 pre release 1 regenerates some chunks
Converting world to 1.14 pre-release 1 completely regenerates some chunks. The regenerated chunks seem to be few and far between, but destroyed some player built areas.
The logs seem to indicate a problem with POI mismatch.
Linked Issues
Attachments1
Created Issue:
Using Optimize World with Clearing Cache Completely regenerates some chunks
Using the optimize world feature with the new clearing cache feature completely regenerates some chunks. The regenerated chunks seem to be few and far between, but destroyed some player built areas.
The logs seem to indicate a problem with POI mismatch.
Using Optimize World with Clearing Cache Completelyregenerates some chunksConverting world to 1.14 pre release 1 regenerates some chunks
Using the optimize world feature with the new clearing cache featurecompletely regenerates some chunks. The regenerated chunks seem to be few and far between, but destroyed some player built areas.
The logs seem to indicate a problem with POI mismatch.
Converting world to 1.14 pre-release 1 completely regenerates some chunks. The regenerated chunks seem to be few and far between, but destroyed some player built areas.
The logs seem to indicate a problem with POI mismatch.
![[Mod] Pokechu22](../../../data/avatars/users/92931.png){kind=small}
Thank you for your report!
We're actually already tracking this issue at
MC-147754, so we will resolve and link this ticket as a duplicate.If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
I'm not convinced this is a duplicate as it is not causing the game to crash. It is simply regenerating the chunk and moving along as if nothing happened.
Potential workaround: Delete the poi folder inside of your world folder. It stops the bug from occurring and I have not noticed any detrimental effects of doing so yet.
I think it's kinda a duplicate or at least the same underlying cause in that both have the same "java.util.IllegalStateException: POI data mismatch: already registered at ev{x=##, y=##, z=##}" message. I've edited the issue title to include this at least.
Note that [Mojang] Bartosz Bok said over there:
I'm not entirely sure of the full meaning, though.