What Is Redstone Torch Burnout?
A redstone torch normally acts as a signal inverter: it outputs power level 15 while its attachment block is unpowered (power level 0), and turns off (power level 0) when that block is powered to levels 1 to 15. However, if a circuit forces the attachment block to power and depower in a rapid loop, the torch cannot keep toggling forever.
When pushed past its speed limit, the torch experiences burnout. It plays a hissing sound similar to an extinguished fire, produces a smoke particle, and shuts off completely. This is not permanent damage—there is no limit on how often a single redstone torch can burn out.
Exact Burnout & Recovery Rules
A redstone torch takes 1 redstone tick (2 game ticks, or 0.1 seconds barring lag) to change state, and it usually does not respond to 1-tick fluctuations of power. The game tracks how frequently each torch toggles:
- Triggering Burnout: A torch burns out when it is forced to change state more than eight times in 60 game ticks (three seconds, barring lag).
- Cooldown Condition: While burned out, the torch stays inactive and ignores attempts to change its state until the number of state changes recorded in the last 60 game ticks drops to fewer than eight.
- Re-activation: Once the cooldown condition is met, the torch turns back on when it receives a block update (an adjacent block changing its state) or a redstone update that would not normally deactivate the redstone torch.
Step-by-Step Burnout Demonstration
You can observe redstone torch burnout in a few seconds with a tiny feedback loop:
- Place any full solid opaque block on the ground.
- Attach a redstone torch to one side of that block.
- Place a second full solid opaque block directly above the redstone torch. Because an active torch strongly powers a full solid opaque block directly above it to power level 15, this top block is now strongly powered.
- Place redstone dust on top of the first block (the attachment block).
What happens: The torch powers the block above it, which powers the adjacent redstone dust, which powers the attachment block and turns the torch off after 1 redstone tick. Turning off unpowers the top block and dust, turning the torch back on. This 1-tick self-loop toggles the torch more than eight times inside 60 game ticks, causing it to hiss, smoke, and burn out.
How Players Use and Exploit Burnout
Although burnout stops infinite 1-tick loops from running continuously, builders can use its predictable behavior in compact contraptions:
- Quick Pulse Bursts: A self-powering torch loop rapidly fires a short burst of pulses into an adjacent mechanism component (such as a dropper, dispenser, note block, piston, or redstone lamp) and then automatically stops itself after burning out.
- Block Update Detectors (BUDs): Because a cooled-down torch waits until an adjacent block changes state before relighting, a burned-out torch loop can act as a simple sensor that fires a burst of pulses whenever an adjacent block updates next to the torch.
- Self-Sustaining Burnout Clocks: By pairing multiple burnout torches so that one torch's state change gives an update to a cooled-down neighbor, players can create compact, fast-pulsing clocks.
Common Mistakes and How to Avoid Them
- Accidental Feedback via the Top Block: Beginners often forget that a redstone torch strongly powers a full solid opaque block directly above it to power level 15. If redstone dust next to that upper block feeds back into the torch's attachment block, the torch will rapidly cycle and burn out.
- Waiting for Automatic Relighting: If a single burned-out torch sits in complete isolation, it may appear permanently off even after three seconds have passed. Remember that after the 60-game-tick window drops to fewer than eight state changes, it still requires an adjacent block update or redstone update to wake up.
- Too Little Delay in Torch Clocks: A 1-tick torch loop will always burn out. To build a continuous, non-burning torch clock, add delay (for example, using redstone repeaters or chaining more torches) so that the torch does not change state more than eight times in 60 game ticks.
