1.4.0
Compatibility
Changes
- Bug Fixes & Cleanup
Cleanup of Incorrect Command Duplicates // The incorrect alternative command /rebelion has been removed. A suspected /war duplicate was identified as a false positive, as the Brigadier framework automatically merges these.
Fixed a display error in the war GUI // An existing error in the display of surrender progress for the defending faction has been successfully corrected.
- System Improvements & GUI
Optimization of the claim request system // Village mayors can now request claims without an additional nation role. The /claim request command without a specific village name automatically assigns the chunk to the user’s own village instead of the parent nation.
Expansion of the Village Management Menu in the GUI // The menu under /nation gui now allows users to change village ranks, manage and kick members, and appoint new village mayors via a new, dedicated permission.
- System Reworks & Balancing (Mechanics)
Complete removal of the teleport feature // The /village tp command, the associated teleport permission, and the corresponding server configuration option have been completely removed from the mod.
Restructuring of the Capital City System // The /claim setcapital command has been removed. The capital city is now dynamically defined by the highest-ranked village (Capital City). From now on, losing a war requires the complete conquest of the entire village rather than just a single chunk.
Adjustment of Conquest and Surrender Logic // The war GUI displays the surrender progress live as a percentage. Villages no longer fall simply by losing the village center; they now also require the conquest of a rank-dependent, configurable chunk percentage (0% to 90%).
- Documentation
Update to the project documentation // The README file has been updated in all relevant sections (commands, mechanics, permissions table) and expanded to include new guides for the rebellion system and the village GUI.
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:442ThJ8M:YxcKVuhD"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:442ThJ8M:YxcKVuhD"
}

