Links
Tags
Creators
Details
Licensed CC-BY-NC-ND-4.0
Published 4 months ago
Updated 4 months ago
All versions
1.1.0
Release
Elytra+ 1.1.04 months ago 24
Uploaded by
Compatibility
Minecraft: Java Edition
26.1.x
Platform
Fabric
Supported environments
Client-side
Client and server
Required content
Unavailable version
Any compatible version
Changes
ElytraPlus 1.1.0
A new powered-cruise autopilot, plus a batch of fixes for the dedicated slot and trails.
New
- Powered cruise autopilot. Fly-to (the Go button) and auto-level now use a smooth rocket-powered cruise: climb up to your cruise height, then hold it by pitching up, spending one rocket, gliding back down, and repeating — instead of trickling up at a shallow angle.
- Climb angle slider. Set how steeply the autopilot climbs to cruise height — from a gentle ascent all the way to straight up. Found under Assisted auto-level and on the Flight Locations screen.
- Rockets are only spent to keep your climb above ~10 m/s, so the ascent no longer burns a firework every second.
Fixes
- Ribbon trails now show in first person. Your own swept-ribbon trail was only visible in third person; it now renders in first person too (the segments right at your wings are trimmed so they don't smear across the screen).
- Creative mode: the dedicated slot works again. In creative, an elytra placed in the dedicated slot wasn't registering on the server, so gliding would start and instantly drop. It now glides correctly. (Survival was unaffected.)
- No more dropping your elytra. Clicking the elytra in its slot threw it on the floor instead of picking it up — because the slot sits just outside the inventory panel. You can now click and drag it normally.
- New empty-slot icon. The dedicated slot now shows a subtle elytra outline when empty, instead of the chestplate silhouette.
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:hTRiDzaC:CfSal1da"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:hTRiDzaC:CfSal1da"
}

