Tags
Creators
Details
Licensed ARR
Published 5 months ago
Updated 2 days ago
All versions
0.1.16
Release
Create Aeronautics: Thrusters and Things 0.1.16 - HOTFIX 23 months ago 6,919
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
Changelog
0.1.16 - HOTFIX 2 - 2026-06-09
- Fixed various issues with the Physics Gantry where nested sub-levels would glitch and behave unexpectedly
- Unified Entity Launcher anchor rope handoff so ropes fired while riding a placed anchor use the same anchor-owned rope behavior, kinetic reeling, and persistence as ropes transferred from the handheld launcher.
- Entity Launchers can now place an empty launcher anchor by sneak-right-clicking a block, and pick block on a placed launcher anchor now selects the Entity Launcher item.
- Fixed
simulated:directional_gearshiftsupport with CC:Tweaked so it now correctly dispatches rotational kinetics to adjacent blocks when controlled via ComputerCraft API's. - Added full
Create: Connectedsupport to the CC:Tweaked peripherals list. - added full
Create: Connectedsupport to theContraption Controllerto allow wireless control overCreate: Connectedkinetic blocks. - Added a new
Shipping Manifestblock. When placed on an item or fluid container, it lists stored items and fluids, including fluid fill graphs and thruster fuel details. - Shipping Manifests attached to Create Diesel Generators distillation tanks can now be wrenched into a combined manifest that lists fluids from every level of the tower.
- Fixed server side feature gating so dedicated server is not the source of truth for features, server side disabled blocks and items no longer show in the creative menu or EMI
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:OOfSF6ZZ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Sza3GgEL:OOfSF6ZZ"
}

