Tags
Creators
Details
All versions
1.0.4
Release
Keybind 1.0.4last week 106
Compatibility
Minecraft: Java Edition
26.3
26.2
26.1.x
1.21.x
1.20.x
1.19.x
1.18.x
Platforms
Bukkit
Paper
Purpur
Spigot
Changes
Fixes & Reliability
- Controls Menu Duplication: Resolved issue where keybinds appeared twice in Settings → Controls → Key Binds and were duplicated in
options.txt. Replaced redundant static registration with name-based deduplication and in-place mapping updates inKeybindManager. - Automatic Settings Deduplication: Client options mappings are automatically scanned and pruned of duplicate entries on initialization.
- Forge Event Listener Cleanup: Removed redundant
RegisterKeyMappingsEventregistration in Forge 26 to rely on unified dynamic injection without duplicates. - Chat Formatting & Encoding: Replaced legacy
\u00a7formatting codes in chat sync and key capture overlay messages with nativeChatFormattingtext components, preventingA a[Keybind]Mojibake on Windows systems. - Forge 26.1 Runtime Bootstrap: Resolved launcher issue on Forge 26.1 where vanilla unpatched jar was selected instead of patched client binaries.
NeoForge (Released)
- NeoForge 1.21.11: Official support added targeting NeoForge 21.11.48 (Minecraft 1.21.11).
- NeoForge 26.1 / 26.2: Full support for Minecraft 26.x with custom Category sorting, payload networking, and client tick handling.
- NeoForge 1.21: Stable build targeting NeoForge 21.0.167.
Plugin
- Chest GUI Fallback: Added interactive 54-slot Chest GUI with pagination and click sounds for servers without Paper Dialog API.
- Update Checker: Automatic GitHub release check that notifies administrators when joining.
- Metrics: Anonymous telemetry via bStats.
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:wxcbxrMu"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:yuttqmXl:wxcbxrMu"
}

