1.5.0
Compatibility
Changes
Anti StickyK 1.5.0
Now Open Source under the MIT License! Render thread stutter fixes, session self-healing, and loader cleanup.
This update focuses on performance, open-source licensing, crash resilience, and multi-version compatibility.
Fixed
- Eliminated render thread micro-stutters by moving session file I/O, OS locking, and
fsyncoperations to a dedicated background worker thread (StickyKeys-IO-Worker) - Fixed startup crashes on Forge and NeoForge environments by removing invalid loader metadata (
mods.toml/neoforge.mods.toml) that lacked Forge@Modentrypoints - Fixed modern Minecraft (1.14+) window focus detection in
WindowFocusby inspecting the client'sWindowinstance (class_1041) rather than missing direct methods onMinecraftClient - Prevented premature hotkey disabling during early mod initialization before the game window is created or focused
- Removed unused and redundant boilerplate forwarders in
AntiStickyK
Reliability
- Added self-healing session recovery: corrupted, zero-byte, or incompatible
session.statefiles are safely intercepted and reset rather than permanently breaking the mod - Refactored session file channel locking using standard
try-with-resourcesto prevent file descriptor leaks during sudden process termination - Ensured background tasks are cleanly awaited upon client close (
close()) to guarantee accessibility settings are restored before the JVM shuts down - Preserved graceful fallback for non-Windows operating systems (macOS / Linux)
Licensing & Metadata
- Replaced "All Rights Reserved" with the official MIT License (Copyright (c) 2026 eternql2938)
- Added dedicated root
LICENSEand updatedLICENSE_sticky-keys-disable - Updated mod version to 1.5.0 in
fabric.mod.json
Verification
- Successfully compiled all classes targeting Java 17 with zero warnings or errors
- Verified archive structure with
META-INF/MANIFEST.MFplaced first in the jar - Verified that Fabric metadata, mixin mappings, icon assets, and bundled libraries are intact in both the mod jar and the source archive
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:HdIbBmek:zf7u9ZXe"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:HdIbBmek:zf7u9ZXe"
}

