Recommended Free Tools
An observer is a redstone block that watches the block, fluid, or air space directly in front of its eye-textured face and sends a short, strong pulse from the red-dot side when that target changes. Craft one in a crafting table, aim the eyes at the event you want to detect, and connect the red-dot side to dust, a repeater, piston, lamp, dispenser, or another powerable component.
Godlike.Host offers hosted Minecraft Java servers with its own game panel, SFTP access and free DDoS protection, if you would rather not host it yourself.
What an observer does
An observer is a compact change detector. It does not provide a continuous redstone signal simply because a block is present. Instead, it monitors the space immediately in front of its face and reacts when the watched block, fluid, or air changes in a way recognized by the edition you are playing.
As an Amazon Associate I earn from qualifying purchases.
The block has two functionally different sides:
- Eye-textured face: the observing side. This must point toward the target.
- Red-dot side: the output side. This sends the redstone pulse into the circuit behind the observer.
Think of the observer as a one-way sensor. The eyes look outward; the red dot sends the result backward. A correctly crafted circuit can use that event to harvest a crop, move a piston, open a mechanism, trigger a dispenser, or start another redstone action.
How to craft an observer
You need a crafting table and these ingredients for one observer:
#1 Best Overall
| Ingredient | Quantity | Role in the recipe |
|---|---|---|
| Cobblestone | 6 | Six blocks |
| Redstone dust | 2 | Two pieces |
| Nether quartz | 1 | One piece |
The recipe produces one observer in a single crafting operation. In a standard 3×3 crafting grid, arrange the materials as follows:
| Cobblestone | Cobblestone | Cobblestone |
| Redstone dust | Nether quartz | Redstone dust |
| Cobblestone | Cobblestone | Cobblestone |
Alternatively, open the crafting-table recipe book and select the observer entry. The recipe book places the required materials in the correct pattern when you have the ingredients available.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrafting steps
- Place and open a crafting table.
- Open the recipe book, search for Observer, and select it, or use the 3×3 arrangement shown above.
- Confirm the craft and move the observer into your inventory.
- Before placing it, decide which block change you want to detect and where the output circuit will run. Orientation is determined by placement, not by a later menu setting.
Which way should an observer face?
Place the observer so its eye-textured face points directly at the block, fluid, or air space you want to monitor. The opposite face, marked by a red dot, must point toward the redstone component that should receive the pulse.
A simple way to check orientation is to stand beside the block before wiring it:
- If you can see the observer’s eyes from the target side, it is looking at that target.
- If the red dot faces your dust, repeater, piston, lamp, or other device, the output has a path into the circuit.
- If the eyes point away from the changing block, the observer is watching the wrong space even if the wiring looks correct.
Observers detect the space directly in front of their face. They are not area sensors, and they do not automatically watch every block adjacent to them. For a crop line, for example, each observer must be positioned so that its face sees the crop, stem, or other changing block you intend to use as the trigger.
How the observer’s pulse works
When the watched target changes, the observer emits a redstone signal from its red-dot side. The output is a strong, short pulse rather than a sustained signal. The documented general behavior is a strength-15 pulse lasting two game ticks, with a normal response delay of two game ticks after the detected change.
Microsoft’s Bedrock redstone description summarizes the behavior as: “Observer: When it detects block updates with its face, it sends a one-tick pulse through the red spot on the back.” The terminology and exact duration can therefore vary with edition documentation and implementation. Design timing-sensitive machines around the version you are running, rather than assuming every observer remains powered for a long interval.
The pulse is powerful enough to activate normal redstone components, but its brief duration matters. A lamp or piston that needs a longer signal may appear to flicker or fail to remain active. In that situation, preserve the observer as the detector and add a repeater chain, pulse extender, or latch after the output.
Java Edition and Bedrock Edition behavior
Observers are not guaranteed to react to exactly the same events in Java Edition and Bedrock Edition. The key difference is how each edition handles update detection and propagation.
| Comparison | Java Edition | Bedrock Edition |
|---|---|---|
| Detection model | Detects relevant target block-state or shape changes. | Functions as a block-update detector. |
| Typical examples | Events such as crop growth or a block being placed or broken can produce a detectable change when the target state changes. | Responses depend on Bedrock’s block-update propagation for the event and version. |
| Propagation | Java update rules determine whether the observer sees the change. | Bedrock update rules can cause a circuit to trigger differently from an otherwise identical Java build. |
| Timing considerations | Use the normal observer delay and pulse behavior for the Java version being played. | Normal timing applies, but a documented MCPE-15793 bug case can show four- or six-tick delays. |
When publishing or sharing a design, state the edition and version assumptions. A machine that relies on a narrow Java block-state change should not be advertised as identical on Bedrock. If a build works in one edition but never fires in the other, first verify that the target event is an update that edition actually exposes to observers.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Using observers in practical builds
Automatic farms
Observers are useful when a farm needs to react to a changing plant or stem. Aim the eye at the crop, stem, or other block whose state changes as the farm progresses. Route the red-dot output to the harvesting mechanism, commonly a piston arrangement or another redstone-controlled device.
- Place the observer with its eyes facing the plant or changing block.
- Leave the red-dot side accessible for wiring.
- Connect that side to the piston or control circuit with redstone dust, a repeater, or both.
- Test the target event in the edition and version you are using.
- If the harvest action is too brief, lengthen the pulse after the observer instead of changing the detector’s orientation.
The observer only reports a detected change; it does not decide whether the resulting farm action is safe. Keep moving pistons, collection systems, and reset mechanisms isolated so the harvest itself does not create an unintended second trigger.
Piston machines
An observer can make a compact piston controller by detecting a block movement or another state change and forwarding the pulse to a piston. Place the observer so the eyes see the intended movement, then run the output into the piston line.
Piston contraptions are also where feedback problems appear most often. A piston moves a block, that movement updates the block seen by the observer, and the observer sends another pulse. If the new pulse moves the piston again, the circuit can repeat indefinitely. Design the machine so the output does not feed directly back into the observed target, or add a stabilizing stage.
Pulse conversion and timing control
Use a repeater when the next mechanism needs the observer’s event at a different delay or when the circuit needs a more controllable redstone path. A repeater-based chain can also help isolate the observer from a feedback path.
When a device requires a signal longer than the observer’s brief pulse, use one of these approaches:
- Repeater chain: adds delay and provides a more sustained powered interval through the chain.
- Pulse extender: converts a short trigger into a longer output.
- Latch: stores the event until a separate reset action turns the output off.
Choose the simplest option that matches the device. A single piston may only need the raw pulse, while a lamp display, timed door, or multi-step machine may require an extender or latch.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteObserver clocks
Place two observers so that their observing faces point at each other and each red-dot side feeds the other observer’s watched space. The resulting interaction can create a rapid repeating pulse, commonly called an observer clock.
This arrangement is intentionally repetitive, not a one-time detector. Use it only when the downstream mechanism can tolerate frequent pulses. A lamp, dispenser, piston, or other component may be activated far more often than intended if it is connected directly to the clock. Add timing control or a shutoff so the clock can be stopped without breaking the build.
Doors and secondary mechanisms
An observer can watch a button-controlled redstone state, piston movement, or another changing block and use the resulting pulse to trigger a second mechanism. This is useful when the first event is physically separated from the action you want to start.
For a dependable connection, place the observer close enough to see the intended state change, then use dust or a repeater from the red-dot side to reach the secondary device. Test both the initial activation and the return to the original state; a mechanism that changes twice may produce two separate observer events.
Free tools Windows power users keep installed
One-click scans. No signup required.
Preventing observer-piston loops
A loop occurs when the observer’s output changes the same target, or a connected target, that the observer is watching. The resulting update produces another pulse, which repeats the movement.
Break the feedback path
Move the observer so it detects the original trigger rather than the piston output. If that is not possible, redesign the wiring so the piston movement cannot update the observer’s watched space.
Add a repeater stabilizer
The documented observer-stabilizer arrangement uses two repeaters and connecting redstone dust to cut a piston-and-observer circuit after one pulse. The repeaters separate the immediate output from the return path, preventing the first movement from becoming an uncontrolled rapid cycle.
Best Value
- Run the observer output into the stabilizer rather than directly into the piston feedback line.
- Use the two repeaters and connecting dust to create a controlled one-way path.
- Place the piston on the stabilized output side.
- Trigger the machine once and watch whether the piston stops after the intended action.
- If the circuit still repeats, inspect every block changed by the piston and remove the remaining path back to the observer’s face.
Troubleshooting an observer circuit
Nothing happens
- Rotate the observer so the eye-textured face points at the intended target.
- Confirm that the red dot faces the dust, repeater, piston, lamp, dispenser, or other component you want to power.
- Check that the target actually changes rather than merely remaining in a changed state.
- Verify that the event is detected by the edition you are playing.
- Test with a simple downstream component before reconnecting a complex machine.
The circuit fires in one edition but not the other
Compare the event itself, not just the block layout. Java and Bedrock use different update-detection and propagation rules. A crop, placement, break, shape, or state change that triggers a Java observer may not produce the same Bedrock update. State the edition and version in the build instructions and choose a target event known to be visible in that environment.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
The piston or lamp activates for too little time
The observer is designed to send a short pulse. Add a repeater chain, pulse extender, or latch after the red-dot output. Do not assume that placing more redstone dust will lengthen the pulse; dust carries the event but does not turn it into a stored signal.
The machine repeats or becomes a clock
Inspect the observer’s face and list every block the piston or mechanism changes. If any of those changes reach the watched space, the circuit has feedback. Break that path or install the two-repeater stabilizer arrangement. If the repeating behavior is intentional, treat it as a clock and add a shutoff and timing control before connecting a device.
The timing is inconsistent
Allow for the normal two-game-tick response and the short output duration. On Bedrock, also account for documented MCPE-15793 cases in which the delay can appear as four or six ticks. Test the complete machine in the target version instead of timing it from a different edition.
Choosing the right observer design
| Goal | Recommended arrangement | Main caution |
|---|---|---|
| Detect one block change | One observer facing the target, with the red-dot side wired to the device. | Orientation and edition-specific update rules determine whether it fires. |
| Start a piston action | Observer output routed directly to a piston when a short pulse is sufficient. | Prevent the piston from updating the watched target. |
| Run a longer action | Observer followed by a repeater chain, pulse extender, or latch. | Choose the duration the mechanism actually needs. |
| Repeat rapidly | Two observers facing each other as a clock. | Provide a shutoff and ensure the device tolerates frequent pulses. |
| Stop a feedback loop | Observer output isolated through two repeaters and connecting dust. | Check for any alternate path that still returns updates to the face. |
Observer build checklist
- Have six cobblestone, two redstone dust, and one nether quartz ready for the craft.
- Place the eyes toward the exact block, fluid, or air space to monitor.
- Point the red dot into the circuit.
- Expect a strong but brief pulse, not a permanent power source.
- Account for the normal two-game-tick response.
- Identify whether the build targets Java Edition or Bedrock Edition.
- For Bedrock timing-sensitive machines, test for the documented four- or six-tick delay anomaly.
- Add repeaters, a pulse extender, or a latch when the receiving device needs a longer or delayed signal.
- Trace piston movement back to the observer’s face before operating the machine repeatedly.
- Use a stabilizer when a piston-and-observer feedback path cannot be removed.
Key takeaway
Craft the observer from six cobblestone, two redstone dust, and one nether quartz, then place it with the eyes facing the event and the red dot facing the circuit. Its strength-15 pulse is ideal for detecting changes and starting compact machines, but its short duration, edition-specific update rules, and vulnerability to feedback loops must be built into the design from the beginning.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
