Placeholder Reference

PlaceholderAPI Placeholders

Expansion identifier: emakiforge

When PlaceholderAPI is installed, EmakiForge registers the following placeholders.

Placeholder	Description	Example
%emakiforge_craft_count_<recipe_id>%	How many times the player crafted a specific recipe.	5
%emakiforge_has_crafted_<recipe_id>%	Whether the player has crafted a specific recipe.	true
%emakiforge_total_crafts%	Total craft count across all recipes.	42
%emakiforge_guarantee_<key>%	Current guarantee/pity counter for the given key.	3

Usage Example

lore:
  - '<gray>Crafts: <white>%emakiforge_craft_count_flame_sword%'
  - '<gray>Total: <white>%emakiforge_total_crafts%'
  - '<gray>Pity: <yellow>%emakiforge_guarantee_flame_sword%'

Internal Template Variables

Forge injects the following %variable% format variables when applying result name and lore actions.

Variable	Description	Example
%quality%	Quality tier name. Injected only when a quality tier resolved.	Perfect
%quality_name%	Quality display name, same value as %quality%.	Perfect
%quality_multiplier%	Quality multiplier, formatted as 0.##.	1.2
%multiplier%	Short alias of the quality multiplier.	1.2
%<stat_id>%	Any variable injected via material variables effects, already scaled by material amount and quality multiplier.	10

Available In

• Material effect name_action value fields
• Material effect lore_action content fields
• Recipe result.success.name_actions value fields
• Recipe result.success.lore_actions content fields
• Global quality config quality.item_meta.tiers.<tier> name_actions and lore_actions

Template Example

name_actions:
  - action: "append_suffix"
    value: " <gray>[%quality_name%]</gray>"

lore_actions:
  - action: "append"
    content:
      - ""
      - "<gray>Quality: %quality_name%</gray>"
      - "<gray>Multiplier: <white>%quality_multiplier%</white></gray>"
      - "<gray>Fire Damage: <red>+%fire_damage%</red></gray>"

Notes

• PlaceholderAPI placeholders work anywhere PAPI is supported (scoreboards, chat, menus, etc.).
• Internal template variables only work within Forge name/lore actions, not in external plugins.
• %<stat_id>% is dynamic and depends on keys injected by material variables effects.
• Quality item_meta action lines run through the CoreLib action system, where general CoreLib placeholders such as %player_name% are available. That is a separate mechanism from the internal template variables above.