How to Craft / Obtain
Uses for this Item (Recipes Including This)
This item is not used as an ingredient in any known crafting recipes.
About
The chain command block is a specialized, indestructible variant of the standard command block in Minecraft, visually distinguished by its cyan coloration. Like all command blocks, it cannot be obtained, destroyed, or used in Survival mode without commands, making it a staple of multiplayer servers, Creative worlds, and custom map creation. It shares the same blast resistance as bedrock and is entirely immune to piston movement and fire damage. While impulse command blocks execute once when activated and repeating command blocks run every game tick, chain command blocks are engineered specifically to form sequential processing loops in conjunction with other command blocks.
In terms of placement and acquisition, chain command blocks can be obtained through the Creative inventory under the Operator Utilities tab if the Operator Items Tab setting is enabled in controls, or through commands such as give and setblock. Players can also copy an existing block with its internal data by pressing the pick block control combined with the Control key. Placing or breaking command blocks is strictly restricted to operator players in Creative mode. In Java Edition, the game rule command_blocks_work must be active, server.properties must have enable-command-block set to true, and op-permission-level must be configured correctly, while Bedrock Edition requires command blocks to be enabled within the world options.
When interacting with a chain command block through its graphical user interface, operators can configure various parameters including block type, conditional behavior, redstone activation requirements, and tick delays. By default, chain command blocks are set to Always Active, meaning they do not require external redstone power to function once placed, unlike impulse and repeating blocks which default to Needs Redstone. They also feature a conditional setting where a conditional chain command block executes its command only when the command block directly behind it has achieved a successful execution count greater than zero.
The primary operational mechanic of a chain command block is its ability to be triggered by a preceding command block that faces it. When any command block executes its command, it triggers any chain command block directly in its path to attempt execution during the same game tick. If the chain command block has been activated and meets any conditional requirements, it executes its stored command, updates its success count, and propagates the trigger to the next chain command block in the sequence, allowing complex multi-command logic systems to run simultaneously and deterministically in a single tick.
During execution, chain command blocks interact with success counts and output logging to help mapmakers debug their contraptions. The success count is an integer reflecting the last executed command, which can power a redstone comparator facing away from the block. Additionally, output messages indicating command success or failure are written to the Previous Output pane in the GUI and can be broadcast to chat or server logs depending on game rules. Certain administrative commands are restricted from being executed within any command block to maintain server security, and chain command blocks can utilize command text limits up to 32,500 characters while operating with permission level two in Java Edition or level one in Bedrock Edition.