Tags
Creators
Details
1.17.8-BETA
Compatibility
Changes
Bug Fixes
⚠️ Warning ⚠️
This is an unstable build. Use with caution in a production server. [Learn more]
Beta Phase
The plugin has moved from Alpha ➡️ Beta phase. What does this mean for you? It means that the plugin will no longer receive updates that may break the data structure, meaning that you can use the plugin without fearing data/config resets for future updates. However, beware that data corruptions caused by converting your v1.16 data to v1.17 can still happen, and you should take a backup before upgrading.
From here on out, you the people determine when the plugin moves from Beta ➡️ Release as more servers need to start using the plugin in order to catch bugs in production environments.
- For people using any of the previous alpha versions, you need to reset your data for this update.
- For people upgrading from any version, you should reset all your configs for this update.
- Added support for Geyser's Floodgate dot-prefixed names.
- Added a template GUI for turret GUIs for easier configuration.
- Fixed
/k flyspeed issues. - Fixed
/k claim fillerror. - Fixed an issue with MythicMob intregation.
- Fixed an error caused by purchasing turrets/structures.
- Allies can no longer break your nexus or change your nexus settings (like ranks or upgrades)
- Fixed negative numbers for some inputs.
- Fixed
/k admin debugcommands. - Fixed an issue with
v1.16 -> v1.17data migration. - Fixed a few issues with
/k admin relationshipcommand. - Buildings now use the standard options used for determining their construction duration. (they used a fixed value before)
- You can now purchase structures/turrets regardless of your kingdom level in admin mode.
- Fixed server crashes caused by placing structures.
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:PNfIpMko"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Iva4aI3A:PNfIpMko"
}

