Tags
Creators
Details
Licensed GPL-3.0-only
Published 11 months ago
Updated 6 months ago
All versions
3.0.0
Beta
Immersive Aircraft: Better Engines 3.0.06 months ago 546
Uploaded by
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Required content
Unavailable version
Unavailable version
Unavailable version
Changes
Changelog:
- Engines:
- Added a starring system, inspired by hypixel skyblock! Every engine can be upgraded up to 10 stars, the first 5 are normal the last 5 are "master" stars. The stars need glowstone dust, ender eyes and diamonds to be made! Each star increases fuel usage and power usage by 5%.
- **Upgrades: **
- Gold propeller - upgrade to the enhanced propeller
- Power gyroscope - gyroscope that also buffs the engine
- Reinforced pipes - upgrade to the industrial pipes
- Perfect landing gear - upgrade to the improved landing gear
- Fuel:
- added dense fuel, which is just made from 9 compressed fuels, and is what its name says it is
- New Planes!
- Sport Biplane: a sport version of the biplane, faster, with better handling and more upgrade slots, but with no weapon slot, significantly higher fuel usage and less storage space
- Commercial Hopper: a commercialised version of the bamboo hopper. Has seats for up to 17(or 16, I dont remember) players and storage space split into 4. It is also slightly faster. However, it does use more fuel and there is only 1 weapon slot.
- Rebalancing! Huge changes!
- supercharger and turbo rebalanced to both be useful
- Added new items for recipes including steel and plates.
- Rebalanced most upgrade recipes, including vanilla immersive aircraft upgrades and upgrades from this addon, to be harder to make and have a more complex recipe. Weapons and vehicles(except for biplane) have been left untouched.
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:kNsl999k:krkB24Gq"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:kNsl999k:krkB24Gq"
}

