Tags
Creators
Details
Licensed LGPL-3.0-only
Created 4 years ago
Updated last month
All versions
2.9.3e-1.21.1
Release
Kingdom Keys 2.9.3elast month 438
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Changes
Added:
- Consumables bag for potions and other recovery items.
Changed:
- Update notifier is now a button that can take you to the mod download page.
- Growth abilities coming from Drive Forms no longer require leveling said form in order to work.
- This change does not affect mod progression due to the need of leveling them in order to earn the growth ability but it might help for servers giving them in different ways.
- Glide animation now won't move its arms and legs.
Fixed:
- Lilostitched incompatibility where villages were made out of Moogle houses exclusively.
- Station of Awakening being very dark when using Sodium.
- Savepoint top buttons not rendering when using Immediately Fast.
- Hangar will now return the combustible remainder (for example a bucket when using a lava bucket).
- Savepoint tooltip numbers.
- Tooltip not visible for current savepoint.
- Shop item description not being properly aligned.
- (Hopefully) the bug where org portals could occasionally teleport all players in a radius on servers.
- (Hopefully) party crash under weird names like color codes.
- Translated banned blocks in hangar chat message.
- Translated savepoint tooltip attributes.
- Translated area button from Hangar screen.
- Some warnings when loading the mod.
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| kingdomkeys-1.21.1-2.9.3e-sources.jar | Unknown | 71.88 MiB |
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:DrsqKwVw:AB92PAeX"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:DrsqKwVw:AB92PAeX"
}
