[MC-627] Difference in powered times for wooden and stone buttons Created: 25/Oct/12  Updated: 13/Dec/19  Resolved: 08/Nov/12

Status: Closed
Project: Minecraft: Java Edition
Component/s: None
Affects Version/s: Minecraft 1.4.2
Fix Version/s: None

Type: Bug
Reporter: Jon Bermejo Assignee: Unassigned
Resolution: Works As Intended Votes: 0
Labels: None
Environment:

Windows 7, Java 7


Attachments: JPEG File Stone button.jpg     JPEG File Wooden button.jpg    
Issue Links:
Duplicate
is duplicated by MC-17216 Wooden Buttons send a Signal longer t... Resolved
is duplicated by MC-152199 Wooden button output a redstone signa... Resolved
is duplicated by MC-1027 Wood and Stone button Resolved
is duplicated by MC-2797 wood button has longer pulse than a s... Resolved
Confirmation Status: Unconfirmed

 Description   

I was testing out a Redstone toggle switch that did not utilize pistons, but instead the new behavior of repeaters locking. The set up is like this:
a 1 clock is made with two repeaters, side by side but facing opposite directions, Redstone is placed connecting one into the other, one of the repeaters powers into a block, and a Redstone torch is placed on the side of the block, powering the second repeater. Then, adjusting the timing of the repeaters to either three or four ticks of delay, you place a third repeater so that when powered, it locks the repeater that feeds into the block. Last, you place a block with a torch on the side powering the third repeater, and place a button on the block.
When used with a stone button, the circuit acts as normal, depowering the torch just long enough for the Redstone to make half a loop, turning half of the circuit off/on each press.
However, with a wooden button, allowing the Redstone to make a full loop, effectively diminishing the circuit's purpose.
tldr: Wooden buttons stay powered longer than stone buttons



 Comments   
Comment by Amaranth (Travis Watkins) [ 26/Oct/12 ]

This is an intentional difference in the two buttons.

Generated at Sun Jan 12 11:51:41 UTC 2025 using Jira 9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13.