Tags
Creators
Details
2.3.0
Compatibility
Required content
Changes
Controlify 2.3.0
This version has the following targets:
- 1.21.9-fabric:1.21.9
- 1.21.8-fabric:1.21.8
- 1.21.8-neoforge:1.21.8
- 1.21.5-fabric:1.21.5
- 1.21.5-neoforge:1.21.5
- 1.21.4-fabric:1.21.4
- 1.21.4-neoforge:1.21.4
- 1.21.3-fabric:1.21.3
- 1.21.3-neoforge:1.21.3
- 1.21.1-fabric:1.21.1
- 1.21.1-neoforge:1.21.1
By donating on my Patreon, you will gain access to builds of Controlify for splitscreen support and snapshot versions
Data-driven button guides
Controlify's button guide system (found in-game and in container screens) has been completely rewritten to be data-driven. This means that resource packs can now add or overwrite button guides.
If you would like to make a resource pack to add or change button guides, consider reading the newly written documentation on the Controlify wiki.
Although this feature has not been highly requested, people have expressed discontent with the current set of button guides. Although the guides present in 2.3.0 are the same as before, this new system allows for players to make their own guides, or mod developers to add guides for their mods.
Other changes
- New
LEDComponentfor controllers, to allow mods to control the LED on controllers that support it. - Rewrote the dualsense trigger effect API, to allow mods to use the DualSense's adaptive triggers more easily.
Bug fixes
- Fixed the crash on startup for some users, with the log
Argument value 0x200000001 exceeds native capacity - Fix Switch 1 Joy-Cons having incorrect button glyphs (by rinOfTheStars)
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:DOUdJVEm:YwQzAbP8"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:DOUdJVEm:YwQzAbP8"
}

