EmakiStrengthen Changelog

[2.0.0] - 2026-04-09

Default data has been consolidated from profiles/, rules/, and materials/ into recipes/*.yml, and each recipe can now define matching rules, star stages, material requirements, presentation rules, economy cost, and action hooks in one place.
The release now ships with six starter recipes: weapon_physical, weapon_projectile, weapon_spell, armor_guard, generic_visual, and offhand_focus, making it easier to bootstrap weapon, armor, and off-hand growth lines.
Each star stage can now define its own materials, presentation, success_actions, failure_actions, and economy overrides, so growth design is no longer constrained by the old profile model.

Failures now build up temper, and later success rates increase according to each recipe's max_temper and temper_chance_bonus_per_level.
Optional materials can now declare protection and temper_boost at the star-stage level, which enables anti-drop-star effects and extra temper gain.
The strengthen GUI now uses four optional-material slots, and the preview area now shows success rate, cost, and required materials together.

Recipe economy definitions now support multiple currency entries, formula-based cost calculation, and per-star overrides so different equipment lines can follow different cost curves.
Strengthen presentation now reuses CoreLib features such as lore_search_insert, conditional name appends, variable substitution, and expression rendering for finer control over item names and lore.

setstar, givecatalyst, inspect, reload, and tab completion now all work around recipes and the material catalog instead of the old profile IDs.
Fixed strengthen materials are now consumed directly from the inventory, which lets the GUI focus on the target item and optional-material choices for the current attempt.
State output and player-facing messages now consistently use the new recipe, first_reach, and temper terminology.

Fixed materials, optional materials, and economy costs are now validated before the strengthen attempt proceeds, preventing failures that were only discovered after result write-back.
If result write-back fails, the attempt is now aborted immediately instead of writing a broken state back onto the item.
Missing recipe matches, invalid optional materials, and insufficient cost conditions now return clearer failure reasons, which reduces operator investigation time.

The old default profiles/, rules/, and materials/ directories have been removed; move custom strengthen content into recipes/*.yml.
Global config.yml fields such as max_star, max_crack, crack_chance_bonus_per_level, success_chance_cap, and economy.* have moved into each recipe's limits and economy sections.
If admin scripts still use /emakistrengthen setstar <star> [profile] or depend on old inspect field names, migrate them to the new recipe terminology and output format.