Tags
Creators
Details
Licensed GPL-3.0-only
Published 7 months ago
Updated 2 months ago
All versions
4.0.0
Release
Emaki Attribute 4.0.06 months ago 36
Compatibility
Minecraft: Java Edition
1.21.x
Platforms
Paper
Purpur
Spigot
Required content
Unavailable version
Changes
EmakiAttribute 4.0.0 Release
This release adds skill-based damage integration, enhanced damage messages, and PAPI placeholder expansion, while unifying condition expression syntax.
New Features
- EmakiSkills Damage Integration: When EmakiSkills is installed, skill scripts can use
attribute_damageto trigger the full attribute damage pipeline (attribute bonuses, crits, penetration, dodge, damage messages, etc.) with configurable damage type, target, and element tag. - Enhanced Damage Messages: New placeholders in damage message templates:
{attacker_health},{attacker_max_health},{target_health},{target_max_health},{distance}. - PAPI Resource Regen Placeholder:
%emakiattribute_resource_<id>_regen%returns per-second regeneration rate for HUD/scoreboard display. - Damage API: Other plugins can invoke the attribute damage pipeline via
EmakiAttributeBridge.applyDamage().
Improvements
- Config and language files auto-merge new keys on upgrade.
- All attribute definition files and condition files now include detailed field comments.
- Console log messages streamlined for cleaner startup/shutdown output.
Breaking Changes
- Condition expression syntax changed from
%value%to{value}(e.g.,%player_name%→{player_name}). Custom condition files must be updated manually.
Upgrade Notes
- Default condition files are auto-updated; custom condition files need manual syntax migration (
%var%→{var}). - Config version updated to
4.0.0— structure remains compatible, new entries are auto-merged.
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:dCg9vBHg"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ZzBwu6WX:dCg9vBHg"
}

