Hey everybody, it’s Under My Cap, and welcome back to another video! Today, I’m going to be explaining each function of a command block and going in-depth on each one. If you’re familiar with my channel, you know that 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 creating this video to help you—my viewers—understand how to use a command block, because many of my videos use one. Without further ado, let’s get straight into this. As you can see, I have two command blocks here. Basically, in the command block, you have this button. It makes sense: if the command block is set to “Needs Redstone,” it will require a redstone signal to work. When I click the button, a redstone signal is transmitted to the command block, and it displays “Hello.” On the other hand, with “Always Active” enabled, the command will only activate once and will remain active after that. As you can see, when I turn “Always Active” on, the command executes, but it only does it once. If I had it set to “Repeat,” it would continuously say “Hello.” Because it’s always active, it doesn’t need a redstone signal. Now, if we come over to the command blocks here, we can talk about each individual one. The impulse command block executes a single impulse of redstone. When I click the button, it executes the command only once. You can see that it executes successfully, and this is reflected in the output. The next command block operates similarly, but it repeats every single tick. Instead of executing the command just once like the impulse block, the “Repeat” block will continuously execute the command. When I do this, you can see it activates multiple times for the duration of the button click. If it’s constantly active, it will continue to do this. One thing to keep in mind: if you don’t like seeing these messages pop up, it’s easy to get rid of them. Just do “Game Rule,” then “Command Block Output,” and set that to false. Now, whenever we hit the button, the output message won’t display anymore, which is really cool. Next, we have the chain block. This block can be a bit confusing at first, but it’s actually quite simple once you understand it. The chain command block is one of the coolest commands in Minecraft. At the moment, it doesn’t do much because we need to set it up in a chain, which I’ve done over here. A chain command block works off the end of a command line. If the command block is pointing this way, you want to place the chain block so that the arrow is lined up. If the arrows don’t line up, the command won’t work. A chain command block checks if the command before it was executed successfully. This only works with the execute command. For example, I have an execute command here. If it works, it means that the command in front of it—the conditional command block—was successful. If you want to learn more about the execute command, I have a link in the description and in the info card for my execute command video. Conditional and unconditional formatting can be set in this block. This setting is only available for chain command blocks because it relies on the conditional and unconditional commands. Please note that this only works with execute commands; if an execute command does not run properly, it will result in false, and if it does run successfully, it will result in true. For example, I have a command block set to conditional, and it only displays a particle effect if I’m standing on a yellow block when I click the button. Initially, when I click it, nothing happens because I’m not standing on the yellow block. However, as soon as I stand on it, you see that I get the particle effect along with the sound from the conditional block. Now, you’re probably wondering, “Oh, that’s pretty simple,” and yes, it is! The other mode is also straightforward. Unconditional means that the command will always go through these two command blocks, regardless of whether I’m standing on the yellow block. If I click it, you’ll hear the sound playing through the conditional block, but you’ll notice that the execute command hasn’t registered true, meaning that the block isn’t checking anything; it’s just relying on the command block output. Please note that I’ve set this video to “Always Active.” You want this always active because the command block will only work if it has redstone power. You can place it next to a redstone block or something similar, but if there is no redstone, it won’t work. So, that’s basically a quick command tutorial on the command block. One of my viewers suggested this video, so if you have any other ideas, make sure to leave them in the comments below. I will read through them and potentially gather more video ideas. Thank you so much for watching, and I can’t wait to see you in the next video! Don’t forget to subscribe, and see you later!