Item

This page explains how to configure custom items through a YAML section. This configuration is used for defining equipment, loot, or any other items that are dynamically created via configuration file

📄 YAML Example

Item Configuration
material: DIAMOND_SWORD
amount: 1
name: "&bMagic Sword"
lore:
  - "&7This sword holds great power."
  - "&eUse it wisely."
enchantments:
  - SHARPNESS;5
  - UNBREAKING;3
unbreakable: true
durability: 50
custom-model-data: 1234
item-flags:
  - HIDE_ATTRIBUTES
  - HIDE_ENCHANTS

🧱 Item Options

Option
Description

material

The material of the item. Can be a regular Minecraft material (like DIAMOND_SWORD) or a special item type (see below).

amount

Number of items to give. Can also be replaced dynamically using variables.

name

The custom display name of the item. Supports color codes using &.

lore

A list of text lines describing the item. Supports color codes and placeholders.

unbreakable

Makes the item unbreakable if set to true.

durability

Sets the durability or damage value of the item (not recommended for newer Minecraft versions).

custom-model-data

Used to assign custom textures via resource packs.

enchantments

A list of enchantments in the format ENCHANTMENT;LEVEL, for example: SHARPNESS:5.

item-flags

A list of item flags that hide certain attributes, like HIDE_ENCHANTS, HIDE_ATTRIBUTES, etc.


🪄 Special Material Types

You can use various custom item sources by using specific prefixes in the material field:

Prefix
Description

<nickname>PlayerName

Creates a player head based on the given player name.

<uuid>UUID

Creates a player head based on a UUID.

<texture>Base64

Creates a head using a texture URL or base64 string.

<base64>Base64

Similar to <texture>, uses a raw base64 string.

<itemsadder>item_id

Loads a custom item from the ItemsAdder plugin.

<oraxen>item_id

Loads a custom item from the Oraxen plugin.

<hdb>head_id

Loads a head from the Head Database plugin.

Example:

material: "<nickname>Notch"
name: "&6Notch's Head"

✅ Tips

  • Always make sure your material is a valid Minecraft material or starts with a recognized custom prefix.

  • Use custom-model-data when working with resource pack models.

  • Avoid using durability on modern Minecraft versions (1.13+), as it may behave inconsistently.

Last updated