Tags
Creators
Details
All versions
3.3.0
Release
LandClaimPlugin 3.3.03 weeks ago 711
Compatibility
Minecraft: Java Edition
26.3
26.2
26.1.x
1.21.6–1.21.11
Platforms
Folia
Paper
Purpur
Changes
[3.3.0] - 2026-10-01
Added
- Combat Tag PvP Claim Protection Bypass:
- Actively combat-tagged players temporarily lose claim PvP protection while their combat tag is active (
combatTag.combatTagBypass: true), preventing them from initiating a fight in the wilderness and running into a claim to hide. - Integrated with DeluxeCombat, CombatLogX, PvPManager, and EternalCombat.
- Added robust combat hooks with reflection and Bukkit/Paper API fallbacks.
- Actively combat-tagged players temporarily lose claim PvP protection while their combat tag is active (
- Inactive Claim Auto-Decay & Exemption System:
- Added configurable automatic cleanup of inactive claims (
decay.enabled,decay.inactiveDays,decay.checkIntervalHours,decay.onlyCheckOwner). - Claims belonging to players who have been offline longer than
inactiveDays(default: 14 days) are automatically unclaimed and their profiles cleaned up. - Staff and VIP exemption support via permission
landclaim.decay.exemptand per-player exemption commands. - Added
/claim admin decay run(trigger manual decay sweep). - Added
/claim admin decay exempt <player> [true|false](toggle or set player exemption). - Added
/claim admin decay list(view all manually exempt players). - Added
INACTIVITY_DECAYreason toClaimDeleteEvent. - Added
decay_exemptdatabase column and automatic migration inSQLPlayerDao.
- Added configurable automatic cleanup of inactive claims (
Fixed
- Minecraft Entity Selector Resolution (
@s,@p,@a,@r):- Resolved
IllegalStateExceptionon Paper servers by scheduling entity selector resolution (Bukkit.selectEntities) on the primary server thread. - Extracted execution location and executor entity from Brigadier's
CommandSourceStack, correctly resolving@sand@pwhen commands are executed via/execute at @p ...or/execute as @p ....
- Resolved
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:PAlDTriF:HEQSoLcN"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:PAlDTriF:HEQSoLcN"
}

