[MC-552] Command block choosing wrong people / Selecting players cross-dimensional

When using @p for command blocks (in the overworld is the only one tested), if there is no closest player (easier to do with the radius) it will take someone from the nether or the end instead.

Comments 17

spetznack 2012-11-10T23:00:25Z

Yes, I have the exact same issue with the_end, also on bukkit servers with multiverse (which enables us to create more worlds than the original 3 vanilla worlds) we are having the same problem there. :/ For me this is a BIG PROBLEM, it makes command blocks in a adventure world teleport people from survival world!!

spetznack 2012-11-10T23:13:21Z

How to simply replicate:
1. Requires two players
2. Make a command block at coordinate 0 100 0 in overworld
3. Type in this: /tp @p 0 120 0
4. Get 2.nd player in creative and tp him to 0 100 0 in the nether.
5. 1.st player should stand a couple blocks away from the command block and the activate it.

What will happen:
Bascily the server will search the coordinates for the closest player to the search area, no matter what world he is in.

With this exact command it will tp the 2.nd player from 0 100 0 to 0 120 0 even if the command block is in another world than the 2.nd player..

Black Sheep 2012-11-10T23:16:38Z

Need this fixed.

David Cohoe 2012-11-11T00:32:06Z

It also still works even if the player in the nether is thousands of blocks away from area it is searching at.

spetznack 2012-11-11T01:51:03Z

This is not only a problem with /tp commands, it's the general @p that is not world sensitive, tested it out with @r and @a, it's the same with them aswell.. :/

7 more comments

gareth taylor 2012-12-18T23:34:41Z

This is a very severe issue for me! I need to be able to use large search areas for my tp commands, right now it is making people in other worlds teleport to death! Please do something to fix this issue.

Anon Ymus 2012-12-18T23:47:57Z

I think a fix would be to add a dIMENSION parameter (for example, /tp @p [ d=0 ] 0 100 0).

spetznack 2013-01-07T21:14:51Z

That is a very good idea, although we would still want it to be default at the world the command block is in right? (not super important but it would make things easier ^^)

Michael Irvine 2013-01-07T21:26:55Z

would it be in the parameters though? Like instead of being /tp@pd=0 0 100 0, perhaps it could be /tp @p [d=0] 0 100 0. Then it would fit in with all the other perameters. If you didn't put this in, like spetznack said, it would do the world that the command block is in.

spetznack 2013-01-07T21:42:54Z

the @?(search arguments) defines where the command block will search for players.
Basicly the "@?(search arguments)" will replace itself with the player(s) it found through the search parameter.

so for example:
/spawnpoint @a(0,100,0)
will look like this if the search only chooses one player: (in this case me)
/spawnpoint spetznack

adding a dimension parameter to the /command itself will not affect the way players are chosen 😉 At least that's what sounds logical to me ^^

spetznack 2013-01-31T07:09:17Z

This problem is now fixed for craftbukkit. Commandblocks only selects players in the same world that the commandblock is in. Tested it yesterday and it works 🙂

Tails 2013-03-14T03:10:19Z

Is this still a concern in the current Minecraft version? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.

Ryan Leach 2013-03-20T12:59:35Z

> This problem is now fixed for craftbukkit.

This is not bukkits JIRA, a fix in craftbukkit does not necessarily mean it has been fixed for vanilla.

spetznack 2013-03-21T11:08:06Z

@Ryan Leach
Sorry for not being more specific, the problem is fixed for bukkit servers now. Here is the bug-tracker:https://bukkit.atlassian.net/plugins/servlet/mobile#issue/view/BUKKIT-3515

The problem exists in vanilla 1.4.7, I will try to start a 1.5 vanilla server and test it out with someone later today..

spetznack 2013-03-24T15:49:24Z

Just tested for 1.4.7 and 1.5, the command blocks is still selecting players cross-dimentional.

Here is the setup: http://i.imgur.com/CE0q1Zb.jpg
One person stood right next to the command block in Overworld and pressed it while I was in nether (I also tried in The End, same result).

Nathan Adams 2013-06-14T09:50:27Z

Player selectors with the following arguments will ensure that the resulting player(s) are on the same world:

Range minimum
Range maximum
X coordinate
Y coordinate
Z coordinate

spetznack 2013-06-16T19:04:21Z

in other words, @a will select ALL players on the server but if you add one of those arguments for example

@a[r=50]

it will only select people within that radius in that world* right?