MC-121739Normal players can use player selectors in /msg command
The bug
Since 17w45a's command update, non-op players can use selectors in the /msg command as recipient and in the message. This appears to be the only affected command.
This allows disconnecting other players if the message exceeds the maximum length of a string in a packet.
Also note that a survival player can now simply run /msg @s @e to view all entities, quantify their search with selector arguments, etc. Obviously a non-operator should not have access to this information.
Linked Issues
![[Mod] Pokechu22](../../../data/avatars/users/92931.png){kind=small}
![[Mojang] Bartosz Bok](../../../data/avatars/users/10122.svg){kind=small}
Created Issue:
Normal players can use player selectors
Since 17w45a's command update, normal players can again use selectors. An example of this is /tell @p @e, which will disconnect the sending player due to exceeding the max chat message length.
Environment
Ubuntu 12.04 64bit
Java HotSpot(TM) 64-Bit Server VM (build 23.7-b01, mixed mode)
Ubuntu 12.04 64bit
Java HotSpot(TM) 64-Bit Server VM (build 23.7-b01, mixed mode)
clones
Normal players can use player selectors in /msg command
Since 17w45a's command update, no
rmalplayers canagainuse selectors. An example of this is/tell @p @e, which will disconnect the sending player due to exceeding the max chat message length.
![[Mod] tryashtar](../../../data/avatars/users/41963.png){kind=small}
The bug
Since 17w45a's command update, non-op players can use selectors in the /msg command as recipient and in the message. This appears to be the only affected command.
This allows disconnecting other players if the message exceeds the maximum length of a string in a packet.
Also note that a survival player can now simply run /tell @p @e to view all entities, quantify their search with selector arguments, etc. Obviously a non-operator should not have access to this information.
relates to
relates to
The bug
Since 17w45a's command update, non-op players can use selectors in the /msg command as recipient and in the message. This appears to be the only affected command.
This allows disconnecting other players if the message exceeds the maximum length of a string in a packet.
Also note that a survival player can now simply run /
tell@p@e to view all entities, quantify their search with selector arguments, etc. Obviously a non-operator should not have access to this information.The bug
Since 17w45a's command update, non-op players can use selectors in the /msg command as recipient and in the message. This appears to be the only affected command.
This allows disconnecting other players if the message exceeds the maximum length of a string in a packet.
Also note that a survival player can now simply run /msg @s @e to view all entities, quantify their search with selector arguments, etc. Obviously a non-operator should not have access to this information.
![[Mojang] Nathan Adams](../../../data/assets/gravatar/dinnerbone.png){kind=small}
[Mojang] Nathan Adamsis duplicated by
Re-resolving as fixed (in the version it was originally fixed in) in favor of creating a clone issue, MC-121739.
Came back at some point (for the "recipient" parameter), currently an issue in 18w22c.