Tags
Creators
Details
All versions
3.2.1
Release
LandClaimPlugin 3.2.1last month 530
Compatibility
Minecraft: Java Edition
26.2
26.1.x
1.21.6–1.21.11
Platforms
Folia
Paper
Purpur
Changes
[3.2.1] - 2026-09-15
Fixed
- Admin Command Console Execution & Argument Order:
- Fixed
/claim admin add chunk <player> <amount>failing to execute from server console (such as DeluxeMenus, donation stores, and server console scripts). - Aligned
/claim admin add chunkargument syntax to the documented order<player> <amount>instead of the previous reversed order. - Enabled console execution for
/claim admin reloadand the root shortcut/claim reload. - Replaced strict
PlayerSourcerestriction on the/claimroot builder withSource, allowing non-player senders for applicable administrative subcommands while preserving player-only restrictions on gameplay and GUI commands. - Resolved potential
ClassCastExceptionby properly handlingCommandSenderinstead of forcingPlayercasting in admin handler callbacks.
- Fixed
[3.2.0] - 2026-09-04
Added
- Claim Boundary Chat Notifications:
- Added configurable chat notifications upon entering and leaving claim territory (
claimChatNotifications.enabled). - Added personal player toggle command
/claim notify(alias/claim chatnotify) to opt in/out of chat notifications. - Added
landclaim.notifypermission node for command access. - Formatted messages configurable in
messages.ymlwith territory name placeholders (%claim%).
- Added configurable chat notifications upon entering and leaving claim territory (
- Server-Wide Visitor Settings Locking:
- Added server-wide lock setting
visitorSettings.lockedinconfig.yml. - Added configurable server default flags via
visitorSettings.defaultFlags(e.g. allowing exploration while restricting block breaking/placing). - Enforced server default flags during permission resolution when locked, completely bypassing individual profile overrides.
- Blocked access to
VisitorSettingsGUIwhen locked to prevent player confusion.
- Added server-wide lock setting
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:lndGv2Ps"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:PAlDTriF:lndGv2Ps"
}

