MC-41378Redstone Torch Pulse Bug/Glitch
When you have Redstone torches like in this setup here, only a few of them blink. In another world only the last of them blinked, so it seems to happen only in specific locations of the world.
A quick but bad fix for this is setting different delay in front of the torches, so they don't activate the same time.
Maybe there are more affected versions, I only tested these two.
(With all this i mean the torches on top of the blocks, not those on the side of the blocks..)
Environment
os: Windows 7 Home Premium
os version: 6.1
java version: 1.7.0_25
Linked Issues
Created Issue:
Redstone Torch Pulse Bug/Glitch
When you have Redstone torches like in this setup here, only a few of them blink. In another world only the last of them blinked, so it seems to happen only in specific locations of the world.
A quick but bad fix for this is setting different delay in front of the torches, so they don't activate the same time.
Maybe there are more affected versions, I only tested these two.Environment
os: Windows 7 Home Premium
os version: 6.1
java version: 1.7.0_25
Attachments1
When you have Redstone torches like in this setup here, only a few of them blink. In another world only the last of them blinked, so it seems to happen only in specific locations of the world.
A quick but bad fix for this is setting different delay in front of the torches, so they don't activate the same time.
Maybe there are more affected versions, I only tested these two.
To the guy that commented: I dont know where the comment button is..
But I am sure that it is no visual glitch, because pistons dont retract/extend at the same time.
When you have Redstone torches like in this setup here, only a few of them blink. In another world only the last of them blinked, so it seems to happen only in specific locations of the world.
A quick but bad fix for this is setting different delay in front of the torches, so they don't activate the same time.
Maybe there are more affected versions, I only tested these two.
To the guy that commented: I dont know where the comment button is..
But I am sure that it is no visual glitch, because pistons dont retract/extend at the same time.
When you have Redstone torches like in this setup here, only a few of them blink. In another world only the last of them blinked, so it seems to happen only in specific locations of the world.
A quick but bad fix for this is setting different delay in front of the torches, so they don't activate the same time.
Maybe there are more affected versions, I only tested these two.
(With all this i mean the torches on top of the blocks, not those on the side of the blocks..)
duplicates
![[Mod] Ezekiel (ezfe)](../../../data/assets/gravatar/ezekielelin.jpeg){kind=small}
Its a restone update glitch (not necassarily a bug, just a graphics thing). The redstone is updating very fast and actually has a positional variable now. So the update will have occured just not vissually. The only way to fix this would be to slow the pulse down a bit or slow the redstone update coding down a bit which could/would mess a lot of things up.
Ok now that I found the comment button, i can say that this is not a graphical glitch, because pistons on top of the torches that dont get lighten wont extend.
Not a glitch, it is a visual effort to reduce lag.
Again, this is not just a visual thing, only the last of the torches will output a redstone signal.
Cannot reproduce.
@Michael McCluskey - are you flipping the lever on and off quickly? Its a pulse thats causing this not a constant signal.
@Paul Hege - This bug is similar to
MC-29430where the location of the piston setup is determined by the piston location. Now that I'm re-reading your bug I can tell its this same basic issue. Basically the formula for redstone updates and redstone ticks seems to have a location variable in it, possibly to reduce lag when distance to player is determined or when chunks are unloaded, but I can't say for sure as I don't know how to view the coding, and probably wouldn't understand the code without help.Is this still a concern in the latest Minecraft version 14w03b? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.