Command argument validation does not work for entity id in /summon
The bug
Command argument validation does not work for the entity id for the /summon command. It appears to treat any value as valid. However, entity ids are validated when used in selectors.
How to reproduce
Copy the following in the chat
/summon non-existent
→ "non-existent" is colored, indicating that it is considered a valid value
Created Issue:
Command argument validation does not work for entity id in /summon
The bug
Command argument validation does not work for the entity id for the /summon command. It appears to treat any value as valid. However, entity ids are validated when used in selectors.
How to reproduce
Copy the following in the chat
/summon non-existent→ "non-existent" is colored, indicating that it is considered a valid value
Added Labels: command-syntax-help
Changed Summary:
Command argument validation does not work for entity id in /summon and /effect
Changed Summary:
Command argument validation does not work for entity id in /summon and effect ids in /effect
Added Affects Versions: 17w46a
Added Affects Versions: 17w50a
Added Affects Versions: 18w01a
Changed Summary:
Command argument validation does not work for entity id in /summonand effect ids in /effect
Added Affects Versions: 18w02a
Added Affects Versions: 18w03b
Added Affects Versions: 18w09a
Added Assignee:
[Mojang] Nathan Adams
Added Affects Versions: 18w16a
Added Affects Versions: 1.13-pre3
Added Fixed Versions: 1.13-pre6
@ZockerAxel please create a separate report for this if it has not been reported yet.
Reported it as MC-121861 now
effects in /effect are also not validated
ZockerAxel At least in 18w01a, this is not true
Can confirm this bug for /summon for 18w01a, tho.
confirmed for 18w09a