[MC-52668] Player skulls UUID compatibility incomplete (NBT tag SkullOwner was of wrong type)

Bug #1: Skulls won't keep their item name.
Bug #2: Skulls always have the default Steve texture on mobs.

Steps for #1:
----------------
1. Take a custom skull, for example "/give @p 397 1 3 {SkullOwner:"MHF_ArrowUp"}". The inventory name says "MHF_ArrowUp's Skull" for now.

2. Place it on ground. The server generates the log entry: "Server thread/WARN: NBT tag SkullOwner was of wrong type; expected TAG_Compound, found TAG_String".

3. Take the placed skull back to inventory. The item name changes to "Head", though the custom skull still shows up if placed in-game again.

Steps for #2:
----------------
1. Summon a mob with a custom skull by using a command block. For example "/summon Skeleton ~ ~1 ~ {Attributes:[{Name:generic.movementSpeed,Base:0.001}],Equipment:[{},{},{},{},{Damage:3,id:397,tag:{SkullOwner:MHF_ArrowRight}}]}"

2. Once again, the server responds with "Server thread/WARN: NBT tag SkullOwner was of wrong type; expected TAG_Compound, found TAG_String"

3. The mob's head has the Steve texture instead of MHF_ArrowRight's head.

Comments 6

kumasasa 2014-04-09T18:50:11Z

/give @p skull 1 3 {SkullOwner:Dinnerbone}

-> Place head

[20:46:56 INFO]: Client> [20:46:56] [Server thread/INFO]: [Kumasasa: Given [Dinnerbone's Head] * 1 to Kumasasa]
[20:46:56 INFO]: Client> [20:46:56] [Client thread/INFO]: [CHAT] Given [Dinnerbone's Head] * 1 to Kumasasa
[20:46:59 INFO]: Client> [20:46:59] [Server thread/WARN]: NBT tag SkullOwner was of wrong type; expected TAG_Compound, found TAG_String

Rezzing (Adriana) 2014-04-11T11:44:57Z

Not trying to get on somebody's nerves lol but bug #2 (summon mobs with skulls) still shows up with a Steve texture. Plus, placing a skull for the first time, still generated the server log "NBT tag SkullOwner was of wrong type; expected TAG_Compound, found TAG_String".

Reproduce like this:
1. /give @p 397 16 3 {SkullOwner:"Rezzing"}
2. Place one on ground and the server generates an exception.
3. Pick it up again and it creates a new stack, which is not prone to log exceptions.

Nathan Adams 2014-04-11T11:48:37Z

Ignore the warning in the chat.

Items with SkullOwner:"xxx" are the "old" format and will need be turned into a proper blob, you can achieve this by placing it and picking it back up.

Rezzing (Adriana) 2014-04-11T11:59:00Z

Alrighty! In this case, I'll look forward to the updated knowledge base. Thank you.

lisa 2014-04-11T17:18:08Z

[Client thread/WARN]: NBT tag SkullOwner was of wrong type; expected TAG_Compound, found TAG_String
Occur in 1.7.8

Aaron Loyd 2014-04-11T18:05:48Z

@lisa The error message is not a bug.