I was a few chunks away from spawn in a world that was created in 1.14-pre2. I am unsure if the chunk had been loaded prior to updating to pre3. Upon trying to push and hit a pig, I was not able to do either of these things, but while trying to move through the pig, I was met with normal resistance. The pig didn't move even when I wasn't interacting with it. After re-entering the world, I noticed that other mobs were also acting in this manner. The map in my hand stopped updating, and my position on the map was also stuck in the position where I had first noticed the bug. Once this bug occurs, I am not able to save or crash the game normally, and I have to go into task manager and manually end the program to exit.
What I expected to happen was...:
the pig would move of its own accord, react to the player pushing it by moving, and react to the player punching it by turning red and fleeing.
What actually happened was...:
the pig did not move. it might as well have been an Armor Stand.
Steps to Reproduce:
1. load a Default world
2. create a map and enlarge it twice
3. walk away from spawn while holding the map in either hand and look for a mob
4. attempt to interact with the mob
5. attempt to save or crash the game
Attachments
Comments 6
The game's internal server probably crashed while you were playing, hence the game didn't register that you interacted the pigs, or wanted to save and close the world.
Please attach the crash report found in [minecraft/crash-reports/crash-<DATE>-server.txt|http://hopper.minecraft.net/help/guides/finding-minecraft-data-folder] here.
If you cannot find a crash report, please attach the full launcher log found in [minecraft/launcher_log.txt|http://hopper.minecraft.net/help/guides/minecraft-logs/].
This issue has been temporarily closed as Awaiting Response. Once the requested information has been delivered, the report will be reopened automatically.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
after the initial crash and after returning and forcing a crash, I still didn't have a crash report. Attached is the launcher log.
uploaded another launcher log from trying to run the world as it was backed up at 1.14-pre2, in 1.14-pre4.
As of 1.14-pre5, this issue appears to have been fixed on my world. Other things have cropped up, but I will make a separate bug report for those.
I have managed to reproduce this bug once again in 1.14-pre5, but it seems to require using a map, and it also prevents the user from saving or generating a crash report once the bug occurs (this has occured in pre3 and pre4 as well, but I was not certain as to the correlation). I'm going to update this bug to reflect this information.
I don't know if this is relevant, but upon discovering this bug and attempting to exit the game, I have been stuck with a "saving world" screen for over an hour.