Tags
Creators
Details
All versions
3.0.0
Release
LandClaimPlugin 3.0.02 months ago 406
Compatibility
Minecraft: Java Edition
26.2
26.1.x
1.21.6–1.21.11
Platforms
Folia
Paper
Purpur
Changes
[3.0.0] - 2026-08-30
Added
- Radius Claiming & Unclaiming:
- Added
/claim radius <1-5>and/unclaim radius <1-5>for bulk area territory expansion and contraction. - Automatically respects permission gates, claim limits, world blacklists, WorldGuard boundaries, and adjacency rules.
- Added
- Instant Particle Feedback & Quota Progress:
- Dynamic temporary boundary visualization flash upon claiming or unclaiming chunks.
- Pling/Bass audio feedback for interactive confirmation.
- Chat quota indicator displaying
<chunks>/<limit>claimed.
- Auto-Unclaim Command:
- Registered
/unclaim autoallowing players to unclaim chunks as they move.
- Registered
- In-Game Held Territory Map (Minimap):
- Live 128×128 pixel radar map rendering directly onto a vanilla
FILLED_MAPitem using Bukkit'sMapView&MapRenderercanvas. - Accurate player-centered projection tracking smooth sub-chunk movement across 16×16 blocks.
- Renders chunk polygons, boundary grid lines, custom profile claim colors (
#RRGGBB), allies (#9b59b6), members/trusted (#3498db), foreign claims (#e74c3c), and wilderness (#282c34). - Real-time rotating player cursor (
MapCursor.Type.PLAYER) and dynamic territory name banner. - Interactive right-click zoom toggle between Overview mode (16×16 chunks) and Close Detail mode (8×8 chunks) with audio feedback.
- Full Bedrock / Geyser support (rendered seamlessly in hand, off-hand, and wall Item Frames).
- New commands:
/claim minimap,/claim map,/claim menu map. - New permission:
landclaim.minimap(default:true). - Configurable via
minimapsection inconfig.yml.
- Live 128×128 pixel radar map rendering directly onto a vanilla
- Modrinth Update Checker:
- Automated asynchronous update checker querying the Modrinth v2 API on startup (
PAlDTriF). - Interactive MiniMessage join notification with clickable links for server operators/admins with
landclaim.update.notifypermission. - Configurable via
updateCheckersection inconfig.yml.
- Automated asynchronous update checker querying the Modrinth v2 API on startup (
- Action Bar Display Toggle:
- Added
actionbarEnabledoption (default:true) to enable/disable claim status and wilderness action bar messages.
- Added
- Java 25 & Paper 26.2+ Compatibility:
- Upgraded bytecode target to Java 25 (
release 25, class file version 69.0) aligned with Paper API26.2.build.120-stable. - Upgraded
maven-shade-pluginto3.6.0with ASM 9.8 for Java 25 bytecode relocation.
- Upgraded bytecode target to Java 25 (
Changed & Improved
- Unclaim Command Consolidation:
- Unified all unclaiming commands exclusively under
/unclaim(/unclaim,/unclaim radius <1-5>,/unclaim auto,/unclaim all [confirm]). - Removed duplicate unclaim subcommands from
/claim.
- Unified all unclaiming commands exclusively under
- SQL Error Handling & Transaction Integrity:
- Fixed
CompletableFutureexception propagation inSQLProfileDaoandSQLWarpDaoto prevent cache desyncs on rolled-back transactions. - Removed redundant queries in
SQLProfileDao.getProfile. - Added safe
Material.getMaterial(...)fallback inSQLWarpDaoto prevent server startup crashes on missing/renamed materials.
- Fixed
- Role Cleanup on Ownership Transfer:
- Automatically cleans up member and trusted roles for the new owner upon claim transfer.
Removed
- Legacy V1 Code Purge:
- Removed dead legacy
Claim.javaandChunkSelection.javamodels. - Removed unused
ClaimDao,SQLClaimDao,RoleDao, andSQLRoleDao. - Removed legacy
claimCachefromCacheManagerandINVALIDATE_CLAIMfromRedisManager. - Removed outdated inventory-based GUI map (
ClaimMapGUI,ClaimMapInfoGUI) in favor of the high-resolution held Territory Map.
- Removed dead legacy
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:SLdzY2lN"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:PAlDTriF:SLdzY2lN"
}

