Russell Woollums

I want to call attention to this issue.  It is not a duplicate of the post above.  Villager Breeding and Villager Harvesting are 2 different mechanics.  This issue is that you are unable to breed villagers with mob griefing disabled.

For this type of error, is it possible to improve the logging to indicate which region file and chunk was the source of the bad entry for the crash?

I was experiencing the same issue.  1.13 was fine, but from 1.14 snapshots through 1.14.2 PreRelease 1 I was experiencing restarts every 30-60 minutes.  I ran the commands below from MC-142134 and was able to play all morning without a single restart.  Not sure if this is the fix for everyone, but make sure you backup worlds if you attempt the fix below.

In order to fix your existing world, you can try following these steps. Apparently this is just a temporary workaround, so you might need to repeat this once the issue reoccurs again.

Singleplayer: Select world → Edit world → Optimize world → check "erase cache data" → Backup and load

Multiplayer: Start the server.jar with the following command:

java -jar server.jar --forceUpgrade --eraseCache

Tested this morning with a 1.13 world that previously experienced the issue.  I was not able to reproduce the issue with world loads, teleports, portals or flying around the world.  This additionally fixed some older dark spot issues we had.  Thank you!

Thanks for the reply.  I was hoping it wasn't world loading dependent and was just done at startup.

Will the server startup flags need to be used for one start-up, or should those remain in the startup file indefinitely.

If it helps, I have uploaded a single region file due to the 10MB limit, and screenshot, which shows the issue.  I originally noticed this issue teleporting to player builds, both of which showed this issue.

Edit:  Also, you can see that it also extends to lava, glowstone and nether rack light sources.

If you need a pristine vanilla world, then we'll need to have one of the other watchers upload their world.  Our world was demodded with 1.12 and would not have reported an issue had their not been an existing ticket.  The zipped world backup is 4GB, so not sure if that is an issue as well and someone has a smaller example for testing?

Upgraded 1.13.2 world to 19w13b, then upgraded yesterday to 19w14a.  Confirmed lighting issue.  Replacing torches manually is not an option when you think of worlds that are thousands of blocks by thousands of blocks.  It would be nice if there was a means to rescan lightlevels for entire worlds given past lighting issues.