Bedrock Edition distance effects

This article needs cleanup to comply with the style guide. ^[discuss^]

Please help improve this page. The talk page may contain suggestions.
Reason: Organize this page more like Java Edition distance effects - should allow a lot more in-depth analysis of each effect

This feature is exclusive to Bedrock Edition.

As the player travels far from the world origin in Bedrock Edition, the world starts to behave abnormally. This is mostly caused by precision loss of the 32-bit floating point numbers used for location, which dedicates only 23 bits to the fraction; thus, for any position between n and 2n, where n is a power of 2, the precision error makes the world (including blocks and entities) offset by ⁿ⁄_8388608 blocks, or ⁿ⁄₅₂₄₂₈₈ block pixels (e.g. at between 16777216 and 33554432, coordinates of all entities are multiples of 2, and only blocks at these coordinates can be rendered; blocks not at these values visually snap to them).

Key
Very minor effects
Minor effects / minor vertical effects
Medium effects
Lower major effects
Upper major effects
Far Lands
Stripe Lands / major vertical effects
Technical alert point

Minor effects (X/Z ±1–131,071)

Bedrock Edition uses 32-bit floating points for many of its calculations, such as the player's position. When the player moves, the player changes position each tick, and this change is affected by floating point precision errors. At slow speeds/high coordinates, this change in position is considered negligible, meaning that the player does not move at all. The amount of precision error doubles at every power of 2.

Note that while the positions of the centers of entities are stored in NBT, the positions of the hitbox corners are stored in memory. If the player is crossing a power of 2, these corners may move at different speeds, thus changing the hitbox size. The hitbox size resets to 0.6 in certain situations, such as reloading the world, using the /tp command, and others.^{[more information needed]} However, the player can shrink to size 0, making it possible to fall through the edges of blocks and into the void (MCPE-39299).

There are several ways to slow the player’s movement, such as sneaking, status effects, using an item (e.g. drawing back a bow), or certain blocks (such as cobwebs). In addition, moving diagonally decreases the player’s speed on any given axis. Moving with a solid block in front at slight diagonal causes the player to move sideways as slow as the player’s coordinates allow.


Coordinates		Effects
	X/Z ±256 (2⁸)	Lowest coordinates at which anyone has fallen through the world, although incredibly unlikely at this distance. Since the glitch is caused by hitbox corners affected by different levels of floating point precision errors, it could theoretically happen at X/Z ±1. However, this would require nearly 6 real-life days of nonstop gameplay (where one must start over if they exit the game).^[verify]
	X/Z ±512 (2⁹)	The slowest method of movement in Survival without standing against a solid block (sneaking while under the effect of Slowness VI [achievable by using the potion of the Turtle Master II] and using an item on blue ice with cobwebs) becomes impossible.^{[needs in-game testing]}
	X/Z ±1,024 (2¹⁰)	Coordinates of all entities are slices of 8,192. The slowest method is now impossible.^{[needs in-game testing]}
	X/Z ±16,384 (2¹⁴)	Coordinates of all entities are slices of 512. Extremely minor jitteriness can be first experienced at this point, noticeable if the player walks slowly.
	X/Z ±32,768 (2¹⁵)	Coordinates of all entities are slices of 256. It becomes impossible to sneak diagonally on top of soul sand with cobwebs while drawing back a bow.^[1]
	X/Z ±65,536 (2¹⁶)	Coordinates of all entities are slices of 128.

Medium effects (X/Z ±131,072–1,048,575)

Eventually, some common forms of movement begin to glitch. In addition, blocks with detailed models begin to render incorrectly.


Coordinates		Effects
	X/Z ±131,072 (2¹⁷)	Coordinates of all entities are slices of 64. Climbing up ladders, vines, twisting vines and weeping vines while sneaking is slightly slower than normal if climbing by walking against a block.^[2] Sneaking diagonally starts to become bumpy. Lecterns and tripwire hooks start to become distorted.
	X/Z ±262,144 (2¹⁸)	Coordinates of all entities are slices of 32. Climbing up ladders and vines while sneaking is even slower and less smooth.^[2] Sea pickles render with slightly thinner stems than normal. Tripwire string becomes invisible. Sweet berry bushes and cobwebs appear slightly larger. Sunflowers become glitched.^[3]
	X/Z ±524,288 (2¹⁹)	Coordinates of all entities are slices of 16. All entities are on the edges of block pixels. Paintings are placed halfway inside the block, allowing multiple paintings to be placed on the same block. The inner part of item frames render flush along the block. Moving horizontally while on cobwebs becomes impossible. Jitter is noticeable beyond this point. Many mobs are unable to jump on blocks correctly. Sea Turtles can no longer move on land.

Major effects (X/Z ±1,048,576–16,777,215)

This section is missing information about the following features and effects:

Leads
Cave generation
Raycasting, which seems to result in incorrect blocks being targeted.

Please expand the section to include this information. Further details may exist on the talk page.

Blocks are rendered based on their corners, whose coordinates are 32-bit floating point numbers. Generally, these are multiples of ¹⁄₁₆. Thus, most blocks render normally as long the floating points are precise to the nearest sixteenth. This breaks at X/Z ±1,048,576 (2²⁰), and blocks continue to render incorrectly as the coordinates go even farther out.^[4]

In the RTX betas, the lighting is unaffected by floating-point precision errors, although block shapes themselves are incorrect.^[5]

Besides, many "normal" forms of movement become impossible.

The different types of block model deformation have changed a lot over the years, although the update specifics and hardware requirements are unknown. Previously, blocks such as flowers and grass would appear completely 2D beyond 8,388,608 blocks, whereas they appeared as almost normal X shapes in more recent versions, but appearing as 2D again as of 1.16.220. Also, sunflower heads could previously distort to become square, which also no longer happens; the flower appears detached from the plant instead.


Coordinates		Effects
	X/Z ±1,048,576 (2²⁰)	Coordinates of all entities are slices of 8. Walls render wider than normal. Fences (excluding the posts) and closed fence gates render completely flat. Doors and open trapdoors render thinner than normal. Iron bars and glass panes render twice as wide than normal. Climbing up ladders and vines is impossible without holding the jump button, and climbing up them while sneaking is extremely slow. It becomes impossible to sneak outside the X/Z axis. The cube inside slime blocks is slightly wider. The cube inside honey blocks is stretched to a full block, which results in a flickering effect. Cakes appear stretched to full block. Fire renders a bit differently. Sea pickles render in slightly different places without stems. Lanterns render wider than usual and without the top part. The logs in campfires render farther apart, overlapping with each other. In brewing stands, the base renders incorrectly and the central pole is invisible. The bases of anvils render incorrectly. The supports of grindstones render incorrectly. The sides of item frames render wider than the top and bottom. Flower pots appear slightly wider. The inside of beacons render incorrectly. The supports of bells render incorrectly. Horizontal end rods render flat, while vertical End rods render only with their bases. Redstone renders slightly differently. Torches become invisible. Buttons placed anywhere other than the sides of blocks are distorted and such buttons are pushed all the way into the block. Pressure plates cover an entire block. Redstone repeaters and redstone comparators render without torches. Cocoa beans in the second stage render as wide as mature cocoa beans. Cacti render as full blocks, with gaps at the edges. Bamboo renders wider than normal, flat, or invisible. The dragon egg appears to be more blocky. Turtle eggs are distorted. The small bumps on chorus plant stems disappear. The barrier at Y -40 stops generating.
	X/Z ±2,097,152 (2²¹)	Coordinates of all entities are slices of 4. Moving while sneaking becomes impossible. Walking appears jerky. Dropped items fall through the edges of blocks. Dropped items that land on the edges of lava bounce off without burning; this effect continues into the Stripe Lands. Fence posts are invisible. Open fence gates are completely flat. Doors and trapdoors render wider than normal. Iron bars and glass panes render completely flat. The supports of scaffolding are invisible. Cauldrons and composters have completely flat walls and whatever is inside them are stretched to fit the top. The bottom part of hoppers are invisible. Lecterns are wider more than a block. Nether portal blocks are completely flat. Flowers, sweet berry bushes, cobwebs, and tall grass are much smaller than normal. The first stage of cocoa beans is flat. Chorus flowers render as full blocks.
	X/Z ±4,194,304 (2²²)	It becomes extremely difficult to traverse the world on foot from here. Players need to use ender pearls, chorus fruit, elytra with fireworks or a Riptide trident (if raining or underwater), horseback, boats, or any method that would be at least five blocks per second under normal conditions (the minimum speed possible from here is 10 blocks per second), meaning moving in normal walking speed is impossible. One can travel on foot past 4,194,304 by jumping one time and sprinting. One cannot jump normally. The Jump boost effect does not work. Stairs and slabs or blocks less than 0.5 blocks tall are work past this point. Coordinates of all entities are slices of 2. Entities less than 0.5 blocks wide (such as items and silverfish) fall through the edges of blocks, but can still stand on the centers. This is likely because the hitbox corners on both sides round to the same coordinates, resulting in a "null" hitbox; however, it is not confirmed. Status effect particles snap to the center of the player, causing them to bunch around the center of the screen. Eyes of ender placed inside end portal blocks are stretched to cover the entire block. Piston bases are stretched to full block. If retracted, the front "flickers" between the head and base textures. Crops and seagrass render on the edges of blocks.
	X/Z ±8,388,608 (2²³)	Coordinates of all entities are integers, comparable to slices of 536,870,912 in Java Edition, meaning that all entities are on the edges of blocks. As a result, the player, along with other entities less than 1 block wide, always falls through blocks. The only entities that can stand on blocks from this point onward are boats, spiders, horses, iron golems, polar bears, and ravagers. If only one coordinate exceeds this value, blocks still have collision detection from the side. The player can still be considered "under" blocks, meaning that phantoms do not spawn. Thus, it is theoretically possible to travel to and from the Far Lands in survival using horses. To fly in creative the player must sprint or look directly along an axis, unless the player position is controlled by 64-bit doubles instead of 32-bit floats. The Speed effect does not work, due to MCPE-61425. All blocks that normally render as partial blocks are either stretched to become full blocks, or squished to become 2-dimensional. The exception is a few blocks that render normally no matter how far out the player travels, such as chests and bells. If both coordinates exceed this value, blocks become 1-dimensional and are therefore completely invisible. The blade of a stonecutter duplicates, with each blade appearing on the edge. Entering active End Portals becomes impossible. Previously, cross models would render stretched out (changed from rendering 2D as of an unknown update), however as of 1.16.210 they render flat again.

Examples

Fence texture renders flat
Fence gate texture renders flat after X/Z ±2,097,152
Cacti incorrectly render as full blocks, with gaps at the edges
Cauldron & composter have completely flat walls
Fence Post renders invisible in a Pillager Outpost beyond X/Z ±2,097,152
Stonecutters blade duplicates on the edge after X/Z ±8,388,608

Game-breaking effects (X/Z ±16,777,216–2,147,483,647)

Here, the terrain and rendering fundamentally break down to the point where normal gameplay is completely impossible.


Coordinates		Effects
	X/Z ±12,550,824	The Far Lands begin at these coordinates
	X/Z ±16,777,216 (2²⁴)	The floating point precision errors cause only blocks with even coordinates not divisible by 4 to render, and are stretched to 2 blocks wide. This phenomenon is known as the Stripe Lands. In contrast, the Stripe Lands starts at X/Z ±9,007,199,254,740,992 in Java Edition, as the block rendering coordinates use 64-bit doubles instead. Some blocks at other coordinates can render 2-dimensional, but not if they would be rendered on the end of a double-length block. In general, blocks render only if they are "exposed" to air or another see-through block. Coordinates of all entities are multiples of 2, comparable to slices of 268,435,456 in Java Edition. This does not impact the way maps are rendered. 2D blocks are non-solid, even from the sides. However, ghasts, large slimes, and large magma cubes treat both 2D and 3D blocks as solid because they are more than 2 blocks wide. The game does not properly register when the player is in water if the player' coordinates are divisible by 4. As a result, the player falls through water, is unable to enter swimming, and the fog is black or dark blue. However, water still causes the player to exit gliding, and boats still float. The only method of transportation possible is by elytra or by teleportation (an invisible barrier exists here).
	X/Z ±33,554,432 (2²⁵)	Horizontal block rendering stops completely, leaving only vertical block rendering in its place, marking the start of the Slice Lands.^{[unofficial name]} Blocks whose sides are not "exposed", such as the naturally-generated water, are completely invisible. At this point, the slices are 4 blocks apart, but the gap widths double for every power of 2. The phenomenon is known as the Stripe Gap Lands Coordinates of all entities are multiples of 4, comparable to slices of 134,217,728 in Java Edition. It is difficult to place blocks from this point onward. The player must look at an existing block and extend it along an axis. The only way to generate blocks (to place on) without external tools is to use structure blocks. Block rendering essentially stops completely in the Corner Slice Lands;^[6] blocks are rendered as one-dimensional, and are therefore impossible to see. Water becomes completely non-solid. To move, the player must glide with elytra at a downward angle of approximately 45 degrees, or use Riptide. Note that because the player is not considered to be "in water", Riptide can only be activated by rain. Tridents and ender dragons are the only other entities that can move horizontally beyond this point. It is therefore impossible to teleport using ender pearls.
	X/Z ±67,108,864 (2²⁶)	The only form of movement possible is with Riptide II or higher. It is also possible to teleport using chorus fruit. Coordinates of all entities are multiples of 8, comparable to slices of 67,108,864 in Java Edition. The visual gaps are 8 blocks wide, Marking The Start Of The Slice Gap Lands.
	X/Z ±134,217,728 (2²⁷)	Maximum coordinates where generated structures can generate on mobile devices. However, on Windows, structures continue to generate all the way to the 32-bit integer limit. Coordinates of all entities are multiples of 16, comparable to slices of 33,554,332 in Java Edition. The visual gaps are 16 blocks wide. Riptide II can no longer move the player horizontally, and Riptide III only works if the player looks directly along an axis. However, it is still possible to teleport using chorus fruit.
	X/Z ±268,435,456 (2²⁸)	It is impossible for any entity to move horizontally, without modifying the player's flying speed, or the player position is controlled by 64-bit doubles. Teleportation using chorus fruit is impossible. Coordinates of all entities are multiples of 32, comparable to slices of 16,777,216 in Java Edition. The visual gaps are 32 blocks wide.
	X/Z ±536,870,912 (2²⁹)	Coordinates of all entities are multiples of 64, comparable to slices of 8,388,608 in Java Edition. The visual gaps are 64 blocks wide. A large "cone shape" in front of the player disappears from view. This cone is oriented along the X or Z axis, rather than the direction the player is facing. It is always composed of 16x16x16 cubes (essentially sections of chunks).
	X/Z ±1,073,741,824 (2³⁰)	Coordinates of all entities are multiples of 128, comparable to slices of 4,194,304 in Java Edition. The visual gaps are 128 blocks wide. The "cone" in front of the player widens. The world is completely invisible with a render distance of 16 chunks or less (unless the player position is controlled by 64-bit doubles), despite the fact that the gaps are only 8 chunks wide.
	X/Y/Z ±2,147,483,647 (2³¹)	Coordinates of all entities are multiples of 256, comparable to slices of 2,097,152 in Java Edition. The game crashes near this point, as this is above the maximum signed binary integer allowed for 32-bit systems, such as C++. Specifically, the game crashes if the player attempts to load a chunk that is within 64 blocks of this limit, so increasing the render distance can crash the game.

Stripe Lands

The Stripe Lands are an artifact of the game's rendering and block hitbox calculation, rather than a quirk relating directly to terrain generation.^[7]^[8] The Stripe Lands starts at X/Z ±16,777,216, under the same terrain effects as Nothingness and Skygrid. They exist because coordinates are off by up to a full meter, causing the blocks themselves (not just their corners) to appear in the wrong places.

Past X/Z: ±33,554,432 all blocks are rendered as two-dimensional, and the gap between valid blocks doubles to 1 out of four. This gap doubles again at every power of 2 and reaches 128 blocks wide at X/Z: ±1,073,741,824. This is the widest the gaps can be since the game crashes near X/Z: ±2,147,483,648.

The first screenshot posted of the Stripe Lands, by Tommaso Checchi, at X/Z 32,000,000.
A village in the corner stripe Lands.
A jungle temple in the corner stripe Lands.
Fossils in the Far Lands.jpeg

Some fossils that have generated in the Corner Stripe Lands.
Overhead view of the Corner Stripe Lands.
The 25-bit boundary area in the form of 2d lands and stripe lands.
At the integer X / Y: 24-bit position, The nether begins to strip and becomes a dot chunk.
A savanna village at the Stripe Lands at X/Z 16,777,216. Any structure that generates past this limit is rendered as two-dimensional.
The previous screenshot at the opposite angle.
A cold biome in the corner Stripe Lands. 2 Polar Bears are visible. Notice how they don't fall into the void.

Vertical limits

Like the X and Z axes, the game breaks at excessive Y coordinates. Since blocks cannot be placed above Y=255, block rendering glitches do not occur, but other effects do.

Many of these effects would occur at negative coordinates, but there is a barrier at Y -40. Beyond this entities can move only vertically using the "fall through the world" glitch, or teleporting below Y -40. Thus the barrier can be avoided by teleporting past X/Z ±8,388,608. Also, all entities, except players in creative, disappear in the void.

Coordinates		Effect
	Y ±65,536	Particles Turn Black
	Y ±1,048,576	Levitation floating is slightly faster at this point.
	Y ±2,097,152	Floating upward by holding the jump button with elytra and Slow Falling is no longer possible.
	Y ±8,388,608	Status effect particles snap to the head, feet, and center of the player, resulting in a glitched animation assuming the player is in first person. Slow Falling causes the player to be stuck in mid-air. Flying upward in Creative is no longer possible, although the player can still fly downward. There is a noticeable delay between when the player exits flight mode and when the player actually starts falling.
	Y ±16,777,216	The delay described above is even longer. Flying downward in Creative is no longer possible.
	Y ±2,147,483,647	The game crashes near these coordinates.

History

This section needs expansion.

You can help by expanding it.

Pocket Edition Alpha

v0.10.0

{{Extension DPL}}<ul><li>[[Cookie|Cookie]]<br/>{{Item
| title = Cookie
| image = Cookie.png
| heals = {{hunger|2}}
| renewable = Yes
| stackable = Yes (64)
}}
'''Cookies''' are [[food]] items that can be obtained in large quantities, but do not restore hunger or saturation significantly.

== Obtaining ==
=== Trading ===
Journeyman-level farmer [[villager]]s sell 18 cookies for 3 [[emerald]]s as part of their trades.

=== Crafting ===
{{Crafting
|A2= Wheat
|B2= Cocoa Beans
|C2= Wheat
|Output= Cookie,8
|type= Foodstuff
}}

=== Villager gifts ===
{{in|java}}, if the [[player]] has the [[Hero of the Village]] effect, a farmer villager may gift them a cookie.

== Usage ==
=== Food ===
To eat a cookie, press and hold {{control|use}} while it is selected in the hotbar. Eating one restores {{hunger|2}} [[hunger]] and 0.4 hunger 
[[Hunger#Mechanics|saturation]].

=== Parrots ===
Feeding a cookie to a [[parrot]] kills the parrot instantly, and causes it to give off [[Poison]] [[particles]] as it dies due to chocolate being toxic to parrots.
{{IN|Bedrock}}, feeding a cookie to a parrot inflicts the parrot with [[Fatal Poison]] for 1,000 seconds.

=== Composting ===
Placing a cookie into a [[composter]] has an 85% chance of raising the compost level by 1.

Considering the high yield of cookies (8 cookies from 1 cocoa bean and 2 wheats) and the higher chance to successfully compost a cookie (85%), it is more efficient to craft cookies to compost rather than using separate ingredients. For example, 100 wheats and 50 cocoa beans, which in total could yield only 13.92 bone meal on average, could be crafted into 400 cookies to yield 48.57 bone meal on average.

== Sounds ==
{{Sound table/Entity/Food}}

== Advancements ==
{{load advancements|Husbandry;A Balanced Diet}}

== Data values ==
=== ID ===
{{edition|java}}:
{{ID table
|edition=java
|showforms=y
|generatetranslationkeys=y
|displayname=Cookie
|spritetype=item
|nameid=cookie
|form=item
|foot=1}}

{{edition|bedrock}}:
{{ID table
|edition=bedrock
|shownumericids=y
|showforms=y
|notshowbeitemforms=y
|generatetranslationkeys=y
|displayname=Cookie
|spritetype=item
|nameid=cookie
|id=271
|form=item
|foot=1}}

== History ==

{{History|java beta}}
{{History||1.4|[[File:Cookie JE1 BE1.png|32px]] Added cookies. 
|Cookies restore {{hp|1}} and are currently the only stackable [[food]], up to 8 cookies per stack.}}
{{History||1.8|snap=Pre-release|Cookies can now be stacked to 64.
|Cookies now restore {{hunger|1}}.}}
{{History|java}}
{{History||1.3.1|snap=12w18a|Cocoa beans have become farmable, making cookies [[renewable resource|renewable]] and ''much'' cheaper.}}
{{History|||snap=12w19a|Cookies now restore {{hunger|2}} instead of {{hunger|1}}.}}
{{History|||snap=12w21a|Farmer [[villager]]s now [[trading|sell]] 8–10 cookies for 1 [[emerald]].}}
{{History||1.8|snap=14w02a|Farmer villagers now sell 6 cookies for 1 emerald.}}
{{History||1.11|snap=16w33a|Farmer villagers now sell 6–10 cookies for 1 emerald.}}
{{History||1.12|snap=17w13a|Cookies can now be used to tame [[parrot]]s.}}
{{History|||snap=pre3|Cookies are no longer used to tame [[parrot]]s. Instead, a cookie now instantly kills a parrot.}}
{{History||1.13|snap=17w47a|Prior to [[1.13/Flattening|''The Flattening'']], this [[item]]'s numeral ID was 357.}}
{{History||1.14|snap=18w43a|[[File:Cookie JE2 BE2.png|32px]] The texture of cookies has been changed.}}
{{History|||snap=19w03a|Placing a cookie into the new [[composter]] has a 80% chance of raising the compost level by 1.}}
{{History|||snap=19w05a|Cookies now have an 85% chance of increasing the compost level in a composter by 1.}}
{{History|||snap=19w13a|Farmer villagers now give cookies to players under the [[Hero of the Village]] effect.}}

{{History|pocket alpha}}
{{History||v0.9.0|snap=build 1|[[File:Cookie JE1 BE1.png|32px]] Added cookies.}}
{{History||v0.12.1|snap=build 1|Cookies now restore [[hunger]] instead of [[health]].}}
{{History|pocket}}
{{History||1.0.4|snap=alpha 1.0.4.0|Farmer [[villager]]s now [[trading|sell]] 6-10 cookies for 1 [[emerald]].}}
{{History|bedrock}}
{{History||1.2.0|snap=beta 1.2.0.2|Cookies can now be used to inflict a fatal [[Poison]] [[status effect]] to [[parrot]]s.}}
{{History||1.10.0|snap=beta 1.10.0.3|[[File:Cookie JE2 BE2.png|32px]] The texture of cookies has been changed.}}
{{History||1.11.0|snap=beta 1.11.0.1|Cookies can now be used to fill up [[composter]]s.}}
{{History|||snap=beta 1.11.0.4|Farmer [[villager]]s now [[trading|sell]] 18 cookies for 3 [[emerald]]s as part of their third tier [[trading|trades]].}}

{{History|console}}
{{History||xbox=TU1|xbone=CU1|ps=1.0|wiiu=Patch 1|[[File:Cookie JE1 BE1.png|32px]] Added cookies.}}
{{History||xbox=none|xbone=none|ps=1.90|wiiu=none|switch=none|[[File:Cookie JE2 BE2.png|32px]] The texture of cookies has been changed.}}

{{History|new 3ds}}
{{History||0.1.0|[[File:Cookie JE1 BE1.png|32px]] Added cookies.}}
{{History|foot}}

== Issues ==

{{issue list}}

== Gallery ==

<gallery>
File:12w21a CookiePurchase.png|Cookies being obtained by [[trading]] with a farmer [[villager]].
File:Eating Steve.png|[[Steve]] eating a cookie.
File:Eating Alex.png|Alex eating a cookie.
</gallery>

== References ==
{{reflist}}

== External Links ==
*[https://www.minecraft.net/en-us/article/taking-inventory--cookie Taking Inventory: Cookie] – Minecraft.net on August 22, 2019

{{Items}}

[[Category:Food]]
[[Category:Renewable resources]]

[[cs:Sušenka]]
[[de:Keks]]
[[es:Galleta]]
[[fr:Cookie]]
[[hu:Csokis süti]]
[[ja:クッキー]]
[[ko:쿠키]]
[[nl:Koekje]]
[[pl:Ciastko]]
[[pt:Biscoito]]
[[ru:Печенье]]
[[uk:Печиво]] 
[[zh:曲奇]]</li><li>[[Item (entity)|Item (entity)]]<br/>{{Entity
| title = Item Entity
| image = Item.gif
| health = {{hp|5}}<ref>Items cannot be damaged by attacking them.</ref>
| size = Height: 0.25 Blocks<br>Width: 0.25 Blocks
}}

'''Items''' are "dropped" [[block]]s or [[item]]s (non-block resources) that appear in the world, rather than being in the [[inventory]] of a [[player]] or [[block entity]]; they are a type of [[entity]].

== Appearance ==

[[File:Item entities.png|150px|thumb|3D dropped items, both blocks and strict items.]]

Items have two possible appearances, generally corresponding to whether the item appears as a 3D or 2D shape in a player's inventory screens. 3D items appear as their 3D shape, miniaturized to about {{frac|1|4}} scale, while 2D items appear as {{frac|1|2}} scale with all the pixels extruded into a cube. Both types slowly rotate and bob up and down; this is merely a visual effect, the item itself does not actually rotate or bob up and down.

Item entities that represent a stack of more than one item appear as several items stuck together. Stacks of 1 appear as one item, 2-16 as two items, 17–32 as three, 33-48 as four, and 49+ as five.

The rotation rate of the item is approximately 2.87675 degrees per tick, or 57.595 degrees per second.

== Behavior ==

Item entities come from many sources. Some common ones are:
* The death of a [[mob]] or [[player]].
* A [[block]] that is mined by a player, destroyed by an [[explosion]], or washed away by [[water]].
* An inventory item tossed by pressing the drop item key (default {{key|Q}} on PC, {{xbtn|dpad-down}} on Xbox, {{nsbtn|down}}/{{nsbtn|dpad-down}} on Nintendo Switch, {{psbtn|dpad-down}} on PlayStation) or dragging a stack outside of an inventory window.
** In the mobile versions of {{el|be}}, items in the hotbar can be dropped by pressing on the item's slot. The entire stack is dropped.
* A container (other than an {{BlockLink|ender chest}} or a {{BlockLink|shulker box}}) that is destroyed while holding items inside.

The player may be thought of as having an "item pickup" box that surrounds their hitbox. This pickup box extends 1 additional block to the horizontal sides, and 0.5 additional blocks up and down. Any item whose hitbox intersects with the pickup box can be picked up. The pickup box is inclusive on the horizontal sides (distance less than or equal to 1 will count), and exclusive on the vertical sides (distance less than 0.5 will count, but not equal). When the player's hitbox size changes, such as when crouching{{only|java}} or sleeping, the pickup box size changes with it.

Once an item entity's hitbox overlaps with the player's pickup box, it can transfer its items. As many items as can fit in the player inventory, excluding the armor slots and the [[dual wield|off-hand slot]], are transferred. If any item is transferred, [[Item (entity)#Sounds|a "plopping" sound]] is played. If all items are transferred, the items appear to move into the center of the player. The item entity never physically moves, however, which means it can appear to go through lava and blocks in its path. This can happen through blocks that are thinner than a full block, but also through the shared edge of two full blocks. Unlike [[experience orb]]s, multiple item entities can be picked up simultaneously. Dropped items have a delay of 10 [[tick]]s (half a second) between appearing and being able to be picked up, or 40 ticks (2 seconds) if thrown by a player, [[dolphin]], or [[fox]].

When two stackable items of the same type come within 3/4 of a block of each other, they merge into a single stack if the resulting stack size does not exceed that item's maximum stack size.

Items do not collide with other entities(except boats) and are only moved or stopped by blocks.

Like other entities, items can be pushed by flowing water and [[bubble column]]s, pushed by a [[piston]], launched by a moving [[slime block]], stuck to a [[honey block]], or caught in a [[cobweb]]. Items move at faster speeds if [[ice]] is placed under the flowing water. When in still water, items float slowly up to the surface.

Items can be reared by [[fishing rod]]s, costing 3 [[durability]].{{only|je}}

If an item is within a [[solid block]], then it flies out one of the unobstructed sides, or out of the top of the block if surrounded by solid blocks on all sides. It does this even if the space below is unoccupied; therefore, it is possible to recover an item dropped by breaking a hole in a floor by quickly placing another block there.

Items visually disappear when the player is about 16 blocks away from them, and reappear when they get closer. This distance can be adjusted by the "Entity Distance" slider in [[Options#Video Settings|video settings]].

Unlike most entities, items cannot be spectated in [[Spectator]] mode without use of the {{cmd|spectate}} command.

=== Damage ===
Items cannot be attacked by players or mobs; attempting to do so simply hits through them. However, they take damage and disappear from environmental or block-based damage such as [[explosion]]s, [[fire]], [[lava]], and contact with [[cactus|cacti]]. Items have essentially no health, so they are destroyed by the slightest damage, though if set on fire they may remain for a few seconds before disappearing. [[Nether star]]s are immune to explosions, and [[netherite]]-based items and tools are immune to fire and float on top of lava. Also, some blocks that normally damage mobs, such as [[magma block]]s, [[campfire]]s, [[Sweet Berries|sweet berry bushes]], [[flower|wither rose]]s and [[powder snow]], do not damage items.

=== Despawning ===

Items despawn after 6000 game [[tick]]s (5 minutes) of being in a loaded, entity-ticking [[chunk]]; this is affected by the player's [[simulation distance]]. If two item stacks merge, the timer is set to the item that has more time remaining. The 5-minute timer is paused when the chunk is unloaded or no longer processing entities. Nether stars do not despawn{{only|bedrock}}.

Items that fall into the [[void]] immediately despawn when they fall below Y=-128 in the [[Overworld]], or Y=-64 in [[the Nether]] and [[the End]].

== Sounds ==
{{Edition|Java}}:<br>
Item Entities use the Ambient/Environment sound category for entity-dependent sound events.
{{Sound table
|nocat=1
|sound=Pop.ogg
|subtitle=Item plops
|source=player<!--Even when not picked up by player-->
|description=When an item is picked up
|id=entity.item.pickup
|translationkey=subtitles.entity.item.pickup
|volume=0.2
|pitch=1.6-3.4 <ref group=sound>0.6-3.4 for using {{cmd|give}} and items from advancement rewards</ref>
|distance=16}}
{{Sound table
|sound=fizz.ogg
|nocat=1
|subtitle=Burning
|source=ambient
|description=When an item is destroyed by [[lava]], but not [[fire]]<ref>{{bug|MC-36538}}</ref>
|id=entity.generic.burn
|translationkey=subtitles.entity.generic.burn
|volume=0.4
|pitch=2.0-2.4
|distance=16
|foot=1}}

{{Edition|Bedrock}}:
{{Sound table
|type=bedrock
|rowspan=2
|sound=Pop.ogg
|source=player
|description=When an item is picked up
|id=random.pop
|volume=0.25
|pitch=0.6-2.2}}
{{Sound table
|source=player
|description=When an item is dropped
|id=random.pop
|volume=0.3
|pitch=0.55-0.75}}
{{Sound table
|sound=fizz.ogg
|source=block
|description=When an item is destroyed by lava, but not fire
|id=random.fizz
|volume=0.5
|pitch=1.8-2.4
|foot=1}}

== Data values ==

=== ID ===

{{editions|java}}:
{{ID table
|generatetranslationkeys=java
|displayname=Item
|spritename=items
|spritetype=env
|translationtype=entity
|nameid=item
|foot=1}}

{{editions|bedrock}}:
{{ID table
|shownumericids=y
|generatetranslationkeys=bedrock
|displayname=Item
|spritename=items
|spritetype=env
|translationtype=entity
|nameid=item
|id=64
|foot=1}}

=== Entity data ===
{{see also|Chunk format}}
Dropped items have entity data associated with them that contain various properties of the entity.

{{el|java}}:
{{main|Entity format}}
{{/ED}}

{{el|bedrock}}:
: See [[Bedrock Edition level format/Entity format]].

== History ==
{{History|java classic}}
{{History||0.24 Resource Test|In the first public mention of item entities, {{ytl|OP3jzMWJmu8|this early video of Minecraft (Classic 0.24) by Notch}}, they were referred to as "resources".<ref name="resources">{{ytl|YIm_AKUbqh8}} Early video of Minecraft (Classic 0.24) by Notch referring to item entities as "resources"</ref>}}
{{History||August 4, 2009|link=https://notch.tumblr.com/post/155882307/a-video-showing-what-i-did-today-are-vids-like|Items were showcased by [[Notch]] in a blog post.}}
{{History||0.24_SURVIVAL_TEST|Added items to the game.
|Items currently take the form of destroyed [[block]]s.
|Items currently pulse white (similar to the selection cursor).<ref name="resources"/>
|Instead of appearing as shrunken down blocks, items use pixels the same size as block pixels.}}
{{History|java indev}}
{{History||0.31|snap=20091231-2|Dropped items don't spin and don't glow white anymore.
|Dropped items now appear as shrunken down blocks.
|Items no longer prevent the placement of blocks but instead are moved to the nearest chunk. {{info needed}}
|Non-block items added (as sprites); they now rotate to face the [[player]].}}
{{History||?|Dropped items now spin again.}}
{{History|java beta}}
{{History||1.8|snap=Pre-release|[[File:Oversized items.png|100px|right]][[File:In awe at the size of these fluids.png|100px|right]] A bug causing many item forms of blocks to be displayed at the {{frac|1|2}} scale rather than {{frac|1|4}} was fixed. The following items were affected by this at least at one point:
* [[Cactus]]
* [[Oak Trapdoor]]
* [[Oak Fence]]
* [[Oak Pressure Plate]]
* [[Stone Pressure Plate]]
* [[Stone Button]]
* [[Oak Stairs]]
* [[Cobblestone Stairs]]
* [[Snow]] (unobtainable at the time)
* [[Farmland]] (unobtainable)
* [[Cake]] ([[Technical blocks/Cake|unobtainable version]])
* [[Nether Portal (block)|Nether Portal]] ([[Technical blocks/Nether Portal|unobtainable]])
* [[Water]] ([[Technical blocks/Water|unobtainable]], before becoming 2D in [[Java Edition Infdev 20100615]])
* [[Lava]] ([[Technical blocks/Lava|unobtainable]], before becoming 2D in [[Java Edition Infdev 20100615]])
}}
{{History|java}}
{{History||1.3.1|snap=12w15a|Items that are moved into the same location now combine into stacks instead of remaining independent entities.}}
{{History||1.4.2|snap=12w34a|Items, like other entities, can now travel through [[portal]]s.}}
{{History|||snap=12w34b|Some [[zombie]]s, [[skeleton]]s and [[Zombified Piglin|zombie pigmen]] can now pick up items.}}
{{History||1.4.4|snap=1.4.3|Items are now pushed out of transparent solid blocks as well as opaque ones.<ref>{{bug|MC-15}}</ref> Items can push into solid blocks while trying to escape a solid block instead of stopping (this has been used to create vertical transport of items). New feature: items are pushed out of the inside corner of stair blocks, causing "bouncing" effects.}}
{{History||December 11, 2012|link=none|[[Dinnerbone]] tweeted a picture of [[diamond]]s being rendered in 3D as dropped items.<ref>{{tweet|dinner|278457679805030401|Diamonds are a miners best friend. It's only fair they get treated to some luxury rendering. http://dinnerbone.com/media/uploads/2012-12/screenshots/Minecraft_2012-12-11_12-13-11.png … #AndMaybeEverythingElseToo|December 11, 2012}}</ref> He also revealed that other items would rendered in this way, but only in [[fancy graphics]].<ref>{{tweet|dinner|278463997982949378|@PaymenowTV It's Fancy Rendering option, but really won't make much of a difference on even a slow pc.|December 11, 2012}}</ref>}}
{{History||December 12, 2012|link=none|TeamMojang ([[wikipedia:Youtube|YouTube]]) posted a video showing off the new 3D items.<ref>{{ytl|tMOZLAxPWFE}}</ref>}}
{{History||1.4.6|snap=12w49a|[[Nether star]]s are the first items to not be deleted by [[explosion]]s.}}
{{History|||snap=12w50a|When dropped, items now render in the [[fancy graphics]] setting as 3D spinning animations (non-block items no longer display as [[Wikipedia:Sprite (computer graphics)|sprites]]).
|Dropped items now merge with nearby items and be stacked.
|Enchanted items now show the enchanted glow when dropped.}}
{{History||1.5|snap=13w01a|Added [[hopper]]s, which can collect items.}}
{{History|||snap=13w03a|Added [[Minecart with Hopper|hopper minecart]]s, which can collect items.}}
{{History||1.8|snap=14w04a|Dropped items don't spin, and they are visible only from the south on fast graphics.}}
{{History|||snap=14w04b|Dropped items are now completely invisible on fast graphics.}}
{{History|||snap=14w05a|Dropped items on fast graphics now face the player on all three axes, and they spin again on fancy graphics.}}
{{History|||snap=14w25a|Dropped items now render in 3D on fast graphics, instead of just on fancy graphics, likely due to item models being fully implemented and replacing the need for 2D items. However, they do not spin.}}
{{History||1.8.1|snap=pre4|Dropped items now spin on fast graphics.}}
{{History||1.10|snap=16w21a|Items can now be reared by [[fishing rod]]s.}}
{{History||1.11|snap=16w32a|The entity ID of items has been changed from <code>Item</code> to <code>item</code>.}}
{{History||1.13|snap=18w07a|Items in water now float up.}}
{{History||1.16|snap=20w06a|Netherite items are the first items to not burn in [[lava]], and float in lava.}}
{{History||1.20|snap=Pre-release 5|Item are no longer destroyed by falling [[anvil]]s.<ref>{{bug|MC-120158
||Anvils and other falling_blocks with HurtEntities set to true kill items and xp orbs|Fixed}}</ref>}}

{{History|pocket alpha}}
{{History||v0.2.0|Added items to the game.}}
{{History||?|Items now have improved graphics.{{more info|clarify}}}}
{{History|Bedrock}}
{{History||1.4.0|snap=beta 1.2.14.2|Items in [[water]] now float up.}}
{{History||1.16.0|snap=beta 1.15.0.51|When dropped, items now render as 3D spinning animations (non-block items no longer display as [[Wikipedia:Sprite (computer graphics)|sprites]]).}}
{{History|||snap=beta 1.16.0.51|Added [[netherite]] items, which float and do not burn in [[lava]].}}

{{History|console}}
{{History||xbox=TU1|xbone=CU1|ps=1.0|wiiu=Patch 1|switch=1.0.1|Added items to the game.}}
{{History||xbox=TU12|When dropped, items now render as 3D spinning animations (non-block items no longer display as [[Wikipedia:Sprite (computer graphics)|sprites]]).}}
{{History||xbox=TU69|xbone=none|ps=1.76|wiiu=Patch 38|switch=none|Items in [[water]] now float up.}}
{{History|foot}}

== Trivia ==
* {{bug|MC-4}}, the oldest standing bug in the Minecraft [[bug tracker]], involves item entity positioning being incorrectly handled.

==Gallery==
<gallery>
3D Diamonds.png|First image of 3D dropped items.
</gallery>

== See also ==
* [[Drops]] — items dropped by [[mobs]] when killed.
* [[Chunk format#Items|Chunk format]] for more information about the attributes of items.

== References ==

{{Reflist}}

{{entities}}
{{items}}

[[Category:Items| ]]

[[de:Drop]]
[[es:Objeto (entidad)]]
[[fr:Objet (entité)]]
[[ja:アイテム (エンティティ)]]
[[ko:아이템 (개체)]]
[[nl:Voorwerp (entiteit)]]
[[pt:Drops]]
[[ru:Предмет (сущность)]]
[[zh:物品（实体）]]</li></ul>

build 1

Chunk jittering at extreme coordinates no longer occur.

Gallery

A cave generated beyond X/Z: ±8,388,608, with serrated-looking edge walls in front and the perfect holes in the back.
Fences after X/Z=8388608 (left) and before (right).
Cacti generated near the Far Lands, rendered as full blocks with gaps.
The first screenshot posted of the Stripe Lands, by Tommaso Checchi, at X/Z ± 32,000,000.
The start of the Stripe Lands at X/Z ±16,777,216.
A frozen ocean biome in the Stripe Lands.
The Stripe Lands in a flat world.
The start of the Corner Stripe Lands.
Overhead view of the Corner "Stripe Lands".
FarlandsMCPE.jpg

The world beyond X/Z ±134,217,728
The world beyond X/Z 536,870,912. A large area in front of the player is completely invisible.
The world beyond X/Z ±1,073,741,824
The piston head Z-fighting with the piston brain.
A Stripe Gap Lands are start generate at X/Z: ±33,554,432.
A monument in the Stripe Lands.
An underwater ruin in the Stripe Lands
An eroded badlands in the Stripe Lands, surrounded by Skygrid.
Redstone posted beyond 4,194,304 blocks. Redstone lines are completely invisible and the rest of redstone renders incorrectly (one of the crosses is connected to four lines).
Redstone placed beyond 8,388,608 blocks. Unlike the similar historical redstone model issue on Java Edition, redstone lines are stretched to a full block in both directions.