Sometimes when activating a wooden or stone button, there is a possibility that the button activates not for 10 or 15 ticks as it should, but a much shorter amount of time. sometimes only a few ticks long.
happens completely randomly in survival and creative mode.
Linked issues
duplicates 1
Comments 10
I have seen this maybe four times my entire life. It's very rare, but it's there. You'd have to push a million buttons to see this happen.
Happens on smp, too, and it's not a client-side problem because a minecart moved halfway through a powered rail with this shorter pulse.
I've seen this in a circuit I currently use. This is using a wooden button, however I have also seen this occur with a stone button. The sounds line up with the shorter pulse as well, playing the second "click" sound more quickly than usual. As for the length, hard to say, maybe describing the circuit path would be helpful? The signal travels through 5 meters of redstone wiring to activate a dispenser, then through a repeater set to a 3 tick delay to a falling edge detector using a repeater lock which powers the dispenser when the pulse ends. The pulse generated normally from either a stone or wooden button is long enough to activate the dispenser twice with that circuit. The shortened pulse is enough to make it through the 3 tick delay repeater and "charge" the falling edge detector but the pulse doesn't stay on long enough for the falling edge to activate the dispenser a second time. This has happened twice in the past 100 uses of the circuit.
Confirmed, but no procedure to reproduce.
SMP: A button in a minecart train station - which was functioning since ever - gave once a too short impulse.
The bug is still there. I'm working on a big redstone stuff so I need to press a lot of buttons and about 1 on 30 clicks is bugged.
I'm surprised there hasn't been much activity for this bug report recently. I'm coming here to confirm that this annoying bug still exists in stable release 1.5.2. It's a semi-rare, randomly-occurring bug, and I've noticed it in some form or another ever since buttons were initially implemented (sometime in Alpha/Beta).
I think the only way of fixing this right now is to place a repeater facing away from the adjacent block where the button is placed, to help sustain the pulse. Although this method won't be practical for things like small button-operated iron doors, for example.
Consolidating to MC-3808.
Unable to reproduce. Are you able to determine exactly how many ticks?