Skip to main content
Item Forge wiki

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.

Naming and Templates

Display Name, Item Name, Lore, and Formatting

Separate display name, item name, and lore clearly so profile output stays readable and predictable.

Item Forge separates three different text layers:

  • display name
  • item name
  • lore

Display name

Display name is the normal player-side item title at the top of the hover card.

Use it when:

  • the item needs its main visible name changed
  • you want a prefix applied to the visible item title
  • you want a dynamic profile template like Hardened {ogitemname}

Item name

Item name is the tooltip-side item label surface. It is different from display name and should be used intentionally.

Use it when:

  • you want a separate tooltip identity
  • you want to override the tooltip-side item naming logic
  • you want profile-generated items to use a template that resolves per output item

If you put a static item name into a profile, every generated output will use that exact text unless you use placeholders.

Lore

Lore is for descriptive lines, tags, flavor text, instructions, or structured item metadata.

Item Forge lets you:

  • append lore
  • replace a specific lore line
  • remove a specific lore line
  • clear lore completely

Default text behavior

Item Forge is built so text defaults to:

  • white
  • non-italic

That means text should only become italic if you intentionally format it that way with MiniMessage or legacy formatting codes.

MiniMessage and legacy & formatting

Item Forge supports both:

  • MiniMessage
  • legacy & formatting codes

Examples:

TEXT
<gold>Forged</gold> {ogitemname}
TEXT
&6&lForged&r &f{ogitemname}

Good naming strategy

If the item output should adapt to the underlying item, avoid typing a fixed final name into a profile.

Use:

TEXT
Hardened {ogitemname}

instead of hardcoding one material name.

Best next pages