1. When placing an observer with its "powered" blockstate set to "true" via command, it will be placed with it set to "false". (Unlike MC-277277 the observer doesn't even detect a block update first, to turn off afterwards, but starts out as unpowered.)
/setblock ~ ~ ~2 minecraft:observer[powered=true]
/fill ~ ~ ~2 ~ ~ ~2 minecraft:observer[powered=true]
2. Executing the same command a second time & thus replacing the unpowered observer (not just any block) will then make it stay powered as was expected from the first execution. (Every consecutive execution of the same command will then result in it failing as expected, because the block doesn't change anymore.)
Execute the same command again
Linked issues
Attachments
Comments
DLSDUFER
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 reproduce.
Few clarifications:
The observer stays powered even after updating the block(i.e. placing any block next to it) OR relogging into the world
The observer does not change the redstone output even if a block was placed/the block was updated on the "face" side
Everything said in the comments and the post happens in BOTH the vanilla version of the game AND the redstone experimental features.