Minecraft Wiki
Advertisement
Clock JE3
This article needs to be updated. 
Please update this page to reflect recent updates or newly available information.
Reason: Slowest movement method may be outdated
Brush
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
Information icon
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 n8388608 blocks, or n524288 block pixels (e.g. at between X/Z ±16,777,216 and X/Z ±33,554,432, 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).

Note: Effects marked with an asterisk (*) are well-known effects.

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, as opposed to Java Edition, which uses 64-bit floating points. 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 ±1 (20)
  • Coordinates of all entities are slices of 8,388,608.
  • Lowest coordinates at which someone can theoretically fall through the world within around 5 to 7 real-life days of nonstop gameplay (where one must start over if they exit the game). However, It is almost impossible to do at these coordinates.
X/Z ±2 (21)
  • Coordinates of all entities are slices of 4,194,304.
X/Z ±4 (22)
  • Coordinates of all entities are slices of 2,097,152.
X/Z ±8 (23)
  • Coordinates of all entities are slices of 1,048,576.
X/Z ±16 (24)
  • Coordinates of all entities are slices of 524,288.
X/Z ±32 (25)
  • Coordinates of all entities are slices of 262,144.
X/Z ±64 (26)
  • Coordinates of all entities are slices of 131,072.
X/Z ±128 (27)
  • Coordinates of all entities are slices of 65,536.
X/Z ±256 (28)
  • Coordinates of all entities are slices of 32,768.
  • 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 (see above).
  • The slowest method is impossible.
X/Z ±512 (29)
X/Z ±1,024 (210)
  • Coordinates of all entities are slices of 8,192.
X/Z ±2,048 (211)
  • Coordinates of all entities are slices of 4,096.
X/Z ±4,096 (212)
  • Coordinates of all entities are slices of 2,048.
X/Z ±8,192 (213)
  • Coordinates of all entities are slices of 1,024.
X/Z ±16,384 (214)
  • Coordinates of all entities are slices of 512.
  • Minor jitter can be first experienced at this point, noticeable if the player walks slowly.
X/Z ±32,768 (215)
  • 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 (216)
  • 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 (217)*
  • 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.
  • When the player stops walking, they are bumped.
X/Z ±262,144 (218)*
  • Coordinates of all entities are slices of 32.
  • Climbing up ladders and vines while sneaking is even slower and less smooth.[2]
  • Moving in powder snow while sneaking becomes impossible if the player waits for too long.
  • Sea pickles render with slightly thinner stems than normal.
  • Tripwire string becomes invisible.
  • Sweet berry bushes and cobwebs appear slightly larger.
  • Sunflowers become glitched and are Z-fighting on the X-axis. They don’t become glitched on the Z-axis.[3]
  • Sneaking in soul sand with a spyglass stops movement.
  • Sneaking in all directions is more bumpy.
X/Z ±524,288 (219)*
  • 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.
  • Moving in powder snow becomes entirely impossible while sneaking.
  • Jitter is noticeable beyond this point.
  • Many mobs are unable to jump on blocks correctly, probability because due to entites being on the edge of block pixels and the mobs are not fast enough to get through the block.
  • Sea turtles and axolotls can no longer move on land.
  • The top part of candles renders incorrectly.
  • Running on soul sand becomes noticeably bumpy.
  • It's impossible to sneak outside the X/Z axis on soul sand without soul speed boots.

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 116. Thus, most blocks render normally as long the floating points are precise to the nearest sixteenth. This breaks at X/Z ±1,048,576 (220), 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.

In addition here, the terrain starts to break down following the table.

Coordinates Effects
X/Z ±1,048,576 (220)*
  • 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.
  • Moving in powder snow becomes impossible if you wait too long, though rapidly inputting sprint allows you to escape.
  • 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.
  • The shafts of lightning rods render as flat.
  • 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‌[until BE 1.18.0] or Y=-104‌[upcoming: BE 1.18.0] stops generating.
  • Walking is as fast as running speed.
  • leads start appearing as a zigzag.
X/Z ±2,097,152 (221)*
  • Coordinates of all entities are slices of 4.
  • Moving while sneaking becomes impossible.
  • Walking appears bumpy.
  • 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.
  • Lightning rods render entirely 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.
  • Flowers begin to distort.
  • 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.
  • Hanging roots render thinner than normal.
  • All four stages of amethyst buds render thinner than normal.
  • The first stage of cocoa beans is flat.
  • Chorus flowers render as full blocks.
  • The top part of the Dragon egg is flat or invisible.
X/Z ±4,194,304 (222)*
  • Coordinates of all entities are slices of 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.
  • 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.[verify]
  • Status effect particles snap to the center of the player, causing them to bunch around the center of the screen.
  • All stages of amethyst buds are stretched to a full block.
  • The stems of both big dripleaves and small dripleaves become two-dimensional.
  • 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, hanging roots, and seagrass render on the edges of blocks.
  • The second stage of cocoa beans is flat just like the first stage.
  • The third stage of cocoa beans appears stretched as a full block.
  • When the player is in Powder snow the screen sometimes flickers fighting trying to see if the player is inside or outside of Powder snow even with leather armor on.
  • The second highest top part of the Dragon egg is invisible including the highest part.
X/Z ±8,388,608 (223)*
  • Coordinates of all entities are integers, 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 Stripe 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. In addition, flying at this coordinate is bumpy, even when the player is sprinting and looking directly along an axis.
  • 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, partial blocks that normally render as 2D this far out become 1-dimensional and are therefore completely invisible.
  • The terracotta strata in badlands biomes become noticeably distorted at this point.
  • The blade of a stonecutter duplicates, with each blade appearing on the edge.
  • Spore blossoms are stretched so that the player sees only half of the flower.
  • 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.
  • The shadow of signs are at the edge of the block the sign is on.
  • The first and second stage of cocoa beans are either pushed into the block or they render as full blocks.
  • The notes that come from jukeboxes and noteblocks are on the edge of the block.
  • Minecarts can no longer run on Powered rails.
  • caves in caves and cliffs sometimes generate with perfect curves or horizontal halls.
  • Chains are streched to a full block.

Examples

Game-breaking effects (X/Z ≥±16,777,216)

This section is missing information about notable effects beyond the 32-bit limit. 
Please expand the section to include this information. Further details may exist on the talk page.

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

Coordinates Effects
X/Z ±16,777,216 (224)*
  • 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.
    • This does not impact the way maps are rendered.
    • If the player manages to set their coordinate to an odd number or move into any area not rendered, they get stuck in a glitched position, unable to move the camera view properly, or move in any direction.
  • 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 sprint flying, elytra or by teleportation (an invisible barrier exists here).
  • The terracotta strata in badlands biomes are distorted further and start to form blocky shapes. Because the majority of blocks do not render in the stripe lands, this is noticeable only when viewed on a map.
X/Z ±33,554,432 (225)*
  • 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.
    • 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 be activated only by rain. Tridents Arrows shot from bows or crossbows 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 (226)*
  • Using Elytra becomes impossible.
  • Tridents can no longer move horizontally.
  • Coordinates of all entities are multiples of 8.
  • The visual gaps are 8 blocks wide, thus marking the beginning of the Slice Gap Lands.
X/Z ±134,217,728 (227)*
  • 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, equivalent to one chunk section.
  • The visual gaps are 16 blocks wide.
  • Riptide I works only if the player looks directly along an axis and does it many times, with Riptide II you dont have to use it as much times.
  • Arrows can't move horizontally.
  • Teleportation using chorus fruit is impossible.
X/Z ±268,435,456 (228)
  • Riptide III works only if the player looks directly along an axis and does it many times.
  • Coordinates of all entities are multiples of 32, equivalent to two chunks section.
  • The visual gaps are 32 blocks wide.
X/Z ±536,870,912 (229)
  • Coordinates of all entities are multiples of 64, equivalent to four chunks section.
  • 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 16×16×16 cubes (essentially sections of chunks).
  • Since beta 1.17.30.24, some devices (low and mid-end classes) can no longer survive in this position and frequently crash at this point. If players can successfully go to this coordinate or over, they can survive for few seconds before the game crashes. Therefore, increasing the render distance can crash the game and only high-end devices can survive at this position.
  • Riptide III and Riptide IV does not work.
X/Z ±1,073,741,824 (230)
  • Coordinates of all entities are multiples of 128, equivalent to eight chunks section.
  • 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 15 chunks or less (unless the player position is controlled by 64-bit doubles), despite the fact that the gaps are only 8 chunks wide.
  • The phenomenon is called the Invisible Stripe Lands.
X/Y/Z ±2,147,483,647 (231 − 1)*
  • 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.
X/Z ±2,147,483,648 (231)
  • Coordinates of all entities are multiples of 256, equivalent to 16 chunks section.
  • The visual gaps are 256 blocks wide.
X/Z ±4,294,967,296 (232)
  • Coordinates of all entities are multiples of 512, equivalent to 32 chunks section.
  • The visual gaps are 512 blocks wide.
X/Z ±8,589,934,592 (233)
  • Coordinates of all entities are multiples of 1,024, equivalent to 64 chunks section.
  • The visual gaps are 1,024 blocks wide.
X/Z ±17,179,869,184 (234)
  • Coordinates of all entities are multiples of 2,048, equivalent to 128 chunks section.
  • The visual gaps are 2,048 blocks wide.
X/Z ±34,359,738,368 (235)
  • Coordinates of all entities are multiples of 4,096, equivalent to 256 chunks section.
  • The visual gaps are 4,096 blocks wide.
X/Z ±68,719,476,736 (236)
  • Coordinates of all entities are multiples of 8,192, equivalent to 512 chunks section.
  • The visual gaps are 8,192 blocks wide.
X/Z ±137,438,953,472 (237)
  • Coordinates of all entities are multiples of 16,384, equivalent to 1,024 chunks section.
  • The visual gaps are 16,384 blocks wide.
X/Z ±274,877,906,944 (238)
  • Coordinates of all entities are multiples of 32,768 equivalent to 2,048 chunks section.
  • The visual gaps are 32,768 blocks wide.
X/Z ±549,755,813,888 (239)
  • Coordinates of all entities are multiples of 65,536, equivalent to 4,096 chunks section.
  • The visual gaps are 65,536 blocks wide.
X/Z ±1,099,511,627,776 (240)
  • Coordinates of all entities are multiples of 131,072, equivalent to 8,192 chunks section.
  • The visual gaps are 131,072 blocks wide.
X/Y/Z ±9,223,372,036,854,775,807 (263 – 1)
  • The game crashes near this point while using 64-bit systems, as this is above the maximum signed binary integer allowed for 64-bit systems, such as C++. Also, the game crashes if the player attempts to load a chunk beyond this coordinate, so increasing the render distance can crash the game.[verify]

[more information needed]

X/Z ±9,223,372,036,854,775,808 (263)
  • Coordinates of all entities are multiples of 1,099,511,627,776 (240).
  • The visual gaps are 1,099,511,627,776 blocks wide.
X/Y/Z ±~3.40282366921e+38 (2128)
  • The maximum 32-bit floating-point integer in Bedrock Edition. Beyond this, it caused the player's coordinates to roll over to read "Infinity" within 32-bit float. It is impossible to go further since this is the physical limit at which the code can render in Bedrock Edition.[verify]

[more information needed]

Stripe Lands

Stripe Lands Swamp

The "Stripe Lands" at X/Z 16,777,216.

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] The Stripe Lands start 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.

Examples

Vertical limits

Like the X and Z axes, the game breaks at excessive Y coordinates. Since blocks cannot be placed above Y=256, 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
Y ±262,144
Y ±524,288
  • Floating with levitation I goes back to normal speed.
  • It's possible to notice jumping being sightly less smooth if the player summons a shulker this high and jumps on the shulker.
Y ±1,048,576
  • Levitation II floating is slightly faster at this point.
  • It's impossible to float with levitation I.
Y ±2,097,152
  • Floating upward by holding the jump button with elytra and Slow Falling is no longer possible.
  • There is a delay between when the player exits flight mode while having slow falling and when the player actually starts falling.
Y ±4,194,304
  • Flying upward in Creative is faster than normal.
  • If the player summons a shulker this high and falls on it, after the player lands on the shulker the players hand moves up and down rapidly (only if view bobbing is on). if the player switches to 3rd person during the small jumps, the player appears as if the player was not jumping.
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 delay between when the player exits flight mode and when the player actually starts falling.
  • When the player fly's downward in Creative it's way faster than normal.
  • The shulker is considered as a block wide entity so if the player gets on the shulker, the player appears floating above the shulker even in survival mode.
Y ±16,777,216
  • The delay described above is even longer.
  • Flying downward in Creative is no longer possible.
Y ±33,554,432
  • The delay to fall is way longer.
  • It's impossible to fly up with elytra with fireworks.
Y ±67,108,864
  • The player becomes stuck in mid-air when trying to fall.
  • in 3rd person the player can only look horizontal or vertical.
Y ±2,147,483,647
  • The game crashes near these coordinates on 32-bit devices (see above).
Y ±~3.402824e+38 (2128)
  • The maximum 32-bit floating-point integer in Bedrock Edition. Beyond this, it caused the player's coordinates to roll over to read "Infinity" within 32-bit float. It is impossible to go further since this is the physical limit at which the code can render in Bedrock Edition.[verify]

History

Jigsaw Block (top texture) JE2 BE2
This section needs expansion. 
You can help by expanding it.
Pocket Edition Alpha
v0.10.0
{{Extension DPL}}<ul><li>[[Disc Fragment|Disc Fragment]]<br/>{{Item
| image = Disc Fragment.png
| renewable = No
| stackable = Yes (64)
}}

A '''disc fragment''' is a [[music disc]] fragment obtained from [[ancient city]] loot chests. Nine fragments can be combined in a [[Crafting Table|crafting table]] to make a music disc named "5".

== Obtaining ==
=== Chest loot ===
{{LootChestItem|disc-fragment-5}}

== Usage ==
=== Crafting ingredient ===
{{crafting usage|Disc Fragment 5}}
== Data values ==
=== ID ===
{{ID table
|edition=java<!--
|showitemtags=y-->
|showforms=y
|firstcolumnname=Track
|generatetranslationkeys=y
|displayname=Samuel Åberg - 5
|spritename=disc-fragment-5
|spritetype=item
|nameid=disc_fragment_5<!--
|itemtags=-->
|form=item
|foot=y}}

== History ==
{{History|java}}
{{History||1.19|snap=22w16a|[[File:Disc Fragment.png|32px]] Added disc fragments.}}
{{History|bedrock}}
{{History||1.19.0|snap=beta 1.19.0.28|[[File:Disc Fragment.png|32px]] Added disc fragments.}}
{{History|foot}}

== Issues ==
{{Issue list}}

==Gallery==
<gallery>
9 to 5.jpg|9 fragments of the 5 music disc.
</gallery>

==See also==
* {{EnvLink|Music}}
* {{ItemLink|Music Disc}}

{{Items}}

[[de:Plattenbruchstück]]
[[es:Fragmento de disco]]
[[fr:Fragment de disque]]
[[ja:レコードの破片]]
[[pl:Fragment płyty]]
[[pt:Fragmento de disco]]
[[ru:Фрагмент пластинки 5]]
[[uk:Фрагмент платівки]]
[[zh:唱片残片]]
[[Category:Non-renewable resources]]</li><li>[[Compass|Compass]]<br/>{{About|the item used to point to the world spawn or to a lodestone|the item used to point to the location of the player's last death|Recovery Compass}}
{{Item
| image = Compass.gif
| image2 = Lodestone Compass.gif
| renewable = Yes
| stackable = '''Compass:''' Yes (64)<br>'''Lodestone Compass:''' No
}}
A '''compass''' is an item used to point to the world spawn or to a [[lodestone]].

== Obtaining ==

=== Crafting ===

{{Crafting
                |B1= Iron Ingot
|A2= Iron Ingot |B2= Redstone Dust   |C2= Iron Ingot
                |B3= Iron Ingot
|Output= Compass
|type= Tool
}}

=== Chest loot ===

{{LootChestItem|compass}}

=== Trading ===

{{IN|java}}, expert-level librarian [[villager]]s have a 50% chance to sell a single compass for 4 [[emerald]]s.

{{IN|bedrock}}, expert-level librarian villagers have a {{frac|1|3}} chance to sell a single compass for 4 emeralds.

== Usage ==

Normally, the compass' needle points toward the world [[Spawn#World spawn|spawn point]]. The compass points to spawn when viewed in any way, including as a dropped [[Item (entity)|item]], in a player's hand, in an inventory or the crafting table, or in an [[item frame]]. The direction the needle points to is relative to the player who is viewing it.

In [[the Nether]] or [[the End]], the compass' needle spins and points in random directions.

The compass can be used on a [[lodestone]], after which it is named lodestone compass by default and points to that lodestone as long as the compass is in the same dimension as the lodestone, but if the compass is taken to a different dimension, it spins randomly, as a normal compass would in the Nether or the End. If the lodestone is destroyed, it also spins randomly, even if the lodestone is replaced afterward.  However, if a lodestone compass is placed in storage, the lodestone can be broken and replaced without the compass losing the attunement, as long as the compass remains in storage while the lodestone is missing.

A lodestone compass appears [[enchanting|enchanted]], similar to the [[Enchanted Golden Apple|enchanted golden apple]].

Using {{cmd|setworldspawn}} to change the world spawn also changes where the compass points.

=== Crafting ingredient ===

{{crafting usage|Compass, Compass.gif}}

=== Anvil usage ===

{{:Map/BE|position}}

=== Trading ===

A single compass can be sold to a journeyman-level cartographer villager for 1 [[emerald]].{{only|java}}

A single compass can be sold to an expert-level cartographer villager for 1 emerald as their sixth trade.{{only|bedrock}}
 
A compass is also part of the cost of [[explorer map]]s:

* An ocean explorer map and{{only|java|short=1}}/or{{only|bedrock|short=1}} a woodland explorer map can be bought from a journeyman-level cartographer for 12 emeralds and one compass, as part of their fifth trade.{{only|bedrock}}

* {{IN|java}}, apprentice-level cartographer villagers offer to sell an ocean explorer map for 13 emeralds and a compass, and journeyman-level cartographer villagers offer to sell a woodland explorer map for 14 emeralds and one compass.

=== Enchantments ===

A compass can receive the following [[enchantment]]s:
{|class="wikitable col-2-center col-3-right"
|+
!Name
!Max Level
![[Enchanting|Method]]
|-
|[[Curse of Vanishing]]
|I
|{{Inventory slot|Anvil}}
|-
|}

== Sounds ==
{{edition|java}}:
{{Sound table
|sound=Lodestone lock1.ogg
|sound2=Lodestone lock2.ogg
|source=player
|subtitle=Lodestone Compass locks onto Lodestone
|description=When a compass is used on a lodestone
|id=item.lodestone_compass.lock
|translationkey=subtitles.item.lodestone_compass.lock
|volume=1.0
|pitch=''varies'' <ref group=sound>Can be 0.85 or 0.95 for each sound</ref>
|distance=16
|foot=1}}

{{edition|bedrock}}:
{{Sound table
|type=bedrock
|sound=Lodestone lock1.ogg
|sound2=Lodestone lock2.ogg
|source=block
|description=When a compass is used on a lodestone
|id=lodestone_compass.link_compass_to_lodestone
|volume=1.0
|pitch=0.85-0.95
|foot=1}}

== Data values ==
=== ID ===
{{edition|java}}:
{{ID table
|edition=java
|showforms=y
|generatetranslationkeys=y
|displayname=Compass
|spritetype=item
|nameid=compass
|form=item
|translationkey=item.minecraft.compass,item.minecraft.lodestone_compass
|foot=1}}

{{edition|bedrock}}:
{{ID table
|edition=bedrock
|showaliasids=y
|shownumericids=y
|showforms=y
|notshowbeitemforms=y
|generatetranslationkeys=y
|displayname=Compass
|spritetype=item
|nameid=compass
|id=391
|form=item}}
{{ID table
|displayname=Lodestone Compass
|spritename=lodestone-compass-be
|spritetype=item
|nameid=lodestone_compass
|aliasid=lodestonecompass
|id=602
|form=item
|translationkey=item.lodestonecompass.name
|foot=1}}

=== Item data ===

{{el|java}}:
{{main|Player.dat format}}
<div class="treeview">
* {{nbt|compound|tag}}: The item's '''tag''' tag.
{{:Player.dat_format/Compasses}}
</div>

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

== Advancements ==
{{load advancements|Country Lode}}

== History ==
{{History|java alpha}}
{{History||v1.1.0|[[File:Compass JE1.gif|32px]] Added compasses.
|They have 102 visually distinct frames due to how the texture is generated - see the section below.}}
{{History|java beta}}
{{History||1.8|snap=Pre-release|Compasses can now be found in library [[chest]]s in the new [[strongholds]].}}
{{History|java}}
{{History||1.3.1|snap=12w21a|Librarian [[villager]]s now [[trading|sell]] 1 compass for 10–11 [[emerald]]s, making them [[renewable]].}}
{{History||1.4.2|snap=12w34a|Since the mapping system has been changed, a compass can now be used to [[crafting|craft]] an empty [[map]].}}
{{History||1.5|snap=13w02a|[[File:Compass JE2 BE2.gif|32px]] Compasses now, instead of splitting two textures, use the new animation feature included in texture packs. As a result, they are considerably less precise, having only 29 visually distinct frames. }}
{{History||1.8|snap=14w02a|Librarian villagers now sell 1 compass for 10–12 emeralds.}}
{{History||1.9|snap=15w31a|Compasses are now broken up into individual textures, instead of having every individual frame on one vertical strip like with animated textures.}}
{{History|||snap=15w43a|The average yield of compasses in [[stronghold]] library [[chest]]s has been increased.}}
{{History||1.11|snap=16w39a|Cartographer [[villager]]s have been added, who [[trading|buy]] compasses as their tier 2 trade.}}
{{History||1.13|snap=17w47a|Prior to [[1.13/Flattening|''The Flattening'']], this [[item]]'s numeral ID was 345.}}
{{History|||snap=18w11a|Compasses can now generate in [[shipwreck]] [[chest]]s.}}
{{History||1.14|snap=18w48a|Compasses can now generate in chests in [[village]] cartographer houses.}}
{{History||1.16|snap=20w13a|[[File:Lodestone Compass JE1.gif|32px]] Compasses can now be used on [[lodestone]]s to make them point to the stones.
|Compasses now point to the center of the spawn point block, instead of its north-west corner.}}
{{History|||snap=20w14a|Compasses now have the <code>LodestonePos</code>, <code>LodestoneDimension</code>, and <code>LodestoneTracked</code> data fields. If <code>LodestoneTracked</code> is zero, the game skips checking for a lodestone in the specified position.
|Compasses can now have the [[Curse of Vanishing]] [[enchantment]] on them.}}
{{History|||snap=20w19a|Compasses no longer work in the [[recipe book]].<ref>{{bug|MC-116293}}</ref>}}
{{History|||snap=20w22a|Compasses no longer work in the villager trading GUI.<ref>{{bug|MC-182888}}</ref>}}
{{History||1.17|snap=20w48a|[[File:Compass JE3.gif|32px]] [[File:Lodestone Compass JE2.gif|32px]] The textures of compass and lodestone compass have been changed.}}
{{History||1.19|snap=22w13a|Compasses may now be found in [[ancient city]] [[chest]]s.}}
{{History|||snap=22w14a|Compasses can now used to craft [[recovery compass]]es.}}

{{History|pocket alpha}}
{{History||v0.2.0|[[File:Compass BE1.png|32px]] Added compasses.
|Compasses currently have no function or legitimate method of obtaining them.}}
{{History||v0.8.0|snap=build 1|[[File:Compass JE2 BE2.gif|32px]] Added animated texture to compasses.
|Compasses are now functional and [[crafting|craftable]]. They have been added into the Creative Inventory.}}
{{History||v0.14.0|snap=build 1|Compasses must now be added to a [[map]] using an [[anvil]] to add the location marker.}}
{{History|pocket}}
{{History||1.0.0|snap=?|[[Windows 10 Edition]] can now use the [[anvil]], as well as the [[crafting table]], to apply position markers, with compasses just as [[Pocket Edition]] can in general.}}
{{History||1.0.4|snap=alpha 1.0.4.0|Librarian [[villager]]s now [[trading|sell]] 1 compass for 10–12 [[emerald]]s.}}
{{History||1.1.0|snap=alpha 1.1.0.3|Cartographer villagers have been added, who [[trading|buy]] compasses as part of their tier 2 trade.
|Compasses used with emeralds can be used to buy explorer maps as part of cartographer villagers' fourth tiers trade.}}
{{History|bedrock}}
{{History||1.4.0|snap=beta 1.2.14.2|Compasses can now be found inside map room [[chest]]s in [[shipwreck]]s.}}
{{History||1.10.0|snap=beta 1.10.0.3|Compasses can now be found in [[village]] cartographer house chests.}}
{{History||1.11.0|snap=beta 1.11.0.4|[[Trading]] has been changed, cartographer [[villager]]s now [[trading|buy]] compassess as part of their fourth tier trades.
|Compasses used with [[emerald]]s can now be used to buy explorer maps as part of cartographer and fletcher villagers' third tier trades.
|Librarian villagers now have a {{frac|1|3}} chance to [[trading|sell]] compasses for 4 emeralds as part of their fourth tier trades.}}
{{History||1.16.0|snap=beta 1.16.0.57|[[File:Lodestone Compass BE1.gif|32px]] Compasses can now be used on [[lodestone]]s to make them point to the stones.
|Compasses now have the <code>LodestonePos</code>, <code>LodestoneDimension</code>, and <code>LodestoneTracked</code> data fields. If <code>LodestoneTracked</code> is zero, the game skips checking for a lodestone in the specified position.
|Compasses can now have the [[Curse of Vanishing]] [[enchantment]] on them.}}
{{History||1.16.100|snap=beta 1.16.100.56|Changed the ID {{code|lodestonecompass}} to {{code|lodestone_compass}}.}}
{{History||1.17.0|snap=beta 1.17.0.54|[[File:Compass JE3.gif|32px]] The texture of compass has been changed.}}
{{History||1.18.10|snap=beta 1.18.10.20|[[File:Lodestone Compass JE2.gif|32px]] The texture of lodestone compass has been changed.}}

{{History|console}}
{{History||xbox=TU1|xbone=CU1|ps=1.0|wiiu=Patch 1|switch=1.0.1|[[File:Compass JE2 BE2.gif|32px]] Added compasses.}}

{{History|New Nintendo 3DS Edition}}
{{History||0.1.0|[[File:Compass JE2 BE2.gif|32px]] Added compasses.}}
{{History|foot}}
	
=== Texture generation prior to Java Edition 13w02a ===
{{:Procedural animated texture generation/Compasses}}

== Issues ==
{{issue list}}

== Gallery ==

<gallery>
12w21a CompassPurchase.png|Purchasing a compass from a librarian [[villager]].
</gallery>

== See also ==
*[[Clock]]
*[[Tutorials/Navigation|Navigation]]

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

{{Items}}

[[Category:Tools]]
[[Category:Renewable resources]]

[[cs:Kompas]]
[[de:Kompass]]
[[es:Brújula]]
[[fr:Boussole]]
[[hu:Iránytű]]
[[it:Bussola]]
[[ja:コンパス]]
[[ko:나침반]]
[[nl:Kompas]]
[[pl:Kompas]]
[[pt:Bússola]]
[[ru:Компас]]
[[uk:Компас]]
[[zh:指南针]]</li></ul>
build 1Chunk jittering at extreme coordinates no longer occurs.
Bedrock Edition
1.17.30
{{Extension DPL}}<ul><li>[[:Category:Combat|Category:Combat]]<br/>[[Category:Items]]

[[fr:Catégorie:Combat]]
[[zh:Category:武器]]</li><li>[[Saddle|Saddle]]<br/>{{about|normal saddles|the removed horse saddle|Horse Saddle}}
{{item
| image = <gallery>
Saddle (Pig).png | Pig
Saddle (Horse).png | Horse
Saddle (Strider).png | Strider
</gallery>
| invimage = Saddle
| renewable = Yes
| stackable = No
}}

A '''saddle''' is an [[item]] required to ride [[Pig|pigs]] and [[Strider|striders]] or control ridden [[camel]]s, [[Horse|horses]], [[Donkey|donkeys]] and [[Mule|mules]].

== Obtaining ==
=== Chest loot ===
{{LootChestItem|saddle}}

=== Fishing ===
Saddles can be obtained as a "treasure" item from [[fishing]] with a base chance (without fishing rod enchantments) of 0.8%.

=== Trading ===
Master-level [[Trading#Leatherworker|leatherworker]] [[villager]]s have a 50% chance to sell a saddle for 6 [[Emerald|emeralds]] as their trade.{{only|bedrock}} This trade is always offered in ''Java Edition''.

=== Mob loot ===
Any mob that the player equips with a saddle drops the saddle upon death.

A [[strider]] may spawn being ridden by a [[zombified piglin]], which causes it to spawn wearing a saddle. This saddle always drops when the strider is killed.

A [[ravager]] always spawns with a saddle and always drops the saddle upon death. Looting does not affect the drop.

== Usage ==
[[File:SaddledHorse.png|thumb|right|A [[horse]] equipped with a saddle.]]
While [[camel]]s, [[horse]]s, [[donkey]]s, [[mule]]s and [[Skeleton Horse|skeleton horse]]s{{Only|Java}} can always be ridden, a saddle is required to control them. These mobs (only after being tamed, in the case of equine mobs) can be equipped with a saddle by placing it in their inventory, which can be opened by pressing {{control|use}} while holding a saddle or {{control|sneaking}}. The saddle can be unequipped by removing it from {{SlotSprite|Saddle}} the specific inventory slot. 

Saddles are required to ride [[Pig|pigs]] and [[Strider|striders]], but even with a saddle their movement cannot be controlled like other mobs. A [[Carrot on a Stick|carrot on a stick]] (for pigs) or a [[Warped Fungus on a Stick|warped fungus on a stick]] (for striders) is required to direct these mobs. {{control|Using}} a saddle on one of these mobs equips them with the saddle, and, since they have no inventory, there is no way to retrieve the saddle without killing the mob.

Animals can also be equipped with saddles by a [[dispenser]].

Although [[ravager]]s are equipped with saddles and sometimes ridden by other mobs, the [[player]] is unable to ride ravagers.

== Sounds ==
{{edition|java}}:
{{Sound table
|rowspan=4
|sound=Saddle equip.ogg
|source=neutral
|subtitle=Saddle equips
|description=When a saddle is equipped to a camel
|id=entity.camel.saddle
|translationkey=subtitles.entity.horse.saddle
|volume=0.5
|pitch=0.8
|distance=16}}
{{Sound table
|subtitle=MC-184399
|source=neutral
|description=When a saddle is equipped to a strider
|id=entity.strider.saddle
|translationkey=-
|volume=0.5
|pitch=1.0
|distance=16}}
{{Sound table
|subtitle=Saddle equips
|source=neutral
|description=When a saddle is equipped to a horse, donkey, mule, skeleton horse, or zombie horse
|id=entity.horse.saddle
|translationkey=subtitles.entity.horse.saddle
|volume=0.5
|pitch=1.0
|distance=16}}
{{Sound table
|subtitle=Saddle equips 
|source=neutral
|description=When a saddle is equipped to a pig
|id=entity.pig.saddle
|translationkey=subtitles.entity.pig.saddle
|volume=0.5
|pitch=1.0
|distance=16
|foot=1}}

{{edition|bedrock}}:
{{Sound table
|type=bedrock
|rowspan=3
|sound=Saddle equip.ogg
|source=neutral
|description=When a saddle is equipped to a camel
|id=mob.horse.leather
|volume=1.0
|pitch=1.0}}
{{Sound table
|source=neutral
|description=When a saddle is equipped to a horse, mule, skeleton horse, or zombie horse
|id=mob.horse.leather
|volume=0.6
|pitch=1.0}}
{{Sound table
|source=neutral
|description=When a saddle is equipped to a donkey
|id=mob.horse.leather
|volume=0.5
|pitch=1.0
|foot=1}}

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

{{edition|bedrock}}:
{{ID table
|edition=bedrock
|shownumericids=y
|showforms=y
|notshowbeitemforms=y
|generatetranslationkeys=y
|displayname=Saddle
|spritetype=item
|nameid=saddle
|id=371
|form=item
|foot=1}}

== Achievements ==
{{load achievements|When Pigs Fly}}

== Advancements ==
{{load advancements|This Boat Has Legs}}

== History ==
{{needs render|type=old|isolated saddles in 1.13 dev|section=11}}
{{History|java infdev}}
{{History||20100625-2|[[File:Saddle (Pig) JE1 BE1.png|32px]] [[File:Saddle JE1 BE1.png|32px]] Added saddles.
|Saddles do not [[drops|drop]] from saddled [[pig]]s.
|Saddles can be found in the new [[dungeon]] [[chest]]s.}}
{{History|java}}
{{History||1.2.4|snap=release|When baby animals were introduced, baby [[pig]]s could be ridden just like adult pigs. After this version, baby pigs can no longer be saddled.}}
{{History||1.3.1|snap=12w21a|Saddles can now be [[trading|bought]] from butcher [[villager]]s for 6–7 [[emerald]]s each, and thus have become [[renewable resource|renewable]].}}
{{History||1.4.2|snap=12w36a|Saddles now [[drops|drop]] from killing saddled [[pig]]s.
|Added [[Carrot on a Stick|carrot on a stick]] to direct saddled pigs, effectively controlling them.}}
{{History|||snap=12w37a|Pigs can now jump when being ridden.}}
{{History||1.6.1|snap=13w18a|Regular saddles can now be used to ride [[horse]]s, while previously they required [[Horse Saddle|horse saddle]]s.
|Added saddles to the loot tables of [[mineshaft]] minecarts, [[stronghold]] altar chests, [[village]] blacksmith chests, as well as [[Desert pyramid|desert]] and [[jungle pyramid]]s.
|Added chests to [[Nether Fortress|nether fortresses]], where saddles can be found.}}
{{History||1.7.2|snap=13w36a|Saddles can now be [[fishing|fished]] with [[Fishing Rod|fishing rod]]s and are described as treasure.}}
{{History||1.8|snap=14w02a|[[Trading]] has been changed: leatherworker [[villager]]s now [[trading|sell]] saddles for 8–10 [[emerald]]s each, and butchers no longer [[trading|trade]] saddles.}}
{{History||1.9|snap=15w31a|Saddles can now be found in [[End City|end city]] [[chest]]s.}}
{{History|||snap=15w43a|The average yield of saddles in [[Nether Fortress|nether fortress]] chests has been slightly decreased.}}
{{History|||snap=15w44a|Saddles have been removed from [[mineshaft]] chests.
|The average yield of saddles in [[dungeon]] chests has been decreased.
|The average yield of saddles in [[desert pyramid|desert temple]] chests has been increased.}}
{{History||1.13|snap=17w45a|[[File:White Horse (Saddle) 17w45a.png|50px]] The models of the horse's saddle has been changed.}}
{{History|||snap=17w46a|[[File:White Horse (Saddle) 17w46a.png|50px]] The models of the horse's saddle has been changed once again.}}
{{History|||snap=17w47a|Prior to [[Java Edition 1.13/Flattening|''The Flattening'']], this [[item]]'s numeral ID was 329.}}
{{History|||snap=18w03a|[[File:White Horse (Saddle) 18w03a.png|50px]] The models of the horse's saddle has been changed once again.}}
{{History|||snap=pre2|[[File:White Horse (Saddle) 1.13pre2.png|50px]] The models of the horse's saddle has been changed once again. The reins bit has now been rendered. Also, the lines of the reins are no longer rendered except when riding.}}
{{History||1.14|snap=18w43a|Added [[ravager|illager beast]]s, which [[drops|drop]] saddles.
|[[File:Saddle (Pig) JE2 BE2.png|32px]] [[File:Saddle (Horse) JE2 BE2.png|32px]] <br>[[File:Saddle JE2 BE2.png|32px]] The textures of saddles have been changed.}}
{{History|||snap=18w48a|Saddles can now be found in [[chest]]s in [[village]] tanneries.}}
{{History|||snap=18w49a|Saddles can now be found in chests in [[savanna]] village houses.}}
{{History||1.16|snap=20w13a|[[File:Saddle (Strider) JE1 BE1.png|32px]] Added [[strider]]s, which can be ridden with saddles.}}
{{History|||snap=20w15a|Saddles placed in a [[dispenser]] can now saddle pigs, striders, and tamed horses, donkeys and mules.}}
{{History|||snap=20w16a|Saddles now generate in [[Bastion Remnant|bastion remnant]] chests.}}
{{History|||snap=20w17a|[[File:Saddle (Strider) JE2.png|32px]] The texture of the strider saddles has been changed. The front and back orientation of the saddle has been corrected.<ref>{{bug|MC-176116}}</ref>}}
{{History||1.19|snap=22w13a|Saddles may now be found in [[ancient city]] [[chest]]s.}}
{{History||1.20<br>(Experimental)|link=1.19.3|snap=22w42a|Saddles can be used to ride [[camel]]s with the use of a built-in experimental data pack.}}

{{History|pocket alpha}}
{{History||v0.7.0|[[File:Saddle JE1 BE1.png|32px]] Added saddles. They are currently unobtainable and have no practical usage since they cannot be equipped on any mobs.}}
{{History||v0.9.0|snap=build 1|Saddles can now be obtained from [[village]] blacksmith [[chest]]s.}}
{{History||v0.11.0|snap=build 1|Saddles can now be [[fishing|fished]] with [[fishing rod]]s and are described as treasure.}}
{{History||v0.12.1|snap=build 1|Saddles can now be found in [[nether fortress]]es.}}
{{History||v0.13.0|snap=build 1|Saddles can now be found in [[desert temple]]s.}} 
{{History||v0.15.0|snap=build 1|[[File:Saddle (Pig) JE1 BE1.png|32px]] [[File:Saddle (Horse) JE1 BE1.png|32px]] Saddles can now be used for riding [[horse]]s and [[pig]]s.|Saddles can now be found inside [[jungle temple]]s.}}
{{History||snap=?||Added saddles to the [[Creative inventory]].{{info needed}}}}
{{History|pocket}}
{{History||1.0.0|snap=alpha 0.17.0.1|Saddles can now be found in [[end cities]].}}
{{History||1.0.4|snap=alpha 1.0.4.0|Saddles are now [[trading|sold]] by leatherworker [[villager]]s for 8-10 [[emerald]]s as their only third tiers [[trading|trades]].}}
{{History|bedrock}}
{{History||1.10.0|snap=beta 1.10.0.3|Saddles can now be found in [[plains]] [[village]] tannery and weaponsmith [[chest]]s.
|Added [[ravager]]s, which [[drops|drop]] a saddle upon death.
|[[File:Saddle (Pig) JE2 BE2.png|32px]] [[File:Saddle (Horse) JE2 BE2.png|32px]] <br>[[File:Saddle JE2 BE2.png|32px]] The textures of saddles have been changed.}}
{{History||1.11.0|snap=beta 1.11.0.1|Saddles can now be found in [[savanna]], [[snowy taiga]], [[taiga]] and [[snowy tundra]] village tannery [[chest]]s.
|Saddles can now be found in savanna, taiga, snowy taiga, and [[desert]] village weaponsmith chests.
|Saddles can now be found in savanna [[village]] house chests.}}
{{History|||snap=beta 1.11.0.4|[[Trading]] has been changed. Leatherworker [[villager]]s now have 50% chance to [[trading|sell]] saddles for 10 [[emerald]]s as part of their last tier [[trading|trade]].}}
{{History||1.12.0|snap=beta 1.12.0.3|The trading price of saddles has been lowered to 6 emeralds.}}
{{History||1.16.0|snap=beta 1.16.0.57|[[File:Saddle (Strider) JE1 BE1.png|32px]] Added [[strider]]s, which can be ridden with saddles.|Saddles now generate in [[Bastion Remnant|bastion remnant]] chests.}}
{{History||1.20.0<br>(Experimental)|link=Bedrock Edition 1.19.50|snap=beta 1.19.50.21|Saddles can now be used to ride [[camel]]s with the use of the "[[Bedrock Edition 1.20|Next Major Update]]" [[experimental]] toggle.}}

{{History|console}}
{{History||xbox=TU1|xbone=CU1|ps=1.0|wiiu=Patch 1|switch=1.0.1|[[File:Saddle (Pig) JE1 BE1.png|32px]] <br>[[File:Saddle JE1 BE1.png|32px]] Added saddles.}}
{{History||xbox=none|xbone=none|ps=1.90|wiiu=none|switch=none|[[File:Saddle (Pig) JE2 BE2.png|32px]] [[File:Saddle (Horse) JE2 BE2.png|32px]] <br>[[File:Saddle JE2 BE2.png|32px]] The textures of saddles have been changed.}}

{{History|3ds}}
{{History||0.1.0|[[File:Saddle (Pig) JE1 BE1.png|32px]] <br>[[File:Saddle JE1 BE1.png|32px]] Added saddles.}}
{{History|foot}}

== Issues ==
{{issue list}}

== Trivia ==
* A saddle is considered "armor" by the game, but the value of protection to the animal is zero.
* A saddle on a pig can still be seen if the pig is afflicted with [[Invisibility]].
* When riding a saddled mob, the hunger bar is replaced by hearts (representing the mounted mob's health) resembling the look of the saddle.

== Gallery ==
<gallery>
File:Pig saddle.png|A [[player]] riding a [[pig]] (before [[Java Edition Beta 1.8|Beta 1.8]]).
File:Horse saddle.png|A player riding a [[horse]].
File:13w21a-new-HorseUI-inventory.png|The horse interface implemented in [[Java Edition 13w21a|13w21a]] that allows for the removal of saddles, but only on horses, [[donkey]]s or [[mule]]s.
File:Saddled Mule (picture).png|Mule equipped with both a saddle and a [[chest]].
File:GodSpawner.png|A saddle found in a monster room chest, which coincidentally contains an [[enchanted golden apple]].
</gallery>

== See also ==
* [[Transportation]]

== References ==
{{reflist}}

{{items}}

[[cs:Sedlo]]
[[de:Sattel]]
[[es:Montura]]
[[fr:Selle]]
[[hu:Nyereg]]
[[it:Sella]]
[[ja:鞍]]
[[ko:안장]]
[[nl:Zadel]]
[[pl:Siodło]]
[[pt:Sela]]
[[ru:Седло]]
[[zh:鞍]]
[[Category:Renewable resources]]
[[uk:Сідло]]</li></ul>
beta 1.17.20.20The Far Lands have been fixed, and terrain beyond X/Z ±12,550,821 for the most part generates normally.

Gallery

References

  1. MCPE-30198 — Cannot move diagonally while sneaking in cobwebs on soul sand while drawing back a bow at excessive coordinates
  2. a b MCPE-102410 — Climbing up ladders and vines while sneaking are slower after X/Z ±131,072
  3. MCPE-102412 — Sunflower slightly glitches after X/Z ±262,144
  4. MCPE-102351 — Rendering error beyond X/Z ±1,048,576
  5. https://youtu.be/-CWqHjVdQXo&t=19s
  6. https://youtu.be/wurHDkvIKhQ
  7. "MCPE uses single precision (faster and more mobile-friendly), so, sadly, you notice the first jittering around 700k and it's well unplayable around 900k."u/mojang_tommo on Reddit, May 5, 2014
  8. "So, I've teleported to X=32.000.000... the Stripe Lands?"@_tomcc (Tommaso Checchi) on X, May 5, 2014
Advertisement