All versions
2.2
Release
OpenPAC Claim Mode Switch 2.23 days ago 6
Compatibility
Minecraft: Java Edition
1.21.4
Platform
NeoForge
Supported environments
Client and server
Changes
Claim Mode Switch 2.2
New Features
- New F3 + F4 Creative Claim game-mode switcher, showing only modes that are actually allowed at the player's current location.
- Creative Inventory can now be selected directly through the game-mode switcher.
- New admin command:
/ccsetmode <player> <creative|creative_inventory|survival|adventure|auto>. - Admin-forced game modes remain saved until automatic claim rules are restored with
auto. - New admin command:
/ccreload. - Bypass and Builderpass players can now switch their mode through
/ccas well. - The Creative Inventory HUD now includes the armor bar.
OpenPAC & Profiles
- Claim-to-profile resolution for Open Parties and Claims has been reworked.
- Per-profile trusts are now correctly respected when actually entering the corresponding claim.
- The configured trusted-player mode per profile is now applied to the real claim at runtime.
- Existing profile data from 2.1 remains compatible.
- OpenPAC server claims are now detected correctly and use the Server chunks setting.
Fixes & Stability
- Game-mode enforcement has been centralized so Minecraft and Creative Claim no longer fight over the player's mode.
- F3+F4 selections are additionally validated by the server.
- The H key now opens
/ccmore reliably. - Personal game-mode preferences can no longer override foreign, trusted or server-claim rules.
- Save files are written more safely and flushed again during a normal server shutdown.
- Duplicate game-mode tick logic has been removed.
- Several obsolete development leftovers have been removed.
- Version, network and Modrinth metadata have been updated to 2.2.
- Open Parties and Claims 0.27.5 or newer is now required.
Performance
- Claim and game-mode checks continue to run only every 4 ticks (~0.2 seconds).
- Duplicate OpenPAC lookups during a game-mode refresh have been reduced.
- OpenPAC profile resolution is briefly cached.
- Unnecessary competing tick handlers have been removed.
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:dYKxZY1g"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:4CWUJIvX:dYKxZY1g"
}

