Tags
Creators
Details
Licensed GPL-3.0-only
Published 3 years ago
Updated 10 months ago
All versions
1.2.0
Release
Konquest 1.2.03 years ago 78
Compatibility
Minecraft: Java Edition
1.20–1.20.2
1.19.x
1.18.x
1.17.x
1.16.x
Platforms
Paper
Purpur
Spigot
Changes
- Bug Fixes
- Fixed town protections of entities like paintings, item frames, and armor stands so that non-resident players cannot break them.
- Language files now correctly get saved with a
.badextension when they have invalid YAML syntax. Any config file with invalid syntax will be saved with a.badextension, and the default version of the file will be used. - Improved player kingdom membership checks when SQL database connection is corrupt or unavailable. Players will no longer be marked as a Barbarian while being members of kingdoms/towns.
- Minor Features
- Added ARENA property for Ruins and Sanctuaries. Also added konquest-arena flag for WorldGuard regions. This allows any player to pvp in the territory/region, regardless of kingdom relationship.
- Added sub-command "/k admin ruin reset (name)", which will reset the ruin by re-generating all critical blocks, and re-spawning all Ruin Golems.
- Added core.yml option loot_after_capture, which will only spawn loot in chests after the ruin has been captured.
- Added sub-commands for joining and leaving kingdoms and towns, which do the same thing as the existing GUI menu methods.
- Command "/k kingdom join (name)" lets the player request to join a kingdom.
- Command "/k kingdom exile" lets the player leave their kingdom to become a barbarian.
- Command "/k town (name) join" lets the player request to join a town.
- Command "/k town (name) leave" lets the player leave the specified town to stop being a resident.
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:fbMrx4oO"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:uM8CLEbn:fbMrx4oO"
}

