I have a repeater that powers a command block with the command "/setblock (repeater's location) 93". When it should spawn an unpowered repeater, it instead goes on an infinite loop, with the repeaters spawning powered for exactly 1 tick. The setup I have involves several of these adjacently positioned, and when the others are powered, they will randomly turn off the other repeaters, and also turn on some randomly as well.
Included is the save.
Attachments
Comments 6
The front command block was for a "/setblock replace" command in another part of my world, the back command block uses the "/setblock replace" for the repeater.
Fairly certain that that statement is false, the comparator is intended to detect a block that is not in the detecting location, and this doesn't explain the continual repetition or the fact the repeaters next to the flickering one can begin flickering themselves. (The command block next to the comparator is detecting a different block in the distance, running a /testfor (~1 ~1 ~ above button locations) 124, and is in no way looking for the repeaters.)
Sorry, you said the command blocks in the back were placing the repeaters, which is obviously successful (and therefore, powers the comparator). Please zip and attach your world.
What are the command blocks in the back doing?