To not cause a lot of lag every time they are loaded, player_head textures are saved offline. But even in situations when they should be queried online again, they often aren't.
One example, replace "FaRo1" with your own username:
1.
/setblock ~ ~ ~ player_head{ExtraType:"FaRo1"}
2. Close Minecraft and change your skin.
3. Reopen world.
Result: The skulls have not changed. They should have.
4.
/setblock ~1 ~ ~ player_head{ExtraType:"FaRo1"}
Result: The new skull also has the old texture. If the world was opened far away from the old skull, so that they were not loaded, this issue does not happen. Going back to it the old skull shows them with the new texture.
5.
/data modify block ~ ~ ~ Owner.Properties.textures[0] merge from block ~1 ~ ~ Owner.Properties.textures[0]
Result: Success message, even though both skulls look the same. Looking at the NBT of a new skull reveals that the string Owner.Properties.textures[0].Value
does actually differ (only a little bit in my test).
Changing the value of Owner.Properties.textures[0].Value
with commands also does not change the texture and setting, getting and comparing the value with other texture strings or regular strings has many inconsistencies, but I haven't found a clear pattern in any of that yet.
Thank you for your report!
We're tracking this issue in MC-68487, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 Game Wiki
-- I am a bot. This action was performed automagically! Please report any issues in Discord or Reddit