All versions
1.0.0
Release
Drone Logistics 1.0.02 months ago 35
Compatibility
Minecraft: Java Edition
1.21.4
Platform
NeoForge
Supported environments
Client and server
Required content
Changes
[1.0.0]
Multi-drone support
- A terminal can now bind up to 4 drones with the linking tool.
- When 2 or more drones are bound, a drone panel appears on the right side of the terminal screen.
- Single-click a drone in the panel to choose which drone handles the next delivery.
- Double-click a drone to rename it directly in the terminal. Drone names are saved with the terminal.
- Dispatch picks the selected drone first, or any free drone if the selected one is busy.
- Opening a terminal with no bound drone shows a "Bind a drone first" screen instead of the terminal list.
Parallel deliveries and live tracking
- Ordering no longer takes over the whole terminal. The terminal list stays fully usable while deliveries are in flight.
- You can dispatch a second free drone while the first one is still delivering. When every drone is busy, opening a warehouse reports that no drone is available.
- The left side of the terminal screen now shows a stacked mini-map card for every drone currently flying for this terminal.
- Each card shows the drone name, a mini-map with the terminal, the warehouse and the live drone position, plus a direction and ETA readout ("To warehouse" while heading out, "Returning" while carrying cargo).
- Orders now remember which drone is carrying them, persisted to disk.
Delivery flight and economy
- Drone speed now depends on cargo. A drone flies fast when empty on the way out and slower on the way back, scaled by how many stacks it carries.
- Added a cooldown after a delivery before a drone becomes available again.
Terminal interaction
- Renaming a terminal is now done directly on that terminal instead of through another one.
- Taking half a stack from the delivery buffer is now done with a middle-click instead of the scroll wheel.
Rendering and map
- New terminal block model with two textures: an idle texture and an "On" texture shown while the terminal screen is open.
- Map icons replace the plain colored squares on the delivery tracking screen.
- Added a persistent Xaero-style minimap: explored chunks stay visible permanently.
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:hwzc2DVP:VKVrPyOY"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:hwzc2DVP:VKVrPyOY"
}


