Tags
Creators
Details
All versions
1.8.4
Release
BanFromClaim 1.8.43 months ago 283
Compatibility
Minecraft: Java Edition
26.3
26.2
26.1.x
Platform
Paper
Changes
- Fix hasTrust always returning false in GriefDefenderHook, plus several unguarded claim/owner null-checks across all 3 region hooks
- Fix false-positive update notifications, duplicate Residence listener registration, yaw config parsing, and remove dead code
- Convert Gradle build to Kotlin DSL, bump wrapper to 9.6.1, bump api-version to 26.2, and drop the now-dead legacy apiversions package
- Use real passenger API instead of manual position scanning, move claim-plugin lookups off the async thread, make data saves async, and cut other redundant per-event work
- Deduplicate repeated permission/teleport/suggestion logic across commands and hooks into shared helpers
- Add a configurable periodic check to catch banned players standing still inside a claim
- Micro-optimize move-event handling and bypass check ordering
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:6JvaV4V7:xYupcjlE"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:6JvaV4V7:xYupcjlE"
}

