Define custom items used by the plugin. This file controls internal item templates (materials, names, lore, enchants, flags, model data) which are referenced across the plugin (classes, GUIs, menus).
Where to find it
Generated after the first server start:
plugins/Zentrix/items.yml
What you edit here
Internal item IDs and their properties
Display names (Hex &#RRGGBB and legacy & codes)
Lore lines shown in GUIs
Enchantments, custom model data, amount, slot
Item flags and glow/unbreakable toggles
Use these internal item IDs (e.g., warrior-sword) in other config files like classes.yml as id: "custom:warrior-sword".
Introduction
items.yml is the canonical list of internal, reusable item definitions. Instead of repeating the same item properties in multiple files, reference a single item key from here. This keeps kits, menus, and GUIs consistent and easy to update.
File structure
Each item is a top-level key with the following typical properties:
Configuration fields
material
The base item source.
Vanilla: Bukkit material enum (e.g., IRON_SWORD, BARRIER, KNOWLEDGE_BOOK)
ItemsAdder: itemsadder:namespace:id
Nexo: nexo:id
Wrap ItemsAdder/Nexo values in quotes because they contain :.
display-name
Item name shown in GUIs and inventories. Supports Hex and legacy color codes.
lore
Array of strings shown under the item name. Use these for descriptive GUI text and brief usage hints.
custom-model-data
Integer used by resource packs to swap models.
amount
Stack size when given (1–64).
slot
Preferred inventory slot (0–8 for hotbar). Not all systems will enforce this.
glow & unbreakable
Visual/enchant behavior.
enchantments
List of enchantments in "name:level" format (lower/upper case accepted).
flags
Hide UI attributes from the item tooltip (HIDE_ENCHANTS, HIDE_ATTRIBUTES, HIDE_UNBREAKABLE, HIDE_ADDITIONAL_TOOLTIP, etc.).
External plugins & referencing
You have two clean ways to use ItemsAdder/Nexo items:
Reference them directly where used (recommended for one-offs):
material: "itemsadder:namespace:id"
material: "nexo:id"
Or define a reusable internal key here, using material: "itemsadder:..." / material: "nexo:...", then reference it elsewhere as material: "custom:<item-key>".
If you’re reusing the same external item in many places, define it once in items.yml. Then reference it via custom:<item-key>. This keeps naming/lore/flags consistent.
Example breakdown: Leave Game item
This entry shows a typical GUI item with slot, lore, and flags.
What this config does:
Uses BARRIER as the base material so it stands out.
Places the item in hotbar slot 8.
Hides attributes to keep tooltip clean.
Example breakdown: Warrior sword
This is a kit item referenced by classes.yml as id: "custom:warrior-sword".
What this config does:
Defines a reusable sword with an enchantment and compact tooltip.
Referenced in kits to ensure consistent naming and lore across the plugin.