EmakiForge | Blueprint Forging

EmakiForge 3.2.0

EmakiForge 3.2.0 is the release that brings the recipe editor and the recipe schema back into full alignment with the code that actually runs. Administrators get a cleaner in-game editing flow, earlier validation for bad configs, and default resources that finally match the real parser contract instead of leaving hidden mismatches behind.

• The editor input flow is command-based now. Pending editor input is submitted through /emakiforge input (content|cancel) instead of the older chat-event path, and the editor logic is now split across dedicated renderer, interaction, and field-resolution components.
• The recipe schema is fully tightened. forge_capacity lives at the root, result output is defined through result.output_item, and structured display output follows structured_presentation.
• Invalid configs fail earlier. The loader now rejects legacy target_item usage and validates condition_type during load time, which makes broken recipes much easier to diagnose.
• Default resources match the parser now. Sample recipes, comments, and zh_CN feedback strings were updated to reflect the real runtime behavior.
• Forge display output stays on the newer structured path. This reduces leftover maintenance cost from older display compatibility branches.

Upgrade Notes

• Replace legacy target_item output fields with result.output_item.
• Move forge_capacity to the recipe root.
• Prefer structured_presentation for custom result display definitions.
• Use /emakiforge input for in-game editor submissions.

View Full Documentation | Join Discord Community | QQ Group