Minecraft:Far Lands (Java Edition)/After Beta 1.8 - Revision history

SyncBot: Sync: updated from Minecraft

2026-07-29T11:10:20Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:10, 29 July 2026
Line 101:		Line 101:
	\|		\|
	* The Far Lands begin degrading into thinner slices due to the decay process, in four stages at the aforementioned distances. However, there are no comb-like artifacts nor dotted lines of terrain generation, as lerp failure, which was responsible for these artifacts, was fixed in [[Minecraft:Beta 1.9-pre2]].		* The Far Lands begin degrading into thinner slices due to the decay process, in four stages at the aforementioned distances. However, there are no comb-like artifacts nor dotted lines of terrain generation, as lerp failure, which was responsible for these artifacts, was fixed in [[Minecraft:Beta 1.9-pre2]].
	* Additionally, the starting points for each stage is extremely variable and will ~~doffer~~ by seed, so an exact distance cannot be stated. However, it is known that it begins within this range.		* Additionally, the starting points for each stage is extremely variable and will differ by seed, so an exact distance cannot be stated. However, it is known that it begins within this range.
	\|		\|
	\|-		\|-
Line 107:		Line 107:
	\|		\|
	* The Far Lands end completely at this point, though the end point is different on each axis, as they continue until at least 20 quindecillion on the Z axis. This marks the end of ''Minecraft'' terrain generation, unless extensive modding on top of this patches the noise overflow and Far Lands.		* The Far Lands end completely at this point, though the end point is different on each axis, as they continue until at least 20 quindecillion on the Z axis. This marks the end of ''Minecraft'' terrain generation, unless extensive modding on top of this patches the noise overflow and Far Lands.
	* As stated ~~befofe~~, the end point is inconsistent due to how the decay works and does not result in a specific point each time, and will vary by seed.		* As stated before, the end point is inconsistent due to how the decay works and does not result in a specific point each time, and will vary by seed.
	\|[[File:Fringe Lands end.png\|thumb\|right\|240px]]		\|[[File:Fringe Lands end.png\|thumb\|right\|240px]]
	\|}		\|}
Line 121:		Line 121:
	\| style="color: #000033; background: #D3D3D3" \| X/Z: ±{{abbr\|2.4317×10<sup>27</sup>\|2,431,799,127,616,978,452,662,452,220}}		\| style="color: #000033; background: #D3D3D3" \| X/Z: ±{{abbr\|2.4317×10<sup>27</sup>\|2,431,799,127,616,978,452,662,452,220}}
	\|		\|
	* Starting in [[Minecraft:Java Edition 1.18.2\|1.18.2]], the Far Lands abruptly ~~stop completely~~ and give way to an endless ocean of [[Minecraft:water]] and/or [[Minecraft:lava]]. This, as well as the lack of bedrock floor is due to <code>NoiseRouter</code> failing and rolling over to "NaN", As such, this is the end of modern ''Minecraft'' terrain generation.		* Starting in [[Minecraft:Java Edition 1.18.2\|1.18.2]], the Far Lands abruptly end at this point and give way to an endless ocean of [[Minecraft:water]] and/or [[Minecraft:lava]]. This, as well as the lack of bedrock floor is due to <code>NoiseRouter</code> failing and rolling over to "NaN", though [[Minecraft:aquifers]] still generate. As such, this is the end of modern ''Minecraft'' terrain generation.
	\|[[File:Endless ocean at extreme large distances.png\|thumb\|240px\|Endless ocean mixed with lava at extreme distances.]]		\|[[File:Modern Far Lands cutoff.png\|thumb\|240px\|The end of the modern Far Lands in 1.20.1 at 2.42 octillion blocks, giving way to endless lava oceans and suspended [[aquifers]]]]
			\|-
			\| style="color: #000033; background: #D3D3D3" \| ?
			\|
			* At even larger distances, even aquifers seem to begin failing to generate, leaving only an ocean of water or lava afterwards.
			**This is most notable and observed when teleporting to the previous degradation points mentioned before.
			\| [[File:Endless ocean at extreme large distances.png\|thumb\|240px\|Endless ocean mixed with lava at extreme distances.]]
	\|}		\|}

SyncBot: Sync: updated from Minecraft

2026-07-28T11:07:00Z

Sync: updated from Minecraft

@@ Line 85: / Line 85: @@
 The only way to see the new location of the Far Lands is by using a BigInteger mod that does not patch the fix. Only modern versions of Minecraft have managed to produced this, as any 64-bit mod incorrectly undoes the patch and then converts coordinates to 64-bit, resulting in a starting point that is not true to vanilla Minecraft. The only versions known to correctly have a mod to do so is [[Minecraft:Java Edition 1.20.1|1.20.1]], [[Minecraft:Java Edition 1.20.4|1.20.4]] and [[Minecraft:Java Edition 1.21.4|1.21.4]].{{note|BigInteger mods exist for versions [[Minecraft:Java Edition 1.3.2|1.3.2]] and [[Minecraft:Java Edition 1.12.2]], but these do not contain the modulo patch or are incorrectly patched, resulting in a false starting position for the Far Lands. The "decay" stages listed in the table are accurate even in these modified versions, though very little documentation exists so far of the Far Lands structure in versions after the [[Minecraft:Java Edition 1.18.2]] change.}}
 {| class="wikitable"
 !Coordinates
@@ Line 96: / Line 97: @@
 **Regardless of the structure, they will appear very stretched out and lack the normal type of terrain normally associated with the Far Lands, due to many other terrain generator features haven broken down by this point. This is why the appearance differs drastically between versions without the modulo patch and those with the patch.
 |[[File:Modern Far Lands start.png|thumb|240px|The Far Lands generating at the new limit in [[Java Edition 1.20.1|1.20.1]] with the solid wall structure]]
 |-
 | ~X/Z: ±{{abbr|7–9×10<sup>48</sup>|7,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000 to 9,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000}}
@@ Line 113: / Line 109: @@
 * As stated befofe, the end point is inconsistent due to how the decay works and does not result in a specific point each time, and will vary by seed.
 |[[File:Fringe Lands end.png|thumb|right|240px]]
 |}

SyncBot: Sync: updated from Minecraft

2026-07-27T11:05:17Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:05, 27 July 2026
Line 97:		Line 97:
	\|[[File:Modern Far Lands start.png\|thumb\|240px\|The Far Lands generating at the new limit in [[Java Edition 1.20.1\|1.20.1]] with the solid wall structure]]		\|[[File:Modern Far Lands start.png\|thumb\|240px\|The Far Lands generating at the new limit in [[Java Edition 1.20.1\|1.20.1]] with the solid wall structure]]
	\|-		\|-
	\| X: ±{{abbr\|8.~~1751×10~~<sup>48</sup>\|8,~~175~~,~~100~~,~~408~~,~~620~~,~~645~~,~~429~~,~~587~~,~~604~~,~~206~~,~~419~~,~~312,153,467,715,321,856~~}}<hr>X: ±{{abbr\|~~8.5766×10~~<sup>48</sup>\|8,~~576~~,~~620~~,~~983~~,~~668~~,~~390~~,~~695~~,~~654~~,~~176~~,~~953~~,~~195~~,~~873~~,~~545~~,~~661~~,~~439~~,~~803~~,~~392}}<hr>X/Z: ±{{abbr\|9.1762×10<sup>48</sup>\|~~9,~~176~~,~~239~~,~~949~~,~~795~~,~~123~~,~~308~~,~~594~~,~~625~~,~~193~~,~~335~~,~~189~~,~~314~~,~~391~~,~~974~~,~~608~~,~~896~~}}		\| style="color: #000033; background: #D3D3D3" \| ~X/Z: ±{{abbr\|2.42×10<sup>27</sup>\|2,420,000,000,000,000,000,000,000,000}}
			\|
			* Starting in [[Minecraft:Java Edition 1.18.2\|1.18.2]], at around this distance,{{needs testing}} the Far Lands abruptly stop completely and give way to an endless ocean of [[Minecraft:water]] and/or [[Minecraft:lava]]. This, as well as the lack of bedrock floor is due to <code>NoiseRouter</code> failing and rolling over to "NaN", but still causing [[Minecraft:aquifers]] to generate. As such, this is the end of modern ''Minecraft'' terrain generation.
			\|[[File:Endless ocean at extreme large distances.png\|thumb\|240px\|Endless ocean mixed with lava at extreme distances.]]
			\|-
			\| ~X/Z: ±{{abbr\|7–9×10<sup>48</sup>\|7,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000 to 9,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000}}
	\|		\|
	* The Far Lands begin degrading into thinner slices due to the decay process, in four stages at the aforementioned distances. However, there are no comb-like artifacts nor dotted lines of terrain generation, as lerp failure, which was responsible for these artifacts, was fixed in [[Minecraft:Beta 1.9-pre2]].		* The Far Lands begin degrading into thinner slices due to the decay process, in four stages at the aforementioned distances. However, there are no comb-like artifacts nor dotted lines of terrain generation, as lerp failure, which was responsible for these artifacts, was fixed in [[Minecraft:Beta 1.9-pre2]].
			* Additionally, the starting points for each stage is extremely variable and will doffer by seed, so an exact distance cannot be stated. However, it is known that it begins within this range.
	\|		\|
	\|-		\|-
	\| X: ±{{abbr\|1.~~0299×10~~<sup>49</sup>\|10,~~299~~,~~981~~,~~089~~,~~825~~,~~331~~,~~303~~,~~027~~,~~420~~,~~223~~,~~646~~,~~772~~,~~450~~,~~634~~,~~036~~,~~674~~,~~560}}<hr>Z:±~{{abbr\|2×10<sup>49</sup>\|~~20,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000}}		\| X/Z: ±~{{abbr\|1.5–2×10<sup>49</sup>\|15,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000 to 20,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000}}
	\|		\|
	* The Far Lands end completely at this point, though the end point is different on each axis, as they continue until at least 20 quindecillion on the Z axis. The only thing that generates after this is an endless bedrock ocean.<ref name="Beyond 10e308">[https://youtu.be/JXdq7G5qUlQ?is=4IvkN92Ig5_EDZsJ Beyond 2^1024 blocks in Minecraft 1.3.2 BigInt mod], YouTube, May 14, 2026</ref> This marks the end of ''Minecraft'' terrain generation, unless extensive modding on top of this patches the noise overflow and Far Lands.		* The Far Lands end completely at this point, though the end point is different on each axis, as they continue until at least 20 quindecillion on the Z axis. This marks the end of ''Minecraft'' terrain generation, unless extensive modding on top of this patches the noise overflow and Far Lands.
			* As stated befofe, the end point is inconsistent due to how the decay works and does not result in a specific point each time, and will vary by seed.
	\|[[File:Fringe Lands end.png\|thumb\|right\|240px]]		\|[[File:Fringe Lands end.png\|thumb\|right\|240px]]
	\|-
	~~\| ?~~
	\|
	* Starting in [[Minecraft:Java Edition 1.18.2\|1.18.2]], at an unknown distance past the above,{{needs testing}} the Far Lands abruptly stop completely and give way to an endless ocean of [[Minecraft:water]] and/or [[Minecraft:lava]]. This, as well as the lack of bedrock floor is due to the changes in cave generation but still causing [[Minecraft:aquifers]] to generate. As such, this is the end of modern ''Minecraft'' terrain generation.
	~~\|[[File:Endless ocean at extreme large distances.png\|thumb\|240px\|Endless ocean mixed with lava at extreme distances.]]~~
	\|}		\|}

SyncBot: Sync: updated from Minecraft

2026-07-26T11:05:37Z

Sync: updated from Minecraft

Show changes

SyncBot: Sync: updated from Minecraft

2026-07-19T11:06:30Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:06, 19 July 2026
Line 1:		Line 1:
	#REDIRECT [[Minecraft:Far Lands (Java Edition)]]		#REDIRECT [[Minecraft:Far Lands (Java Edition)]]
			{{Redr\|merge}}

SyncBot: Sync: updated from Minecraft

2026-07-18T11:08:04Z

Sync: updated from Minecraft

Show changes

SyncBot: Sync: updated from Minecraft

2026-07-15T11:05:19Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:05, 15 July 2026
Line 169:		Line 169:
	\|		\|
	* The Far Lands begin generating at this distance due to the overflowing of the modified noise value. This is due to a change in the Far Lands patch, which now takes the double Noise Coordinate, converts it to a 64-bit integer, and then divides it by 33,554,432.		* The Far Lands begin generating at this distance due to the overflowing of the modified noise value. This is due to a change in the Far Lands patch, which now takes the double Noise Coordinate, converts it to a 64-bit integer, and then divides it by 33,554,432.
	\|[[File:~~Farlands1113~~.png\|thumb\|240px\|The Far Lands generating in a modern version of Minecraft]]		* Groups of infinite tunnels like in prior iterations still generate but only on certain occassions, with most results being a solid wall with very few tunnels
			* As before, the offset for the start may be measured in millions of blocks, but the Far Lands generally begin around this distance.
			\|[[File:Modern Far Lands start.png\|thumb\|240px\|The Far Lands generating in a modern version of Minecraft]]
			\|-
			\| ?
			\|
			* At an unknown distance past the above, the Far Lands abruptly stop completely and give way to an endless ocean of [[Minecraft:water]] and/or [[Minecraft:lava]]. This, as well as the lack of bedrock floor is due to the changes in cave generation but still causing [[Minecraft:aquifers]] to generate. As such, this is the end of modern ''Minecraft'' terrain generation.
			\|[[File:Endless ocean at extreme large distances.png\|thumb\|240px\|Endless ocean mixed with lava at extreme disfances.]]
	\|}		\|}

	~~The same breakdowns into the Fringe Lands and eventually endless bedrock ocean still occur at the same distances as before.~~

	== Effects ==		== Effects ==

SyncBot: Sync: updated from Minecraft

2026-07-12T11:09:25Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:09, 12 July 2026
Line 92:		Line 92:
	* From [[Minecraft:Java Edition 1.3.1\|1.3.1]] until [[Minecraft:Java Edition 1.7.10\|1.7.10]], and again from [[Minecraft:Java Edition 1.9\|1.9]] until [[Minecraft:Java Edition 1.13.2\|1.13.2]], they will generate beyond X/Z: ±32,000,000, although they cannot be accessed due to the player being kicked for being in an "Illegal position" after 32 million blocks in the former versions.		* From [[Minecraft:Java Edition 1.3.1\|1.3.1]] until [[Minecraft:Java Edition 1.7.10\|1.7.10]], and again from [[Minecraft:Java Edition 1.9\|1.9]] until [[Minecraft:Java Edition 1.13.2\|1.13.2]], they will generate beyond X/Z: ±32,000,000, although they cannot be accessed due to the player being kicked for being in an "Illegal position" after 32 million blocks in the former versions.
	* From [[Minecraft:Java Edition 1.8\|1.8]] until [[Minecraft:Java Edition 1.8.9\|1.8.9]], the Far Lands will simply stop genersting at the [[Minecraft:world boundary]] of 30 million blocks, identical to pre-[[Minecraft:Alpha v1.2.0]] and Infdev versions ending at 32 million.		* From [[Minecraft:Java Edition 1.8\|1.8]] until [[Minecraft:Java Edition 1.8.9\|1.8.9]], the Far Lands will simply stop genersting at the [[Minecraft:world boundary]] of 30 million blocks, identical to pre-[[Minecraft:Alpha v1.2.0]] and Infdev versions ending at 32 million.
	*From [[Minecraft:Java Edition 1.14\|1.14]] onwards, because of the switch to a packed coordinate system, the Far Lands will either turn completely black due to lighting breaking (in 1.14) or stop rendering (in modern versions at least later then [[Minecraft:Java Edition 1.20.4\|1.20.4]]) at X/Z: ±33,554,432, both due to packed coordinates ~~overflowinf~~ at this limit. Attempting to go further is impossible as the game will crash [[Minecraft:Java Edition hard limits\|if a chunk is rendered beyond this point]].		*From [[Minecraft:Java Edition 1.14\|1.14]] onwards, because of the switch to a packed coordinate system, the Far Lands will either turn completely black due to lighting breaking (in 1.14) or stop rendering (in modern versions at least later then [[Minecraft:Java Edition 1.20.4\|1.20.4]]) at X/Z: ±33,554,432, both due to packed coordinates overflowing at this limit. Attempting to go further is impossible as the game will crash [[Minecraft:Java Edition hard limits\|if a chunk is rendered beyond this point]].
	[[File:Fl 1.11.2int overload.png\|alt=200 Blocks from the 32-bit integer limit where world rendering glitches out. At 2,147,483,520, the game crashes.\|thumb\|The Far Lands at the 32-bit integer limit with terrain flickering in and out.]]		[[File:Fl 1.11.2int overload.png\|alt=200 Blocks from the 32-bit integer limit where world rendering glitches out. At 2,147,483,520, the game crashes.\|thumb\|The Far Lands at the 32-bit integer limit with terrain flickering in and out.]]
	In versions after 1.8, if the above is combined with a mod that removes the [[Minecraft:world boundary]], and patches the packed coordinate overflow (in 1.14 and later versions) ~~- such as “Beyond the Barrier",~~ then the Far Lands can generate out to the 32-bit limit of X/Z: ±2,147,483,647. In some earlier versions, sometimes ~~fependent~~ on the exact mod, the same glitches and progression from pre-Beta 1.8 will occur, such as terrain flickering at high distances until the game crashes shortly before the 32-bit limit and world rendering stops completely. More modern versions will end up generating without rendering issues straight up until the 32-bit integer limit.		In versions after 1.8, if the above is combined with a mod that removes the [[Minecraft:world boundary]], and patches the packed coordinate overflow (in 1.14 and later versions) then the Far Lands can generate out to the 32-bit limit of X/Z: ±2,147,483,647. In some earlier versions, sometimes dependent on the exact mod, the same glitches and progression from pre-Beta 1.8 will occur, such as terrain flickering at high distances until the game crashes shortly before the 32-bit limit and world rendering stops completely. More modern versions will end up generating without rendering issues straight up until the 32-bit integer limit.

	===64-bit & BigInteger mod===		===64-bit & BigInteger mod===
Line 128:		Line 128:
	\|		\|
	* The 64-bit limit and the maximum the Far Lands will generate using a 64-bit mod, since world renderer breaks completely at this distance in this case, giving way to an endless void like in the 32-bit cases. The game will always crash when approaching this limit. Due to the effects mentioned above however, it will be almost completely invisible, if a Stripe Lands fix is not enabled.		* The 64-bit limit and the maximum the Far Lands will generate using a 64-bit mod, since world renderer breaks completely at this distance in this case, giving way to an endless void like in the 32-bit cases. The game will always crash when approaching this limit. Due to the effects mentioned above however, it will be almost completely invisible, if a Stripe Lands fix is not enabled.
	\|		\|[[File:64-bit limit Far Lands end.png\|thumb\|right\|240px\|Empty void after rendering breaks at the 64-bit limit at X: 9,223,372,036,854,776,000.]]
	\|}		\|}

	Beyond this point, a ~~BigInt~~ mod is required to go even further. ~~Additionally~~, ~~because of~~ the ~~BigInteger mod~~, ~~most of the movement precision issues seemingly don~~'t ~~occur now at such distances~~.		Beyond this point, a 128-bit or BigInteger mod is required to go even further. Because such mods are currently only known to exist are for [[Minecraft:Java Edition 1.3.1\|1.3.1]] and later, all chunks rendered this far out in these versions, in conjecture with the previous distances will be treated as fake chunks, having been so since 30 million blocks out. Additionally, terrain flickering doesn't happen as these patches usually fix them.

	{\| class="wikitable"		{\| class="wikitable"
Line 143:		Line 143:
	\|[[File:1.2.5 biome fill Edge Far Lands.png\|thumb\|240px]]		\|[[File:1.2.5 biome fill Edge Far Lands.png\|thumb\|240px]]
	\|-		\|-
	\| X: ±{{abbr\|8.5766×10<sup>48</sup>\|8,576,620,983,668,390,695,654,176,953,195,873,545,661,439,803,392}}<hr>Z: ±{{abbr\|9.~~17×10~~<sup>48</sup>\|~~9170000000000000000000000000000000000000000000000~~}}		\| X: ±{{abbr\|8.5766×10<sup>48</sup>\|8,576,620,983,668,390,695,654,176,953,195,873,545,661,439,803,392}}<hr>Z: ±{{abbr\|9.176×10<sup>48</sup>\|9,176,239,949,795,123,308,594,625,193,335,189,314,391,974,608,896}}
	\|		\|
	* The Fringe Lands begin generating as a result of the Far Lands progressively beginning to break down. These are are the same occurance that happens on {{BE}}, but it happens at the 64-bit equivalent. They progressively break down into thinner and thinner slices, before becoming scattered cubes increasingly seperated.		* The Fringe Lands begin generating as a result of the Far Lands progressively beginning to break down. These are are the same occurance that happens on {{BE}}, but it happens at the 64-bit equivalent. They progressively break down into thinner and thinner slices, before becoming scattered cubes increasingly seperated.
			* On the Z Axis, it starts slightly later, and seem to break down much more slowly.
	\|[[File:The True Fringe Lands.png\|thumb\|240px]]		\|[[File:The True Fringe Lands.png\|thumb\|240px]]
	\|-		\|-
	\| X/Z: ±{{abbr\|4.119992×10<sup>49</sup>\|41,199,924,359,301,325,212,109,680,894,587,089,802,536,146,698,256}}		\| X/Z: ±{{abbr\|1.0299×10<sup>49</sup>\|10,299,981,089,825,331,303,027,420,223,646,772,450,634,036,674,560}}–{{abbr\|4.119992×10<sup>49</sup>\|41,199,924,359,301,325,212,109,680,894,587,089,802,536,146,698,256}}
	\|
	* The Fringe Lands, and by definition, the Far Lands, end completely at this point, having been reduced to spaced out dirt blocks underwater at Y: 32. The only thing that generates after this point is an endless bedrock ocean.<ref name="Beyond 10e308">[https://youtu.be/JXdq7G5qUlQ?is=4IvkN92Ig5_EDZsJ Beyond 2^1024 blocks in Minecraft 1.3.2 BigInt mod], YouTube, May 14, 2026</ref> This marks the end of ''Minecraft'' terrain generation, unless extensive modding on top of this patches the noise overflow and Far Lands.
	\|		\|
			* The Fringe Lands, and by definition, the Far Lands, end completely around this point, having been reduced to spaced out dirt blocks or very few long lines of grass blocks. The only thing that generates after this is an endless bedrock ocean.<ref name="Beyond 10e308">[https://youtu.be/JXdq7G5qUlQ?is=4IvkN92Ig5_EDZsJ Beyond 2^1024 blocks in Minecraft 1.3.2 BigInt mod], YouTube, May 14, 2026</ref> This marks the end of ''Minecraft'' terrain generation, unless extensive modding on top of this patches the noise overflow and Far Lands.
			* Because of the very high distances and, the exaxt breakdown will vary from map to map and direction and is impossible to pinpoint. In most cases the Fringe Lands will end at X/Z: ±{{abbr\|4.119992×10<sup>49</sup>\|41,199,924,359,301,325,212,109,680,894,587,089,802,536,146,698,256}}, although some cases have observed them persisting until X/Z: ±10<sup>59</sup>
			\|[[File:Fringe Lands end.png\|thumb\|right\|240px]]
	\|}		\|}

SyncBot: Sync: updated from Minecraft

2026-07-11T11:05:40Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:05, 11 July 2026
Line 85:		Line 85:
	The Far Lands were never actually removed from the game in Beta 1.8. Rather, what ''was'' fixed was integers and noise values overflowing at the 32-bit limit, by simply making them 64-bit instead, way beyond the boundaries of a normal ''Minecraft'' world. As such, by patching the game to reverse this change, or by using a BigInteger mod, the Far Lands can be brought back. However, their location, makeup and progression depends entirely on the version and/or method used. Below are tables to simplify what happens:		The Far Lands were never actually removed from the game in Beta 1.8. Rather, what ''was'' fixed was integers and noise values overflowing at the 32-bit limit, by simply making them 64-bit instead, way beyond the boundaries of a normal ''Minecraft'' world. As such, by patching the game to reverse this change, or by using a BigInteger mod, the Far Lands can be brought back. However, their location, makeup and progression depends entirely on the version and/or method used. Below are tables to simplify what happens:
	===Undoing the fix===		===Undoing the fix===
	{{~~main~~\|Far Lands (Java Edition)/Infdev 20100327 to Beta 1.7.3#Vanilla clients}}		{{See also\|Far Lands (Java Edition)/Infdev 20100327 to Beta 1.7.3#Vanilla clients}}
	~~[[File:Fl 1.11.2int overload.png\|alt=200 Blocks from the 32-bit integer limit where world rendering glitches out. At 2,147,483,520, the game crashes.\|thumb\|The World at the 32-bit integer limit.]]~~		If the game is patched to simply undo the fix that patched the original Far Lands, then they will generate at their original starting point of X/Z: ±12,550,821. More recent versions will have the very early Infdev-like generation of the Far Lands rather than the classic structure.
	If the game is patched to simply undo the fix that patched the original Far Lands, then they will generate at their original starting point of X/Z: ±12,550,821 and ~~continue~~ until ~~either~~ X/Z: ±30,000,000 ~~(if~~ the [[Minecraft:world boundary]] ~~is not modified - thus making them similar~~ to ~~the~~ pre-[[Minecraft:Alpha v1.2.0]] versions ~~which simply stopped generated~~ at 32 million), ~~or continue until~~ the 32-bit limit of X/Z: ±2,147,483,647 ~~(if the world boundary is patched to go this far)~~. ~~With~~ the ~~latter~~, the same glitches and progression from pre-Beta 1.8 will occur until the game crashes shortly before the 32-bit limit. More ~~recent~~ versions will ~~have~~ the ~~very early Infdev~~-~~like generation of the Far Lands rather than the classic structure~~.
			The limit to how much of the Far Lands will generate is dependent on what mods and/or version is being used. If only the patch is reversed, then it will vary due to various features throughout different versions that affected the edge of the world.
			* Theoretically, even though there is no known mods reversing the fix for such versions, from [[Minecraft:Beta 1.8]] until [[Minecraft:Java Edition 1.2.5\|1.2.5]], the Far Lands will generate until X/Z: ±30,000,064, due to the bug causing players to get stuck after 32 blocks past the limit existing in these versions.
			* From [[Minecraft:Java Edition 1.3.1\|1.3.1]] until [[Minecraft:Java Edition 1.7.10\|1.7.10]], and again from [[Minecraft:Java Edition 1.9\|1.9]] until [[Minecraft:Java Edition 1.13.2\|1.13.2]], they will generate beyond X/Z: ±32,000,000, although they cannot be accessed due to the player being kicked for being in an "Illegal position" after 32 million blocks in the former versions.
			* From [[Minecraft:Java Edition 1.8\|1.8]] until [[Minecraft:Java Edition 1.8.9\|1.8.9]], the Far Lands will simply stop genersting at the [[Minecraft:world boundary]] of 30 million blocks, identical to pre-[[Minecraft:Alpha v1.2.0]] and Infdev versions ending at 32 million.
			*From [[Minecraft:Java Edition 1.14\|1.14]] onwards, because of the switch to a packed coordinate system, the Far Lands will either turn completely black due to lighting breaking (in 1.14) or stop rendering (in modern versions at least later then [[Minecraft:Java Edition 1.20.4\|1.20.4]]) at X/Z: ±33,554,432, both due to packed coordinates overflowinf at this limit. Attempting to go further is impossible as the game will crash [[Minecraft:Java Edition hard limits\|if a chunk is rendered beyond this point]].
			[[File:Fl 1.11.2int overload.png\|alt=200 Blocks from the 32-bit integer limit where world rendering glitches out. At 2,147,483,520, the game crashes.\|thumb\|The Far Lands at the 32-bit integer limit with terrain flickering in and out.]]
			In versions after 1.8, if the above is combined with a mod that removes the [[Minecraft:world boundary]], and patches the packed coordinate overflow (in 1.14 and later versions) - such as “Beyond the Barrier", then the Far Lands can generate out to the 32-bit limit of X/Z: ±2,147,483,647. In some earlier versions, sometimes fependent on the exact mod, the same glitches and progression from pre-Beta 1.8 will occur, such as terrain flickering at high distances until the game crashes shortly before the 32-bit limit and world rendering stops completely. More modern versions will end up generating without rendering issues straight up until the 32-bit integer limit.

	===64-bit & BigInteger mod===		===64-bit & BigInteger mod===
Line 136:		Line 143:
	\|[[File:1.2.5 biome fill Edge Far Lands.png\|thumb\|240px]]		\|[[File:1.2.5 biome fill Edge Far Lands.png\|thumb\|240px]]
	\|-		\|-
	\| X: ±{{abbr\|8.5766×10<sup>51</sup>\|8,576,620,983,668,390,695,654,176,953,195,873,545,661,439,803,392}}<hr>Z: ±{{abbr\|9.17×10<sup>51</sup>\|9170000000000000000000000000000000000000000000000}}		\| X: ±{{abbr\|8.5766×10<sup>48</sup>\|8,576,620,983,668,390,695,654,176,953,195,873,545,661,439,803,392}}<hr>Z: ±{{abbr\|9.17×10<sup>48</sup>\|9170000000000000000000000000000000000000000000000}}
	\|		\|
	* The Fringe Lands begin generating as a result of the Far Lands progressively beginning to break down. These are are the same occurance that happens on {{BE}}, but it happens at the 64-bit equivalent. They progressively break down into thinner and thinner slices, before becoming scattered cubes increasingly seperated.		* The Fringe Lands begin generating as a result of the Far Lands progressively beginning to break down. These are are the same occurance that happens on {{BE}}, but it happens at the 64-bit equivalent. They progressively break down into thinner and thinner slices, before becoming scattered cubes increasingly seperated.
	\|[[File:The True Fringe Lands.png\|thumb\|240px]]		\|[[File:The True Fringe Lands.png\|thumb\|240px]]
	\|-		\|-
	\| X/Z: ±{{abbr\|1.~~71529×10~~<sup>52</sup>\|17,~~152~~,~~946~~,~~793~~,~~627~~,~~300~~,~~555~~,~~614~~,~~566~~,~~338~~,~~807~~,~~200~~,~~814~~,~~478~~,~~328~~,~~332~~,~~304~~}}		\| X/Z: ±{{abbr\|4.119992×10<sup>49</sup>\|41,199,924,359,301,325,212,109,680,894,587,089,802,536,146,698,256}}
	\|		\|
	* The Fringe Lands, and by definition, the Far Lands, end completely at this point. The only thing that generates after this point is an endless bedrock ocean. This marks the end of ''Minecraft'' terrain generation, unless extensive modding on top of this patches the noise overflow and Far Lands.		* The Fringe Lands, and by definition, the Far Lands, end completely at this point, having been reduced to spaced out dirt blocks underwater at Y: 32. The only thing that generates after this point is an endless bedrock ocean.<ref name="Beyond 10e308">[https://youtu.be/JXdq7G5qUlQ?is=4IvkN92Ig5_EDZsJ Beyond 2^1024 blocks in Minecraft 1.3.2 BigInt mod], YouTube, May 14, 2026</ref> This marks the end of ''Minecraft'' terrain generation, unless extensive modding on top of this patches the noise overflow and Far Lands.
	\|		\|
	\|}		\|}

			Beyond this point, it remains the same, and what happens after is entirely dependent on how the game is patched, due to BigInt having the ability to change how numbers are stored. This means that, if configured, bedrock and ocean can generate beyond X/Z ±~1.7977×10<sup>308</sup> (±2<sup>1024</sup>) without the coordinates rolling over to "Infinity" and crashing the game,<ref name="Beyond 10e308"/> if set to be stored in 128-bit (quadruple) and even 256-bit (octuple). As Java’s own BigInteger class maxes out at ~8.8081×10<sup>646456992</sup> (2<sup>2<sup>31</sup>−1</sup>), this is theoretically the absolute farthest one could possibly even reach as both BigInt and the coordinates would overflow, the latter rolling over to "Infinity" and crashing the game, making this the absolute maximum ''Minecraft'' can generate, even with extensive modding. However, this is an exceptionally gigantic number that any attempts using this method would almost certainly crash the game long before then.

	====1.14 to present====		====1.14 to present====
Line 193:		Line 202:
	\|{{HistoryLine\|\|1.8\|dev=14w17a\|Added [[Minecraft:Old Customized\|customized]] world generation. This made it possible to create the Sky and Ground Far Lands without mods.}}		\|{{HistoryLine\|\|1.8\|dev=14w17a\|Added [[Minecraft:Old Customized\|customized]] world generation. This made it possible to create the Sky and Ground Far Lands without mods.}}
	\|{{HistoryLine\|\|1.13\|dev=18w06a\|Removed customized worlds. The Sky and Ground Far Lands can no longer be created without mods.}}		\|{{HistoryLine\|\|1.13\|dev=18w06a\|Removed customized worlds. The Sky and Ground Far Lands can no longer be created without mods.}}
	\|{{HistoryLine\|\|?\|The Far Lands now begin at ~1.8 septillion blocks instead of ~53.9 quadrillion blocks due to world generation changes.~~{{check version}}~~}}		\|{{HistoryLine\|\|1.14\|dev=18w46a\|The Far Lands now begin at ~1.8 septillion blocks instead of ~53.9 quadrillion blocks due to world generation changes.}}
	\|{{HistoryLine\|\|1.17\|dev=21w06a\|The Far Lands now appear much thinner than before, with the Edge Far Lands now containing strips of terrain at various widths connecting via right angles.<br>It is also now possible to (with a modification) manipulate the Y Scale to allow the Sky and Ground Far Lands to generate.}}		\|{{HistoryLine\|\|1.17\|dev=21w06a\|The Far Lands now appear much thinner than before, with the Edge Far Lands now containing strips of terrain at various widths connecting via right angles.<br>It is also now possible to (with a modification) manipulate the Y Scale to allow the Sky and Ground Far Lands to generate.}}
	\|{{HistoryLine\|\|\|dev=21w15a\|The Far Lands now look like the Beta Far Lands again as the Noise caves are disabled.}}		\|{{HistoryLine\|\|\|dev=21w15a\|The Far Lands now look like the Beta Far Lands again as the Noise caves are disabled.}}

SyncBot: Sync: updated from Minecraft

2026-07-10T11:12:39Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:12, 10 July 2026
Line 15:		Line 15:
	== Location ==		== Location ==
	[[File:Far Lands in 1.8.1.png\|thumb\|Far Lands generating in 1.8.1]]		[[File:Far Lands in 1.8.1.png\|thumb\|Far Lands generating in 1.8.1]]
	On the X and Z axis, the Far Lands and Farther Lands initiate as they did in Beta 1.7 and below (±12,550,824), with an identical chance of offset at positive positions. However, due to the new height limits and new world generation, they are actually 256 blocks tall, instead of 128, and the Far Lands look more rounded. There is a world border at the 32-bit integer limit (2,147,483,647), which crashes the game upon approaching (likely due to an integer overflow when casting the player's position to a 32-bit integer).		With On the X and Z axis, the Far Lands and Farther Lands initiate as they did in Beta 1.7 and below (±12,550,824), with an identical chance of offset at positive positions. However, due to the new height limits and new world generation, they are actually 256 blocks tall, instead of 128, and the Far Lands look more rounded. There is a world border at the 32-bit integer limit (2,147,483,647), which crashes the game upon approaching (likely due to an integer overflow when casting the player's position to a 32-bit integer).

	Any attempt to quit the game near the 32-bit integer limit also results in crashing.		Any attempt to quit the game near the 32-bit integer limit also results in crashing.

	On the Y-axis, the Far Lands initiate at around twice the former number, which is therefore ±25,101,648.		On the Y-axis, the Far Lands initiate at around twice the former number, which is therefore ±25,101,648.
	~~[[File:Fl 1.11.2int overload.png\|alt=200 Blocks from the 32-bit integer limit where world rendering glitches out. At 2,147,483,520, the game crashes.\|thumb\|The World at the 32-bit integer limit.]]~~
	The Farther Lands also generate at ±2,008,131,840 on the Y-axis, however, they cannot be generated without lowering the selector noise period.		The Farther Lands also generate at ±2,008,131,840 on the Y-axis, however, they cannot be generated without lowering the selector noise period.

	The location of the 64-bit variant of the Far Lands depends of the game version. In versions between Beta 1.8 ~~and 1.6.4 inclusive, they start at 59 quadrillion blocks. In versions 1.7.2 through~~ 1.13.2, they start at 53.9 quadrillion blocks due to a small change in the coordinate scale, that is not noticeable for 32-bit overflowing. The Far Lands in positive coordinates don't begin exactly after {{frac\|2<sup>63</sup>\|171.103}} blocks due to the remainder of the overflow. The Far lands in negative coordinates have a remainder of 2<sup>32</sup>, as a result, they begin exactly after {{frac\|2<sup>63</sup>\|171.103}} blocks. In versions 1.14~~{{check version}}~~ and later they start at 1.8 septillion blocks, due to a change in that version that takes the noise coordinate and divides it by 2<sup>25</sup>.		The location of the 64-bit variant of the Far Lands depends of the game version. In versions between Beta 1.8 to 1.13.2, they start at 53.9 quadrillion blocks due to a small change in the coordinate scale, that is not noticeable for 32-bit overflowing. The Far Lands in positive coordinates don't begin exactly after {{frac\|2<sup>63</sup>\|171.103}} blocks due to the remainder of the overflow. The Far lands in negative coordinates have a remainder of 2<sup>32</sup>, as a result, they begin exactly after {{frac\|2<sup>63</sup>\|171.103}} blocks. In versions 1.14 and later they start at 1.8 septillion blocks, due to a change in that version that takes the noise coordinate and divides it by 2<sup>25</sup>.

	== Structure ==		== Structure ==
Line 74:		Line 74:

	==== Corner Fringe Lands ====		==== Corner Fringe Lands ====
	~~[[File:Sky Skygrid (Corner Fringe Lands).png\|thumb\|The Corner Fringe Lands in the Sky Dimension in Beta 1.7.3. Flat areas can generate above the skygrid.]]~~
	The Corner Fringe Lands appear much earlier than the regular Fringe Lands, at around 40.5 septillion blocks on both axes.		The Corner Fringe Lands appear much earlier than the regular Fringe Lands, at around 40.5 septillion blocks on both axes.

Line 83:		Line 82:
	This type of fringe lands only appears if you set the noise multiplier of all three axis to 1 quadrillion. The vertex fringe lands degrade into skygrid at the much earlier coordinate of 100 quadrillion blocks, and this coordinate does indeed vary.		This type of fringe lands only appears if you set the noise multiplier of all three axis to 1 quadrillion. The vertex fringe lands degrade into skygrid at the much earlier coordinate of 100 quadrillion blocks, and this coordinate does indeed vary.

	===Summary===		==Summary==
	The Far Lands were never actually removed from the game in Beta 1.8. Rather, what ''was'' fixed was integers and noise values overflowing at the 32-bit limit, by simply making them 64-bit instead, way beyond the boundaries of a normal ''Minecraft'' world. As such, by patching the game to reverse this change, or by using a BigInteger mod, the Far Lands can be brought back. However, their location, makeup and progression depends entirely on the version and/or method used. Below are tables to simplify what happens:		The Far Lands were never actually removed from the game in Beta 1.8. Rather, what ''was'' fixed was integers and noise values overflowing at the 32-bit limit, by simply making them 64-bit instead, way beyond the boundaries of a normal ''Minecraft'' world. As such, by patching the game to reverse this change, or by using a BigInteger mod, the Far Lands can be brought back. However, their location, makeup and progression depends entirely on the version and/or method used. Below are tables to simplify what happens:
	====Undoing the fix====		===Undoing the fix===
	{{main\|Far Lands (Java Edition)/Infdev 20100327 to Beta 1.7.3#Vanilla clients}}		{{main\|Far Lands (Java Edition)/Infdev 20100327 to Beta 1.7.3#Vanilla clients}}
			[[File:Fl 1.11.2int overload.png\|alt=200 Blocks from the 32-bit integer limit where world rendering glitches out. At 2,147,483,520, the game crashes.\|thumb\|The World at the 32-bit integer limit.]]
	If the game is patched to simply undo the fix that patched the original Far Lands, then they will generate at their original starting point of X/Z: ±12,550,821 and continue until either X/Z: ±30,000,000 (if the [[Minecraft:world boundary]] is not modified - thus making them similar to the pre-[[Minecraft:Alpha v1.2.0]] versions which simply stopped generated at 32 million), or continue until the 32-bit limit of X/Z: ±2,147,483,647 (if the world boundary is patched to go this far). With the latter, the same glitches and progression from pre-Beta 1.8 will occur until the game crashes shortly before the 32-bit limit. More recent versions will have the very early Infdev-like generation of the Far Lands rather than the classic structure.		If the game is patched to simply undo the fix that patched the original Far Lands, then they will generate at their original starting point of X/Z: ±12,550,821 and continue until either X/Z: ±30,000,000 (if the [[Minecraft:world boundary]] is not modified - thus making them similar to the pre-[[Minecraft:Alpha v1.2.0]] versions which simply stopped generated at 32 million), or continue until the 32-bit limit of X/Z: ±2,147,483,647 (if the world boundary is patched to go this far). With the latter, the same glitches and progression from pre-Beta 1.8 will occur until the game crashes shortly before the 32-bit limit. More recent versions will have the very early Infdev-like generation of the Far Lands rather than the classic structure.

	====64-bit & BigInteger mod====		===64-bit & BigInteger mod===
	Using either a mod that patches integers to 64-bit or a BigInt mod, the new location of the Far Lands after Beta 1.8 can be reached. However, it has been changed once due to the terrain generator receiving changes in 1.14.		Using either a mod that patches integers to 64-bit or a BigInt mod, the new location of the Far Lands after Beta 1.8 can be reached. However, it has been changed once due to the terrain generator receiving changes in 1.14.
	=====Beta 1.8 to 1.14=====		====Beta 1.8 to 1.14====
	{\| class="wikitable"		{\| class="wikitable"
	!Coordinates		!Coordinates
Line 97:		Line 97:
	! Image (if avaliable)		! Image (if avaliable)
	\|-		\|-
	\| X/Z: ±53,905,378,846,979,~~747–53,905,378,859,432,448~~		\| X/Z: ±53,905,378,846,979,747
	\|
	* The Far Lands begin generating due to the noise value overflowing at this point. Because of the four-block offset that sometimes happened in the vanilla Far Lands, this offset is measured in billions of blocks instead, so the actual start will vary between worlds.<ref>[https://youtu.be/F8cMZA8J2Hk?t=473 breaking Minecraft's FINAL Distance Limit…], YouTube, April 1, 2021</ref>
	\|		\|
			* The Far Lands begin generating due to the noise value overflowing at this point. Because of the four-block offset that sometimes happened in the vanilla Far Lands, this offset is measured in tens of millions of blocks instead, so the actual start will vary between worlds.<ref>[https://youtu.be/F8cMZA8J2Hk?t=473 breaking Minecraft's FINAL Distance Limit…], YouTube, April 1, 2021</ref> As such, it can start as late as X/Z: ±53,905,378,859,432,448.
			* If a Stripe Lands fix is not enabled, the Far Lands will appear two-dimensional due to occuring past the 64-bit equivalent where movement precision begins breaking down.
			\|[[File:MC-distance13.png\|thumb\|right\|240px\|Without the fix]][[File:MC-distance12.png\|thumb\|right\|240px\|With the Stripe Lands fix]]
	\|-		\|-
	\| X/Z: ± 4,312,430,307,758,379,833		\| X/Z: ± 4,312,430,307,758,379,833
Line 106:		Line 107:
	* Selector Noise overflows at this point, causing the Farther Lands to generate.		* Selector Noise overflows at this point, causing the Farther Lands to generate.
	\|		\|
	\|-
	~~\| X/Z: ±9,007,199,254,740,992 (±2<sup>53</sup>)~~
	\|
	* At this point, the Far Lands and the game begin breaking down in similiar manners to {{BE}}. This includes:
	**The [[Minecraft:Stripe Lands]] artifact begins here (unless disabled) due to movement precision breaking down at the 64-bit equivalent of the above, and worsens ever power of two doubling the gaps. A patch is required to disable/fix this bug.
	~~\|[[File:1.2.5 Stripe Lands.png\|thumb\|240px]]~~
	\|-		\|-
	\| X/Z: ±576,460,752,303,423,488 (±2<sup>59</sup>)		\| X/Z: ±576,460,752,303,423,488 (±2<sup>59</sup>)
Line 129:		Line 124:
	\|}		\|}

	Beyond this point, a BigInt mod is required to go even further.		Beyond this point, a BigInt mod is required to go even further. Additionally, because of the BigInteger mod, most of the movement precision issues seemingly don't occur now at such distances.

	{\| class="wikitable"		{\| class="wikitable"
Line 136:		Line 131:
	! Image (if avaliable)		! Image (if avaliable)
	\|-		\|-
	\| X/Z: ±{{abbr\|8.5766×10<sup>51</sup>\|8,576,620,983,668,390,695,654,176,953,195,873,545,661,439,803,392}}		\| X/Z: ±147,573,952,589,676,412,928 (2<sup>67</sup>)
			\|
			* Biome fill noise overflows, causing repeating stone layers to be exposed within the Far Lands.
			\|[[File:1.2.5 biome fill Edge Far Lands.png\|thumb\|240px]]
			\|-
			\| X: ±{{abbr\|8.5766×10<sup>51</sup>\|8,576,620,983,668,390,695,654,176,953,195,873,545,661,439,803,392}}<hr>Z: ±{{abbr\|9.17×10<sup>51</sup>\|9170000000000000000000000000000000000000000000000}}
	\|		\|
	* The Fringe Lands begin generating as a result of the Far Lands progressively beginning to break down. These are are the same occurance that happens on {{BE}}, but it happens at the 64-bit equivalent. They progressively break down into thinner and thinner slices, before becoming scattered cubes increasingly seperated.		* The Fringe Lands begin generating as a result of the Far Lands progressively beginning to break down. These are are the same occurance that happens on {{BE}}, but it happens at the 64-bit equivalent. They progressively break down into thinner and thinner slices, before becoming scattered cubes increasingly seperated.
Line 147:		Line 147:
	\|}		\|}

	=====1.14 to present=====		====1.14 to present====
	Due to changes within the way the terrain generator works internally in [[Minecraft:Java Edition 1.14\|1.14]], the Far Lands were patched to be even further away then the 64-bit equivalent listed above. Additionally, the structure changed dramatically several times in the [[Minecraft:Caves & Cliffs]] updates, first being a thin maze-like construct before becoming a mostly giant wall identical to [[Minecraft:Infdev 20100227]]. The only way to reach them in modern versions is with a BigInteger mod.		Due to changes within the way the terrain generator works internally in [[Minecraft:Java Edition 1.14\|1.14]], the Far Lands were patched to be even further away then the 64-bit equivalent listed above. Additionally, the structure changed dramatically several times in the [[Minecraft:Caves & Cliffs]] updates, first being a thin maze-like construct before becoming a mostly giant wall identical to [[Minecraft:Infdev 20100227]]. The only way to reach them in modern versions is with a BigInteger mod.

	{\| class="wikitable"		{\| class="wikitable"
Line 157:		Line 157:
	\| X/Z: ±{{abbr\|1.808×10<sup>24</sup>\| 1,808,764,368,955,220,466,364,897}}		\| X/Z: ±{{abbr\|1.808×10<sup>24</sup>\| 1,808,764,368,955,220,466,364,897}}
	\|		\|
	* The Far Lands begin generating at this distance due to the overflowing of the modified noise value. This is due to a change in the Far Lands patch, which now takes the double Noise ~~Cooordinate~~, converts it to a 64-bit integer, and then divides it by 33,554,432.		* The Far Lands begin generating at this distance due to the overflowing of the modified noise value. This is due to a change in the Far Lands patch, which now takes the double Noise Coordinate, converts it to a 64-bit integer, and then divides it by 33,554,432.
	\|[[File:Farlands1113.png\|thumb\|240px\|The Far Lands generating in a modern version of Minecraft]]		\|[[File:Farlands1113.png\|thumb\|240px\|The Far Lands generating in a modern version of Minecraft]]
	\|}		\|}