Tags
Creators
Details
Licensed ARR
Published 5 months ago
Updated 4 days ago
All versions
1.1.2
Release
Create Aeronautics: Gadgets & Gizmos 1.1.22 months ago 174
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
Changelog
2026-07-22 Version 1.1.2
IMPORTANT: If updating from V 1.0.6 or earlier existing linkers inside controllers may be deleted, back up your world and remove any linkers currently installed in contraption controllers before updating.
Fixes and Updates
- Fixed recursive cleanup logic that was incorrectly running every 20 ticks and causing lag, hangs, and in some cases crashes. Replaced with explicit
/gizmos remove_disabled_items <range/player>op command to remove items from the world after toggling them off in the config. Advanced Contraption Controller:Set Datanode now correctly lists allOutputtagged blocks in it's target list.Direct Controlnode now only exposes correct usable inputs for the target block.Latchnodes now correctly latch their outputs.
Analogue Contraption Controller:- Fixed an issue that caused
Bearingblocks to not show theirCW/CCWdirections and bindable outputs.
- Fixed an issue that caused
QoL changes
Advanced Contraption Controller:- Added
Sticky Notes. - Added session based clipboard to allow copying node groups from one controller to another.
- Added graph state memory to return the graph to it's last pan and zoom after re-opening.
- Added
Notes and Extras
- Cleanup command can take no parameters in order to do a full cleanup of the whole world. Run once after disabling blocks and items.
Toolguncompat has not been fully tested and may experience bug with some schematics.Scissor PistonandScissor Armtextures and block models are work in progress and subject to change.
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:Sza3GgEL:wkfIHdYX"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Sza3GgEL:wkfIHdYX"
}

