Wierd indirect redstone interactions.
Wojbie opened this issue ยท 1 comments
It was recently pointed out to me and after some testing i found it to be the case.
When having setup like this:
As in Computer - any full block - door.
If output is set to true on the side the door will open.
But setting output back to false on that side will not cause the door to close.
It works that way on all sides.
I did test that with repeated as on picture and blocks were getting powered correctly.
It just seems like on indirect un-powereing doors ( and trapdoors) do not receive the redstone update?
Hopefully someone will be able to make more sense of this then me.
EDIT: Shutting computer down (whitch sets all redstone to false) has same effect.
Worth pointing out that the repeater does power down correctly, as do lamps, gates, and pistons. I can also reproduce with doors / trapdoors by having a "lit" turtle move away from the grass block instead of calling rs.setOutput(). Unlike an older redstone related bug, toggling term.setCursorBlink() off / on seems to have no effect here.
Personally I'm testing under MC1.12.
Edit: Also seeing the same thing in MC1.7.10/CC1.74.