mojira.dev
MC-301788

Mannequins with profile.name or profile.properties cannot be set to use a specific model

Mannequin models (slim/wide) cannot set the under the following conditions:

  • profile set to empty object

    • # Stuck at wide model
      {}
  • profile set to use a dynamic name

    • # Mirrors the state of the specified user
      {name: "ZenithKnight"}
  • profile set to properties

    • # Stuck at wide player
      {properties: [{name: "textures", value: "e3RleHR1cmVzOntTS0lOOnt1cmw6Imh0dHA6Ly90ZXh0dXJlcy5taW5lY3JhZnQubmV0L3RleHR1cmUvZDgzMjE4YTY5NDBlMGQ3MWZkMzY0ZDgwOTNjMjQ1YmI0ZmNhNDA5MWViOTE3ZDFhMGNkNzZmNzFhMzI4YzFlOCJ9fX0="}]}

In any of these cases, mannequins are unaffected by attempts to set the profile.model value

data modify entity @n[type=mannequin] profile.model set value "slim"
data modify entity @n[type=mannequin] profile.model set value "wide"

Linked issues

Comments 3

The profile nbt is either a mannequin profile or a profile component, meaning the model field does not exist when using the profile component format.

The wide/slim model is stored within the base64 properties itself and does indeed work when you use a resolved profile from a slim model.

Thank you for your report!
After consideration, the issue is being closed as Working as Intended.

Please note, that mechanics of the game may change between updates.
Things such as graphics, sounds, world creation, biomes, redstone, villagers, and animals may not work the same in current versions.

Full Version HistorySnapshot Version HistoryThe official Minecraft feedback site

Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki

If anyone stumbles across this in the future, this described behavior is now supported as of 1.21.9-pre1

ZenithKnight

(Unassigned)

Confirmed

(Unassigned)

25w36b

Retrieved