Tags
Creators
Details
1.0.1
Compatibility
Changes
New Features
-
Piston Protection Flag (
PISTON_MOVEMENT): A new flag has been added to control piston interactions across claim borders. When set tofalse(the default), pistons can no longer push blocks into a claim from the outside or pull blocks out of a claim. -
Ender Pearl Flag (
ENDER_PEARL_TELEPORT): You can now prevent players from teleporting into a claim with an Ender Pearl. When the flag is set tofalse(the default), non-trusted players will be blocked from entering. -
Mob Griefing Flag (
HOSTILE_MOB_GRIEFING): A new flag has been added to control block damage from hostile mobs. When set tofalse(the default), mobs like Creepers, Endermen, and Zombies cannot destroy or alter blocks within the claim.
Changes & Improvements
-
Custom Greeting & Farewell Messages: The
ENTRY_MESSAGEandEXIT_MESSAGEflags have been upgraded from simple on/off switches to accept custom string messages.- You can now set a unique, colored message for players entering or leaving a claim using the
/claim flag <flag_name> <message>command. - This allows for personalized greetings (e.g., "&aWelcome to my shop!") instead of the old generic message.
- You can now set a unique, colored message for players entering or leaving a claim using the
-
Configuration File Overhaul: The
config.ymlhas been completely corrected and improved.- Correction: The file no longer contains incorrect settings from an unrelated "water system" plugin. It now holds the actual, functional configuration options for GriefProtection999.
- Documentation: The
config.ymlis now heavily commented to provide a comprehensive guide to every setting and flag available, explaining what each one does and how to use it.
-
Removed
WEATHER_CONTROLFlag: The non-functionalWEATHER_CONTROLflag has been removed from the plugin.
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:1wcgXlG0:kmMTPfE6"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:1wcgXlG0:kmMTPfE6"
}

