• Added Forge script module access through emaki.module("forge").
• Added Forge-owned default script examples.
• Added updated Forge Web Console extension registration.
• Added shared condition system integration for Forge recipes.

• Fixed default Forge conditions not being aligned with the shared condition system.
• Fixed item source display and identification consistency issues.
• Fixed unstable old API access expectations for external plugin developers.
• Fixed incomplete Web Console field descriptions and editing entries.

• Refactored Forge API access to static facade + Bridge.
• Refactored Forge Assembly namespace registration.
• Refactored script module registration and cleanup.
• Refactored Web Console frontend entry and registration.
• Refactored recipe loading and item identification services.

• Improved default configs and language resources.
• Improved Web Console file titles, icons, and field comments.
• Improved managed item source display names through CoreLib.
• Improved integration consistency with scripts, conditions, and item sources.

• Review custom recipes, conditions, and item source matching.
• Update third-party integrations to the static facade API if needed.
• Update CoreLib together with Forge.

• Forge can now be accessed from scripts through emaki.module("forge").
• Forge now ships and owns its own script examples.

• Forge now registers its own Assembly layer namespace instead of relying on CoreLib hardcoded setup.
• bStats and runtime dependency handling are aligned with CoreLib.
• Versioned config/language update notices are supported.
• Forge stays aligned with shared CoreLib script, item source, and Web Console improvements.

• Use emaki.module("forge") when scripts need to check Forge availability.
• Update CoreLib together with Forge.

• Quality Pity System: After consecutive forges without a high-tier result, the system guarantees a higher quality outcome on the next attempt.
• Player Signature: Forged items now display the forger's name, giving each piece a unique sense of ownership.
• Web Console & GUI Editor: EmakiForge now integrates with the Web console, offering browser-based forge recipe and GUI editing. Both the forge GUI and recipe book have been redesigned.
• Forge Validation: New pre-forge condition validation ensures all requirements are met before execution.
• Failure Resolution: Independent failure result resolver with flexible multi-tier penalty configuration.
• Preparation Phase: Material checking, consumption, and preview separated into a dedicated preparation stage for clearer flow.
• Result Post-Processing: Additional post-forge actions can be executed, such as triggering skills or sending messages.
• Performance Recorder: New performance monitoring for forge operations.

• Forge main service heavily refactored with clearer stage separation.
• Simplified material model for more intuitive configuration.
• GUI and recipe book redesigned for significantly improved UX.
• Async executor optimized for faster forge response times.

• Name/Lore Action System — Recipes and quality configs now support name_actions / lore_actions fields. Forging can directly modify item names and lore (e.g., append quality marks, stat text) with actions like append_suffix, prepend, insert_below, etc. All operations are tracked via ItemOperationLedger and can be precisely reverted. 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 now store complete audit data in PDC: recipe ID, quality, multiplier, timestamp, material signatures, and output source.

• 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 Chinese comments.
• Config and language files auto-merge new keys on upgrade.

• 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.

• 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 auto-merged.

• Added player kick event handling for forge player data cleanup/save flows.
• Removed deprecated lifecycle cleanup calls.
• Updated dependency alignment to CoreLib 3.5.0.
• Synchronized plugin, config, and language versions to 3.5.0.

• ◆ ForgePdcAttributeWriter now uses PdcAttributeGateway instead of reflection.
• ◆ Forge GUI text can now evaluate structured text config objects.
• ◆ Layer snapshot content, values, replacements, patterns, and anchors can use richer configured text.
• ◆ Forge presentation content can use CoreLib random_text and nested variable support.
• ◆ Material and material effect parsing moved into ForgeMaterialParser.
• ◆ Existing ForgeMaterial.fromConfig and MaterialEffect.fromConfig entry points remain available.

No upgrade notes.

• ◆ A new emakiforge PlaceholderAPI expansion exposes recipe craft counts, crafted-state checks, total crafts, and guarantee counters.
• ◆ The legacy in-game resource editor command path has been removed from commands, tab completion, runtime components, and service classes.
• ◆ The stable command surface is now focused on forge, book, reload, and list recipe.
• ◆ Material contribution, result snapshots, and PDC attribute writes continue to use the current non-EA-prefixed attribute names.
• ◆ config.yml and zh_CN.yml now use the unified version field for 3.3.0.
• ◆ Material planning, quality calculation, result item creation, GUI rendering, and exception paths received cleanup.

• ◆ Run this release on Java 25.
• ◆ Remove any server documentation that still points admins to the old editor, edit, create, delete, or input commands.
• ◆ Test the new PlaceholderAPI values if you use scoreboards, menus, or quest conditions around forging progress.
• ◆ Keep custom attributes on the current non-EA-prefixed names.
• ◆ Use version as the schema key in custom config and language files.

• ◆ Editor pending-input submission now goes through /emakiforge input (content|cancel) instead of the older chat-driven input path.
• ◆ The editor internals were split into dedicated renderer, interaction-handler, and field-resolver pieces, which makes the flow easier to maintain and less fragile.
• ◆ Recipe structure is now fully aligned around root-level forge_capacity, result.output_item, and structured_presentation for result display.
• ◆ Recipe loading now rejects the legacy target_item field and validates condition_type during load, so invalid configs fail early with clearer feedback.
• ◆ Default sample resources and zh_CN messages were updated to match the real parser behavior, including first-craft success feedback and config-error messages.
• ◆ Forge display handling continues to follow the structured presentation path from CoreLib instead of older compatibility layers.

• ◆ Migrate any legacy target_item recipe output to result.output_item, and move forge_capacity to the recipe root.
• ◆ Use structured_presentation for result display instead of removed legacy presentation fields.
• ◆ If you edit recipes in game, submit pending input through /emakiforge input (content) or /emakiforge input cancel.

EmakiForge 3.1.0 focuses on predictable forging resolution, safer GUI interaction, and deeper integration with the shared EmakiCoreLib runtime foundation.

• ◆ ForgeMaterialUsagePlanner — Centralized required and optional material batching.
• ◆ Capacity Planning — Material capacity cost, bonus, and leftover return behavior are now handled in one place.
• ◆ Shared Runtime Support — Adopted CoreLib config base classes and reusable GUI template loading.

• ◆ Reworked plugin startup, lifecycle coordination, runtime components, and PDC attribute registration flow.
• ◆ Hardened forge station, recipe book, and editor interactions.
• ◆ Improved keyboard clicks, drag behavior, held-item validation, and session-state management.
• ◆ Updated config, GUI, and language resources to follow the newer CoreLib GUI syntax.

• ◆ Fixed inconsistent optional-material batching and capacity bonus behavior.
• ◆ Fixed leftover input return issues when multiple matching materials were supplied.
• ◆ Fixed item identification, recipe matching, editor dirty-state, and PDC registration timing edge cases.

• ◆ Back up custom recipes, GUI files, and language files before upgrading.
• ◆ Re-test complex recipes that use required materials, optional materials, capacity, and leftover returns.
• ◆ Upgrade together with EmakiCoreLib 3.1.0.

EmakiForge 更新日志 / Changelog
中文版
✨ 新增特性

• ForgePdcAttributeWriter: 新增 PDC 属性写入器
  • 提供持久化数据容器属性写入功能
  • 支持物品 NBT 数据的持久化存储
• EditableResourceType 增强: 扩展可编辑资源类型支持
  • 新增更多资源类型的编辑支持
  • 改进资源类型转换逻辑
• ForgeLookupIndex: 新增强化查找索引
  • 提供高效的配方和材料查找
  • 优化查找性能
• 配方系统增强: Recipe.java 优化
  • 新增配方验证逻辑
  • 改进配方加载错误处理

问题修复

• BootstrapService 删除: 删除不再需要的引导服务
  • 由 CoreLib 的统一引导机制替代
  • 简化插件启动流程
• MessageService 删除: 删除冗余的消息服务
  • 由 CoreLib 的统一消息服务替代
  • 减少代码重复
• LanguageLoader 删除: 删除语言文件加载器
  • 由 CoreLib 的统一加载机制替代
  • 简化语言文件管理

English Version
✨ Features

• ForgePdcAttributeWriter: New PDC attribute writer
  • Provides persistent data container attribute writing functionality
  • Supports persistent storage of item NBT data
• EditableResourceType Enhancements: Extended editable resource type support
  • Added support for more resource types
  • Improved resource type conversion logic
• ForgeLookupIndex: New forge lookup index
  • Provides efficient recipe and material lookup
  • Optimized lookup performance
• Recipe System Enhancements: Recipe.java optimized
  • Added recipe validation logic
  • Improved recipe loading error handling

Bug Fixes

• BootstrapService Deletion: Removed unnecessary bootstrap service
  • Replaced by CoreLib's unified bootstrap mechanism
  • Simplified plugin startup process
• MessageService Deletion: Removed redundant message service
  • Replaced by CoreLib's unified message service
  • Reduced code duplication
• LanguageLoader Deletion: Removed language file loader
  • Replaced by CoreLib's unified loading mechanism
  • Simplified language file management

EmakiForge Changelog
[2.2.0] - 2026-04-09
Added
Recipe files now own blueprints, materials, and target items together

• recipes/*.yml can now define target_item, blueprint_requirements, materials, and optional_material_limit directly, so the release no longer depends on separate default blueprints/ and materials/ directories.
• Inline recipe materials can now declare capacity cost, stat contributions, name / lore actions, and capacity bonus directly, and the sample flame_sword.yml has been fully migrated to the new schema.

Improved
Forge validation and GUI flow now follow the recipe model end to end

• Material validation now matches inputs directly against recipe-defined required and optional materials by item source, which keeps fixed materials, optional materials, capacity limits, and capacity bonus checks consistent.
• Default GUI wording, reload summaries, and command help now revolve around the "recipe" concept, so players and admins no longer need to reason about the old blueprint / material directory split.
• Forge continues to delegate all external item-source availability to EmakiCoreLib, keeping only business-side matching, capacity calculation, and interaction feedback locally.

Fixed

• Legacy keys such as required_materials, optional_materials, gui, and top-level forge_capacity are now rejected during parsing so old configs cannot be half-loaded into an inconsistent state.
• Optional-material validation now blocks items that do not belong to the current recipe earlier in the flow, reducing follow-up errors caused by wrong materials slipping through.

Upgrade Notes

• If you still use the old blueprints/ and materials/ config structure, migrate it to the new inline recipes/*.yml format before upgrading.
• Default data release and list/editor flows now work around the recipes directory only, so do not rely on the removed default blueprint or material sample files.
• This version should be paired with EmakiCoreLib 2.3.0, and CoreLib startup logs should be treated as the source of truth for external item-source bridge readiness.

Known Issues

• The default template still does not show random-result previews. This limitation remains intentional to prevent reroll abuse.

[2.1.0] - 2026-04-08
Added
Forging Resource Editor Released

• Added editor_gui and EditorGuiService, supporting in-game browsing, creation, and editing of three resource types: blueprints, materials, and recipes.
• Added /emakiforge editor, edit, create, delete subcommands, along with the permissions emakiforge.editor, emakiforge.editor.delete, and emakiforge.editor.*.
• The editor supports chat input, document tree browsing, recipe slot grid switching, writing item / output_item sources from the main hand item, and unsaved close confirmation.
• Automatic backup of the original YAML is performed before saving, renaming, or deleting, followed by a hot-reload of forging resources upon operation completion.

GUI Template and Recipe Book Configuration Enhancements

• The default forging GUI has been updated to a new layout, with clearer visual separation for the blueprint, capacity, materials, and confirmation areas.
• Added the confirm_blocked virtual item and capacity_state text template. Clear blocking feedback is now provided when capacity limits are exceeded.
• Added virtual_items.recipe_entry and multiple sets of state text to the recipe book. Unlock status, whether forged, and click hints are now all configuration-driven.

Improvements & Optimizations
Full Migration to CoreLib Item Source Service

• ItemIdentifierService now delegates to EmakiCoreLib's ItemSourceService. Forge no longer maintains external item plugin bridges independently.
• Removed Forge's direct compile-time dependencies and plugin.yml soft-dependencies on MMOItems, NeigeItems, and CraftEngine.
• Item source availability and bridge timing are now uniformly managed by CoreLib. Forge retains only the business-side identification, matching, and hint logic.

Commands and Interaction Refactoring

• The main command aliases have been adjusted from emforge / forge to eforge / ef.
• The editor now supports resource locking to prevent simultaneous edits of the same resource by multiple administrators.
• Deleting and renaming resources will first create a backup file on disk, reducing the risk of irreversible errors from misoperations during live server periods.

Default Template Detail Optimizations

• forge_gui.yml now unifies capacity display, material slot hints, and result hiding instructions.
• With the addition of virtual item templates to the recipe book pages, custom themes can now directly override text and display styles without modifying Java code.

Upgrade Notes

• Requires EmakiCoreLib 2.1.0 or higher. The availability of external item sources should be verified based on the bridge status in CoreLib's startup logs.
• If your scripts, menu buttons, or documentation still reference the old aliases forge / emforge, please update them to eforge / ef or the full main command emakiforge.
• The resource editor's save and delete operations will generate backups under plugins/EmakiForge/backups/<type>/. It is recommended to include this in your server maintenance backup strategy.
• If you are retaining an older custom forging template, please manually merge the new capacity_state text and the capacity over-limit blocking feedback logic.

Known Issues

• The default template still does not display random result previews. This is a design limitation retained to prevent farming for random results.

EmakiForge Changelog
[2.0.0] - 2026-04-04
Added
Forging Results Integrated into CoreLib Assembly Pipeline

• Forged products are now uniformly constructed through the EmakiItemAssemblyService, no longer relying solely on the legacy process of directly modifying ItemMeta.
• Recipe results, material entries, and quality entries are compiled into assembly-layer snapshots and written into the final product.
• result.meta_actions now supports name modification and Lore modification, making it easier to define product display rules directly at the recipe level.
• Added forging-layer audit data, recording recipe ID, quality, material signature, forging time, and output source.

Assembly Feedback and Lore Search Hints

• Added ForgeAssemblyFeedbackHandler, which synchronously reports Lore search-and-insert failures, regex errors, and configuration errors to the console.
• Players will also receive direct prompts during actual forging if they encounter invalid Lore search configurations.

Asynchronous Caching and Persistence

• Added PlayerDataCache; player forging history and pity counters are now managed by a concurrency-safe cache.
• PlayerDataStore is now integrated into the CoreLib asynchronous YAML saving pipeline.
• Automatic saves, player-offline saves, and plugin-shutdown saves will all wait for pending write tasks to complete, reducing the risk of historical data loss.
• ForgeService added a pre-forge cache and prepareForgeAsync(...) to reduce redundant calculation overhead.

Changed
GUI and Recipe Experience

• The default forging GUI no longer displays random product previews, preventing repeated刷取 of random quality and entry results through previews.
• The default target item slot has been changed to a "result hidden" placeholder description, with interface text updated accordingly.
• The recipe book now uniformly uses configuredOutputSource() to parse the result source when displaying result items.

Recipes and Validation Logic

• Recipe added configuredOutputSource() and requiresTargetInput() for unified output source determination.
• MaterialValidationService rewritten the material normalization and validation logic to prevent disguising required materials and塞入 optional slots.
• RecipeMatchingService optimized error priority; when a recipe fails to match, a more reasonable first failure reason is now given.
• Blueprint capacity, material capacity bonuses, and optional material whitelist/blacklist are now uniformly结算 within the same validation process.

Example Resource Updates

• Default blueprint and material examples have been switched from external item IDs to vanilla items, lowering the barrier to entry for running out-of-the-box.
• Example blueprints added forge_capacity, making capacity sources more intuitive.
• Example recipe flame_sword.yml changed to use vanilla diamond_sword as base material, any_of blueprint requirements, whitelist-style optional materials, and the result.meta_actions写法.
• YAML indentation examples for quality broadcast actions have been corrected.

Upgrade Notes

• Requires EmakiCoreLib 2.0.0 or higher.
• If you use custom recipes, it is recommended to explicitly declare the result source:
  • When there is a fixed product base material, use target_item.item or result.output_item.
  • When name/Lore modifications are needed, prioritize writing them in result.meta_actions.
• The default GUI intentionally hides result previews; if your old workflow relied on the "preview first, then confirm" interaction, you need to evaluate whether to keep the old template.
• If you still use the old forging process of "player places target item for processing", please key inspection the target slot interaction and custom GUI templates before upgrading.

Known Issues

• Random results do not provide product previews in the default template; this is a design trade-off, not a rendering fault.

[1.10.0] - 2026-03-31
New Features
Material Quality Modification Mechanism

• Added ForgeMaterial.QualityModifier record to support influencing forging quality through material effects.
• Supports two modification modes:
  • force: Forcibly specifies a quality tier, overriding random and pity mechanisms.
  • minimum: Sets a quality floor, taking the higher value compared to the random result.
• Added ForgeQualityModifierResolver service to uniformly process quality modification logic.
• The quality_modify effect can now be added in material definitions:

Item Refresh Service

• Added ForgeItemRefreshService, supporting automatic refresh of forging attributes for player inventory and dropped items.
• Added ForgeItemRefreshListener, listening to the following events to trigger refresh:
• Player joins server (PlayerJoinEvent)
• Player clicks inventory (InventoryClickEvent)
• Player drags inventory (InventoryDragEvent)
• Player drops an item (PlayerDropItemEvent)
• Player picks up an item (EntityPickupItemEvent)
• Supports batch refresh for online players, single player inventory refresh, and dropped item refresh.
• The refresh process recalculates quality modifications and updates item metadata.

Material Contribution Record

• Added ForgeMaterialContribution record, representing contribution information of forging materials.
• Includes material ID, quantity, slot, category, sequence, and other information.
• Provides toAuditMap() and toSignatureData() methods for auditing and signing.

Improvements & Optimizations
Quality Calculation Flow Optimization

• QualityRollPlan record structure changes:
• Added rolledTier: Randomly rolled quality tier.
• Added finalTier: Final quality tier after applying modifications.
• Added forceApplied: Whether a force modification was applied.
• PreparedForge record structure changes:
• Added rolledQualityTier: Random quality tier.
• Added forceQualityApplied: Whether forced application occurred.
• Improved quality calculation logic to support material modifier participation.

Quality Tier Comparison Refactoring

• QualitySettings added helper methods:
• findTier(String name): Find a quality tier.
• tierIndex(String name): Get the index of a quality tier.
• tierIndex(QualityTier tier): Get the index of a quality tier.
• hasTier(String name): Check if a quality tier exists.
• higherTier(QualityTier first, QualityTier second): Compare and return the higher quality tier.
• Improved quality tier lookup logic, reducing redundant calculations.
• Optimized quality configuration parsing performance.

ForgeMaterial Enhancements

• Added qualityModifiers() method to get the list of material quality modifiers.
• Added definitionSignatureData() method to generate material definition signature data.
• Improved material effect parsing to support quality modification effects.

ForgeService Improvements

• Added findMaterialById(String materialId) method.
• Added resolveMaterialQualityModifiers() method to parse material quality modifiers.
• Improved forge preparation flow, integrating quality modification calculation.

Configuration Changes
Configuration File Updates

• Action IDs in configuration files have been updated to camelCase format.
• Example recipe configurations have been updated accordingly.

Code Improvements
EmakiForgePlugin

• Added itemRefreshService() accessor.
• Improved plugin lifecycle management.

ForgeLifecycleCoordinator

• Integrated item refresh service initialization.

ForgeRuntimeComponents

• Added itemRefreshService component.

RecipeLoader

• Improved recipe loading logic.

ForgeExecutionService

• Improved forge execution flow.

ForgeLayerSnapshotBuilder

• Optimized layer snapshot building logic.

ForgeLookupIndex

• Added findMaterialById() method.
• Improved material lookup performance.

Usage Notes
Material Quality Modification

• To use the material quality modification feature, you need to add the quality_modify effect in the material definition.
• The effect data must include the mode (force/minimum) and tier (quality name) fields.
• Force mode overrides pity mechanisms; use with caution.
• Minimum mode takes the higher value compared to the random result, suitable for pity scenarios.

Item Refresh Service

• The item refresh service is enabled by default and will automatically refresh upon relevant events.
• The refresh process recalculates quality modifications and updates item metadata.
• May cause performance overhead in scenarios with a large number of items; adjustment based on server load is recommended.

Action ID Migration

• Action IDs in configuration files need to be migrated from underscore_case to camelCase format.
• Affected configurations:
• Quality actions in config.yml
• Custom recipe configurations

Compatibility

• Requires EmakiCoreLib 1.11.0 or above.
• The quality modification feature is optional and does not affect existing recipe configurations.
• Maintains backward compatibility with older configuration files.

API Changes

• QualityRollPlan record structure changed with added fields.
• PreparedForge record structure changed with added fields.
• QualityCalculationService constructor added new parameters.
• The above changes may affect external plugins directly using these APIs.

Known Issues

• The item refresh service may cause performance overhead in scenarios with a large number of items.