Tags
Creators
Details
1.0.7
Compatibility
Changes
π Drone Update: Version 1.0.7
This update gives your delivery drones a makeover, ensures smoother flight paths, and cleans up the "under the hood" mechanics for better performance (about 4% less cpu usage).
π¨ Custom Drone Appearance
You are no longer stuck with the default player-head look. You now have full control over the drone's design:
- Custom Models: Use your own items from Nexo, Oraxen, or ItemsAdder as the drone model.
- Toggleable Glow: You can now easily turn the drone's glowing outline on or off in the
config.yml. - Classic Look: If you don't use custom model plugins, the drone will still use the classic player-head texture by default.
βοΈ Improved Flight (No more lagging!)
I have overhauled the flight logic to make deliveries feel more natural and less taxing on your server:
- Smart Pathing: The drone now calculates its route once at the start. It only recalculates if the target moves, which saves a lot of CPU power.
- Smooth Gliding: Instead of "bouncing" through the air, the drone now glides smoothly from point A to point B. This fixes the "jittery" movement seen on some game clients.
- Stable Visuals: The droneβs internal stand is now rock-solid during flight to prevent any visual flickering.
π οΈ Upgrade Guide
After updating, please check your config.yml. The following new settings are available:
- Provider: Tell the plugin which system provides your model (
NONE,NEXO,ORAXEN, orITEMSADDER). - Item-ID: Enter the ID of your custom item here.
- Glow: Set
glowing-enabledtotrueorfalse.
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:Jh6nK0GQ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:4VBq9J3l:Jh6nK0GQ"
}

