Minecraft:Block update

A block update is an in-game mechanism that occurs when a block is modified in some way. Limited to the computing power of a computer, the game can not process all blocks at all times, which is why the game needs such mechanism. When a block changes (due to a player, an entity, or a chunk tick, etc.), it notifies nearby blocks that they should check if they need to respond to the change.

Java Edition

in Template:Editions, there are two main types of block updates: post placement (PP) and neighbor changed (NC).

Priorities

This article uses the priorities listed in the table below to categorize the various block updates. However, keep in mind that these values are not actually present in the game's code.

Priority	Description	Method in code
-3	Updates before the change.	N/A
-2	Some updates after the change.	Blockstate. REDIRECT Template:Code REDIRECT Template:Info needed
-1	Some updates after the change.	REDIRECT Template:Java block classpath Template:Redr.Template:Cd
0	General NC updates.	REDIRECT Template:Java classpath.Template:Cd
1	General comparator updates.	REDIRECT Template:Java block classpath Template:Redr.Template:Cd
2	General PP updates.	REDIRECT Template:Java block classpath Template:Redr.Template:Cd
3	Later updates.	N/A

Most players only use -3 to 3 priority values to describe scheduled ticks, so it is recommended not to use these values for the update sequence in order to avoid ambiguity with scheduled tick priorities.

Post placement update

A post placement (PP) update (aka update post placement, update neighbor shapes, update shape) is the most common type of block updates, mainly used for connected blocks changing their shapes (e.g. stairs, fences) and attached blocks dropping into items (e.g. torches, cactus, wheat).

Sending

General PP updates

When a block is placed, destroyed, replaced, or its blockstate is changed, the game sends PP update to its immediate neighbors, in this order: west, east, north, south, down, up.

Exceptions

Some blocks have unique behaviors:

• Lighting a nether portal does not send PP update.
• A nether portal generating does not send PP update.
• Changing block state with debug stick does not send PP update.
• Shulker boxes sends general PP updates when beginning to open/close or finished opening/closing.
• When a redstone wire is placed, destroyed, replaced, or its blockstate is changed, for any block that the redstone wire points horizontally to, if it is not a redstone wire, then the game also sends PP updates to the block above it and the block below it. However, it does not send PP update to an observer.
• Pistons and beds have more complex updates.

Receiving

When a block receives a PP update, the direction of the PP update may be considered. For example, a Minecraft:wheat block accepts only PP updates from beneath.

Only the following blocks can receive PP updates:

Block	What to do when receiving a PP update
Support-requiring blocks (e.g. torches, snow, carpets, doors, fire, etc.)	Checks if it should break and drop as an item.
Connective blocks (e.g. fences, stairs, chests, redstone wires, nether portals, etc.)	Checks if it should change its shape.
redirect Template:blockLink Template:Redr || Checks for being locked or unlocked.
redirect Template:blockLink Template:Redr || Tries to update its instrument type.
redirect Template:blockLink Template:Redr || Calculates the distance to logs.
redirect Template:blockLink Template:Redr || Solidifies if contacted with water.
redirect Template:blockLink Template:Redr and waterlogged blocks || Requests a scheduled tick for flowing.
redirect Template:blockLink Template:Redr || Requests a scheduled tick for pulsing.
REDIRECT Template:EntityLink || Requests a scheduled tick for checking for falling.
redirect Template:blockLink	Requests a scheduled tick for checking whether it is covered by a solid block.
redirect Template:blockLink
redirect Template:blockLink Template:Redr || Requests a scheduled tick for checking if it should drop.
redirect Template:blockLink Template:Redr || Requests a scheduled tick for checking whether it is outside of water.
redirect Template:blockLink	Tries to request a scheduled tick to generate bubble columns.
redirect Template:blockLink

Neighbor changed update

Neighbor changed (NC) updates (aka neighbor changed, update neighbors, redstone update) are the most widely known type of block updates (for historical reasons), and are mainly used for redstone components.

Sending

General NC updates

Most blocks send NC updates to their immediate neighbors when they are placed, destroyed, or replaced, in this order: west, east, down, up, north, south.

Exceptions

Some changes do not produce General NC updates:

1. redirect Template:blockLink

• • Thickens when the upper bamboo thickens.

1. redirect Template:blockLink

• • Grows into a bamboo.

1. redirect Template:blockLink

Template:Redr and

1. redirect Template:blockLink

• • Convert to each other.

1. redirect Template:blockLink

Template:Redr,

1. redirect Template:blockLink

Template:Redr,

1. redirect Template:blockLink

Template:Redr and

1. redirect Template:blockLink

• • Turn into a golem.
• Plants
  • Turn into a double-block plant.

1. redirect Template:blockLink

• • Its water level changes.

1. redirect Template:blockLink

Template:Redr and

1. redirect Template:blockLink

• • Grow, ripen or change their shape.

1. redirect Template:blockLink

• • Grows.

1. redirect Template:blockLink

• • Becomes lit or unlit.

1. redirect Template:blockLink

• • Its signal or its mode is changed.

1. redirect Template:blockLink

Template:Redr,

1. redirect Template:blockLink

Template:Redr, and

1. redirect Template:blockLink

• • Die.

1. redirect Template:blockLink

Template:Redr,

1. redirect Template:blockLink

Template:Redr,

1. redirect Template:blockLink

Template:Redr, and

1. redirect Template:blockLink

• • Grow.

1. redirect Template:blockLink

Template:Redr,

1. redirect Template:blockLink

Template:Redr, and

1. redirect Template:blockLink

• • Opes, close, activate, or deactivate.

1. redirect Template:blockLink

• • Transports to destination.

1. redirect Template:blockLink

• • Gets hydrated or dry.

1. redirect Template:blockLink

• • Melts gradually (but has not turned into water).

1. redirect Template:blockLink

• • Inserts or ejects records.

1. redirect Template:blockLink

• • Grows.

1. redirect Template:blockLink

• • Becomes lit or unlit.

1. redirect Template:blockLink

• • Becomes lit or unlit.

1. redirect Template:blockLink

• • Increases its number using bone meal.

1. redirect Template:blockLink

• • Absorbs water.

1. redirect Template:blockLink

Template:Redr and

1. redirect Template:blockLink

• • Grow.
  • Melon or pumpkin is removed from them.

1. redirect Template:blockLink

• • Grows.
  • Its fruits are collected.

1. redirect Template:blockLink

• • Its number decreases.

1. redirect Template:blockLink

• • Grows, changes its shape, grows out a new vine block.

1. redirect Template:blockLink

Template:Redr,

1. redirect Template:blockLink

Template:Redr, and

1. redirect Template:blockLink

• • Turn into a wither.

1. redirect Template:blockLink

• • Gets eaten by a sheep.

1. redirect Template:blockLink

• • Get eaten by a rabbit.

1. redirect Template:blockLink

• • Gets damaged.

1. redirect Template:blockLink

• • The Eye of Ender is placed.

1. redirect Template:blockLink

• • Generates.

1. redirect Template:blockLink

• • Bottles or potions are added into it.

1. redirect Template:blockLink

Template:Redr and

1. redirect Template:blockLink

• • Change their mode.

1. redirect Template:blockLink

Template:Redr and

1. redirect Template:blockLink

• • Grow.

1. redirect Template:blockLink

• • Changes its mode.

1. redirect Template:blockLink

Template:Redr,

1. redirect Template:blockLink

Template:Redr, and

1. redirect Template:blockLink

• • Becomes activated or deactivated.

1. redirect Template:blockLink

• • Its age or shape changes.

1. redirect Template:blockLink

• • Increase their stage.

1. redirect Template:blockLink

• • Its "disarmed" value changes.

1. redirect Template:blockLink

• • Become occupied or unoccupied.

1. redirect Template:blockLink

Template:Redr and

1. redirect Template:blockLink

• • Generates as a nether portal.

1. redirect Template:blockLink

• • Add or remove hay bale below it.

1. redirect Template:blockLink

Template:Redr,

1. redirect Template:blockLink

Template:Redr,

1. redirect Template:blockLink

Template:Redr,

1. redirect Template:blockLink

Template:Redr,

1. redirect Template:blockLink

Template:Redr, and

1. redirect Template:blockLink

• • Its shape changes.

1. redirect Template:blockLink

Template:Redr,

1. redirect Template:blockLink

Template:Redr, and

1. redirect Template:blockLink

• • Be covered or uncovered by snow.

1. redirect Template:blockLink

Template:Redr,

1. redirect Template:blockLink

Template:Redr, and

1. redirect Template:blockLink

• • Grow.
  • Add or remove kelp/vines above/below it.

1. redirect Template:blockLink

• • Its signal changes.
• All blocks
  • Change their blockstate using debug stick.
  • Placed by a command.

1. redirect Template:blockLink

Template:Redrs and

1. redirect Template:blockLink

• • Have more complex behavior.

Other NC updates

Some blocks (mainly redstone components) send more NC updates other than general NC updates when changing.

Block	Change	Priority	Range and order	Schematic diagram
Lever / Button / Pressure plate / Tripwire hook	Destroy an activated lever/button/pressure plate/tripwire hook.	-2	Their immediate neighbors (in order of west, east, down, up, north, south). Then the immediate neighbors (in order of west, east, down, up, north, south) of the block they're attached to.
	Active or deactive them. Change pressure plate's signal. Tripwire hook connects to a tripwire.	3
Repeater and Comparator	Place or its blockstate changes.	-1	The block they're facing. Then the immediate neighbors (without the repeater/comparator itself. In order of west, east, down, up, north, south) of the block they're facing.
	Remove.	-2
	Comparator's signal changes.	3
Chest	Begin to be open/closed	N/A (the block is not changed)	Its immediate neighbors (in order of west, east, down, up, north, south).
Trapped chest	Begin to be open/closed	N/A (the block is not changed)	Its immediate neighbors (in order of west, east, down, up, north, south). Then the immediate neighbors (in order of west, east, down, up, north, south) of the block below it.
Observer	Lit or unlit.	3	The block it's facing. Then the immediate neighbors (without the observer itself. In order of west, east, down, up, north, south) of the block it's facing.
	Destroy or replace an activated observer.	-2
	Place an activated observer.	-1	Set itself to unactivated without any update. Then update the block it's facing. Then the immediate neighbors (excluding the observer itself. In order of west, east, down, up, north, south) of the block it's facing.
Redstone torch	Place or its blockstate changes.	-1	The immediate neighbors (in order of west, east, down, up, north, south) of the immediate neighbors (in order of down, up, north, south, west, east) of the torch.
	Destroy, replace, or its blockstate changes.	-2
Redstone wire	Destroy or replace.	-2	The immediate neighbors (in order of west, east, down, up, north, south) of the immediate neighbors (in order of down, up, north, south, west, east) of the wire. Then updates the immediate neighbors (in order of west, east, down, up, north, south) and the immediate neighbors (in order of west, east, down, up, north, south) of the immediate neighbors (in order of down, up, north, south, west, east) of adjacent redstone wires (in order of north, east, south, west). Then updates the immediate neighbors (in order of west, east, down, up, north, south) and the immediate neighbors (in order of west, east, down, up, north, south) of the immediate neighbors (in order of down, up, north, south, west, east) of redstone wires above the solid blocks adjacent to the redstone wire (in order of north, east, south, west). Then updates the immediate neighbors (in order of west, east, down, up, north, south) and the immediate neighbors (in order of west, east, down, up, north, south) of the immediate neighbors (in order of down, up, north, south, west, east) of redstone wires below the non-solid blocks adjacent to the redstone wire (in order of north, east, south, west).
	Place.	-1	Updates the immediate neighbors (in order of west, east, down, up, north, south) of the block above the wire. Then updates the immediate neighbors (in order of west, east, down, up, north, south) of the block below the wire. Then updates the immediate neighbors (in order of west, east, down, up, north, south) and the immediate neighbors (in order of west, east, down, up, north, south) of the immediate neighbors (in order of down, up, north, south, west, east) of adjacent redstone wires (in order of north, east, south, west). Then updates the immediate neighbors (in order of west, east, down, up, north, south) and the immediate neighbors (in order of west, east, down, up, north, south) of the immediate neighbors (in order of down, up, north, south, west, east) of redstone wires above the solid blocks adjacent to the redstone wire (in order of north, east, south, west). Then updates the immediate neighbors (in order of west, east, down, up, north, south) and the immediate neighbors (in order of west, east, down, up, north, south) of the immediate neighbors (in order of down, up, north, south, west, east) of redstone wires below the non-solid blocks adjacent to the redstone wire (in order of north, east, south, west).
	Its signal changes	3	Update the immediate neighbors (in order of west, east, down, up, north, south) of the datum points. Datum points include the wire and the immediate neighbors of the wire, in random order.
	Changes between dot and cross	3	Update the immediate neighbors (without the wire itself, and in order of west, east, down, up, north, south) of the solid block next to the wire (in order of north, east, south, west).
Rails	​<more information needed></more information needed>
Any block	Placed with a command.	3	Update the immediate neighbors (in order of west, east, down, up, north, south).

Receiving

When an NC update is received, the block that caused that update may taken into consideration. For example, a rail accepts only NC updates from power components.

Only the following blocks can react to NC updates:

Block	What to do when receiving an NC update
redirect Template:blockLink Template:Redr || Tries to melt.
redirect Template:blockLink	Tries to change its state.
redirect Template:blockLink
redirect Template:blockLink
redirect Template:blockLink
redirect Template:blockLink
redirect Template:blockLink
redirect Template:blockLink
redirect Template:blockLink
redirect Template:blockLink
redirect Template:blockLink
redirect Template:blockLink
redirect Template:blockLink
redirect Template:blockLink
redirect Template:blockLink
redirect Template:blockLink
redirect Template:blockLink
redirect Template:blockLink
redirect Template:blockLink
redirect Template:blockLink	Tries to change itself to be in the correct state.
redirect Template:blockLink
redirect Template:blockLink Template:Redr || Tries to absorb water.

Comparator update

Template:Message boxTemplate:Article other Template:Schematic The comparator update (i.e. Block entity updates, Update neighbor for output signal) is a subtype of the neighbor update that is only sent to comparators. Redstone comparators can read certain blocks and produce an output signal, and in turn, these blocks can send comparator updates when changing, to notify the comparators. Comparators can also read some entities (item frames and glow item frames), as such, these entities can send comparator updates too, even though they are not blocks.

When a block that can be detected by comparators changes, it sends updates to surrounding comparators (including comparators separated by a solid block), in this order: north, east, south, west.

After receiving a comparator update, comparators attempt to calculate and change their output signal.

Special blocks

1. redirect Template:blockLink

Template:Redr: during the start of the extension/retraction process, every time a moving piston block gets placed and every time one of the normal blocks<ref>"Normal block" is intended as not a "moving piston" block.</ref> is replaced/removed, PP updates are sent to these blocks' neighbors. Once all moving piston blocks have been placed, the game will send NC updates to the replaced/removed normal blocks' neighbors.

Sticky pistons, however, do not send NC updates around their head when they start to pull blocks: only the NC updates caused by the moving piston block turning back into a normal block are sent, once the retraction process is over. If a sticky piston fails to retract a slime block or a honey block due to the pull limit, no updates will be sent around the head whatsoever.

Block updates and DFS

Block updates follow the principle of

1. REDIRECT Template:Wikipedia

Template:Redr (DFS).

For example, when Block A changes, it maybe sends block updates to B and C one by one. Receiving the update, B maybe changes and sends updates to D and E. Receiving update from B, D changes and sends updates to some block. Then E receives the update from B. Then C receives the update from A.

Self update

When a block is placed, it checks and adapts itself to its surroundings by Blockstate.onPlace() or similar methods. Strictly speaking, this isn't a block update; however when a block is placed or changed, if it changes again when self-updated, then the former change does not produce any general update (this is a bug).

Here is a list of self updates that can cause this bug.

1. redirect Template:blockLink

• • When being placed, if it should be powered, becomes powered.

1. redirect Template:blockLink

• • If in the nether, it turns into an dry sponge.

1. redirect Template:blockLink

• • When being placed, it absorbs water and turns into an wet sponge.

1. redirect Template:blockLink

Template:Redr and

1. redirect Template:blockLink

• • When a powered target or observer is placed, it turns into an unpowered state.

1. redirect Template:blockLink

• • When being placed, it updates the signal and connection.

1. redirect Template:blockLink

• • When being placed, if it should be extinguished, removes itself.

1. redirect Template:blockLink

• • When being placed, if it should explode, removes itself.

1. redirect Template:blockLink

Template:Redr,

1. redirect Template:blockLink

Template:Redr,

1. redirect Template:blockLink

Template:Redr,

1. redirect Template:blockLink

• • When being placed, it updates its shape.

1. redirect Template:blockLink

• • When being placed, it checks whether it is pressed and updates its state.

1. redirect Template:blockLink

• • When being placed, if it should turn into a golem, removes itself.

Bedrock Edition

1. Redirect Template:Empty section

History

Navigation

Versions	Demo Locations Template:FileLink (Beta 1.3)
Development	Version history Template:LegacyBlockLink Template:LegacyBlockLink Template:LegacyBlockLink Template:LegacyBlockLink Template:EnvLink Template:FileLink Template:LegacyBlockLink Template:LegacyBlockLink Template:LegacyItemLink Template:EnvLink Template:ItemLink Template:EntityLink Template:BlockLink Snapshots Template:BlockLink Template:BlockLink Template:ItemLink Template:ItemLink Template:BlockLink Template:ItemLink Template:InvLink Template:BlockLink Template:EnvLink Template:BiomeLink
Technical	See here for more information
Game customization	Template:EnvLink Template:PersonaLink Template:ItemLink Template:FileLink Template:EnvLink

Editions	Merged Template:Edition Template:Edition Ports to consoles Template:Wikipedia Template:Wikipedia Template:Wikipedia Template:Wikipedia Template:Wikipedia Discontinued Template:Edition Template:Edition Template:Edition
Development	Version history Template:LegacyBlockLink Template:EntityLink Template:FileLink Template:FileLink Template:EnvLink Template:ItemLink Template:BlockLink Template:InvLink Template:EntityLink Template:FileLink Template:EntityLink
Technical	Template:EffectLink Template:FileLink Template:FileLink Template:File com.mojang Template:FileLink Template:File Installation files Template:FileLink Template:FileLink Template:FileLink Template:FileLink Template:BlockLink Template:File Identifier Template:FileLink Template:ItemLink Template:EnvLink Template:EnvLink Anomalous Template:ItemLink Template:EnvLink § Formatting codes Simulation distance Template:BlockLink Template:FileLink Template:FileLink Template:EnvLink Template:FileLink Template:EntityLink Template:BlockLink Development resources Template:Nbt NBT format Template:Nbt Level format Template:EnvLink Protocol Template:EnvLink RakNet Creator Template:File Official documentation Template:FileLink Template:EntityLink Template:File File extensions Template:FileLink Add-ons Template:ItemLink Template:EnvLink Template:EnvLink Template:EnvLink Template:EnvLink Template:FileLink Template:EnvLink Template:EnvLink Template:BiomeLink Template:EnvLink Family Spawn event Template:ItemLink Template:BlockLink Template:EnvLink Template:BiomeLink Template:EnvLink Template:BlockLink Template:BlockLink Template:BlockLink Template:BlockLink manifest.json Template:EnvLink Template:Nbt Molang Template:BlockLink
Multiplayer	Template:FileLink Featured servers Event servers Server list Template:FileLink Template:FileLink Template:FileLink Template:FileLink
Exclusive features	Template:FileLink Template:FileLink Template:FileLink Template:FileLink Template:FileLink Template:EnvLink Template:EnvLink Template:ItemLink Template:FileLink Template:FileLink Template:EnvLink Template:EnvLink Template:EnvLink Template:PersonaLink Template:EnvLink Loading tips Template:FileLink Ray Tracing Template:BiomeLink Template:EnvLink Blocks Template:BlockLink Template:BlockLink Mobs Template:EntityLink Template:EntityLink Effects Template:EffectLink Unused Template:BlockLink Template:BlockLink Template:BlockLink Template:BlockLink Template:BlockLink Template:BlockLink Template:BlockLink Template:BlockLink Template:BlockLink Template:BlockLink Template:BlockLink Template:BlockLink Template:EntityLink Template:EntityLink Template:BiomeLink Template:EnvLink
Removed	Template:BlockLink Template:EnvLink Template:EnvLink Template:FileLink Pocket Edition protocol Legacy

de:Blockupdate ja:ブロック更新 lzh:塊竦 pt:Atualização de bloco zh:方块更新