-
Bug
-
Resolution: Duplicate
-
None
-
Snapshot 13w03a
-
None
-
N/A
-
Unconfirmed
When you use the testfor command and a comparator, when the command comes up true, the comparator does not turn off, with no automated way to make it reset. I think this is because when the command block turns to the state 'true' it doesn't reset back to false. This could be fixed by making it so that when the redstone signal stops, the command block reverts to false.
- duplicates
-
MC-7681 Comparator stays powered after performing command from a Command Block
- Resolved