(udalovkorn) player_head like a helmet.

[sweet holly]

Hi everyone, I want to add custom helmets to the server (1.21.1) using the denizen script (I wanted to use player_head for display), but nothing works. There are no errors, but the helmet looks like Steve's head. Is this even possible? phoenix_helmet:
type: item

material: diamond_helmet

material: player_head
display name: "<gold>Шлем Бессмертия"
mechanisms:
skull_texture: "eyJ0ZXh0dXJlcyI6eyJTS0lOIjp7InVybCI6Imh0dHA6Ly90ZXh0dXJlcy5taW5lY3JhZnQubmV0L3RleHR1cmUvNGE4M2RkZjFkNTQ3ODg0NzA1YjFjMzg3OWMzMjU2NDMwZTc0YmVjOTU0ODU1MzBhMTUwNzViNmYwZGQxZTU0YiJ9fX0="
flags:
phoenix_item: true

[orchid depot]

(udalovkorn) player_head like a helmet.

[orchid depot]

Hi I'm AutoThreadBot! Don't mind me, I'll just be adding the helper team to this thread so they can see it. A human will get to you soon.

[glacial oak]

skull_texture isn't a mechanism, you're probably looking for

!m skull_skin

[rustic inlet]

Cannot Specify Searched Mechanism

Multiple possible mechanisms: ItemTag.skull_skin, LocationTag.skull_skin.

[glacial oak]

!m itemtag.skull_skin

[rustic inlet]

Mechanism: skull_skin

Sets the player skin on a player_head.
A head should have a Texture blob, the player's UUID, and the player's Name.
The most-correct input is UUID|Texture|Name.
You can alternately input Name|Texture|UUID and the order will be automatically corrected.
You can alternately input just a UUID, or just a Name, or just UUID|Texture, or just Name|Texture, and the missing data will be downloaded.
You can alternately input just a Texture and the remaining data will be filled as name "null" and UUID "000-...

Object

ItemTag

Input

ElementTag(|ElementTag(|ElementTag))

Tags

<ItemTag.skull_skin> Returns the UUID of the player whose skin a skull item uses. Note: Item must ...
<ItemTag.skin> Returns the UUID of the player whose skin a skull item uses. Note: Item must be a '...
<ItemTag.has_skin> Returns whether the item has a custom skin set. (Only for 'player_head's)

[languid stirrup]

!patchversion @sweet holly

[rustic inlet]

Info: patchversion

We support only the latest patch-version of Minecraft for any recent main version (and Mojang, Spigot, Paper, etc. all generally also follow the same rule).

"Patch version" means the last number in a version label, for example in 1.20.6, the main version is 1.20, and the patch version is .6.
So if 1.20.6 is the latest patch version, then 1.20.3, and 1.20(.0) are all outdated patch versions, and therefore are unsupported.

Note that we do still support recent older main versions (such as 1.19 and 1.18) so long as you are on the latest patch-version of those main versions (like 1.19.4 and 1.18.2).

See also CitizensWiki/Supported_versions

[sweet holly]

It's weird, I fixed the code, but it didn't improve. The helmet just became invisible and still no errors 🙁 phoenix_helmet:
type: item
material: player_head
display name: "<gold>Шлем Бессмертия"
mechanisms:
skull_skin: "eyJ0ZXh0dXJlcyI6eyJTS0lOIjp7InVybCI6Imh0dHA6Ly90ZXh0dXJlcy5taW5lY3JhZnQubmV0L3RleHR1cmUvNGE4M2RkZjFkNTQ3ODg0NzA1YjFjMzg3OWMzMjU2NDMwZTc0YmVjOTU0ODU1MzBhMTUwNzViNmYwZGQxZTU0YiJ9fX0="
attribute_modifiers:
generic_armor:
1:
key: immortal:armor_head
operation: ADD_NUMBER
amount: 4
slot: HEAD
generic_armor_toughness:
1:
key: immortal:toughness_head
operation: ADD_NUMBER
amount: 2
slot: HEAD
flags:
phoenix_item: true

[languid stirrup]

We do not support 1.21.1, please test on 1.21.11

Also provide

!info haste debug

[rustic inlet]

Info: haste

Help us help you by pasting your script to https://paste.denizenscript.com/New/Script and linking it back here.

Info: debug

If you need help with a script issue, one of the most powerful tools Denizen has to offer is full debug output. This is displaying in your console whenever scripts are running until you turn debug off. To share a debug log quickly and easily with helpers, simply run the command /denizen debug -r in-game to begin recording, then run through the part of the script you need help with, then run the command /denizen submit. This will give you a link to a paste of the debug log, which you can then copy/paste back to us!

[gritty sage]

Thread Closing Reminder

Has your issue been resolved, or your question been answered?
If so, please use the </resolved:1028673926114594866> command to close your thread.
Or </invalid:1028673926898909185> if it's not possible to resolve.

If not yet resolved, please reply below to tell us what you still need.

(Note that if there is no reply for a few days, this thread will eventually close itself.)

@sweet holly