Tags
Creators
Details
1.16.20
Compatibility
Changes
Note: Due to some changes in turret system, this build is a little unstable and turrets might not function properly.
Since a large percentage of people continue to use 1.20.1 for some reasons, 1.20.1 is now supported once again.
Fixed a rare error caused by "/k redo/undo" commands.
Fixed an issue with /k admin migrate database when migrating between two SQL databases.
Added some restriction to "/k admin openFile" to prevent possible security issues.
Fixed YAML database issues.
Fixed an issue where some config commands are dispatched async.
Removed unnecessary precision from location placeholders.
Significant turret performance improvements.
Fixed Peace Treaties & Outposts addons.
KingdomInvadeEndEvent can now be cancelled.
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:Iva4aI3A:By4q8tg0"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Iva4aI3A:By4q8tg0"
}

