> For the complete documentation index, see [llms.txt](https://itemsadder.devs.beer/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://itemsadder.devs.beer/adding-content/items/item-properties/2d-icon.md).

# 2D Icon

{% hint style="warning" %}
This is made for clients with version lower than 1.21.4.

ItemsAdder 4.0.13+ and Minecraft 1.21.4+ support a new way of making 2D icons.\
[Read more here](/adding-content/items/modern-items-creation.md#icon).
{% endhint %}

{% hint style="warning" %}
This feature requires Minecraft 1.21.2 clients or greater (server version is not important).

To support older clients refer to the other tutorials:

* [block 2d icon](/adding-content/blocks/block-2d-icon.md)
* [furniture 2d icon](/adding-content/furnitures/furniture-2d-icon.md)
  {% endhint %}

## The `icon` property

You have just to set the icon property to a valid texture path.\
You are done!

### Example

```yaml
info:
  namespace: test
items:
  obsidian_trident:
    name: Obsidian Trident
    resource:
      generate: false
      model_path: item/obsidian_trident
      material: TRIDENT
      icon: item/obsidian_trident
```

{% hint style="info" %}
NOTE:

Both the model `item/obsidian_trident` and the texture `item/obsidian_trident` have the same name, but they are a different file.

They have the same name just to make things more organized.

In this example:

* `item/obsidian_trident` is `contents/test/models/item/obsidian_trident.json`
* `item/obsidian_trident` is `contents/test/textures/item/obsidian_trident.png`
  {% endhint %}

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


---

# 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, and the optional `goal` query parameter:

```
GET https://itemsadder.devs.beer/adding-content/items/item-properties/2d-icon.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.