An impulse command block loops by connecting it to a repeating command block and a chain command block in the right order

A single impulse command block runs its command once when powered. To make it repeat, you need to chain it to a repeating command block that stays powered, then add a chain command block after that. The repeating block triggers the impulse block over and over, creating a loop that runs the same command many times per second until you break the power or remove the blocks.

This setup is different from using a repeating command block alone. A repeating block runs continuously on its own once powered, but an impulse block needs that external trigger. By combining them, you get precise control over when the loop starts and stops, and you can run commands in a specific sequence.

Key Takeaways

  • Place a repeating command block, then an impulse command block facing it, then a chain command block after the impulse to create a working loop.
  • The repeating block must stay powered by redstone (a lever, button, or redstone dust) for the loop to run continuously.
  • Command block type matters: impulse runs once per trigger, repeating runs every tick when powered, and chain runs only when the block before it executes.
  • You can see the loop working by watching the command blocks light up in sequence, or by checking the game output log for repeated command results.

Setting up the three-block chain

Start by placing a repeating command block. This is the engine of your loop. Right-click it, set the type dropdown to "Repeating" if it is not already, and put any command in it—even just say test to start. Leave the redstone requirement as "Needs Redstone" for now.

Next, place an impulse command block directly in front of the repeating block, facing the same direction. Right-click it and set the type to "Impulse". Put the command you actually want to loop in this block. This is where your real work happens.

Finally, place a chain command block in front of the impulse block. Set its type to "Chain" and set the redstone requirement to "Always Active". You can leave the command blank or put a second command here if you want something to run after the impulse command each cycle.

Powering the loop with redstone

The repeating block needs a constant redstone signal to keep firing. Place a lever next to it or run redstone dust from a power source to one of its sides. When you flip the lever on, the repeating block activates and begins firing every game tick (20 times per second). Each time it fires, it triggers the impulse block in front of it.

The impulse block then runs its command once per trigger, and the chain block runs after that. The whole sequence repeats as long as the lever stays on. If you want the loop to start automatically when the world loads, use a redstone clock or a command block setup that powers itself, but a lever gives you manual control and is easier to test with.

Do not power the impulse or chain blocks directly—they get their signal from the repeating block's execution, not from redstone. If you accidentally put redstone on them, they may behave unpredictably.

Understanding command block types and what each one does

An impulse command block (usually orange) runs its command exactly once each time it receives a trigger. It does not run again until it is triggered again. This makes it useful for one-time actions or for actions that should happen in response to something specific.

A repeating command block (usually blue) runs its command every single game tick as long as it has redstone power. It does not wait for a trigger—it just keeps going. In a loop setup, this block is what creates the repetition.

A chain command block (usually green) runs only when the command block directly before it in the chain executes successfully. It does not need redstone power if the block before it is powered. Chain blocks let you run multiple commands in sequence without gaps.

Testing your loop and reading the output

Turn on the lever powering your repeating block. You should see the command blocks light up in sequence—the repeating block glows, then the impulse block, then the chain block. If they light up in order very quickly, your loop is working.

Open the chat window and look at the output. If your impulse command is say test, you should see "test" appear in the chat over and over, many times per second. If you see it only once, the loop is not triggering the impulse block repeatedly—check that the repeating block is actually powered and that the impulse block is facing the right direction.

If nothing happens, verify that the repeating block has redstone power by looking for a small redstone particle effect or by checking that the lever is actually on. Also confirm that you are in Creative mode or that command blocks are enabled in your world settings.

Common mistakes that break the loop

Placing the blocks in the wrong order is the most common error. The repeating block must come first, then the impulse block in front of it, then the chain block in front of that. If you reverse the order or skip a block, the loop will not work.

Forgetting to power the repeating block is another frequent problem. The repeating block needs a constant redstone signal. A lever, a button held down, or redstone dust connected to a power source all work. A button that you click once will not keep the loop running—it powers for only a moment.

Setting the chain block to "Needs Redstone" instead of "Always Active" can also break the loop. Chain blocks should almost always be set to "Always Active" so they run whenever the block before them executes, without needing their own redstone signal.

Adjusting the loop speed or stopping it

The loop runs at the game's tick rate, which is 20 times per second in normal Minecraft. You cannot slow it down without adding delays. To add a delay between repetitions, use the /schedule command or add delay ticks to your command block settings (if your version supports it). Some versions let you set a delay value in the command block interface itself.

To stop the loop, flip the lever off. The repeating block will stop firing when ready, and the impulse and chain blocks will stop triggering. You can turn it back on anytime by flipping the lever again.

If you want the loop to run only a certain number of times, you can use a scoreboard counter inside the impulse block's command to track repetitions and then disable the redstone signal once a target number is reached. This requires more advanced command knowledge but gives you precise control.

Frequently Asked Questions

Can I use just an impulse block and a repeating block without the chain block?

Yes. The chain block is optional—it just gives you a place to run a second command in the sequence. If you only need one command to repeat, the impulse and repeating blocks alone will work. The repeating block triggers the impulse block, and that is the whole loop.

Why does my impulse block not light up when the repeating block is powered?

The impulse block needs to be facing the repeating block so it receives the trigger signal. Check that the impulse block's input side (the side with the arrow or dot) is pointing toward the repeating block. If it is facing the wrong way, rotate it or place it again in the correct orientation.

What happens if I power the impulse block directly with redstone instead of letting the repeating block trigger it?

The impulse block will run once when the redstone signal turns on, and once when it turns off. It will not loop continuously. You need the repeating block to provide repeated triggers, not direct redstone power, for a true loop.

Can I make the loop run slower than 20 times per second?

Yes, but it requires adding delay. Some command block versions have a "Delay" field where you can set ticks to wait before executing. Alternatively, use the /schedule command inside your impulse block to delay the next command. Without a delay setting, the loop will always run at the game's tick rate.

Do I need to be in Creative mode for command blocks to work?

Command blocks are a Creative mode feature by default. In Survival mode, you must enable command blocks in the world settings before you can place or use them. Once enabled, they work the same way in both modes.