1.0.0
Compatibility
Changes
-
Fixed: Heroic golem wouldn't actually attack. It was only told its target once at the moment of spawn — vanilla Iron Golems are passive toward players and clear that target almost immediately on their own. The golem now keeps re-asserting its target (your last hit, skipped if trusted) for as long as it's alive and that target stays valid, so it actually follows through on the attack.
-
Fixed: ability assignments didn't survive a server restart. Abilities were only ever held in memory — nothing loaded or saved them to disk, so stopping the server from console wiped everyone's ability. Assignments are now written to players.yml in the plugin's data folder every time an ability is given, removed, or swapped on a kill, and reloaded automatically on startup.
-
Added a save on plugin shutdown as a backup in case anything changed right before the server stopped.
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:lKvSIfrq:6Ait9BYL"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:lKvSIfrq:6Ait9BYL"
}

