All versions
2.0.0
Release
Keybind Atlas 2.0.06 days ago 2,555
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client-side
Changes
Included multiple suggestions from user feedback, including:
- Edit mode overhaul: Improved flow of editing keybinds, making it faster and more intuitive. Added per-binding restore controls, strikethrough and color-coded feedback for removed/reassigned keys, and a better summary of changes before applying.
- Added search bar for main UI, filter list, and edit mode. Filter by mod or action.
- Keybind sets feature: The user can now save and load keybind sets, allowing them to switch between different configurations easily. Users can save the current keybinds as a new set, delete or rename existing sets, and create new sets that are copies of the current keybinds. The sets are saved in a JSON file in the config folder.
- Added "Layout & Routing" editor under Settings to adjust box sizing, spacing, and connector preferences.
- Game now pauses in single-player when the overlay is open. Not applicable in multiplayer or LAN worlds.
- Added text truncation toggle to limit max keybind text length in unhovered info boxes. Full text is still shown on hover (Toggleable and with custom max length).
- Added command to open the overlay:
/keybindatlas - Renamed a few settings for clarity.
- Reworked some elements to be more visually aligned, such as icons pixel art, animations and buttons.
- Animations no longer replay for every keybind change.
- Animations now only play once when flipping between main and extra keys.
- Positioned key modifier (ex. shift, ctrl) to the left of key action.
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:fokFjwwh:zT1hSwL5"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:fokFjwwh:zT1hSwL5"
}

