Links
Tags
Creators
Details
0.2.2
Compatibility
Changes
Fixes following:
Initiative's integration (gametest classes leaking into release jars on both loaders, public API types living outside the api package, no RNG seam for external consumers' deterministic tests)
Release jars are confirmed clean of gametest entries, and 0.2.1 is published to local Maven.
New CombatInteractionEvent fires whenever one entity attacks another always, even if damage gets cancelled. So other mods can detect combat with one listener instead of hooking loader damage events.
Suppression got safer: clear() is now test-only (clearAllForTesting()), and new suppressedUuids() lets you read who's suppressed.
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:75LzXbWL:R1Y2r338"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:75LzXbWL:R1Y2r338"
}

