Tags
Creators
Details
Licensed GPL-3.0-only
Published 7 months ago
Updated 2 months ago
All versions
4.0.0
Release
Emaki Forge 4.0.06 months ago 34
Compatibility
Minecraft: Java Edition
1.21.x
Platforms
Paper
Purpur
Spigot
Required content
Unavailable version
Changes
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_actionsfields. Forging can directly modify item names and lore with actions likeappend_suffix,prepend_prefix,prepend,append,insert_below,replace_line. All operations tracked via ItemOperationLedger for precise revert capability. Material effects also supporttype: "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
effectslist format withtypefield (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_presentationremoved — replaced byname_actions/lore_actions.- Quality config
item_meta.structured_presentation→item_meta.name_actions/item_meta.lore_actions. - Material
itemfield →item_sources: [...]list format. - Skill effect type:
"skill"→"es_skill",skills→es_skills. - Old example recipe
flame_sword.ymlreplaced byexample_recipe.yml.
Upgrade Notes
- Migrate
structured_presentationtoname_actions/lore_actionsin existing recipes. - Migrate material
itemfields toitem_sourceslist format. - Config version updated to
4.0.0— new entries are auto-merged on upgrade.
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:Ksqjj9TX:wExARsrN"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Ksqjj9TX:wExARsrN"
}

