Tags
Creators
Details
Licensed LGPL-3.0-or-later
Published 4 years ago
Updated 3 weeks ago
All versions
1.7.0-beta.3+1.20.2
Beta
Controlify 1.7.0-beta.3+1.20.23 years ago 2,936
Compatibility
Minecraft: Java Edition
1.20.2
Platform
Fabric
Supported environments
Client-side
Client and server
Required content
Any compatible version
Any compatible version
Any compatible version
Changes
Controlify 1.7.0 (Beta 3) for 1.20.2
New Features
- Added D-Pad snapping in container screens
- Keyboard-like movement whitelist and warning toast when joining new servers
- Added bind to open F3 debug screen
- More snap points on recipe book
- Allow users to define a custom SDL natives path (so you can put them in a common dir if you want)
- Add a reset all binds button to controls tab
Changes
- Internal changes to the way controllers are discovered, loaded and managed. (this could introduce new bugs)
delegate_setupconfig option has been renamed toquiet_mode.- Pause screen's disconnect shortcut now focuses the button instead of clicking it.
- Add a donate button to the controller carousel screen.
- Modify how analogue inputs are processed whilst ingame or using the virtual mouse to make it feel more "circular"
- Marginally improve performance of Controlify by using optimized hashmaps.
Bug Fixes
- Fix hotplugging when using natives.
- Fix SDL download screen progress bar being a missing texture.
- Fix people being unable to write newlines and spaces in signs when using mixed input mode.
- Fix some modded GUIs crashing when attempting to open when Controlify is loaded.
- Fix tridents not causing a vibration.
- Fix rumble not working on joysticks.
- Fix fabric mod json requirement allowing any 1.20 version not 1.20.2 and above.
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:DOUdJVEm:5MMK5oJQ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:DOUdJVEm:5MMK5oJQ"
}

