Skip to main content

Command blocks

There are 3 different types of command blocks:

Impulse, Executes command once!

Repeating, Executes command repeatedly!

Chain, Executes command when triggered by another command block!

What are command blocks?​

Command blocks are like chat commands stored in block data, useful for automatic running, and linking of commands. Command blocks are obtained either through the /give @s minecraft:command_block or operator tab configured in accessibility settings.

Usual use cases

Usually minecraft commands are used in servers, adventure maps, demo scripts, or storage of commands.

Basic Configuration​

Before Use

Make sure the gamerule /gamerule command_blocks_work true is set to true.
If on a server make sure enable-command-block = true in the server.properties file.

When you configure a command block you have 3 options to choose from, the first one is the command input, the second one is the redstone condition, and the third one is the command block type.

Command input​

This field accepts any string input with or without the / symbol.

Redstone condition​

This field has 2 options, Needs Redstone and Always Active.

Conditions​

This field has 2 options, Conditional and Unconditional

Command block type​

This field has 3 options, Impulse, Repeating, and Chain.

Preview of UI​

large-image

Configuration​

As already known command blocks allow for storage of commands and these conditional statements like always active or Unconditional. With these we can stack command blocks and Configure command blocks to build off each other.
The most common configuration of command blocks is:

- Chain command block (Unconditional , Above repeating command block)
- Repeating command block (Always Active , Below pointing to chain command block)

Conditional VS Unconditional

Conditional command blocks activate only if the previos command returns true on a command, Unconditional commands activate without the need of another command use.

Limitations​

Usually minecraft command blocks and datapacks aren't too different on the ideals, but a huge issue with command blocks is its command execution is positioned where the block is. This means that command blocks can't execute a command outside of a players render distance.
There is also a limitation with running certain commands only reserved for datapacks like /function and /schedule commands.
Timing with command blocks are also tricky as the blocks being used have 0 tick and 1 tick mechanisms acting all as 1 tick mechanisms.

Check out here for more information on commands of minecraft!

Reference​

Information:
https://www.youtube.com/watch?v=I6gO7ZCoYeg
https://minecraft.wiki/w/Command_Block

Assets:
https://minecraft.wiki/images/BlockSprite_command-block.png?e7078
https://minecraft.wiki/images/BlockSprite_chain-command-block.png?0afa8
https://minecraft.wiki/images/BlockSprite_repeating-command-block.png?1dad0
https://minecraft.wiki/images/thumb/Command_Block_GUI.png/800px-Command_Block_GUI.png?fb024
https://minecraft.wiki/images/thumb/Repeating_Command_Block.gif/150px-Repeating_Command_Block.gif?7ab3a
https://minecraft.wiki/images/thumb/Chain_Command_Block.gif/150px-Chain_Command_Block.gif?7c365
https://minecraft.wiki/images/Impulse_Command_Block.gif?fb024