How the Observer Works
An observer monitors the block or fluid space directly in front of its detecting face. When it registers a valid change, it waits for a short delay and then emits a strong redstone pulse from the red dot on its opposite (back) end.
- Output Strength: Always outputs strong power at signal strength 15.
- Pulse Length: The output lasts for 2 game ticks (1 redstone tick).
- Delay: In Java Edition, the pulse is delayed by 1 redstone tick after the change. In Bedrock Edition, a timing bug causes a 2 redstone tick delay when triggered by world changes.
- What It Can Power: Because the output is strong power, it can directly activate redstone dust, repeaters, comparators, or any mechanism component placed against its back, as well as power a solid opaque block to strongly power adjacent components.
- Block Properties: Observers have unique hybrid transparency. They block light and allow mobs to spawn on their top surface, yet they do not conduct redstone power, do not cut off diagonal redstone dust lines, and do not prevent chests directly beneath them from opening.
What Observers Detect
What triggers an observer depends on which edition of Minecraft you play, as the underlying detection mechanics differ:
- Block Placement & Removal: Placing, breaking, or piston-pushing any block or fluid in front of the face triggers the observer in both editions.
- Block State Changes (Java Edition): In Java, observers strictly watch the target's
block statedata (not block entity/NBT data). This includes crop age growth, cauldron fill levels, composter levels, repeater delays, note block pitch changes, waterlogging, and leaf distance updates. - Block Updates (Bedrock Edition): In Bedrock, observers act as a traditional Block Update Detector (BUD). They detect any event that causes a block update in front of them, such as chest inventories changing or certain container interactions, even if no block state changed.
- Piston Movement: When an observer itself is pushed or pulled by a piston (directly or via slime/honey blocks), it treats the arrival at its new position as a detection event and fires a pulse after finishing the movement.
How to Place and Configure
An observer has no GUI and only two block states: facing (all 6 directions: north, east, south, west, up, down) and powered (true or false).
Observers are placed using the same orientation logic as pistons, meaning the block orientation is determined by the direction you are looking when you place it:
- Face Orientation: The detecting face looks away from you (toward the block you click against), while the red output dot on the back points toward you.
- Mining: You must mine an observer with a pickaxe; breaking it by hand or with another tool causes it to drop nothing.
Common Circuits & Applications
- 2-Observer Fast Clock: Place two observers facing Directly into each other. Because an observer changing its
poweredstate is a detectable change, they will endlessly trigger each other, producing a rapid 1-tick pulse clock. You can toggle this clock on and off by using a sticky piston to push one of the observers into or out of alignment. - Automated Crop Farms: Point an observer at sugar cane, bamboo, kelp, or melon/pumpkin stems and wire the back output to a piston. When the plant grows or its stem attaches to a fruit, its block state updates, firing the piston to harvest the crop automatically.
- Flying Machines: Because observers emit a pulse after being moved by a piston, pairing observers with pistons, sticky pistons, and slime or honey blocks allows two halves of a contraption to push and pull each other infinitely across the world.
- Long-Distance Instant Wire & Signal Towers: Observers can watch redstone dust power changes, trapdoors flipping, powered rails toggling, or even leaf blocks updating their
distancestate when a log is placed or broken, allowing vertical or horizontal signal transmission with minimal footprint.
Tips & Common Mistakes
- Placing It Backwards: Beginners often expect the face to look at them like a piston head. Remember that the small red dot on the back always faces you when you place the block.
- Dual-Edge Triggering: An observer pulses when a monitored redstone component turns on and pulses a second time when it turns off. If you only want one pulse per button press or lever cycle, follow the observer with a sticky piston and block (T-flip-flop) or a pulse limiter.
- Container Confusion: In Java Edition, opening a barrel or changing a furnace's smelting state changes a block state and triggers an observer, whereas merely putting items into a chest via a hopper changes block entity data and will not trigger a Java observer (use a comparator instead).
- Torch Burnout Risk: Do not connect a fast double-observer clock directly into a redstone torch; the rapid pulses will quickly cause the redstone torch to burn out.
Java vs Bedrock
| Topic | Java Edition | Bedrock Edition |
|---|---|---|
| Detection Mechanism | Detects changes in block states (ignores block updates that do not alter block states and ignores block entity data). | Acts as a Block Update Detector (BUD), triggering on anything that causes a block update. |
| Activation Delay | Emits its pulse with a delay of 1 redstone tick (2 game ticks). | Delayed by 2 redstone ticks (4 game ticks) due to a bug affecting components activated by world changes. |
