Tags
Creators
Details
4.2.0
Compatibility
Required content
Changes
Attribute v4.2.0 makes the attribute system much friendlier to script-based extensions. You can now add runtime attributes, providers, and damage hooks without writing a separate Java plugin.
Highlights
- JavaScript extensions for runtime attributes, providers, and damage hooks.
- Damage hook scripts can inspect attacker and target attribute snapshots.
- Attribute script module access through
emaki.module("attribute").
Improved
- Generic MythicMobs JavaScript mechanics moved to CoreLib.
- Cleaner localized JavaScript extension logs.
- Less repeated startup output.
- CoreLib-managed bStats and runtime dependency handling.
Notes
- Review custom scripts and prefer
emaki.module("attribute").
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:8ZJV8VF6"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ZzBwu6WX:8ZJV8VF6"
}

