In 1.6.4 and earlier the game creates "fake chunks", which are not actually fake (the game saves them to disk) but the player can't interact with them, nor does it decorate them with trees and stuff, only the surface grass/dirt/sand and caves, since the methods that read block data are coded to not return anything after +/- 30 million (an entirely arbitrary limit; I modded the game to remove it and the world generated normally. The server will still kick you after 32 million unless you also edit that out, and edit the /tp command to allow larger values, then the limit is +/- 2.147 billion, the limit of a 32 bit integer).
Also, this should be moved to a different section (discussion?) since off-topic is not for discussing Minecraft.
The funny thing here doe is that when i ran the world on minecraft 1.2.1, it didn't request to re render the world but the whole graph was messed up (XYZ graph), it showed me that im on a normal spot (something about 0-30 on X/Y/Z) but when i went about 20 blocks from where the world border was meant to be, my game started acting weird, it just started to constantly shake (didnt crash) and once my character just started spinning on a very high speed non stop.
I'm not sure what happened in 1.2.1 but going past the world border (or previous boundary/Far Lands/etc) is not really intended and is normally never an issue due to the world size; I noticed that this thread is now in the support section for unmodded clients, but this is in no way considered to be a bug - if you posted this to the official bug tracker they would just write it off as "invalid"/"works as intended"/"won't fix" and also admonish you for downgrading with an additional statement that older versions are no longer supported; even the most game-breaking bugs will never be fixed. For example, see this bug report: https://bugs.mojang.com/browse/MC-3383
Also, if you want to see what is beyond the 1.7+ world border I suggest starting in 1.6.4 since bad things will happen if you downgrade.
I opened a world on minecraft 1.7.10 and TPed to border,
Opened the same world on 1.2.1 and crossed the border for about 20 blockes an player started to act weird,
Opened again at 1.7.10 and the play was stuck and unable to move,
Opened the world on minecraft 1.4.6 and the world started to continue rendering without minecraft's physics,
i was able to go through the world, be underwater without being underwater (same thing with lava).
In 1.6.4 and earlier the game creates "fake chunks", which are not actually fake (the game saves them to disk) but the player can't interact with them, nor does it decorate them with trees and stuff, only the surface grass/dirt/sand and caves, since the methods that read block data are coded to not return anything after +/- 30 million (an entirely arbitrary limit; I modded the game to remove it and the world generated normally. The server will still kick you after 32 million unless you also edit that out, and edit the /tp command to allow larger values, then the limit is +/- 2.147 billion, the limit of a 32 bit integer).
Also, this should be moved to a different section (discussion?) since off-topic is not for discussing Minecraft.
TheMasterCaver's First World - possibly the most caved-out world in Minecraft history - includes world download.
TheMasterCaver's World - my own version of Minecraft largely based on my views of how the game should have evolved since 1.6.4.
Why do I still play in 1.6.4?
The funny thing here doe is that when i ran the world on minecraft 1.2.1, it didn't request to re render the world but the whole graph was messed up (XYZ graph), it showed me that im on a normal spot (something about 0-30 on X/Y/Z) but when i went about 20 blocks from where the world border was meant to be, my game started acting weird, it just started to constantly shake (didnt crash) and once my character just started spinning on a very high speed non stop.
I'm not sure what happened in 1.2.1 but going past the world border (or previous boundary/Far Lands/etc) is not really intended and is normally never an issue due to the world size; I noticed that this thread is now in the support section for unmodded clients, but this is in no way considered to be a bug - if you posted this to the official bug tracker they would just write it off as "invalid"/"works as intended"/"won't fix" and also admonish you for downgrading with an additional statement that older versions are no longer supported; even the most game-breaking bugs will never be fixed. For example, see this bug report: https://bugs.mojang.com/browse/MC-3383
Also, if you want to see what is beyond the 1.7+ world border I suggest starting in 1.6.4 since bad things will happen if you downgrade.
TheMasterCaver's First World - possibly the most caved-out world in Minecraft history - includes world download.
TheMasterCaver's World - my own version of Minecraft largely based on my views of how the game should have evolved since 1.6.4.
Why do I still play in 1.6.4?