All versions
1.3.0
Release
Attribute Modify 1.3.038 minutes ago 4
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
NeoAttributeModify 1.3.0
New Features
Entity Attribute System
- Added support for modifying mob attributes through datapacks.
- Configure individual entities or entire groups using entity tags.
- Supports vanilla and modded attributes.
- Added entity attribute operations:
add,set,multiply_base, andmultiply_total. - Entity-specific rules take priority over matching entity tag rules.
- Attribute changes are automatically applied when mobs spawn, load, or when datapacks are reloaded.
- Preserves existing health and attribute modifiers from other mods.
- Improved attribute persistence and cleanup when rules are modified or removed.
Entity Effects
- Added configurable passive status effects for mobs.
- Added on-hit effects that apply status effects to attacked targets.
- Supports customizable effect levels, durations, probabilities, particles, and icons.
- Added support for direct attacks, mob-attributed projectiles, and area-based damage.
- Passive effects support infinite duration.
- Improved protection of status effects applied by Minecraft or other mods.
- Added read-only information about known and observed mob effects.
- Entity attributes, passive effects, and on-hit effects can be configured together in the same datapack files.
New Entity Editor
- Added
/attributemodify_entity_editor. - Create and modify entity rules directly in-game.
- Search for entities, entity tags, attributes, and effect information.
- Added server-provided entity catalogs and attribute information.
- Added Apply, Save, and Reload workflows.
- Added validation, conflict detection, and protection against overwriting rules from external datapacks.
- Improved handling of large entity catalogs and network responses.
Redesigned Item Editor
- Introduced the updated item editor interface from AttributeModify 1.3.0.
- Added searchable item, tag, and attribute selection.
- Improved navigation between Attributes, Mining, and Durability settings.
- Added improved scrolling and draggable scrollbars.
- Improved rule editing, confirmation dialogs, and save/reload feedback.
- Added base mining and durability information for supported items.
- The item editor is now opened with
/attributemodify_editor.
Improvements
- Ported major AttributeModify 1.3.0 features to NeoForge 1.21.1.
- Improved compatibility with Minecraft 1.21.1 attribute and equipment systems.
- Improved mining speed and harvest-tier handling.
- Added support for explicitly identified custom mining-tier block tags.
- Improved handling of vanilla mining-tier identifiers and aliases.
- Improved entity attribute synchronization and datapack reload behavior.
- Improved editor responsiveness, navigation, and state management.
- Added an option to disable additional attribute tooltip formatting.
- Improved multiplayer packet validation and editor permission checks.
- Improved protection against invalid or conflicting datapack rules.
- Improved handling of large server-side entity metadata.
Fixes & Stability
- Fixed incorrect mining-tier resolution for namespaced vanilla tiers.
- Fixed mining speed calculations for tools with low effective mining speeds.
- Fixed potential stale entity modifiers after datapack changes.
- Improved health preservation when updating entity attributes.
- Fixed several editor synchronization and stale-response issues.
- Improved Save and Reload transaction safety.
- Prevented unauthorized or conflicting editor changes from overwriting external datapacks.
- Improved recovery from malformed entity catalogs and invalid editor snapshots.
- Improved datapack reload validation and rollback behavior.
- Improved compatibility with foreign attribute modifiers and externally applied status effects.
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:bOWz461U:8jZscamL"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:bOWz461U:8jZscamL"
}

