Advanced Item Creation

This guide will walk you through creating highly customized items using the plugin's configuration files. This system allows you to define every aspect of an item in YAML, from its name and lore to custom skins and hidden data, without touching any Java code.

All items are defined within an item section, which you can place in files like boosters.yml or a dedicated items.yml.

The Basic Structure

At a minimum, every item needs a material, a name, and lore.

YAML

basic_stone:
  material: "STONE"
  name: "&aSimple Stone"
  lore:
    - "&7This is the first line."
    - "&7This is the second."

---

Common Item Properties

Beyond the basics, you can add many other properties to customize your items.

• amount: Sets the stack size of the item.

• glow: (true/false) Adds an enchantment glint without a visible enchant.

• unbreakable: (true/false) Makes tools and armor have infinite durability.

• custom-model-data: A number used by resource packs to give the item a custom texture.

• enchantments: A list of enchantments to apply. The format is "ENCHANTMENT_NAME:LEVEL".

• flags: A list of ItemFlags to hide parts of the item's default tooltip, like enchantments or attributes. Common flags include HIDE_ENCHANTS, HIDE_ATTRIBUTES, and HIDE_UNBREAKABLE.

Example with Common Properties:

YAML

example_sword:
  material: "IRON_SWORD"
  name: "&eExample Sword"
  lore:
    - "&7A basic but reliable weapon."
  glow: true
  unbreakable: true
  enchantments:
    - "DAMAGE_ALL:3"
  flags:
    - "HIDE_ENCHANTS"
    - "HIDE_UNBREAKABLE"

---

Advanced Customization: Skulls & NBT

Here is where the system becomes truly powerful, allowing you to create unique items with custom skins and hidden data.

Creating Custom Player Heads (Skulls)

To create a custom head, you must set the material to PLAYER_HEAD. You can then define its skin in one of two ways.

1. By Player Name (skull-owner)

This is the easiest method. It uses the skin of an existing Minecraft player.

YAML

heads:
  notch_head:
    material: "PLAYER_HEAD"
    name: "&eHead of Notch"
    # This will apply Notch's skin to the item.
    skull-owner: "Notch"

2. By Texture Value (texture)

This is a more advanced and permanent method. It uses a Base64 texture value that you can get from websites like mineskin.org. The advantage is that the skin will never change, even if the original player changes their skin.

YAML

heads:
  earth_globe:
    material: "PLAYER_HEAD"
    name: "&bThe Globe"
    lore:
      - "&7A whole world in your hands."
    # This is a long Base64 string that represents the skin texture.
    texture: "eyJ0ZXh0dXJlcyI6eyJTS0lOIjp7InVybCI6Imh0dHA6Ly90ZXh0dXJlcy5taW5lY3JhZnQubmV0L3RleHR1cmUvYjFkZDRmZTRhNDI5YWJkNjY1ZGZkYjNlMjEzMjFkNmVmYTZhNmI1ZTg3ZDVmZWE0Mzg5ZmFlZDBmY2I0Y2YifX19"

Adding Custom NBT Data

NBT (Named Binary Tag) is hidden data stored on an item. It is the best way to identify your custom items because players cannot see or change it. This prevents players from simply renaming a normal item to cheat the system.

You can add NBT data under the nbt section using the format "key: 'type:value'".

Supported Types: string, int (or integer), double, boolean (or bool), and long.

Example with NBT:

This creates a "key" item that your plugin can later identify in a listener by checking for the door_id and is_master_key tags.

YAML

special_key:
  material: "TRIPWIRE_HOOK"
  name: "&6Ancient Key"
  lore:
    - "&7Unlocks a mysterious door."
  glow: true
  nbt:
    # A string tag to identify which door this key opens.
    door_id: "string:dungeon_level_1"
    # A boolean tag to check if this is a special version of the key.
    is_master_key: "boolean:false"
    # An integer tag to store how many times it's been used.
    uses_remaining: "int:5"