2.0
Compatibility
Required content
Changes
Claim Mode Switch 2.0 – Changelog
This version is a major complete rework of Claim Mode Switch. The mod has been rebuilt with a new graphical menu system and many new quality-of-life features.
Main changes:
- New main menu opened with
/cc - Menu can also be opened with the
Hkey - The keybind can be changed in Minecraft’s controls menu
- Trust system directly inside the menu using player heads
- Players can trust or untrust other players for their claims
- New admin menu for server configuration
- Admins can configure claim rules directly through the menu
- Bypass and Builderpass management through player-head menus
- Bypass and Builderpass status is shown as a small text in the bottom-left corner
- Home system with configurable home limit
- Homes can only be set on your own claims or on claims where you are trusted
- Home teleport with a short countdown
- Pressing ESC cancels an active home teleport
- New Creative Inventory hybrid system
- Hybrid mode allows access to the Creative inventory without flight or invulnerability
- Hybrid mode shows hearts, hunger, XP bar and golden absorption hearts
- On their own claims, players can switch between Creative, Creative Inventory and Survival if enabled by admins
- In Creative Inventory areas, players can personally switch between hybrid mode and normal Survival
- Persistent storage for trusts, bypass players, builderpass players, homes and settings
- Improved trust notifications with message, actionbar and sound
- Improved menu design closer to the vanilla Minecraft style
- Added mod description, author and license metadata
Usage:
/ccopens the Creative Claim menuHalso opens the Creative Claim menu- Players can manage trusts, homes and personal modes through the menu
- Admins can manage rules, bypass, builderpass and home settings through the admin menu
Note:
This version must be installed on both the server and the client because it includes client-side features such as keybinds, HUD overlays and custom menu rendering.
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:4CWUJIvX:LtrYA6WD"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:4CWUJIvX:LtrYA6WD"
}




