# Player Heads

## Overview

ArenaLegends head values are parsed through XERLib's `HeadBuilder`.

The current supported formats are:

* `uuid-><uuid>`
* `custom-><base64>`
* direct texture URL starting with `http`
* a short `textures.minecraft.net` texture ID

***

## Supported Formats

### UUID Owner

```yaml
head: "uuid->550e8400-e29b-41d4-a716-446655440000"
```

This uses the owning player by UUID.

### Raw Base64

```yaml
head: "custom->eyJ0ZXh0dXJlcyI6..."
```

### Direct Texture URL

```yaml
head: "https://textures.minecraft.net/texture/8a29a81f777e847932961125122b6a61b1e294aaa0f24ab7657bc0f8d01986ba"
```

### Texture ID Only

```yaml
head: "8a29a81f777e847932961125122b6a61b1e294aaa0f24ab7657bc0f8d01986ba"
```

***

## Important Note

Older examples that use `player->Name` are outdated for the current codebase.

If you need a real player owner, use the UUID form instead.

***

## Where Heads Are Used

Head values appear in many places, for example:

* menu icons
* dummy skin icons
* cosmetic previews

Because of that, broken head values often show up as menu issues rather than obvious startup errors.

***

## Related Pages

* [Item Builders](https://xerickerspigot.gitbook.io/arenalegends/menus/item-builders)
* [Cosmetics](https://xerickerspigot.gitbook.io/arenalegends/features/cosmetics)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://xerickerspigot.gitbook.io/arenalegends/menus/player-heads.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.