Tags
Creators
Details
Licensed GPL-3.0-only
Published 7 months ago
Updated 2 months ago
All versions
3.1.0
Release
EmakiForge 3.1.06 months ago 20
Compatibility
Minecraft: Java Edition
1.21.x
Platforms
Paper
Purpur
Spigot
Changes
EmakiForge Changelog
[3.1.0] - 2026-04-16
Added
- Added
ForgeMaterialUsagePlannerto centralize required/optional material batching, capacity cost/bonus calculation, and unconsumed input return logic for more predictable forge resolution. - Adopted CoreLib's
AbstractConfigurableEmakiPlugin,BaseAppConfig, and sharedGuiTemplateLoaderso Forge now shares the common config and GUI-loading foundation.
Improved
- Reworked
EmakiForgePlugin,ForgeLifecycleCoordinator, andForgeRuntimeComponentsso PDC attribute registration, service exposure, and CoreLib assembly feedback wiring follow one consistent startup path. - Hardened interactions in the forge station, recipe book, and editor by covering keyboard clicks, drag behavior, held-item validation, and session-state management.
- Updated
config.yml,gui/*.yml, and language resources so button sounds, hidden tooltips, and GUI structure follow the newer CoreLib GUI syntax.
Fixed
- Fixed inconsistent optional-material batching, capacity bonuses, and leftover input return behavior when multiple matching materials were supplied together.
- Fixed edge cases in item identification, recipe matching, and editor dirty-state handling to reduce false input mismatches and lingering editor state.
- Fixed the timing of PDC attribute registration so Forge keeps writing external attribute data reliably after reloads and dependency rewiring.
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:oQaowyHc"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Ksqjj9TX:oQaowyHc"
}

