top of page

Command Blocks

This tutorial will teach you about the basics of command blocks. It is not in the creative menu and not obtainable in survival. To get one type /give @p command_block. It will be quicker if after you type "com" press tab and it will autofill. There are three types of command block. Impulse, chain and repeat. The one you just got is impulse. Place it down and open it up. You will see this.

There are 6 buttons and a text interface on the top. The button that says "0" we can ignore. If something doesn't work press the button try it again and tell me what it says. This is the command block output. This will also appear in chat. It will spam your chat so I would recommend typing /gamerule commandBlockOutput false. Like with give you can press tab to autocomplete after typing "com". Don't forget the last bit aswell. The done and cancel buttons (can also be activated by enter and escape respectively) are what you use to get outside the interface. Cancel will not save what you did since you last opened the command block. Done will save what you did. That leaves the button saying impulse and the button saying needs redstone. The button saying impulse will switch between the mode of your command block. Impulse, chain and repeating. For now just think of impulse as what is your chat. That leaves us with needs redstone. That button can be either needs redstone or always active. Needs redstone means it will power at when redstone is powering it. Always active means it is always active. For impulse always active is quite useless as it only activates once and that is when you first press done after making it always active.

​

Now onto chain and repeat. And we will talk about the middle button aswell. It goes with chain. First repeat. Repeat will run 20 times a second as long as its powered either by redstone if its on needs redstone or if it's always active. Now onto chain. This is a bit complicated. But basically it will run in the same game tick (1/20 of a second) as the starting command block. It has to start with an impulse or a repeat. I recommend always setting chain command blocks to always active. Then chain command blocks will only power if there is a command block pointing into them. You can tell by the arrows.

As you can see I set each command block to say their order. 4 doesn't run because there is no command block running into it. 5 doesn't run because even though 4 is pointing into it the command never runs.

​

Since the removal of /testfor /testforblock and /testforblocks conditional is pretty much useless as far as I know.

​

One final thing the text box is just like your chat. Except it doesn't need to ever type '/'. If you accidentally put them in it will work just less you have to type the better. Same thing with server consoles if you are using one of those.

 

This is the last tutorial on the basic level. I will link the first tutorial in intermediate. It is the magic carpet. It is fairly simple and is at the basic level. I just decided to put it in intermediate for grouping purposes.

bottom of page