Tags
Creators
Details
Licensed LGPL-3.0-only
Published 6 months ago
Updated 2 months ago
All versions
4.0.0
Release
Emaki Strengthen 4.0.06 months ago 26
Compatibility
Minecraft: Java Edition
1.21.x
Platforms
Paper
Purpur
Spigot
Required content
Unavailable version
Changes
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_treefor 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_actionsfields modify item names and lore on successful enhancement. Star-level effects also supporttype: "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
effectslist format withtypefield. - Conditions support structured
ConditionGroupparsing. - Two new comprehensive example files:
example_recipe.yml(linear) andexample_branch_recipe.yml(branching). - Config and language files auto-merge new keys on upgrade.
Breaking Changes
stats→variables(supports expressions),attributes→ea_attributesin star configs.success_actions/failure_actions→actions.success/actions.failure.- Material
item→item_sourceslist format. structured_presentationremoved — replaced byname_actions/lore_actions.- Skill effect type:
"skill"→"es_skill",skills→es_skills. - All old built-in recipes removed; replaced by
example_recipe.ymlandexample_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_treestill work as linear enhancement. - Config version updated to
4.0.0.
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:SH4PlNS2:5SdWGBA8"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:SH4PlNS2:5SdWGBA8"
}

