Instant Repeater

Standard redstone repeaters introduce at least one redstone tick of delay every 15 blocks, which quickly adds up over long distances. An instant repeater (or instant wire) refreshes your signal strength with zero delay, letting you trigger distant contraptions or synchronized machines at the exact same tick. This guide covers classic piston instant repeaters, lag-reducing upgrades, spam-proofing, and low-lag powered rail alternatives.

Signal TransmissionAdvancedJava Edition
Instant Repeater video tutorial

Video: Different Instant Repeater Designs | Redstone Essentials #4 by amplitude

How to build it

  1. Build the Classic Dual-Piston Core

    At the end of a 15-block redstone dust line, set up the classic instant repeater (by Sydney600MC) using two sticky pistons, a solid block, and a redstone block. When the input line turns on, the first sticky piston pushes the redstone block to power the next 15-block line, while the second sticky piston controls the retraction so both rising and falling edges happen with zero delay.

  2. Pre-Power the Line to Reduce Dust Lag

    To prevent the redstone dust from changing between signal strength 0 and 15 (which causes heavy block updates), place a stationary redstone block above the start of the line on a transparent block like glass so it doesn't directly power the piston below. Route the dust down a solid block onto the main line so the wire constantly sits at signal strength 14 while idle.

  3. Connect the Pre-Powered Output

    When the instant repeater activates, its moving redstone block pushes one block closer to the main line, bumping the signal strength from 14 to 15. Because each dust along the line only changes its signal strength by 1 instead of 15, lag is significantly reduced.

  4. Add FallenBreath's Spam-Proofing (First Module Only)

    Rapidly toggling the input can cause the sticky piston to drop its redstone block and break the line. On the very first instant repeater in your chain, place an extra sticky piston next to the extended redstone block position and have it push an observer facing into that redstone block to send an immediate recovery update.

  5. Alternative 1: Ilmango's Powered Rail & BUD Line

    To avoid redstone dust lag altogether, replace the dust line with powered rails. At each repeater station, use a sticky piston quasi-powered (BUD-powered) by a redstone block above it, pushing a slime block attached to a redstone block and an extra solid block (which keeps the update order stable so the piston does not pulse endlessly).

  6. Chain the Powered Rail Modules

    When the BUD sticky piston receives a block update, it pushes the slime structure forward so its redstone block powers the next segment of powered rails. That rail line immediately updates the next BUD piston down the chain, transmitting the signal instantly.

  7. Alternative 2: OneTickPulse's BUD-Rail Repeater

    For a spam-resistant rail design (1.13+), place a note block with redstone dust on or next to it and a detector rail beside the dust to redirect it. The powered rail line remains in a BUD-powered state because the redirected dust does not update the rail directly.

  8. Install the Observer and Detector Rail Reset

    At the end of the BUD-powered rail line, face an observer into a sticky piston that pushes the detector rail. When the rails receive an update and turn off in a chain reaction, the observer fires the sticky piston to shift the detector rail, allowing the dust to re-power the note block and rail line before resetting.

How it works

Normal repeaters take at least 1 redstone tick (0.1 seconds) to refresh a signal. Instant repeaters bypass this by using block retraction and zero-tick piston mechanics or instant rail update chains:

  • Classic Piston Design: In Java Edition, a sticky piston starts moving its block the exact game tick it is unpowered, while extending takes time unless zero-ticked. By combining two sticky pistons, a solid block, and a Block of Redstone, both turning the line ON and turning it OFF immediately shift the redstone block to update the next wire segment in the same tick.
  • Signal Strength 14 Optimization: Redstone dust creates block updates every time its signal strength changes. Keeping the line pre-powered at strength 14 means toggling the circuit only shifts each dust by 1 level (14 to 15), cutting lag drastically.
  • Powered Rail Update Lines: Powered rails propagate their ON/OFF state changes along a 9-rail limit instantly and create far fewer block updates than redstone dust. Pairing rails with quasi-connectivity (BUD) pistons or redirected dust around a Note Block and Detector Rail transmits updates across massive distances in a single tick.

Tips & variations

  • Redstone Lamps Have Built-in Turn-Off Delay: If you test your instant wire with a Redstone Lamp, it will turn on instantly but take 2 redstone ticks to turn off. That delay comes from the lamp itself, not the repeater.
  • Only Spam-Proof the First Module: You only need to attach the extra sticky piston and observer stabilizer to the very first instant repeater in a chain; every module after it will automatically receive clean signals.
  • Watch Your Spacing on BUD Designs: Because Ilmango's rail design relies on quasi-connectivity (BUD powering), building two lines too close together will cause one line's updates to accidentally trigger the neighbor.
  • Java Edition Exclusive: All three designs rely on Java-specific mechanics (sticky piston block dropping, zero-tick chaining, quasi-connectivity, and instant rail update order) and will not work in Bedrock Edition.

Frequently asked questions

Why does my Redstone Lamp take a moment to turn off at the end of an instant wire?
Redstone lamps always have a hardcoded 2-redstone-tick delay when turning off, regardless of how fast the power is removed. The instant repeater itself is still turning off with zero delay.
Why does the classic instant repeater break when I spam the lever?
Rapidly pulsing the input causes the sticky piston to spit out its redstone block and fall out of sync. Adding the observer and sticky piston stabilizer to the first repeater forces an update that prevents it from breaking.
Why use powered rails instead of redstone dust for instant wires?
Redstone dust produces a large number of block and lighting updates every time its signal strength changes, which causes lag over long distances. Powered rails produce far fewer updates while still transmitting changes instantly.
Do these instant repeaters work in Minecraft Bedrock Edition?
No. These designs depend on Java Edition piston update order, sticky pistons dropping blocks on short pulses, and quasi-connectivity (BUD powering).

Components used

More instant wire