Tags
Creators
Details
1.1.0
Compatibility
Changes
Release 1.1.0!
A whole bunch of cool stuff added! Now play with all the dying player's stuff! Now, having such armor or holding such item is also a condition option! And I see you server administrators! I admit, that mod was floody as hell. But I fixed that! Your console will be much cleaner now. You though the file's condition properties' names were disturbing? I also fixed that. And don't panic! I also handled the file versioning! (Aren't I amazing?) And... Stop right there! I see you flooding your config file with all the combinations of conditions you can imagine with the now options! But behold! You can now use lists! (Warning. Lists will be validated if any element is valid, so a whole bunch of possibilities with only two lists)
I got a little bit carried away for that update message, but I hope you like that new content ^^
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:64koG3e4:UYzZJXBK"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:64koG3e4:UYzZJXBK"
}

