Java Edition distance effects

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

Entities

 * TNT ignited by other explosions is generated at the wrong place.
 * Mob spawning loses precision
 * 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
 * Detector rails do not correctly detect minecarts

Particles

 * Bone meal particles lose precision.
 * Smoke from adding eye of enders to end portal frames loses precision.
 * Ember particles from campfires lose precision.
 * Ember particles and popping sounds from lava lose precision.
 * Dripping particles from leaves in rain lose precision.
 * Redstone repeater particles lose precision
 * Particles which exist in Soul Sand Valley, Crimson Forest, Warped Forest and Basalt Deltas biomes lose precision
 * Particles from rain landing
 * Particles from rain hitting lava
 * Particles from redstone dust
 * Extra smoke from rain hitting campfires and soul campfires

Rendering

 * Rain and snow appear stretched out at large heights.
 * Enchanting tables do not detect when the player is there correctly

World generation

 * Minecarts with chests generated in mineshafts are generated in incorrect positions
 * The generation of mineral veins becomes slightly more blocky

Beyond the world border (X/Z ±29,999,984–2,147,483,647)
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

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

Light

 * Light stops working beyond 2.

Rendering

 * 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 2.

Sounds

 * Sounds break down especially after 2.

World generation

 * Ore vein generation breaks down at high distances, which causes crashes between 2 and 2.
 * Villages just break after 2.

Game

 * Game crashes after 2, 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, although doing so would simply not be worthwhile.

Explanation
The following paragraphs mainly concern pre-Beta 1.8 distance effects. 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 $1/4194304$ (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 $n/8388608$ blocks, or $n/524288$ 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, 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
Note: This history table is sorted by when each case was fixed.

Trivia

 * Up until 1.1, there existed a spectacular bug with the OptiFine mod 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.