Tags
Creators
Details
0.2.0-beta
Compatibility
Changes
📜 Changelog — FabulousClaims 0.2.0-beta ✨ Added Vault economy integration
Players can be charged for claim creation.
Balance checks and withdrawals now use OfflinePlayer for cross-version compatibility.
LuckPerms group limits
Claim limits can be configured per group via LuckPerms.
Fallback to default limits if no group is matched.
Adventure API support
GUI and messages now use net.kyori.adventure.text.Component for modern formatting.
Added repository and dependency for Adventure API (Spigot) or native support (Paper).
Visualization improvements
Particle names updated to Particle.VILLAGER_HAPPY for compatibility across 1.13+.
Claim boundaries can be visualized with particles.
Permissions reference sheet
Documented all permission nodes for server owners.
Plugin.yml improvements
Version bumped to 0.2.0-beta.
Added softdepend: [Vault, LuckPerms].
Expanded command aliases (/claims, /fc).
Polished descriptions for clarity.
🛠️ Fixed Maven build issues
Added correct repositories for Spigot, Paper, LuckPerms, Vault, and Adventure.
Resolved missing dependencies (VaultAPI, Adventure API).
Cleaned Maven cache to fix snapshot resolution.
Particle enum mismatch
Replaced Particle.HAPPY_VILLAGER with Particle.VILLAGER_HAPPY.
Economy methods
Updated Vault calls to use OfflinePlayer instead of Player.
📦 Changed Compile target
Now compiles against spigot-api:1.20.1-R0.1-SNAPSHOT for broad compatibility.
Plugin versioning
Version scheme updated to semantic pre-release: 0.2.0-beta.
Documentation
Added compatibility matrix for Spigot/Paper/Bukkit across 1.16–1.21+.
Permissions sheet prepared for publishing.
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:kX04h4Sr:xP6ip4EY"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:kX04h4Sr:xP6ip4EY"
}

