Tags
Creators
Details
2.1.0-beta.1+mc1.20.x
Compatibility
Required content
Changes
This is a minor update to FlightAssistant. There are no breaking changes in this release.
Minecraft version limitations
Some features are only available on certain versions of Minecraft:
1.20.4, 1.20.3: All features are available
1.20.2: Cannot load flight plans created in version 2.0.0
1.20, 1.20.1: Cannot load flight plans created in version 2.0.0, elytra state protections are not available (Open Elytra automatically and Close Elytra automatically when submerged)
Additions
- Flight plans will now be saved and loaded as JSON instead of NBT
- This allows the mod to run on Minecraft versions older than 1.20.3
- Flight plans created in version 2.0.0 can be loaded in Minecraft versions 1.20.3 or higher, where they can be re-saved as JSON and loaded anywhere
- Added the
UNLOADED CHUNKalert and protection- If the chunk where the player is currently located hasn't loaded in ~3 seconds, a warning will appear on the alert display
- The radar altitude display will be hidden while in an unloaded chunk
- Additionally, the player's pitch will automatically be corrected to preserve altitude and reduce ground speed
Changes
- Reduced the Minecraft version requirement to 1.20.0-1.20.4
- Allowed
LANDmode to engage earlier- GPWS and flight mode display will be able to provide more relevant alerts during approach as a result of this change
- Options not available in the Config Screen will now appaer switched off
- Reduced the speed at which Autopilot will try to reach a selected target altitude
- Errors during flight plan loading will provide more useful information
- Changed the message that appears when Auto-Firework is armed but no target speed/altitude is set
Fixes
- Fixed an issue that caused the Autopilot to lose altitude on approach
Optional dependencies
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:CWqLEOPt:hHel3A1h"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:CWqLEOPt:hHel3A1h"
}




