mojira.dev
MC-268898

Head name component is too restrictive, breaking old and new player heads

Player Head Component "minecraft:profile={name:""} is too restrictive requiring no spaces/special characters and/or a character limit of 0-16. This bricks old player heads that have these use cases in the name field by stripping profile components completely.

This is typically used to keep the custom item name for a head where a player sets a custom value like `Spider` would display "Spider's Head" that would persist when placed down when they already have a custom texture.

How to Replicate:
+Working:
+

/give @s minecraft:player_head[minecraft:profile={name:"test"}]

+Not Working:

+

/give @s minecraft:player_head[minecraft:profile={name:"test test"}]
/give @s minecraft:player_head[minecraft:profile={name:"testtesttesttesttest"}]
/give @s minecraft:player_head[minecraft:profile={name:"test☺"}]

Β 

Linked issues

Attachments

Comments 5

Worth noting this is typically used instead of Item Name because MC-174496 causes item names to disappear when broken/placed.

This is WAI, but we have increased the prio of MC-174496 πŸ™‚Β 

Thank you for your report!
After consideration, the issue is being closed as Working as Intended.

Please note, that mechanics of the game may change between updates.
Things such as graphics, sounds, world creation, biomes, redstone, villagers, and animals may not work the same in current versions.

Full Version History – Snapshot Version History – The official Minecraft feedback site

Quick Links:
πŸ““ Bug Tracker Guidelines – πŸ’¬ Community Support – πŸ“§ Mojang Support (Technical Issues) – πŸ“§ Microsoft Support (Account Issues)
πŸ““ Project Summary – ✍️ Feedback and Suggestions – πŸ“– Game Wiki

I'd strongly urge that MC-174496 be fixed before 1.20.5 and that player heads with the name field having incorrect datasets be datafixed with "'s Head" appended to the end. If not this is a massive breaking change for many maps & datapacks that updating will break existing worlds with little to no workaround.

If this is breaking a world save from before 1.20.5, I'd recommend creating a new bug report, and providing a 1.20.4 world save that breaks or has issues when being upgraded to 1.20.5. This bug report focuses only on the behaviour in the current snapshot with the new command syntax, but not the world upgrade path.

Edit: There's now MC-268898

n1njag0

(Unassigned)

Confirmed

Commands

24w09a

Retrieved