What Is a Zero-Tick Pulse?
When you shorten a redstone signal using a pulse limiter, pistons begin to behave differently. A sticky piston given a 2-tick pulse starts extending, drops its block after 2 ticks, and retracts. With a 1-tick pulse, this happens after 1 tick. A zero-tick pulse takes this to the absolute limit: the redstone line powers on and depowers within the exact same tick.
When a sticky piston receives a 0-tick pulse, it instantly drops its block into the new position (or pulls a block from one space away if empty) and begins retracting in the same tick. Because the signal turns on and off before the game renders a new frame, the redstone dust often does not appear to light up, even though the pulse travels through the circuit.
Exact Rules and Processing Order
Every 0-tick pulse is generated by turning on a redstone line and using a piston to cut off or remove the power source later within that same tick. Mastering 0-tick mechanics requires understanding how the game orders events inside a single tick:
- Tile Tick Priority: Repeaters and comparators are processed during the tile tick phase, but comparators always process later in the tick than repeaters.
- Tile Ticks vs. Block Events: Tile ticks (repeaters and comparators) are always processed earlier in a tick than block events (piston extensions and retractions).
- Update Chains (BUDs): Budded pistons only retract when they receive a block update. By lining up budded pistons, you can control the exact sequence in which pistons retract within a single tick.
- Signal Refreshing: You cannot run a 0-tick pulse through a normal repeater (which lengthens it to 2 ticks) or a comparator (which ignores it). Instead, you must use a 0-tick repeater, which uses a 0-tick pulse to instantly push a redstone block forward and immediately 0-tick it back to its starting spot, adding only block event delay.
Step-by-Step: Building a 0-Tick Generator
Here are two reliable ways to generate a 0-tick pulse, ranging from an easy beginner trick to a dedicated circuit generator:
- The Instant Button Trick (One-Shot): Place a sticky piston with a block on its face. Place a button directly on the side of the piston body (not the back) and press it. The button powers the piston, and as the piston starts moving, it immediately pops the button off its side—cutting power in the same tick and 0-ticking the block.
- Tile-Tick Priority Generator (Reusable): Split a single redstone input into two parallel paths: one going into a
redstone-repeaterand the other into aredstone-comparator. - Place a solid block directly in front of the repeater, and connect your output redstone line to the other side of that solid block.
- Aim a sticky piston at that solid block (or set it up to pull the block away) and wire the comparator's output directly into this piston.
- When you power the main input, BOTH the repeater and comparator receive power after a 2-tick delay. However, because repeaters process before comparators in the same tick, the repeater powers your output line first, and the comparator fires the piston right after to move the solid block and cut the power—creating an early-tick 0-tick pulse.
Practical Uses and Exploits
Because standard logic components ignore or ruin 0-tick signals, almost all practical uses focus on manipulating pistons:
- 0-Tick Chaining: You can fire multiple 0-tick pulses sequentially within the very same tick to move a block multiple spaces instantly. This is done either by firing a tile-tick generator before a block-event generator, using budded piston update chains, or linking stages with 0-tick repeaters.
- Embedding Entities in Blocks: Normally, an extending piston pushes mobs or armor stands out of the way. If you 0-tick a block into a space occupied by an entity, the block teleports directly over the entity without pushing it. Players use this to trap mobs in 1-block glass display cases, suffocate mobs with solid blocks, or overlap armor stands and solid blocks for compact vertical tripwire signaling.
- Fast Block Farms: In tree, cobblestone, and basalt farms, 0-tick pistons harvest and shift generated blocks into TNT blast chambers or wither cages much faster than standard piston clocks.
- 0-Tick Clocks: Built by placing two 0-tick block pushers facing each other and passing a single block back and forth. When running properly, the central block appears completely stationary while piston heads glitch through it, and one output line stays visually on (capable of BUD-powering pistons) while the other stays visually off (BUD-proof).
- Patched Plant Farms: Prior to Java Edition 1.16, rapidly 0-ticking the dirt or sand beneath bamboo, cactus, chorus plants, kelp, sugar cane, and vines forced random growth ticks (discovered in October 2016 and tracked as bug MC-113809). This famous exploit has since been patched out.
Common Mistakes to Avoid
- Using Standard Repeaters or Comparators on the Output: Routing a 0-tick line into a regular repeater stretches the pulse to 2 ticks, breaking instant piston behavior. Routing it into a comparator stops the signal completely.
- Expecting Regular Pistons to Teleport Blocks: Only sticky pistons teleport their pushed block instantly on a 0-tick pulse. A normal piston will start retracting immediately, but the pushed block will slide at normal speed.
- Relying on Visual Cues: Do not assume your generator or 0-tick clock is broken just because the redstone dust does not flash. Many 0-tick pulses never render visually on screen; always test the output with a sticky piston holding a block.
- Overusing Tile-Tick Chaining: When chaining 0-tick pulses by putting a tile-tick generator before a block-event generator, remember that this specific priority jump can only be used once per chain. Use update chains or 0-tick repeaters for longer chains.
