After 1.21.70, when typing a /testforblocks command the command will not check any block state commands including facing_direction, button_pressed_bit, and all others.
Steps to Reproduce:
Place a wooden button facing up
Enter the following command: /testforblock <coordinates of the button> wooden_button ["button_pressed_bit"=true,"facing_direction"=1]
Observed Results:
The chat says “Successfully found the block at <coordinates>” even though the button is not pressed.
Before 1.21.70, it would say “The block at <coordinates> did not match the expected block state”.
Expected Results:
The chat should say “The block at <coordinates> did not match the expected block state”.
Linked issues
is duplicated by 12
MC-297419
The testforblock command is no longer able to tell the difference between block states. For example a pushed button, and an unpushed button
Resolved
MCPE-194285
The command does not check the condition for checking the button.
Resolved
MCPE-194496
/testforblock "button_pressed_bit" and/or "facing_direction" not working correctly after recent update
Resolved
MCPE-194746
The command /testforblock ignores blockstates
Resolved
MCPE-201864
Testforblock is not working properly
Resolved
Comments 3
I'm facing the same issue: the /testforblock command isn't working correctly after the Minecraft Bedrock 1.21.70 update. I heavily rely on it for activating various systems.
Specifically, the command is no longer detecting whether a button is pressed or not. For example, I use this command in a repeating, always active command block:
/testforblock ~ ~ 3 ~ stone_button [ "button_pressed_bit" = true ,"facing_direction" = 2 ]
This command used to identify when the button was pressed to activate a system. However, now it only detects the button itself, not its pressed state.
I reported the same issue in the next post 😂