Upon trying to set a mannequin’s profile using {selector:”@p”} through either /summon or /data, the game will state that the command was completed. However, the mannequin’s profile will be reset to {} and the skin will default to whatever they were set to before (putting this for summon, setblock, or give defaults to Alex). Both a valid player username and {selector:”@p”} in the text space of a sign cannot be copied over either, resulting in the same empty profile field. I have not tested copying other data to the profile field of mannequins, however one can assume that any use of the /data command that does not specify an exact user name results in failure.
EDIT:
Player heads suffer from the same problem.
Comments 6
Commands that work correctly:
/data modify entity @e[type=minecraft:mannequin,sort=nearest,limit=1] profile set value Crazybomb101
/data modify block ~ ~ ~ profile set value Crazybomb101(~ ~ ~ is a player head)
Commands that don’t work:
/data modify entity @e[limit=1,type=minecraft:mannequin,sort=nearest] profile set from block ~1 ~-1 ~ front_text.messages[0]
(Sign message can be anything, from “Crazybomb101” to {selector:”@p”}. The line copied from the sign can also be any line.)
/give @s minecraft:player_head[profile={selector:"@p"}] 1
(Results in unnamed Alex head)
/setblock ~ ~ ~ minecraft:player_head[
Oh, these also don’t work:
/setblock ~ ~ ~ minecraft:player_head{profile:{selector:"@p"}}
/data modify block ~ ~ ~ profile set from block ~1 ~-1 ~ front_text.messages[0]
/data modify block ~ ~ ~ profile set value {selector:”@p”}
Specifically for the player heads, this results in the skin being reset to Alex.
To get the sign command to work, use front_text.messages[0].extra[1]
selector directly in profile is a feature request
Please provide the full and exact commands used