What Is a Block Update Detector?
A Block Update Detector (commonly called a BUD switch) is a mechanism that exploits game rules to sense changes in adjacent blocks. A redstone component is placed into a state where it should activate or deactivate according to power rules, but the game has not yet notified the component of the change. This waiting component becomes the sensor.
When any neighboring block changes—for example, a block is placed or broken, water or lava levels shift, ice melts, a furnace starts or stops smelting, cake is eaten, or plants and crops grow—the game sends a block update to surrounding spaces. This wakes up the sensor component, causing it to update its state, fire a pulse or toggle an output, and (in self-resetting designs) return to standby.
Core Types and Exact Rules
Players build BUD switches using several distinct component mechanics, or by using the dedicated single-block Observer:
- Piston (Quasi-Connectivity) BUDs: In Java Edition, pistons can be powered by anything that would power the space directly above them (a power source two blocks above, or one block above and to the side). Because the piston does not immediately notice changes in that distant power source, it waits until an adjacent block update wakes it up.
- Stuck-Piston BUDs: Extended pistons cannot be pushed by other pistons. Furthermore, when an extended piston retracts, it does not notify another piston that was already trying to push it. The pushing piston remains stuck until it receives a block update.
- Burned-Out Redstone Torch BUDs: If a redstone torch is wired to loop its redstone dust signal straight back into the block it is attached to, the torch rapidly flashes and burns out. Once burned out, the torch stays off until an update occurs in any block directly adjacent to the torch (including above or below it), causing it to reset and pulse.
- The Observer Block: Added as a compact, single-block detector, the Observer watches the space directly in front of its face. When triggered, it outputs strong power at signal strength
15from its back for2 game ticks(1 redstone tick). It also fires a pulse after being pushed or pulled by a piston.
Step-by-Step Builds: Self-Resetting Piston BUD & Slime BUD
Method 1: Repeater & Redstone Block Piston BUD (Convertible to T-BUD)
- Place a sticky piston horizontally (parallel to the ground).
- Attach a block of redstone directly to the sticky piston's face.
- Run a line from that block of redstone out to the side of the piston into a redstone repeater.
- Point the repeater into a solid block positioned diagonally adjacent to the sticky piston.
- Leave the repeater on its default
1-tickdelay for a self-resetting pulse BUD. When the piston updates and extends, the arm notices the repeater turning off and immediately retracts. If you change the repeater to any delay greater than1 tick, the circuit becomes a toggleable T-BUD that flips states on each update.
Method 2: Compact 1×3 Vertical Slime BUD
- Place a sticky piston facing straight up.
- Place a slime block directly on top of the piston head.
- Place a block of redstone on top of the slime block.
This vertical 1×3 layout (1×4 while extended) resets automatically and allows the sticky piston to detect block updates from 5 of its sides.
How Players Use and Exploit BUDs
- Automated Crop & Plant Farms: BUDs and Observers detect the growth of sugar cane, bamboo, cacti, melons, pumpkins, chorus flowers, vines, cocoa beans, and nether wart, harvesting them the moment they grow.
- Hidden Switches & Inputs: Because BUDs react to furnace smelting states, redstone ore glowing when stepped on, note blocks being played, comparator mode toggles, or composters filling, players use them to build completely hidden secret door triggers.
- One-Time Traps: A compact 2×1 trap BUD can be made by stacking two horizontal sticky pistons facing the same direction with blocks of redstone on both faces. Updating the detector switches the bottom piston outward to pull a floor out from under a player, though it must be manually reset after firing.
- BUD Arrays & Flying Machines: Both quasi-connectivity pistons and in-line stuck pistons can be tiled into 1-wide multi-sensor arrays to monitor long rows of blocks. Observers are indispensable in slime/honey flying machines because moving an Observer with a piston triggers its output after the movement finishes.
Common Mistakes to Avoid
- Misplacing the Diagonal Block on Piston BUDs: On a repeater feedback piston BUD, the powered block must remain diagonally adjacent to the sticky piston. If you accidentally place it horizontally adjacent to the piston, the circuit will turn into a rapid clock and pulse constantly.
- Slime Block Grabbing Walls: In the 1×3 vertical slime block BUD, ensure the slime block does not touch any adjacent wall blocks, or it will snag on the wall and fail to activate.
- Expecting BUDs to Read Container Inventories: Standard BUDs frequently cannot detect changing the inventory contents of a chest, trapped chest, shulker box, ender chest, dispenser, dropper, brewing stand, or furnace, nor inserting a disc into a jukebox or opening an ender chest or shulker box. Use a comparator for inventory checks instead.
- Breaking One-Time Trap Setups in the Wrong Order: When priming a floating extended piston trap using a block, redstone torch, and switched-on lever, you must break the redstone torch before breaking the lever; otherwise the torch briefly relights and updates the piston prematurely.
Java vs Bedrock
| Topic | Java Edition | Bedrock Edition |
|---|---|---|
| Circuit-based BUD switches | Quasi-connectivity piston BUDs, stuck-piston BUDs, and burned-out torch BUDs work reliably because redstone and quasi-connectivity interact directly with block updates. | Most circuit-based BUD switches do not work at all because redstone is largely separated from block updates and quasi-connectivity does not exist. |
| What the Observer detects | Detects changes in block states (such as crop age or block placement/breaking) rather than raw block updates, allowing it to detect a wider range of events that do not cause block updates. | Acts as a true Block Update Detector and detects anything that causes a block update, rather than purely checking block state changes. |
| Observer output delay | Emits its 1-redstone-tick pulse after a delay of 1 redstone tick (2 game ticks). | Delayed by 2 redstone ticks (4 game ticks) instead of 1 due to a bug affecting redstone components activated by world changes. |
