> For the complete documentation index, see [llms.txt](https://jugandomiguel.gitbook.io/custom-resource-pack-geysermc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://jugandomiguel.gitbook.io/custom-resource-pack-geysermc/last-steps/inventory-texture.md).

# Inventory Texture

If you already finished the creation of your custom things and the custom mappings you can continue following this part

***

To start go to your resource pack in this path `MyAmazingResourcePack/textures` and create a new file named **item\_texture.json**.

<figure><img src="/files/EZbWEfPyMg6V1uS1wQal" alt=""><figcaption></figcaption></figure>

Inside the file put this next code

```json
{
  "resource_pack_name": "im a resource pack",
  "texture_name": "atlas.items",
  "texture_data": {
    "name_of_your_custom_thing": {
      "textures": "textures/items/im_a_texture"
    }
  }
}
```

With this code we are selecting which texture we are going to use in the item for the inventory display. So lets fill it, in `"resource_pack_name": ""` we put any name of our preference, this don't need to match with the name in the [**manifest.json**](/custom-resource-pack-geysermc/general/manifest.md)

```json
{
  "resource_pack_name": "Im a beautiful resource pack",
  "texture_name": "atlas.items",
  "texture_data": {
    "name_of_your_custom_thing": {
      "textures": "textures/items/im_a_texture"
    }
  }
}
```

Then we are going to define the texture, first you need to put the identifier of your item without `geyser_custom:`. To avoid problems make the identifier the same name as the texture, in Minecraft Java put the identifier name as the texture name too.

```json
{
  "resource_pack_name": "Im a beautiful resource pack",
  "texture_name": "atlas.items",
  "texture_data": {
    "ice_helmet": {
      "textures": "textures/items/ice_helmet"
    }
  }
}
```

{% hint style="info" %}
Here don't matter if you are making a item/armor or what ever because you are only saying the textue on the inventory
{% endhint %}

To define more than 1 texture you can add a coma and put the same format, like this:

```json
{
    "resource_pack_name": "Im a beautiful resource pack",
    "texture_name": "atlas.items",
    "texture_data": {
        "ice_helmet": {
            "textures": "textures/items/ice_helmet"
        },
        "ice_chestplate": {
            "textures": "textures/items/ice_chestplate"
        },
        "ice_leggings": {
            "textures": "textures/items/ice_leggings"
        },
        "ice_boots": {
            "textures": "textures/items/boots"
        }
    }
}
```

With this you are done with the textures, you can continue with the next

{% content-ref url="/pages/UhXZ5ssyen9ZSBx1DqCo" %}
[Compressing the texture](/custom-resource-pack-geysermc/last-steps/compressing-the-texture.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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://jugandomiguel.gitbook.io/custom-resource-pack-geysermc/last-steps/inventory-texture.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.