*步骤1*:我放了一个大箱子
[media]Step2:Run command "/clone ~~~~ 1~ ~~1"
[media]Step3:Run command "/testforblocks ~~~~ 1~ ~~1"
then feedback shows they are not identical !
[media]
Other trials in developer version:
[media][media]
BUT,when I run “/clone ~~~~ ~~~1 ~3~~"~:
[media]then run “/testforblocks ~~~~ ~~~1 ~3~”
[media]The feedback shows they are identical now!
To compareed the block debug window,I infer when the command(testforblocks) runs ,it might contrasted the “pairx” and “pairz”,so if the tow large chests‘ position x and z are same ,command testforblocks run successfully.BUT,if their position x and z are not same ,it cause the “pairx”and “pairz” are not identical ,the result shows the command runs abnormally.
BUT ,When i destroyed a block one of a large chest then place a chest back ,which makes the "pairlead" blockdata changed.
[media][media]、
[media][media]
"pairlead"blockdata situations:
0 1
1 0
then I run testforblocks
[media][media]
They are not identical AGAIN!
Suggested solutions:
When testforblocks runs ,make sure the “pairx”, “pairz”and "pairlead" blockdata are ignored.**
Seems like this is caused by
pairx
/pairz
block data. To fix that bedrock should implement large chests like java does, with aleft
/right
block state. The current implementation causes other issues too like MCPE-44173, and makes chest placement awkward