Command Block always activates Comparator

Command Block always activates Comparator - Set of red dice stacked together on wooden table placed on sunny terrace in daylight

I am trying to do something with command blocks. I have it test for a player at a certain position. I have set up a hopper clock that activates a command block with

/testfor @a[x=-611,y=80,z=714]

For some reason, no matter where i stand, the command block will always produce a redstone signal. Even though when I check the "last output" it says that the player can't be found.

I think I figured it out, the redstone comparator is picking up a signal from the block like its a regular block, but I do not know how to fix this.

Screenshots (open in new tab to enlarge):

onetwo



Best Answer

Connect the comparator output to a command block with the following command:

/blockdata x y z {SuccessCount:0}

where x, y, and z are the coordinates of the first command block

This happens because the comparator outputs if the command block has ever successfully executed the command. By using the blockdata command, you set the successful-execution-of-command counter of the command block to 0, making the comparator turn off

sorry for my english :(




Pictures about "Command Block always activates Comparator"

Command Block always activates Comparator - Cute little girl playing with wooden blocks at table near window at home
Command Block always activates Comparator - Anonymous crop parent playing with toys on floor at home
Command Block always activates Comparator - Unrecognizable little girl playing with wooden blocks at table at home



How do you get command blocks always active?

A command block can also be activated by setting it to "Always Active" mode. When activated, a command block executes its command, depending on the command block's type: An impulse command block executes its command once.

How make command block activate with command?

A redstone comparator can measure the fullness of a chest, as well as other block states, even through an opaque block.



Comparator Testfor Problem fix




More answers regarding command Block always activates Comparator

Answer 2

If you write a wrong command like "testfor @a[asdsfa]" it will be "testfor @a" so it will search all the map and find you so comparator will powered "testfor @a[, , , r=]" try this

Answer 3

Comparators release a small signal to the first piece of redstone connected to it. The repeater is simply amplifying this signal. To fix, just make the repeater and the comparator a block or maybe two apart with redstone in the middle.

Sources: Stack Exchange - This article follows the attribution requirements of Stack Exchange and is licensed under CC BY-SA 3.0.

Images: Matthias Groeneveld, Tatiana Syrikova, Tatiana Syrikova, Tatiana Syrikova