Powered mechanisms react to change of redstone connectivity
What I expected to happen was...:
When I broke the torch the redstone dust would not be powered anymore and nothing would happen to the piston.
What actually happened was...:
For a brief moment the piston became powered.
Steps to Reproduce:
1. Place one redstone torch on a wall.
2. In front of the torch place one piece of redstone dust.
3. Place a piston directly to the left or right of the redstone dust.
4. Break the redstone torch.
5. For a brief moment the piston will become powered.
I put a picture down below to show you how you can set it up. But the piston can also be placed on the right
Environment
OSX 10.8.2 Not Sure What Java Version
Linked Issues
is duplicated by4
MC-7166Signal strenght, piston BUD and inconsistent behavior (activating when it shouldn't, not in all cases)DuplicateMC-8494Piston powered indirectlyDuplicateMC-181594Inconsistent redstone lamp alimentation when a redstone torch is brokenDuplicateMC-938pistons retracting after power is cut Duplicaterelates to3
MC-8328Powered mechanisms react when receiving a 0 tick redstone signal (existence of micro-pulses in general / inconsistent block update 'algorithm')
NormalMC-8923Powered mechanisms (except for Dispensers and Droppers) react when they should notFixedMC-4052Powered mechanisms react to change in redstone power levelFixedAttachments1
Created Issue:
Sometimes a piston will be powered for a second when it is not supposed to.
What I expected to happen was...:
When I broke the torch the redstone dust would not be powered anymore and nothing would happen to the piston.What actually happened was...:
For a brief moment the piston became powered.Steps to Reproduce:
1. Place one redstone torch on a wall.
2. In front of the torch place one piece of redstone dust.
3. Place a piston directly to the left or right of the redstone dust.
4. Break the redstone torch.
5. For a brief moment the piston will become powered.I put a picture down below to show you how you can set it up. But the piston can also be placed on the right
Environment
OSX 10.8.2 Not Sure What Java Version
Attachments1
is duplicated by
is duplicated by
Sometimes a piston will be powered for a second when it is not supposed to.Powered mechanisms react to change of redstone connectivity
is duplicated by
is duplicated by
relates to
![[Mod] Michael Wobst](../../../data/avatars/users/37868.png){kind=small}
is duplicated by
No, its a different thing than MC-1263. Mine is getting unpowered when a pressure plate is unpowerig it when at the same time a redstone line is powering it. Its two different things. And the redstone line must be five or longer for it to work. Just try it yourself.
It's updating the piston because the redstone connectivity changes from "dot" to "line", see MC-1263.
Yup you're indeed right. I still don't see it as a duplicate of MC-108 though, as it is the update that is the problem here, not the BUD itself (the redstone shouldn't update the piston to go along with the recent change of the fence gates, redstone lamps and such). Also not a duplicate of MC-1263 because in it the issue is the redstone powering the piston, not just updating (it oculd update just fine without powering the piston).
I apologies for the rudeness in the previous post.
![[Bot] Arisa](../../../data/avatars/users/43007.png){kind=small}
Duplicate of MC-1263
Yeah while I was playing with redstone inventions, pistons would randomly power when redstone is 2 blocks away, for one tick.
Confirmed in 1.4.5.
Applies to all powered mechanisms.
Still happens in 13w09b but... can anybody provide a working design where redstone wire does not turn into a dot on connectivity change? I can't come up with any.
Is this still a concern in the current Minecraft version 1.6.4 / Launcher version 1.2.5 ? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.
This ticket is incomplete without the requested information, no response has been received within a reasonable time and we are assuming the issue has been resolved. If you are still experiencing this issue, we can reopen it at your request.
Please review the guidelines before reporting issues.
I also tried reproducing the issue, and it seems that the bug has been fixed.