Tags
Creators
Details
Licensed ARR
Published last month
Updated 1 hour ago
All versions
0.6.1
Beta
Create: Flight Control 0.6.1last month 472
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
Fixes:
- Fixed phantom stress and lost connections when placing sublevel with Sable Photomacy.
- Fixed blocks not being returned to the player’s inventory when picked up with a wrench.
- Fixed optical sensor connections on substructures.
- Fixed packet synchronization for Engineer’s Goggle displays on Attitude and 5. Altitude Hold controllers.
- Fixed thrust allocation for clustered Propulsion thrusters.
Added:
- Adjacent fuel and electric thrusters can now redistribute excess fuel and energy.
- Aerodynamic Trail Creators can now be toggled via redstone.
- Engines on rotating-bearing substructures can now be connected to a Flight Control Redstone Proxy through the bearing.
- Linear and Angular Velocity Couplers can now use separate maximum speeds for positive and negative directions.
- Controllers now provide three PD tuning presets.
- Aeronautics Optical Sensors gain a detection range of 128 blocks when connected to a Distance Coupler.
- Added the Forward Indicator, which can supply aircraft nose direction to compatible controllers.
- Added Mouse Flight Control, with support for Shoulder Surfing perspectives and seats connected to Fire Control.
- Added support for the new Propulsion engines.
- Added flap control with support for multiple camouflaged flap variants, Analog Compact Flap Bearings, and Create Mechanical Bearings.
- Controllers can now be rotated with a wrench.
- Flight Control Computers and Creative Flight Control Computers can now have their master switches controlled through a Flight Control Redstone Proxy.
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:cNJQOC16"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:IGVrnkhH:cNJQOC16"
}

