Tags
Creators
Details
1.8.0
Compatibility
Required content
Changes
First published build for Minecraft 26.3 on Fabric.
This is the same mod as 1.8.0, ported forward to 26.3. Behaviour is unchanged: the pie menu, the list menu, the priority system, K-key priority capture, live conflict re-scanning, per-category filters, and the in-game config screen all work the same way.
Porting notes
Minecraft 26.3 moved the client from GLFW to SDL3, so the port covers:
- The capture key and key handling now use
InputConstants.Type.KEYBOARDinstead of the removedKEYSYM - Unbound keys are detected by their negative key value rather than by scanning GLFW state
- Rendering moved to the 26.3
RenderPipelineAPI in thecom.mojang.renderpearlpackage; the pie menu is drawn through the GPU-batched ring renderer - The
org.lwjgl.glfwclasses no longer exist, so GLFW references were replaced with the SDL3 equivalents
Requirements
- Minecraft 26.3
- Fabric Loader 0.19.3 or newer
- Fabric API 0.161.0+26.3 or newer
- Java 25 or newer
- Cloth Config 26.3.159 or newer
- ModMenu 21.0.0 or newer (optional, only for the settings screen)
Known limitations
- The pie menu has no keyboard navigation, which is the largest accessibility gap
- Neighbouring wedge labels can overlap when action names are long; they are clamped so they are never cut off by the screen edge, but they cannot reflow
- The pie menu does not pause the game, intentionally
- Colour inputs are hex text fields rather than RGB pickers, because the Cloth Config release in use provides no picker widget
- Bindings changed by another mod at runtime are not detected; only the listed refresh triggers cause a rescan
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| keybindsgalore-1.8.0+26.3-sources.jar | Sources jar | 80.21 KiB |
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:l6y7RMn7:zCLq83OM"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:l6y7RMn7:zCLq83OM"
}

