BuffedItems lets you create unique, custom items with persistent potion effects, attributes, and special properties, all from a comprehensive in-game GUI editor.

• Full In-Game GUI Editor: Access a powerful menu with /bi menu to manage every aspect of your items.
• Persistent Effects: Grant permanent potion effects (like Speed, Haste) or attribute modifiers (like +Max Health, +Movement Speed).
• Slot-Based Application: Apply effects only when an item is in a specific slot:
  • MAIN_HAND or OFF_HAND
  • HELMET, CHESTPLATE, LEGGINGS, BOOTS
  • INVENTORY (applies if the item is anywhere in the player's inventory)
• Deep Customization:
  • Display Name & Lore: Full support for Hex codes (&#RRGGBB) and standard color codes (&c).
  • Material: Choose any item material from a paginated in-game selector.
  • Enchantments: Add any enchantment with any level (e.g., Sharpness 10).
  • Glow: Toggle the enchantment glow effect with one click.
  • Custom Model Data: Supports direct integers and integration with ItemsAdder and Nexo (e.g., itemsadder:my_sword).
• Powerful Item Flags (Protections):
  • PREVENT_DEATH_DROP: The item stays in the player's inventory on death.
  • PREVENT_DROP: Prevents dropping the item or storing it in containers/item frames.
  • UNBREAKABLE: The item never loses durability.
  • PREVENT_ANVIL_USE: Blocks the item from being used in anvils.
  • PREVENT_SMITHING_USE: Blocks the item from being used in smithing tables.
  • ...and many more, like PREVENT_CRAFTING, PREVENT_PLACEMENT, and HIDE_ATTRIBUTES.
• Permission-Based Effects: Optionally require players to have a specific permission node for an item's effects to apply.
• Integrations:
  • PlaceholderAPI: Use placeholders in your item's display name and lore.
  • ItemsAdder: Get custom model data from an ItemsAdder item (e.g., itemsadder:my_sword).
  • Nexo: Get custom model data from a Nexo item (e.g., nexo:my_sword).
• Performance: Features an intelligent caching and task-scheduling system to apply effects with minimal impact on server performance.

1. Create: Use /bi menu to create a new item and give it a unique ID (e.g., warriors_talisman).
2. Configure: Use the GUI to set the item's name, material, and add effects. For example, add STRENGTH 1 and GENERIC_MAX_HEALTH +4.0 to the INVENTORY slot.
3. Give: Give the item to a player using /bi give <player> warriors_talisman.
4. Apply: The plugin's core task detects that the player has the item in their inventory and automatically applies the STRENGTH 1 and +2 Hearts effects. If the player drops the item, the effects are instantly removed.

• PAPI Placeholders: PlaceholderAPI placeholders (e.g., %player_name%) are only parsed when the item is given using the /bi give command. They will not update dynamically while the item is already in a player's inventory.
• Custom Armor Textures: This plugin only sets the CustomModelData tag. It does not manage resource packs or custom armor models. Wearable items (helmets, armor) using ItemsAdder/Nexo IDs will show the custom texture in the inventory, but will render as the default material (e.g., Diamond Helmet) when equipped on the player.
• Configuration Files:
  • config.yml: Contains general plugin settings (messages, debug level, etc.)
  • items.yml: Stores all your custom items.
  • Editing: We recommend using the in-game GUI (/bi menu) as it handles everything for you instantly. However, you CAN edit these files manually if you prefer! Just run /bi reload afterwards to apply your manual changes.

The main command is /buffeditems (Aliases: /bi, /buffitems).

Command	Permission	Description
/bi menu	buffeditems.command.menu	Opens the main GUI editor to create, edit, and delete items.
/bi give <player> <item_id> [amount]	buffeditems.command.give	Gives a player the specified custom item.
/bi reload	buffeditems.command.reload	Safely reloads both config.yml and items.yml from disk.
/bi list	buffeditems.command.list	Lists all created items and shows if any have configuration errors.

Admin Permission:

• buffeditems.admin: Grants access to all BuffedItems commands.

Item Permissions:

• You can define a custom permission (e.g., myitems.warrior_perk) inside the item editor. If set, a player must have this permission to receive the item's effects.

• Java 17 or newer
• Minecraft 1.21 or newer