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, thus marking the beginning 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 begin turning 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>[[Redstone Comparator|Redstone Comparator]]<br/>{{Block
| image = 
| image2 = 
| transparent = Yes
| light = No
| tool = any
| renewable = Yes
| stackable = Yes (64)
| flammable = No
| lavasusceptible = No
| group = Redstone Comparator
| group2 = Subtracting
| group3 = Powered
| group4 = Powered+Subtracting
| 1-1 = Redstone Comparator.png
| 2-1 = Subtracting Redstone Comparator.png
| 3-1 = Powered Redstone Comparator.png
| 4-1 = Powered Subtracting Redstone Comparator.png
}}
{{Many images}}
A '''redstone comparator''' is a [[block]] that can produce an [[Redstone Dust|output signal]] from its front by reading [[chest]]s, [[lectern]]s, [[beehive]]s and similar blocks, or repeat a signal without changing its strength. It can also be set to either stop outputting a signal when its side input recieves a stronger one (front torch off), or subtract its side input's signal strength from its output (front torch on).

== Obtaining ==
=== Natural generation ===
Redstone comparators generate in [[Ancient City|ancient cities]].

=== Breaking ===
A redstone comparator can be broken instantly with any [[tool]], or by hand, and drops itself as an item.

{{Breaking row|Redstone Comparator|horizontal=y}}

A redstone comparator is removed and dropped as an item if:
* its attachment block is moved, removed, or destroyed;
* [[water]] flows into its space;{{only|java}}
* a [[piston]] tries to push it or moves a block into its space.

If [[lava]] flows into a redstone comparator's space, the redstone comparator is destroyed without dropping as an item.

=== Crafting ===
{{Crafting
|B1=Redstone Torch
|A2=Redstone Torch
|B2=Nether Quartz
|C2=Redstone Torch
|A3=Stone
|B3=Stone
|C3=Stone
|Output= Redstone Comparator
|type=Redstone
}}

== Usage ==
A redstone comparator can be placed on the top of any [[opaque]] block with a solid full-height top surface (including upside-down [[slab]]s and upside-down [[stairs]]). {{IN|be}}, a comparator can also be placed on [[wall]]s and fences. For more information about placement on transparent blocks, see [[Opacity/Placement]].

The redstone comparator has a front and a back — the arrow on the top of the comparator points to the front. When placed, the comparator faces away from the player. The comparator has two miniature redstone torches at the back and one at the front. The back torches turn on when the comparator's output is greater than zero (the arrow on top also turns red). The front torch has two states that can be toggled by {{control|using}} the comparator:
* Down and unpowered (indicating the comparator is in "comparison mode")
* Up and powered (indicating the comparator is in "subtraction mode")

The redstone comparator can take a signal strength input from its rear as well as from both sides. Side inputs are accepted only from [[redstone dust]], [[block of redstone]], [[redstone repeater]]s, other comparators, and [[observer]]s in specific scenarios. The redstone comparator's front is its output.

It takes 1 [[redstone tick]] (2 game ticks, or 0.1 seconds barring lag) for signals to move through a redstone comparator, either from the rear or from the sides. This applies to changing signal strengths as well as simply to turning on and off. 

Redstone comparators check their power state before their scheduled ticks update. This results in redstone comparators not usually responding to 1-tick fluctuations of power or signal strength — for example, a [[clock circuit|1-clock]] input is treated as always off from the side, and always on from the rear. This happens because the signal changes back to its original state before the redstone comparator checks its input states. However, certain setups such as powering any input with two separate observer pulses at the same time will cause a redstone comparator to respond to 2 gametick pulses.

The redstone comparator has four functions: maintain signal strength, compare signal strength, subtract signal strength, and measure certain block states (primarily the fullness of containers).

=== Maintain signal strength ===
A redstone comparator with no powered sides outputs the same signal strength as its rear input.

=== Compare signal strength ===
[[File:Comparators Explained.png|Comparators in comparison mode.|thumb]]
A redstone comparator in comparison mode (front torch down and unpowered) compares its rear input to its two side inputs. If either side input is greater than the rear input, the comparator output turns off. If neither side input is greater than the rear input, the comparator outputs the same signal strength as its rear input.

The formula for calculating the output signal strength is as follows:

<code>output = rear × [[Wikipedia:Iverson bracket|[]]'''''left''''' ≤ '''''rear''''' AND '''''right''''' ≤ '''''rear'''''[[Wikipedia:Iverson bracket|<nowiki>]]]</code>
{{-}}

=== Subtract signal strength ===
[[File:Redstone comparator.png|thumb|The greatest of the side inputs A and C is subtracted from the rear input B, outputting 1. If either A or C were greater than B, it would output 0.]]
A redstone comparator in subtraction mode (front torch up and powered) subtracts the signal strength of the higher side input from the signal strength of the rear input.

<code>output = max('''''rear''''' − max('''''left''', '''right'''''), 0)</code>

For example: if the signal strength is 6 at the left input, 7 at the right input and 4 at the rear, the output signal has a strength of ''max(4 − max(6, 7), 0) = max(4−7, 0) = max(−3, 0) = 0''.

If the signal strength is 9 at the rear, 2 at the right input and 5 at the left input, the output signal has a strength of ''max(9 − max(2, 5), 0) = max(9−5, 0) = 4''.

=== Measure block state ===
{{Schematic | caption = A redstone comparator can measure the fullness of a chest, as well as other block states, even through an opaque block.
 |rd-ew!|rc-w!|ch|SB|rc-e!|rd-ew!
}}
A redstone comparator treats certain blocks behind it as power sources and outputs a signal strength proportional to the block's state. The comparator may be separated from the measured block by an opaque block. However, {{in|je}}, if the opaque block is powered to signal strength 15, then the comparator outputs 15 no matter the fullness of the container.<ref>{{bug|MC-64394}} (resolved as "Works As Intended")</ref>
[[Category:Java Edition specific information]]
{{-}}

==== Fullness of containers ====
{| class="wikitable floatright" style="margin-left: 0.5em; margin-right: 0; text-align: center;"
|+ Minimum Items for Container Signal Strength
|-
!Containers
!{{BlockSprite|Furnace|link=Furnace}}<br>{{BlockSprite|Blast Furnace|link=Blast Furnace}}<br>{{BlockSprite|Smoker|link=Smoker}}
!{{BlockSprite|Hopper|link=Hopper}}<br>{{EntitySprite|Minecart with Hopper|link=Minecart with Hopper}}<br>{{BlockSprite|Brewing Stand|link=Brewing Stand}}
!{{BlockSprite|Dispenser|link=Dispenser}}<br>{{BlockSprite|Dropper|link=Dropper}}
!{{BlockSprite|Chest|link=Chest}}<br>{{EntitySprite|Minecart with Chest|link=Minecart with Chest}}<br>{{BlockSprite|Shulker Box|link=Shulker Box}}<br>{{BlockSprite|Barrel|link=Barrel}}
![[Double Chest|{{Schematic|size=16|ch-s|-|ch-n}}
]]
!{{BlockSprite|Jukebox|link=Jukebox}}
|-
!Total Slots
!3!!5!!9!!27!!54!!1
|-
!Power Level
! colspan="5" |Number of Items
!Music Disc
|-
|0||0||0||0||0||0||No disc
|-
|1||1||1||1||1||1||"13"
|-
|2||14||23||42||1s 60||3s 55||"cat"
|-
|3||28||46||1s 19||3s 55||7s 46||"blocks"
|-
|4||42||1s 5||1s 60||5s 51||11s 37||"chirp"
|-
|5||55||1s 28||2s 37||7s 46||15s 28||"far"
|-
|6||1s 5||1s 51||3s 14||9s 42||19s 19||"mall"
|-
|7||1s 19||2s 10||3s 55||11s 37||23s 10||"mellohi"
|-
|8||1s 32||2s 32||4s 32||13s 32||27s||"stal"
|-
|9||1s 46||2s 55||5s 10||15s 28||30s 55||"strad"
|-
|10||1s 60||3s 14||5s 51||17s 23||34s 46||"ward"
|-
|11||2s 10||3s 37||6s 28||19s 19||38s 37||"11"
|-
|12||2s 23||3s 60||7s 5||21s 14||42s 28||"wait"
|-
|13||2s 37||4s 19||7s 46||23s 10||46s 19||"Pigstep"
|-
|14||2s 51||4s 42||8s 23||25s 5||50s 10||"Otherside"<br>"Relic"
|-
|15||3s||5s||9s||27s||54s||"5"
|}
A redstone comparator can output a signal indicating how full a container is. (0 for empty, 15 for full, etc.) The table on the right is described more in detail, later in this section.

Containers that can be measured by a comparator include:
* {{BlockLink|Furnace}}
* {{BlockLink|Blast Furnace}}
* {{BlockLink|Smoker}}
* {{BlockLink|Brewing Stand}}
* {{BlockLink|Hopper}}
* {{ItemLink|Minecart with Hopper}} on top of a [[detector rail]]
* {{BlockLink|Dispenser}}
* {{BlockLink|Dropper}}
* {{BlockLink|Chest}}
* {{BlockLink|Trapped Chest}}
* {{ItemLink|Minecart with Chest}} on top of a [[detector rail]]
* {{BlockLink|Barrel}}
* {{SchematicSprite|size=16|ch-e}}{{SchematicSprite|size=16|ch-w}} Large chest
* {{SchematicSprite|size=16|ch-e}}{{SchematicSprite|size=16|ch-w}} Large trapped chest
* {{BlockLink|Shulker Box}} (any color)

Generally speaking, the comparator output signal strength represents the average fullness of the slots, based on how many of that item form a full stack (64, 16, or 1 for non-stackable items).

The ''Minimum Items for Container Signal Strength'' table (right) shows the minimum '''''full-stack-equivalent (FSE)''''' to produce different signal strengths from common containers. A '''''full-stack-equivalent''''' quantifies how many normal 64-stackable items are needed to output a corresponding signal strength. The 's' is a constant 64, with the additional amount needed following after.

One may also consider the terms: '''c''umulative-weight''''' or '''''weighted-sum''''' instead of '''''full-stack-equivalent'''''.

Items that stack to a max of 16  ([[snowball]]s, [[sign]]s, [[ender pearl]]s, etc.), contribute +4 to the ''full-stack-equivalent'' for each unity (count of 1 item). Similarly, items that stack to 1 ([[minecart]], [[boat]], etc.) contribute +64, and items that stack to 64 contribute +1.

Example 1: 3 ender pearls will contribute a 3 x 4 = 12 ''full-stack-equivalent''.

Example 2: 16 ender pearls and 60 redstone dust contributes a 16x4 + 60x1 = 124 ''full-stack-equivalent''.

Example 3: 1 minecart and 60 redstone dust contributes a 1x64 + 60x1 = 124 ''full-stack-equivalent''.

Example 4: To produce a signal strength of 10 from a hopper, one requires a ''full-stack-equivalent'' of at least 3s + 14 = 206 but strictly less than than 3s + 37 = 229. This can be done with 3 minecarts, and 14 dirt.

When a comparator measures a large chest or large trapped chest, it measures the entire large chest (54 slots), not just the half directly behind the comparator. A chest or trapped chest that cannot be opened (either because it has an opaque block, [[ocelot]], or [[cat]] above it) always produces an output of 0 no matter how many items are in the container — shulker boxes can always be measured, even if they cannot open.

;Calculating signal strength from items

:When a container is empty, the output is off.

:When it is not empty, the output signal strength is calculated as follows:

:<code>'''''signal strength''''' = floor(1 + (('''''sum of all slots' fullnesses''''') / ('''''number of slots in container''''')) × 14)</code>

:<code>fullness of a slot = '''''number of items in slot''''' / '''''max stack size for this type of item'''''</code>

:''Example:'' 300 blocks in a dispenser (which has 9 slots), where each block stacks to a maximum of 64 has a 300 ''full-stack-equivalent.'' This produces an output with a signal strength of 8:
<blockquote>
1 + ((300 items / 64 items per slot) / 9 slots) × 14 = 8.292, floored is 8
</blockquote>

;Calculating items from signal strength

:It can be useful in redstone circuits to use containers with comparators to create signals of a specific strength. The number of items required in a container to produce a signal of desired strength is calculated as follows:

:<code>items required = max('''''desired signal strength''''', roundup(('''''total slots in container''''' × 64 / 14) × (desired signal strength − 1)))</code>

:''Example:'' To use a furnace (which has 3 slots) to create a strength 9 signal, players need 110 items:
<blockquote>
max(9, (3×64/14) × (9−1)) = 109.714, rounded up is 110
</blockquote>
{{-}}

==== Miscellaneous ====
[[File:Comparator storage.png|Comparators used to measure containers.|thumb]]
Some non-container blocks can also be measured by a redstone comparator:

;{{BlockLink|Beehive}} and {{BlockLink|Bee nest}}

: A hive or nest outputs a signal strength equal to the amount of honey in the hive/nest.

;{{BlockLink|Cake}}

: A cake outputs a signal strength relative to the amount of cake remaining.  Each slice is worth 2 signal strength, with 7 total slices, for an output of 14 for a full cake.

[[File:Cauldron Redstone Strength Values.png|Cauldron signal strength|thumb]]
;{{BlockLink|Cauldron}}

: A cauldron outputs different signal strengths depending on how much water or powdered snow is inside. From completely empty to completely full, the output values are 0, 1, 2, and 3. If lava or powder snow is inside, the strength is always 3.

[[File:Composter Redstone Strength Values.png|Composter signal strength|thumb]]
;{{BlockLink|Composter}}

: A composter outputs different signal strengths depending on the level inside. From completely empty to completely full, the output values are 0, 1, 2, 3, 4, 5, 6, 7 and 8.

;{{Anchor|CommandBlock}}{{BlockLink|Command Block}}

: A command block stores the "success count" of the last command executed, which represents the number of times the most recently used command of this command block succeeded. A "success" is defined by the [[command]]'s success conditions: if a red error message is returned in the chat, the command was not successful.

: Most commands can succeed once per execution, but certain commands (such as those that accept players as arguments) can succeed multiple times, and the comparator outputs the number of times it succeeded (maximum 15 when sent to redstone dust, but in the code it is able to go up to the 32-bit integer limit, and can be used in contraptions with no redstone dust with those values).

: A command block continues to store the success count of the last command executed until it executes its command again, thus the comparator continues to output the same signal strength even after the command block is no longer being activated (it doesn't turn off when the signal to the command block turns off).

;{{BlockLink|End Portal Frame}}

: An end portal frame outputs a full signal of 15 if it contains an [[eye of ender]] and zero otherwise.

[[File:Item frame and comparator.png|A comparator can measure the presence and rotation of an item frame's contents.|thumb]]

;{{EntityLink|Item Frame}}

: A comparator can measure the state of an [[item frame]]'s contents. An item frame comparator outputs 0 if the item frame is empty, or 1 to 8 for any item depending on its rotation: 1 at initial placement, plus 1 for each 45° of rotation for a maximum of 8.

: For an item frame that holds a map, a unit of rotation is 90° instead of 45°, but a comparator still outputs power levels 1 to 8. It takes two full rotations to cycle through all comparator outputs, and each orientation of the map corresponds to two output levels that differ by 4.

: The comparator must be placed behind the block the item frame is attached to, facing away from the item frame. The block must be a full block, and the item frame cannot be submerged in water. Having a sign in the same block as the item frame will prevent the frame from sending a signal as well.{{only|java}}

;{{BlockLink|Jukebox}}

: A jukebox outputs a signal strength indicating which music disc is currently playing. See the ''Minimum Items for Container Signal Strength'' table above.

;{{BlockLink|Lectern}}

: A lectern outputs a signal strength that depends on what page the player is currently on. The calculation used is:
:<code>'''''signal strength''''' = floor(1 + (('''''current page''''' - 1) / ('''''number of pages in book''''' - 1)) × 14)</code>
:This results in page 1 having a signal strength of 1, and the last page having a signal strength of 15. The exception is a single page book, which will output a signal strength of 15.
:For example, a book with 15 pages will output a signal equal to the current page number.  A book with 5 pages will output signal strengths of 1, 4, 8, 11 and 15 for the different pages. A book with 100 pages will have the signal strength increase to the next level on pages 1, 9, 16, 23, 30, 37, 44, 51, 58, 65, 72, 79, 86, 93 and 100.
:

;{{BlockLink|Respawn Anchor}}

: A respawn anchor outputs a signal strength of 0, 3, 7, 11, or 15, depending on the "charged" value.

;{{BlockLink|Sculk Sensor}}

: A sculk sensor outputs a signal strength depending on the type of vibration that is detected.

;{{BlockLink|Chiseled Bookshelf}}

: A chisled bookshelf outputs a signal strength between 1 and 6 indicating the last slot interacted with. When no slot has been interacted with yet, it outputs 0.
{{-}}

== Sounds ==
=== Generic ===
{{Edition|Java}}:
{{Sound table/Block/Stone/JE}}
{{Edition|Bedrock}}:
{{Sound table/Block/Wood/BE}}

=== Unique ===
{{edition|java}}:
{{Sound table
|rowspan=2
|sound=Click.ogg
|subtitle=Comparator clicks
|source=block
|description=When a comparator is set to subtraction mode
|id=block.comparator.click
|translationkey=subtitles.block.comparator.click
|volume=0.3
|pitch=0.55
|distance=16}}
{{Sound table
|subtitle=Comparator clicks
|source=block
|description=When a comparator is set to comparison mode
|id=block.comparator.click
|translationkey=subtitles.block.comparator.click
|volume=0.3
|pitch=0.5
|distance=16
|foot=1}}

{{edition|bedrock}}:
{{Sound table
|type=bedrock
|rowspan=2
|sound=Click.ogg
|source=block
|description=When a comparator is set to subtraction mode
|id=block.click
|volume=0.2
|pitch=0.55}}
{{Sound table
|source=block
|description=When a comparator is set to comparison mode
|id=block.click
|volume=0.2
|pitch=0.5
|foot=1}}

== Data values ==
=== ID ===
{{edition|java}}:
{{ID table
|edition=java
|showforms=y
|generatetranslationkeys=y
|displayname=Redstone Comparator
|spritetype=block
|nameid=comparator
|foot=1}}
{{ID table
|displayname=Block entity
|spritename=redstone-comparator
|spritetype=block
|nameid=comparator
|foot=1}}

{{edition|bedrock}}:
{{ID table
|edition=bedrock
|firstcolumnname=Redstone Comparator
|shownumericids=y
|showforms=y
|generatetranslationkeys=y
|displayname=Unpowered block
|spritename=unpowered-comparator
|spritetype=block
|nameid=unpowered_comparator
|id=149
|form=block
|translationkey=-}}
{{ID table
|displayname=Powered block
|spritename=powered-comparator
|spritetype=block
|nameid=powered_comparator
|id=150
|form=block
|translationkey=-}}
{{ID table
|displayname=Item
|spritename=redstone-comparator
|spritetype=item
|nameid=comparator
|id=522
|form=item
|foot=1}}
{{ID table
|notnamespaced=y
|displayname=Block entity
|spritename=redstone-comparator
|spritetype=block
|nameid=Comparator
|foot=1}}

=== Block states ===
{{see also|Block states}}
{{/BS}}

=== Block data ===
A redstone comparator has a block entity associated with it that holds additional data about the block.

{{el|je}}:
{{see also|Block entity format}}
{{/BE}}

{{el|be}}:
: See [[Bedrock Edition level format/Block entity format]].

== Advancements ==
{{Load advancements|the power of books}}

== Video ==

<div style="text-align:center">{{yt|J7Z20Zzz3yU}}</div>

== History ==
{{info needed section|If {{bug|MC-50242}} also affected comparators?}}
''For a more in-depth breakdown of changes to repeater textures and models, including a set of renders for each state combination, see [[/Asset history]]''
{{History|java}}
{{History||November 24, 2012|link=https://youtube.com/watch?v=YG9RNyRhIow&t=6m56s|[[Jeb]] stated that there may be a "capacitor" in [[Minecraft]]. }}
{{History||December 27, 2012|link={{tweet|Dinnerbone|284388625595125760}}|[[Dinnerbone]] released [https://web.archive.org/web/20190710120115/https://imgur.com/a/FBKed pictures] of the first version of the "comparator", stating it was a replacement for the "capacitor" idea that has variable, alternate inputs.}}
{{History||January 2, 2013|link={{tweet|Dinnerbone|286428595423965184}}|Dinnerbone released one more [http://dinnerbone.com/media/uploads/2013-01/screenshots/2013-01-02_12.06.47.png picture] of the comparator. The picture itself showing a digital-to-analog converter, using the comparator as the main [[block]].}}
{{History||1.5|snap=13w01a|[[File:Redstone Comparator (S) JE1.png|32px]] [[File:Powered Redstone Comparator (S) JE1.png|32px]] [[File:Subtracting Redstone Comparator (S) JE1.png|32px]] [[File:Powered Subtracting Redstone Comparator (S) JE1.png|32px]] [[File:Redstone Comparator (item) JE1 BE1.png|32px]] Added redstone comparators.
|Redstone comparators have 0 delay.
At this point, block ID 149 was used for unpowered comparators, and block ID 150 for powered comparators.}}
{{History|||snap=13w01b|A delay of 1 game tick ({{frac|1|2}} redstone tick) has now been added to redstone comparators to fix bugs.
|The ability to measure containers to redstone comparators has now been added.}}
{{History|||snap=13w02a|[[File:Redstone Comparator (S) JE2.png|32px]] [[File:Powered Redstone Comparator (S) JE2.png|32px]] [[File:Subtracting Redstone Comparator (S) JE2.png|32px]] [[File:Powered Subtracting Redstone Comparator (S) JE2.png|32px]] The appearance of redstone comparators has now been changed - the top texture has changed to show [[quartz]] in the middle and the sides now use the [[smooth stone]] texture rather than the smooth stone slab side texture.
|The algorithm for measuring containers has now been changed so that redstone comparators output a signal with as few as 1 [[item]] in the container.}}
{{History|||snap=13w02b|Redstone comparators now treat large [[chest]]s as a single container.}}
{{History|||snap=13w03a|Redstone comparators now output success count of [[command block]]s.
|Redstone comparators now measure container [[minecart]]s on [[detector rail]]s.}}
{{History|||snap=13w04a|Redstone comparators now measure [[jukebox]]es.}}
{{History|||snap=13w05a|Redstone comparators no longer cause constant [[block]] updates. The delay has now been made consistent, and side input no longer causes a pulse output.
|Block 150 (later <code>powered_comparator</code>) is no longer used; powered state is now represented by the 8s bit on block 149 (later <code>unpowered_comparator</code>).}}
{{History|||snap=13w05b|Redstone comparator delay has now been changed from 1 game tick (1/2 [[redstone]] tick) to 2 game ticks (1 redstone tick).}}
{{History|||snap=13w09c|The redstone signal strength from a redstone comparator next to a [[brewing stand]] with 3 [[water bottle]]s in it is now the same as one with 3 water bottles and 1 ingredient in it.}}
{{History||1.6.1|snap=13w18a|Redstone comparators now measure [[cauldron]]s and [[end portal frame]]s.}}
{{History||1.8|snap=14w04a|Redstone comparators now measure [[item frame]]s.}}
{{History|||snap=14w10a|The torches under redstone comparators have now been shortened, which has changed the underside appearance from [[File:Redstone Comparator UNKVER1 (facing NWU).png|32px]] [[File:Powered Redstone Comparator UNKVER1 (facing NWU).png|32px]] [[File:Subtracting Redstone Comparator UNKVER1 (facing NWU).png|32px]] [[File:Powered Subtracting Redstone Comparator UNKVER1 (facing NWU).png|32px]] to [[File:Redstone Comparator UNKVER2 (facing NWU).png|32px]].}}
{{History|||snap=14w25a|[[File:Redstone Comparator (S) JE3.png|32px]] [[File:Powered Redstone Comparator (S) JE3.png|32px]] [[File:Subtracting Redstone Comparator (S) JE3.png|32px]] [[File:Powered Subtracting Redstone Comparator (S) JE3.png|32px]] The torches on comparators are now subject to ambient occlusion.
|Comparators set to subtract mode appear to be powered as well regardless of incoming power. The subtracting-only model still exists and can be achieved through {{cmd|setblock}}.}}
{{History|||snap=14w25b|[[File:Subtracting Redstone Comparator (S) JE4.png|32px]] [[File:Powered Subtracting Redstone Comparator (S) JE4.png|32px]] The powered front torch when in subtraction mode is now lower.
|Comparators set to subtract by hand now appear normally again.}}
{{History|||snap=14w28a|Redstone comparators now measure [[cake]]s.}}
{{History||1.9|snap=15w42a|With the addition of the [[blaze powder]] fuel slot, [[brewing stand]]s now have 5 slots instead of 4. Their original comparative power values from redstone comparators are listed below:
{{{!}} class{{=}}"wikitable collapsible collapsed" data-description{{=}}"Original values"
! Original values
{{!}}-
{{!}}
*0: 0
*1: 1
*2: 19
*3: 37
*4: 55
*5: 1s 10
*6: 1s 28
*7: 1s 46
*8: 2s
*9: 2s 19
*10: 2s 37
*11: 2s 55
*12: 3s 10
*13: 3s 28
*14: 3s 46
*15: 4s
{{!}}}
}}
{{History|||snap=15w47a|Redstone comparators' side inputs now take power from [[redstone block]]s.}}
{{History||1.13|snap=17w47a|All 3 IDs for the redstone comparator have now been merged into one ID: <code>comparator</code>.
|Redstone comparators now render their underside, which has changed their undersides from [[File:Redstone Comparator UNKVER2 (facing NWU).png|32px]] to [[File:Redstone Comparator UNKVER3 (facing NWU).png|32px]].
|Prior to [[1.13/Flattening|''The Flattening'']], these blocks' numeral IDs were 149 and 150, and the [[item]]'s 404.
|As a result, the formerly unused comparator ID is now technically used again, due to both unpowered and powered versions being merged into a single comparator block ID.}}
{{History||1.14|snap=18w43a|[[File:Redstone Comparator (S) JE4.png|32px]] [[File:Powered Redstone Comparator (S) JE4.png|32px]] [[File:Subtracting Redstone Comparator (S) JE5.png|32px]] [[File:Powered Subtracting Redstone Comparator (S) JE5.png|32px]] [[File:Redstone Comparator (item) JE2 BE2.png|32px]] The textures of redstone comparators have now been changed.}}
{{History|||snap=19w02a|Redstone comparators now measure [[lectern]]s.}}
{{History|||snap=19w03a|Redstone comparators now measure [[composter]]s.}}
{{History|||snap=19w12b|Redstone comparators can now be placed on [[glass]], [[ice]], [[glowstone]] and [[sea lantern]]s.}}
{{History||1.15|snap=19w34a|Redstone comparators now measure how much honey is inside [[beehive|bee hive]]s and [[bee nest]]s.}}
{{History||1.16|snap=20w06a|The way to calculate the input signals of redstone comparators has now been changed.}}
{{History|||snap=20w11a|The changes to the way of calculating the input signals of redstone comparators from [[Java Edition 20w06a|20w06a]] have now been reverted.}}
{{History|||snap=20w16a|Redstone comparators now measure [[Pigstep music disc]]s in [[jukebox]]es.}}
{{History||1.17|snap=20w45a|Redstone comparators now measure [[lava cauldron]]s.}}
{{History|||snap=20w46a|Redstone comparators now measure [[Cauldron#Holding powder snow|powder snow cauldron‌]]s.}}
{{History||1.18|snap=21w41a|[[File:Powered Redstone Comparator (S) JE5.png|32px]] [[File:Powered Subtracting Redstone Comparator (S) JE6.png|32px]] The texture of powered redstone comparator have now been changed.}}
{{History||1.19|snap=22w13a|Redstone comparators now generate as part of [[ancient cities]].}}
{{History||1.20<br>(Experimental)|link=1.19.3|snap=22w42a|Redstone comparators now measure [[chiseled bookshelves]].}}
{{History||1.20.2|snap=23w33a|Redstone comparators now use stone sounds instead of wood sounds.<ref>{{bug|MC-182820|||Fixed}}</ref>}}

{{History|pocket alpha}}
{{History||v0.14.0|snap=build 1|[[File:Redstone Comparator (S) JE2 BE1.png|32px]] [[File:Powered Redstone Comparator (S) JE2 BE1.png|32px]] [[File:Subtracting Redstone Comparator (S) JE2 BE1.png|32px]] [[File:Powered Subtracting Redstone Comparator (S) JE2 BE1.png|32px]]{{verify|Was this the model used?}} [[File:Redstone Comparator (item) JE1 BE1.png|32px]] Added redstone comparators.}}
{{History|pocket}}
{{History||1.0.0|snap=alpha 0.17.0.1|Redstone comparators now measure [[end portal frame]]s.}}
{{History||1.0.5|snap=alpha 1.0.5.0|Redstone comparators now output success count of [[command block]]s.}}
{{History||1.1.0|snap=alpha 1.1.0.0|Redstone comparators now measure [[shulker box]]es.}}
{{History|bedrock}}
{{History||1.2.0|snap=beta 1.2.0.2|Redstone comparators now measure [[jukebox]]es.
|Redstone comparators now render their underside, which has changed their undersides from [[File:Redstone Comparator UNKVER1 (facing NWU).png|32px]] to [[File:Redstone Comparator UNKVER3 (facing NWU).png|32px]]}}
{{History||1.10.0|snap=beta 1.10.0.3|[[File:Redstone Comparator (S) BE.png|32px]] [[File:Powered Redstone Comparator (S) BE.png|32px]] [[File:Subtracting Redstone Comparator (S) BE.png|32px]] [[File:Powered Subtracting Redstone Comparator (S) BE.png|32px]] [[File:Redstone Comparator (item) JE2 BE2.png|32px]] The textures of redstone comparators have now been changed.}}
{{History||1.11.0|snap=beta 1.11.0.1|Redstone comparators now measure [[smoker]]s, [[blast furnace]]s, [[lectern]]s and [[composter]]s.}}
{{History||1.18.10|snap=beta 1.18.10.20|[[File:Powered Redstone Comparator (S) JE5.png|32px]] [[File:Powered Subtracting Redstone Comparator (S) JE6.png|32px]] The texture of powered redstone comparator have now been changed.}}
{{History||1.20.30|snap=beta 1.20.30.20|Redstone comparators now use the <code>minecraft:cardinal_direction</code> [[block state]] instead of <code>direction</code>.}}

{{History|console}}
{{History||xbox=TU19|xbone=CU7|ps=1.12|wiiu=Patch 1|switch=1.0.1|[[File:Redstone Comparator (S) JE2 BE1.png|32px]] [[File:Powered Redstone Comparator (S) JE2 BE1.png|32px]] [[File:Subtracting Redstone Comparator (S) JE2 BE1.png|32px]] [[File:Powered Subtracting Redstone Comparator (S) JE2 BE1.png|32px]]{{verify|Was this the model used?}} [[File:Redstone Comparator (item) JE1 BE1.png|32px]] Added redstone comparators.}}
{{History||xbox=TU31|xbone=CU19|ps=1.22|wiiu=Patch 3|switch=1.0.1|Redstone comparators can now measure [[item frame]]s.}}
{{History||xbox=none|xbone=none|ps=1.90|wiiu=none|switch=none|[[File:Redstone Comparator (S) BE.png|32px]] [[File:Powered Redstone Comparator (S) BE.png|32px]] [[File:Subtracting Redstone Comparator (S) BE.png|32px]] [[File:Powered Subtracting Redstone Comparator (S) BE.png|32px]]{{verify|Was this the model used?}} [[File:Redstone Comparator (item) JE2 BE2.png|32px]] The textures of redstone comparators have now been changed.}}

{{History|3ds}}
{{History||0.1.0|[[File:Redstone Comparator (S) JE2 BE1.png|32px]] [[File:Powered Redstone Comparator (S) JE2 BE1.png|32px]] [[File:Subtracting Redstone Comparator (S) JE2 BE1.png|32px]] [[File:Powered Subtracting Redstone Comparator (S) JE2 BE1.png|32px]]{{verify|Was this the model used?}} [[File:Redstone Comparator (item) JE2 BE2.png|32px]] Added redstone comparators.}}
{{History|foot}}

=== Redstone comparator "items" ===
{{:Technical blocks/Redstone Comparator}}

== Issues ==
{{issue list}}

== Trivia ==
* Comparators do not emit redstone particles when powered, unlike redstone torches and repeaters.<ref>{{bug|MC-51692|||WAI}}</ref>

== Gallery ==
<gallery>
Dinnerbone Comparator 1.png|Dinnerbone showing how comparators work.
Dinnerbone Comparator 2.png|Dinnerbone showing how comparators work.
Dinnerbone Comparator 3.png|Dinnerbone showing how comparators work.
Dinnerbone Comparators 1.png|A contraption incorporating comparators.
Dinnerbone Comparators 2.png|Comparators in action.
Dinnerbone Comparators 3.png|Output specific signals.
Dinnerbone Comparator Thing.png|Another comparator in use.
Item Frame Comparator.png|Rotating the torch in the item frame adjusts the comparator's output.
</gallery>

== References ==
{{reflist}}

{{Redstone}}
{{Blocks|Utility}}
{{Items}}

[[Category:Mechanics]]
[[Category:Block entities]]
[[Category:Redstone mechanics]]
[[Category:Mechanisms]]
[[Category:Manufactured blocks]]
[[Category:Non-solid blocks]]

[[de:Redstone-Komparator]]
[[es:Comparador de redstone]]
[[fr:Comparateur de redstone]]
[[hu:Redstone-komparátor]]
[[ja:レッドストーンコンパレーター]]
[[ko:레드스톤 비교기]]
[[nl:Redstonevergelijker]]
[[pl:Komparator]]
[[pt:Comparador de redstone]]
[[ru:Компаратор]]
[[uk:Редстоуновий компаратор]]
[[zh:红石比较器]]</li><li>[[Bow|Bow]]<br/>{{For}}
{{For|the ranged weapon of a similar name|Crossbow}}
{{Item
| image = <gallery>
Bow.png | Bow
Bow (Pull 0).png | Pulled (state 0)
Bow (Pull 1).png | Pulled (state 1)
Bow (Pull 2).png | Pulled (state 2)
</gallery>
| rarity = Common
| renewable = Yes
| durability = 384
| stackable = No
}}

A '''bow''' is a ranged [[weapon]] that shoots [[arrow]]s.

== Obtaining ==

=== Crafting ===

{{crafting
|showname=0
|B1= Stick
|C1= String
|A2= Stick
|C2= String
|B3= Stick
|C3= String
|Output= Bow
|type= Combat
}}

===Mob loot===

==== Skeletons and Strays ====

[[Skeleton]]s and [[stray]]s have an 8.5% chance of dropping a normal or enchanted bow on death when killed by a [[player]] or a tamed [[wolf]]. 

The chance of dropping a bow is increased by 1% per level of [[Looting]], allowing up to an 11.5% chance of dropping. 

The chance of being enchanted depends on the [[difficulty]], whether it is normal or hard. The enchantment level is equal to enchant level 5-22. 

Bows of [[skeleton trap]]s are always enchanted at level 5 to 23. The exact level depends on [[regional difficulty]], as on Easy it is always a level-5 enchantment.

==== Illusioners ====
{{exclusive|java|section=1}}

[[Illusioner]]s have an 8.5% chance of dropping an unenchanted bow when killed by the player. The chance of dropping a bow is increased by 1% per level of Looting, allowing up to an 11.5% chance of dropping. 

=== Trading ===

Apprentice-level fletcher [[villager]]s sell bows for 2 [[emerald]]s as part of their [[trading|trade]]s.

Expert-level fletcher villagers sell enchanted bows for 7–21 emeralds as part of their trades. The enchantment level is equal to enchant level 5–19.

=== Fishing ===

Bows have a chance of being caught by [[fishing]]. When caught, the bow may be damaged and contain random [[enchantment]]s equivalent to a level 30 enchantment from an [[enchanting table]], including treasure enchantments like [[Mending]].

=== Repairing ===
{{Grinding
|showdescription=1
|ingredients=2x Damaged [[Bow]]
|Damaged Bow
|Damaged Bow
|Bow
|description=The durability of the two bows is added together, plus an extra 5% durability.
}}
{{Crafting
|Damaged Bow
|Damaged Bow
|Output=Bow
|type=Combat
|ignoreusage=1
}}

== Usage ==

=== Weapon ===
[[File:Steve aiming with Bow.png|150px|right]]
[[File:Alex aiming with Bow.png|150px|right]]

Bows can be drawn back by {{control|using}} them. In order to use a bow, the player must have at least one [[arrow]] in their [[inventory]] or be in [[Creative]] mode. The arrow that is shown inside the bow always looks like a regular arrow, regardless of what kind of arrow is actually being shot from the bow.<ref>{{bug|MC-87685||Drawn bow texture does not reflect arrow that will be shot|WF}}</ref>

When drawing a bow, the display zooms in slightly. Charging the bow to its maximum causes it to visually shake as an indicator. Releasing the button shoots an [[arrow]]. Drawing a bow can be canceled by switching to another hotbar slot while holding use.

While the bow is being charged or remains fully charged, the player is forced to move at [[sneaking]] speed, unless they are riding a [[horse]], [[minecart]] or [[boat]], or flying with [[elytra]]. It is not possible to [[Sprinting|sprint]] while charging a bow or holding a drawn bow. When the bow is released, normal motion resumes although any prior sprint is cancelled. Sneaking while drawing the bow makes the player move even slower.

If an arrow hits another player, the player that shoots the arrow hears a high-pitched "ding" sound.{{only|je}}

Fully charged shots launch critical arrows which have a trail of [[particles]] behind them and deal up to <math display="inline">\left ( \frac{3x}{2} \right ) + 2</math>damage, where <math>x</math>is the damage after any enchantments. The listed values below describe maximum damage from a bow with no [[Power]] enchantments, assuming the target is at a distance where drag and gravity are negligible. However, the critical damage is likely to be more around 8-10; critical damage is added at a random value between <math>x</math>and <math display="inline">\left ( \frac{3x}{2} \right ) + 2</math> and it is rare to have minimum or maximum values. The damage dealt can ultimately be less than the maximum damage if the arrow slows down after being shot. 

{| class="wikitable" style="text-align:center" data-description="Shot base damage by changing time"
|-
! Charging time
! Maximum attack damage
|-
|{{ItemSprite|Bow|text= '''0.1 s'''}} (no charge)
|{{hp|1}}
|-
|{{ItemSprite|Bow|text= '''0.2–0.9 s'''}} (medium charge)
|{{hp|5}}
|-
|{{ItemSprite|Bow|text= '''1+ s'''}} (full charge)
|{{hp|6}}
|-
|{{ItemSprite|Bow|text= '''1+ s'''}} (critical)
|{{hp|11}}
|-
|}

The game stores the damage of arrows even in values with a decimal point. For example, it is possible for a critical arrow shot to cause damage values such as 6.4. In this cases of a broken value, the game can round up or down and store the amount for subsequent damage sources.

Any projectile thrown by the player is under the influence of momentum in current versions of ''Minecraft''. Naturally, the player's movement speed can be modified under a number of circumstances, affecting the ballistic trajectory of projectiles, and as a result, the damage inflicted by arrows.

In [[Java Edition Combat Tests]], to avoid sniping, arrows shot from fully-charged bows become non-critical if held drawn back for longer than three seconds. Instantaneous effects on tipped arrows are scaled by 1/8, just like the duration of other effects. For example, Instant Damage I arrow will deal an additional {{hp|0.75}} magical damage.

Damage caused by the arrow is not affected by the [[Strength]] effect.

[[Endermen]] cannot be shot using an arrow, because the arrow either disappears as the enderman teleports, or it gets deflected. Even while immobile, the enderman is immune to damage from arrows. However, an arrow shot from a bow enchanted with [[Flame]] can ignite the enderman.

=== Crafting ingredient ===

{{crafting usage|Bow, Damaged Bow}}

=== Enchantments ===

Bows can receive several different [[enchantment]]s and have a base enchantability of 1. Bow enchantments have no effect on [[arrow]] speed or the distance it travels. In [[Bedrock Edition]], if a bow is enchanted with any level 1 enchantment, it always gets Power I.{{verify|This used to be in the trivia section. Not valid in Java Edition.}}

{| class="wikitable col-3-center"
|+
!Name
!Summary
!Max Level
|-
|[[Power]]
|Increases the damage dealt by bow-shot arrows.
|V
|-
|[[Punch]]
|Increases the knockback dealt by bow-shot arrows.
|II
|-
|[[Flame]]
|Ignites arrows, dealing fire damage to anyone hit as well as igniting TNT and campfires.
|I
|-
|[[Infinity]]<ref group=n name=exclusive>Mending and Infinity are mutually exclusive.</ref> 
|Stops the bow from consuming arrows when shot. A minimum of 1 arrow is still required to work.
|I
|-
|[[Unbreaking]]
|Grants a chance to negate durability consumption, making the bow last longer.
|III
|-
|[[Mending]]<ref group=n name=exclusive></ref>
|Repairs the bow using experience, but also preventing the player from gaining score.
|I
|-
|[[Curse of Vanishing]]
|The bow vanishes on death, not dropping as an item. Overridden by keepInventory.
|I
|}
;Notes
{{Reflist|group=n}}

=== Fuel ===

A bow can be used as [[fuel]] in [[furnace]]s, smelting 1.5 items per bow {{in|java}} or 1 item per bow {{in|bedrock}}.

== Arrows ==

{{main|Arrow}}

As in real life, a flying [[arrow]] in ''Minecraft'' is affected by gravity. Its vertical speed is modified by one block downward every second, resulting in a {{w|Parabola|parabolic}} flight path. An arrow slows down if shot through water, reducing its damage to near zero unless brought back into the air or otherwise given momentum.{{Only|Java}}

Arrows that hit solid [[blocks]] become stuck and can be retrieved, unless the arrow was shot by a bow [[enchant]]ed with [[Infinity]], a player in Creative mode, or a mob.

An arrow shot through [[lava]] ignites, giving it the effect of the [[Flame]] enchantment, igniting any entity it hits. If not extinguished, the fire inflicts up to {{hp|4}} damage. Although a [[wither skeleton]] does not spawn naturally with bows, if it holds a bow then it also shoots flaming arrows.

On impact, an arrow can trigger a wooden [[pressure plate]], [[target]] block, [[wooden button]], or [[tripwire]]. Arrows cannot trigger stone pressure plates or stone buttons.

The player can choose the type of arrow to shoot based on its location in the inventory. Arrows in the off-hand, or the selected hotbar slot if the bow is in the off-hand, are prioritized first. If there are no arrows in the off-hand or selected hotbar slot then the arrow closest to [[Inventory#Slots|slot 0]] is selected.

== Sounds ==
{{edition|java}}:
{{Sound table
|sound=Arrow hit1.ogg
|sound2=Arrow hit2.ogg
|sound3=Arrow hit3.ogg
|sound4=Arrow hit4.ogg
|subtitle=Arrow hits
|source=neutral
|description=When an arrow impacts something
|id=entity.arrow.hit
|translationkey=subtitles.entity.arrow.hit
|volume=1.0
|pitch={{frac|12|11}}-{{frac|4|3}}
|distance=16}}
{{Sound table
|sound=Bow shoot.ogg
|subtitle=Arrow fired
|source=player
|description=When a bow shoots an arrow
|id=entity.arrow.shoot
|translationkey=subtitles.entity.arrow.shoot
|volume=1.0
|pitch={{frac|4|3}}-1.125 <ref group=sound>Depends on how long the bow has been charging. uncharged bows give {{frac|5|6}}-0.625</ref> 
|distance=16}}
{{Sound table
|sound=Succesfull Hit.ogg
|subtitle=Player hit
|source=player
|description=When an arrow shot by a player hits another player
|id=entity.arrow.hit_player
|translationkey=subtitles.entity.arrow.hit_player
|volume=0.18
|pitch=0.45
|distance=16}}
{{Sound table
|sound=Random break.ogg
|subtitle=Item breaks
|source=player
|description=When a bow's durability is exhausted
|id=entity.item.break
|translationkey=subtitles.entity.item.break
|volume=0.8
|pitch=0.8-1.2
|distance=16
|foot=1}}

{{edition|bedrock}}:
{{Sound table
|type=bedrock
|sound=Arrow hit1.ogg
|sound2=Arrow hit2.ogg
|sound3=Arrow hit3.ogg
|sound4=Arrow hit4.ogg
|source=player
|description=When an arrow impacts something
|id=random.bowhit
|volume=1.0
|pitch=1.09-1.3}}
{{Sound table
|sound=Bow shoot.ogg
|source=player
|description=When a bow shoots an arrow
|id=random.bow
|volume=1.0
|pitch=0.83-1.25}}
{{Sound table
|sound=Random break.ogg
|source=player
|description=When a bow's durability is exhausted
|id=random.break
|volume=1.0
|pitch=0.9
|foot=1}}

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

{{edition|bedrock}}:
{{ID table
|edition=bedrock
|shownumericids=y
|showforms=y
|notshowbeitemforms=y
|generatetranslationkeys=y
|displayname=Bow
|spritetype=item
|nameid=bow
|id=300
|form=item
|foot=1}}

== Achievements ==

{{load achievements|Sniper Duel;Archer;Dispense with this;Bullseye}}

== Advancements ==

{{load advancements|Take Aim;Sniper Duel;Bullseye}}

== Video ==

<div style="text-align:center">{{yt|orNlaO12EQg}}</div>

== History ==
{{History|java classic}}
{{History||June 14, 2009|link=https://notch.tumblr.com/post/123343045/my-vision-for-survival|[[Notch]] discussed how bows and [[arrow]]s would work in [[Survival]] mode: "Bows and arrows can be made out of wood. To use it, select the bow from your inventory and make sure you’ve got some arrows. Click in front of you, and an arrow goes flying using real physics. To actually HIT something, aim above it."}}
{{History||0.24 SURVIVAL TEST|The [[player]] did not need a bow to shoot arrows. Instead, {{Key|Tab}} was used to fire arrows. However, arrows still had to be collected to shoot. Launching arrows this way was much slower than the bow that now fires them.}}
{{History|java indev}}
{{History||0.31|snap=20100110|[[File:Bow JE1.png|32px]] Added bow texture to [[items.png]].}}
{{History|||snap=20100122|[[File:Bow JE2 BE1.png|32px]] Added bows as item with changed texture. The right mouse button can be held down to fire in rapid succession. Each [[arrow]] deals {{hp|4}} for each hit. They fly in a [[wikipedia:Trajectory of a projectile|ballistic trajectory]] affected by gravity and drag in air or water. They travel approximately 15 [[block]]s when fired parallel to a flat plane. Arrows also have a maximum range of around 52 blocks when fired at a 38 degree angle on a flat plane.
|Bows often fail to interact with objects, but instead shoot. This is due to the fact that shooting arrows is an instantaneous action.
|At this point, bows have no durability, and can essentially be used infinitely.}}
{{History|java alpha}}
{{History||v1.2.6|Interacting with objects (door, chest, etc.) while holding a bow no longer shoots the arrow.}}
{{History|java beta}}
{{History||1.2|Bows are now used to craft [[dispenser]]s.}}
{{History||1.8|snap=July 8, 2011|slink={{tweet|notch|89414265441763328}}|[[Notch]] teased hold-to-charge bows.}}
{{History|||snap=July 13, 2011|slink={{tweet|notch|91250232981061632}}|Notch indicated that along with bow charging, he would add an [[achievement]] based around shooting a [[skeleton]] at 50 meters, eventually to be known as ''Sniper duel''.}}
{{History|||snap=Pre-release|Bow behavior has been overhauled; they now need to be charged to fire.}}
{{History|java}}
{{History||1.0.0|snap=RC1|A fully charged [[arrow]] from a bow now consistently deals {{hp|9}} damage, with a rare chance of dealing {{hp|10}}.
|Bows now have a [[durability]] of 385 uses.
|Bows no longer need arrows for ammo in [[Creative]] mode.
|The bow can now be [[enchanting|enchanted]] via console commands, but no enchantment affects it.}}
{{History||1.1|snap=release|Bows can now be legitimately enchanted. Four enchantments have been added: [[Flame]], [[Punch]], [[Power]] and [[Infinity]].}}
{{History||1.2.1|snap=12w06a|[[Skeleton]]s now have a 2.5% chance of dropping a bow. One fifth of the time, this bow is enchanted with Power I (20%).}}
{{History||1.4.6|snap=12w50a|Bows can now be enchanted with [[Unbreaking]] using an [[anvil]] and an appropriate [[enchanted book]].}}
{{History|||snap=pre|When a [[player]] hits another player from far away with a bow it makes a high pitched "dinging" sound.}}
{{History||1.7.2|snap=13w36a|Bows can now be obtained as a "treasure" [[item]] from [[fishing]].
|Bows can now be [[enchanting|enchanted]] with [[Unbreaking]] directly in an [[enchantment table]] without the use of an [[anvil]].}}
{{History||1.8|snap=14w02a|Fletcher [[villager]]s now [[trading|sell]] 1 bow for 2–3 [[emerald]]s.}}
{{History|||snap=14w30a|Bow placement when drawing back has been slightly changed.}}
{{History||1.9|snap=15w31a|When shooting, the arrows are no longer offset to the right of the Crosshair.
|The bow in the hotbar now shows an [[arrow]] when being drawn.
|Bows can now shoot an additional 14 types of arrows, selected based on the arrow type held in the off-hand or closest to slot 0.
|Bows cannot be used in the off-hand.}}
{{History|||snap=15w37a|The bow can now be used in the off-hand.
|Bows now prioritize the selected hotbar slot for [[arrow]]s if the bow is in the off hand.
|When using the bow in the off-hand, the bow does do the animation, but does not aim at the target.}}
{{History|||snap=?|Momentum now affects the physics of arrows fired from bows.}}
{{History||1.10|snap=16w20a|Bows are now used by [[stray]]s and can now sometimes be obtained as a rare [[drop]].}}
{{History||1.11|snap=16w33a|Bows can now be used to fuel [[furnace]]s.}}
{{History||1.11.1|snap=16w50a|[[Infinity]] and [[Mending]] are now mutually exclusive for bows.}}
{{History||1.12|snap=17w16a|Bows are now used by [[illusioner]]s and can now sometimes be obtained as a rare [[drop]], although unenchanted.}}
{{History||1.13|snap=17w47a|Prior to [[1.13/Flattening|''The Flattening'']], this [[item]]'s numeral ID was 261.}}
{{History||1.13.1|snap=18w30a|{{bug|MC-88356}}: Fixed a bug: When using the bow in the off-hand, the bow does do the animation, but does not aim at the target.}}
{{History||1.14|snap=19w11a|Fletcher [[villager]]s now [[trading|sell]] enchanted bows.}}

{{History|pocket alpha}}
{{History||v0.3.3|[[File:Bow JE2 BE1.png|32px]] Added bows.}}
{{History||v0.4.0|Bows now have a durability of 385 uses.
|Bows also now slow down the player while aiming.}}
{{History||v0.5.0|Bows are now obtainable after activating the [[nether reactor]].}}
{{History||v0.8.0|snap=build 1|[[File:Bow BE2.png|32px]] The texture of bows has been changed.}}
{{History|||snap=build 7|Bows can now be used as fuel in a [[furnace]].}}
{{History||v0.11.0|snap=build 1|Bows can now be obtained as a "treasure" [[item]] from [[fishing]].}}
{{History||v0.12.1|snap=build 1|Fully charged bows now cause [[particle]]s.
|Bows can now be [[enchanting|enchanted]].
|Bows obtained by [[fishing]] can now be caught enchanted.
|Bows are no longer available from the [[nether reactor]].}}
{{History||v0.15.0|snap=build 1|Added [[stray]]s, which are equipped with a bow that can rarely be dropped by them.
|Bows can now shoot an additional 14 types of [[arrow]]s, selected based on the arrow type closest to slot 0.}}
{{History|pocket}}
{{History||1.0.4|snap=alpha 1.0.4.0|Bows can now be obtained by [[trading]] with a fletcher [[villager]].}}
{{History||1.1.0|snap=alpha 1.1.0.0|Added the [[Mending]] enchantment, which can now be applied to bows and is mutually exclusive to the [[Infinity]] enchantment.
|[[Arrow]]s can now be placed in the offhand slot and bows now prioritize the arrows in that slot.}}
{{History|bedrock}}
{{History||?|Momentum now affects the physics of arrows fired from bows.}}
{{History||1.8.0|snap=beta 1.8.0.10|Bows in the hotbar now show an [[arrow]] when being drawn.}}
{{History||1.10.0|snap=beta 1.10.0.3| [[File:Bow JE2 BE1.png|32px]] The texture of bows has been changed to match {{el|je}}'s texture.}}
{{History||1.11.0|snap=beta 1.11.0.4|Fletcher villagers now sell unenchanted bows for 2 emeralds, and enchanted bows for 8 emeralds.}}
{{History||1.16.210|snap=beta 1.16.210.58|Bows in first-person view is now held differently.<ref>{{bug|MCPE-116741}}</ref>}}
{{History||1.17.0|snap=beta 1.17.0.52|Bows are now held like it was before [[Bedrock Edition beta 1.16.210.58|1.16.210.58 beta]].<ref>{{bug|MCPE-116741}}</ref>}}

{{History|console}}
{{History||xbox=TU1|xbone=CU1|ps=1.0|wiiu=Patch 1|switch=1.0.1|[[File:Bow JE2 BE1.png|32px]] Added bows.}}
{{History||xbox=TU5|Bow behavior is overhauled; they now need to be charged to fire.}}
{{History||xbox=TU31|xbone=CU19|ps=1.22|wiiu=Patch 3|Bows can now be obtained by [[trading]] with a fletcher [[villager]].}}
{{History||xbox=TU46|xbone=CU36|ps=1.38|wiiu=Patch 15|Bows can now shoot an additional 14 types of [[arrow]]s, selected based on arrow type held in the off-hand or closest to slot 0.}}
{{History|foot}}

Historical sounds:

{| class="wikitable"
! Sound
! From
! to
! Pitch
|-
| {{sound||Bow Shooting Old.ogg}}
| 0.31
| Sound Update
| 1.0
|}

== Issues ==
{{issue list}}

== Trivia ==
*Bows were left unchanged in the [[Texture Update]].<ref>{{bug|MC-168156|||WAI}}</ref>
*Dinnerbone got the idea for the high-pitched "ding" sound from playing on a former PvP server called Project Ares.<ref>{{tweet|Dinnerbone|280044119345229826|Also things I learnt from pvping today: Bows need to ding when you hit people (it's so much fun/rewarding!) & arrows don't render far enough|December 15, 2012}}</ref><ref>{{ytl|-b5aXYacYsk|Minecraft PvP with Dinnerbone & Docm77 - Team DocBone @ 11:52|docm77|December 7, 2013|t=712s}}</ref>

== Gallery ==
<gallery>
Enchanted Bow.gif|An enchanted bow.
Bow Shooting.gif|Using the bow.
1.9bow.gif|Drawback animation.
Bow SDGP.png|Bow in the [[Super Duper Graphics Pack]].
Hunting Wabbits.jpg|Using a bow to hunt rabbits.
</gallery>

== References ==
{{reflist}}

==External Links==
*[https://www.minecraft.net/en-us/article/taking-inventory--bow Taking Inventory: Bow] – Minecraft.net on April 13, 2023

{{items}}

[[Category:Combat]]
[[Category:Renewable resources]]

[[cs:Luk]]
[[de:Bogen]]
[[es:Arco]]
[[fr:Arc]]
[[hu:Íj]]
[[it:Arco]]
[[ja:弓]]
[[ko:활]]
[[nl:Boog]]
[[pl:Łuk]]
[[pt:Arco]]
[[ru:Лук]]
[[uk:Лук]]
[[zh:弓]]</li></ul></nowiki>

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.