Tags
Creators
Details
All versions
1.0.5
Release
Keybind 1.0.5yesterday 7
Compatibility
Minecraft: Java Edition
26.3
26.2
26.1.x
1.21.x
1.20.x
1.19.x
Platforms
Bukkit
Folia
Paper
Purpur
Spigot
Changes
Quilt (New)
- Native Quilt builds: Dedicated
quilt/modules for Minecraft 1.21 and 26.x — no Fabric API required. - Vanilla custom-payload transport via codec registration mixins, packet listener mixins, and
minecraft:registerchannel announcement for Paper/ViaVersion compatibility.
Fixes & Reliability
- MC 26.3 Crash: Resolved
NoSuchFieldErroronInputConstants.Type.KEYSYM(renamed toKEYBOARDin 26.3) with a reflective cross-version resolver shared by all loaders. - NeoForge/Forge Hello Retry: Hello packet is now only marked sent after a successful send; failures are logged and retried instead of silently swallowed.
- Duplicate Sync Message: Repeat sync packets (early-join resend) no longer spam the
[Keybind] Syncedchat — it only shows on first sync or when actions change. - Sync Delivery: Server resends sync ~1 second after hello (Folia-safe scheduler) to cover early-join packet loss; sync is only sent to clients that announced the mod.
- Controls Category Order: The Keybind Actions category now appears at the top of Settings → Controls on all loaders and versions.
Plugin
- Folia Support: Sync scheduling works on both Paper and Folia via a reflective scheduler compatibility layer.
- Compatibility Gating: Plugin messages are only sent to players who sent the keybind hello — vanilla clients receive nothing.
- Diagnostics: Hello receipt and sync sends are logged for troubleshooting.
- bStats: Corrected metrics ID to the registered
Keybindsproject (34789).
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:yuttqmXl:pmjzJNCi"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:yuttqmXl:pmjzJNCi"
}

