Tags
Creators
Details
3.4
Compatibility
Changes
Core & Performance
- NBT-API Update: Bumped to version 2.15.5. Fixed compatibility issues with Minecraft 1.21.1.
- Auto-Migration: Implemented a new configuration versioning system. Config, GUI, and Lang files now automatically update with new keys while preserving your existing settings.
- Hologram Support: Optimized FancyHolograms and DecentHolograms integration with improved default offsets.
- Database & Storage: General optimizations for claim data loading and saving.
Security & Bug Fixes
- Exploit Fix (End Crystals): Prevented End Crystals from damaging blocks inside claims. Non-owners can no longer detonate crystals within claimed territories.
- Exploit Fix (Flying Machines): Blocked piston-based flying machines from entering and griefing claims.
- Admin Interaction: Fixed an issue where admins accidentally opened the claim menu. Admins must now Sneak + Right-Click to access management menus.
- TNT Logic: End Crystals will no longer cause block damage if TNT damage setting is disabled.
UI & UX Improvements
- Admin Menu Filters: Added new filtering options based on sale status (All, For Sale, Not For Sale).
- Selection Visibility: Selected claims in the Admin Menu now show an item amount of 2 for better visual feedback.
- Dynamic Menus: Changed claim_id to display_slug in the My Claims menu for better readability.
- Actionbars: Added {display_name} support to movement actionbars.
- Naming System: You can now give your claim a custom name during the initial purchase.
Commands & Management
- Claim Naming: Added /nclaim name <name> for players to set custom display names for their claims.
- Admin Slug Management: Admins can now view all claim slugs and manage names via /nclaim name <slug> <name>.
- Claim Marketplace: Fully implemented the claim selling system. Players can set prices and list claims via the GUI.
With this version, the config structure has changed, so the plugin will back up your old files to the backups folder upon startup and then update them. If you encounter any issues, you can reach us via Discord.
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:MP2O67Cx"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:qepTJym0:MP2O67Cx"
}

