Tags
Creators
Details
3.5.0+mc26.2
Compatibility
Required content
Changes
Controlify 3.5.0
This version has the following targets:
- 26.1
- 26.2
By donating on my Patreon, you will gain access to builds of Controlify for splitscreen support and snapshot versions
Changes
Contextual API
Button guides and DualSense adaptive trigger effects are now powered by a shared contextual system. Contextual domains collect facts and values from the game, derive additional facts from them, and evaluate ordered rules to decide which guide labels or trigger effects to use. This gives Controlify more precise built-in behaviour while providing one extensible system for both mods and resource packs.
- Add built-in in-game and container domains covering player movement, vehicles, targeted blocks and entities, held and active items, and inventory state
- Expand button guides with more specific actions such as trading, riding, opening, crafting, blocking, consuming, shooting, placing, and fishing
- Allow resource packs to define reusable facts and guide or trigger-effect rules under
assets/<namespace>/contextual/ - Support combining facts with
all_of,any_of, andnone_of, as well as matching item, block, and entity slots using Minecraft's standard predicates - Allow mods to contribute state to the built-in domains, register custom domains, and create their own button-guide or trigger-effect instances
- Replace the old guide and adaptive-trigger APIs and resource formats with the contextual API and
contextualresource paths
Other changes
- Update SDL to 3.4.14 and refresh the bundled controller mappings
- Fix Controlify clients incorrectly enabling analogue movement merely because a server completed the Controlify handshake
- Allow analogue movement on Realms without requiring an IP whitelist entry
- Fix the DualSense mute light remaining on after the controller is closed or Minecraft exits
- Launch the redesigned VitePress documentation site with expanded controller, resource-pack, and developer documentation
- Update community translations
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:9ePC9FQ4"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:DOUdJVEm:9ePC9FQ4"
}

