Player A = originally generated the world
Player B and C = played this world in local multiplayer with A
Now the world was exported / imported to the faster computer of player B.
1. If now A and B go in the same chunk, instandly both game crashes. With A + C or B + C all fine!
2. With distance between the players: player B gets the damage of A. It depends not player C.
This Issue is on local multiplayer and realm, with the difference that on realm player C is not touched from the game crash.
Tried out on differnt devices (Windows 10 Desktop, XBOX One, Android Phone).
I think there is something in trouble after change the player id for the main player.
Comments 7
Not fixed in 1.2.10
The error also occurs when nothing is transferred to Realms. You just need to move your world to a guest player and play again in local mode. Game crashes when the old main player joins in the same area.
@Ralf Neumann That's unfortunate, I was hoping it'd be fixed in this version. I think I read somewhere that some of the bugfixes that were due to be rolled out in 1.2.10 had to be pushed back due to time constraints so hopefully the next update fixes this game-breaking bug.
Not fixed in 1.2.11
After the crash, I was right at the point where the original main player was at the time of the crash.
It shows that the game still doesn't get along with the changed player identity.
Still not fixed in 1.2.13, please get this fixed soon because there's no real point in me paying for a realm if I can't play on it with my friends 😞 Crashes both xbox and windows 10. I have a theory that changing gamertag might reset the player data and fix the issue, but I don't want to risk the $9.99 fee on a hunch
Thank you for your report!
Crashes such as these are logged automatically, and will be looked into further by the development team.
If you need help or support you might like to follow a link below.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki
I think you may be correct about the "main" (local) player change being involved. Switching between online and local player is at the center of two of the most common bug reports for 1.2.9. The problem has reportedly been fixed in the 1.2.10 Beta, but I assume you and your friends are not planning to join the beta and are more interested in a workaround or a way to rescue your world.
Unfortunately, the fact that you transferred this world between local players via the Realms intermediary makes this a unique example. I doubt anyone has had experience with this exact problem, let alone discovered a workaround. Your best bet might be to try catching a developer on the #beta-n-bugs channel in the Minecraft Discord.
It's also possible this isn't related to those earlier bugs at all and represents something new. In that case we'll be passing this issue on to the developers.