-
Bug
-
Resolution: Fixed
-
0.16.1, 0.17.0.1, 0.16.2, 1.0.0.0, 1.0.0.1, 1.0.0.2, 1.0.0, 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.9, 1.1.0.55, 1.1.1.0, 1.1.2.50, 1.1.3.1, 1.1.4.51, 1.2.0.2, 1.1.5.0, 1.2.0.22, 1.2.5.15, 1.2.6.2, 1.2.5.52, 1.2.9.1, 1.2.10.1
-
Confirmed
-
Windows
-
61479
Solid/opaque blocks are supposed to all act the same in how they transmit redstone power. However, solid/opaque blocks that are also redstone components (droppers, dispensers, redstone lamps, & note blocks), power other components differently.
First of all, if you strongly power a solid component, then a powered rail or activator rail that is adjacent to a plus-shaped dust adj. to the solid component, then the rail will NOT be powered. See attached screenshots. If you replace the solid component with a normal solid block, the rails will be powered.
Second, it appears that MCPE-16286 does not occur when the block between the activation-power-source and the piston is a solid-component.
It seems like redstone components that are solid/opaque are coded differently/incorrectly or something. It is possible that looking into the code and finding the root causes could lead to the fix of both this bug and MCPE-16286. There may be other quirks with solid redstone components that I have yet to discover, but these are all that I've found so far.
Steps to reproduce:
- Create a setup with a powered/activator rail, single redstone dust, & solid redstone component like the ones in the attached screenshot.
- Power the solid component and see how the rails don't turn on.
- discovered while testing
-
MCPE-15704 Power Rail not activating
- Resolved
- relates to
-
MCPE-16286 Pistons are incorrectly activated when adjacent to a block that is adjacent to an activation-power source, but the block is not powered by the power source
- Resolved