Tags
Creators
Details
0.4.0
Compatibility
Required content
Changes
0.4.0
Note: this version adds a lot of new logic. I have tested as many combinations as I could, but some edge cases may still have slipped through. The core cargo and route systems are tested, but I have not yet fully tested every storage mod listed below in live gameplay. Some of those integrations are currently based on the capability hooks now being in place, so please let me know if you find any issues.
New Features
- Added explicit linked item and fluid cargo ownership on both ships and stations.
- Added item and fluid threshold waits.
- Added item and fluid full/empty waits.
- Added ship-versus-station cargo target selection for cargo-state waits.
- Added supported-target cargo link mode with multi-pick add, source re-right-click finish/cancel flow, and linked-cargo world preview.
- Added grouped stop-condition runtime with
ANDinside groups andORbetween groups. - Added
Redstone Linkwaits. - Added
Time of Daywaits. - Added initial linked cargo compatibility hooks for:
- Chests / Trapped Chests
- Barrels
- Shulker Boxes
- Create Item Vaults
- Create Fluid Tanks
- Storage Drawers blocks and Drawer Controller networks
- Functional Storage drawers and controller-linked storage
- Sophisticated Storage blocks and controller-linked storage
- Placed Sophisticated Backpacks
- Iron Chests
- Mekanism storage blocks and supported multiblock tank storage
- Tom's Storage connector/interface/proxy endpoints
- Refined Storage 2 grids, storage monitors, interfaces, exporters, and importers
- Applied Energistics 2 ME interfaces, ME chests, and cable-bus import/export parts
Enhancements
- Destination-side docking runtime now resolves against the actively running ship/controller instead of station-selected ship context.
- Dock waits, dock redstone output, and stable held docking state now reuse the correct transponder dock link at destination stations.
- Route playback now hands off directly into the next scheduled leg after a completed docking wait instead of briefly dropping control first.
- Active schedules can now be opened during playback in a read-only
Stopsview. - Missing-dock messaging now makes it clear the failure may be on either the ship or station side.
- Dead route legs and stale schedule entries are now cleaned up automatically when supporting stations or ships are deleted.
- Stale active route playback is now reconciled against the transponder’s current schedule every tick and on runtime restore.
- One-way schedules that reach their final stop now reset the transponder runtime back to
Ready/ idle cleanly instead of leaving the UI stranded in an activeWaiting/Runningstate with the play control still locked out. - Breaking an Airship Station or Ship Transponder can now require crouch-confirm mining, with an action-bar warning before related route data is removed.
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:BngGFM0a"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:73ZXeRfx:BngGFM0a"
}



