1.0.0
Compatibility
Required content
Changes
Elytra Slot
Wear your elytra and your chestplate at the same time.
Ever wished you could keep your Netherite Chestplate on while still enjoying elytra flight? Elytra Slot adds a dedicated equipment slot for your elytra, right next to your armor slots, so you no longer have to choose between defense and mobility.
Features
- Dedicated elytra slot, appearing next to your chestplate slot in both the survival inventory and the Creative inventory tab
- Wear armor and elytra simultaneously, no more compromise between protection and flight
- Hover-to-reveal design: the slot stays hidden until you hover over the chestplate area, keeping your inventory clean and uncluttered
- Full vanilla-like interactions:
- Shift-click an elytra from your inventory to send it straight to the slot
- Right-click an elytra in your hotbar to equip it instantly
- Take it out normally with a regular click
- Persistent: your elytra stays safely in its slot across game sessions
- Custom slot icon, matching the style of vanilla equipment slots
- Fully functional flight: durability, gliding physics, and skin rendering all work exactly as if the elytra were worn normally
- Works seamlessly in the Creative inventory tab too
Installation
- Install Fabric Loader for Minecraft 26.2
- Download and install Fabric API (required dependency)
- Download the latest Elytra Slot .jar and drop it into your mods folder
- Launch the game and enjoy the skies without compromise
Requirements
- Minecraft 26.2
- Fabric Loader
- Fabric API
Found a bug?
This is a solo-developed passion project. Feedback and bug reports are always welcome, feel free to leave a comment.
License
MIT
Made with curiosity, a lot of debugging, and zero prior Java experience.
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:mlbhj1OD:WBvDokEz"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:mlbhj1OD:WBvDokEz"
}

