Hello there,
After searching my problem on youtube, google, the wiki and even reddit, I decided to look at some answers here. I made an account and I searched my problem here, but couldn't find it ( I was only looking at the first page of the results, because let's be honest, if that's not the top result, then it wasn't reported).
So me and my friend were flying in a server, far out in the end Dimension, we let our computers running during the night so that we reach our destination faster. The next morning, we woke up and found out that we are flying in the void. Looking at our map-plugin we found out that the map didn't show anything since 30-50k blocks. We rejoined because we thought it was a glitch, but it wasn't.
We didn't know what was happening, and we thought it was something the owner configured, since it was an anarchy server. When we reached the terrain, we found something like this (image 1).
I really didn't know what was going on, I looked up if the bug was known, trying to find an explanation for this, with no result.
So I decided to find out why exactly the end wasn't generating anymore. I created a new world, tped to the coords, and found out that this bug is occuring in ALL worlds in minecraft 1.15.2. because I already travelled 50k beyone that edge, I was certain that it would be like that for a long time. Though when I tped to 30 million the end the end looked normal.
I looked at the exact chunk where the world wasn't loading anymore, and found out that this chunk was 2^15th chunk away from 0,0. I tped to the 2^15th chunk in one axis to check my theory, and found this (image 2).
Because I knew that at some point the end was generating again, and I knew when it stopped generating, I took a guess and tped myself to the 2^16th chunk, which is double the distance from spawn. No surprise there: both the corner and the edge that stopped generating at 2^15th the distance to spawn started to generate there again (look at image 3 and 4 respectively).
I wondered if this bug happened periodically, so I tped myself 3 times the distance of 2^15 chunks from spawn. And yes, it again made a transation between void and normal end biome. But it wasn't in the right direction. Based on what I knew the void should have begun there again, but instead the normal terrain begun there again. which meant that between 2 times the distance of 2^15 chunks, and 3 times the distance of 2^15 chunks from spawn, there was yet another transition.
Unfortunately, the transition wasn't normal (image 5), it was completely random (or I didn't see a regularity here), which is where I drew the line and decided to report here. The farther out you go, the more complicated and random the transitions seem to get.
What I can still confirm is that every time you reach a radius x*2^15th chunks (if x is an integer), you make a sharp transition, like the ones you see on those images, from void to normal terrain, or from normal terrain to void, depending on the previous state, which can change because there are irregular transitions inside those transitions.
Now I know I wrote a lot, and it is getting patched rn in the newest snapshot, but the fact I didn't see ANY reports whatsoever just forced me to report this. I'm not sure how helpful that was, but it makes me feel better when I know that the issue is known.
Tl;dr: End 2 doesn't generate anymore after getting to a certain radius, but continues when you reach double that radius, and then changes irregularly, while still changing regularly at that radius.
How to recreate:
Open a world in Minecraft 1.15.2, go to the end, tp to 2^15*16(or 524288) 255 0.
For diagonal edges half the previous number (262144 255 262144).
Linked issues
duplicates 1
Attachments
Comments 4
Quick update: After 2 days without any responses, and now even another guy finding the same bug, I decided to check if there are other versions with that problem, will make another comment that says what versions I tested and what the results were.
I plan to test every version since the end 2 update and then look at the snapshot 20w16a.
Second bug thread:
Update 1:
I tested the last version of every major version since 1.9 (the end 2 update), and here are the results:
1.9.4: No bug
1.10.2: No bug
1.11.2: No bug
1.12.2: No bug
1.13.2: No bug
1.14.4: Bugged
1.15.2: Bugged
Will now look closer at the snapshot and the 1.14.x to see where exactly it started to appear, and if it's fixed now.
Update 2:
The bug started to appear in the initial 1.14 version AND is still there in the newest snapshot, 20w16a. I did everything I could do while testing these things out, the only further thing would be to look into the code myself to find the bug, but since Minecraft isn't open source I will leave that to the developers, now I just hope that this issue finally gets attention before 1.16 comes out.
I just found another thread with the same issue that was made in december, again no answers....
Third bug thread:
My issue can be closed now, since it's a dupe of an existing issue.
Also have to reclaim where it starts, as the issue states it starts earlier. Interestingly though my transitions are still correctly predicted, though not all of the transitions.
Thank you for your report!
We're actually already tracking this issue in MC-159283, so I resolved and linked 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 in the future to see if the issue has already been reported.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 Game Wiki
Forgot image 5