Links
Tags
Creators
Details
All versions
1.6.6
Beta
Open Parties and Claims: Warfare 1.6.63 months ago 1,378
Compatibility
Minecraft: Java Edition
1.21.1–1.21.11
Platform
NeoForge
Supported environments
Server-side
Client and server
Changes
1.6.6
Added
- Persistent attack and defense cooldown windows for war declarations, including saved slot usage after restarts.
- Configurable cooldown durations and target-chunk limits for each role.
war/side-cooldowns.datfor persisted cooldown state.- A separate
/claimrules assemblyrule for Create and Sable contraption assembly. - Settings for global war notifications, bossbars, and Xaero markers.
Changed
- Updated the mod version to
1.6.6. - Daily outgoing and incoming war-start limits are disabled by default (
0) but remain available as optional additional quotas. - Post-war protection now applies to all claims owned by the defending side rather than individual chunks.
- Replaced
max_active_wars_per_partywith role-specific cooldown limits; a side cannot attack and defend at the same time. /claimrules createnow covers only Create and Offroad mining machines; assembly is controlled through/claimrules assembly.- Removed storage-specific protection, leaving container access and breaking behavior to vanilla and OPaC.
- Villager, wandering trader, and Wither protections are disabled by default and remain configurable opt-ins.
- War notifications, bossbars, and Xaero markers for active/preparing wars are visible to all compatible players by default; settings can restore side-, admin-, and radius-based filtering.
Fixed
- Fixed denied Sable assemblies potentially leaving an orphan sub-level and causing a critical server error.
- Fixed Sable assembly bounds detection, removing misleading reflection warnings and unnecessary fallback handling.
- Create and Sable assemblies now validate all eight source AABB corners when crossing claims.
Notes
- The first successful declaration starts fixed windows:
2hours for the attacker and1hour for the defender by default. - Later successful starts consume slots without extending the window.
- A duration of
0disables only the timed quota, not the concurrent-war limit. - Xaero markers contain active-war metadata only and never expose a global claim-owner map.
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:huf0vwbj"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:kOE5HGwC:huf0vwbj"
}

