1.0.15
Compatibility
Changes
This update focuses on improving flight stability, multiplayer reliability, and long-term server safety.
Fixed a singleplayer pause issue where resuming the game could launch the player forward with excessive stored momentum. Fixed a short delay where flight state could remain active briefly after wings were removed. Improved flight anti-cheat behavior to reduce bypasses using intermittent abnormal movement. Fixed underwater flight speed checks being skipped entirely when underwater flight is allowed. Fixed inaccurate command feedback counts. Commands now report the number of players actually affected. Improved client/server code separation to reduce compatibility risks on dedicated servers. Improved wing command input. Wing names can now be entered directly without always typing the full namespace. Cleaned up unused code and clarified a few internal names.
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:KkyXV6R9:ngYtUtQC"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:KkyXV6R9:ngYtUtQC"
}

