Datapack Codex

Data component format/profile

Minecraft Wiki article. Categories: Information_needed, Top-level_data_pages

📌 Mirrored from Minecraft Wiki

This article is reproduced from Data component format/profile on the Minecraft Wiki. Mirrored from revision 3437136. It is licensed CC BY-NC-SA 3.0 by the Minecraft Wiki contributors — not under the Codex’s CC BY-SA 4.0, and it may not be used commercially. Edits belong upstream, not here.

    • [String][NBT Compound / JSON Object] minecraft:profile: Provides the textures needed for rendering player models (player head blocks, player head item models, and mannequins) and player face sprites. Each texture can be provided either as the namespaced path to a texture in a resource pack, or from a player profile. A player profile can be specified either as player information whose profile properties must be requested on the fly, or a list of already-resolved profile properties.
    • If specified as a string, it corresponds to [String] name.
    • If present on a player head item, and the [String] name field is specified, the base item name is overridden as "name's Head".
    • If present on any item, exactly one of either [String] name or [Int Array] id is specified, and [NBT List / JSON Array] properties is not specified, a gray "Dynamic" text is shown in the item's tooltip.
      • [String] name: A username with a maximum length of 16, and only consisting of username-allowed characters​[more information needed]. If no other profile fields are specified, this is used to dynamically request the profile of a player with that username from Mojang's servers. Once received, that profile's properties (such as its skin, cape, and elytra textures) can be used for rendering. If the profile does not exist, a random default skin is provided. Optional.
      • [Int Array] id: A UUID. If no other profile fields are specified, this is used to dynamically request the profile of a player with that UUID from Mojang's servers. Once received, that profile's properties (such as its skin, cape, and elytra textures) can be used for rendering. If the profile does not exist, a random default skin is provided. Optional.
      • [NBT List / JSON Array] properties: A non-empty list of user profile properties. If this is specified, the dynamic profile fields are ignored, and a custom profile with these properties is used instead. If set to an empty list, the field is removed rather than invalidating the whole component. Optional.
        • [NBT Compound / JSON Object]: A single property.
          • [String] name: The name of the property. Can only be "textures".
          • [String] value: The texture data json, encoded in base64.
          • [String] signature: Optional. Mojang's signature of the value, encoded in base64.
      • [String] texture: Namespaced path to a player skin texture, relative to the textures folder in a resource pack. If specified, this texture is used when rendering a player model or skin, overriding the skin texture provided by a profile. This skin texture may have transparent pixels on the inner body layers whereas resolved skins' are always opaque. If omitted and no skin is provided by a profile, the slim Alex skin is used (minecraft:entity/player/slim/alex). Optional.
      • [String] cape: Namespaced path to a cape texture, relative to the textures folder in a resource pack. If specified, this texture is used when rendering a cape, overriding the cape texture provided by a profile. If the resolved profile (or lack thereof) does not have a cape, it will gain one. This does not affect the elytra texture. If Optional.
      • [String] elytra: Namespaced path to an elytra texture, relative to the textures folder in a resource pack. If specified, this texture is used when rendering an elytra, overriding the elytra texture provided by a profile. This does not affect the cape texture. If omitted and no elytra texture is provided by a profile, the normal elytra texture is used (minecraft:entity/equipment/wings/elytra). Optional.
      • [String] model: The type of player model to use. Either "wide" or "slim". If specified, this overrides the model type provided by a profile. If omitted and no model type is provided by a profile, a slim model type is used. Optional.

Sources