Let's say you were to place down an armor stand and name it TEST then use /setblock to place a chest on its location then place another chest somewhere nearby facing the same direction and put the same item in the same slot of both chests then run "/execute as @e[type=Minecraft:armor_stand,name="Crafting Table"] at @e[type=armor_stand,name="TEST"] if blocks ~~~ ~~~ (second chest location) all run say §aYes" you will get the error message shown in the picture and this glitch doesn't happen outside the beta/preview
Linked issues
duplicates 1
Attachments
Comments 3
Yes this does seem similar to MCPE-161257 and I think the if blocks statement in the /execute command is the same as /testforblocks but MCPE-161257 is close now due to not having the steps to reproduce the bug.
Thank you for your report!
We're tracking this issue in MCPE-161257, 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
📓 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.
This seems related to MCPE-161257, as both commands behave similarly. It could be a duplicate for that very reason however, as a different means to the same end.