1.0.0
Compatibility
Changes
š¦ Elycher
The Ultimate Seamless Elytra Launcher for Survival Minecraft
Tired of awkward high-ground jumps or wasting gunpowder on rockets? Elycher brings cinematic, Iron Man-style takeoffs directly to vanilla Survival.
š Why Elycher?
Most flight plugins either break the survival economy or require a master's degree in configuring yml files. Elycher is built differently. It's a lightweight, drag-and-drop, zero-config utility that feels like it belongs in the vanilla game. No commands, no permissions, no databases-just pure, optimized gameplay.
⨠Features
- š Zero Configuration: Literally plug-and-play. Drop the
.jarinto yourplugins/folder and restart. Done. - š¬ Cinematic Launch: Double-jump while wearing an Elytra to shoot into the air with heavy rocket audio, a custom cloud particle trail, and an automatic wing-pop at the apex.
- āļø Survival Balanced: Built strictly for Survival Mode. Players must touch solid ground before launching again, completely preventing mid-air infinite flight abuse.
- ā” Highly Optimized: Written with raw performance in mind. Uses smart movement caching to ensure zero TPS drops, even on potato servers.
š„ Installation & Usage
- Download the latest
Elycher.jar. - Drop it into your server's
/pluginsdirectory. - Restart your server.
- In-Game: Ensure you are in Survival Mode, equip an Elytra in your chestplate slot, and press
Spacetwice to launch!
š Note on Anti-Cheats
Since Elycher modifies player velocity to launch them, strict anti-cheats (like Vulcan or Grim) might falsely flag the movement. If players experience rubber-banding, ensure you whitelist Elytra boost mechanics in your anti-cheat config.
š Beta Testing & Support
Elycher is currently in Active Beta. Found a bug? Have a feature request? Don't leave a bad review-come yell at us directly in the Discord!
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:SRHDbZY6:AmNK5Z5i"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:SRHDbZY6:AmNK5Z5i"
}

