Links
Tags
Creators
Details
1.5.0
Compatibility
Required content
Changes
CC-Aeroworks 1.5.0
Important dependency notice
CC-Aeroworks 1.5.0 requires TeutonLib 1.5.0 on both the client and server.
TeutonLib is not yet available on Modrinth. Download the official release manually from GitHub:
Highlights
- Moved the reusable computer workspace, peripheral lifecycle, channel groups, wire signals, hosted computers and Sable geometry into TeutonLib.
- Added persistent UUID-based Control Desk assemblies with improved placement, separation and multiblock handling.
- Integrated Create Contraption Controls and native Train Controls into connected desk rows.
- Added embedded computers and peripherals to moving Create contraptions.
- Split programmable displays into normal and advanced small/large variants.
- Added persistent display colour configuration.
- Advanced displays support programmable touch input when an advanced computer is installed.
- Create: Radars can now be selected as an optional source for advanced displays.
- Wireless modems and GPS information sources now use visible-world coordinates on moving Sable sublevels.
- Existing computer IDs, files, channel UUIDs, group bindings and public Lua APIs remain compatible.
Required versions
- Minecraft
1.21.1 - NeoForge
21.1.234or newer - Create
6.0.10 - Create: Aeroworks
1.5.x - Create: Aeronautics
1.3.2 - Sable
2.0.1or newer (2.0.5tested) - CC:Tweaked
1.119.xor1.120.x(1.120.2tested) - Kotlin for Forge
5.11.xor newer, below6.0 - TeutonLib
1.5.x
Optional integrations
- Create: Simulated
1.3.x - Drive-By-Wire With Sable
0.2.9–0.3.x(0.3.0tested) - Create: Radars
0.4.9.4or newer
Upgrade notes
The former display item IDs are migrated through registry aliases.
The old dedicated cc_aeroworks:train_controls item and module were removed in favour of Create's native Train Controls. Existing stacks of that specific removed item are not migrated automatically.
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:YJqoniYI:EEgCpJyz"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:YJqoniYI:EEgCpJyz"
}

