1. When an observer is placed using a command, it will "observe" a block update and thus switch its "powered" blockstate to "true" for a brief moment. This is unexpected because placing an observer by hand doesn't cause such an activation.
/setblock ~ ~ ~2 minecraft:observer
/fill ~ ~ ~2 ~ ~ ~2 minecraft:observer
2. The same occurs when the command fails to place the observer when there's already an observer placed at the target position (see the attached screenshot).
Execute the command from above again (i.e. two or more times in total)
3. The behaviour from both 1 and 2 even occurs when the blockstate "powered" is specified in the command as "false".
/setblock ~ ~ ~2 minecraft:observer[powered=false]
/fill ~ ~ ~2 ~ ~ ~2 minecraft:observer[powered=false]
Linked issues
Attachments
Comments
sof
Dhranios
Arisa Bot
Thank you for your report!
We're tracking this issue in MC-31100, 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.
Can confirm