When the tag contains capital letters the command will not be executed.
The following command can be successfully executed correctly in 1.12.2.
This command should summon a husk.
/summon Husk ~ ~ ~This command should give you a stone.
/give @p Stone 1The husk should be holding a stone when summoned.
/summon husk ~ ~ ~ {HandItems:[{id:Stone,Count:1},{}]}The husk should be holding a stone when spawned.
1.12.2:
/setblock ~ ~ ~ minecraft:mob_spawner 0 replace {SpawnData:{id:"husk",HandItems:[{id:Stone,Count:1},{}]}}
18w05a:
/setblock ~ ~ ~ minecraft:mob_spawner{SpawnData:{id:"husk",HandItems:[{id:Stone,Count:1},{}]}} replaceThis command caused the
.
1.12.2:
/setblock ~ ~ ~ minecraft:mob_spawner 0 replace {SpawnData:{id:"Husk"}}
18w05a:
/setblock ~ ~ ~ minecraft:mob_spawner{SpawnData:{id:"Husk"}} replace
Linked issues
relates to 2
Attachments
Comments 5
The Wiki is not an official source, it is run by volunteers who are describing the current state only.
Yes, I forgot to mention that the way the game handles capital letters when creating error messages is still an issue, but eliminating/reducing the use of capital letters in the "minecraft:" namespace seems to be the direction that Mojang is heading in, in which case it would be intentional that the above commands don't execute (this is only based on observations, the developers will ultimately decide whether or not this is intentional).
Perhaps you should update the description of the ticket, because "the command will not be executed(correctly)" seems too vague and doesn't really explain what the actual issue is. Did you mean that the errors given by these commands are the issue, or is it the fact that these commands no longer work? This is just for clarity and to make sure that the issue of capital letters missing in error messages doesn't get overlooked.
It is intentional. The developers already decided. They even say so in the changelog: https://minecraft.net/de-de/article/minecraft-snapshot-17w45a#commands
Most commands are even more case sensitive than before. Lowercase is preferable wherever possible.
For example, this is no longer allowed:
{color:red}/scoreboard ObJeCtIvEs ...{color}They will be so much more faster and efficient. Especially functions. Oh man.
It's all to make the command parser more efficient.
I believe that uppercase letters are no longer acceptable for entity, block, and item names in the latest snapshots. Most commands will now be case sensitive and will require lowercase letters.
From the 1.13 wiki:
Commands and functions are much faster and more efficient.
Most commands are now more case-sensitive. Lowercase is preferable wherever possible.
For example, this is no longer allowed: /scoreboard ObJeCtIvEs ...
The same applies to entity, block, and item names, where /summon HuSK ~ ~ ~, which worked in 1.12.2, will no longer work in 1.13.
The game does however give the correct tab completion when typing /summon Husk, showing the name as "minecraft:husk".
If you can't provide more information as to why this is a bug, then I would say this is WAI.