Tags
Creators
Details
Licensed GPL-3.0-only
Published 3 years ago
Updated 10 months ago
All versions
1.7.0
Release
Konquest 1.7.02 years ago 192
Compatibility
Minecraft: Java Edition
1.21–1.21.4
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.
- Minecraft Version
- Added support for Minecraft versions up to 1.21.4.
- Bug Fixes
- Reduced iron golem search radius for enemy players in towns, which is no longer dependent on the max town size setting.
- Fixed town protection logic to only broadcast warmup messages when a town starts its warmup timer, not every time a player leaves the server.
- Updated compatibility check for enchantments to exclude those from custom data packs.
- Fixed kingdom stat to correctly decrease when players disband a kingdom.
- Changed camp bed placement conditions to allow multiple beds to be placed within a camp, where breaking any bed will destroy the camp.
- Updated ChestShop integration to display error messages when an invalid ChestShop plugin is loaded.
- New Features
- Added placeholders for Ruins: cooldown time, capture status, number of criticals, and number of spawns.
- Added integration support for QuickShop-Hikari, replacing the integration for QuickShop.
- Added core options to make barbarian players peaceful, controlling whether they can attack kingdoms, camps, or pvp.
- Added ability to swap kingdom capitals with other towns, after an optional warmup and for an optional cost in currency.
- Improved DiscordSRV integration
- Added auto roles feature for automatically managing and assigning roles for each kingdom in the Discord server.
- Updated Konquest events to work better with DiscordSRV Alerts system.
- Konquest API
- Added more events for kingdom actions and improved existing event documentation.
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:TbsKfHik"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:uM8CLEbn:TbsKfHik"
}

