Tags
Creators
Details
Licensed ARR
Published 5 months ago
Updated 3 days ago
All versions
1.2.6
Release
Create Aeronautics: Gadgets & Gizmos 1.2.64 days ago 3,028
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
Gadgets & Gizmos 1.2.6 patch notes
- Fixed a bug when breaking belt wheels that prevented the belt item from dropping.
- Replaced custom support mannequin models with vanilla Fake Player models.
- Added
Advanced Contraption Controllerrenaming to recover graphs from accidentally destroyed controllers. - Belt wheels can now have multiple connections (Up to 8).
- The
Powered Ziplinecan now jump acrossRope Connectorblocks whenRope Connectorsare adjacent and have attached rope. - The
Powered Ziplinecan now be used onChain Conveyors. Advanced Contraption Controller:- New
Desmos: Plot Pointnode for plotting changes over time on the function plotter. - Nodes can now be moved using
Arrow Keys. - Better controls in the
Set Datanode when targeting:Smart GearboxServo Bearing
- Cleaned up the
SCM: Navigatenode input ports to be less ambiguous. - Fixed a bug in the
SCM: Hovernode that locked out yaw controls.
- New
- Fixed the peripheral timings in
CC:Tweakedwhen controllingThrustersandRCS Thrustersto allow sub-tick commands. - Updated the
Thrusterperipheral API so it's internal tank can be targeted like other tanks in CC:Tweaked for refueling over network cables. - Fixed a bug that caused some recipes to not show when using EMI.
- Updated the
Advanced Navigation Tableto auto start as soon as a valid item is present. - Added nodes to the
Advanced Contraption Controllerto plot data over timeWhen pulsedto theFunction Plotterwith optional export options forCSVandJSON. Thrusterblocks now emit light based on output.- Added
Creative RCS Thruster.
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:PXctFUSv"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Sza3GgEL:PXctFUSv"
}

