Windows 10, Java v8 update 65
In the newest version of the snapshot, redstone blocks are sending signals through other non-redstone related blocks.
What I expected to happen was...:
Describe what you thought should happen here
I expect the redstone block not to power non-redstone related blocks, as it had done before.
What actually happened was...:
Describe what happened here
The redstone blocks powered all surrounding blocks, causing multiple problems in a lot of my redstone creations.
Steps to Reproduce:
1. Put a step by step guide on how to trigger the bug here
2. Place a redstone block, next to it any opaque block, next to it a block that is activated by redstone (door, redstone lamp, piston, etc.)
3. The activation block will power through the opaque block. Breaking the redstone block afterwards will result in the activated block still being powered until the original opaque block is broken.
The first picture has no levers, buttons, etc. hidden on it. It is solely those three blocks. The second picture demonstrates the same structure once the redstone block is broken.
The posted video demonstrates another way to re-create the bug, causing a normal piston with a redstone block on the extension side (not facing upwards) with an opaque block on top of the redstone block to extend and retract violently once a block update is caused near the piston.(please excuse my bad recording software).