Redstone powers the wrong blocks when redirected by pistons
When redstone dust is connected to any redstone component that redirects dust but does not produce power(will call this a 'consumer' [*] component to match the technical community's term), unintended blocks will also be powered by it. See attachments
Note: This appears to work as if the dust wasn't redirected in the first place while also powering the consumer* component
Steps to reproduce:
- Build the setups from the attachments
- Power the lever
Expected results:
Powering matches with the visual representation(as it does in Java edition), and so only the blocks that seem like they'll be powered, get powered.
Observed results:
The dust powers not only the block it redirects into, but also blocks it shouldn't from visual logic (testing shows that it powers as if it was not redirected in that case)
2016-09-03, 02:47 PM
2025-01-16, 08:23 PM
83
31
55366
piston, redstone, redstone-redirection, redstone_wire
1.19.70.23 Preview - 1.21.51 Hotfix
1.19.70.23 Preview, 1.19.60.23 Preview, 1.19.50.22 Preview, 1.17.10, 1.16.100.58 Beta, 1.16.100.56 Beta, 1.16.100.55 Beta, 1.16.0.63 Beta, 1.16.0.58 Beta, 1.14.30.51 Beta, 1.14.2.51 Beta, 1.14.2.50 Beta, 1.14.0.51 Beta, 1.13.3, 1.14.0.4 Beta, 1.13.1, 1.14.1 Hotfix, 1.14.0.3 Beta, 1.14.0.2 Beta, 1.14.0.1 Beta, 1.13.0.18 Beta, 1.13.0.17 Beta, 1.13.0.16 Beta, 1.13.0.9 Beta, 1.13.0.6 Beta, 0.15.90.0, 0.15.7, 0.15.90.1, 0.15.90.2, 0.15.90.7, 0.15.10, 0.16.0, 0.16.1, 0.17.0.1, 0.16.2, 1.0.0.0, 1.0.0.1, 1.0.2, 1.0.3, 1.0.4.0, 1.0.4.1, 1.0.4.11, 1.0.5.13, 1.0.6.0, 1.0.5.54, 1.1.0.0, 1.0.7.0, 1.1.0.8, 1.1.0.9, 1.1.0.55, 1.1.1.0, 1.1.2.50, 1.1.3.1, 1.1.5.0, 1.2.0.31, 1.2.3.6, 1.2.5.15, 1.2.6.2, 1.2.9.1, 1.2.10.1, 1.7.0.9 Beta, 1.12.1, 1.12.0, 1.13.0, 1.14.1.2 Beta, 1.16.40 Hotfix, 1.16.100, 1.16.201 Hotfix, 1.16.210, 1.17.0, 1.17.2 Hotfix, 1.17.34, 1.19.40, 1.19.50.23 Preview, 1.19.41, 1.19.50, 1.19.51, 1.20.41 Hotfix, 1.20.60, 1.21.2 Hotfix, 1.21.40, 1.21.51 Hotfix
-