Tags
Creators
Details
All versions
0.5.0
Beta
Beta v0.5.010 months ago 963
Compatibility
Minecraft: Java Edition
1.21.x
Platforms
Paper
Purpur
Changes
Mostly quality of life additions this time round. Not many additional protections added compared to last release, I guess it means the protections are already fairly comprehensive.
Added
- Support for Minecraft 1.21.11
- Action bar popup text on entering and exiting claim.
- New flag for villagers' ability to use doors.
- Auto claim visualisation refreshes when moving between chunks, joining the server, and switching dimensions.
- New config options to blacklist certain permissions and flags. This allows the action that would be blocked by permission/flag to always be allowed.
- Claim bells are now blocked from being created or moved into protected zones such as end portals and gateways.
- The mob flag now protects players dropping cobwebs from the weaving effect.
- New submenu for claim details. The primary icon in the management menu now shows the name, description, and location of claim.
- Claim tool can now be removed from inventory by clicking out of inventory window with item on cursor.
Changed
- Optimised the visualisation checks with a pre-cache to ensure visualisation checks aren't unnecessarily run.
Fixed
- Visualiser can now refresh when the claim tool state in hand is changed externally (e.g. wiping inventory using /clear, given via /claim)
- Visualisers showing up in all worlds instead of only the one where the claim exists in.
- Player permissions can now be modified when the player is offline.
- The button to Select all on player permissions works as intended.
- Falling blocks don't fall when mob flag is active.
- Versions 1.21.0-1.21.3 not working due to inventory framework.
- Claim tool not being removed from inventory on death.
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:hAvtSuKv:MUV1dGbK"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:hAvtSuKv:MUV1dGbK"
}

