> For the complete documentation index, see [llms.txt](https://wiki.mypet-plugin.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.mypet-plugin.com/mypet-3/setup/configurations/configitems.md).
# Custom-Item-Data in Config
It is possible to set the `item data` (like wool color) and `NBT data` (like enchantments, name and lore) for items in the MyPet config.
You have to provide the Item properties in this order:
* `1.13-Item-ID` `NBT-Data`
Example:
{% tabs %}
{% tab title="1.13" %}
`beef {display:{Name:"Wolf Food",Lore:["Tasty wolf food","Tastes like banana"]}}`
{% endtab %}
{% tab title="1.14" %}
`beef {"display":{"Name":"[{\"text\":\"Wolf Food\"}]","Lore":["{\"text\":\"Tasty wolf food\"}","{\"text\":\"Tastes like banana\"}"]}}`
{% endtab %}
{% endtabs %}
When you set the food of the wolf to this, a player needs an item that is like in this picture: 
This will allow server owners to set the food and leash items (and some other items used by MyPet) to items that can only be obtained by shops etc.
## Item generators
You can create any item you want but sometimes MyPet will not recognize these items. This happens because the item comparison is very harsh in MyPet. To make it easier to setup config items the plugin now has the `/petadmin info item` command. This command will output the item you are currently holding in your main hand to the server logs (don't copy from console). Copy and paste this output to your config and it should work fine.
You can use item generators from various site like these:
*
*
*
Just copy the generated command and remove the `/give @a`.
## NBT data
The syntax for the NBT data is the same like in the `/give` command in *Minecraft*. You can find all possible NBT properties [here](http://www.minecraftwiki.net/wiki/Player.dat_Format#Item_structure) or just use one of the generators from above.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://wiki.mypet-plugin.com/mypet-3/setup/configurations/configitems.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.