Tags
Creators
Details
3.3.0+mc26.2
Compatibility
Required content
Changes
Controlify 3.3.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
Adaptive Trigger Effects
Controlify now has built-in support for DualSense Adaptive Trigger effects.
This is a never-seen-before feature for Minecraft, on any edition.
The current built-in effects are:
- Bow pull back
- Weapon attack (any item with weapon component)
- Crossbow pull back (any item with charged_projectiles component)
- Crossbow shoot (any item with charged_projectiles component)
- Eating (any item with consumable component)
- Shields (any item with blocks_attacks component)
- Equipping items (any item with equippable component)
- Spears (any item with kinetic_weapon component)
- Goat horns (any item with instrument component)
All of these effects are completely data-driven and can be modified just with a resource pack. This extends to server-provided resource packs. Target data components, item tags, vanilla item predicates, and item IDs.
Check out the wiki for instructions on creating resource packs.
GUI Scale for Button Guides
The GUI scale option for the Ingame and Screen button guides have returned! Rather than a % scale slider, you can now choose a vanilla GUI scale number, defaulting to one minus the default.
Bug Fixes
- Fix Mixed Input leaving the virtual mouse unresponsive for 2 seconds (thank you Ifbusta)
- Fix Xbox Controllers not being detected when wired on Windows
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:MJ0IIPqj"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:DOUdJVEm:MJ0IIPqj"
}



