Tags
Creators
Details
4.74.1
Compatibility
Changes
-Added <include_entities> parameter to to_range action type, whether the action must also apply to other entities and not only players.
-Added %is_critical% variable to player_attack event.
-Added %player_is_present% variable to custom events to check whether the player exists in the executed event or not.
-Fixed issue with hide_join_message action type on player_join events.
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:4EEcEnDG:aKaGo5gj"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:4EEcEnDG:aKaGo5gj"
}

