> For the complete documentation index, see [llms.txt](https://docs.mantic.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mantic.dev/mantichoes/nexo-items.md).

# Custom items

Use Nexo, Oraxen or ItemsAdder items for ManticHoes tools, menu icons, custom drops and prestige requirements. Install the provider you use, along with ManticLib 1.0.53.3 or newer.

Custom items are optional. Leave the provider setting out or blank to keep your normal material or player head.

## Choosing a provider

Each item uses exactly one setting:

```yaml
nexo-item: ruby_hoe
# or
oraxen-item: ruby
# or
itemsadder-item: 'myitems:ruby'
```

Choose one provider per item. Mixing providers in the same entry is not supported.

The ID used for counts, requirements and placeholders depends on the provider:

| Setting                           | ID to use                 | Count placeholder                     |
| --------------------------------- | ------------------------- | ------------------------------------- |
| `nexo-item: ruby`                 | `ruby`                    | `{ruby_collected}`                    |
| `oraxen-item: ruby`               | `oraxen:ruby`             | `{oraxen_ruby_collected}`             |
| `itemsadder-item: 'myitems:ruby'` | `itemsadder:myitems:ruby` | `{itemsadder_myitems_ruby_collected}` |

Shorter aliases also work: `{ruby_collected}` for Oraxen and `{myitems_ruby_collected}` for ItemsAdder. Use the longer form when two providers reuse the same name. Replace `_collected` with `_sell` for prices.

## Tools

In `harvester-hoes.yml`, add the provider setting to an existing entry under `hoe-settings`:

```yaml
nexo-item: ruby_hoe
```

The item must use a supported hoe material, such as `DIAMOND_HOE`. The provider supplies the item and its model; ManticHoes keeps enchant levels, owner and autosell on the tool.

Keep your existing `display-name` and `lore` to show ManticHoes text. To keep the provider's own name and text instead, set:

```yaml
display-name: ''
lore: []
```

## Menu icons

In a menu item, add the provider setting:

```yaml
nexo-item: ruby_icon
```

This works for main-menu buttons, upgrades, disenchant items, prestige items, leaderboard buttons and shop icons. The item keeps its provider model instead of the menu's material, skull or custom-model number.

Use `display-name: ''` and `lore: []` to keep the provider's text, or enter your own to replace it. Changing a shop icon does not change its reward commands.

## Custom drops

In `custom-drops.yml`, add a drop for the crop you want to change:

```yaml
drops:
  - crop: WHEAT
    nexo-item: ruby
    sell-price: 12.5
```

The same entry works with `oraxen-item: ruby` or `itemsadder-item: 'myitems:ruby'`. For a normal item, use `material: DIAMOND` instead.

Use `drops: []` to keep all normal drops. A configured crop uses its custom drops instead of its normal item drops. Multiple entries for the same crop give multiple rewards, and harvest/drop boosters still affect the quantity. Wheat seed settings stay separate.

Custom rewards need their own positive `sell-price` to be sold automatically; otherwise players receive the item even when autosell is on. Keep `display-name` and `lore` out of the entry to keep the provider's original text and item data.

## Prestige limits

In `prestige.yml`, set `enabled: true` and add a rule to your existing `unlock-crops` list:

```yaml
unlock-crops:
  - prestige: 1
    nexo-item: ruby
```

Use the same provider and item as in the drop config. This reward unlocks at prestige 1 and stays unlocked at higher levels. For a normal item, use `material: DIAMOND` instead of the provider setting. Your existing crop restrictions still work.

## Show custom prices

In `menus/crop-prices.yml`, use `{ruby_sell}` for `nexo-item: ruby`:

```yaml
lore:
  - '&7Sell price: &a${ruby_sell}'
```

For Oraxen use `{oraxen_ruby_sell}`, and for ItemsAdder `{itemsadder_myitems_ruby_sell}`. A display name also works, such as `{silver_ruby_sell}` — lowercase it and replace spaces with underscores. These placeholders work in menu titles, item names and lore, and show the price of one item. Material placeholders such as `{diamond_sell}` also work.

## Custom reward counts

Use `{ruby_collected}` to show how many items the player has received, with the provider-prefixed forms above for Oraxen and ItemsAdder. `{ruby}` and `{ruby_harvested}` show the same count.

Counts include automatically sold items and are saved under `custom-collected` in player data. Tracking starts when the feature is installed; earlier rewards cannot be counted back. Normal crop totals keep working as before.

## Custom-item prestige requirements

In `prestige.yml`, add `custom-items` inside the level you want under `costs-and-requirements`. This example requires 100 Ruby items before prestige 2:

```yaml
costs-and-requirements:
  '2':
    custom-items:
      ruby: 100
```

Use the provider's exact ID: `ruby` for Nexo, `oraxen:ruby` for Oraxen, `itemsadder:myitems:ruby` for ItemsAdder. Use the same capitalization as the drop entry. You can list several items; the player must meet every requirement.

These are lifetime counts, including automatically sold rewards. A reward stack of three adds three. Prestiging does not take items or reset the counts. Show progress in prestige-menu lore with:

```yaml
lore:
  - '&7Ruby: &f{ruby_collected}&7/&a{prestige_required_custom_ruby}'
```

## Apply changes

Run `/mantichoes reload` after editing files, or edit existing custom-drop entries through `/mantichoes editor` under Custom Drops. If an item does not appear, check that the provider is installed, finished loading, and contains that exact item name. The server console identifies missing items.
