Tags
Creators
Details
1.1.1
Compatibility
Changes
🚀 DeliveryDrones Update — Storage GUI, Animal Modes & Improvements
This update brings highly requested quality-of-life features, flexible configuration options for server administrators, and crucial bug fixes for custom skull textures and localization.
Here is everything new in this release!
✨ New Features
📦 Storage Preview & Preparation GUI
- Safe Loading: Added a dedicated GUI that allows players to place items into the drone for storage or preparation and close the interface safely without automatically launching the drone. This makes managing large shipments much easier and safer!
⚙️ Advanced Behavior Configuration
I have expanded the configuration file with powerful new settings to customize your server's drone mechanics:
- Animal Return Mode (
animal-return-mode): You can now define how drones behave when an animal delivery is aborted (due to a player being offline, cancellation, or declination).FLY: The drone realistically flies back to its original send point.TELEPORT: The drone instantly teleports back to the send point.
- Direct Inventory Sending (
open-inventory-on-send): Added the ability to completely bypass the standard compose-hub GUI.- When set to
true, interacting with a drone opens its package inventory directly, and closing the interface automatically dispatches the drone.
- When set to
🛠️ Fixes & Tweaks
- Full GUI Customization: Resolved an issue where several parts of the user interface were hardcoded. All remaining elements have been properly moved to
gui.yml, allowing for 100% full translation and customization! - Custom Skull Support: Fixed and stabilized the Base64 texture support for custom player skulls within the
gui.ymlconfiguration. Custom heads will now load reliably without skin-fetching delays.
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:4VBq9J3l:f5Negpjc"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:4VBq9J3l:f5Negpjc"
}

