-
Bug
-
Resolution: Unresolved
-
None
-
1.17.2 Hotfix, 1.18.12 Hotfix, 1.20.81 Hotfix
-
None
-
Confirmed
-
Multiple
-
581399
步骤1:我放了一个大箱子
Step2:Run command "/clone ~~~~ 1~ ~~1"
Step3:Run command "/testforblocks ~~~~ 1~ ~~1"
then feedback shows they are not identical !
Other trials in developer version:
BUT,when I run “/clone ~~~~ ~~1 ~~3~":
then run “/testforblocks ~~~~ ~~1 ~~3~”
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.
、
"pairlead"blockdata situations:
0 1
1 0
then I run testforblocks
They are not identical AGAIN!
Suggested solutions:
When testforblocks runs ,make sure the “pairx”, “pairz”and "pairlead" blockdata are ignored.**
- is duplicated by
-
MCPE-181630 The subcommand "if|unless blocks", which is a part of "/execute", run abnormally
- Resolved
- relates to
-
MCPE-44173 Cloning two single chests from source creates double chest at destination
- Open
-
MCPE-80815 Chests placed with data don't combine until relogging
- Reopened