Zero-Tick Pulse Generator

A zero-tick pulse generator creates a redstone pulse that turns on and off within the exact same game tick. When applied to a sticky piston, this ultra-short pulse allows it to instantly teleport a block forward or drop it without going through the standard three-game-tick movement delay. It is an essential circuit for fast piston doors, instant wire, and advanced technical contraptions.

Pulse CircuitsAdvancedJava Edition
Zero-Tick Pulse Generator video tutorial

Video: How Zero Ticks Work [It's Not Magic] by PotatoCraft_TMC

How to build it

  1. Method 1: Place the Output and Cutoff Pistons (Tick Priority)

    Place the sticky piston you want to zero-tick facing your desired direction, with a movable block on its face. Place a solid conductive block directly behind this piston, and set a second sticky piston to the side so it can push that conductive block out of the way.

  2. Add the Repeater and Comparator

    Run a Redstone Repeater directly into the solid conductive block behind your main sticky piston. Next to it, run a Redstone Comparator (or an Observer) into the side sticky piston that moves the conductive block.

  3. Wire the Input for Method 1

    Connect both the repeater and the comparator to the exact same redstone dust input line and place a lever or button. Because repeaters have higher tile tick priority than comparators, the main piston receives power and immediately loses it in the same game tick when the comparator fires.

  4. Method 2: Set Up the Piston Line (Rail Update Order)

    For a flexible multi-piston setup, place a row of sticky pistons you want to zero-tick. Directly above each piston, place a Note Block to serve as a block updater.

  5. Place the Slider Blocks and Pistons

    Above the note blocks, place a row of solid movable blocks (this acts as your conductive slider). At the ends of this row, place sticky pistons facing inward to push the row of solid blocks back and forth.

  6. Position the Powering Observers

    Place a row of Observers pointing directly into the movable slider blocks. Add one additional Observer pointing into the slider piston that will push the row of blocks away.

  7. Lay the Rail Line and Input

    Place a continuous line of Powered Rails across the faces of all the observers. Place your input trigger on the end of the rail line closest to the slider piston; rail updates trigger observers furthest from the power source first, ensuring the main pistons are powered and updated via the note blocks just before the slider moves away.

How it works

A standard Minecraft game tick happens every 1/20th of a second. Normally, when a piston is powered, it takes two game ticks to extend and three game ticks for the pushed block to become solid again. Shortening a pulse to two game ticks (using an observer) causes a sticky piston to drop its block, while a one-game-tick pulse (created by cutting off an observer pulse using scaffolding or leaf update delays) moves a block in just one tick.

A zero-tick pulse goes a step further by starting and ending the redstone signal within the exact same game tick. To achieve this, two things must happen in a strict micro-order during a single tick:

  • Powering and Updating: The target piston must receive power through a solid conductive block along with a block update so it begins extending.
  • Instant Cutoff: Another piston must push that conductive block away. The moment a solid block starts moving, it instantly turns into a non-conductive moving block entity, severing the power connection in the same tick.

To guarantee the piston powers before the block moves, you must exploit Minecraft's internal update orders:

  • Tile Tick Priority: In Method 1, when a redstone-repeater and a redstone-comparator are powered simultaneously after a 2-gt delay, the game always processes the repeater first. This powers the main piston right before the comparator activates the cutoff piston.
  • Component Update Order: In Method 2, observers watching a line of powered-rail always fire from the furthest rail back toward the power source. By triggering the rail line near the slider piston, the distant observers power the slider blocks first. Because the main pistons are lowered to avoid remaining powered via quasi-connectivity from the observers, note-block updaters are placed above them to pass the block update downward before the last observer shifts the slider.

Tips & variations

  • Test Pulse Length with an Armor Stand: Place an armor stand on top of the block being pushed sideways by a sticky piston. A 2-gt pulse pushes the armor stand completely off the block, a 1-gt pulse nudges it slightly without it falling, and a true 0-tick pulse teleports the block so fast that the armor stand does not move at all.
  • Always Use Sticky Pistons for Instant Travel: While regular pistons can receive a zero-tick pulse, their pushed blocks will still take the full three game ticks to turn solid. Only a sticky piston can instantly teleport the first block attached to its face.
  • Alternative Update Orders: If you use a straight line of redstone-dust instead of rails, observers closest to the power source fire first. If you push a line of blocks with a piston, the blocks furthest from the piston head update first.
  • Repeating Repeater Priority: If two lines use two repeaters each to arrive on the same tick, the line whose first repeater is set to a higher delay increment will fire before the other.
  • Watch Out for Quasi-Connectivity: If your cutoff block moves away but the target piston stays extended or fails to zero-tick, check if the observer powering the cutoff block is accidentally powering the piston diagonally via quasi-connectivity.

Frequently asked questions

Why doesn't my piston activate at all when I trigger the circuit?
Your update order is likely inverted. If the cutoff piston moves the conductive block before the powering component fires, the block becomes non-conductive too early and the signal never reaches the target piston. Flip your rail input side or swap your repeater and comparator.
Can I use a Copper Bulb for a 1-game-tick delay to build zero-tick generators?
No. While Copper Bulbs originally had a 1-game-tick toggle delay during early snapshots, Mojang changed them to update instantly like note blocks. For a 1-gt delay, use scaffolding or leaf update chains instead.
Why do only the top pistons fire when I stack two rows of pistons behind the moving blocks?
Pistons require both power and a block update to trigger. If a piston is powered via quasi-connectivity from two blocks above without an adjacent instant updater—such as a note block, rail, bell, or moving block—it will not realize it has been powered before the zero-tick pulse ends.

Components used

More pulse limiter