Video Summary
In this video, I explain the three types of command blocks in Minecraft – Impulse, Repeat, and Chain – and how each one functions differently. I demonstrate how Impulse blocks execute commands once per redstone signal, Repeat blocks constantly execute commands, and Chain blocks execute conditionally based on the success of previous commands in a line. I also show how to disable command block output messages and explain the importance of proper arrow alignment for chain blocks to work correctly.
How To Use Command Blocks In Minecraft! (All Types) Chain, Impulse and Repeat!
Hey everybody, it’s UnderMyCap and welcome back to another video! Today I’m going to be explaining each function of a command block and going into depth on each one. If you’re familiar with my channel, you’ll know I like to do a whole bunch of command tutorials, so if you’re new, make sure to leave a like and subscribe to the channel! I’m doing this video to help my viewers understand how to use a command block, because a lot of my videos actually use command blocks. Without further ado, let’s get straight into it!
Redstone vs Always Active
First things first — in the command block settings, you have two options for activation: Needs Redstone and Always Active. When a command block is set to Needs Redstone, it requires a redstone signal to work. For example, when you click a button connected to the command block, a redstone signal is transmitted and the command executes. On the other hand, when set to Always Active, the command block will activate on its own without needing a redstone signal. It’s worth noting that on Always Active, the command will only execute once unless it is set to Repeat mode, in which case it will constantly run.
The Three Types of Command Blocks
Impulse Command Block
The Impulse Command Block is the most straightforward of the three. It only executes the command a single time per redstone signal. When you click the button, you’ll see it executes the command once successfully, which you can also see confirmed in the output. It’s great for one-time actions that you want to trigger manually.
Repeat Command Block
The Repeat Command Block works similarly to the Impulse block, except it repeats every single game tick. Instead of executing the command just once, it will constantly execute it for as long as it has a redstone signal — or indefinitely if set to Always Active. This makes it incredibly useful for commands that need to run continuously.
Chain Command Block
The Chain Command Block is probably one of the coolest command blocks in Minecraft, and while it might seem confusing at first, it’s actually really simple once you understand it. The Chain block is designed to sit at the end of a command line, and it’s important that the arrow on the Chain block lines up with the direction of the previous command block. If the arrows don’t line up, the command will not work. What the Chain block does is check whether the command before it was executed successfully — and this only works in conjunction with the Execute (XQ) command. If the execute command runs properly, it returns true, and the Chain block’s command will fire. If it doesn’t run properly, it returns false and the chain stops.
Conditional vs Unconditional
Conditional and Unconditional settings are found within the Chain command block and play an important role in how your command chains behave. Conditional means the command block will only execute if the previous command in the chain ran successfully. For example, I have a command block set to Conditional that displays particles and plays a sound — but only if I’m standing on a yellow block. When I’m not standing on the yellow block, nothing happens. The moment I step onto it, the particles and sound trigger perfectly. Unconditional, on the other hand, means the command block will always execute regardless of whether the previous command was successful. So even if the execute command hasn’t tested true, the unconditional block will still run its command.
Hiding Command Block Output Messages
One handy tip — if you find the command output messages that pop up on screen annoying or distracting, there’s a really simple way to get rid of them. All you need to do is use the game rule command and set commandBlockOutput to false. Once you do that, the messages will no longer appear on screen, which keeps things much cleaner, especially when working with Repeat command blocks.
Final Thoughts
And that’s basically a short tutorial on command blocks! One of my viewers actually suggested this video, so a big thank you for that. If you have any other video ideas, make sure to leave them in the comments below — I read through them all and love getting new ideas for content. Thank you so much for watching, don’t forget to subscribe, and I’ll see you in the next one!
If you’d prefer to watch the full video, you can check it out here: How To Use Command Blocks In Minecraft! (All Types)





