There are some commands (in CM blocks) that fail to work consistently when there are multiple similer command blocks activated at the same time. The CM blocks that fail to work can be reset by simply changing the CM block type (ex: from reapeat to chain and back to reapeat), however this action will make other CM blocks around it stop working.
Steps to reproduce:
This bug can be replicated most easily with repeat command blocks set to always active. I was able to reproduce this bug by using rows of command blocks set with the command [execute @a ~~~ testforblock ~-1 quartz] and stepping on a quartz block.
Observed result:
Some of the CM blocks will fail to activate while others with the same command will activate.
Expected result:
All command blocks should still be working.
Note
I have tested this bug with multiple different commands and only a few of them produce this bug. It is most prominent with the testfor/testforblock command.
Comments 3
Cleaning up old tickets: This ticket had been set to 'Awaiting Response', but has not received a response from the reporter (~3 months+) so is being closed as Incomplete. If you feel this is still a valid issue then please comment, or create a new ticket following the Issue Guidelines which includes steps to reproduce the problem.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki
The issue has been reported with repeating command blocks (with specific commands) fails to work suddenly and/or reopening the world ^^
This is a self-prescribed hotfix done to my world:
-Use /execute commands when available (didn't run into many problems with /execute compared to /tp or /testfor)
-Change the repeating command block to 'Needs Redstone'
-Power the command block with a redstone_block
So far, the world has been running much smoother. Most of the faults now are with my own coding. Hope this works!