Tags
Creators
Details
1.8.0
Compatibility
Required content
Changes
NeoForge port. This is the same mod as the Fabric 1.8.0 build, ported to NeoForge for Minecraft 26.2. 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.
Requirements
- Minecraft 26.2
- NeoForge 26.2.0.88 or newer
- Java 25+
- Cloth Config 26.2.155+
No Fabric Loader, no Fabric API, and no ModMenu. The config screen is contributed through NeoForge's own settings extension point and appears in the Mods list.
What changed from the Fabric build
Only the loader-facing surface. The conflict engine, configuration model, and both selector screens are untouched, because nearly all of the mod is plain Minecraft or plain Java.
- The mod entrypoint is now a NeoForge
@Modclient class - Key registration uses
RegisterKeyMappingsEvent - Tick and connection events use the NeoForge equivalents
- The config directory uses
FMLPaths.CONFIGDIR - The ModMenu settings entrypoint became a
ModContainerextension point - Configuration loading moved to the first client tick, since
Minecraft.optionsis still null during NeoForge mod construction - The deprecated
logoFilemetadata key is nowiconFile, clearing the startup warning - The mod now reports its version correctly in-game
Known issue
One harmless deprecation warning appears at startup. It comes from Cloth Config 26.2.155 itself, is already fixed in Cloth Config 26.3.159, and will disappear when Cloth ships a 26.2 patch. Nothing in this mod causes it.
The limitations of the Fabric 1.8.0 build still apply, notably: no keyboard navigation in the pie menu, overlapping labels for long action names, and no detection of bindings another mod changes at runtime.
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| keybindsgalore-1.8.0+26.2-neoforge-sources.jar | Sources jar | 79.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:OmOcyOGS"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:l6y7RMn7:OmOcyOGS"
}

