A repeating command block runs its command repeatedly while its activation conditions are met.
Quick answer
Check the Java or Bedrock edition, permission level, and every command argument. Run a harmless test before changing a main world.
What to do
Work through these checks in order. Stop if a menu, command, or world state differs from the conditions described.
- Confirm your Minecraft edition and release, then identify the world, device, or server involved.
- Obtain the block with appropriate command permission and place it in a test world.
- Set the repeat and redstone conditions deliberately, then use a harmless command to confirm its rate.
- Check the result in the game. If it differs, record the exact error or menu label and compare the official source for your version.
Edition and version differences
Command names, selectors, and permissions can differ between Java and Bedrock or change after an update. Custom server commands need their own documentation.
If the result differs
Compare the current screen or error text with the conditions above. Check the Java or Bedrock edition, permission level, and every command argument. Run a harmless test before changing a main world. Change one variable at a time so you can tell which step made a difference.
Official sources and version scope
Examples are based on the original BlockGuide research snapshot dated 2026-10-12. Check the current edition and release before changing a live world.