1.0.2
Compatibility
Changes
New feature in this version 1.0.2
A new server configuration option has been added that allows you to decide what happens when a GuardStone is broken.
By default, the behavior is the same (the stone breaks and drops the block normally).
If the server administrator enables this new option in the GuardStone configuration file, when the owner (or an operator with permissions) breaks their GuardStone, it will be completely destroyed and disappear without dropping any item.
This is the main new feature in this version.
destroy_guardstone_on_break = true
You can modify this in-game if you are an OP (Operational Leader) with the command
/guardstone admin
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:jyzyCn5L:ysaTCK7v"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:jyzyCn5L:ysaTCK7v"
}

