When using the command /testforblock, it ignores the block states
So for example, when typing in the command
/testforblock ~ ~ ~ stone_pressure_plate ["redstone_signal"=1]
Even if the pressure plate isn’t activated meaning the block state is wrong, the command will say the block is found
To recreate the bug, put down a block that is going to be tested with the command, then do the command /testforblock <position: x y z> <tileName: block> [blockStates: block states]
And the result will be that the command will result in a success even if the block states are wrong
Linked issues
Attachments
Comments 0
No comments.
