> For the complete documentation index, see [llms.txt](https://phantom-development.gitbook.io/phantom-development-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://phantom-development.gitbook.io/phantom-development-docs/phantom-series/phantom-armor-usd17.99/faq/items-adder-integration.md).

# Items-Adder Integration

{% hint style="warning" %}
**Note:** This is still in experimental stage, so there may be bugs, visual glitches & more.
{% endhint %}

Phantom Armor allows users to integrate their models / armor textures onto the armor very easily, and only requires the **Namspace,** **ID** & **Custom-Model-Data**  of the model / texture to do so. Here are some examples on how to put armor textures onto the set.

```yaml
Armor-Set:
  Physical-Settings:
    Helmet:
      #
      # BEWARE! Armor textures are only supported by the leather armor type and nothing else.
      # If you have your texture as anything else other than leather, it will NOT work.
      #  
      Material: 'LEATHER_HELMET'
      #
      # As you can see below, we can simply add a config string called "Namespace-ID"
      # and this will take the input Namespace:ID, however if you do not know the namespace.
      # You can try just the ID and it may work, but for correct usage use namespace:id
      #
      # You can easily get these details by holding the armor texture/model in your hand, and
      # running the command /iatag, this will give you the current held data of the item which
      # contains this information. 
      #
      Namespace-ID: "lunardragonset:lunar_dragonhelmet"
      # 
      Base64: 'eyJ0ZXh0dXJlcyI6eyJTS0lOIjp7InVybCI6Imh0dHA6Ly90ZXh0dXJlcy5taW5lY3JhZnQubmV0L3RleHR1cmUvOGMwZTdhYjc2NTk3MDdmZWE5NDA3MTE4MDA5MGI3ZDNiZjRlMTE2M2NhNjgxYzhmNGQ5YWY2MDkyNGFjMWRkNCJ9fX0='
      Display-Name: '#FF3423&lL#FF472A&lu#FF5A31&ln#FF6D38&la#FF803F&lr #FFA54D&lD#FFB854&lr#FFCB5B&la#FFDE62&lg#FFDA5C&lo#FFD657&ln #FFCD4C&lH#FFC946&le#FFC541&ll#FFC03B&lm#FFBC36&le#FFB830&lt'
      Lore:
        - '&8ᴀʀᴍᴏʀ'
        - '&7'
        - '&7&o When equipped, gain a &b&opickaxe boost'
        - '&7&o which will boost your pickaxe xp gain!'
        - '&7'
        - '#FF3423&lInformation'
        - ' #FFCB5B→ &7Type: #FF3423Pickaxe EXP'
        - ' #FFCB5B→ &7Amount: &f%boost_percent%% &8/ &f12.5%'
        - ''
        - '#FF3423&lProgression'
        - ' #FFCB5B→ &7Level: &f%level% &8/ &f%maxlevel%'
        - ' #FFCB5B→ &7Experience: &a%exp% &8/ &c%exp_required%'
        - ' #FFCB5B→ &7Progress: %progress_bar% &a%progress_percent_decimal%'
        - ''
        - '&7&o(( &fBreak Blocks &7to level this armor up! &7&o))'
      #
      # Please make sure that your custom-model-data is correct, or else it will not work
      # correctly and cause some visual bugs, you can get the custom-model-data by running
      # the command /data get entity @SelectedItem which will contain it. Or use the ia command.
      #
      Custom-Model-Data: 12
```


---

# 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://phantom-development.gitbook.io/phantom-development-docs/phantom-series/phantom-armor-usd17.99/faq/items-adder-integration.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.