Tags
Creators
Details
Licensed ARR
Published 3 months ago
Updated 13 hours ago
All versions
0.8.3
Release
Create: Flight Control 0.8.313 hours ago 893
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Any compatible version
Changes
0.8.3 Change Log Flight & Navigation
- Added fixed-wing target following, including circling while waiting for slow or stopped targets.
- Added smoother waypoint turns and improved takeoff, orbiting, approach and landing.
- Improved mouse-flight handling, braking and recovery after brief control interruptions.
Aircraft & Equipment
- Added arresting cables and tailhooks for carrier-style landings, with adjustable braking and redstone controls.
- Added decorative flap control to creative FCCs, including physical Compact Flap bearings.
- Added trapezoid and clipped-corner wing editing, plus updated thruster models and animations.
Controls & Interfaces
- Redesigned velocity coupler screens with directional layouts, presets and live readings.
- Added wireless frequency settings and key/axis mappings for Drive-By-Wire, Tweaked Controllers and Create Fire Control.
- Separated mouse flight control from free look.
- Added /gamerule createfcRequiresStress false to make controller stress requirements optional.
Compatibility
- Expanded support for Synaxis welding and added Pocket/Pym integration for welded and scaled structures.
- Added Gadgets & Gizmos RCS thruster support.
Fixes & Improvements
- Fixed thruster control with Create Propulsion Simulated.
- Fixed redstone proxy control of thrusters mounted on swivel bearings.
- Fixed Tool Gun area-selection linking for Gadgets & Gizmos thrusters.
- Fixed duplicate controller stress usage after network reloads or power-source changes.
- Improved welded-structure handling, engine/flap linking and AFN reload recovery.
- Fixed HUD, wing, thruster flame, cable and tailhook rendering issues.
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:IGVrnkhH:FSr0O2k8"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:IGVrnkhH:FSr0O2k8"
}

