Tags
Creators
Details
Licensed GPL-3.0-only
Published 7 months ago
Updated 2 months ago
All versions
2.2.0
Release
EmakiAttribute 2.2.07 months ago 13
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.x
Platforms
Paper
Purpur
Changes
EmakiAttribute Changelog
[2.2.0] - 2026-04-09
Added
New preview and lint admin commands
- Added
/emakiattribute preview [player] [slot]so operators can inspect the snapshot signature, item name, and non-zero attributes of a specific equipment slot directly. - Added
/emakiattribute lint, which summarizes load issues from config, attribute definitions, damage types, default groups, lore formats, presets, and PDC read rules for pre-launch or post-reload checks.
Improved
Better operational diagnostics and attribute display order
- The
previewsubcommand now provides player-name and slot completions, and the help output now includes clearer separators and command hints. - Default attribute priorities were reorganized for entries such as
attack_speed_vanilla,physical_damage_bonus,projectile_damage_bonus,spell_crit_rate, andspell_damage_bonus, making lore display order more stable.
Fixed
- The
previewcommand now distinguishes "no permission", "player not found", "invalid slot", and "no item in slot", which reduces ambiguity during investigation. lintnow validates whetherdefault_damage_typeandallowed_damage_causesactually point to loaded damage types, preventing dangling config references.
Upgrade Notes
- If you plan to run
/emakiattribute previewfrom the console, always provide both player name and slot explicitly. - If your item lore depends on the old default attribute ordering, re-check the rendered display after upgrading.
- It is recommended to run
/emakiattribute lintafter every reload of custom attributes, damage types, presets, or PDC condition rules.
Known Issues
- None
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:JIFVil9Y"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ZzBwu6WX:JIFVil9Y"
}

