Tags
Creators
Details
Licensed GPL-3.0-only
Published 3 years ago
Updated 10 months ago
All versions
1.6.0
Release
Konquest 1.6.02 years ago 218
Compatibility
Minecraft: Java Edition
1.21–1.21.1
1.20.x
1.19.x
1.18.x
1.17.x
1.16.x
Platforms
Paper
Purpur
Spigot
Changes
For complete history, Click Here.
- API Updates
- Updated Konquest API Java version to 21 for Jitpack API repository, so that the API artifacts build successfully.
- Updated Spigot API to version 1.21.1.
- Added support for Minecraft 1.21.1.
- Updated compatibility between Minecraft versions.
- Bug Fixes
- The Health town upgrade now correctly applies and removes health bar hearts in newer Minecraft versions.
- When EssentialsX integration is enabled, barbarian players can now set homes in their own camps.
- Kingdom payments are now correctly calculated for all online players.
- New Features
- Added experimental option
enable_advanced_tnt_protectionfor tracking which players own TNT explosions, with added protections in towns based on owner relationships. For example, players cannot launch TNT into towns they are allied with. - Added option
no_protected_attackingto prevent players in kingdoms that are offline-protected from attacking other kingdoms with more online members. - Added option
settle_increment_kingdomto make the cost to settle new towns based on all towns within the kingdom, instead of the towns which the player is the lord. - Added option
upgrade_while_attackedto allow whether players can purchase upgrades while a town is under attack. - Changed the Town Watch upgrade to have a warmup time, specified by option
no_enemy_edit_offline_warmup, after a resident quits the server. - Added option
enable_afk_paymentsto allow whether or not players can receive kingdom payments while marked as AFK by Essentials.
- Added experimental option
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:uM8CLEbn:HV8kE7YQ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:uM8CLEbn:HV8kE7YQ"
}

