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
A command block is an indestructible block that can execute commands across multiplayer servers, Creative worlds, and custom maps, since it cannot be obtained, destroyed, or used in Survival mode without commands. There are three primary types of these blocks including the impulse command block which executes only once when activated, the chain command block which executes every time it is triggered, and the repeating command block which executes every game tick as long as it remains activated. Across both Java and Bedrock editions, command blocks can be obtained using various commands such as /give or /setblock, through the Creative inventory under Operator Utilities when enabled, or by using pick block while holding Control to copy internal data. These blocks are completely flammable, possess the same blast resistance as bedrock, and cannot be mined in Survival mode.
When activated by redstone power, a command block executes its commands with permission levels equivalent to level 2 in Java Edition or level 1 in Bedrock Edition, allowing specific command executions by players who might otherwise lack general permissions. To ensure proper functionality, the game rule command_blocks_work must be enabled in Java Edition, while Command Blocks Enabled must be activated in Bedrock Edition world options, and placement or destruction is restricted to operator players in Creative mode. Modifying a command block requires interacting with its graphical user interface in Creative mode with cheats enabled, and in Java Edition, the server property files must have enable-command-block set to true and op-permission-level set to 2 or higher. The console command text pane supports up to 32,500 characters, allows command entry without a forward slash, and provides tab completion alongside target selector tips in Bedrock Edition.
The command block interface also features a Previous Output pane displaying the success or failure message of the last executed command, which can be toggled on or off to optimize memory and storage on worlds with heavy clock usage. The block type can be modified between impulse, chain, and repeat variants, which correspond distinctively to orange, cyan, and purple colors. Conditional behavior can be adjusted between conditional mode, where execution requires the preceding block behind it to yield a success count greater than zero, and unconditional mode, which executes regardless of the previous block. Activation requirements can likewise be configured between needing redstone power or remaining always active, while Bedrock Edition provides additional settings such as execution on first tick, tick delays, hover notes, and cancellation controls.
Command blocks function as redstone mechanisms and can be activated by adjacent active power components, powered blocks, comparators, repeaters, or powered redstone dust pointing toward them, while Bedrock Edition responds to redstone signals specifically on even-numbered consume ticks. Upon activation, an impulse command block executes its command once, a repeat command block executes once every game tick until deactivated, and a chain command block waits until triggered by another executing block. When executing, the block updates its success count and checks conditional parameters against the block behind it, while special placement rules determine whether newly cloned or placed command blocks execute immediately based on their redstone configuration and block updates.
Chain command blocks introduce a structured chaining mechanism where any executing block facing a chain command block will trigger it to attempt execution in the same game tick. When triggered, an activated chain command block checks its conditional requirements and execution status to prevent infinite loops, running its command simultaneously in the order they are chained if all criteria are met. In Java Edition, chain command blocks can even execute multiple times in the same tick if UpdateLastExecution is disabled, whereas Bedrock Edition supports configured tick delays before execution occurs. Success counts are updated accordingly during these chained operations and can power external redstone comparators with signal strengths ranging from 0 to 2,147,483,647.
Beyond internal execution mechanics, command blocks output descriptive success or failure messages to the Previous Output pane, server logs, and chat windows unless suppressed by game rules like commandBlockOutput or logAdminCommands. Standard player-name prefixes in chat are replaced with the @ symbol in Java Edition or an exclamation mark in Bedrock Edition, or by custom names if the command block was previously renamed in an anvil. However, security restrictions prevent command blocks from executing sensitive server administration commands such as banning, stopping, reloading, or managing operator lists. An amusing easter egg involves entering the case-insensitive command Searge without a slash, which sets the previous output to a specific reference string and yields a success count of one.
Command blocks maintain total physical permanence within the game world by refusing to be moved by pistons or sticky pistons, and they store extensive block entity data across Java and Bedrock editions. Their robust configuration options, flexible conditional checking, and multi-edition compatibility make them the cornerstone of advanced map making and server automation. Whether handling simple item distributions or complex multi-tick logic circuits, command blocks provide map creators with precise programmatic control over the game environment.