This is a big problem because i cant finish a big project that i'm working on basically when it succesfully testfors someone it sends a current when it doesn't the redstone doesn't turn off unless i open and close a command block GUI heres some pictures showing my setup:
(P.S Plz help A.S.A.P)
Attachments
Comments 3
You need to have a repeating Redstone pulse going into the Command Block for it to keep testing. Otherwise, it will remain "on" until it receives a Redstone signal. (Try putting "/setblock ~ ~+1 ~ redstone_block 0 destroy" into a Command Block and input a Redstone signal of some sort on top. This will create a very quick Redstone pulse - then hook up Redstone to it. You can also power other sides of the Command Block, only if the setblock co-ords are to that side.)
The command block will output a permanent signal as long as it doesn't get triggered again and the condition is no longer met.