Tags
Creators
Details
2.4.0
Compatibility
Changes

🚀 SpawnElytra v2.4.0 - Critical Fixes & Compatibility Update
🎯 Major Fixes
- 🔧 Multi-plugin compatibility - No more conflicts with FlyCraft and similar plugins
- 🛡️ Exploit prevention - Double-jump spam and nether portal exploits fixed
- 🎮 Enhanced Bedrock protection - Death drops, inventory clicks, and cleanup
✨ What's New
Breaking Fixes
Critical fixes that improve server stability:
- FlyCraft Compatibility: Managed players tracking prevents flight permission conflicts
- Double-Jump Spam Fix: Players can no longer spam jump to gain altitude while flying
- Gliding State Detection: Checks
isGliding()to prevent flight re-enabling during active glide - Multi-Plugin Support: Plugin now tracks which players it controls, preventing interference
Enhanced Bedrock Protection
Bedrock players get better experience:
- Death drop prevention (virtual elytra no longer drops)
- Inventory click protection (cannot remove elytra while flying)
- Join cleanup system (removes leftover elytra from crashes)
- Proper chestplate restoration in all scenarios
Bug Fixes
- Nether Portal Exploit Fixed: Flight immediately stops when changing worlds
- World Change Cleanup: Managed players properly cleared on world transitions
- Ground Detection: Improved detection for various block types
- State Management: Consistent player state across all scenarios
🔧 Technical Details
managedPlayerslist for plugin-controlled player tracking- Enhanced event handlers:
InventoryClickEvent,PlayerDeathEvent - Automated dev environment with Paper 1.21.11 support
- Java 21 LTS compatibility optimizations
- State validation with
flying.contains()andisGliding()checks
📥 Installation
Download SpawnElytra-2.4.0.jar and place it in your plugins folder.
🔄 Upgrading
Existing configurations from v2.3.x work perfectly. No configuration changes required.
⚠️ Important for Multi-Plugin Servers
If you run flight plugins like FlyCraft alongside SpawnElytra, this update is critical for proper functionality.
🌟 Why This Update?
- ✅ Fixes critical multi-plugin conflicts
- ✅ Prevents exploitation of flight mechanics
- ✅ Better Bedrock player protection
- ✅ Production-tested stability improvements
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:NAFqBu99:Zdx2U0Jy"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:NAFqBu99:Zdx2U0Jy"
}

