Tags
Creators
Details
Licensed ARR
Published 6 months ago
Updated 11 hours ago
All versions
1.0.9
Release
ClaimMod 1.0.9yesterday 6
Compatibility
Minecraft: Java Edition
26.1.x
Platform
Fabric
Supported environments
Server-side
Singleplayer
Required content
Any compatible version
Changes
ClaimMod 1.0.9
β¨ New
- BlueMap web map integration β every claim is drawn on BlueMap as an outlined area in its own toggleable "Claims" layer. Click a claim to see its name, owner, size, corners and trusted players. Colours, fill opacity, marker height and admin-claim visibility are set in the new
web_mapsection ofconfig.yml. Completely optional: without BlueMap nothing changes. - Personal notification mutes β any claim member can mute a claim's kill and/or death notifications just for themselves (
/claim manage mute, or one click in ClaimModCompanion). The claim'snotify_*flags keep working for everyone else. - New flag:
permanent_fireβ fire in the claim never spreads, never goes out (not even in rain) and never burns the block under it. Great for fireplaces on any block. Overridesfire_spread. - Companion: Trusted Claims list β the server now also sends the claims you're trusted in, for the companion's new β tab.
π‘οΈ Protection improvements
- Dispensers outside a claim can no longer dispense into it (lava, water, fire charges, placed blocksβ¦). Still allowed from another claim of the same owner, or when the claim lets visitors place blocks.
- Pistons (
piston_protection): outside pistons can no longer break blocks inside a claim or pull blocks out with sticky pistons β not just push blocks in. - Ravagers can no longer break crops in claims with
protect_cropson. - Lightning can no longer start fires in claims with
fire_spreadoff.
βοΈ Notes for server owners
- No new required dependencies. BlueMap is optional, like LuckPerms, EcoBal, BasicsMod, ShopShelves and TradeShelves.
- All new options and messages work with built-in defaults (web map on, marker height 64,
permanent_fireoff). To customise them, copy theweb_mapsection and thepermanent_fireline from the new defaultconfig.yml. - New permission node:
claimmod.flag.permanent_fire(defaulttrue). - Update ClaimModCompanion together with this version β the claim list data changed, so an older companion shows empty claim lists (nothing crashes).
Optional dependencies
Any compatible version
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:XoTGYdpA:Ccxnzr9p"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:XoTGYdpA:Ccxnzr9p"
}

