Minecraft:Java Edition hard limits - Revision history

SyncBot: Sync: updated from Minecraft

2026-09-11T11:06:40Z

Sync: updated from Minecraft

SyncBot: Sync: updated from Minecraft

2026-09-05T11:11:53Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:11, 5 September 2026
Line 200:		Line 200:
	====== (Y: >+2,147,483,647) ======		====== (Y: >+2,147,483,647) ======
	\|		\|
	* In [[Minecraft:Beta 1.7.3]], as it rains when the player flies up to the coordinates Y=+2,147,483,647, the rain disappears. Instead of rain being there, ~~the sky now looks like an empty world~~. It has the sun, moon, and they are all visible depending on the time of day~~. going into third person will crash the game~~.		* In [[Minecraft:Beta 1.7.3]], as it rains when the player flies up to the coordinates Y=+2,147,483,647, the rain disappears. Instead of rain being there, all weather featrures will be gone. It has the sun, moon, and they are all visible depending on the time of day.

	* ~~In some versions of Minecraft going~~ into third person ~~after~~ 2,147,483,~~648 blocks on the Y axis~~ will crash ~~your~~ game. This ~~happens more often in modern versions but can happen in vanilla sometimes. In Beta, this can crash~~ the ~~game more than newer versions. However, this has~~ a ~~less likely to crash~~.		* Going into third person past Y=2,147,483,647 will crash the game. This is caused by the player cameras ray casting failing due to a integer overflow.
	\|		\|
	\|-		\|-

SyncBot: Sync: updated from Minecraft

2026-09-04T11:06:45Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:06, 4 September 2026
Line 252:		Line 252:
	[[Category:Glitches]]		[[Category:Glitches]]

			[[Minecraft:pt:Limites rígidos da Edição Java]]
	[[Minecraft:zh:距离现象/Java版/Beta 1.8之前版本的现象]]		[[Minecraft:zh:距离现象/Java版/Beta 1.8之前版本的现象]]

SyncBot: Sync: updated from Minecraft

2026-08-30T11:09:00Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:09, 30 August 2026
Line 1:		Line 1:
	{{about\|effects which arise due to integer limits\|effects which arise due to floating-point precision loss\|Java Edition distance effects}}		{{about\|effects which arise due to integer limits\|effects which arise due to floating-point precision loss\|Java Edition distance effects}}
	~~{{No navbox}}~~
	{{Cleanup\|		{{Cleanup\|
	* (Various) grammatical mistakes make parts of the page difficult to read.		* (Various) grammatical mistakes make parts of the page difficult to read.
Line 246:		Line 245:

	== References ==		== References ==
	{{Reflist}}{{Navbox environment\|nocat=1}}		{{Reflist}}

			== Navigation ==
			{{Navbox environment\|nocat=1}}

	[[Category:Glitches]]		[[Category:Glitches]]

	[[Minecraft:zh:距离现象/Java版/Beta 1.8之前版本的现象]]		[[Minecraft:zh:距离现象/Java版/Beta 1.8之前版本的现象]]

SyncBot: Sync: updated from Minecraft

2026-08-14T11:07:31Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:07, 14 August 2026
Line 215:		Line 215:
	\|-		\|-
	\|		\|
	====== ~~'''~~(Y:>+4,503,599,627,370,496) and (Y:<-4,503,599,627,370,496)~~'''~~ ======		====== (Y:>+4,503,599,627,370,496) and (Y:<-4,503,599,627,370,496) ======
	\|		\|
	* There are two critical thresholds set at positive and negative 4,503,599,627,370,496, denoted as (Y: >+4,503,599,627,370,496) and (Y: <-4,503,599,627,370,496) respectively. These numerical limits serve as the primary barriers, beyond which the player's manual movement is disabled.		* There are two critical thresholds set at positive and negative 4,503,599,627,370,496, denoted as (Y: >+4,503,599,627,370,496) and (Y: <-4,503,599,627,370,496) respectively. These numerical limits serve as the primary barriers, beyond which the player's manual movement is disabled.
Line 222:		Line 222:
	\|-		\|-
	\|		\|
	====== ~~'''~~(Y:>+36,028,797,018,963,968)~~'''~~ ======		====== (Y:>+36,028,797,018,963,968) ======
	\|		\|
	* Another threshold is established at positive 36,028,797,018,963,968, marked as (Y: >+36,028,797,018,963,968). Beyond this point, the player is rendered completely stationary; conventional movement is entirely stalled.		* Another threshold is established at positive 36,028,797,018,963,968, marked as (Y: >+36,028,797,018,963,968). Beyond this point, the player is rendered completely stationary; conventional movement is entirely stalled.

SyncBot: Sync: updated from Minecraft

2026-08-04T11:13:28Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:13, 4 August 2026
Line 40:		Line 40:
	\|		\|

	* Beyond this point (2<sup>30</sup>), [[Minecraft:village]]s seem to stop generating correctly at all. The only part which generates is the meeting point, sometimes with accompanying villagers, but every other part is missing.		* Beyond this point (2<sup>30</sup>), [[Minecraft:village]]s seem to stop generating correctly at all. The only part which generates is the meeting point, sometimes with accompanying villagers, but every other part is missing.{{info needed\|Are we sure this is an internally-defined hard limit and not a severe float-related bug?}}
	* It has been sighted in some superflat worlds that strange phantom villages composed solely of block light can generate.		* It has been sighted in some superflat worlds that strange phantom villages composed solely of block light can generate.
	* The reasoning for this happening remains unknown and it is not known if this is tied to [[Minecraft:jigsaw block]]s.		* The reasoning for this happening remains unknown and it is not known if this is tied to [[Minecraft:jigsaw block]]s.
Line 239:		Line 239:
	<gallery>		<gallery>
	File:32BitBorder.png\|Picture of someone going to the 32-bit integer limit in Vanilla 1.8 using external programs		File:32BitBorder.png\|Picture of someone going to the 32-bit integer limit in Vanilla 1.8 using external programs
	~~File:FarLandsEnd.png\|The end of Minecraft terrain generation at X: 2,147,483,794, about 146 blocks over the 32-bit limit. World rendering stops working at this point.~~
	~~File:FarLandsEndNether.png\|The end of Minecraft terrain generation in the Nether at X: 2,147,483,644 (2{{^\|31}} - 4).~~
	~~File:ChunkEndOverwrite.png\|X: 34,359,738,079, where chunks start to become overwritten.~~
	~~File:ChunkEndOverwritePauseScreen.png\|Same location as the previous screenshot, but the game is paused (notice an extremely high spike in CPU usage).~~
	File:RainRenderingStop.png\|Y: 2,147,483,647, where rain and snow rendering stops.		File:RainRenderingStop.png\|Y: 2,147,483,647, where rain and snow rendering stops.
	File:PlayerTeleportingToNaNInVinnillaMinecraftWithoutMods.png\|A player teleporting to "Not a number" on the X/Z axis.		File:PlayerTeleportingToNaNInVinnillaMinecraftWithoutMods.png\|A player teleporting to "Not a number" on the X/Z axis.
	File:Disapeear.png\|alt=1 frame before the crash.\|Fast clouds disappear exactly at 17,179,869,184 on this limit for 1 frame.		File:Disapeear.png\|alt=1 frame before the crash.\|Fast clouds disappear exactly at 17,179,869,184 on this limit for 1 frame.
	~~File:Java Edition hard limits map.jpg\|The far lands map~~		File:Java Edition hard limits map.png\|The hard limit map that was removed in here
	File:Java Edition hard limits map.png\|The hard limit map that was removed in here ~~Note: Misleading map~~
	</gallery>		</gallery>

SyncBot: Sync: updated from Minecraft

2026-07-30T11:10:17Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:10, 30 July 2026
Line 24:		Line 24:
	\|-		\|-
	\|		\|
	====== (X/Z: ±370,727; The End generation breakdown) ======		====== (X/Z: ±370,727; The End generation breakdown){{until\|je 26.3}} ======
	\|		\|
	{{main\|The End#Outer islands}}		{{main\|The End#Outer islands}}
	* [[Minecraft:The End]]'s generation is completely absent in some parts of the repeating concentric rings centered on the main end island.<ref>{{bug\|MC-159283}}</ref> This is due to an integer overflow resulting from a square root being taken from a negative number. Since this integer overflow happens based on the ''squared'' distance (creating extremely high values rapidly), multiple overflows happen within a reachable distance, creating rings of void inside a landscape that gets thinner and thinner further away from the original part, the [[Minecraft:End Island\|main end island]]. The first ring of void starts at 370,727 blocks away from the center and ends at 524,288 blocks away from the center, where terrain continues generating until the next integer overflow occurs. Interestingly, all the rings (whether they are void or land) approximately cover the same area.		* [[Minecraft:The End]]'s generation is completely absent in some parts of the repeating concentric rings centered on the main end island.<ref>{{bug\|MC-159283\|\|\|Fixed}}</ref> This is due to an integer overflow resulting from a square root being taken from a negative number. Since this integer overflow happens based on the ''squared'' distance (creating extremely high values rapidly), multiple overflows happen within a reachable distance, creating rings of void inside a landscape that gets thinner and thinner further away from the original part, the [[Minecraft:End Island\|main end island]]. The first ring of void starts at 370,727 blocks away from the center and ends at 524,288 blocks away from the center, where terrain continues generating until the next integer overflow occurs. Interestingly, all the rings (whether they are void or land) approximately cover the same area.
	\|		\|
	\|-		\|-

SyncBot: Sync: updated from Minecraft

2026-07-24T11:06:43Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:06, 24 July 2026
Line 1:		Line 1:
	{{about\|effects which arise due to integer limits\|effects which arise due to floating-point precision loss\|Java Edition distance effects}}		{{about\|effects which arise due to integer limits\|effects which arise due to floating-point precision loss\|Java Edition distance effects}}
	~~{{Merge\|Java Edition distance effects\|reason=Heavy overlap between pages, would be better suited as one page to cover both floating-point precision loss and integer limits}}~~
	{{No navbox}}		{{No navbox}}
	{{Cleanup\|		{{Cleanup\|

SyncBot: Sync: updated from Minecraft

2026-06-24T11:19:46Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:19, 24 June 2026
Line 29:		Line 29:
	{{main\|The End#Outer islands}}		{{main\|The End#Outer islands}}
	* [[Minecraft:The End]]'s generation is completely absent in some parts of the repeating concentric rings centered on the main end island.<ref>{{bug\|MC-159283}}</ref> This is due to an integer overflow resulting from a square root being taken from a negative number. Since this integer overflow happens based on the ''squared'' distance (creating extremely high values rapidly), multiple overflows happen within a reachable distance, creating rings of void inside a landscape that gets thinner and thinner further away from the original part, the [[Minecraft:End Island\|main end island]]. The first ring of void starts at 370,727 blocks away from the center and ends at 524,288 blocks away from the center, where terrain continues generating until the next integer overflow occurs. Interestingly, all the rings (whether they are void or land) approximately cover the same area.		* [[Minecraft:The End]]'s generation is completely absent in some parts of the repeating concentric rings centered on the main end island.<ref>{{bug\|MC-159283}}</ref> This is due to an integer overflow resulting from a square root being taken from a negative number. Since this integer overflow happens based on the ''squared'' distance (creating extremely high values rapidly), multiple overflows happen within a reachable distance, creating rings of void inside a landscape that gets thinner and thinner further away from the original part, the [[Minecraft:End Island\|main end island]]. The first ring of void starts at 370,727 blocks away from the center and ends at 524,288 blocks away from the center, where terrain continues generating until the next integer overflow occurs. Interestingly, all the rings (whether they are void or land) approximately cover the same area.
			\|
			\|-
			\|
			====== (X/Z: ±33,554,432; Packed coordinate limit) ======
			\|
			* Certain systems in {{JE}} use packed block coordinates, which compress a block coordinate into a single 64-bit value, allocating 26 bits for each horizontal direction and 12 bits vertically. 33,554,432 (2<sup>25</sup>) is the horizontal limit beyond which coordinates cannot be correctly packed in this system anymore, resulting in a game crash if the player goes out this far.
	\|		\|
	\|-		\|-
Line 34:		Line 40:
	====== (X/Z: ±1,073,741,824; Village generation limit) ======		====== (X/Z: ±1,073,741,824; Village generation limit) ======
	\|		\|

	* Beyond this point (2<sup>30</sup>), [[Minecraft:village]]s seem to stop generating correctly at all. The only part which generates is the meeting point, sometimes with accompanying villagers, but every other part is missing.		* Beyond this point (2<sup>30</sup>), [[Minecraft:village]]s seem to stop generating correctly at all. The only part which generates is the meeting point, sometimes with accompanying villagers, but every other part is missing.
	* It has been sighted in some superflat worlds that strange phantom villages composed solely of block light can generate.		* It has been sighted in some superflat worlds that strange phantom villages composed solely of block light can generate.
Line 66:		Line 73:
	\|-		\|-
	\|		\|
	====== (Y: ±179,769,313,486,231,590,772,930,519,078,902,473,361,797,697,894,230,657,273,430,081,157,732,675,805,500,963,132,708,477,322,407,536,021,120,113,879,871,393,357,658,789,768,814,416,622,492,847,430,639,474,124,377,767,893,424,865,485,276,302,219,601,246,094,119,453,082,952,085,005,768,838,150,682,342,462,881,473,913,110,540,827,237,163,350,510,684,586,298,239,947,245,938,479,716,304,835,356,329,624,224,137,216; Absolute limit) ======		====== (Y: ±2^1024; Absolute limit) ======
	\|		\|
	*The maximum possible [[Minecraft:Altitude\|height]] is ~1.798×10<sup>308</sup> (2<sup>1024</sup>). Attempting to teleport beyond this limit will result in the value being interpreted as infinity, and the teleportation will fail. However, teleporting to a number that will round to 2<sup>1024</sup> will render the game for exactly 1 frame ~~because~~ it crashes.		*The maximum possible [[Minecraft:Altitude\|height]] is ~1.798×10<sup>308</sup> (2<sup>1024</sup>). Attempting to teleport beyond this limit will result in the value being interpreted as infinity, and the teleportation will fail. However, teleporting to a number that will round to 2<sup>1024</sup> will render the game for exactly 1 frame before it crashes.
	* The reason previous limits do not restrict going this high is because chunks do not load past Y: +320/-64, meaning that there is nothing to render except for snow and rain.		* The reason previous limits do not restrict going this high is because chunks do not load past Y: +320/-64, meaning that there is nothing to render except for snow and rain.
	\|		\|
Line 170:		Line 177:
	\|-		\|-
	\|		\|
	====== 64-bit floating point limit (X/Z: >±179,769,313,486,231,590,772,930,519,078,902,473,361,797,697,894,230,657,273,430,081,157,732,675,805,500,963,132,708,477,322,407,536,021,120,113,879,871,393,357,658,789,768,814,416,622,492,847,430,639,474,124,377,767,893,424,865,485,276,302,219,601,246,094,119,453,082,952,085,005,768,838,150,682,342,462,881,473,913,110,540,827,237,163,350,510,684,586,298,239,947,245,938,479,716,304,835,356,329,624,224,137,216) ======		====== 64-bit floating point limit (X/Z: >±2^1024) ======
	\|		\|
	* Because 2<sup>1024</sup> is the maximum 64-bit floating-point integer, it causes the player's X coordinate to roll over to read "Infinity".<ref>Video reupload https://www.youtube.com/watch?v=OiqM07e7Odw</ref> It is impossible to go further since this is the physical limit at which Java can render, and the game is expected to crash at this distance. The only way to go further is by using BigInt and BigDecimal mods.		* Because 2<sup>1024</sup> is the maximum 64-bit floating-point integer, it causes the player's X coordinate to roll over to read "Infinity".<ref>Video reupload https://www.youtube.com/watch?v=OiqM07e7Odw</ref> It is impossible to go further since this is the physical limit at which Java can render, and the game is expected to crash at this distance. The only way to go further is by using BigInt and BigDecimal mods.

SyncBot: Sync: updated from Minecraft

2026-05-08T11:08:35Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:13, 4 August 2026
Line 40:		Line 40:
	\|		\|

	* Beyond this point (2<sup>30</sup>), [[Minecraft:village]]s seem to stop generating correctly at all. The only part which generates is the meeting point, sometimes with accompanying villagers, but every other part is missing.		* Beyond this point (2<sup>30</sup>), [[Minecraft:village]]s seem to stop generating correctly at all. The only part which generates is the meeting point, sometimes with accompanying villagers, but every other part is missing.{{info needed\|Are we sure this is an internally-defined hard limit and not a severe float-related bug?}}
	* It has been sighted in some superflat worlds that strange phantom villages composed solely of block light can generate.		* It has been sighted in some superflat worlds that strange phantom villages composed solely of block light can generate.
	* The reasoning for this happening remains unknown and it is not known if this is tied to [[Minecraft:jigsaw block]]s.		* The reasoning for this happening remains unknown and it is not known if this is tied to [[Minecraft:jigsaw block]]s.
Line 239:		Line 239:
	<gallery>		<gallery>
	File:32BitBorder.png\|Picture of someone going to the 32-bit integer limit in Vanilla 1.8 using external programs		File:32BitBorder.png\|Picture of someone going to the 32-bit integer limit in Vanilla 1.8 using external programs
	~~File:FarLandsEnd.png\|The end of Minecraft terrain generation at X: 2,147,483,794, about 146 blocks over the 32-bit limit. World rendering stops working at this point.~~
	~~File:FarLandsEndNether.png\|The end of Minecraft terrain generation in the Nether at X: 2,147,483,644 (2{{^\|31}} - 4).~~
	~~File:ChunkEndOverwrite.png\|X: 34,359,738,079, where chunks start to become overwritten.~~
	~~File:ChunkEndOverwritePauseScreen.png\|Same location as the previous screenshot, but the game is paused (notice an extremely high spike in CPU usage).~~
	File:RainRenderingStop.png\|Y: 2,147,483,647, where rain and snow rendering stops.		File:RainRenderingStop.png\|Y: 2,147,483,647, where rain and snow rendering stops.
	File:PlayerTeleportingToNaNInVinnillaMinecraftWithoutMods.png\|A player teleporting to "Not a number" on the X/Z axis.		File:PlayerTeleportingToNaNInVinnillaMinecraftWithoutMods.png\|A player teleporting to "Not a number" on the X/Z axis.
	File:Disapeear.png\|alt=1 frame before the crash.\|Fast clouds disappear exactly at 17,179,869,184 on this limit for 1 frame.		File:Disapeear.png\|alt=1 frame before the crash.\|Fast clouds disappear exactly at 17,179,869,184 on this limit for 1 frame.
	~~File:Java Edition hard limits map.jpg\|The far lands map~~		File:Java Edition hard limits map.png\|The hard limit map that was removed in here
	File:Java Edition hard limits map.png\|The hard limit map that was removed in here ~~Note: Misleading map~~
	</gallery>		</gallery>

← Older revision		Revision as of 11:08, 8 May 2026
Line 42:		Line 42:
	====== (X/Z: >±2,147,483,647; 32-bit limit) ======		====== (X/Z: >±2,147,483,647; 32-bit limit) ======
	\|		\|
	* A hard limit exists at X/Z: ±2,147,483,647—the mathematical limit of a signed 32-bit [[Minecraft:NBT format#Data types\|integer]] (2<sup>31</sup>-1)—and attempting to travel or load chunks beyond here is expected to cause the game to crash. The world renderer stops working 147 blocks beyond this point, allowing the player to get stuck, lightning stops working entirely, and clouds in fast graphics are stretched, while fancy cloud rendering still works normally. It is advisable to set the world border to at least several hundred blocks before this limit and make sure not to teleport past this, if it is modded.		* A hard limit exists at X/Z: ±2,147,483,647—the mathematical limit of a signed 32-bit [[Minecraft:NBT format#Data types\|integer]] (2<sup>31</sup> − 1)—and attempting to travel or load chunks beyond here is expected to cause the game to crash. The world renderer stops working 147 blocks beyond this point, allowing the player to get stuck, lightning stops working entirely, and clouds in fast graphics are stretched, while fancy cloud rendering still works normally. It is advisable to set the world border to at least several hundred blocks before this limit and make sure not to teleport past this, if it is modded.
	\|		\|
	\|-		\|-
Line 48:		Line 48:
	====== (X/Z: >±9,223,372,036,854,775,807; 64-bit limit) ======		====== (X/Z: >±9,223,372,036,854,775,807; 64-bit limit) ======
	\|		\|
	* The very last hard limit exists at X/Z: >±9,223,372,036,854,775,807 blocks—the mathematical limit of a signed 64-bit integer value (2<sup>63</sup> - 1). It is only realistically accessible by directly modifying the game to use 64-bit [[Minecraft:NBT format#Data types\|floats]] and/or {{w\|Integer (computer science)#Long integer\|long integers}}. Attempting to travel or load chunks beyond here is expected to cause the game to crash.		* The very last hard limit exists at X/Z: >±9,223,372,036,854,775,807 blocks—the mathematical limit of a signed 64-bit integer value (2<sup>63</sup> − 1). It is only realistically accessible by directly modifying the game to use 64-bit [[Minecraft:NBT format#Data types\|floats]] and/or {{w\|Integer (computer science)#Long integer\|long integers}}. Attempting to travel or load chunks beyond here is expected to cause the game to crash.
	\|		\|
	\|}		\|}
Line 66:		Line 66:
	\|-		\|-
	\|		\|
	====== (Y: ~~±2^1024~~; Absolute limit) ======		====== (Y: ±179,769,313,486,231,590,772,930,519,078,902,473,361,797,697,894,230,657,273,430,081,157,732,675,805,500,963,132,708,477,322,407,536,021,120,113,879,871,393,357,658,789,768,814,416,622,492,847,430,639,474,124,377,767,893,424,865,485,276,302,219,601,246,094,119,453,082,952,085,005,768,838,150,682,342,462,881,473,913,110,540,827,237,163,350,510,684,586,298,239,947,245,938,479,716,304,835,356,329,624,224,137,216; Absolute limit) ======
	\|		\|
	*The maximum possible [[Minecraft:Altitude\|height]] is 1.798×10<sup>308</sup> (2<sup>1024</sup>). Attempting to teleport beyond this limit will result in the value being interpreted as infinity, and the teleportation will fail. However, teleporting to a number that will round to 2<sup>1024</sup> will render the game for exactly 1 frame because it crashes.		*The maximum possible [[Minecraft:Altitude\|height]] is ~1.798×10<sup>308</sup> (2<sup>1024</sup>). Attempting to teleport beyond this limit will result in the value being interpreted as infinity, and the teleportation will fail. However, teleporting to a number that will round to 2<sup>1024</sup> will render the game for exactly 1 frame because it crashes.
	* The reason previous limits do not restrict going this high is because chunks do not load past Y: +320/-64, meaning that there is nothing to render except for snow and rain.		* The reason previous limits do not restrict going this high is because chunks do not load past Y: +320/-64, meaning that there is nothing to render except for snow and rain.
	\|		\|
Line 170:		Line 170:
	\|-		\|-
	\|		\|
	====== 64-bit floating point limit (X/Z: >~~±1.797693134862315907729305190789×10{{^\|308}}~~) ======		====== 64-bit floating point limit (X/Z: >±179,769,313,486,231,590,772,930,519,078,902,473,361,797,697,894,230,657,273,430,081,157,732,675,805,500,963,132,708,477,322,407,536,021,120,113,879,871,393,357,658,789,768,814,416,622,492,847,430,639,474,124,377,767,893,424,865,485,276,302,219,601,246,094,119,453,082,952,085,005,768,838,150,682,342,462,881,473,913,110,540,827,237,163,350,510,684,586,298,239,947,245,938,479,716,304,835,356,329,624,224,137,216) ======
	\|		\|
	* Because ~~1.797693134862315907729305190789×10{{^\|308}}~~ is the maximum 64-bit floating-point integer, it causes the player's X coordinate to roll over to read "Infinity".<ref>Video reupload https://www.youtube.com/watch?v=OiqM07e7Odw</ref> It is impossible to go further since this is the physical limit at which Java can render, and the game is expected to crash at this distance. The only way to go further is by using BigInt and BigDecimal mods.		* Because 2<sup>1024</sup> is the maximum 64-bit floating-point integer, it causes the player's X coordinate to roll over to read "Infinity".<ref>Video reupload https://www.youtube.com/watch?v=OiqM07e7Odw</ref> It is impossible to go further since this is the physical limit at which Java can render, and the game is expected to crash at this distance. The only way to go further is by using BigInt and BigDecimal mods.
	\| [[File:Infinity Java X Y Z.png\|thumb\|240px\|]]		\| [[File:Infinity Java X Y Z.png\|thumb\|240px\|]]
	\|		\|