EmakiStrengthen | Equipment Star Strengthening

Added

- Public API StrengthenTransferOutcome and StrengthenTransferCompletedEvent, fired once a star transfer completes, carrying the source, target, target recipe id, source star and decay rate. - Public API catalog().successRate(), catalog().recipes(), catalog().recipe(String), operations().transfer(), operations().refreshItem(), operations().refreshPlayer() and operations().openGui().

Changed

- Actions use a new syntax, and you do not have to rewrite anything yourself. On first startup CoreLib rewrites the config files of every Emaki plugin under plugins/, once only. Each edited file keeps the original beside it with a .legacy-backup suffix. A line that cannot be converted leaves your config untouched and goes into a separate .v2-failed file, with the file and line listed in the console. - The six strengthen actions are yours to rename by hand; automatic rewriting does not cover them. Drop the emakistrengthen prefix for strengthen: - emakistrengthen_set_star → strengthen_set_star - emakistrengthen_add_star → strengthen_add_star - emakistrengthen_remove_star → strengthen_remove_star - emakistrengthen_reset_star → strengthen_reset_star - emakistrengthen_clear_layer → strengthen_clear_layer - emakistrengthen_rerender → strengthen_rerender - Strengthen variables inside a recipe's actions: block need a var. prefix, also by hand. What used to be %star% is now %var.star%. Available names: star, temper, was_star, dropped, protected, operation_id, strengthen_star, strengthen_temper, strengthen_recipe, strengthen_recipe_id, strengthen_max_star, strengthen_success_rate, strengthen_show_item, strengthen_result_slot, strengthen_operation_id. The old %show_item% is gone; use %var.strengthen_show_item%. - Placeholders elsewhere in a recipe are unchanged: %star%, %temper%, %max_temper% and %temper_color% in lore_actions and name_actions, and %base_cost% and %star% in cost_formula. Only action lines take the prefix, and adding it elsewhere breaks them. - The preview, temper and confirm slots are supplied through placeholders. If you keep your old gui/strengthen_gui.yml, set custom_name of preview_display to %preview_title% and its lore to a single %preview_lines%; set the lore of temper_display to a single %temper_lines%, keeping your own title; set custom_name of confirm to %confirm_title% and its lore to a single %confirm_lines%. Each placeholder expands one entry per line, so no extra lines are needed. The wording lives under gui.preview.*, gui.temper.* and gui.confirm.* in the lang files. - "Forge mark" and "crack" are both called temper now, renamed from Crack to Temper in English, across GUI titles, the messages and help text of /emakistrengthen clearcrack, the failure messages, and the sample recipe comments and lore. The clearcrack command name, the permissions, the config keys (max_temper, temper_chance_bonus_per_level, temper_boost) and the placeholder names are unchanged; only player-facing wording moved. - Config check lines in the console are coloured by severity, yellow for warnings and red for errors. - A star transfer attempted without ownership of the target player's thread fails outright instead of skipping StrengthenTransferEvent and completing anyway, which used to bypass third-party listeners. - For developers: EmakiStrengthenApi.available() is replaced by status(), returning ApiStatus. canStrengthen(), readState(), preview(), attempt() and rebuild() move behind catalog() for read-only queries and operations() for state changes. Every fallible call returns EmakiResult<T>, and an absent plugin yields EmakiResult.unavailable() instead of throwing or returning a fabricated empty object. EmakiStrengthenApi.Bridge is now @ApiStatus.NonExtendable, and install()/uninstall() are @ApiStatus.Internal. - For developers: the model classes move from emaki.jiuwu.craft.strengthen.model to emaki.jiuwu.craft.strengthen.api.model (AttemptContext, AttemptResult, AttemptPreview, AttemptCost, AttemptMaterial, AttemptOutcome, StrengthenState, StrengthenRecipe and the rest). Contract types such as EmakiResult, ApiStatus and ItemSourceRef come from emaki.jiuwu.craft.corelib.api, so the build base needs CoreLib's API artifact too.

Fixed

- The preview, temper status and confirm slots in the strengthen GUI showing nothing but fixed text, with no success rate, cost, failure penalty, material checklist or current temper. Those three slots configure their own name and lore in gui/strengthen_gui.yml, and that config overwrote everything the plugin had worked out, so players only ever saw the two hint lines from the file. Content is fed into placeholders now: your config owns the layout, the plugin supplies the live values. The material checklist is not new work either, it was always being worked out and simply swallowed; this is the first time you get to see it, listing every material the current star needs one per line, counted as "amount placed in the GUI / amount required", green when satisfied and red when short, with any other materials already in the GUI in their own section. - The confirm button keeping its anvil icon while requirements were unmet, which made it look clickable. It switches to BARRIER with a "cannot strengthen" title as intended. - gui_template in a recipe being ignored. The key was always accepted but never read, so every item opened strengthen_gui regardless. The GUI now follows the recipe matched by the item in hand and falls back to strengthen_gui when the named template does not exist. - A broken config being half applied. /emakistrengthen reload could leave the language file swapped while the recipes had failed to load, stranding the server between old and new. Everything is checked as a set first, and a failure keeps the whole previous config active, with the offending file and line named in the console.

Removed

- JS scripting, including strengthen chance rules (registerChanceRule) and result hooks (onResult). There is no automatic conversion, so use a recipe's condition and actions for the same effect. The bundled scripts/examples/strengthen_success.js sample is gone as well. - EmakiStrengthenApiProvider; call the static methods on EmakiStrengthenApi directly. - EmakiStrengthenApi.canStrengthen(), with no direct replacement. Decide it yourself from catalog().readState().

Notes

- Update EmakiCoreLib to 4.7.0 first. - Back up your whole plugins/EmakiStrengthen/ folder before upgrading, especially gui/strengthen_gui.yml and recipes/. - Four things need doing by hand: renaming the six emakistrengthen_* actions, prefixing strengthen variables in recipe action lines with var., rewriting JS chance rules and result hooks as recipe conditions and actions, and converting the three display slots in an old gui/strengthen_gui.yml to the placeholder form. Everything else is rewritten for you. - Strengthen layers, stars and temper already on player equipment are unaffected and need no migration. The recipe structure itself has not changed; only the writing inside actions: needs adjusting. - After updating, run /emakistrengthen reload and open the strengthen GUI to confirm the success rate, cost and material checklist all show up.

Emaki Strengthen v4.6.0

MineBBS 更新日志

破坏性变更与必要迁移

- 【破坏性】GUI 槽位物品结构改为嵌套组件：原 item: "<MATERIAL>" 搭配 display_name、lore、hidden_components: [tooltip]，现改为 item.source 搭配 item.components.custom_name、item.components.lore、item.components.tooltip_display.hide_tooltip。自定义 gui/strengthen_gui.yml 必须迁移。 - 【破坏性】插件描述文件迁移到 paper-plugin.yml，其中的 commands: 段已移除，必须使用 Paper 系服务端。 - 【破坏性】AttemptContext 与 AttemptResult 从 Java record 改为 final 类：访问器方法名保持不变，但 record 模式解构不再可用，依赖 record 语义的反射或序列化使用方需要调整。 - 【移除】浏览器端

Added

- Config key release_default_data (default true); set false to stop writing the bundled sample strengthen recipes and script examples. - Six configurable held-item actions: emakistrengthen_set_star, emakistrengthen_add_star, emakistrengthen_remove_star, emakistrengthen_reset_star, emakistrengthen_clear_layer, emakistrengthen_rerender. - Localizable config precheck text and translatable load type names. - Public API AttemptOutcome enum (NOT_COMMITTED, COMMITTED_SUCCESS, COMMITTED_FAILURE, COMPENSATION_PENDING), separating "the roll succeeded" from "the transaction committed". - Public API idempotency key operationId, exposed through AttemptContext, AttemptResult (operationId(), outcome(), committed(), compensationPending()) and the attempt events. - Optional soft dependency on EmakiItem, so the EmakiAttribute integration degrades gracefully when that plugin is absent.

Changed

- Economy charge failure changed from a direct refund to "rollback plus pending compensation": items and currency roll back separately and an incomplete rollback is reported as pending instead of being treated as refunded. - StrengthenPreAttemptEvent.getTargetItem() now returns a defensive copy, so mutating it no longer affects the real strengthen input; success rate is clamped to 0-100 and non-finite values become zero. - AttemptContext.materialInputs now keeps null placeholders so list indexes remain stable GUI slot identifiers. Callers that assumed "list length equals material count" are affected. - The API no longer mutates the item stacks passed in through AttemptContext; callers apply AttemptResult.resultItem() themselves and handle external inventory material consumption themselves. - Returning leftover materials after settlement now also clears the corresponding session slot state, and closing the GUI only closes the current session. - Message prefix switched to a new brand gradient. - api-version raised from 1.21 to 1.21.8; the build base moved from spigot-api to paper-api. Java target stays 25, folia-supported: true and the permission and subcommand sets (inspect/refresh/setstar/clearstate/clearcrack/givecatalyst) are unchanged.

Fixed

- A null-pointer in the strengthen result message path meant players received no result feedback in that case; the missing null check is added. - /emakistrengthen reload replies are delivered on the sender's execution domain, which is required for correctness on Folia.

Removed

- The browser-based Web Console layer (web-console.yml, web-extensions/, the CSS asset, the web-console/ frontend project). - The strengthen route preview capability, entirely. It only ever had a browser-side entry point (no in-game command or GUI), so the impact is limited to Web Console users. - Record semantics for AttemptContext and AttemptResult, which changed from Java records to final classes. Accessor method names are preserved, but record pattern destructuring no longer works and reflection or serialization consumers relying on record semantics must adjust. - The flat GUI slot item structure: item: "<MATERIAL>" with display_name, lore and hidden_components: [tooltip] becomes item.source with item.components.custom_name, item.components.lore and item.components.tooltip_display.hide_tooltip. Custom gui/strengthen_gui.yml must be migrated. - The commands: section, as the descriptor moved to paper-plugin.yml. Paper is required.

Notes

- Requires EmakiCoreLib 4.6.0. - Back up gui/strengthen_gui.yml and migrate it to the structure above; set release_default_data to false if you no longer want the bundled sample data written. - After updating, run /emakistrengthen reload and verify the strengthen flow, material returns and result messages.

Added

- Held-item strengthen actions for rerendering, star changes, reset, and layer clearing. - Manifest v2 Web Console integration for route preview, branches, stars, materials, economy, and effects. - Command suggestions after /emakistrengthen .

Fixed / Improved

- Fixed a possible null pointer when returning materials after closing the GUI. - Fixed strengthened item names flattening localized vanilla base names. - Improved Web Console route preview style loading. - Aligned with the Paper API / paper-plugin.yml 1.21.8+ baseline.

Notes

- Update with the matching CoreLib release. - Breaking: Action aliases were removed; use canonical action IDs. - Legacy config fields remain consolidated (es_skills, stars).

Added

- Public Bukkit events StrengthenPreAttemptEvent (cancellable, success-rate editable) and StrengthenAttemptEvent. - JavaScript extensions for strengthen success-rate rules and result hooks. - Config precheck on startup and reload.

Fixed

- Fixed a crash when opening the strengthen GUI with empty material slots. - Fixed suffixed strengthen names flattening localized base item names.

Notes

- Legacy compatibility fields are consolidated (es_skills, stars); migrate older formats if still in use.

Added

- Web Console Strengthen route preview. - Strengthen layered item preview support. - Star-stage name/lore action payloads. - Branch star preview data.

Fixed

- Fixed stage name/lore actions not affecting rebuilt item displays. - Fixed Item final preview missing reached Strengthen stage actions. - Fixed branch-aware attribute and skill writing. - Fixed overly broad example recipe matching.

Refactored

- StarStage API data. - Strengthen recipe parsing and rebuild flow. - Web Console route preview registration.

Improved

- Better recipe selection in Item preview. - Clearer route preview for configuration checks. - Better final-preview integration with CoreLib and Item.

Strengthen v4.2.0 focuses on cleaner module ownership and better integration with the shared CoreLib toolset.

Highlights

- Strengthen script module access through emaki.module("strengthen"). - Strengthen-owned script examples.

Improved

- Strengthen registers its own Assembly namespace. - Shared CoreLib effect/action editor integration in Web Console. - CoreLib-aligned bStats, runtime dependency handling, and versioned resource notices.

EmakiStrengthen v4.1.0

Branch tree system, strengthen transfer, Web console, and unified recipe format.

---

New Features

#### Strengthen Branch Tree Equipment can now define multiple upgrade branches instead of a single linear path. Each branch provides unique stat bonuses, giving players meaningful choices at branch points — choose the upgrade direction that fits your playstyle. #### Strengthen Transfer A new transfer service allows you to move strengthen levels from one piece of equipment to another. Preserve your hard-earned upgrades when switching gear. #### Web Console Integration EmakiStrengthen is now accessible through the built-in Web management console, allowing you to edit strengthen recipes and GUI configurations directly in your browser. #### Unified Recipe Format Recipe configuration has been unified into a cleaner success branch format, grouping all results, failure handling, stat bonuses, and lore effects together for better readability.

Improvements

- The strengthen GUI has been redesigned for a better user experience. - Recipe models have been extracted to the API module for cross-plugin reference. - Language files have been fully updated with new translations. - Snapshot building and refresh logic has been optimized for better performance.

EmakiStrengthen 4.0.0 Release

This release introduces a branching enhancement system, expression variables, and name/lore actions, significantly expanding enhancement gameplay depth.

New Features

- Branching Enhancement System: Recipes support branch_tree for tree-based enhancement paths. Players choose different branches at specified star levels (e.g., Sharp → Crit, Heavy → High Damage). Branches can be nested. Paths are recorded as slash-separated strings (e.g., sharp/lethal). - Name/Lore Actions: New name_actions / lore_actions fields modify item names and lore on successful enhancement. Star-level effects also support type: "lore_action" for per-star lore control. - Expression Variables: Star-level attributes support expressions (e.g., "5 * {star}") for dynamic scaling. - PAPI Placeholders: %emakistrengthen_item_max_star%, %emakistrengthen_item_success_rate% (real-time with temper bonus), %emakistrengthen_item_crack_level%. - Enhanced Action Context: Success/failure actions now have {strengthen_max_star} and {strengthen_success_rate} placeholders.

Improvements

- Unified effects list format with type field. - Conditions support structured ConditionGroup parsing. - Two new comprehensive example files: example_recipe.yml (linear) and example_branch_recipe.yml (branching). - Config and language files auto-merge new keys on upgrade.

Breaking Changes

- stats → variables (supports expressions), attributes → ea_attributes in star configs. - success_actions / failure_actions → actions.success / actions.failure. - Material item → item_sources list format. - structured_presentation removed — replaced by name_actions / lore_actions. - Skill effect type: "skill" → "es_skill", skills → es_skills. - All old built-in recipes removed; replaced by example_recipe.yml and example_branch_recipe.yml.

Upgrade Notes

- Existing recipes must be migrated to the new format — refer to the new example files. - Branching is optional; recipes without branch_tree still work as linear enhancement. - Config version updated to 4.0.0. [View Full Documentation](https://jiuwu02.github.io/Emaki_Series/) | [Join Discord Community](https://discord.gg/FV4GFQbvCM) | [QQ Group](https://qm.qq.com/q/GqGrzHp0wU)

EmakiStrengthen 3.5.0 Release

This release improves strengthen recipe parsing and execution stability while aligning with the CoreLib 3.5.0 dependency line. - Improved strengthen recipe parsing and field handling. - Improved strengthen attempt execution, cost, failure, and result write-back flows. - Removed deprecated lifecycle cleanup calls. - Updated dependency alignment to CoreLib 3.5.0. - Synchronized plugin, config, and language versions to 3.5.0.

Upgrade Notes

- Existing recipe fields remain compatible. - Retest success, failure, material cost, and attribute write-back flows after updating. [View Full Documentation](https://jiuwu02.github.io/Emaki_Series/) | [Join Discord Community](https://discord.gg/FV4GFQbvCM) | [QQ Group](https://qm.qq.com/q/GqGrzHp0wU)

EmakiStrengthen 3.4.0 Dev Update

This dev update follows CoreLib's PDC attribute API refactor — attribute writing now uses PdcAttributeGateway instead of reflection. - PDC attribute writing: StrengthenPdcAttributeWriter now uses PdcAttributeGateway. - Structured display text: strengthen snapshots now evaluate display templates through CoreLib text config support. - Dynamic presentation support: expressions, nested variables, and random_text can be used in strengthen presentation content. - Recipe parser cleanup: parsing moved into StrengthenRecipeParser.

Upgrade Notes

No upgrade notes. [View Full Documentation](https://jiuwu02.github.io/Emaki_Series/) | [Join Discord Community](https://discord.gg/FV4GFQbvCM) | [QQ Group](https://qm.qq.com/q/GqGrzHp0wU)

EmakiStrengthen 3.3.0

EmakiStrengthen 3.3.0 adds PlaceholderAPI output for the strengthening state of the player's main-hand item. This makes star level, temper, recipe identity, eligibility, and attempt history easier to show in scoreboards, menus, quests, or admin tools. - PlaceholderAPI support: %emakistrengthen_mainhand_star%, %emakistrengthen_mainhand_temper%, %emakistrengthen_mainhand_recipe%, %emakistrengthen_mainhand_eligible%, %emakistrengthen_mainhand_success_count%, and %emakistrengthen_mainhand_failure_count% are available when PlaceholderAPI is installed. - Current attribute naming: default recipes continue using the current non-EA-prefixed attribute keys. - Admin cleanup remains available: /emakistrengthen clearstate can remove the strengthen layer from the held item. - Unified version fields: default config and language files use version. - Runtime cleanup: GUI-only material handling, interactions, rendering, and attribute write-back received maintenance.

Upgrade Notes

- Use Java 25. - Install PlaceholderAPI if you want the new placeholders. - Keep custom recipe attributes on the current naming scheme. - Keep player instructions aligned with GUI-only material consumption. [View Full Documentation](https://jiuwu02.github.io/Emaki_Series/) | [Join Discord Community](https://discord.gg/FV4GFQbvCM) | [QQ Group](https://qm.qq.com/q/GqGrzHp0wU)

EmakiStrengthen 3.2.0

EmakiStrengthen 3.2.0 tightens the strengthening flow around explicit GUI material handling, structured display output, and better admin cleanup controls. The practical result is a more predictable player workflow, cleaner default recipe presentation, and more flexible broadcast behavior for milestone star levels. - Admins now have a direct layer cleanup command. /emakistrengthen clearstate removes the strengthen layer from the held item, which is useful for support, testing, and state recovery. - Material handling is GUI-only now. Strengthening attempts resolve materials through a dedicated plan instead of silently topping up from the player's inventory. - Default display resources moved to `structured_presentation`. Recipes can organize stat lines with section_id and section_order, which makes layered lore output cleaner and easier to roll back. - Broadcast thresholds are more configurable. config.yml now exposes broadcast.local_stars and broadcast.global_stars, letting you separate nearby announcements from server-wide ones. - Attribute write-back is more isolated. A dedicated strengthen PDC writer helps keep post-strengthen item state cleaner across module interactions.

Upgrade Notes

- Migrate older display configs from presentation to structured_presentation. - Adjust player instructions if they still mention backpack auto-consumption. - Review the new local/global broadcast thresholds after upgrade. [View Full Documentation](https://jiuwu02.github.io/Emaki_Series/) | [Join Discord Community](https://discord.gg/FV4GFQbvCM) | [QQ Group](https://qm.qq.com/q/GqGrzHp0wU)

EmakiStrengthen Changelog

[3.1.0] - 2026-04-16

Added

- Added explicit per-star success_rates to the default weapon, armor, offhand, and generic strengthen recipes, while moving the shared baseline success table directly into config.yml. - Adopted CoreLib's shared config base classes, GUI template loader, and player session utilities to give the Strengthen module a common runtime foundation.

Improved

- Updated EmakiStrengthenPlugin, StrengthenLifecycleCoordinator, ChanceCalculator, and the GUI session/render pipeline so startup, chance calculation, and screen refresh behavior stay aligned. - Migrated strengthen_gui.yml to the nested sounds syntax and added hidden_components to filler items so the GUI matches the newer CoreLib conventions. - Cleaned up lore insertion anchors, material consumption definitions, and presentation rules across the bundled recipe set so different equipment categories behave more consistently.

Fixed

- Fixed lore search insertion still falling back to the old insert_below semantics, ensuring strengthen lines attach to their anchors instead of drifting to the wrong position. - Fixed coordination issues between the GUI, success-rate sources, and bundled recipes to reduce open-screen crashes, display inconsistencies, and value drift.

EmakiStrengthen 更新日志 / Changelog

中文版

新增特性

- 配方系统增强: StrengthenRecipe.java 83 行变更 - 重构配方数据模型 - 支持更灵活的配方配置和强化等级定义 - 配方加载器优化: StrengthenRecipeLoader.java 5 行变更 - 优化配方加载逻辑 - 改进错误处理

问题修复

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

English Version

Features

- Recipe System Enhancements: StrengthenRecipe.java 83 lines changed - Refactored recipe data model - Supports more flexible recipe configuration and strengthening level definitions - Recipe Loader Optimization: StrengthenRecipeLoader.java 5 lines changed - Optimized recipe loading logic - Improved 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 - AppConfigLoader Deletion: Removed configuration file loader - Replaced by CoreLib's unified configuration loading mechanism

EmakiStrengthen Changelog

[2.0.0] - 2026-04-09

Added

#### The strengthen system now uses a recipe-driven model - 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. #### Temper and optional-material mechanics - 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. #### Multi-currency cost and presentation actions - 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.

Improved

#### Admin commands and player flow were aligned with the new recipe model - 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

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

Upgrade Notes

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

Known Issues

- None