Tags
Creators
Details
1.0.0
Compatibility
Required content
Changes

🚀 SpawnElytra v1.0.0 - Fabric Edition
🎯 Major Features
- 🎮 Full Fabric support for Minecraft 1.20.1 - 1.21.10
- 🔑 LuckPerms integration with smart defaults
- 📊 Update checker via Modrinth API
- ⚙️ Cloth Config for easy in-game configuration
✨ What's New
Fabric Platform
SpawnElytra is now available for Fabric servers:
- Native Fabric API integration
- Efficient mixin-based event handling
- TOML configuration via Cloth Config
- Automatic update notifications
Permission System
- Optional LuckPerms integration
- Smart defaults: all players can fly and boost by default
- Fine-grained control with
spawnelytra.use,spawnelytra.useboost, andspawnelytra.admin - Works perfectly without LuckPerms installed
Performance & Safety
- Thread-safe async operations with CompletableFuture
- Tick-based delay system (no blocking)
- Instant elytra activation on double-jump
- World-specific flight boundaries
🔧 Technical Details
- Fabric Loader 0.15.0+ required
- Fabric API (version-specific)
- Cloth Config 11.0.0+
- Java 21+
- Optional: LuckPerms API 5.4
📥 Installation
- Install Fabric API and Cloth Config
- Download
spawnelytra-1.0.0.jarand place it in yourmodsfolder - Configure in
config/spawnelytra.toml
🌟 Why Fabric?
- ✅ Lightweight and efficient server-side mod
- ✅ Compatible with Minecraft 1.20.1 through 1.21.10
- ✅ Easy configuration with Cloth Config
- ✅ Optional LuckPerms support with sensible defaults
- ✅ Automatic update notifications
🙏 Credits
Fabric Port: @SchlangeGoto - Initial Fabric implementation
Original Concept: CoolePizza - Original SpawnElytra
Also available for Paper/Bukkit servers - check the versions tab!
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:P8b9AbbA"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:NAFqBu99:P8b9AbbA"
}

