EmakiForge | Blueprint-Driven Quality-Tiered Crafting System

EmakiForge 4.0.0 Release

This release introduces a ledger-based reversible name/lore modification system, PAPI placeholder support, and unifies the effect configuration format.

New Features

• Name/Lore Action System: Recipes and quality configs support name_actions / lore_actions fields. Forging can directly modify item names and lore with actions like append_suffix, prepend_prefix, prepend, append, insert_below, replace_line. All operations tracked via ItemOperationLedger for precise revert capability. Material effects also support type: "lore_action" / "name_action".
• PAPI Placeholders: %emakiforge_recipe_count% (loaded recipe count) and %emakiforge_last_crafted% (player's last crafted recipe ID).
• Enhanced Forge Audit: Forged items store complete audit data in PDC: recipe ID, quality, multiplier, timestamp, material signatures, and output source.

Improvements

• Unified effects list format with type field (variables / ea_attribute / es_skill / name_action / lore_action).
• Material item sources unified to item_sources: [...] list format.
• Example recipe fully rewritten with comprehensive field coverage and detailed comments.
• Config and language files auto-merge new keys on upgrade.

Breaking Changes

• structured_presentation removed — replaced by name_actions / lore_actions.
• Quality config item_meta.structured_presentation → item_meta.name_actions / item_meta.lore_actions.
• Material item field → item_sources: [...] list format.
• Skill effect type: "skill" → "es_skill", skills → es_skills.
• Old example recipe flame_sword.yml replaced by example_recipe.yml.

Upgrade Notes

• Migrate structured_presentation to name_actions / lore_actions in existing recipes.
• Migrate material item fields to item_sources list format.
• Config version updated to 4.0.0 — new entries are auto-merged on upgrade.

View Full Documentation | Join Discord Community | QQ Group