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
yaml
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 supports the following %variable% format variables in name_actions and lore_actions templates, resolved by ForgePresentationBuilder.
| Variable | Description | Example |
|---|---|---|
%quality% | Quality ID. | rare |
%quality_name% | Quality display name. | <blue>Rare |
%quality_multiplier% | Quality multiplier (full key). | 1.25 |
%multiplier% | Quality multiplier (shorthand). | 1.5 |
%player_name% | Name of the player who performed the forge. | Steve |
%player_uuid% | UUID of the player who performed the forge. | 550e8400-e29b-... |
{<stat_id>} | Any variable injected via material variables effects. | 10 |
Available In
- Material effect
name_actionvaluefields - Recipe
result.meta_actionsname_actionsvaluefields - Recipe
result.meta_actionslore_actionscontentfields - Quality config
name_actionsandlore_actions
Template Example
yaml
name_actions:
- action: "append_suffix"
value: " <gray>[Forged by %player_name%]</gray>"
lore_actions:
- action: "append"
content:
- ""
- "<gray>Forged by: <white>%player_name%</white></gray>"
- "<gray>Quality: %quality_name%</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 templates, not in external plugins.
{<stat_id>}is dynamic and depends on keys injected by materialvariableseffects.