Distance effects in Java Edition

From Minecraft Wiki
Jump to: navigation, search

In Java Edition, certain game mechanics start to break down as the player reaches the edges of the world.

Vanilla bounds (X/Y/Z ±0–29,999,984)[edit]

Entities[edit]

  • TNT ignited by other explosions is generated at the wrong place.[1]
  • Mob spawning loses precision[2]
  • Mob pathfinding may start to break down after 2^24 or so blocks, as there have been reports of mobs rotating on their own accord[3]
  • Detector rails do not correctly detect minecarts[4]

Particles[edit]

Rendering[edit]

  • Rain and snow appear stretched out at large heights.[17]
  • Enchanting tables do not detect when the player is there correctly[18]

World generation[edit]

  • Minecarts with chests generated in mineshafts are generated in incorrect positions[19]
  • The generation of mineral veins becomes slightly more blocky[20]

Beyond the world border (X/Z ±29,999,984–2,147,483,647)[edit]

The contents of this page are not supported by Mojang Studios or the Minecraft Wiki.

Horizontal distances far beyond 30 million blocks cannot be reached without game modification. Mods such as the FarLands mod can be used to move the world border further out to make these regions accessible.

Entities[edit]

  • Mob pathfinding breaks down considerably, with mobs tending to aggregate at certain spots
  • The player can get stuck in the sides of blocks after 230.

Light[edit]

  • Light stops working beyond 225.

Rendering[edit]

  • Rendering order of transparent blocks breaks down, as the order they are rendered in use a player position which loses precision.
  • Rain and snow fade at certain horizontal distances.
  • Entities lose their shadows after 229.

Sounds[edit]

  • Sounds break down especially after 228.

World generation[edit]

  • Ore vein generation breaks down at high distances, which causes crashes between 226 and 227.
  • Villages just break after 230.

Game[edit]

  • Game crashes after 231, which cannot be remedied without intense modifications to the game. Attempts have been made to exceed this limit and allow terrain and the game to work further out,[21] although doing so would simply not be worthwhile.

Explanation[edit]

The following paragraphs mainly concern pre-Beta 1.8 distance effects.

Giant redstone past X/Z 1,073,741,824, which is halfway to X/Z 2,147,483,648. It appears as large as 128 blocks.

Many effects are noticeable after traveling millions of blocks away from the center of the map. The first effect that becomes evident from 0624 Infdev to Beta 1.7.3 is the jumpy or stuttering movement of the map. In old versions of Minecraft, when the game renders the map around the player, there are two different versions that are generated, the rendering of the blocks themselves (i.e. entities, how much the block generates) and the visual aspect to the blocks (e.g. the hitbox, block pixels etc.). In Java Edition Beta 1.7 and prior, the visual aspect of world rendering loses precision, resulting in the jumpy movement. The reason the world loses precision in the first place is that the rendering engine uses double-double precision, which determines the position of the world around the player. The rendering engine then uses a floating point integer to determine how far the already rendered blocks move around the player when they move. Unfortunately, this floating point integer cuts the double-double precision number in half, and thus the rendering engine doesn't have enough information to render the terrain correctly, and the information gets cut in half every time the player doubles their distance. Removing the floating text from the rendering engine fixes the stuttering movement.

This jumpy movement is notable even at an X/Z of ±16,384, becoming increasingly noticeable around ±524,288. The intensity of such glitches doubles every time the player passes a coordinate that is a power of two (e.g. 2,097,152 or 4,194,304). After about X/Z 16,777,216, the hitbox is a full block off, which makes placing and destroying blocks almost impossible. The floating point precision errors are no longer noticeable past X/Z 2,147,483,519, as surface textures stop rendering and blocks no longer generate. At the center of the world, the world would be off by only 14194304 (0.000000238...) blocks. Past the 32-bit limit, the world would be off by 256 blocks. For any position between n and 2n, where n is a power of 2, the world is offset by n8388608 blocks, or n524288 block pixels. The precision errors also affect entities like Redstone dust and ladders. If the player performs the "Spawn Chunk Glitch" (see Distance effects in Java Edition/Before Beta 1.8#Spawn chunk glitch (X/Z: ±524,288–X/Z: ±1,073,741,824), then Redstone dust and ladders become noticeably stretched. They double in size for every exponent of 2 that the player travels from here on out. At X/Z: 268,435,456, Redstone dust is larger than one chunk and at X/Z: 1,073,741,824, Redstone dust is 128 blocks wide. If terrain were to theoretically generate out to the 64-bit limit (X/Z: ±9,223,372,036,854,775,807), then the hitbox would be over 2.2 trillion blocks off and redstone dust would be 2.2 trillion blocks wide as well.

History[edit]

Note: This history table is sorted by when each case was fixed.

Introduced Fixed/changed Error Example Notes
Classic or Indev Early Infdev[needs in-game testing] The wireframe hitbox of blocks becomes distorted and non-cubic at high distances.
Infdev 20100227 Early Infdev[needs in-game testing] World rendering loses precision in such a way that chunks become detached from each other. May have technically occurred earlier, but the world stopped rendering after less than 3000 blocks out anyway, so it would never have manifested anyway
Likely Indev Alpha v1.0.1 Gears appear visually stretched at high distances. Stretched gear.png "Fixed" by removing gears entirely, replacing the block with redstone wire.
Alpha v1.0.1 Beta 1.5 Redstone wire appears bugged at high distances when travelling up a block. Up broken redstone type 1.png
Likely Indev Beta 1.8
(pre)
Water and lavafalls render incorrectly at high distances. Distorted streams.png
Infdev 20100607 Beta 1.8
(pre)
Ladders appear visually stretched at high distances. Distorted ladder.png
Infdev 20100618 Beta 1.8
(pre)
Rails appear visually stretched at high distances. Infdev big rail.png
Infdev 20100624 Beta 1.8
(pre)
The terrain rendering appears offset and loses precision at high coordinates, giving way to the famous jitter of the Far Lands. Farlandsblockmovement.gif
Beta 1.3 Beta 1.8
(pre)
The top faces of redstone repeaters lose precision at high coordinates. Stretched repeater.png
Beta 1.5 Beta 1.8
(pre)
Powered rails and detector rails appear visually stretched at high distances. Redstone rail model bug.png
Beta 1.5 Beta 1.8
(pre)
Redstone wire appears offset from its base block, although otherwise correctly sized, when travelling up a block. Up broken redstone type 2.png
1.0.0
(Beta 1.9 Prerelease 4)
1.3.1
(12w18a)
Smoke from adding an eye of ender to an end portal frame loses precision. End portal frame precision error old.png "Fixed" by them not showing up at all anymore. Later regression in 19w14a to present when they show up again.
1.4.2
(12w34a)
1.4.4
(1.4.3)
The wall collision box loses precision. Wall collision precision loss.png
[needs in-game testing] 1.4.6
(12w49a)
Falling blocks at high distances can duplicate items.
1.0.0
(Beta 1.9 Prerelease 2)
1.5
(13w06a)
Fence and nether brick fence collision boxes are broken at high distances. Fence collision precision loss.png Likely due to changes allowing corner fences to not be a cuboid for collision, allowing them to be fallen through
Likely Indev 1.7.2
(13w38a)
Paintings are placed at the incorrect positions when far from the origin. Painting bug pre 38a.png
1.4.2
(12w34a)
1.7.2
(13w38a)[22]
Item frame rendering breaks at high coordinates, with the frames following the player's position somewhat. Item frame bug pre 38a.png
1.7.2
(13w38a)
1.7.2
(13w41a)[23]
Item frame and painting rendering breaks at high coordinates, with these entities following the player's position to an extent but also erratically changing position depending on the camera angle. 1.7 dev frame and painting.png perhaps from the self-luminous fix?
1.7.2
(13w38a)
1.7.2
(13w41a)[23]
Entities, tile entities, translucent blocks and the wireframe hitbox seem desynced from the terrain itself, especially pronounced with View Bobbing active. Hitbox too big.png Entities, block entities such as chests and signs, the wireframe hitbox shown around blocks, and ice and water are all in sync with each other. These become desynced from the terrain. The terrain is in sync with itself.
Likely Indev 1.8
(14w02a)
Lava ember particles lose precision. Lava particle precision loss old.png There exists a later regression from 18w10c to the current version.
Beta 1.7 1.8
(14w02a)
The arms of pistons lose precision, causing them to stretch or even escape the block itself if far enough. Piston model bug.png
Beta 1.8
(pre)
1.8
(14w02a)
Underwater particles lose precision. Water particle error early.png There exists a later regression from 18w10c to 1.15pre4.
1.0.0
(Beta 1.9 Prerelease 3)
1.8
(14w02a)
The inside faces of cauldrons lose precision, and can escape the block itself if far enough. Cauldron model bug.png May affect prerelease 2 with the mod.
1.3.1
(12w22a)
1.8
(14w02a)
The tripwire model loses precision, causing it to disappear or stretch when far enough.[needs in-game testing] Tripwire model bug.png
1.4.2
(12w34a)
1.8
(14w02a)
The inside faces of flower pots lose precision, and can escape the block itself if far enough. Flower pot model bug.png
1.5
(13w01a)
1.8
(14w02a)
The inside faces of hoppers lose precision, and can escape the block itself if far enough. Hopper model bug.png
Likely Indev 1.8
(14w17a)
Fire's model (on a wall) breaks at high distances and can z-fight with its base or become very outstretched from it. Fire model precision loss.png
Alpha v1.0.1 1.8
(14w17a)
Redstone wire appears bugged at high distances. Far lands redstone.png
[needs in-game testing] 1.8
(14w28a)
When breaking a container, the contained items are dropped in the wrong area. Furnace drop precision loss.png
1.8
(14w30a)
1.8
(14w30c)[24]
World rendering is now extremely broken at high distances, reminiscent of the distance effects of Infdev 20100227 or Pocket Edition v0.9.0 alpha. Shaky terrain.png This bug appears to be hardware-dependent and may not affect all computers.
Likely Indev 1.8
(14w32a)[25]
Torch flame particles are formed at the wrong positions at high distances. Torch precision loss.png
Likely Indev 1.8
(14w32a)[25]
Fire smoke particles are formed at the wrong positions at high distances. Fire precision loss.png
Likely Indev 1.8
(14w32a)[25]
Furnace flame particles are formed at the wrong positions at high distances. Furnace precision loss.png
[needs in-game testing] 1.8
(14w32a)
Sand, gravel, dragon eggs and anvils can become suspended in midair at high distances. Physics precision loss.png
[needs in-game testing] 1.8
(14w32a)
Minecarts are placed incorrectly at high distances. In some cases (usually stretches of rail), the minecart itself renders in the correct position but its shadow and rider are offset. Minecart precision loss.png
Beta 1.8
(pre)
1.8
(14w34c)
Void particles are formed incorrectly at high distances. 1.6.2 Farlands Void.png "Fixed" by removing them entirely.
1.7.2
(13w41a)
1.8
(pre2)
Paintings are placed at the incorrect positions when far from the origin. Painting precision loss.png
[needs in-game testing] 1.8
(pre2)[26]
There existed high-distance bugs with item frames.
Beta 1.5 1.8.2
(pre5)
Rain particles lose precision. Rain precision loss old.png There exists a later regression from 20w06a onwards.
Beta 1.8
(pre)
1.8.2
(pre5)
Smoke particles from rain hitting lava lose precision. Lava rain precision loss old.png There exists a later regression from 20w06a onwards.
Alpha v1.0.1 1.8.2
(pre5)[27]
Redstone torch particles lose precision. Redstone torch precision loss.png
1.9
(15w31a)
1.9
(15w33a)
The end gateway block's effect breaks when far from the origin. End gateway precision loss.png
Alpha v1.0.1 1.9
(15w37a)
Pressure plates detect activating entities wrongly when far from the origin. Pressure plate precision loss.png
Alpha v1.0.11 1.9
(15w38a)
The cactus collision box loses precision. Cactus collision precision loss.png
Beta 1.2 1.9
(15w38a)
The cake collision box loses precision. Cake collision precision loss.png
Beta 1.2 1.9
(15w38a)
The cake wireframe hitbox loses precision. Cake hitbox bug.png Likely due to MC-106300, making it impossible to see; was probably truly fixed alongside cactus
1.1
(12w01a)
1.9
(15w38a)
The fence gate collision box loses precision. Fence gate collision precision loss.png
Alpha v1.0.11 1.9
(15w49a)
The cactus wireframe hitbox loses precision. Cactus hitbox bug.png
Alpha v1.0.6 1.9
(16w04a)
Boats are placed at the wrong position when far enough. Boat precision loss.png
1.6
(13w16a)
1.9
(16w06a)
Lead knots are placed at the wrong position when far enough. Lead position precision loss.png
1.7.2
(13w41a)
1.9
(16w06a)
Item frames are placed at the incorrect positions when far from the origin. Item frame position precision loss 1.7.png
[needs in-game testing] 1.11
(16w40a)[28]
Piston placement no longer approximates the player's position using a precision-losing float. Placement precision loss.png
Beta 1.7 1.11
(16w40a)[29]
The extension and contraction animations of pistons act oddly, somewhat following the player around at high distances. Piston offset bug.png While this bug did affect Beta 1.7, it was impossible to notice due to the rest of the world being broken in the same way, such that the two effects would occur in unison. While world rendering was fixed in Beta 1.8, piston tile entity rendering was not, resulting in pistons looking out of place as a result until their fixing.
1.0.0
(Beta 1.9 Prerelease 3)
1.11
(16w40a)
The rendering of the end portal block breaks and z-fights at high distances. Black portal block.png In this version, the effect was made to remain static in respect to the screen, as opposed to moving with the player, a change made to end gateway blocks early in their development which also fixed high distance bugs.
Alpha v1.0.2 1.13
(17w47a)
Redstone ore particles are formed wrongly when far from the origin. Redstone ore precision loss.png
1.4.6
(12w49a)
1.14
(19w03a)
Firework rockets are placed at the wrong positions when far from the origin. Firework precision loss.png
Beta 1.3 1.14
(19w08a)
Beds place the player at their edge when used far from the origin, and drop them off at a precision-losing point when far as well. Bed precision loss.png
[needs in-game testing] 1.15
(19w39a)[30]
Falling blocks render very oddly at high distances. Falling block precision loss.png
Likely Indev 1.15
(pre1)
Black smoke particles from TNT exploding are generated at the wrong place at far distances. Explosion precision loss.png "Fixed" by removing these particles entirely, see MC-165991
Likely Indev 1.15
(pre4)[31]
When lit, TNT is generated at the wrong place at far distances. TNT offset bug.png
Infdev 20100625-2 1.15
(pre4)
Spawner particles lose precision. Spawner precision loss.png
Alpha v1.2.0 1.15
(pre4)
The particles of the nether portal block form at the wrong place high distances. Nether portal precision loss.png
1.0.0
(Beta 1.9 Prerelease)
1.15
(pre4)
Mycelium particles lose precision. Mycelium precision loss.png
1.0.0
(Beta 1.9 Prerelease 3)
1.15
(pre4)
The particles of the end portal block form at the wrong place high distances. End portal particle precision loss.png
1.0.0
(Beta 1.9 Prerelease 3)
1.15
(pre4)
Brewing stand particles lose precision. Brewing stand precision loss.png
1.0.0
(Beta 1.9 Prerelease 3)
1.15
(pre4)[32]
The book of the enchanting table faces the wrong direction when far enough from the origin. Enchantment table angle precision loss.png
1.5
(13w06a)
1.15
(pre4)
Particles from minecart with spawners lose precision. Spawner cart precision loss.png
1.7.2
(13w36a)
1.15
(pre4)
Particles from falling from a height lose precision. Fall precision loss.png
1.7.2
(13w36a)
1.15
(pre4)[33]
Particles from fishing lose precision. Fishing precision loss.png
1.8
(14w04a)
1.15
(pre4)
The /particle command generates particles at the wrong place at far distances. Particle command precision loss.png
1.8
(14w06a)
1.15
(pre4)
Barrier particles lose precision. Barrier precision loss.png
1.8
(14w33a)
1.15
(pre4)
Particles from breaking an armor stand lose precision. Armor stand precision loss.png
1.9
(15w31a)
1.15
(pre4)[34]
End gateway particles move to the wrong place. End gateway particle precision loss.png
1.9
(15w34b)
1.15
(pre4)
Dark heart particles from hurting mobs lose precision. Damage heart precision loss.png
1.9
(15w34c)
1.15
(pre4)
Particles from sweep attacks lose precision. Sweep attack precision loss.png
1.10
(16w20a)
1.15
(pre4)
The particles of suspended gravity affected blocks form at the wrong place at high distances. Physics particle precision loss.png
1.13
(18w07a)
1.15
(pre4)[35]
Squid ink particles lose precision. Squid precision loss.png
1.13
(18w10c)
1.15
(pre4)
Underwater particles lose precision. Underwater precision loss.png
1.13
(18w15a)
1.15
(pre4)[36]
Conduit particles move to the wrong place. Conduit precision loss.png
1.5
(13w04a)
1.16
(20w12a)[37]
Bone meal particles lose precision. Bone meal precision loss.png
Likely Indev Current When set off by another explosion, TNT is generated at the wrong place at far distances. Detonation offset.png
[needs in-game testing] Current Mineral veins generate more blocky at high distances. Ore gen precision loss.png
Beta 1.3 Current Red smoke from redstone repeaters loses precision. Repeater precision error.png
[needs in-game testing] Current Rain and snow appear stretched when the player is high up or low down enough. StretchedSnow.png
Beta 1.5 Current Detector rails do not detect the presence of minecarts properly. Detector rail precision loss.png
1.0.0
(Beta 1.9 Prerelease 3)
Current The book of the enchanting table sometimes does not open at all when far enough from the origin. Enchantment table presence precision loss.png
[needs in-game testing] Current Minecarts with chests that generate in mineshafts appear at the wrong locations at high distances. Minecart generation precision loss.png
[needs in-game testing] Current Dripping particles from leaves lose precision. Leaves precision error.png
1.13
(18w10c)
Current Embers from lava lose precision. Lava precision error.png
1.14
(19w03a)
Current Embers from campfires lose precision. Campfire precision error.png
1.14
(19w14a)
Current Smoke from adding an eye of ender to an end portal frame loses precision. End portal frame precision error.png due to fix for MC-10369
1.16
(20w06a)
Current Rain particles lose precision. Rain precision error.png Likely from fix to MC-131770
1.16
(20w06a)
Current Smoke particles from rain hitting lava lose precision. Rain precision error.png resurfaced due to MC-164158 and above ticket
1.16
(20w06a)
Current Smoke particles from rain hitting campfires lose precision. Campfire smoke precision loss.png Likely related to the very similar lava case
1.16
(20w06a)
Current Ambient particles from the crimson forest, soul sand valley and warped forest lose precision.
1.16
(20w15a)
Current Smoke particles from rain hitting soul campfires lose precision. Soul campfire smoke precision loss.png
1.16
(20w15a)
Current Ambient particles from the basalt deltas lose precision. Basalt deltas precision loss.png
1.16
(20w19a)
Current Particles from active redstone wire lose precision. Redstone dust precision error.png From the fix to MC-181566

Trivia[edit]

  • Up until 1.1, there existed a spectacular bug with the OptiFine mod (https://www.youtube.com/watch?v=jVSvf06rqBg , https://www.youtube.com/watch?v=FR9xvH-u21k , https://www.youtube.com/watch?v=a8CHopq3Tzw ) which would cause world rendering to completely break when travelling a far enough distance away, with effects manifesting as soon as 10000 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^integer 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.

Gallery[edit]

Fixed bugs[edit]

Particle errors[edit]

Model issues[edit]

References[edit]

External links[edit]