Tags
Creators
Details
Licensed GPL-3.0-only
Published 2 years ago
Updated 5 months ago
All versions
2.0.0-alpha.1
Alpha
Claim 2.0.0-alpha.16 months ago 27
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Unavailable version
Changes
[2.0.0-alpha.1] - 2026-04-26
Added
- Comprehensive Protection System (blocks break/place, bucket usage, and farmland trample).
- Permission Modes (PRIVATE/PUBLIC) for fine-grained interaction control (chests, doors, buttons).
- Configuration System (
claim-common.toml) with toggleable OP bypass settings. - Item-based (configurable) position selection system.
/claimcommand with support for selections and relative coordinates (~).- JSON-based claim persistence (saves to
world/data/claim/claims.json). - networking system to sync claims from server to client.
/claim listcommand with a custom 3D-styled management screen.
- Claim metadata system (trusted players, permission modes, color, and timestamps).
- Overlap protection to prevent players from claiming already occupied areas.
- Deep optimistic updates for instant configuration synchronization.
- Specialized Developer Testing rules (Creative/Dev bypass overrides).
Fixed
- Overhauled Xaero's Map integration: fixed color bleeding and corrected ABGR/RGBA conversion.
- Improved 3D previews to support terrain elevation variations and strict Y-boundary clipping.
- Compacted Configuration UI to support all screen sizes and GUI scales.
- Synchronized Configuration UI borders and 3D previews with selected color presets.
Changed
- Updated mod logo.
- Cleaned up source code and assets for a full project rewrite.
- Initialized alpha stage for version 2.0.0.
Full Changelog: https://github.com/yigit-guven/Claim/compare/1.1.0...2.0.0-alpha1
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:qhiyN1hu:YFoCKKxy"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:qhiyN1hu:YFoCKKxy"
}

