The bug
Unspecified states in block-checking commands are treated as though you specified the default value. This is fine for block-placing commands, but for block-checking commands, it's problematic.
How to reproduce
1. Place some acacia stairs facing all four directions
2. Run this command:
/fill ~-5 ~-5 ~-5 ~5 ~5 ~5 stone replace acacia_stairs["upside_down_bit":false]Expected result
All stairs should be replaced with stone
Observed result
Only the west-facing stairs were replaced
Notes
This affects /execute if block as well. This is identical to MC-121690, which affected Java for a single snapshot in 2017. An equally hasty fix for bedrock would be much appreciated
Linked issues
is duplicated by 7
MCPE-168545
“button_pressed_bit” does not work without “facing_direction”
Resolved
MCPE-170392
Test for block states not working under experimental features
Resolved
MCPE-172162
/testforblock fails to detect Bell "toggled_bit".
Resolved
MCPE-174513
Using the "/testforblock" command to test for a pressed button does not work
Resolved
MCPE-178161
/testforblock cannot detect for open barrels
Resolved
2 more links
relates to 3
Comments 3
Now that block states have been enforced, this bug is now a bigger issue. Affects 1.19.73 and 1.20.0.21 Preview
I am experiencing the same issue:
This command does not detect the pressed button, unless I provide
facing_direction: