Testforblocks command doesn't work item detection in the storage block. (In the screenshot, the same block on the left and right of the command block and the same item inside the same space. The command block is detecting the testforblocks command whether the left and right blocks are the same.) Originally, after recognition, if the two blocks are the same, an electical signal is sent through the redstone comparator but there is no output. Please fix the bugs until the next version, thank you.
Linked issues
is duplicated by 2
Attachments
Comments 5
This seems kinda like a glitch that I posted about here MCPE-162293 and if it is based on the same premise then the steps would be to place two chests down and have them facing the same way with the same item inside then do "/testforblocks (first chest location) (first chest location) (second chest location)" but that's if the glitch still happens because I'm no longer in the beta/preview.
I found out by testing that the full release of the game doesn't have the glitch it's only the beta/preview.
This bug also occurs on xbox one, and it is likely due specifically to the fact that the game sometimes considers two separate non stackable items to be different items example a potion of strength brewed by hand is considered different from one pulled from the creative inventory
This can also apparently happen with swords but you need to advanced pick block the reference container and put either the container or the sword that was in the copy in the tested area
Ps trying to come up with the rules that this bug seems to follow is like trying to herd cats it feels extremely inconsistent but I think the rules that I have provided work at least in these two specific cases
I have no idea why an exact copy of something means it's incompatible and a non-exact copy means it is compatible when it comes to the swords, at the very least a crafted potion and a creative inventory potion being different makes sense. My guess for this issue is that it's another one of those sheared leaves and silk touch leaves being different type of bugs and it hasn't been noticed until now because it only affects non-stackable items and non-stackable items not being in the same stack is not a problem
Your report does not contain enough information to fully understand or reproduce the problem.
Please include a numbered list of steps along with the Observed and Expected results by Editing the Description above as shown here:
(add screenshots or video to help explain the issue)
This report has been temporarily closed as Awaiting Response. It will automatically reopen when you add information. Please follow the format shown and include all sections (steps, observed, expected). Reports that do not contain all of the requested information and complete steps to reproduce the issue may be closed as Incomplete. For more information please read the Bug Tracker Guidelines.
You may find this Report Creation Form helpful for any future reports you create.