Tags
Creators
Details
Licensed LGPL-3.0-only
Published 4 years ago
Updated 4 days ago
All versions
fabric-1.21.8-0.26.1.
Beta
0.26.14 months ago 622
Compatibility
Minecraft: Java Edition
1.21.8
Platforms
Fabric
Quilt
Supported environments
Server-side
Client and server
Required content
Changes
- Added personal player groups that every player can define in their player configs. Server claims, expired claims and wilderness claims can also have custom player groups defined.
- Converted every single player config option that had multiple possible levels of protection/exception based on party relations to a player group exception option. You are no longer confined by party relations. Keep in mind that most options were also reversed in meaning by being converted from protection enabling options to exception enabling options. Not only was this necessary to work with the new player group system but it also seems more intuitive to use.
- Reversed the meaning of some toggle options so that they're more consistent with the player group exception options. Other toggle options were left untouched because the wording felt more natural that way.
- Replaced the "Protect From Party" and "Protect From Allies" options with a single "Full Access" option that you can set to a group.
- Made explosion protection respect entity block access exceptions. This means that giving creepers block access will now let them blow up things even if explosion protection is enabled.
- For Addon Developers: This update contains player config API changes. While the API should still be more-or-less backwards compatible, it is recommended to switch to non-deprecated API for optimal performance and to be able to fully benefit from the new player group system.
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| open-parties-and-claims-fabric-1.21.8-0.26.1-sources.jar | Source jar | 1.06 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:9EMq3igz"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:gF3BGWvG:9EMq3igz"
}


