Tags
Creators
Details
1.12.1
Compatibility
Required content
Changes
Separate Fabric builds for Minecraft 1.21.10, 1.21.11, 26.1, 26.1.1, 26.1.2, 26.2 and 26.3. Choose the JAR matching your exact game version.
- A click that lands just before its key goes with that key. With two hands, the click of a key-and-click pair sometimes lands a few milliseconds first. Vanilla forgives that inside a tick; 1.12.0 ran that click with the item of the step before: a second glowstone instead of the detonation, and the loop one click late. Now a click pressed up to 30 ms before a hotbar key goes with that key when it is the only one waiting and the item in hand has already had its click, or cannot be used at all (an empty hand, a sword, a mace, a totem). A first click with an item keeps the order you pressed.
- The core has no switches. Split bursts, Offhand sync, Hold guard and Ignore key repeat are always on. Strict attacks, Mouse-like keys and One click per tick are gone, and attacks run as in Vanilla.
- Combat items too is off in a fresh install: swords and the other combat items keep Vanilla's equip animation, which shows the attack cooldown starting again. A saved setting is kept.
- Four tabs: Order, Feel, Monitor and KoHs. The Monitor counts the clicks that went with their key, and the first time it sees a slot change after a click it writes in the log which mod sent it.
- Measured against Grim Anticheat 2.3.74 with its experimental checks on, with
a player's own keys and kit: no alerts, and no tick Vanilla could not send.
The audit is in
docs/audits/AUDIT-1.12.1-slips-and-core.md.
Your saved order and Feel switches are kept when you update.
Requires Fabric Loader 0.19.3+. Minecraft 1.21.x uses Java 21; Minecraft 26.x uses Java 25. Install Fabric API for localized mod text and Mod Menu to reach the settings button. Client-side only.
Optional dependencies
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:5yMyq4qM:niQducSh"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:5yMyq4qM:niQducSh"
}

