1.1.0
Compatibility
Changes
The Logistics & Automation Update
What's New in v1.1.0
- Zephyr Hub: Added a new master routing block. Instead of linking haulers to individual docks, players can now link to a Hub. The Hub dynamically scans the network and automatically assigns the first available dock to incoming haulers.
- Zephyr Cable: Added networking cables to connect Docks to a Zephyr Hub. A single Hub can scan and manage up to 256 connected blocks.
- Hub Monitor UI: Shift + Right-Clicking a Zephyr Hub with an empty hand now opens a paginated Monitor Screen, displaying real-time coordinates and statuses of all connected docks.
- Zephyr Auto-Station: Added an automated version of the Maintenance Station. It can store repair materials and autonomously repair damaged haulers that land on it. Includes a toggle to enable/disable auto-repairs.
- Zephyr Launcher: Added redstone-triggered automation block. When placed next to a docked hauler and powered, it automatically fuels and launches the balloon.
- Wind Sensor: Added a redstone meteorology block. When linked to a destination, it outputs a redstone signal proportional to how favorable the wind currents are for that specific route.
Changed
-
Controller GUI Overhaul: The Zephyr Controller screen now features a dual-tab navigation system (Docks and Hubs).
-
Live Telemetry & 4-State System: The network now actively tracks 4 precise states for Docks and Hubs, visually represented in the UIs:
- 🟢 Free: Empty and ready to receive.
- 🟡 Reserved: A hauler has been dispatched here; locked for others.
- 🔴 Occupied: A hauler is physically anchored.
- ⚪ Inaccessible: Airspace blocked, chunk missing, or dock destroyed.
- "Smart Memory" Link (Return Sender): Haulers launched from a Hub will temporarily overwrite their destination to the assigned dock, but will safely store the OriginalHubPos in their NBT. When picked up, they automatically restore their link to the Hub, preventing players from having to manually re-link them.
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:SI4rHRlM:CYUdH8CF"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:SI4rHRlM:CYUdH8CF"
}

