![]() attribute minecraft:generic.armor base set 5Ĭhanged from resource_location to resource argument type for the attribute argument.I just started looking at updating a datapack that adds head drops for all mobs ("more mob heads" from Vanilla Tweaks) to use the new format for UUIDs - an integer array instead of a hexadecimal string - and I've found that the loot tables work with either data format. The dropped player head has the correct texture either way and the SkullOwner Id is held in whichever format is given in the loot tables. I get the head textures from and I've noticed in the past that the Id is essentially a random number, not the UUID of the player whose skin was used to get the head texture in the first place and not consistent if you obtain the give command for the same texture twice. Hi, as the owner of I can hopefully give a satisfying answer: So, question for anyone who knows the internal workings of the game, is the SkullOwner Id totally irrelevant if the texture Value string is already provided and can it be omitted entirely in that case?Įdit to add: If I use /give minecraft:player_head to get a head without the pre-specified Id and texture value so that the game has to go and look them up, it generates the Id in the new format. ![]() ![]() The UUID is totally random, but it is necessary. We on Minecraft-Heads generate a random UUID with every new submitted head and save it since it's easier to save it then to generate it newly every time.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |