I need to use /testfor for a build currently, and I am stuck trying to get repeated signals from the same testfor command multiple times. For instance, the command is [/testfor @a] I activate it once and it activates a dispenser, but of course if I activate the /testfor again it will not send another signal and will simply stay on. What is the smallest circuit I can use to overcome this (preferably vertical)? I have a rough design but I need something better...
A test for @a can't be reset once triggered because there is always someone logged in. You need to use a different command with some arguments or something.
What is the easiest way to eliminate /testfor constant signal?