Matt Smollinger
Assigned
Reported
Comments
Meaning no longer crashing. Should I upload the additional crash reports?
Hah. So we've hit this 2 more times today. I reverted the world back to 18w22c and its working as expected.
This was originally created on a 1.13 snapshot. 18w16a I believe.
Is that a problem? Or just a note?
Wanted to add my upvote here as well. My players and I have also determined exact coords inside our world running on 18w20b that cause the crash listed above. We're running on Ubuntu 16.04, multiplayer survival, on Oracle Java 1.8.0_171. World was originally generated on 18w19b with a world seed of k1w5sWlDeWjSoVrHPUpQ - crash however is happening on 18w20b. Coords to reproduce the crash: x: -2896.976, y: 62.073, z: -7229.122
If this is a world generation problem, meaning you need my exact version of the world, let me know (mention me here) and I can upload. It's rather larger at this point however which is why I'm, refraining from just posting it. I guess we were lucky in that respect to not hit it early on?
@anon Sorry about that, but to be honest that answer is unacceptable. Where are we to post issues about the minecraft.net website? This is a pain point amongst anyone running any kind of sophisticated server backend.
X-posting my comment from my duplicate ticket: https://bugs.mojang.com/browse/MC-130974
We got to a point with this where one of my players would log in and the world would immediately crash, so I reverted back to 18w22c and that appears to have temporarily resolved it. Temporarily because my players were whining about all their books being bugged from the issue in that snapshot 😃