MCPE-18114Solid/opaque redstone components act differently from normal solid/opaque blocks
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.
Linked Issues
Attachments1
Created Issue:
Solid/opaque redstone components act differently from other solid/opaque blocks
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-16286does 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.Steps to reproduce:
1. Create a setup with a powered/activator rail, single redstone dust, & solid redstone component like the one in the attached screenshot.
2. Power the solid component and see how the rails don't turn on.
- Unresolved
- Open
- Unconfirmed
- Windows
- Windows 10 Version 1607
- 0.16.1
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-16286does 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.Steps to reproduce:
1. Create a setup with a powered/activator rail, single redstone dust, & solid redstone component like the ones in the attached screenshot.
2. Power the solid component and see how the rails don't turn on.
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-16286does 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.Steps to reproduce:
1. Create a setup with a powered/activator rail, single redstone dust, & solid redstone component like the ones in the attached screenshot.
2. Power the solid component and see how the rails don't turn on.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-16286does 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:
1. Create a setup with a powered/activator rail, single redstone dust, & solid redstone component like the ones in the attached screenshot.
2. Power the solid component and see how the rails don't turn on.
Solid/opaque redstone components act differently fromothersolid/opaque blocksSolid/opaque redstone components act differently from normal solid/opaque blocks
discovered while testing
relates to
![[Mojang] Adrian Östergård](../../../data/assets/gravatar/nighter.jpeg){kind=small}
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-16286does 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:
1. Create a setup with a powered/activator rail, single redstone dust, & solid redstone component like the ones in the attached screenshot.
2. Power the solid component and see how the rails don't turn on.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-16286does 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.
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-16286does 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.
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-16286does 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.
![[MCPE Mod] Celesian](../../../data/avatars/users/81635.png){kind=small}
![[Mojang] Mega_Spud (Jay Wells)](../../../data/avatars/users/92696.png){kind=small}
Sometimes, when you load up a world, a couple random pistons, dispensers, droppers, observers, and/or redstone lamps will be stuck in either their on or off state, and will not change state until broken, pushed, pulled, or upon reloading the world. The blocks also act as if they were just normal non-rs-component solid/opaque blocks. This means that pistons will be able to pass a redstone signal through them via dust & a repeater, and the blocks will not be affected by any redstone-component-specific bugs like MCPE-18114. This bug is difficult to reproduce since it seems to be somewhat random as to when it occurs, but it tends to happen to the same particular blocks when testing.
I have discovered that the bug WAS indeed fixed in 0.16.0, and what I thought to be proof that the bug was still occurring was actually a previously-undiscovered bug, MCPE-18114. I have removed the screenshots relating to that bug and will now close this issue as fixed.
This is fixed as of 1.7.0.9 Beta, possibly earlier. (I have not tested any other recent versions.)
Confirmed to be fixed.