Tags
Creators
Details
0.7.0
Compatibility
Required content
Changes
Create Aeronautics: Automated Logistics 0.7
Version 0.7 expands the information available from Airship Stations, with live Display Link output and broader map support. It also adds new Cargo Link integrations for several popular Create addons. Underneath those visible additions are extensive reliability improvements for autonomous docking, cargo waits, queues, and recovery after world reloads.
Safer cargo waits and docking
- Cargo conditions now include items and fluids staged inside linked Docking Connectors. Ships no longer depart merely because the main linked storage emptied before the transfer crossed the dock.
- New cargo conditions default to requiring a stable result for two seconds, reducing apparent false completions caused by brief transfer gaps.
- Improved hand-off of items already buffered in a connector before the physical dock finishes locking.
- Removing a linked Docking Connector now clears the stale dock link and station redstone output instead of leaving the automation in a misleading state.
- Dock queues now continue to treat stopped, paused, or faulted ships inside the protected dock area as occupying the dock.
- Physical dock occupancy survives world reloads and temporary vehicle-restoration gaps.
- Broken docking connections are now restored automatically after reloading a world, allowing item and fluid transfer to resume.
- Restarting a stopped ship retains departure clearance until that ship has physically left the dock area, preventing the next queued ship from approaching too early.
- Improved recovery when a connector is removed and rebuilt while a vehicle is docked or restoring.
Airship Station displays
Airship Stations can now provide live information to Create Display Links.
- The station-wide view shows live inbound and outbound vehicle counts, including queued arrivals, alongside vehicles at the station, current dock state, and queue length.
- Dock state distinguishes between free, approaching, occupied, and departing states.
- Boards can be filtered to one known vehicle to show its location or journey, next station, and a labelled status such as travelling, arriving, departing, docked, or queued.
- The vehicle picker suggests vehicles with routes connected to that station and respects normal ownership, permission, and FTB Teams access rules.
- When Jade is installed, station tooltips show the station name and Ship Transponder tooltips show the ship name.
Expanded map support
- Added automated vehicle markers to Xaero's Minimap and Xaero's World Map.
- Added separate client toggles for the FTB Chunks, JourneyMap, and Xaero map integrations.
- Added a shared map-marker size setting. Marker labels scale gently with their icons to remain readable.
- Improved the Logistics Terminal's tabletop map with steadier line widths, less glare, clearer route colours, and vehicle icons rendered above routes and station markers.
More Cargo Link targets
Cargo Links now additionally support:
- Create: Connected Item Silos, including their vertical multiblock sizes.
- Create: Iron Vaults storage variants.
- Propulsion: Simulated Platinum Tanks.
Missing linked cargo blocks are now removed from saved links automatically when their loaded position no longer contains supported storage.
Recorded-route animation polish
- Added Mechanical Bearing animation during automated playback, allowing attached sails and other bearing contraptions to visibly rotate along a recorded route.
- Retuned the existing automated Small Propeller and Propeller Bearing animations: large propeller types now run faster while small propellers use a calmer speed.
- Propellers and bearings now ramp up and down smoothly when a vehicle starts, stops, or waits instead of snapping instantly between motion and rest.
- These animations are visual only and do not add propulsion or alter the vehicle's machinery.
- Updated the optional Simurail bogey animation bridge for both the previous and current bogey APIs.
Mod compatibility
The 0.7 development build was tested on Minecraft 1.21.1 and NeoForge 21.1.229 with the following required stack:
- Create 6.0.10
- Create Aeronautics 1.3.0
- Create: Simulated 1.3.0
- Sable 2.0.6
New and updated integrations in 0.7 were tested with:
- Create: Connected 1.3.3
- Create: Iron Vaults 1.2.0
- Create Propulsion: Simulated 1.1.5
- Jade 15.10.6
- Simurail 0.1.0
- Xaero's Minimap 26.6.0 and Xaero's World Map 1.47.0
Other supported optional integrations include:
- Applied Energistics 2 19.2.18
- FTB Chunks 2101.1.22 and FTB Teams 2101.1.11
- Functional Storage 1.5.7
- Iron Chests 16.0.7
- JourneyMap 6.0.9
- Mekanism 10.7.19
- Refined Storage 2.0.9
- Sophisticated Backpacks 3.26.12 and Sophisticated Storage 1.6.6
- Storage Drawers 13.11.4
- Tom's Simple Storage 2.4.2
What's next: Redstone Drive
Substantial foundations for the future Redstone Drive system were developed during 0.7, including Drive Modules, calibration, route guidance, and real redstone control of player-built propulsion. The public Advanced Transponder and Drive Module items are deliberately unavailable in 0.7 while the feature receives further design work and testing.
Normal recorded-route playback remains the supported automation mode in this release.
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:73ZXeRfx:ESwTkggq"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:73ZXeRfx:ESwTkggq"
}

