Tags
Creators
Details
2.2
Compatibility
Changes
Admin Dashboard Menu Removed The old Admin Dashboard menu has been removed. You can now access the full claim management menu by typing /nclaim admin menu. (We might re-add the admin menu with more options in future updates).
Customizable Claim Hologram Details You can now toggle the visibility of various sections on claim holograms! This includes the title, owner, expiration time, co-op count, and total size. Here's how to configure it in your config.yml:
hologram_settings:
show_title: true # Show title in hologram?
show_owner: true # Show owner name in hologram?
show_time_left: true # Show time left in hologram?
show_coop_count: true # Show co-op player count in hologram?
show_total_size: true # Show total claim size in hologram?
show_edit: true # Show edit text in hologram?
Configurable Expiration Time Colors You can now customize the colors (green, yellow, red) for the "Time Left" display based on different thresholds!
Example configuration in your config.yml:
hologram_settings:
time_left_thresholds:
- threshold: "day >= 2"
color: "&a" # Green
- threshold: "day >= 1"
color: "&e" # Yellow
- threshold: "day < 1"
color: "&c" # Red
Tip: You'll find more detailed information about hologram_settings in the config.yml file itself.
GUI Material, CustomModelData, and Custom Head Support We've added full material support to GUIs! You can now use any material you want in GUIs. Additionally, CustomModelData and CustomHead support are now available. Example usage: "HEAD:base64" and "MATERIAL:10000".
Gradient Support! You can now use gradients in your guis.yml and language files (like en-us.yml, tr-tr.yml)! Example: <#RRGGBB> </#RRGGBB>
French Language Support Added Bonjour! French language support has now been implemented.
Optional dependencies
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:qepTJym0:KBQ3RuXo"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:qepTJym0:KBQ3RuXo"
}

