Tags
Creators
Details
Licensed LGPL-3.0-only
Published 4 years ago
Updated 4 days ago
All versions
fabric-1.20.1-0.28.1
Beta
Open Parties and Claims 0.28.1last week 1,806
Compatibility
Minecraft: Java Edition
1.20–1.20.1
Platforms
Fabric
Quilt
Supported environments
Server-side
Client and server
Required content
Changes
- The default claiming mode will now be chosen automatically instead of claiming as yourself always being the default. If party-owned claims are enabled and you can claim as the party then you'll claim as the party by default. You can still change the mode manually.
- Fixed a way for party moderators to claim as the party owner despite party-owned claims being disabled.
- Added a new player config option to let every party member claim as your party. The default player config value is used by default, so it's very easy to change this for the whole server.
- Started ignoring permission-based claim and forceload limits for party-owned claims because it doesn't really work.
- Access to claims is now partially blocked when you are over the claim limit until you unclaim enough chunks to be back within the limit. Your allies are also partially blocked from accessing your claims when you are over the claim limit.
- Fixed owner transfer in the default party system breaking the online member counter, affecting forceloading.
- The default color for party-owned claims is now the party color when the primary party system supports colors.
- Fixed tooltips colliding with dropdown menus in some places.
- (1.21.10) Fixed other UI elements affecting the cursor style when hovered over a dropdown menu.
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| open-parties-and-claims-fabric-1.20.1-0.28.1-sources.jar | Source jar | 1.1 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:cL9Bpu8O"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:gF3BGWvG:cL9Bpu8O"
}


