Wiki
Item Forge Wiki
Custom item editing, profile automation, smart scaling, batch workflows, and admin-friendly generation docs for Item Forge.
Getting Started
Start here for install, first boot, and the three main editing lanes.
Naming and Templates
Get display name, item name, lore, placeholders, and prefix behavior right before you mass-generate items.
Profiles and Automation
Build reusable modifier workflows, scale item math, and generate outputs from the Give menu.
Item Editing Systems
Trim, dye, attribute, hide, model, and tag items without dropping into raw NBT tooling.
Operations and Support
Teach admins the command surface, the built-in help surfaces, and the troubleshooting path for common item issues.
This is the part of Item Forge that moves the plugin beyond simple renaming and lore editing.
Attributes
Item Forge supports real attribute editing with EquipmentSlotGroup.
Use attributes when you need to change things like:
- armor
- armor toughness
- knockback resistance
- attack speed
- health-related values
- other vanilla attribute-driven behavior
Use direct attributes when the item needs an exact value.
Use Smart Scaling when the value should adapt to the base item automatically.
Flags and properties
The flags and properties surfaces control how much of the item's extra behavior is shown or hidden.
This includes things such as:
- unbreakable
- glint override
- tooltip hiding
- manual item-flag control
Default hidden upgrade presentation
By default, Item Forge hides upgrade-style tooltip details through the configured hidden item flags.
Current defaults are centered around hiding:
- enchants
- attributes
- armor trim
- dye
Advanced item components
Item Forge also supports advanced component editing such as:
- CustomModelData
- ItemModel
- TooltipStyle
- Rarity
- Enchantable
- MaxStackSize
PDC tags
The PersistentDataContainer editor is there for metadata work.
Use it when the item needs:
- internal identifiers
- tier markers
- custom plugin data
- structured tags for other systems
Profiles can also apply PDC data through:
KEEP_EXISTINGOVERWRITE