MineKhan
MineKhan copied to clipboard
Willard21
Wobbly World Far From Origin
Here is a very astonishing glitch I found in minekhan it's a spin-off https://www.khanacademy.org/computer-programming/minecraft-but-broken/4914589619929088
You may notice that your x, y coordinates are VERY VERY high, meaning that we hundred of thousands of blocks away from spawn which makes the game TOO glitchy
If you are a Minecraft nerd then you might know about the far lands which are basically on the topic of how infinite can you make procedurally generated terrain if you do not know what far lands is here is a summary :
The Far Lands is a terrain bug that appears upon the overflowing of a noise generator, most notably the low and high noise overflow 12,550,821 blocks from the origin of the Minecraft world. There are other parts of Far Lands called Farther Lands and Corner Far Lands.
Lol I've known about this since before I released the game. But noise overflow has nothing to do with it, unlike the real Minecraft farlands. This is caused by too low float precision in the vertex shaders. It's the highest precision available though. It's fixable, but would cause a universal performance decrease. Since people basically have to hack the game to get out there, it's not worth it.
@Willard , so you are saying it's not possible to get to the glitch on foot so it's only possible by hacking or modyfying.
oh my god
i was just trying to make a switch
Can you make a project and try to change the x and y to astronomically levels and then make a spin off and send here ?
@Hacker1254
Yea, it will take many years
I don't think you even could make it that far no matter how much time you have because the game will run out of memory.
Lol yeah, chunks stay loaded forever after they're generated. So would definitely run out of memory.
@SnehasishCodez
@willard , so you are saying it's not possible to get to the glitch on foot so it's only possible by hacking or modyfying.
I actually did get the glitch on foot. I put something like this in the url box:
javascript:player.x = 1000000
Well the obvious solution to this is to remove global access to the player object then, since this is clearly something everybody does during normal gameplay.