MC-268045The name of Entity Argument is plural in Query literal node of Experience command
Description of issue
The command with issue is (experience|xp) query <targets> (levels|points) and it affects since 17w45a, includes April Fools' Joke snapshots and many experimental versions.
Steps to reproduce
When executing the command, if you forward any multiple player to the Entity Argument (a.k.a. Target Selector) named "targets", then you can see the message "Only one player is allowed, but the provided selector allows more than one", which keyed "argument.player.toomany". A single player is required, but the argument name is plural, such as targets.
Expected result
It's make sense to rename targets to singular, like target or player because it affects only a player.
Attachments
Attachment 1
Internal Minecraft source code which have the issue in Yarn mapping, 1.20.4.
You can see that "targets" was used with EntityArgumentType.player(), not players(). You can also ignore the red underline.
Attachment 2
In-game screenshot in 17w45a which the issue starts.
![[Mod] Jiingy](../../../data/avatars/users/91802.png){kind=small}
Created Issue:
The name of Entity Argument is plural in Query literal node of Experience command
Description of issue
The command with issue is (experience|xp) query <targets> (levels|points) and it affects since 17w45a, includes April Fools' Joke snapshots and many experimental versions.
Steps to reproduce
When executing the command, if you forward any multiple player to the Entity Argument (a.k.a. Target Selector) named targets, then you can see the message "Only one player is allowed, but the provided selector allows more than one", which keyed "argument.player.toomany". A single player is required, but the argument name is plural, such as targets.
Expected result
It's make sense to rename targets to singular, like target or player because it affects only a player.
Attachments
Attachment 1
Internal Minecraft source code which have the issue in Yarn mapping, 1.20.4.You can see that "targets" was used with EntityArgumentType.player(), not players(). You can also ignore the red underline.
Attachment 2
In-game screenshot in 17w45a which the issue starts.
Attachments2
![[Bot] Arisa](../../../data/avatars/users/43007.png){kind=small}
Description of issue
The command with issue is (experience|xp) query <targets> (levels|points) and it affects since 17w45a, includes April Fools' Joke snapshots and many experimental versions.
Steps to reproduce
When executing the command, if you forward any multiple player to the Entity Argument (a.k.a. Target Selector) named targets, then you can see the message "Only one player is allowed, but the provided selector allows more than one", which keyed "argument.player.toomany". A single player is required, but the argument name is plural, such as targets.
Expected result
It's make sense to rename targets to singular, like target or player because it affects only a player.
Attachments
Attachment 1
Internal Minecraft source code which have the issue in Yarn mapping, 1.20.4.You can see that "targets" was used with EntityArgumentType.player(), not players(). You can also ignore the red underline.
Attachment 2
In-game screenshot in 17w45a which the issue starts.
Description of issue
The command with issue is (experience|xp) query <targets> (levels|points) and it affects since 17w45a, includes April Fools' Joke snapshots and many experimental versions.
Steps to reproduce
When executing the command, if you forward any multiple player to the Entity Argument (a.k.a. Target Selector) named targets, then you can see the message "Only one player is allowed, but the provided selector allows more than one", which keyed "argument.player.toomany". A single player is required, but the argument name is plural, such as targets.
Expected result
It's make sense to rename targets to singular, like target or player because it affects only a player.
Attachments
Attachment 1
Internal Minecraft source code which have the issue in Yarn mapping, 1.20.4.You can see that "targets" was used with EntityArgumentType.player(), not players(). You can also ignore the red underline.
Attachment 2
In-game screenshot in 17w45a which the issue starts.
Description of issue
The command with issue is (experience|xp) query <targets> (levels|points) and it affects since 17w45a, includes April Fools' Joke snapshots and many experimental versions.
Steps to reproduce
When executing the command, if you forward any multiple player to the Entity Argument (a.k.a. Target Selector) named targets, then you can see the message "Only one player is allowed, but the provided selector allows more than one", which keyed "argument.player.toomany". A single player is required, but the argument name is plural, such as targets.
Expected result
It's make sense to rename targets to singular, like target or player because it affects only a player.
Attachments
Attachment 1
Internal Minecraft source code which have the issue in Yarn mapping, 1.20.4.You can see that "targets" was used with EntityArgumentType.player(), not players(). You can also ignore the red underline.
Attachment 2
In-game screenshot in 17w45a which the issue starts.
Description of issue
The command with issue is (experience|xp) query <targets> (levels|points) and it affects since 17w45a, includes April Fools' Joke snapshots and many experimental versions.
Steps to reproduce
When executing the command, if you forward any multiple player to the Entity Argument (a.k.a. Target Selector) named targets, then you can see the message "Only one player is allowed, but the provided selector allows more than one", which keyed "argument.player.toomany". A single player is required, but the argument name is plural, such as targets.
Expected result
It's make sense to rename targets to singular, like target or player because it affects only a player.
Attachments
Attachment 1
Internal Minecraft source code which have the issue in Yarn mapping, 1.20.4.You can see that "targets" was used with EntityArgumentType.player(), not players(). You can also ignore the red underline.
Attachment 2
In-game screenshot in 17w45a which the issue starts.
Description of issue
The command with issue is (experience|xp) query <targets> (levels|points) and it affects since 17w45a, includes April Fools' Joke snapshots and many experimental versions.
Steps to reproduce
When executing the command, if you forward any multiple player to the Entity Argument (a.k.a. Target Selector) named "targets", then you can see the message "Only one player is allowed, but the provided selector allows more than one", which keyed "argument.player.toomany". A single player is required, but the argument name is plural, such as targets.
Expected result
It's make sense to rename targets to singular, like target or player because it affects only a player.
Attachments
Attachment 1
Internal Minecraft source code which have the issue in Yarn mapping, 1.20.4.You can see that "targets" was used with EntityArgumentType.player(), not players(). You can also ignore the red underline.
Attachment 2
In-game screenshot in 17w45a which the issue starts.
![[Mod] turbo](../../../data/avatars/users/92867.png){kind=small}
Low![[Mod] Michael Wobst](../../../data/avatars/users/37868.png){kind=small}
![[Mojang] slicedlime](../../../data/assets/gravatar/slicedlime.jpeg){kind=small}
[Mojang] slicedlime![[Bot] Piston](../../../data/avatars/users/31202.png){kind=small}
Can confirm in 24w04a. This behavior is irregular when compared to other commands which require a single target, such as '/data get entity ...'
Note:
Using @a[limit=1] can circumvent the warning.