Minecraft:Java Edition distance effects/Historical effects - Revision history

SyncBot: Sync: updated from Minecraft

2026-09-24T11:11:17Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:11, 24 September 2026
Line 1:		Line 1:
	{{Italic title\|Java Edition}}		{{Italic title\|Java Edition}}
	{{cleanup}}		{{cleanup}}

	This page is a near-comprehensive list of all known '''distance effects''' throughout the game's history. A page that only accounts for those that affect the latest versions of the game can be found at [[Minecraft:Java Edition distance effects]].		This page is a near-comprehensive list of all known '''distance effects''' throughout the game's history. A page that only accounts for those that affect the latest versions of the game can be found at [[Minecraft:Java Edition distance effects]].

Line 285:		Line 284:
	\|-		\|-
	! [[Minecraft:Java Edition Infdev 20100624\|Infdev 20100624]]		! [[Minecraft:Java Edition Infdev 20100624\|Infdev 20100624]]
	! {{tc\|unknown\|[[Minecraft:Java Edition 1.8\|1.8]]?<br>{{~~checkthecode~~\|May exist in 1.3.1 to 1.7.10, if modded.}}}}		! {{tc\|unknown\|[[Minecraft:Java Edition 1.8\|1.8]]?<br>{{check the code\|May exist in 1.3.1 to 1.7.10, if modded.}}}}
	\| {{tc\|yes\|Fixed}}		\| {{tc\|yes\|Fixed}}
	\| World rendering loses precision at high distances, resulting in chunks disappearing from the player's view even if the player is inside them.		\| World rendering loses precision at high distances, resulting in chunks disappearing from the player's view even if the player is inside them.

SyncBot: Sync: updated from Minecraft

2026-09-13T11:20:02Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:20, 13 September 2026
Line 1:		Line 1:
			{{Italic title\|Java Edition}}
	{{cleanup}}		{{cleanup}}

SyncBot: Sync: updated from Minecraft

2026-07-31T11:11:32Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:11, 31 July 2026
Line 1,678:		Line 1,678:
	=== OptiFine ===		=== OptiFine ===
	Up until [[Minecraft:Java Edition 1.1\|1.1]], there was a bug with the OptiFine mod<ref>{{ytl\|jVSvf06rqBg}}</ref><ref>{{ytl\|FR9xvH-u21k}}</ref><ref>{{ytl\|a8CHopq3Tzw}}</ref> which would progressively break world rendering when traveling a far enough distance away, with effects manifesting as soon as 10,000 blocks. The effects would appear to get more intense continuously when moving far away from the center of the world, as opposed to having cutoffs every 2{{^\|''n''}} blocks, due to this rendering bug also taking rotation into account (although if the rotation is kept constant and along one axis discrete jumps become noticeable). The bug existed due to the mod undoing vanilla's fix for said bug.		Up until [[Minecraft:Java Edition 1.1\|1.1]], there was a bug with the OptiFine mod<ref>{{ytl\|jVSvf06rqBg}}</ref><ref>{{ytl\|FR9xvH-u21k}}</ref><ref>{{ytl\|a8CHopq3Tzw}}</ref> which would progressively break world rendering when traveling a far enough distance away, with effects manifesting as soon as 10,000 blocks. The effects would appear to get more intense continuously when moving far away from the center of the world, as opposed to having cutoffs every 2{{^\|''n''}} blocks, due to this rendering bug also taking rotation into account (although if the rotation is kept constant and along one axis discrete jumps become noticeable). The bug existed due to the mod undoing vanilla's fix for said bug.

			In November 2020, an unofficial patch for older versions of the OptiFine mod was released, fixing the aforementioned bug.<ref>{{Citation\|url=https://github.com/sp614x/optifine/issues/1233#issuecomment-735321866\|title=<nowiki>[Beta]</nowiki> Jittery textures on big coords for beta 1.7.3 optifine\|website=GitHub\|date=29 November 2020}}</ref>

	<gallery>		<gallery>

SyncBot: Sync: updated from Minecraft

2026-07-28T11:09:08Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:09, 28 July 2026
Line 36:		Line 36:
	\| At extreme coordinates, the player's AABB loses floating-point precision. As the player moves, rounding errors accumulate, causing the collision box to gradually stretch or shrink along the affected axis. This can result in standing on distant blocks, walking in mid-air after stepping off a ledge, or the collision box collapsing entirely, causing the player to fall through the world.		\| At extreme coordinates, the player's AABB loses floating-point precision. As the player moves, rounding errors accumulate, causing the collision box to gradually stretch or shrink along the affected axis. This can result in standing on distant blocks, walking in mid-air after stepping off a ledge, or the collision box collapsing entirely, causing the player to fall through the world.
	\| [[File:Indev 0223 collision bug.gif\|64px]]		\| [[File:Indev 0223 collision bug.gif\|64px]]
	\|		\| [[#pre-Classic - Indev 20100223 entity hitboxes\|''→ Go to section'']]
	\|-		\|-
	! {{tc\|unknown\|Likely from the start}}		! {{tc\|unknown\|Likely from the start}}
	! [[Minecraft:Java Edition Infdev 20100227-1414\|Infdev 20100227-1414]]~~{{verify\|was it fixed in this version, or was it present in this version and was fixed in the next?}}~~		! [[Minecraft:Java Edition Infdev 20100227-1414\|Infdev 20100227-1414]]
	\| {{tc\|yes\|Fixed}}		\| {{tc\|yes\|Fixed}}
	\| At coordinates beyond ±16,777,216, the stripe lands appear, because adjacent block positions can no longer be represented with full precision.		\| At coordinates beyond ±16,777,216, the stripe lands appear, because adjacent block positions can no longer be represented with full precision.
Line 46:		Line 46:
	\|-		\|-
	! {{tc\|unknown\|Likely from the start}}		! {{tc\|unknown\|Likely from the start}}
	! [[Minecraft:Java Edition Infdev 20100227-1414\|Infdev 20100227-1414]]~~{{verify\|was it fixed in this version, or was it present in this version and was fixed in the next?}}~~		! [[Minecraft:Java Edition Infdev 20100227-1414\|Infdev 20100227-1414]]
	\| {{tc\|~~yes~~\|~~Fixed~~}}		\| {{tc\|partial\|Changed}}
	\| At extreme distances, block geometry becomes distorted. Cubes appear warped and exhibit incorrect depth (Z) ordering.		\| At extreme distances, block geometry becomes distorted. Cubes appear warped and exhibit incorrect depth (Z) ordering.
	\| [[File:RubyDung rendering precision loss.gif\|64px]] [[File:Indev 0223 rendering precision loss.gif\|64px]]		\| [[File:RubyDung rendering precision loss.gif\|64px]] [[File:Indev 0223 rendering precision loss.gif\|64px]]
Line 53:		Line 53:
	\|-		\|-
	! {{tc\|unknown\|Likely from the start}}		! {{tc\|unknown\|Likely from the start}}
	! [[Minecraft:Java Edition Infdev 20100227-1414\|Infdev 20100227-1414]]~~{{verify\|was it fixed in this version, or was it present in this version and was fixed in the next?}}~~		! [[Minecraft:Java Edition Infdev 20100227-1414\|Infdev 20100227-1414]]
	\| {{tc\|yes\|Fixed}}		\| {{tc\|yes\|Fixed}}
	\| Entities use 32-bit floats for position, rather than doubles.		\| Entities use 32-bit floats for position, rather than doubles.
	\|		\|
	\| [[#Indev entity movement\|''→ Go to section'']]		\| [[#pre-Classic - Indev 20100223 entity movement\|''→ Go to section'']]
	\|-		\|-
	! {{tc\|unknown\|Likely from the start}}		! {{tc\|unknown\|Likely from the start}}
	! [[Minecraft:Java Edition Infdev 20100227-1414\|Infdev 20100227-1414]]~~{{verify\|was it fixed in this version, or was it present in this version and was fixed in the next?}}~~		! [[Minecraft:Java Edition Infdev 20100227-1414\|Infdev 20100227-1414]]
	\| {{tc\|yes\|Fixed}}		\| {{tc\|yes\|Fixed}}
	\| Entities & player AABB hitbox lose precision past X/Z: +8,388,608, resulting in to flattened hitbox, which makes them fall into a void.		\| Entities & player AABB hitbox lose precision past X/Z: +8,388,608, resulting in to flattened hitbox, which makes them fall into a void.
	\|		\|
	\|		\| [[#pre-Classic - Indev 20100223 entity hitboxes\|''→ Go to section'']]
	\|-		\|-
	! [[Minecraft:Java Edition Infdev 20100227-1414\|Infdev 20100227-1414]]		! [[Minecraft:Java Edition Infdev 20100227-1414\|Infdev 20100227-1414]]
Line 71:		Line 71:
	\| Blocks AABB hitbox lose precision past X/Z: +16,777,216.		\| Blocks AABB hitbox lose precision past X/Z: +16,777,216.
	\|		\|
	\|		\| [[#Infdev 20100227 blocks collision issue\|''→ Go to section'']]
	\|-		\|-
	! [[Minecraft:Java Edition Pre-classic rd-160052\|rd-160052]]		! [[Minecraft:Java Edition Pre-classic rd-160052\|rd-160052]]
Line 85:		Line 85:
	\| The outline box of blocks shakes and jitters considerably at high distances.		\| The outline box of blocks shakes and jitters considerably at high distances.
	\| [[File:Outline box rendering precision loss.png\|64px]]		\| [[File:Outline box rendering precision loss.png\|64px]]
	\| [[#~~Indev/~~Infdev hitbox rendering issue\|''→ Go to section'']]		\| [[#Classic - Infdev 20100227 hitbox rendering issue\|''→ Go to section'']]
	\|-		\|-
	! [[Minecraft:Java Edition Infdev 20100227-1414\|Infdev 20100227-1414]]		! [[Minecraft:Java Edition Infdev 20100227-1414\|Infdev 20100227-1414]]
Line 117:		Line 117:
	![[Minecraft:Java Edition Infdev 20100227-1414\|Infdev 20100227-1414]]		![[Minecraft:Java Edition Infdev 20100227-1414\|Infdev 20100227-1414]]
	![[Minecraft:Java Edition Infdev 20100327\|Infdev 20100327]]		![[Minecraft:Java Edition Infdev 20100327\|Infdev 20100327]]
	\|{{tc\|~~yes~~\|~~Fixed~~}}		\|{{tc\|partial\|Changed}}
	\|All generation beyond 2<sup>25</sup> is completely stone, up to the world height.		\|All generation beyond 2<sup>25</sup> is completely stone, up to the world height.
	\|[[File:Farlandsnotchededge.png\|width=64x64]]		\|[[File:Farlandsnotchededge.png\|width=64x64]]
Line 1,531:		Line 1,531:


	==== ~~Indev/~~Infdev hitbox rendering issue ====		==== Classic - Infdev 20100227 hitbox rendering issue ====
	{{cleanup\|section=1}}		{{cleanup\|section=1}}
	* Every power of 2 that the player goes, the hitbox of the block that the player is facing becomes more and more distorted.		* Every power of 2 that the player goes, the hitbox of the block that the player is facing becomes more and more distorted.
Line 1,544:		Line 1,544:

	=== Gameplay ===		=== Gameplay ===
	==== Indev entity movement ====		==== pre-Classic - Indev 20100223 entity movement ====
	{{cleanup\|section=1}}		{{cleanup\|section=1}}
	* Every power of 2 that the player goes, it becomes harder and harder to walk along the axis the player is traveling on.		* Every power of 2 that the player goes, it becomes harder and harder to walk along the axis the player is traveling on.
	* At X/Z ±4,194,304, the player falls through the blocks. However, if the player teleports beyond this point they can still stand on the blocks ~~but cannot move along that axis~~.		* At X/Z ±4,194,304, the player & entities cannot move along that axis anymore.

			Prior to Infdev, all entity positions are tracked using single-precision 32-bit floats rather than 64-bit doubles. As the coordinate values grow, the distance between representable floating-point values increases, causing movement calculations to snap to a rigid grid.

			==== pre-Classic - Indev 20100223 entity hitboxes ====
			{{cleanup\|section=1}}
			* Every power of 2, hitbox has higher chance to stretch or collapse entirely.
			* At X/Z ±524,288, the entities collision box can shrink or stretch everytime they move, this as well happens to player's hitbox.
			* At X/Z ±2,097,152, the entities hitbox has high chance to collapse entirely, this makes them slip through the world into void. Sometimes hitbox can stretch to insane lengths.
			* At X/Z ±4,194,304, the player falls through the blocks. However, if the player teleports beyond this point they can still stand on the blocks. Also if entity gets teleported at exactly ±4,194,304 and moves back below ±4,194,304, their collision box will stretch to crazy length.
	* At X/Z ±8,388,608, the player can no longer stand on the blocks and falls into the void.		* At X/Z ±8,388,608, the player can no longer stand on the blocks and falls into the void.

	==== Infdev ~~0227~~ blocks collision issue ====		Because Axis-Aligned Bounding Boxes (AABBs) rely on 32-bit float variables in these versions, rounding errors accumulate rapidly during positional checks. Depending on the size of the specific bounding box, total failure occurs between ±8,388,608 and ±33,554,432.

			==== Infdev 20100227 blocks collision issue ====
	{{cleanup\|section=1}}		{{cleanup\|section=1}}
	* X/Z ±16,777,216: Blocks begin to lose their collision due to floating-point precision limitations. Their collision boxes become distorted into alternating "stripes," allowing the player to stand only on every other two blocks while falling through the rest.		* X/Z ±16,777,216: Blocks begin to lose their collision due to floating-point precision limitations. Their collision boxes become distorted into alternating "stripes," allowing the player to stand only on every other two blocks while falling through the rest.
	* Beyond X/Z ±33,554,432, collision degrades further until it effectively becomes a single flat plane. Players attempting to walk normally will fall into the void, but if they happen to stand exactly on the remaining collision plane, they can stand on it indefinitely until they move.		* Beyond X/Z ±33,554,432, collision degrades further until it effectively becomes a single flat plane. Players attempting to walk normally will fall into the void, but if they happen to stand exactly on the remaining collision plane, they can stand on it indefinitely until they move.

			When AABBs collisions and entity coordinates were changed from float to double, a typecasting oversight in Block.java causes collision boundaries to fail past ±16,777,216 blocks. While entity coordinates and block files successfully transitioned to use 64-bit doubles, the bounding box coordinate returns (getCollisionBoundingBoxFromPool) route integer metrics through an unoptimized single-precision float conversion before returning them as a double. Because 32-bit floats cannot precisely represent unique sequential integers past 2^24, tracking computations truncate into discrete intervals, creating ghost stripes where physical collision vanishes entirely despite visible blocks remaining stable.

	==== Sculk vibration positioning errors ====		==== Sculk vibration positioning errors ====

SyncBot: Sync: updated from Minecraft

2026-07-26T11:07:37Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:07, 26 July 2026
Line 34:		Line 34:
	! [[Minecraft:Java Edition Infdev 20100227-1414\|Infdev 20100227-1414]]		! [[Minecraft:Java Edition Infdev 20100227-1414\|Infdev 20100227-1414]]
	\| {{tc\|yes\|Fixed}}		\| {{tc\|yes\|Fixed}}
	\| At coordinates ~~beyond ±2~~,~~097~~,~~152~~, ~~block~~ collision ~~boxes break down~~. ~~The player~~ can ~~step off a solid block but remain~~ walking in mid-air ~~as if~~ the ~~block's physical boundary is stretching out or "following" them~~.		\| At extreme coordinates, the player's AABB loses floating-point precision. As the player moves, rounding errors accumulate, causing the collision box to gradually stretch or shrink along the affected axis. This can result in standing on distant blocks, walking in mid-air after stepping off a ledge, or the collision box collapsing entirely, causing the player to fall through the world.
	\| [[File:Indev 0223 collision bug.gif\|64px]]		\| [[File:Indev 0223 collision bug.gif\|64px]]
	\|		\|
Line 42:		Line 42:
	\| {{tc\|yes\|Fixed}}		\| {{tc\|yes\|Fixed}}
	\| At coordinates beyond ±16,777,216, the stripe lands appear, because adjacent block positions can no longer be represented with full precision.		\| At coordinates beyond ±16,777,216, the stripe lands appear, because adjacent block positions can no longer be represented with full precision.
	\| [[File:RubyDung StripeLands.png\|64px]]		\| [[File:RubyDung StripeLands.png\|64px]] [[File:Indev 0223 stripe lands.png\|64px]]
	\|		\|
	\|-		\|-
Line 49:		Line 49:
	\| {{tc\|yes\|Fixed}}		\| {{tc\|yes\|Fixed}}
	\| At extreme distances, block geometry becomes distorted. Cubes appear warped and exhibit incorrect depth (Z) ordering.		\| At extreme distances, block geometry becomes distorted. Cubes appear warped and exhibit incorrect depth (Z) ordering.
	\| [[File:RubyDung rendering precision loss.gif\|64px]] [[File:Indev 0223 ~~far away~~.gif\|64px]]		\| [[File:RubyDung rendering precision loss.gif\|64px]] [[File:Indev 0223 rendering precision loss.gif\|64px]]
	\| [[#pre-Classic - Indev 20100223 block deformation & depth precision\|''→ Go to section'']]		\| [[#pre-Classic - Indev 20100223 block deformation & depth precision\|''→ Go to section'']]
	\|-		\|-
Line 62:		Line 62:
	! [[Minecraft:Java Edition Infdev 20100227-1414\|Infdev 20100227-1414]]{{verify\|was it fixed in this version, or was it present in this version and was fixed in the next?}}		! [[Minecraft:Java Edition Infdev 20100227-1414\|Infdev 20100227-1414]]{{verify\|was it fixed in this version, or was it present in this version and was fixed in the next?}}
	\| {{tc\|yes\|Fixed}}		\| {{tc\|yes\|Fixed}}
	\| Entities & player AABB hitbox lose precision past X/Z: +8,388,608, resulting in to flattened hitbox, which makes them fall into a void~~, sometimes can happen as early as X/Z: +524,288~~.		\| Entities & player AABB hitbox lose precision past X/Z: +8,388,608, resulting in to flattened hitbox, which makes them fall into a void.
	\|		\|
	\|		\|

SyncBot: Sync: updated from Minecraft

2026-07-25T11:06:53Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:06, 25 July 2026
Line 30:		Line 30:
	\| [[File:Weather rendering precision loss 1.png\|64px]]		\| [[File:Weather rendering precision loss 1.png\|64px]]
	\| Effectively returned in later versions with the introduction of Winter Mode, and proper weather in Beta 1.5		\| Effectively returned in later versions with the introduction of Winter Mode, and proper weather in Beta 1.5
			\|-
			! {{tc\|unknown\|Likely from the start}}
			! [[Minecraft:Java Edition Infdev 20100227-1414\|Infdev 20100227-1414]]
			\| {{tc\|yes\|Fixed}}
			\| At coordinates beyond ±2,097,152, block collision boxes break down. The player can step off a solid block but remain walking in mid-air as if the block's physical boundary is stretching out or "following" them.
			\| [[File:Indev 0223 collision bug.gif\|64px]]
			\|
	\|-		\|-
	! {{tc\|unknown\|Likely from the start}}		! {{tc\|unknown\|Likely from the start}}
Line 59:		Line 66:
	\|		\|
	\|-		\|-
	! ~~{{tc~~\|~~unknown\|Likely from the start}}~~		! [[Minecraft:Java Edition Infdev 20100227-1414\|Infdev 20100227-1414]]
	! [[Minecraft:Java Edition Infdev 20100313\|Infdev 20100313]]<ref name="notch">Likely due to changes mentioned in https://notch.tumblr.com/post/443693773/the-world-is-bigger-now ([https://web.archive.org/web/20111212094340/https://notch.tumblr.com/post/443693773/the-world-is-bigger-now archive])</ref>		! [[Minecraft:Java Edition Infdev 20100313\|Infdev 20100313]]<ref name="notch">Likely due to changes mentioned in https://notch.tumblr.com/post/443693773/the-world-is-bigger-now ([https://web.archive.org/web/20111212094340/https://notch.tumblr.com/post/443693773/the-world-is-bigger-now archive])</ref>
	\| {{tc\|yes\|Fixed}}		\| {{tc\|yes\|Fixed}}
Line 1,533:		Line 1,540:

	==== Falling block rendering issue ====		==== Falling block rendering issue ====
	~~{{empty section}}~~
	~~The shape of the block distorting and becoming non-cubic is also possible on some GPUs.~~
	[[File:Falling Block Glitch.png\|alt=Shape of gravel distorting at high distances\|thumb\|376x376px\|Falling block rendering issues at high distances]]		[[File:Falling Block Glitch.png\|alt=Shape of gravel distorting at high distances\|thumb\|376x376px\|Falling block rendering issues at high distances]]
			The shape of the block distorting and becoming non-cubic is also possible on some GPUs.{{info needed\|Is this the same as the infdev hitbox distortion?}}

	=== Gameplay ===		=== Gameplay ===

SyncBot: Sync: updated from Minecraft

2026-07-24T11:06:35Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:06, 24 July 2026
Line 13:		Line 13:
	* Test item frame drop location throughout history		* Test item frame drop location throughout history
	* {{bug\|MC-205680}}		* {{bug\|MC-205680}}
	* Camera rotation: {{bug\|MC-306546}}, {{bug\|MC-131146}}}}		* Camera rotation: {{bug\|MC-306546}}, {{bug\|MC-131146}}
			* {{bug\|MC-308844}}
			* {{bug\|MC-280133}} needs a visual example}}
	{\| class="wikitable sortable mw-collapsible" data-description="Spatial distance effect history"		{\| class="wikitable sortable mw-collapsible" data-description="Spatial distance effect history"
	! Added		! Added
Line 30:		Line 32:
	\|-		\|-
	! {{tc\|unknown\|Likely from the start}}		! {{tc\|unknown\|Likely from the start}}
	! [[Minecraft:Java Edition Infdev 20100227-1414\|Infdev 20100227-1414]]		! [[Minecraft:Java Edition Infdev 20100227-1414\|Infdev 20100227-1414]]{{verify\|was it fixed in this version, or was it present in this version and was fixed in the next?}}
	\| {{tc\|yes\|Fixed}}		\| {{tc\|yes\|Fixed}}
	\| At coordinates beyond ±16,777,216, the stripe lands appear, because adjacent block positions can no longer be represented with full precision.		\| At coordinates beyond ±16,777,216, the stripe lands appear, because adjacent block positions can no longer be represented with full precision.
Line 37:		Line 39:
	\|-		\|-
	! {{tc\|unknown\|Likely from the start}}		! {{tc\|unknown\|Likely from the start}}
	! [[Minecraft:Java Edition Infdev 20100227-1414\|Infdev 20100227-1414]]		! [[Minecraft:Java Edition Infdev 20100227-1414\|Infdev 20100227-1414]]{{verify\|was it fixed in this version, or was it present in this version and was fixed in the next?}}
	\| {{tc\|yes\|Fixed}}		\| {{tc\|yes\|Fixed}}
	\| At extreme distances, block geometry becomes distorted. Cubes appear warped and exhibit incorrect depth (Z) ordering.		\| At extreme distances, block geometry becomes distorted. Cubes appear warped and exhibit incorrect depth (Z) ordering.
Line 44:		Line 46:
	\|-		\|-
	! {{tc\|unknown\|Likely from the start}}		! {{tc\|unknown\|Likely from the start}}
	! [[Minecraft:Java Edition Infdev 20100227-1414\|Infdev 20100227-1414]]		! [[Minecraft:Java Edition Infdev 20100227-1414\|Infdev 20100227-1414]]{{verify\|was it fixed in this version, or was it present in this version and was fixed in the next?}}
	\| {{tc\|yes\|Fixed}}		\| {{tc\|yes\|Fixed}}
	\| Entities use 32-bit floats for position, rather than doubles.		\| Entities use 32-bit floats for position, rather than doubles.
Line 51:		Line 53:
	\|-		\|-
	! {{tc\|unknown\|Likely from the start}}		! {{tc\|unknown\|Likely from the start}}
	! [[Minecraft:Java Edition Infdev 20100227-1414\|Infdev 20100227-1414]]		! [[Minecraft:Java Edition Infdev 20100227-1414\|Infdev 20100227-1414]]{{verify\|was it fixed in this version, or was it present in this version and was fixed in the next?}}
	\| {{tc\|yes\|Fixed}}		\| {{tc\|yes\|Fixed}}
	\| Entities & player AABB hitbox lose precision past X/Z: +8,388,608, resulting in to flattened hitbox, which makes them fall into a void, sometimes can happen as early as X/Z: +524,288.		\| Entities & player AABB hitbox lose precision past X/Z: +8,388,608, resulting in to flattened hitbox, which makes them fall into a void, sometimes can happen as early as X/Z: +524,288.

SyncBot: Sync: updated from Minecraft

2026-07-17T11:10:01Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:10, 17 July 2026
Line 1,499:		Line 1,499:
	{{info needed section}}		{{info needed section}}
	Whether or not this issue occurs appears to be tied to the VBOs setting - switching this on will cause the issue to go away, and disabling VBOs will cause it to happen.		Whether or not this issue occurs appears to be tied to the VBOs setting - switching this on will cause the issue to go away, and disabling VBOs will cause it to happen.
			This regression may have occurred because the 1.8 rendering engine was being rewritten. Previous versions relied on masking chunk coordinates (0–1023, or 0–511 in older versions) as a temporary workaround for floating-point precision issues. During the rewrite, this workaround appears to have been removed before camera-relative rendering was introduced, briefly exposing the chunk detachment bug.
			The VBO rendering path, however, appears to upload chunk geometry relative to the camera (or otherwise uses a different transformation pipeline), avoiding the precision loss responsible for the detached chunks.

	Stuttering and falling block entity problems also occur with this glitch! Falling block entities can glitch and have their hitboxes offset in weird ways!		Stuttering and falling block entity problems also occur with this glitch! Falling block entities can glitch and have their hitboxes offset in weird ways!

SyncBot: Sync: updated from Minecraft

2026-07-10T11:15:40Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:15, 10 July 2026
Line 1,483:		Line 1,483:

	==== pre-Classic - Indev 20100223 block deformation & depth precision ====		==== pre-Classic - Indev 20100223 block deformation & depth precision ====
	At extreme distances from the origin, block geometry becomes distorted due to floating-point precision loss. Cubes appear warped and exhibit incorrect depth (Z) ordering, causing surfaces to flicker or render through neighboring blocks. This issue is present from [[Minecraft:pre-Classic]] through [[Minecraft:Indev 20100223]]. Beginning with [[Minecraft:Infdev 20100227]] the ~~tessellator~~ and world renderer translation were changed these artifacts are no longer present and are instead replaced by detached chunks at large distances.		At extreme distances from the origin, block geometry becomes distorted due to floating-point precision loss. Cubes appear warped and exhibit incorrect depth (Z) ordering, causing surfaces to flicker or render through neighboring blocks. This issue is present from [[Minecraft:pre-Classic]] through [[Minecraft:Indev 20100223]]. Beginning with [[Minecraft:Infdev 20100227]] the block renderer and world renderer translation were changed these artifacts are no longer present and are instead replaced by detached chunks at large distances.
	These rendering artifacts are visually identical to those observed in [[Minecraft:Beta 1.7.3]] with OptiFine at extreme distances, exhibiting the same block deformation and incorrect depth (Z) ordering.		These rendering artifacts are visually identical to those observed in [[Minecraft:Beta 1.7.3]] with OptiFine at extreme distances, exhibiting the same block deformation and incorrect depth (Z) ordering.

Line 1,494:		Line 1,494:
	* X/Z: 268,435,456: Gaps between chunks become multiple blocks long, causing the world to look like either stripes or a grid (depending on the axes which exceed this distance).		* X/Z: 268,435,456: Gaps between chunks become multiple blocks long, causing the world to look like either stripes or a grid (depending on the axes which exceed this distance).

	Note: This issue wasn't in game versions prior to [[Minecraft:Infdev 20100227]], but instead the blocks geometry warped and exhibited incorrect depth (Z) ordering. Following the ~~tessellator~~ and world renderer translation changes introduced in [[Minecraft:Infdev 20100227]], these artifacts were replaced by detached chunks at large distances.<br />A similar glitch occurred in snapshot 14w30a/b.		Note: This issue wasn't in game versions prior to [[Minecraft:Infdev 20100227]], but instead the blocks geometry warped and exhibited incorrect depth (Z) ordering. Following the block renderer and world renderer translation changes introduced in [[Minecraft:Infdev 20100227]], these artifacts were replaced by detached chunks at large distances.<br />A similar glitch occurred in snapshot 14w30a/b.

	==== 14w30a/b chunk detaching issue ====		==== 14w30a/b chunk detaching issue ====
Line 1,540:		Line 1,540:
	* At X/Z ±8,388,608, the player can no longer stand on the blocks and falls into the void.		* At X/Z ±8,388,608, the player can no longer stand on the blocks and falls into the void.

	==== Infdev 0227 blocks ~~solidness~~ issue ====		==== Infdev 0227 blocks collision issue ====
	{{cleanup\|section=1}}		{{cleanup\|section=1}}
	* X/Z ±16,777,216: Blocks ~~are no longer solid;~~ the player ~~falls and hits~~ a ~~layer of lava~~.		* X/Z ±16,777,216: Blocks begin to lose their collision due to floating-point precision limitations. Their collision boxes become distorted into alternating "stripes," allowing the player to stand only on every other two blocks while falling through the rest.
			* Beyond X/Z ±33,554,432, collision degrades further until it effectively becomes a single flat plane. Players attempting to walk normally will fall into the void, but if they happen to stand exactly on the remaining collision plane, they can stand on it indefinitely until they move.

	==== Sculk vibration positioning errors ====		==== Sculk vibration positioning errors ====

SyncBot: Sync: updated from Minecraft

2026-07-07T11:08:56Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:08, 7 July 2026
Line 41:		Line 41:
	\| At extreme distances, block geometry becomes distorted. Cubes appear warped and exhibit incorrect depth (Z) ordering.		\| At extreme distances, block geometry becomes distorted. Cubes appear warped and exhibit incorrect depth (Z) ordering.
	\| [[File:RubyDung rendering precision loss.gif\|64px]] [[File:Indev 0223 far away.gif\|64px]]		\| [[File:RubyDung rendering precision loss.gif\|64px]] [[File:Indev 0223 far away.gif\|64px]]
	\| [[#~~RubyDung~~ - Indev 20100223 block deformation & depth precision\|''→ Go to section'']]		\| [[#pre-Classic - Indev 20100223 block deformation & depth precision\|''→ Go to section'']]
	\|-		\|-
	! {{tc\|unknown\|Likely from the start}}		! {{tc\|unknown\|Likely from the start}}
Line 90:		Line 90:
	\| Frustum loses precision and the world periodically stops rendering entirely when the player is at far distances.		\| Frustum loses precision and the world periodically stops rendering entirely when the player is at far distances.
	\| [[File:Frustum_precision_loss.gif\|64px]]		\| [[File:Frustum_precision_loss.gif\|64px]]
	\| [[#~~RubyDung~~ - Infdev 20100227 frustum issue\|''→ Go to section'']]		\| [[#pre-Classic - Infdev 20100227 frustum issue\|''→ Go to section'']]
	\|-		\|-
	! [[Minecraft:Java Edition Infdev 20100313\|Infdev 20100313]]		! [[Minecraft:Java Edition Infdev 20100313\|Infdev 20100313]]
Line 1,483:		Line 1,483:

	==== pre-Classic - Indev 20100223 block deformation & depth precision ====		==== pre-Classic - Indev 20100223 block deformation & depth precision ====
	At extreme distances from the origin, block geometry becomes distorted due to floating-point precision loss. Cubes appear warped and exhibit incorrect depth (Z) ordering, causing surfaces to flicker or render through neighboring blocks. This issue is present from [[Minecraft:pre-Classic]] through [[Minecraft:Indev 20100223]]. Beginning with [[Minecraft:Infdev 20100227]]~~. Following~~ the tessellator and world renderer translation ~~changes~~ these artifacts are no longer present and are instead replaced by detached chunks at large distances.		At extreme distances from the origin, block geometry becomes distorted due to floating-point precision loss. Cubes appear warped and exhibit incorrect depth (Z) ordering, causing surfaces to flicker or render through neighboring blocks. This issue is present from [[Minecraft:pre-Classic]] through [[Minecraft:Indev 20100223]]. Beginning with [[Minecraft:Infdev 20100227]] the tessellator and world renderer translation were changed these artifacts are no longer present and are instead replaced by detached chunks at large distances.
	These rendering artifacts are visually identical to those observed in [[Minecraft:Beta 1.7.3]] with OptiFine at extreme distances, exhibiting the same block deformation and incorrect depth (Z) ordering.		These rendering artifacts are visually identical to those observed in [[Minecraft:Beta 1.7.3]] with OptiFine at extreme distances, exhibiting the same block deformation and incorrect depth (Z) ordering.