[MC-12239] command block testfor command does not work with coordinate arguments

When I put "testfor x=7,y=5,z=32" in a command block and hooked it up to a redstone clock so that it would update itself and put a redstone comparitor in front of it...

What I expected to happen was...:
-When I was at coordinates "7 5 32", the comparitor would turn on, powering the redstone in front of it
-When I was not at said coordinates, the comparitor would turn off

What actually happened was...:
As soon as the command was entered in the command block, the comparitor turned on, and refused to turn off no matter where i was (including those coordinates)

Steps to Reproduce:
1. Place a command block
2. Place a redstone comparitor facing out from the command block
3. In the command block, type the following: "testfor @p[x=<your x coordinate>,y=<your y coordinate,z=<your z coordinate>]"
4. Place a redstone repeater facing out from the comparitor
5. Place a redstone lamp so that it gets input from the redstone repeater
6. Hook the command block up to a redstone clock (google how to do this if you don't know)

All other commands and testfor arguments work perfectly for me.

Edit:
At the input of a commenter, I included a maximum search radius argument ("r=<radius>"). Now the command block acts as if the search radius argument was the only argument, turning on when I am in radius and off when I am out of radius, regardless of coordinates.

Linked issues

is duplicated by 9

MC-30435 "/testfor" Coordinate Output Always True Resolved

MC-34979 /testfor not working with coordinates Resolved

MC-38417 Location parameters not working when selecting a non-specific player. Resolved

MC-40797 /testfor with co-ordinates doesn't work? Resolved

MC-50183 Strange coordinates behavior Resolved

4 more links

Attachments

Comments 22

migrated 2013-03-17T17:53:26Z

[^11-1-13[2334@-5gmt]Bueller.png]

[media][media][media][media][media][media][media]

Tails 2013-03-17T17:55:00Z

You haven't provided a search radius.

Evan B 2013-03-17T17:56:57Z

Is that necessary? And why is that necessary if I specify the coordinates?

Tails 2013-03-17T18:07:58Z

Please do not mark issues as private, unless your bug report is a security issue containing information that may compromise your server/client.

Tails 2013-03-17T18:08:48Z

Search radius is always required when using specific coordinates.

12 more comments

Ferdinand B. 2013-05-05T11:09:25Z

also, you didn't really give us a real clue what you put into the command block.

Once you said testfor x=<number> y=<number> z=<number>
and once you said testfor @px=<number>,y=<number>,z=<number> and in your pic you said @p[x=<number>,y=<number>,z=<number>]

The way it works is this:

testfor <playername>
The @-Notations are treated as playernames

If you do an @-notation with arguments [x,y,z] then it will search from that location but the radius will still be infinite.
So @p[3,4,5] will still be on as long as at least one player is online (he is the nearest to 3,4,5)

In your case, I would either do @p[x,y,z,r], @a[x,y,z,r] or @r[x,y,z,r] to get the disired effect (only triggering if you are in a certain area)

Example: testfor @a[x=27,y=65,z=-1226,r=3]
Will test for a player within 3 blocks spherical radius of x=27, y=65 and z=-1226

Steven Valenski 2013-10-30T02:36:47Z

I have had similar issues as well but mine was looking for a person to TP for example
tp @a[70,64,-15,1] 60.5 68 -2.5
using this as my command it pulled everyone in my game not just everyone in that location, further testing also showed this is not the case when a specific player is called, for example
tp Kurai_ookami[70,64,-15,1] 60.5 68 -2.5
only work while within the radius, so it seems @p, @r, and @a are not simply being treated as a player name as they behave differently. Also playing around with different input structures
tp @a[x=70,y=64,z=-15,r=1] 60.5 68 -2.5
tp @a[x=70,y=64,z=-15,r=1,rm=0] 60.5 68 -2.5
tp @a[x=70,y=64,z=-15] 60.5 68 -2.5
has shown that none of the formats for writing arguments work with the @p, @r and @a calls but do work when referring to a specific player. Including the 3rd which does not list a radius (defaulting to both minimum and maximum radius being 0 A.K.A. the exact location called and nothing more) showing that a radius is NOT required.

Edit: to be more clear this was actually tested with an effect command, /tp still does not work

Steven Valenski 2013-10-30T16:06:58Z

Just realized I have another couple command blocks with similar code but they do work.....
effect @a[60,69,4,1,score_MobKills_min=500] 5 3600 3
scoreboard players remove @a[60,69,4,1,score_MobKills_min=500] MobKills 500
not sure why one works and the other doesn't

Steven Valenski 2013-10-30T16:39:17Z

New development: I moved the command blocks to a new location, didn't even change the commands in the slightest and now they work.

Edit: the TP command block still didn't work

Steven Valenski 2013-10-30T22:02:54Z

can someone update this to affects 1.7.2?

Steven Valenski 2013-10-30T22:06:33Z

Also in the same right I have no idea why my new report was referred to here considering this was for 1.5 and I was reporting for 1.7.2

Steven Valenski 2013-10-31T01:15:21Z

it appears I need to correct myself again. it seems that location restricting arguments are simply not working with the /tp command, whether or not it is executed via a command block. Though it is working with other commands like /give and /scoreboard

Steven Valenski 2013-10-31T20:34:58Z

tested a couple more commands /tell and /testfor are also not responding to location arguments correctly

Steven Valenski 2013-10-31T20:39:37Z

please update to include affects versions 1.7.2 and mark it as re-opened

Steven Valenski 2013-11-02T03:21:34Z

can someone please take the time to confirm this instead of just writing it off as someone else' syntax errors. This is NOT working as intended.

Steven Valenski 2013-11-02T03:36:43Z

A screenshot of my location, the command used and the return I get when attempting to use it.

Ferdinand B. 2013-11-02T15:02:15Z

confirming that commands /tp and /tell do NOT work with @ statements that make use of the x,y,z or r arguments in Minecraft 1.7.2
Other arguments work fine though.

Examples:

/tell @p[score_lolz=1] Whisper
works
/tell @p[x=102,y=65,z=-364] Whisper
doesn't work (claims to not be able to find player)

Steven Valenski 2013-11-02T16:58:53Z

thank you Ferdinand B., I thought no one was going to notice this just because it's already been written off

Ferdinand B. 2013-11-02T17:12:57Z

I suggest you to change the title into something similar to "[Command Block] testfor, tell, tellraw and tp don't accept coordinate-@ arguments", but that's only my thought, so if you think the existing title suits this topic better, go leave it.

I sure notice this as I receive email-notifications about it, so I thought I re-confirm the issue with 1.7.2
And there we are, with a (in my thoughts) really important bug that should be fixed, because it really makes adventure-maps suffer.

Steven Valenski 2013-11-02T20:24:49Z

mine was forced onto this and marked as resolved >_> so I'll probably just make a new one

Edit: new ticket MC-38817

Ethan L! 2015-01-22T23:54:23Z

Yup, I'm having the same basic issue. Mojang's gotta' fix this.

KingSupernova 2015-03-17T01:43:59Z

To all you people saying this is still an issue:

No it's not. The radius argument defaults to infinity if you don't input it. So if you type "/testfor @a[x=0,y=0,z=0]", it will look for all players within a radius of infinity of 0, 0, 0, and it will obviously find all players in the world. If you want to limit the search radius, input a radius argument. In the future, please actually check the correct syntax for commands before posting a bug report.