All versions
1.0.1
Release
Zephyr Hauler 1.0.12 months ago 30
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
Zephyr Hauler 1.0.1 - QoL fixes
This update focuses on quality of life (QoL) improvements, stability, and fixing edge-case bugs to make the logistic experience flawless before introducing new mechanics.
Quality of Life & UI Improvements:
- Dynamic Tooltips: The Zephyr Hauler tooltip now hides the upgrades list by default to prevent screen clutter. Hold ALT to view all installed upgrades.
- Safe Item Recovery: Shift + Right Click to retrieve a Hauler or abort a launch will now attempt to place the balloon directly into your inventory. If your inventory is full, they will drop safely on the ground.
- Wind Meter Upgrade: The Wind Vane now scans your Y level and warns you if the altitude provides optimal or weak wind currents.
- Dynamic Maintenance: Preventive maintenance at the Maintenance Station now uses a progressive loot pool. A Netherite Hauler will require a much wider variety of materials (13 possible items) than a basic one.
- Controller Feedback: The Zephyr Controller screen now features floating, centered feedback messages that turn red (Error) or yellow (Success).
Bug Fixes & Stability:
- Total Flight Invulnerability: Haulers are now completely invulnerable to all damage types (including projectiles) while in transit.
- Landing Zone Validation: The Hauler now scans the 3x3 area above the destination dock before launching. If the destination is blocked by blocks, the launch is safely aborted.
- Controller Reset Fix: Using the "Reset" button on the Zephyr Controller now correctly clears the target coordinates of the Hauler item currently in the slot.
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:jl3CCuI3"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:SI4rHRlM:jl3CCuI3"
}

