What Is Pulse Length?
In Minecraft redstone, a pulse is a temporary signal that turns on and then turns back off. Pulse length refers to the amount of time the signal stays in its active state. While many basic power sources stay on until a player or entity interacts with them again, specialized components like the observer are designed to emit a fixed, ultra-short pulse whenever they detect a change in front of their face.
Pulse length matters because redstone components process signals at specific intervals. If a pulse is too short or arrives after an unexpected delay, downstream components might fire rapidly, behave differently than expected, or fail to synchronize with the rest of your build.
Exact Rules and Numbers: The 1-Tick Observer Pulse
The standard benchmark for a short pulse in modern redstone is the output of an observer:
- Duration: When triggered, an observer emits a pulse that lasts for exactly 2 game ticks, which equals 1 redstone tick.
- Power Type and Level: This pulse delivers strong power at the maximum signal strength of level 15 from the back of the block.
- Valid Targets: Because the output is strong power at level 15, the 1-tick pulse can directly activate
redstone dust, aredstone repeater, aredstone comparator, or any mechanism component placed against its output side. - Activation Delay: In Java Edition, the 1-tick pulse is emitted after a delay of 1 redstone tick. In Bedrock Edition, although it is intended to have a 1-tick delay, a timing bug with world-change activations causes the pulse to be delayed by 2 redstone ticks.
Worked Example: Building a Fast Observer Pulse Clock
Because an observer's activation state is itself a detectable change, you can use its 1-redstone-tick pulse length to construct one of the fastest and most compact clocks in the game.
- Place one observer on the ground, noting the direction of its detecting face and the red output dot on its back.
- Place a second observer directly in front of the first one so that the two detecting faces are looking straight at each other.
- As soon as the second observer is placed, the first observer detects the placement and emits a 1-redstone-tick pulse after its internal delay.
- Changing from unpowered to powered changes the observer's state, which the second observer immediately detects, causing it to emit its own 1-tick pulse.
- Place
redstone dustor a mechanism like adispenserbehind either observer to harness the rapid, continuous stream of 1-tick pulses.
How Players Use and Exploit Short Pulses
Short, predictable pulse lengths are the backbone of compact technical builds:
- Flying Machines: When an observer is pushed or pulled by a
pistonorsticky piston(directly or via aslime blockorhoney block), it counts as an update. The observer emits its 1-tick pulse after finishing the movement, never before. Players chain this post-movement pulse into pistons to create self-propelling flying machines. - Automated Crop Farms: In Java Edition, crops changing their age block state trigger an observer to send a brief 1-tick pulse to a piston, harvesting the plant without needing bulky timer circuits.
- Compact Signal Lines: Because observers do not cut off redstone wire and cannot conduct redstone power through themselves, they can deliver isolated 1-tick pulses into tight spaces where full solid blocks would cross-power adjacent wires.
Common Mistakes with Pulse Length and Timing
- Assuming Java and Bedrock Timings Match: A circuit that relies on a 1-redstone-tick observer response in Java Edition will often break in Bedrock Edition because Bedrock observers take 2 redstone ticks to fire after a world change.
- Expecting Pulses from Container Contents: In Java Edition, observers only emit a pulse when a block's block state changes, not its block entity data. Putting items into a chest will not generate a pulse from an observer watching it.
- Confusion Over Quasi-Connectivity States: A
dropper,dispenser, or piston changing its quasi-connectivity state is detectable, which commonly surprises builders when a dropper deactivates and triggers an unexpected extra 1-tick pulse from an adjacent observer.
Java vs Bedrock
| Topic | Java Edition | Bedrock Edition |
|---|---|---|
| Observer Pulse Emission Delay | Emits its 1-redstone-tick pulse after a delay of 1 redstone tick. | Emits its pulse after a delay of 2 redstone ticks due to a bug when components are activated by world changes. |
| What Triggers an Observer Pulse | Detects changes in block states (such as crop age or block placement/breaking), but not block updates or block entity data. | Acts as a block update detector (BUD) and triggers a pulse on anything that causes a block update, rather than block state changes. |
