mojira.dev
MC-7681

Comparator stays powered after performing command from a Command Block

I tested the /testfor command and i found it was great!
I powered the command block with a button but when the button wasn't pressed anymore the command block had still a redstone output.

It only went off when I destroyed the commandblock!

I don't know if that has to be so or if it's a bug.
Please correct me if it has to be so!

Linked issues

MC-7759 Door Closes When It's Not Supposed To Resolved MC-7765 Testfor and Comparator Don't Work Properly Resolved MC-7883 Command block /Testfor command don't update. Resolved MC-8931 When a command block outputs true it remain true until it is activated again and doesn't meet the requirements Resolved MC-9438 /testfor with comand block does not accept location arguments Resolved

Comments 11

What command did you put in the commandblock ?
Was the condition still valid by your player because you were walking aroung the command block ?

Any command will do. The Comparator is what stays powered.

Ok after more testing I figured it out: First off give the command "testfor" a search radius. If a player is within that radius and the Command Block is activated it tells the Comparator to output a signal. Then if you leave that radius and activate the Command Block again, it checks again, this time no player is around - tells Comapartor - signal shuts off.

I can confirm. I just tried this while my block had "/xp -1L @p"; it turned on like I assume it should when I had xp to give it, but then when I ran out, the signal was still on, which I don't think was supposed to happen. Please reopen.

The Comparator connected to the Command Block is only usefull if "/testfor" - command is used.

1 more comments

It seems to work with all commands, which is great! Even with /clear, only a signal if clear was successful. Great for my new adventure map. 🙂
But the comparator staying active is causing some troubles. I have already several clocks in the area and FPS are getting down so I tried to use a button but this way it stays on. :/

Dunno if bug or feature, but it's still the case in Snpashots 13w09a/b !
I had this troubles with the /testfor command too. Please update the "Affects Version/s" tag so Mojang can find and maybe fix it !

@zombie hunter:

"Works As Intended"

also, this gives you trouble, just use this: http://imgur.com/2nCkfPD

@kinsi:
Thanks, exactly what I need 🙂

The same thing is happening to me. Except the /testfor command block isn't staying on while a /summon command block is.

MinecraftShamrock

(Unassigned)

Confirmed

command_block, redstone, redstone-comparator

Snapshot 13w03a

Retrieved