Tags
Creators
Details
Licensed LGPL-2.1-only
Published 2 years ago
Updated 2 weeks ago
All versions
2.0.2
Release
Clowder Update – Warfare & Raid Overhaul5 months ago 53
Compatibility
Minecraft: Java Edition
1.7.10
Platform
Forge
Supported environments
Client and server
Changes
Clowder Update – War & Raid Overhaul
Warfare Rework
/xc warenablenow enables war declarations- Wars are now faction vs faction
- Wars can only be declared against factions considered online (2+ players)
- Allied factions can join allied wars
- Allies can no longer declare war on each other
- Breaking an alliance now applies a 24-hour war cooldown
War Diplomacy
-
Surrender
- Allows a faction to surrender
- Applies an 84-hour war cooldown if accepted
-
Ceasefire
- Applies a 24-hour war cooldown if accepted by both parties
-
Peace
- Applies an 84-hour war cooldown if accepted by both parties
Raid Rule Changes
Factions can only be raided if:
- They are considered online
- Less than 30 minutes have passed since dropping below the online threshold
- 12+ hours have passed since the war declaration
Grace & Protection Systems
-
Added admin-controlled new player protection:
- 4-hour grace period
- 24-hour keep inventory
-
Added
/c gracebuild- One-time 48-hour build grace
- Grace factions cannot attack or be attacked
- Grace factions cannot enter wilderness or foreign land
- Foreign factions cannot enter grace faction territory
Admin Controls
- Added admin commands to individually control war/raid restriction checks
- Legacy behavior can be re-enabled if desired
Fixes & Improvements
- Fixed
/c mergenot transferring claimed territory correctly - Fixed crash when MCHeli is not installed
- Claim flags now broadcast when enemy territory claiming successfully begins
- Improved clowder command error feedback and usage guidance
- Reorganized
/c helpoutput
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:5XIaYcvL:4RopHNtp"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:5XIaYcvL:4RopHNtp"
}

