-
Bug
-
Resolution: Unresolved
-
None
-
1.16.1, 20w29a, 20w30a, 1.16.2 Pre-release 1, 1.16.2 Pre-release 2, 1.16.2 Pre-release 3, 1.16.2 Release Candidate 1, 1.16.2 Release Candidate 2, 1.16.2, 1.16.3 Release Candidate 1, 1.16.3, 1.16.4 Pre-release 1, 1.16.4 Pre-release 2, 1.16.4 Release Candidate 1, 1.16.4, 20w45a, 20w46a, 20w48a, 20w49a, 20w51a, 21w03a, 21w05b, 21w06a, 21w07a, 21w08b, 21w10a, 21w11a, 21w14a, 21w38a, 21w39a, 22w14a, 1.19.2, 1.19.4, 23w51b
-
None
-
Community Consensus
-
Commands, Redstone
Was able to test using MC-191016.
Running the command
/setblock {X} {Y} {Z} observer
on a block that is already an observer shows that the command failed to run (either through the chat or the command block output). However, a redstone pulse is sent out from the observer (MC-191016), implying that the block was actually changed.
The expected behavior is that the observer would not be updated when the setblock command is reused on the block (as the command resulted in an error).
I'm attaching a short video of this bug.
- relates to
-
- Open