MC-70812Red stone torch burnout on a a block connected to a hooper clock
had a command block system that worked fine in 1.8pre3, but in the new update it seems that on a block connected to a hopper clock ie: two hoppers facing each other with one item going back and forth with a comparator running into a block with a redstone torch on it, the torch blinks like it is supposed to like twice but then burn out for awhile thus ruining the system
Environment
Put your operating system (Windows 7, Windows XP, OSX) and Java version if you know it here
Created Issue:
Red stone torch burnout on a a block connected to a hooper clock
had a command block system that worked fine in 1.8pre3, but in the new update it seems that on a block connected to a hopper clock ie: two hoppers facing each other with one item going back and forth with a comparator running into a block with a redstone torch on it, the torch blinks like it is supposed to like twice but then burn out for awhile thus ruining the system
Environment
Put your operating system (Windows 7, Windows XP, OSX) and Java version if you know it here
probably lag or game tick messup, but who knows
Did it make the fire extinguish noise?
Relates to another glitch I found earlier, but I forget which one. If you have multiple hopper clocks running, and you exit the reenter the world, some of the clocks will stop working properly (some will not produce a redstone signal.) When I tested this, I got a hopper clock that had a much faster redstone output, which might be what you got. This usually happens when a fast redstone signal is sent to a redstone torch, putting it out and playing the fire extinguish sound.
Is this still an issue in the current Minecraft Snapshot 15w45b or later? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.
If so, please provide screenshots of your setup.
Ticket resolved as incomplete, because no answer in a reasonable amount of time (1+ year), if it still happens, please update the ticket.