[MC-12239] command block testfor command does not work with coordinate arguments Created: 17/Mar/13 Updated: 29/Dec/17 Resolved: 17/Mar/13 |
|
| Status: | Resolved |
| Project: | Minecraft: Java Edition |
| Component/s: | None |
| Affects Version/s: | Minecraft 1.5 |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Evan B | Assignee: | Unassigned |
| Resolution: | Works As Intended | Votes: | 0 |
| Labels: | command_block, comparator, coordinates, redstone | ||
| Environment: |
Windows 8 |
||
| Attachments: |
|
||||||||||||||||||||||||||||||||||||||||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||||||
| Confirmation Status: | Unconfirmed | ||||||||||||||||||||||||||||||||||||||||
| Game Mode: | Creative | ||||||||||||||||||||||||||||||||||||||||
| Description |
|
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...: What actually happened was...: Steps to Reproduce: All other commands and testfor arguments work perfectly for me. Edit: |
| Comments |
| Comment by KingSupernova [ 17/Mar/15 ] |
|
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. |
| Comment by Ethan L! [ 22/Jan/15 ] |
|
Yup, I'm having the same basic issue. Mojang's gotta' fix this. |
| Comment by Steven Valenski [ 02/Nov/13 ] |
|
mine was forced onto this and marked as resolved >_> so I'll probably just make a new one Edit: new ticket |
| Comment by Ferdinand B. [ 02/Nov/13 ] |
|
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 |
| Comment by Steven Valenski [ 02/Nov/13 ] |
|
thank you Ferdinand B., I thought no one was going to notice this just because it's already been written off |
| Comment by Ferdinand B. [ 02/Nov/13 ] |
|
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 Examples:
|
| Comment by Steven Valenski [ 02/Nov/13 ] |
|
A screenshot of my location, the command used and the return I get when attempting to use it. |
| Comment by Steven Valenski [ 02/Nov/13 ] |
|
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. |
| Comment by Steven Valenski [ 31/Oct/13 ] |
|
please update to include affects versions 1.7.2 and mark it as re-opened |
| Comment by Steven Valenski [ 31/Oct/13 ] |
|
tested a couple more commands /tell and /testfor are also not responding to location arguments correctly |
| Comment by Steven Valenski [ 31/Oct/13 ] |
|
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 |
| Comment by Steven Valenski [ 30/Oct/13 ] |
|
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 |
| Comment by Steven Valenski [ 30/Oct/13 ] |
|
can someone update this to affects 1.7.2? |
| Comment by Steven Valenski [ 30/Oct/13 ] |
|
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 |
| Comment by Steven Valenski [ 30/Oct/13 ] |
|
Just realized I have another couple command blocks with similar code but they do work..... |
| Comment by Steven Valenski [ 30/Oct/13 ] |
|
I have had similar issues as well but mine was looking for a person to TP for example Edit: to be more clear this was actually tested with an effect command, /tp still does not work |
| Comment by Ferdinand B. [ 05/May/13 ] |
|
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> The way it works is this: testfor <playername> If you do an @-notation with arguments [x,y,z] then it will search from that location but the radius will still be infinite. 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] |
| Comment by Tails [ 17/Mar/13 ] |
|
Search radius is always required when using specific coordinates. |
| Comment by Tails [ 17/Mar/13 ] |
|
Please do not mark issues as private, unless your bug report is a security issue containing information that may compromise your server/client. |
| Comment by Evan B [ 17/Mar/13 ] |
|
Is that necessary? And why is that necessary if I specify the coordinates? |
| Comment by Tails [ 17/Mar/13 ] |
|
You haven't provided a search radius. |