Links
Tags
Creators
Details
1.6.1
Compatibility
Changes
Open Parties and Claims: Warfare 1.6.1
First public Modrinth release of Open Parties and Claims: Warfare.
This is an unofficial warfare addon for Open Parties and Claims, adding chunk wars, contested claims, raid windows, protection rules, Create integration, Create Big Cannons protection, and optional Xaero war waypoints.
Added
- Single-jar distribution as
opac-warfare. - Open Parties and Claims territory and party integration.
- Chunk wars for party and personal claims.
- Preparation and active war phases.
- Contested chunks with capture progress.
- Claim transfer on successful capture.
- Original claim owner restore on cancelled or failed wars.
- Raid window support.
- AFK defender checks.
- Bossbar, actionbar, chat notifications, and war lives.
- Post-war protection.
- Claim protection rules for explosions, storage, villagers, and Withers.
/warplayer commands./waradminadmin commands./claimrulescommands for explosion and Create machine rules.- Create contraption, drill, saw, and block-breaking protection.
- Create Big Cannons projectile launch blocking and terrain-damage protection.
- Optional Xaero temporary war waypoints.
Required
- Minecraft 1.21.1
- NeoForge 21.1.232+
- Java 21
- Open Parties and Claims 0.27.5+
Optional integrations
- Create 6.0.9+
- Create Big Cannons 5.11.7+
- RPL 2.1.2+
- Xaero's Minimap for Minecraft 1.21.1
- Xaero's World Map for Minecraft 1.21.1
Installation note
Install only:
opac-warfare-1.6.1.jar
Do not install the separate customclaims_* module jars together with opac-warfare, because the single jar already contains all OPaC Warfare modules.
Notes
- This is an unofficial addon for Open Parties and Claims.
- This is the first public Modrinth release.
- Earlier versions were internal development builds.
- Server owners should make backups before using this on production worlds.
- Configs, balancing, and compatibility behavior may change in future versions.
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:kOE5HGwC:wJ2DYPnQ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:kOE5HGwC:wJ2DYPnQ"
}

