What Is Component Delay?
In Minecraft redstone, signals rarely travel from input to output instantaneously. Most redstone components require a specific amount of time to change their state from off to on, or from on to off. This processing time is measured in redstone ticks.
One redstone tick is equal to two game ticks, or 0.1 seconds (assuming the game is running without lag at its standard 20 game ticks per second). Whenever redstoners refer to a "tick" in a circuit, they mean a redstone tick unless they specifically state "game tick" or "block tick."
Component Delay Rules and Numbers
Different components introduce different delays and pulse behaviors into a circuit:
- Redstone Repeater (1 to 4 redstone ticks): When first placed, a repeater has a delay of 1 redstone tick (2 game ticks / 0.1s). Interacting with it increases the delay by 1 redstone tick per use, up to a maximum of 4 redstone ticks (0.4s) before returning to 1. In Bedrock Edition, the first repeater in a line can exhibit a delay of 0 ticks even though it visibly displays a 1-tick setting.
- Observer (1 or 2 redstone ticks): When an observer detects a change in front of its face, it outputs a strong power pulse at signal strength 15 lasting for 1 redstone tick (2 game ticks). In Java Edition, this pulse is emitted after a 1 redstone tick delay. In Bedrock Edition, it is actually delayed by 2 redstone ticks due to a bug with world-change activations.
- Redstone Torch (1+ redstone ticks): Torches require one or more ticks to flip states and will completely fail to respond to a 1-tick pulse.
- Redstone Comparator (1+ redstone ticks): Like torches, comparators cannot respond to a 1-tick pulse because of their internal update sequence.
- Redstone Dust: Dust transmits power up to 15 blocks, losing 1 signal strength per block traveled before needing to be maintained by a comparator or boosted back to 15 by a repeater.
Worked Example: Synchronizing Two Branches
To see component delays in action, you can build a synchronized dual-lamp tester that compares observer delay against repeater delay:
- Place a solid block on the ground with a lever on it, and run two parallel lines of
redstone_dustout from the block. - On Path A, place a piston facing sideways, and place an
observerwatching the space where the piston head will extend. Run dust from the observer's output back to aredstone_lamp. - On Path B, place a line of
redstone_repeaterblocks leading into a secondredstone_lampright next to the first one. - In Java Edition, the observer takes 1 redstone tick to emit its pulse after detecting the movement. By adjusting the repeaters on Path B (from 1 to 4 ticks each), you can match the arrival time of Path A or chain repeaters together—such as a 4-tick repeater followed by a 1-tick repeater for a 0.5-second (0.4s + 0.1s) total delay.
How Players Use and Exploit Delays
Technical players and beginners alike use component delays to shape signals and control timing:
- Pulse Stretching: A repeater set to a delay of 2 to 4 redstone ticks automatically increases the length of any shorter incoming ON-pulse to match the repeater's setting. For example, feeding a 1-tick, 2-tick, or 3-tick pulse into a 4-tick repeater turns it into a 4-tick ON-pulse.
- Pulse Suppression: Repeaters set to 2 to 4 ticks also suppress any OFF-pulse shorter than their delay setting, keeping a line continuously powered through brief signal drops.
- Observer Clocks and Flying Machines: Placing two observers facing each other creates a fast, compact clock because each observer detects the other changing state. Furthermore, because being moved by a piston counts as a block update after movement finishes, observers provide the delayed pulse needed to drive self-moving flying machines.
- Same-Tick Repeater Locking: A repeater can be locked from the side by another powered repeater or comparator. If a lock and an input change on the exact same tick (because they are fed by the same clock with identical repeater delays), the target repeater will not switch states.
Common Mistakes with Delays
- Feeding a 1-tick pulse into a torch or comparator: Because an observer outputs a 1-redstone-tick pulse (2 game ticks), wiring an observer directly into a
redstone_torchorredstone_comparatoroften fails. The pulse is too short for their update sequences, so neither component will respond. Place a repeater set to 2 to 4 ticks in between to lengthen the pulse first. - Confusing game ticks with redstone ticks: Remembering that 1 redstone tick equals 2 game ticks (0.1 seconds) is critical when planning delays. For example, a half-second delay (0.5s) requires a 4-tick repeater plus a 1-tick repeater.
- Copying Java timings directly to Bedrock: Because Bedrock Edition observers take 2 redstone ticks to fire instead of 1, and the first repeater in a Bedrock circuit has a delay of 0, timing-sensitive contraptions built from Java tutorials will often misfire on Bedrock without repeater adjustments.
Java vs Bedrock
| Topic | Java Edition | Bedrock Edition |
|---|---|---|
| Observer output delay | Emits its 1-tick pulse after a delay of 1 redstone tick (2 game ticks). | Delayed by 2 redstone ticks due to a bug when activated by world changes. |
| First repeater delay | Always delays the signal by at least 1 redstone tick on its default setting. | The first repeater has a delay of zero ticks even though it visually displays 1 tick. |
| Observer detection trigger | Detects changes in block states (including changes that do not cause block updates). | Acts as a block update detector (BUD) and detects anything that causes a block update. |
