Skip to content

Placeholder Reference ​

PlaceholderAPI Placeholders ​

Expansion identifier: emakistrengthen

Prerequisite: PlaceholderAPI is installed. Once installed, EmakiStrengthen registers the following placeholders, all reading strengthen data from the player's main-hand item

PlaceholderDescriptionExample
%emakistrengthen_mainhand_star%Current star level (0 if not eligible)7
%emakistrengthen_mainhand_temper%Temper level3
%emakistrengthen_mainhand_recipe%Associated recipe ID (empty if none)weapon_basic
%emakistrengthen_mainhand_eligible%Whether the item is eligible for strengtheningtrue
%emakistrengthen_mainhand_success_count%Cumulative success count5
%emakistrengthen_mainhand_failure_count%Cumulative failure count2
%emakistrengthen_mainhand_max_star%The recipe's maximum star (0 when not eligible)12
%emakistrengthen_mainhand_success_rate%Success rate for the current star65.5
%emakistrengthen_mainhand_crack_level%Crack level (temper value)3

Usage Example ​

yaml
lore:
  - '<gray>Star: <white>%emakistrengthen_mainhand_star%'
  - '<gray>Temper: <white>%emakistrengthen_mainhand_temper%'
  - '<gray>Recipe: <white>%emakistrengthen_mainhand_recipe%'
  - '<gray>Eligible: <white>%emakistrengthen_mainhand_eligible%'

Internal Template Variables ​

The following variables are injected while the strengthen layer presentation is built and can be used in recipe name_actions, lore_actions, and stat line templates

General Variables ​

VariableDescriptionExample
%star%Current star level7
%temper%Temper level3
%max_temper%Recipe max temper limit4
%temper_color%Color tag (<red> if temper > 0, else <green>)<red>

Stat Line Variables ​

Available in stat line templates:

VariableDescriptionExample
%id%Stat IDphysical_attack
%sign%Sign character+
%value%Formatted absolute stat value15.5
%<stat_id>%Any cumulative stat value. The actual key comes from accumulated recipe stats or variables120

NOTE

stat_lines is parsed and stored on the recipe model; the strengthen layer output in the current version comes from each star's name_actions / lore_actions, and the stat line template rendering path is not wired in yet. The stat line variables %id% / %sign% / %value% are only available while rendering a stat line template

Template Example ​

Recipe-level lore_actions (general variables available):

yaml
lore_actions:
  - action: "prepend"
    content:
      - "<yellow>★ Strengthen Level: +%star%"
      - "%temper_color%Temper: %temper%/%max_temper%"

stat_lines stat line templates (stat line variables available):

yaml
stat_lines:
  physical_attack:
    template: "<gray>Attack: <white>%sign%%value%"
    section_id: "strengthen.stats.primary"
    section_order: 210

Action Context Variables ​

When the success/failure actions (StrengthenActionCoordinator) run, these variables are injected into the Action context:

VariableDescriptionExample
%strengthen_recipe_id%Strengthen recipe IDweapon_basic
%strengthen_recipe%Strengthen recipe display nameBasic Weapon Strengthen
%strengthen_star%Resulting star8
%strengthen_temper%Temper level3
%strengthen_max_star%Recipe maximum star12
%strengthen_success_rate%Success rate of this attempt65.5
%strengthen_show_item%Hover text of the result item[Shadow Blade +8]
%strengthen_result_slot%Result slot IDmain_hand
%strengthen_operation_id%Operation ID of this attempt3f1c…
%operation_id%Same as %strengthen_operation_id%3f1c…
%star%Resulting star (same as %strengthen_star%)8
%temper%Temper level (same as %strengthen_temper%)3
%was_star%Star before the attempt (failure actions only)8
%dropped%Whether the item dropped (failure actions only)false
%protected%Whether protection triggered (failure actions only)true

Notes ​

  • All PlaceholderAPI keys prefixed with mainhand_ read main-hand item data
  • When the main-hand item has no strengthen data, star and temper return 0 and recipe returns empty
  • Internal template variables only work within Strengthen's name_actions / lore_actions and stat line templates
  • %<stat_id>% is dynamic and depends on stat keys configured in the recipe