Tags
Creators
Details
Licensed LGPL-3.0-only
Created 4 years ago
Updated 5 days ago
All versions
2.9.1a-1.21.1
Release
Kingdom Keys 2.9.1a3 months ago 47
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Changes
Added:
- Shotlock followup minigames, they are enabled by default (serverconfig for it), if they work and scale fine we'll remove the config later.
- Mini helm cockpit, 1x1x1 and can hold a single rider.
- New button to add Savepoints as favourite.
- Support for JER is back.
- New serverconfig to set individual magic cooldowns (Similar to BBS).
- New serverconfig to set the cooldown multiplier compared to the global cooldown (only if individual magic cooldown is set to true, defaults to x4).
- New clientconfig to set the portrait render as 2D or 3D.
- Airstep and shotlock trails.
Changed:
- Org portal block visuals similar to Savepoint.
- You can no longer shotlock while controlling an entity.
- You can no longer move while casting a shotlock.
- You are sent upwards when casting a Ragnarok-like shotlock.
- Bag-held shotlocks color in the selector gui are now cyan, same as the bag item color.
- Updated Japanese translation (thanks to roxchan6668).
Fixed:
- Gummi Hangar screen crash.
- Savepoint screenshots being stretched.
- Savepoint model outline has been removed.
- Particles when running over a savepoint showing up as missing.
- Bio barrage not being a circular shotlock.
- Flame Salvo not being a volley shotlock.
- Crown not being rendered in the 2D Player Portrait.
- /kingdomkeys dimension command throwing errors in chat.
- Idle animation playing while walking in EFM.
- EFM attack happening when starting a shotlock.
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| kingdomkeys-1.21.1-2.9.1a-sources.jar | Unknown | 62.91 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:rNcKGGJK"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:DrsqKwVw:rNcKGGJK"
}
