Repeater blinking / powering itself
Repeaters will reactivate them selfs if there is power on the output side.
What I expected to happen was:
That the repeater would lose power after losing the input signal.
What actually happened was:
The repeater kept blinking on and off while it wasn't powered.
Steps to reproduce. (see image from top to bottom)
1. power the output side of a repeater.
2. power the input side of a repeater.
3. remove power from the input side of the repeater.
4. bugged repeater is created
Environment
OS: Windows 7 (ver 6.1, arch x86)
Java: 1.6.0_22 (by Sun Microsystems Inc.)
Launcher: Minecraft Launcher 1.4.4 (bootstrap 5)
Minecraft: 14w25b (updated Thu Jun 19 14:29:48 CEST 2014)
Linked Issues
is duplicated by22
MC-58936Repeater turns on and of repeatedlyDuplicateMC-58977{Redstone Rotational issue}DuplicateMC-58983Redstone repeaters creating clocks with no inputDuplicateMC-58993Redstone repeaters and torches have strange behavioursDuplicateMC-59010Repeaters act like a selfpowering clock - very strangeDuplicateMC-59011Repeaters with one tick delay do not turn offDuplicateMC-59031blinking repeaterDuplicateMC-59055Redstone repeaters that face north cause the followling redstone dust to start blinking.DuplicateMC-59090Repeaters sometimes pulse repeatedly forever when given a 1-tick pulse.DuplicateMC-59125Repeater flickeringDuplicateMC-59130Redstone Repeater glitchesDuplicateMC-59133Repeaters flash when powered a certain way.DuplicateMC-59140Repeater Turns Into ClockDuplicateMC-59148Redstone Repeater Stays On After It Turns OnDuplicateMC-59186Reapeter BugDuplicateMC-59227Repeaters don't stop sending power when unpowered.DuplicateMC-59248Redstone repeater looping on it's ownDuplicateMC-59273Repeater looping when not poweredDuplicateMC-59316When Sending a redstone signal to a repeater it somehow creates a clock and that repeater keeps activating and sending signals.DuplicateMC-59420Strange Redstone ClockDuplicateMC-59531Strange Redstone ClockDuplicateMC-59762Redstone Torch/Repeater Signal GlitchDuplicateAttachments1
Created Issue:
Repeater blinking
Repeaters will reactivate them selfs if there is power on the output side.
What I expected to happen was:
That the repeater would lose power after losing the input signal.What actually happened was:
The repeater kept blinking on and off while it wasn't powered.Steps to reproduce. (see image from top to bottom)
1. power the output side of a repeater.
2. power the input side of a repeater.
3. remove power from the input side of the repeater.
4. bugged repeater is createdEnvironment
OS: Windows 7 (ver 6.1, arch x86)
Java: 1.6.0_22 (by Sun Microsystems Inc.)
Launcher: Minecraft Launcher 1.4.4 (bootstrap 5)
Minecraft: 14w25b (updated Thu Jun 19 14:29:48 CEST 2014)
Linked Issues
is duplicated by1
TRASH-36505
Attachments1
is duplicated by
duplicates
duplicates
is duplicated by
is duplicated by
Repeater blinking / powering itself
is duplicated by
is duplicated by
is duplicated by
is duplicated by
![[Mod] Torabi](../../../data/assets/gravatar/torabi.png){kind=small}
Dupe of MC-58918
confirmed also for 14w26b
Only happens in certain directions.
Can cause an infinite loop when the output updates the repeater itself from a certain side.
Video explanation:
https://www.youtube.com/watch?v=Sjr_FS6eaLI
not only in certain directions....seems to be chunk related
http://youtu.be/k_MSjZtcoio
(left contraption is inside another chunk than the right one)
My repeater here is facing east, the whole contraption is in the same chunk: https://www.youtube.com/watch?v=d0b7gFBr5vg
Confirmed. I've created a player detection to summon wither skulls with custom names, creating floating messages when the player comes. I tested it, and when I saw, my world had a mountain of wither skulls. This is annoying.
Confirmed. All my 2-ticks monostables are now broken.
Not happening for me
Confirmed.
http://youtu.be/aKGapYzogfs
tested it on 26c ... seems to be gone
Yep, all my stuff is working again.
confirmed fixed in 14w26c
They forgot to add this to the "fixes in 14w26c" list.
It probably was a "collateral" fix! Some other bug must have been causing this issue, and they must have fixed that other bug.