Links
Tags
Creators
Details
Licensed MIT
Published 5 months ago
Updated 36 minutes ago
All versions
1.3.0+26.3
Release
Keybindery 1.3.0+26.3last week 494
Compatibility
Minecraft: Java Edition
26.3
Platform
Fabric
Supported environments
Client-side
Client and server
Required content
Any compatible version
Any compatible version
Changes
Nothing changes in the Key Binds menu in this release. The additions are for other mods, and players see them through those mods, like the key on each sandbox in Sandboxes 2.1.0.
Added
- Keybindery has its own icon in Mod Menu.
- For mod developers, runtime key bindings.
KeybinderyAPI.getInstance().bindings()registers key bindings while the game runs, one for each thing the player makes, like a sandbox.register(id, label, chord, onPress)adds or replaces one, andunregister(id)removes it. A binding fires on the same presses as vanilla's key mappings, follows the player's chord mode, and runs on the client thread. Runtime bindings don't show in the Key Binds menu and aren't saved, so the mod stores the chord withChord.serialize()and registers it again at startup.conflicts(chord, id)lists every key mapping and other runtime binding that shares a key with it. - For mod developers, a chord button for any screen.
captureWidget(x, y, w, h, chord, onChange)returns a vanilla button that captures a chord and passes it toonChange. Escape, Delete, or a right-click clears it. - Without Keybindery installed, runtime bindings do nothing,
conflictsreturns an empty list, andcaptureWidgetreturnsnull.
Changed
- Requires MenuKit 7.2.0 or newer, below 8.0.0.
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:Ufxx9AC2:sXvJwSzU"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Ufxx9AC2:sXvJwSzU"
}

