If a command block does nothing, check four things in order: cheats and command blocks are enabled, the block is set to Always Active or is receiving redstone, the command works when typed in chat, and the chunk is loaded. The Previous Output box in the block shows the exact error.
Beginner Java Bedrock
Checklist
- Open the block and read Previous Output. It names the failure.
- Paste the same command into chat. If chat rejects it, fix the command.
- Confirm the type, condition and redstone setting.
- Confirm command blocks are allowed in this world.
- Stand within render distance to make sure the chunk is loaded.
Server settings
- Java server: set
enable-command-block=truein server.properties, then restart. The default is false. - Game rule: command blocks can be turned off with a game rule. It is commandBlocksEnabled on Bedrock and command_blocks_work on Java 1.21.11 and newer. Set it to true.
- Permissions: only operators in Creative mode can place or edit a block. Run
/op yournamefrom the console.
Block settings
- Needs Redstone, but nothing powers it. Add a button or switch to Always Active.
- Chain block not on Always Active. It then waits for its own signal.
- Arrow points the wrong way. A chain follows the arrow.
- Conditional by mistake. The block before it failed, so this one is skipped.
- Impulse block already powered. It runs only on a new signal. Turn the power off and on again.
The command itself
- @s used in a command block. A command block is not a player. Use @p or execute as.
- Wrong edition syntax.
/effect giveis Java,/effect @sis Bedrock. See the command table. - Old game rule name. Java 1.21.11 and newer use snake_case.
- No valid target. A kill or tp command with no match fails quietly in a conditional chain.
Tip Put a temporary say test block at the start of the chain. If it speaks and the next one does not, the problem is between them.
Chunk not loaded
Command blocks only run in loaded chunks. If you walk away, the block stops. Use a ticking area on Bedrock (/tickingarea add) or /forceload add on Java to keep a chunk active.
FAQ
Why is my command block not working?
The usual causes are command blocks disabled on a Java server, no redstone signal, a wrong edition syntax or an unloaded chunk.
How do I enable command blocks on a server?
Set enable-command-block=true in server.properties and restart the server.
What does Previous Output mean?
It is the last message the block produced, including error text, so it is the first thing to read.
Why does my chain command block not run?
It must be set to Always Active, its arrow must point onward, and the block before it must run.
Do command blocks work when I am far away?
Only if the chunk is loaded. Use /forceload on Java or a ticking area on Bedrock.
Checked by the Game Respawned editorial team against the current Java and Bedrock versions. Spotted something out of date? Tell us.