As shown in the attached screenshots, when blocks are given redstone power via a comparator, repeater, redstone wire, etc. they do not pass on their powered state to nearby redstone until that redstone receives a different block update.
Linked issues
is duplicated by 44
relates to 2
Attachments
Comments 12
I can confirm this is true, my redstone race mechanism just failed on me in survival, and when I went to check on it I saw I had to manually update the blocks for them to send the signal through.
Same issue with Comand Blocks. I have a redstone world with some comand block contraptions and mostly has contraptions that has a block going into a power sorce. now my entire world doesnt work. (Im using 16w42a)
This was marked as a Duplicate for MC-108939 that I made upon updating to 16w42a
These are the two screenshots I added demonstrating the issue.
https://bugs.mojang.com/secure/attachment/126653/2016-10-19_19.27.16.png
Blocks from left to right are as follows:
stone_pressure_plate, unpowered_repeater, command_block, unpowered_repeater, command_block, unpowered_repeater, command_block,unpowered_repeater,command_block
Commands of command blocks are as follows:
say @p just got a free Shulker Box!
clear @p purple_shulker_box -1 -1
give @p purple_shulker_box
kill @e[type=Item]
and
https://bugs.mojang.com/secure/attachment/126654/2016-10-19_19.27.31.png
I would imagine this bug is caused in attempt to limit the capabilities of the observer block. Because the observer block shouldn't be able to detect redstone updates to the block, the feature of redstone updating blocks was simply removed. However, this also causes errors when updating other items attached to the block, such as, in this case, torches.
As I noted in my (unintentional) duplicate MC-109084, the converse is true where the block doesn't unpower the redstone properly.
Jikes oops.