MC-62209Redstone-Repeaters are going crazy
First things first:
The Commandblock will, when activated, clone the redstone repeater one block below it one block behind it.
When you place a redstone torch right on top of the redstone block, the torch will be active for exactly one tick.
I am currently playing on 14w28b, it's my latest version, but I couldn't select it above.
UPDATE: It's still a problem in 14w29b!
UPDATE: It's still a problem in 1.8.2-pre1
1.) What I expected to see:
Obviously, the command block will replace the repeater behind it. This happens in one tick, and the torch turns off. There is no more signal coming in and nothing else should happen.
2.)What actually happened:
The repeaters (yes plural - they are constantly being cloned, you can prove that easily by changing the delay of one of the 2 repeaters) are blinking like they are crazy, even though there is no signal coming in. You can remove both the redstone block and the torch, but nothing changes.
3.) Steps to reproduce:
Just build this contraption, place the torch on top of the redstone block and watch carefully 
Environment
Operating System: Windows 7 Home Premium 64 bit
Java: version 1.8.0_05
Linked Issues
relates to1
Attachments1
Created Issue:
Redstone-Repeater are going crazy
First things first:
1.) What I expected to see:
Obviously, the command block will replace the repeater behind it. This happens in one tick, and the torch turns off. There is no more signal coming in and nothing more should happen.2.)What actually happened:
The repeaters (yes plural - they are constantly being cloned, you can prove that easily by changing the delay of one of the 2 repeaters) are blinking like the are crazy, even though there is no signal coming in. You can remove both the redstone block and the torch, but nothing changes.3.) Steps to reproduce:
Just build this contraption, place the torch and watch carefullyEnvironment
Operating System: Windows 7 Home Premium 64 bit
Java: version 1.8.0_05
Attachments1
Redstone-Repeaters are going crazy
First things first:
1.) What I expected to see:
Obviously, the command block will replace the repeater behind it. This happens in one tick, and the torch turns off. There is no more signal coming in and nothingmore should happen.2.)What actually happened:
The repeaters (yes plural - they are constantly being cloned, you can prove that easily by changing the delay of one of the 2 repeaters) are blinking like the are crazy, even though there is no signal coming in. You can remove both the redstone block and the torch, but nothing changes.3.) Steps to reproduce:
Just build this contraption, place the torch and watch carefullyFirst things first:
1.) What I expected to see:
Obviously, the command block will replace the repeater behind it. This happens in one tick, and the torch turns off. There is no more signal coming in and nothing else should happen.2.)What actually happened:
The repeaters (yes plural - they are constantly being cloned, you can prove that easily by changing the delay of one of the 2 repeaters) are blinking like the are crazy, even though there is no signal coming in. You can remove both the redstone block and the torch, but nothing changes.3.) Steps to reproduce:
Just build this contraption, place the torch and watch carefully
First things first:
1.) What I expected to see:
Obviously, the command block will replace the repeater behind it. This happens in one tick, and the torch turns off. There is no more signal coming in and nothing else should happen.2.)What actually happened:
The repeaters (yes plural - they are constantly being cloned, you can prove that easily by changing the delay of one of the 2 repeaters) are blinking like they are crazy, even though there is no signal coming in. You can remove both the redstone block and the torch, but nothing changes.3.) Steps to reproduce:
Just build this contraption, place the torch and watch carefully
First things first:
UPDATE: It's still a problem in 14w29b!1.) What I expected to see:
Obviously, the command block will replace the repeater behind it. This happens in one tick, and the torch turns off. There is no more signal coming in and nothing else should happen.2.)What actually happened:
The repeaters (yes plural - they are constantly being cloned, you can prove that easily by changing the delay of one of the 2 repeaters) are blinking like they are crazy, even though there is no signal coming in. You can remove both the redstone block and the torch, but nothing changes.3.) Steps to reproduce:
Just build this contraption, place the torch and watch carefully
First things first:
UPDATE: It's still a problem in 14w29b!
UPDATE: It's still a problem in 1.8.2-pre11.) What I expected to see:
Obviously, the command block will replace the repeater behind it. This happens in one tick, and the torch turns off. There is no more signal coming in and nothing else should happen.2.)What actually happened:
The repeaters (yes plural - they are constantly being cloned, you can prove that easily by changing the delay of one of the 2 repeaters) are blinking like they are crazy, even though there is no signal coming in. You can remove both the redstone block and the torch, but nothing changes.3.) Steps to reproduce:
Just build this contraption, place the torch on top of the redstone block and watch carefully
relates to
![[Mojang] Grum (Erik Broes)](../../../data/assets/gravatar/grum.png){kind=small}
[Mojang] Grum (Erik Broes)
Is this still a problem in 14w29b?
@Anon Ymus: Yes it is
Why is no one interested in this problem? It's actually not that hard to prove that it exists.
This is difficult to test in 14w29b due to
MC-62166.As far as I know, the "block-delay"-thing is only visual. Additionally, the repeater was still blinking after I relogged/waited for several minutes.
Furthermore, the problem has already existed in 14w28b, so it's pretty sure that it isn't related with the block-delay-issue, which first appeared in 14w29b (as far as I know).
I'm not asserting that this bug has anything to do with
MC-62166, it's just thatMC-62166makes it difficult to confirm this bug.@[Mod] Galaxy_2Alex Yes, it is still an issue in the current Minecraft version; I just checked it. Sorry for my late reply, but I haven't found the time to update this bug report.
Might be invalid because of Searge's comment on
MC-48372Confirmed for