What Is a Block Update?
Because a computer cannot process every single block in a world simultaneously, Minecraft relies on an event-driven notification system called a block update. Whenever a block is modified—whether by a player, an entity, or a chunk tick—it alerts adjacent blocks so they can verify if their own state needs to change.
In Java Edition, block updates are split into three distinct categories:
- Post Placement (PP) updates: Also known as shape updates, these handle connected blocks altering their visual appearance (like stairs or fences) and attached blocks breaking off into items (like torches or crops).
- Neighbor Changed (NC) updates: Commonly called redstone updates, these notify redstone components about power and state changes.
- Comparator updates: Specialized notifications sent to update comparator output signals.
Exact Rules, Priorities, and Update Order
When a block changes, it can trigger multiple types of updates. The game processes these according to a strict numerical priority from -3 to 3:
- Priority -3: Updates occurring before the block change happens.
- Priority -2: Specific updates right after a block is removed (
Blockstate.onRemove()), such as destroying an active lever, observer, redstone torch, or wire. - Priority -1: Specific updates right after a block is placed (
Blockstate.onPlace()), such as placing a repeater, comparator, redstone torch, or wire. - Priority 0: General NC updates (
Level.blockUpdated()). - Priority 1: General comparator updates (
Level.updateNeighbourForOutputSignal()). - Priority 2: General PP updates (
Level.updateNeighbourShapes()). - Priority 3: Later updates, such as an observer turning on/off, a comparator's signal changing, or activating a lever, button, or pressure plate.
Directional order also differs by update type. General PP updates notify immediate neighbors in the order: West, East, North, South, Down, Up. General NC updates notify immediate neighbors in the order: West, East, Down, Up, North, South.
Many redstone components send extended NC updates beyond their immediate 6 neighbors. For example, levers, buttons, pressure plates, and tripwire hooks update their own immediate neighbors, and then update the 6 neighbors around the block they are attached to. Repeaters, comparators, and observers send updates specifically to the block they are facing and that front block's immediate neighbors. Trapped chests also update the neighbors of the block directly beneath them when opened or closed.
Worked Example: Trapped Chest Wireless Update
You can observe extended Neighbor Changed (NC) updates in action by comparing a normal chest to a trapped chest:
- Place a solid block in the air with a Trapped Chest on top of it.
- Leave a 1-block air gap below the solid block, and place a component that awaits an NC update next to the block beneath the chest (within the immediate neighbors of the supporting block).
- Open the trapped chest. Even though the chest block itself does not change its physical shape, beginning to open or close it sends NC updates to its immediate neighbors, followed by the immediate neighbors of the block below it (in
West, East, Down, Up, North, Southorder). - If you swap the trapped chest for a standard Chest, only the immediate 6 neighbors around the chest itself receive the NC update when opened, leaving the lower area unnotified.
How Players Use and Exploit Block Updates
Understanding the distinction between PP and NC updates allows technical players to build silent sensors and hidden triggers:
- Remote NC Detection: Because components like redstone torches, repeaters, levers, and redstone dust send NC updates up to two blocks away in specific patterns, players use them to wake up dormant components without touching them directly.
- Suppression and Stealth Changes: Many natural or specific actions do not emit general NC updates. For example, lighting or generating a nether portal, changing block states with a debug stick, placing blocks via commands, melting ice (before it turns to water), sheep eating grass, or adding/removing a hay bale beneath a campfire do not send general NC updates. Players use these exceptions to create states that only update when a secondary trigger occurs.
- Directional Priority Timing: Because both PP and NC updates always start by checking
WestthenEast, circuits aligned along specific axes will consistently trigger one side before the other within the exact same game tick.
Common Mistakes
- Expecting redstone dust to trigger adjacent observers laterally: When redstone wire changes state, it sends PP updates to the blocks above and below any non-wire block it points horizontally toward, except it specifically does not send that indirect PP update to an observer.
- Confusing PP and NC exceptions: Assuming all block state changes trigger redstone updates. Actions like inserting a music disc, changing a daylight detector's mode, or a plant growing into a double-block plant do not produce general NC updates.
- Using the Debug Stick to test update circuits: Changing a blockstate with a debug stick intentionally bypasses both general PP and general NC updates, which can make a working detector appear broken during creative testing.
