Tags
Creators
Details
4.1.0
Compatibility
Required content
Changes
EmakiForge v4.1.0
Quality pity system, player signatures, Web console editor, and a completely refactored forge pipeline.
✨ New Features
Quality Pity System
After a streak of forges without a high-tier result, the system now guarantees a better quality outcome on your next attempt. No more endless bad luck — the pity mechanic has your back.
Player Signature
Every forged item now proudly displays the name of the player who created it, giving each piece of equipment a personal touch and a unique sense of ownership.
Web Console & GUI Editor
EmakiForge is now fully integrated with the Web management console. Edit forge recipes and GUI configurations directly in your browser. Both the forge interface and recipe book have been completely redesigned for a better player experience.
Forge Validation Service
A new pre-forge validation step ensures that all conditions are met before the forge operation proceeds, preventing invalid forge attempts.
Failure Resolution
A dedicated failure handling service provides flexible multi-tier penalty configurations — customize what happens when a forge attempt fails.
Preparation Phase
Material checking, consumption, and preview have been separated into their own preparation stage, making the forge flow clearer and more maintainable.
Result Post-Processing
Additional actions can now be executed after a forge completes — trigger skills, send messages, or run custom logic.
Performance Recorder
A new performance monitoring feature lets server admins track forge operation performance.
♻️ Improvements
- The main forge service has been extensively refactored, with each stage now having a clear, single responsibility.
- The material model has been simplified for more intuitive recipe configuration.
- The forge GUI and recipe book have been redesigned for a significantly improved user experience.
- The async executor has been optimized for faster forge response times.
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:Th7DAekf"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Ksqjj9TX:Th7DAekf"
}

