Tags
Creators
Details
Licensed ARR
Published 2 years ago
Updated last month
All versions
0.6.0
Release
ChunkClaimPlugin 0.6.06 months ago 463
Compatibility
Minecraft: Java Edition
26.1.x
1.21.x
Platforms
Bukkit
Paper
Spigot
Changes
- Command Prefix Update: The plugin alias is now officially /ccp\ for faster typing!
- Dual API Support: Single universal JAR compatible with both \1.21.0-1.21.11\ and \26.1+\ servers.
- Item-Based Claiming: Claim chunks by simply right-clicking with a configurable item (Default: Wooden Shovel).
- Chunk Entry Titles: See a Welcome Title and Subtitle when entering a claimed area.
- Granular Permissions: Full LuckPerms support with \ccp.claim, \ccp.unclaim, \ccp.check, \ccp.info, \ccp.visualize, \ccp.expand, \ccp.lang, \ccp.settings, \ccp.teleport, and \ccp.transfer.
- GUI Enhancements: Added 'Back' buttons for easier menu navigation.
- Rename Claims: Rename your claims seamlessly via an interactive chat prompt directly from the GUI.
- Granular Interaction Settings: Protect or allow access to specific blocks via the GUI:
- Chests & Containers
- Furnaces
- Crafting/Utility blocks (Stonecutters, etc.)
- Doors/Trapdoors
- Redstone Inputs (Buttons/Levers)
- Mob Protection (toggle damage to passive mobs like cows and pigs)
- Message Toggle System: Admins can now disable specific chat messages (deny notifications, success messages, etc.) via \config.yml\ without code changes.
- Claim Ownership Transfer: Transfer claim ownership to other players directly from the claim details GUI with all settings preserved.
- Teleport Command: Use /chunktp <name>\ to quickly teleport to any of your claims by name.
- Fixed Player Combat: Players can now properly attack each other; the PvP flag correctly controls only player-vs-player interactions.
- New Languages: Added full support for German (\de_DE), Portuguese (\pt_BR), and Russian (\ru_RU).
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:8C4QfJDU:gII4QUXZ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:8C4QfJDU:gII4QUXZ"
}

