Tags
Creators
Details
Licensed LGPL-3.0-or-later
Published 3 years ago
All versions
3.0.0-beta.3
Beta
3.0.0-beta.3 for neoforge 1.21.15 months ago 34.5K
Compatibility
Minecraft: Java Edition
1.21–1.21.1
Platform
NeoForge
Supported environments
Client-side
Client and server
Required content
Changes
Controlify 3.0.0-beta.3
This version has the following targets:
- StonecutterProject(project=1.21.11-fabric, version=1.21.11)
- StonecutterProject(project=1.21.11-neoforge, version=1.21.11)
- StonecutterProject(project=1.21.10-fabric, version=1.21.10)
- StonecutterProject(project=1.21.10-neoforge, version=1.21.10)
- StonecutterProject(project=1.21.8-fabric, version=1.21.8)
- StonecutterProject(project=1.21.8-neoforge, version=1.21.8)
- StonecutterProject(project=1.21.5-fabric, version=1.21.5)
- StonecutterProject(project=1.21.5-neoforge, version=1.21.5)
- StonecutterProject(project=1.21.4-fabric, version=1.21.4)
- StonecutterProject(project=1.21.4-neoforge, version=1.21.4)
- StonecutterProject(project=1.21.3-fabric, version=1.21.3)
- StonecutterProject(project=1.21.3-neoforge, version=1.21.3)
- StonecutterProject(project=1.21.1-fabric, version=1.21.1)
- StonecutterProject(project=1.21.1-neoforge, version=1.21.1)
By donating on my Patreon, you will gain access to builds of Controlify for splitscreen support and snapshot versions
Changes
- Fix crash when attempting to edit the radial menu
- Add some error checking surrounding DefaultConfigManager to debug an ongoing bug
- Stop periodically saving when using gyro auto-calibration
- Fix stale boundInputs in InputBindings for controllers sharing the same settings
- Make vmouse CURSOR_ONLY truly cursor only, and add a new CURSOR_SCROLL mode to replace the original functionality
- Allow registration and rendering of custom guide domains
- Update translations
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:mOESpLJa"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:DOUdJVEm:mOESpLJa"
}


