-
Bug
-
Resolution: Unresolved
-
None
-
1.20.10.20 Preview, 1.19.80.21 Preview, 1.19.70, 1.19.81 Hotfix, 1.20.0, 1.20.15 Hotfix, 1.20.51 Hotfix, 1.20.62 Hotfix, 1.21.43 Hotfix
-
None
-
Confirmed
-
Windows
-
997772, 1133402
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
- is duplicated by
-
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
-
MCPE-179147 "Button_pressed_bit" and "Facing_direction" don't work
- Resolved
- relates to
-
MCPE-171919 /testforblock fails to detect bed block state "occupied_bit"
- Open
-
MC-121690 Not providing block states will make the game test for the defaults, instead of ignore the states
- Resolved
-
MCPE-133360 /fill replace doesn't differentiate blockstates
- Resolved