> For the complete documentation index, see [llms.txt](https://1robie.gitbook.io/recipebook/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://1robie.gitbook.io/recipebook/plugin-integrations/integration.md).

# Integration Overview

RecipeBook supports integration with many popular Minecraft plugins for custom items, placeholders, and more. This guide explains how to use these integrations for the best experience.

***

## ItemsAdder Integration

RecipeBook fully supports ItemsAdder custom items in recipes, menus, and storage.

* **Item Syntax**: Use `itemsadder:<item_id>` in your YAML files.

  ```yaml
  result:
    item: "itemsadder:magic_sword"
  ingredients:
    A:
      item: "itemsadder:magic_gem"
  ```
* **Tips**:
  * Make sure ItemsAdder is loaded before RecipeBook.
  * Use the correct item IDs (check `/ia items list` or ItemsAdder documentation).
* **Troubleshooting**:
  * If items do not appear, check for typos or missing ItemsAdder resources.
  * Some custom textures may require a resource pack reload.

***

## Nexo Integration

Nexo custom items are supported in all RecipeBook features.

* **Item Syntax**: Use `nexo:<item_id>` in your YAML files.

  ```yaml
  result:
    item: "nexo:reinforced_stone"
  ingredients:
    S:
      item: "nexo:steel_ingot"
  ```
* **Tips**:
  * Ensure Nexo is installed and enabled.
  * Use the correct item IDs as defined in Nexo.
* **Troubleshooting**:
  * If items are not recognized, check for plugin conflicts or outdated configs.

***

## PlaceholderAPI Integration

RecipeBook supports PlaceholderAPI for dynamic text in menus, messages, and requirements.

* **Tips**:
  * Install PlaceholderAPI and any required expansions.
  * Reload placeholders with `/papi reload` if needed.
* **Troubleshooting**:
  * If placeholders show as raw text, check that PlaceholderAPI is installed and expansions are loaded.

***

## Custom Items (General)

RecipeBook can work with most custom item plugins that use unique item IDs.

* **Item Syntax**: Use the plugin prefix and item ID (e.g., `oraxen:custom_sword`, `zitems:super_pickaxe`).
* **Best Practices**:
  * Always check the correct item ID in the plugin's documentation and verify that the plugin shows it hooks to this plugin during startup.
  * Test recipes in-game to ensure compatibility.
* **Troubleshooting**:
  * If items are not recognized, check for typos, plugin load order, or missing dependencies.

***

## Eco Plugins Integration

RecipeBook supports all items plugins make by developer of Eco:

* **EcoItems**: Use `eco:ecoitems:<item_id>`
* **EcoArmor**: Use `eco:ecoarmor:set_<set>_<slot>`, `eco:ecoarmor:shard_<set>` or `eco:ecoarmor:crystal_<id>`
* **EcoCrates**: Use `eco:ecocrates:<crate>_key`
* **EcoMobs**: Use `eco:ecomobs:<id>_spawn_egg`
* **EcoPets**: Use `eco:ecopets:<id>_spawn_egg`
* **EcoScrolls**: Use `eco:ecoscrolls:scroll_<id>`
* **Reforges**: Use `eco:reforges:stone_<id>`
* **StatTrackers**: Use `eco:stattrackers:<id>`
* **Talismans**: Use `eco:talismans:<id>`

See the documentation [here](https://plugins.auxilor.io/all-plugins/the-item-lookup-system#using-items-from-eco-plugins)

***

## Other Plugin Support

RecipeBook is designed to be compatible with many other plugins, including:

* **Oraxen**: Use `oraxen:<item_id>`
* **zItems**: Use `zitems:<item_id>`
* **zHead**: Use `zhead:<item_id>`
* **ExecutableItems**: Use `ei:<item_id>`

For each, follow the same syntax and best practices as above.

***

If you encounter issues, see the [Troubleshooting](/recipebook/troubleshooting-and-support/common-issues.md) section or contact support.