Tags
Creators
Details
Licensed GPL-3.0-only
Published 7 months ago
Updated 2 months ago
All versions
3.1.0
Release
EmakiAttribute 3.1.06 months ago 24
Compatibility
Minecraft: Java Edition
1.21.x
Platforms
Paper
Purpur
Spigot
Changes
EmakiAttribute Changelog
[3.1.0] - 2026-04-16
Added
- Added a
default_profileblock inconfig.ymlso base resources and base attributes now live in the main configuration instead of the oldprofiles/global.ymlfile. - Added a flexible
checksmodel for condition files withpdc_meta,pdc_attribute, andlore_regexsupport; the default Forge, Strengthen, and bind conditions now use the new structure as well.
Improved
- Reworked lifecycle, directory loading, default-profile registration, and PDC read-rule handling so reload-time discovery, registry refresh, and summary output stay consistent.
- Introduced
AttributeFusionMathand updated snapshot collection, stage calculation, movement speed sync, and attack-speed sync so fused combat values map back to vanilla behavior more consistently. - Replaced string-based managed vanilla targets with direct
Attributetracking to reduce repeated resolution and runtime-specific divergence.
Fixed
- Fixed a startup crash on Leaf / Spigot-style runtimes where vanilla attribute binding could fail when a runtime-specific API path was missing.
- Corrected the minimum value semantics for
physical_crit_damageand clarified the default health resource description to avoid misleading defaults. - Fixed inconsistent health, movement-speed, and attack-speed syncing when fused combat snapshots were re-applied after reload.
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:FGi47mOo"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ZzBwu6WX:FGi47mOo"
}

