Crash while opening world / while ticking entity: "IllegalStateException: POI data mismatch: already registered at ev{x=##, y=##, z=##}"
Was going to test some bugs today, but the world crashed when trying to open it, twice. Both crash reports attached, I can also attach the world file if desired.
Not sure if this ticket should be private or not.
java.lang.IllegalStateException: POI data mismatch: already registered at ev{x=-1, y=31, z=47}
at aqc.a(SourceFile:72)
at aqc.a(SourceFile:43)
at aqc$$Lambda$2583/1281199057.accept(Unknown Source)
at java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:184)
at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193)
at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193)
at java.util.Iterator.forEachRemaining(Iterator.java:116)
at java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1801)
at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:512)
at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:502)
at java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:151)
at java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:174)
at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
at java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:418)
at aqc.<init>(SourceFile:43)
at aqa$$Lambda$2444/1399778887.apply(Unknown Source)
at bxt.a(SourceFile:123)
at bxt$$Lambda$2578/72956740.apply(Unknown Source)
at java.util.Optional.map(Optional.java:215)
at bxt.a(SourceFile:122)
at bxt.a(SourceFile:102)
at bxt.d(SourceFile:76)
at aqa.a(SourceFile:69)
at aqa.a(SourceFile:65)
at aqa$$Lambda$2806/45311108.apply(Unknown Source)
at java.util.stream.ReferencePipeline$7$1.accept(ReferencePipeline.java:267)
at java.util.stream.IntPipeline$4$1.accept(IntPipeline.java:250)
at java.util.stream.Streams$RangeIntSpliterator.forEachRemaining(Streams.java:110)
at java.util.Spliterator$OfInt.forEachRemaining(Spliterator.java:693)
at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:512)
at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:502)
at java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:151)
at java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:174)
at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
at java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:418)
at java.util.stream.ReferencePipeline$7$1.accept(ReferencePipeline.java:270)
at bgn$1.tryAdvance(SourceFile:164)
at java.util.stream.ReferencePipeline.forEachWithCancel(ReferencePipeline.java:126)
at java.util.stream.AbstractPipeline.copyIntoWithCancel(AbstractPipeline.java:529)
at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:516)
at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:502)
at java.util.stream.FindOps$FindOp.evaluateSequential(FindOps.java:152)
at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
at java.util.stream.ReferencePipeline.findFirst(ReferencePipeline.java:464)
at aqa.b(SourceFile:85)
at apj.b(SourceFile:49)
at apj.a(SourceFile:34)
at apj.a(SourceFile:19)
at apo.b(SourceFile:31)
at ajb.a(SourceFile:249)
at ajb$$Lambda$2783/813156550.accept(Unknown Source)
at java.util.LinkedHashMap$LinkedValues.forEach(LinkedHashMap.java:600)
at ajb.c(SourceFile:249)
at ajb.a(SourceFile:221)
at ave.K(SourceFile:255)
at ain.cZ(SourceFile:623)
at aim.k(SourceFile:2257)
at ain.k(SourceFile:479)
at aib.k(SourceFile:140)
at aim.h(SourceFile:2102)
at ain.h(SourceFile:293)
at ave.h(SourceFile:293)
at vf.a(SourceFile:581)
at vf$$Lambda$2749/1657880339.accept(Unknown Source)
at bha.a(SourceFile:669)
at vf.a(SourceFile:384)
at net.minecraft.server.MinecraftServer.b(SourceFile:817)
at net.minecraft.server.MinecraftServer.a(SourceFile:754)
at dwy.a(SourceFile:128)
at net.minecraft.server.MinecraftServer.run(SourceFile:629)
at java.lang.Thread.run(Thread.java:745)
Linked Issues
is duplicated by14
MC-147763The game crashed whilst ticking entityDuplicateMC-147768Converting world to 1.14 pre release 1 regenerates some chunksDuplicateMC-147782crash reportDuplicateMC-147783Updating from snapshot 19w14b to 1.14 Pre-Release 1 corrupts certain villagers.DuplicateMC-147802"ticking entity" villagerDuplicateMC-147820The game crashed whilst ticking entity The game crashed whilst ticking entity Error: java.lang.IllegalStateException: POI data mismatch: already registered at ev{x=31, y=79, z=-305}DuplicateMC-147823Ticking Villager Entity Server Crash due to POI data mismatchDuplicateMC-147830One specific chunk regeneratesDuplicateMC-147834The game crashed whilst ticking entity The game crashed whilst ticking entity Error: java.lang.IllegalStateException: POI data mismatch: already registered at ev{x=15, y=79, z=255}DuplicateMC-147835Game crashed while Ticking EntityDuplicateMC-147863Crash when villager claims smokerDuplicateMC-147875Ticking entity CrashDuplicateMC-147921POI data mismatch - Crash whilst loading world in 1.14 Pre-Release1DuplicateMC-1479791.14-pre1 crash when loading world from 19w14bDuplicateAttachments8
Created Issue:
Crash while opening world
Was going to test some bugs today, but the world crashed when trying to open it, twice. Both crash reports attached, I can also attach the world file if desired.
Not sure if this ticket should be private or not.
Attachments2
Crash while opening world / Crash while ticking entity
![[Mod] violine1101](../../../data/avatars/users/92858.png){kind=small}
Was going to test some bugs today, but the world crashed when trying to open it, twice. Both crash reports attached, I can also attach the world file if desired.
Not sure if this ticket should be private or not.
1.14 Pre-release 1: crash-2019-04-10_16.09.26-server.txtjava.lang.IllegalStateException: POI data mismatch: already registered at ev{x=-1, y=31, z=47} at aqc.a(SourceFile:72) at aqc.a(SourceFile:43) at aqc$$Lambda$2583/1281199057.accept(Unknown Source) at java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:184) at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193) at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193) at java.util.Iterator.forEachRemaining(Iterator.java:116) at java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1801) at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:512) at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:502) at java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:151) at java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:174) at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) at java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:418) at aqc.<init>(SourceFile:43) at aqa$$Lambda$2444/1399778887.apply(Unknown Source) at bxt.a(SourceFile:123) at bxt$$Lambda$2578/72956740.apply(Unknown Source) at java.util.Optional.map(Optional.java:215) at bxt.a(SourceFile:122) at bxt.a(SourceFile:102) at bxt.d(SourceFile:76) at aqa.a(SourceFile:69) at aqa.a(SourceFile:65) at aqa$$Lambda$2806/45311108.apply(Unknown Source) at java.util.stream.ReferencePipeline$7$1.accept(ReferencePipeline.java:267) at java.util.stream.IntPipeline$4$1.accept(IntPipeline.java:250) at java.util.stream.Streams$RangeIntSpliterator.forEachRemaining(Streams.java:110) at java.util.Spliterator$OfInt.forEachRemaining(Spliterator.java:693) at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:512) at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:502) at java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:151) at java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:174) at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) at java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:418) at java.util.stream.ReferencePipeline$7$1.accept(ReferencePipeline.java:270) at bgn$1.tryAdvance(SourceFile:164) at java.util.stream.ReferencePipeline.forEachWithCancel(ReferencePipeline.java:126) at java.util.stream.AbstractPipeline.copyIntoWithCancel(AbstractPipeline.java:529) at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:516) at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:502) at java.util.stream.FindOps$FindOp.evaluateSequential(FindOps.java:152) at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) at java.util.stream.ReferencePipeline.findFirst(ReferencePipeline.java:464) at aqa.b(SourceFile:85) at apj.b(SourceFile:49) at apj.a(SourceFile:34) at apj.a(SourceFile:19) at apo.b(SourceFile:31) at ajb.a(SourceFile:249) at ajb$$Lambda$2783/813156550.accept(Unknown Source) at java.util.LinkedHashMap$LinkedValues.forEach(LinkedHashMap.java:600) at ajb.c(SourceFile:249) at ajb.a(SourceFile:221) at ave.K(SourceFile:255) at ain.cZ(SourceFile:623) at aim.k(SourceFile:2257) at ain.k(SourceFile:479) at aib.k(SourceFile:140) at aim.h(SourceFile:2102) at ain.h(SourceFile:293) at ave.h(SourceFile:293) at vf.a(SourceFile:581) at vf$$Lambda$2749/1657880339.accept(Unknown Source) at bha.a(SourceFile:669) at vf.a(SourceFile:384) at net.minecraft.server.MinecraftServer.b(SourceFile:817) at net.minecraft.server.MinecraftServer.a(SourceFile:754) at dwy.a(SourceFile:128) at net.minecraft.server.MinecraftServer.run(SourceFile:629) at java.lang.Thread.run(Thread.java:745)
relates to
![[Mojang] Bartosz Bok](../../../data/avatars/users/10122.svg){kind=small}
[Mojang] Bartosz Bok![[Mod] Asteraoth](../../../data/avatars/users/92886.png){kind=small}
is duplicated by
![[Mod] Pokechu22](../../../data/avatars/users/92931.png){kind=small}
Crash while opening world /Crashwhile ticking entityCrash while opening world / while ticking entity: "POI data mismatch: already registered at ev{x=-1, y=31, z=47}
Crash while opening world / while ticking entity: "POI data mismatch: already registered at ev{x=-1, y=31, z=47}Crash while opening world / while ticking entity: "IllegalStateException: POI data mismatch: already registered at ev{x=##, y=##, z=##}"
is duplicated by
is duplicated by
is duplicated by
![[Mod] Neko](../../../data/avatars/users/92901.png){kind=small}
relates to
is duplicated by
is duplicated by
screenshot-1.png
is duplicated by
is duplicated by
is duplicated by
![[Mod] Michael Wobst](../../../data/avatars/users/37868.png){kind=small}
is duplicated by
![[Bot] Piston](../../../data/avatars/users/31202.png){kind=small}
is duplicated by
Yeah, good idea to make backups.
relates to
![[Mod] Urielsalis](../../../data/assets/gravatar/urielsalis.jpeg){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.
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.
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.
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.
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.
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.
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.
![[Helper] Johnibur](../../../data/avatars/users/28381.png){kind=small}
It is actually a duplicate of MC-147754. If you look up your logs, you will see errors saying that some chunks couldn't be loaded because POI was already registered at location…
Your issue is MC-147754.
Okay I tested again and it is related to render distance, and "several minutes" was clearly an exaggeration on my side. I had distance set to 32 from trying to debug MC-138114 (it didn't help).
But there is a regression in save times - my results with world seed 77 (setup: Linux, SSD, i5-6400 2.7GHz, 16GB RAM)
Render distance 32:
- 1.13.2 - saving a new world took 2 seconds
- try 1: 1.14pre1 - saving took 20 seconds for a brand new world
- try 2: 1.14pre1 - a new world i explored a little by flying around in creative, saving took 40 seconds and then crashed with
MC-147754
Render distance 20:
- 1.13.2- saved almost instantly
- 1.14pre1 - saved in 2 seconds
- 1.14pre1 - the more explored world, saved in 8 seconds (maybe it didn't crash because it didn't try to generate the buggy chunk?)
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.
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.
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.
Snapshots (and pre-releases) might and sometimes will break your world. That's why you're advised to make backups of it.
The chunk corruption probably came from a bug in 1.14-pre1 (MC-147754) and has been fixed in 1.14-pre2. There's no way to fix affected worlds retroactively.
Seems like duplicate of MC-147754. Should be fixed after loading in later versions. Please re-check.
Destroying all workplaces and killing all villagers in the world loaded in a previous snapshot seemed to resolve this issue, although some chunks appeared to have been deleted.
Same "point of interest" crash, this happens after optimizing world for the pre-release and clearing all caches.
ETA: Also happens if the world is NOT optimized.
Just happened to me too. Stupid Snapshot!
Just had a ton of chunks regenerate on me in the 1.14 Pre-Release. World is totally fine on 19w14b but as soon as I update it regenerates the chunks.
Also had the POI error when loading certain chunks, would crash the server.
Crash
willmay occur for chunks that contain POIs (villager workplaces, beds, etc) that were created:We will try to re-create broken data, but villager assignments may be lost.
By "in this snapshot" do you mean in this pre-release, or in the snapshot before the pre-release? Or something else entirely?
It's spamming in the server console for me and regenerating chunks with chests/furnances.
--> attached log.txt.
This issue occurs only if there is "already" registered POI data upon restart. It means this issue never occurs if I remove the POI data (deleting the files from the poi world folder). But even with new computed data from this version pre-1, this issue will be happening again after restarting the server if there is any existing POI data, old one or not.
Crash happened to me when upgrading to 1.14-pre1:
crash-2019-04-10_21.37.51-server.txt
Please DON'T remove POI data, it will only make this issue worse.
Confirmed for 1.14 pre-release 1
Had this with a new world generated in the pre-release 1, so its not necessarily related to migrating old save data or optimizing.
This happened to me as well, and only affects to the entity, Villager.
Loading up other worlds from previous snapshots seems to work fine.
hopefully we will get this bug fixed in 1.14 pre-release 2
Confirmed. Some worlds from the previous snapshot can be loaded properly, but the world that already in pre-release 1 version can no longer be loaded again.
As soon as I loaded 1.14-pre1:
The game crashed whilst ticking entity Error: java.lang.IllegalStateException: POI data mismatch: already registered at ev{x=-49, y=79, z=-17}This may or may not be causing chunk corruption also, loading up a world with this issue appears to cause some chunks to completely break. Reloading the world reveals the chunks to have been completely reset.
It's worth noting that I have not yet experienced this happening in worlds without this issue, even when transitioning from 19w14b to 1.14-pr1. If you need a test world, I will be happy to provide one for you.
I can confirm that it will break your chuck(s).
Had 50% of a house deleted because of it, it complained about a POI being allready registered on 1727,79,-913 , which is an airblock just above my house ...
------------
[22:49:00] [Server thread/INFO]: Preparing start region for dimension minecraft:overworld
[22:49:04] [Server thread/ERROR]: Couldn't load chunk
java.lang.IllegalStateException: POI data mismatch: already registered at ev{x=1727, y=79, z=-913}
at aqc.a(SourceFile:72) ~[server.jar:?]
at aqc.a(SourceFile:43) ~[server.jar:?]
at java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:184) ~[?:1.8.0_201]
at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193) ~[?:1.8.0_201]
at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193) ~[?:1.8.0_201]
at java.util.Iterator.forEachRemaining(Iterator.java:116) ~[?:1.8.0_201]
at java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1801) ~[?:1.8.0_201]
at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481) ~[?:1.8.0_201]
at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471) ~[?:1.8.0_201]
at java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:151) ~[?:1.8.0_201]
at java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:174) ~[?:1.8.0_201]
at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) ~[?:1.8.0_201]
at java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:418) ~[?:1.8.0_201]
at aqc.<init>(SourceFile:43) ~[server.jar:?]
at bxt.a(SourceFile:123) ~[server.jar:?]
at java.util.Optional.map(Optional.java:215) ~[?:1.8.0_201]
at bxt.a(SourceFile:122) ~[server.jar:?]
at bxt.a(SourceFile:102) ~[server.jar:?]
at bxt.d(SourceFile:76) ~[server.jar:?]
at aqa.a(SourceFile:165) ~[server.jar:?]
at bxo.a(SourceFile:113) ~[server.jar:?]
at us.f(SourceFile:416) ~[server.jar:?]
at java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1590) [?:1.8.0_201]
at agf.h(SourceFile:135) [server.jar:?]
at agf.p(SourceFile:114) [server.jar:?]
at vd$a.p(SourceFile:438) [server.jar:?]
at vd.d(SourceFile:194) [server.jar:?]
at net.minecraft.server.MinecraftServer.p(SourceFile:698) [server.jar:?]
at agf.bf(SourceFile:99) [server.jar:?]
at net.minecraft.server.MinecraftServer.o(SourceFile:676) [server.jar:?]
at net.minecraft.server.MinecraftServer.a(SourceFile:467) [server.jar:?]
at net.minecraft.server.MinecraftServer.a(SourceFile:370) [server.jar:?]
at ug.d(SourceFile:218) [server.jar:?]
at net.minecraft.server.MinecraftServer.run(SourceFile:602) [server.jar:?]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_201]
-------------
Ticking on "trapped" villagers. Had to eliminate a villager in a player's automatic carrot farm in order to get the server to boot.
Confirmed. Crash when villagers are in sight.
crash-2019-04-11_14.24.55-server.txt
Villagers(NPC) are not the problem, new 1.14 villages(location) are. Problem still occurs when you kill all NPCs
Did not have this problem with 1.13.2 villages, but a newly generated village is a problem.
When you delete the POI files you can play again, until you find a 1.14 village, then close your world and try to rejoin.
POI likely stands for Points of Interest, villages are a point of interest. A Pillager Outpost is likely aso a Point of Interest, but no crash at those locations.
Hope this helps.
No MuMe, points of interest are the blocks villagers can interact with: beds, bells, and all the working stations: cauldron, brewing stands, lectern, stonecutter, loom, grindstone, composter, cartography table, smithing table, barrel, smoker, blast furnace and fletching table.
The bug can occur with poi created either with this pre1, or with versions prior to 19w11a (the village overhaul).
But even if it seems to not trigger the problem at first, like boq said, do not delete the poi data, and be sure to have a world backup.
If I don't delete POI data I cannot play at all, as it crashes right after starting the world.
But my only reason to do this is to check for bugs with my Realms server before the full release. My Server uses multiple command systems and datapacks, so I need to test those before the server breaks after the automatic update of realms. As long as i delete POI data I can at least test the other things.
I may have found a better work round than removing the POI files.
I tried that and chunks kept regening every time I opened the game, even if I had removed blocks etc. Then I looked through posts on the mcr files and found one from way back that suggested renaming the level.dat_mcr to level.dat_mcr_old so I gave it a try and touch wood the game has been more stable since.
I have had one odd crash but not related to this but a fatal in the Java runtime environment which I will look into seperatly.
Hope this helps.
Just to join the mass.
Confirmed! Yesterday, when I first upgraded server to 1.14-pre1, I played normally. Today I cannot join the server (with server being crashed) because of this bug.
Can you mark my
MC-147877as duplicate ifMC-147768/MC-147783/MC-147830are marked?My case was this:
In the morning I started MC to play for a few minutes. New version. Backup and load. I noticed there are now guardians around the monument and other fish in the ocean around. Then I went home and switched the game off. When I loaded my world when I came back from work, I found my house gone, only one side still there, surroundings seemed OK too. I checked with a bit of digging that the basement is gone too. best described by MC-147768.
@boq Will the fix of this bring in the end any data loss to existing worlds prior to the villages overhaul?
What does being fixed in "Future Version - 1.14+" mean? Does it mean I have to wait until the full release of 1.14 rather than just the next pre-release?
maybe on 1.14 pre-release 2
"Future Version - xx" is a common name for the strict next upcoming version not labeled on Mojira yet. Will be 1.14-pre2 in this case.
Confirmed for Pre Release 1
I also had the same problem opening a world created in previous snapshot versions. It usually opens the 1st time in Pre 1, but the second time the crash occurs. It seems that the crash is always related to the villager entity in certain chunks created in previous versions of snapshots. If you drop a villager with an egg in the creative mode in these chunks, the crash also occurs instantly. As in the logs posted here, the villager entity is always referred in these errors.
Details:
Entity Type: minecraft: villager (bird)
Entity ID: 222
Entity Name: Dorfbewohner
Entity's Exact location: -756.53, 66.00, -852.33
Entity's Block location: World: (-757,66, -853), Chunk: (at 11.4,11 in -48, -54; contains blocks -768,0, -864 to -753,255, -849), Region : (-2.2, contains chunks -64, -64 to -33, -33, blocks -1024.0, -1024 to -513.255, -513)
By deleting the villager entity mentioned in the logs with nbtexplorer it is possible to enter the world without the crash, but some chunks are lost.
Unfortunately the issue is not fixed in pre2.
[14:37:27] [Server thread/INFO]: Starting minecraft server version 1.14 Pre-Release 2 […] [14:37:36] [Server thread/ERROR]: Failed to load POI chunk java.lang.IllegalStateException: POI data mismatch: already registered at ev{x=15, y=79, z=-1} at aqc.a(SourceFile:81) ~[server.jar:?] at aqc.a(SourceFile:44) ~[server.jar:?] …Edit: although, the aforesaid chunks are not being overwritten this time.
Edit: error message only appeared on first startup. Second try, no error.
Working as intended, corrupted data needs to be regenerated, but that does not destroy whole chunk.
OK, Mr. Bok, I'll try it, but I'm holding you responsible if Skelly, Bones, Ice Runner, Zenith, Rusty, Bedrock, Leonard, Otis, Lars, Jellie, Jeb_, Toast, Rueben, Drumstick's cousin Drumstick, Chocolate, Gabe, Goldie, or any of my other pet are harmed by this!!Unable to render embedded object: File ( Have a nice day) not found.!Unable to render embedded object: File ( Rockatoa, Brickticks out) not found.
If you test anything other than release without backups, it's your own fault.