All versions
1.1.0
Release
Claim Kickstart 1.1.08 months ago 79
Compatibility
Minecraft: Java Edition
1.21.x
1.20.x
Platforms
Paper
Purpur
Changes
[1.1.0] - 2026-02-16
Added
- Configurable reward delivery mode (
reward-delivery-modein config.yml)AUTO(default): original behavior — grant immediately, drop at feet if inventory fullCLAIM_CHAT: sends a clickable chat message; reward only granted when player clicks it
- Claim token system for CLAIM_CHAT mode:
- Tokens are bound to the player's UUID — cannot be used by other players
- Tokens expire after a configurable duration (
claim-token-expiry-minutes, default 10) - Full inventory on click shows an error and allows retry (no drop, no grant)
- Already-claimed tokens are invalidated
/ck claim <token>internal command (used by clickable chat, not for manual use)- New config messages:
claim-chat-prompt,claim-chat-success,claim-chat-full-inventory,claim-chat-already-claimed,claim-chat-expired,claim-chat-invalid - Periodic expired token cleanup (every 5 minutes)
Added (1.1.0 extras)
- Project icon for Modrinth/launcher display (golden shovel in hexagonal frame)
- Icon embedded in jar as
icon.pngfor future Paper plugin metadata support
Changed
- Compiled against Paper API 1.21.1 (previously Spigot API)
- Java target updated to 21
Unchanged
- AUTO mode behavior is identical to 1.0.0 — no breaking changes for existing servers
- All existing config keys, commands, and permissions remain the same
[1.0.0] - 2026-02-15
Added
- Initial release
- Automatic golden shovel reward on first chest placement
- GriefPrevention integration (optional soft dependency)
- Full inventory handling (drop at feet)
- Admin commands:
/ck reload,/ck grant,/ck reset,/ck status - Configurable reward item, amount, and messages
- Flat-file data storage (data.yml)
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:bXgM0jd9:zYQzPBWH"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:bXgM0jd9:zYQzPBWH"
}

