I noticed today that the testfor command is a bit odd, in that if it finds something in its parameters it delivers a constant output as a command block. If you open it, the signal disappears. I saw this in 1.8 - maybe this is a glitch I don't know about.
Ex: /testfor @p[score_test=1] -> activating comparator -> comparator stays on.
The Meaning of Life, the Universe, and Everything.
Join Date:
7/1/2017
Posts:
130
Minecraft:
jjlr
Member Details
The comparator will do that with every command, since it is only testing for the command to run successfully. you need another command block to either reset the command blocks success count, or copy and replace the entire command block from another location.
I noticed today that the testfor command is a bit odd, in that if it finds something in its parameters it delivers a constant output as a command block. If you open it, the signal disappears. I saw this in 1.8 - maybe this is a glitch I don't know about.
Ex: /testfor @p[score_test=1] -> activating comparator -> comparator stays on.
The comparator will do that with every command, since it is only testing for the command to run successfully. you need another command block to either reset the command blocks success count, or copy and replace the entire command block from another location.