The Far Lands is a terrain generation bug that appears when the noise generators responsible for creating the shape of terrain stop functioning properly. This results in a large, spongy wall of terrain appearing around 12,550,821 blocks from the origin of the Minecraft world.
Currently, across all currently-developed editions, the Far Lands only occur either in older versions of the game or via modding to remove the patches which prevent them from occurring.
The Far Lands still retain a legacy as one of the franchise's most famous glitches, even being referenced in other official games such as Minecraft: Story Mode and Super Smash Bros. Ultimate.
This article includes a list of related items that share the same name (or similar names). If an internal link led you here, you may wish to change the link to point directly to the intended article.Contents
General information[]
What the Far Lands are not[]
Due to many occurrences at high distance being lumped together with each other, confusion often arises as to what is related to or caused by the Far Lands, and what is not. The following is a list of things which are commonly misattributed to being a product, effect or even type of the Far Lands, despite not being so.
- Precision loss errors are not caused by the Far Lands
The position where the world appears to render is considerably offset at the point where the Far Lands begin in Beta 1.7.3 and earlier, with a magnitude of one block, with the player appearing to be at the edges and corners of blocks at all times.
However, this is purely a floating-point bug, and exists whether or not the Far Lands themselves do. This can be demonstrated by the following:
- Noticing that the precision loss is a gradual change, which increases at each power of 2. This is in stark contrast to the Far Lands, which happen immediately due to integer overflow.
- Backporting a Superflat world (with flat terrain where the Far Lands would be) from 1.1 to Beta 1.7.3, and noticing that the effect persists in said version, proving that it's clearly not linked to terrain. While Far Lands chunks will still generate outside of what superflat chunks were generated in 1.1, these still are unrelated.
- Modding the game can be done to either patch out this precision loss issue or the Far Lands individually. This proves their existence to be completely independent.
- Generating the Far Lands in any version between the March 27 and June 18 builds of Infdev inclusive. Whereas the Far Lands clearly generate in these versions, the precision loss bug was first introduced in the June 24th build.
This is also true of every other precision loss bug, especially those which were not fixed in Beta 1.8 and persisted into later versions after the Far Lands were removed in said version, demonstrating that they are two completely different things which are only associated with each other due to happening at high distances.
- The Stripe Lands are not a type of Far Lands
The Stripe Lands, a mostly Bedrock Edition-exclusive phenomenon which can only be seen in Java Edition through extensive modding, are another example of floating-point precision loss, and are not a terrain bug.
- Fake chunks are not caused by the Far Lands
"Fake" chunks at the world boundary are another anomaly that happens at high distances. Occurring considerably past the Far Lands' beginning, they are commonly said to be a "part" or "layer" of the Far Lands. While they are among the interesting effects which can be experienced when moving high distances from the world origin, their occurrence is a distinct phenomenon, and, to an extent, actually intended. This is further reinforced by them being at a rather round number (32 million), rather than the seemingly overall arbitrary 12,550,824 of the Far Lands, or power-of-two values such as 16,777,216 where precision loss worsens.
It is likely that them occurring past the Far Lands is accidental. Their original positioning at 32,000,000 was likely done to make the Far Lands, then at 33,554,432, inaccessible without modifying the game. However, when terrain generation was redone, the Far Lands moved closer to their familiar position of 12,550,824, despite the boundary remaining at 32,000,000, meaning that the Far Lands were once more accessible, with the boundary no longer making them inaccessible as intended; it is likely that Notch would not have thought to check this at the time due to the distances being ludicrous. Fake chunks beginning in Alpha v1.2.0 (as opposed to the void seen in prior versions) are also likely unintentional, probably arising due to changes in chunk handling for biomes, the Nether, or both, and would have presumably also flown under the radar given their inaccessibility in normal gameplay without external editors.
- Hard limits are not caused by the Far Lands
While the Far Lands themselves are technically a hard limit due to arising from integer overflow, they are treated solely as a terrain phenomenon, and the game still functions fine with them. Integer overflows in other cases such as player position are much more dangerous and much harder to reach, and are considered separately.
Types of Far Lands[]
The Far Lands comprise a very, very wide array of terrain generation bugs. The effects vary depending on which noise generator breaks (for traditional Far Lands, "low noise" and "high noise" are jointly responsible), as well as the player's distance on each axis (the "Edge Far Lands" refer to when noise breaks on only one axis, the "Corner Far Lands" on two, and the "Vertex Far Lands" on three).
Other noise generators are capable of breaking down. Selector noise, a noise generator which determines whether low noise or high noise is used at a given position in the world, breaks down 80 times further than low and high noise by default, giving rise to what is known as the "Farther Lands".
A full list of Java Edition noise generators known to break down and give rise to their own unique effects, many of which require mods to see, is as follows. Note that it assumes that the X and Z axes are identical, and ignores the Y axis; in many cases, the Y axis has a different value from the X and Z axes, whereas in other cases the noise generator is entirely 2D.
| Noise generator | Breaks down at... (32-bit) |
Version range | Notes | |
|---|---|---|---|---|
| First | Last | |||
| Low noise | 12,550,824 | inf-20100327 | present[n 1] | Jointly responsible for the Far Lands |
| High noise | ||||
| Selector noise | 1,004,065,924 | inf-20100327 | present[n 1] | Responsible for the Farther Lands |
| Depth noise | 42,949,672 | [more information needed] | present[n 1] | Causes the terrain to rise up several blocks. "Stretching effects" are rare. Impossible to see unless made to start before low and high noise overflow. |
| Scale noise | 7,662,742,722 | [more information needed] | Beta 1.7.3 | Superseded by biome-based terrain height in Beta 1.8. |
| Classic world noise | 33,554,432 | probably the first version that generated terrain | inf-20100325 | Causes the famous "stone wall" of Infdev. |
| Island carver noise | 933,688,542 | [more information needed] | in-20100223 | Used to create Floating maps in Indev. Due to their limited world size, this breaks far beyond what can generate. |
| Soil depth | 34,359,738,368 | [more information needed] | present[n 1] | Causes large regions of exposed stone in earlier versions, or gravel in later versions. |
| Sand beaches | 68,719,476,736 | [more information needed] | Beta 1.7.3 | Determines whether beaches use sand or not. In the Nether, this controls soul sand. |
| Gravel beaches | 68,719,476,736 | [more information needed] | Beta 1.7.3 | Determines whether beaches use gravel or not. Also exists in the Nether for gravel. |
Fandom[]
One player known as KilloCrazyMan is known to have walked to the Far Lands in vanilla Minecraft, beginning the journey in September 2019 and reaching them nine months later in June 2020. Upon arrival, a USD$10,000 donation was awarded to him by Notch for his efforts.[1]
In Bedrock Edition, the Far Lands were first introduced with the infinite terrain generation in 0.9.0 alpha, and were removed in 1.17.30 (beta 1.17.20.20).
