Tags
Creators
Details
Licensed LGPL-3.0-only
Published 4 years ago
Updated 8 hours ago
All versions
fabric-26.3-0.33.0
Beta
Open Parties and Claims 0.33.08 hours ago 1,132
Compatibility
Minecraft: Java Edition
26.3
Platforms
Fabric
Quilt
Supported environments
Server-side
Client and server
Required content
Any compatible version
Any compatible version
Changes
- Overhaul of the player config screen, including a new search bar, option categories and the ability to switch sub-configs while staying where you are.
- Fixed server-claiming just a single chunk not working when anchor-based claiming is enabled.
- Added admin-configurable player config options to control whether a player can claim or add new forceloads, so you're not forced to do that with claiming limits, which wasn't always ideal.
- Added new permission nodes, by default xaero.pac_claiming_paused and xaero.pac_new_forceloads_paused that pause claiming and new forceloads for a player.
- Added a new "Can Claim Next To" player config option that lets you choose who you want to be able to claim next to when claims are not allowed to touch by default on the server.
- Added a sub-claim switching and creation menu on the mod's main menu.
- Added a button on the mod's main menu to quickly open the config used for the current claiming mode and sub-claim.
- The mod now auto-assigns a sub-claim name for all new sub-configs.
- You now automatically switch the sub-claim when creating a new sub-config.
- Added tooltips to the player/claims config menu explaining what each config is used for.
- Made exception wildcards work with any language for cases where you're using a mod that extends what characters Minecraft identifiers support.
- Create train protection now uses block protection based on the train controls block.
- Made /oparties join work without an ID using the latest invite.
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| open-parties-and-claims-fabric-26.3-0.33.0-sources.jar | Sources jar | 1.22 MiB |
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:gF3BGWvG:KBCCg0os"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:gF3BGWvG:KBCCg0os"
}

