Tags
Creators
Details
4.1.0
Compatibility
Required content
Changes
EmakiAttribute v4.1.0
Vanilla damage takeover, combat debug system, scaling curves, and attribute contribution API.
✨ New Features
Vanilla Damage Takeover
A new configuration option lets you control whether EmakiAttribute fully takes over vanilla damage calculation, giving you complete control over how damage is computed in your server.
Perfect Takeover Coordinator
A new coordination mechanism ensures smooth integration between EmakiAttribute's damage calculation and vanilla Minecraft damage events, preventing conflicts and double-calculations.
Combat Debug System
A new combat debug handler and listener allow server admins to trace damage calculations step by step — invaluable for debugging complex combat mechanics and ensuring everything works as expected.
Damage Calculation Cache
A new caching service reduces redundant damage calculations, improving combat performance especially in high-frequency combat scenarios.
Scaling Curve Configuration
Customizable attribute scaling curves allow you to define how attribute values grow — linear, exponential, logarithmic, or any custom curve you need for balanced stat progression.
Attribute Contribution API
A new API interface allows other plugins to register custom attribute sources, enabling cross-plugin attribute bonuses and integrations.
Web Console Integration
EmakiAttribute is now accessible through the built-in Web management console, allowing you to edit attribute configurations and damage types directly in your browser.
♻️ Improvements
- The damage handling system has been refactored, splitting the original monolithic listener into a dedicated combat damage listener for cleaner, more maintainable code.
- Lore format templates have been updated and optimized.
- The attribute snapshot collector has been optimized for better performance.
- The attribute API has been extracted to a separate module for cross-plugin reference.
- Language files have been significantly expanded with new translations.
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:ZzBwu6WX:Zp2umdBS"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ZzBwu6WX:Zp2umdBS"
}

