MCPE-133660testforblocks shows not identical when testzone includeing large chest or large trapped chest although they are identical
步骤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.**
Linked Issues
Attachments16
Created Issue:
testforblocks shows not identical when testzone includeing large chest or large trapped chest although they are identical
步骤1：我放了一个大箱子
Step2:Run command "/clone ~~~ 1~ ~~~1"
Step3:Run command /testforblocks ~~~ 1~ ~~~1"
then feedback shows they are not identical
Attachments3
步骤1：我放了一个大箱子
Step2:Run command "/clone ~~~ 1~ ~~~1"
Step3:Run command "/testforblocks ~~~ 1~ ~~~1"
then feedback shows they are not identical !
步骤1：我放了一个大箱子
Step2:Run command "/clone ~~~ 1~ ~~~1"
Step3:Run command "/testforblocks ~~~ 1~ ~~~1"
then feedback shows they are not identical !
Other try in developer version
![[Mod] tryashtar](../../../data/avatars/users/41963.png){kind=small}
步骤1：我放了一个大箱子
Step2:Run command "/clone ~~~ 1~ ~~~1"
Step3:Run command "/testforblocks
~~~ 1~ ~~~1"then feedback shows they are not identical !
Other try in developer version
步骤1：我放了一个大箱子
Step2:Run command "/clone ~~~ 1~ ~~~1"
Step3:Run command "/testforblocks ~~~ 1~ ~~~1 "
then feedback shows they are not identical !
Other try in developer version：
BUT,when I do this：
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”,under these circumstances 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.
步骤1：我放了一个大箱子
Step2:Run command "/clone ~~~ 1~ ~~~1"
Step3:Run command "/testforblocks ~~~ 1~ ~~~1 "
then feedback shows they are not identical !
Other try in developer version：
BUT,when I do this：
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”,under these circumstances 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.
步骤1：我放了一个大箱子
Step2:Run command "/clone ~~~ 1~ ~~~1"
Step3:Run command "/testforblocks ~~~ 1~ ~~~1 "
then feedback shows they are not identical !
Other try in developer version：
BUT,when I do this：
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 DESTORY AND PLACE THE CHEST AGAIN BUT CLONE (it makes the "pairlead"blockdata not same)
"pairlead"blockdata situations:
0 1
1 0
then I run testforblocks
They are not identical AGAIN!
Suggested solutions：
When testforblocks runs ，make sure ignore the “pairx”, “pairz”and "pairlead" blockdata 。
步骤1：我放了一个大箱子
Step2:Run command "/clone ~~~ 1~ ~~~1"
Step3:Run command "/testforblocks ~~~ 1~ ~~~1 "
then feedback shows they are not identical !
Other tr
yin developer version：
BUT,when I do this：
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 DESTORY AND PLACE THE CHEST AGAIN BUT CLONE (it makes the "pairlead"blockdata not same)
"pairlead"blockdata situations:
0 1
1 0
then I run testforblocks
They are not identical AGAIN!
Suggested solutions：
When testforblocks runs ，make sure ignore the “pairx”, “pairz”and "pairlead" blockdata 。
步骤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 do this：
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 DESTORY AND PLACE THE CHEST AGAIN BUT CLONE (it makes the "pairlead"blockdata not same)
"pairlead"blockdata situations:
0 1
1 0
then I run testforblocks
They are not identical AGAIN!
Suggested solutions：
When testforblocks runs ，make sure ignore the “pairx”, “pairz”and "pairlead" blockdata 。
步骤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 do this：
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 DESTORY AND PLACE THE CHEST AGAIN BUT CLONE (it makes the "pairlead"blockdata not same)
"pairlead"blockdata situations:
0 1
1 0
then I run testforblocks
They are not identical AGAIN!
Suggested solutions：
When testforblocks runs ，make sure ignore the “pairx”, “pairz”and "pairlead" blockdata 。
步骤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 DESTORY AND PLACE THE CHEST AGAIN BUT CLONE (it makes the "pairlead"blockdata not same)
"pairlead"blockdata situations:
0 1
1 0
then I run testforblocks
They are not identical AGAIN!
Suggested solutions：
When testforblocks runs ，make sure ignore the “pairx”, “pairz”and "pairlead" blockdata 。
步骤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 ,W
HEN I DESTORY AND PLACE THE CHEST AGAIN BUT CLONE (itmakes the "pairlead"blockdatanot same)
"pairlead"blockdata situations:
0 1
1 0
then I run testforblocks
They are not identical AGAIN!
Suggested solutions：
When testforblocks runs ，make sure
ignorethe “pairx”, “pairz”and "pairlead" blockdata。
步骤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.**
![[MCQA] v-weszaj](../../../data/avatars/users/18941.svg){kind=small}
is duplicated by
![[Bot] Arisa](../../../data/avatars/users/43007.png){kind=small}
Thank you for your report!
We're tracking this issue in MCPE-133660, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
Seems like this is caused by pairx/pairz block data. To fix that bedrock should implement large chests like java does, with a left/right block state. The current implementation causes other issues too like MCPE-44173, and makes chest placement awkward