Tags
Creators
Details
All versions
3.9.0+1.20.1
Release
Minecraft Cursor for Fabric v3.9.0+1.20.1last year 536
Compatibility
Minecraft: Java Edition
1.20.1
Platforms
Fabric
Quilt
Supported environments
Client-side
Required content
Changes
- Increased maximum texture size to 128x128 in steps of 8. Minimum size remains 8x8.
Recommended texture size is 2n with custom scale or 16x16 with auto-scale enabled. - Changed element detection logic (again). Inactive vanilla widgets are now detected.
- Registered disabled vanilla buttons and sliders with the Not Allowed cursor. Can be disabled. (#31)
- Overhauled the Cursor Settings screen.
- Added sidebar with sections: Global, Adaptive Cursor, Cursors, Mod Compatibility, and Debug.
- Added search functionality.
- Adaptive Cursor: Added option to toggle Not Allowed cursor on disabled widgets.
- Cursors: Added Reset to Defaults option.
- Mod Compatibility: Added option to aggressively update the cursor.
- Removed More Cursor Options screen (consolidated to Cursor Settings screen)
- Improved performance of
random_cycleanimation mode. - Fixed cursor not being destroyed when switching to resource packs with an invalid cursor image.
- Fixed the cursor reverting to Default when holding right shift on inventory items if the Shift cursor was disabled.
For Fabric versions:
- Fixed custom cursors from other mods not being detected unless a standard cursor was also created.
- Fixed cursor reload (via resource reload or changing cursor settings) bypassing the custom cursor check.
The expected behavior is that the Adaptive Cursor is disabled when a custom cursor is present to improve compatibility with mods that use custom cursors like FancyMenu.
Optional dependencies
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| minecraft-cursor-fabric-3.9.0+1.20.1-sources.jar | Unknown | 128.31 KiB |
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:o5fhgLeQ:ApMEzrnv"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:o5fhgLeQ:ApMEzrnv"
}


