[MC-107164] Selector arguments without required argument key are treated as invalid

The bug

In the past you could use some arguments in selectors without providing the argument key, for example @a[0,0,0] would select players at x=0, y=0, z=0. Because of the fix of MC-106842 these arguments are now treated as invalid.

How to reproduce

Use the following command when you are not at 0, 0, 0:

/say @a[0,0,0,r=1]

In previous versions (pre 16w38a) it would only target players at 0, 0, 0 in a radius of 1. In 16w38a+ it targets players who are in a 1 block radius of the command block / entity running the command.

Linked issues

is duplicated by 2

MC-107850 Command coordinate arguments only accept values with x=, y=, z=, and r= in front, even if the values are the first four arguments Resolved

MC-110315 Target selector arguments x, y, z, r doesn't work alone. Resolved

relates to 1

MC-106842 Target selector stops parsing its arguments if an entry is not <argument>=<value> Resolved

Comments 2

[Mod] redstonehelper 2016-09-22T15:18:18Z

It's worth noting that if the coordinates are specified at the beginning of the arguments, r= can be omitted as well, so this does not only affect coordinates.

Erik Broes 2016-09-27T14:09:47Z

Removed ancient and (only slightly) shorter hacky version 😃