[MC-7681] Comparator stays powered after performing command from a Command Block Created: 17/Jan/13  Updated: 05/May/19  Resolved: 18/Jan/13

Status: Resolved
Project: Minecraft: Java Edition
Component/s: None
Affects Version/s: Snapshot 13w03a
Fix Version/s: None

Type: Bug
Reporter: MinecraftShamrock Assignee: Unassigned
Resolution: Works As Intended Votes: 1
Labels: command_block, redstone, redstone-comparator
Environment:

Windows 7 (64BIT), JRE 7, JDK 7


Issue Links:
Duplicate
is duplicated by MC-7759 Door Closes When It's Not Supposed To Resolved
is duplicated by MC-7765 Testfor and Comparator Don't Work Pro... Resolved
is duplicated by MC-7883 Command block /Testfor command don't ... Resolved
is duplicated by MC-8931 When a command block outputs true it ... Resolved
is duplicated by MC-9438 /testfor with comand block does not a... Resolved
is duplicated by MC-10449 Comparators doenst become OFF after b... Resolved
is duplicated by MC-12996 command-block with a testfor command ... Resolved
is duplicated by MC-14296 Comparator doesn't update when it rec... Resolved
is duplicated by MC-15389 Command Block gives signal to a Redst... Resolved
is duplicated by MC-28062 Command Block outputs a signal contin... Resolved
is duplicated by MC-33577 Testingfor score command block glitch Resolved
is duplicated by MC-35931 Comparator doesn't turn off after a c... Resolved
is duplicated by MC-35968 Commandblock Output Lock Resolved
is duplicated by MC-41146 Comparator stay powered after a Command. Resolved
is duplicated by MC-41570 Command blocks with /testfor still se... Resolved
is duplicated by MC-44804 Comparators not interacting with comm... Resolved
is duplicated by MC-87132 Comparators remain lit after testfor Resolved
is duplicated by MC-89877 Repeating Command Block fails to dete... Resolved
is duplicated by MC-113119 Command block output not updated when... Resolved
is duplicated by MC-120204 Comparator that remains lit after exe... Resolved
is duplicated by MC-144741 Sometimes when u put a command block ... Resolved
is duplicated by MC-150879 компаратор не выключается. the compar... Resolved
CHK:
Confirmation Status: Confirmed
Game Mode: Creative

 Description   

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!



 Comments   
Comment by Cody Shearer [ 13/Jan/14 ]

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

Comment by _zombiehunter [ 07/Mar/13 ]

@kinsi:
Thanks, exactly what I need

Comment by kinsi [ 07/Mar/13 ]

@zombie hunter:

"Works As Intended"

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

Comment by _zombiehunter [ 27/Feb/13 ]

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 !

Comment by Alexander Spielvogel [ 16/Feb/13 ]

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. :/

Comment by irunor [ 18/Jan/13 ]

Weird, the wiki says "Comparators fed by command blocks will now indicate whether the last run command was run successfully," I'll have to update it.

Comment by Tails [ 18/Jan/13 ]

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

Comment by irunor [ 18/Jan/13 ]

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.

Comment by Tails [ 18/Jan/13 ]

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.

Comment by Tails [ 17/Jan/13 ]

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

Comment by Kumasasa [ 17/Jan/13 ]

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

Generated at Sun Jan 12 12:15:19 UTC 2025 using Jira 9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13.