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

Placeholders, Prefixes, and Dynamic Templates

Use placeholder-aware templates and prefixes so one profile can adapt cleanly across many output items.

If you want one profile to work cleanly across many different items, you should use placeholder-aware templates instead of hardcoding one fixed final name.

The item placeholders

Item Forge currently supports item-side tokens such as:

  • {ogitemname}
  • {original_item_name}
  • {itemname}
  • {material}
  • {item_type}
  • {itemtype}
  • {material_key}
  • {amount}

The player and context placeholders

Item Forge also supports context tokens such as:

  • {player}
  • {player_name}
  • {editor_name}
  • {last_player_name}
  • {player_display_name}
  • {display_name}
  • {uuid}
  • {world}
  • {x}
  • {y}
  • {z}
  • {yaw}
  • {pitch}

Prefix versus template

Prefix and template are not the same job.

Prefix

Prefix is a reusable front-loaded text layer for the final display name.

Item Forge automatically treats prefix like:

  • your prefix text
  • then a reset
  • then one separator space

Template display or item name

Template display and template item name are where you put dynamic placeholder logic.

Use them when:

  • the output name should change based on the original item
  • one profile should work across helmets, chestplates, leggings, boots, swords, or blocks

Good examples

TEXT
Hardened {ogitemname}

Prefix:

TEXT
<gradient:#FF8A00:#FFD84D><bold>Fortified</bold></gradient>

Template display:

TEXT
{ogitemname}

Lore:

TEXT
<gray>Issued to {player} in {world} at {x}, {y}, {z}</gray>

What trips people up most

If you type a fixed display or item name into a profile, every generated output will use that fixed value.

That is correct behavior, but it feels wrong if you expected the text to adapt automatically.

Use placeholders whenever one profile is meant to target many different item materials.

How placeholder storage works

Profile templates keep the raw placeholder string so it can resolve later per output item.

Main-hand and batch editing are more immediate. They are for live edits, not reusable template output logic.

Use the Placeholder browser

The Placeholder browser exists so admins can:

  • preview tokens
  • click tokens into chat
  • create display templates
  • create item-name templates
  • append lore templates

Best next pages