All versions
1.6+26.2
Release
KeyCPS 1.6 for 26.2last month 13
Compatibility
Minecraft: Java Edition
26.2
Platforms
Fabric
Quilt
Supported environments
Client-side
Required content
Any compatible version
Changes
New
- In-game settings screen — press Right Shift (rebindable), or open it from Mod Menu.
- Mod Menu integration (optional — KeyCPS still works without it).
- Minecraft 26.1, 26.1.1, 26.1.2, 26.2 and 26.3 support.
- Key repeat counting on every version: holding a keyboard-bound attack/use key counts the OS key-repeat rate (aaaaaaa…). 1.21.11 was missing this before.
- Optional rate on every key — see how often W/A/S/D fire per second, repeats included.
- Optional sneak / sprint row.
- CPS warning: the counter turns red at a threshold you choose.
- Keys show what they're actually bound to (AZERTY → Z Q S D, attack on F → "F", …).
- New keybinds: Open Settings, Toggle HUD, Move HUD.
- One-time tip in chat on first join telling you how to open the settings.
- Translations: English, German, French, Spanish, Portuguese (BR), Italian, Dutch, Polish, Turkish, Russian, Ukrainian, Chinese (Simplified), Japanese, Korean.
Better looking
- Rounded keys, smooth press/release fade, CPS shown inside the mouse buttons, the jump key drawn as a space bar, text shadow, optional rainbow text. Scaling now scales the text too.
- The HUD starts in the top-left corner on first launch.
- Move screen: drag the HUD anywhere; it snaps to the edges and the centre.
Fixed
- Very fast clicks (shorter than one frame) were sometimes missed — clicks are now counted from input events, not sampled once per frame.
- Typing in chat no longer bumps the counters when attack/use are on keyboard keys.
- Each jar now only loads on the Minecraft version it was built for.
Optional dependencies
Any compatible version
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:qjIgtNcw:MHpgruqD"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:qjIgtNcw:MHpgruqD"
}

