-
Bug
-
Resolution: Fixed
-
None
-
1.19.0.27 Preview, 1.19.0.26 Beta, 1.18.0.24 Beta, 1.17.11 Hotfix, 1.17.10, 1.17.2 Hotfix, 1.17.41 Hotfix, 1.18.30, 1.18.31, 1.19.11 Hotfix
-
None
-
Creative
-
Confirmed
-
Windows
-
605958
Steps to Reproduce:
1. Find or make an area with a specific version of a block you'd like to replace and another version of the same block that you don't want to be replaced. ex) upside-down cobblestone stair and upright cobblestone stair
2. Execute a fill command with the coordinates of the location you had made/found and use a block state tag to select the one version of the block you would like to be replaced with another block of your choice. ex) /fill <from: x y z> <to: x y z> obsidian [] replace stone_stair ["upside_down_bit": true]
Observed Results:
What I found to happen was that both of the blocks got turned to obsidian even though it was only supposed to replace the upside-down one. The message that was shown after the execution of the command was "2 blocks filled".
Expected Results:
What I was expecting to happen was for it to only replace the block with the same block state value as input, leaving the other untouched.
- is duplicated by
-
MCPE-137199 Using the replace component of the /fill command with tiledata ignores data provided
- Resolved
- relates to
-
MCPE-168391 Block state predicates in commands do not work properly (unprovided states require default value)
- Open