Tags
Creators
Details
Licensed MIT
Published last year
Updated 2 months ago
All versions
0.2.2
Release
Create: Propulsion 0.2.29 months ago 1,046
Compatibility
Minecraft: Java Edition
1.20.1–1.20.6
Platform
Forge
Supported environments
Client and server
Required content
Changes
Create 6.0.7 support
- Create: Propulsion now works with Create 6.
- Propulsion now provides masses for all Create blocks, including those added in C6! (Before masses were provided by clockwork).
Wings
- Added iron & tempered iron wings. They have identical lift and drag values as clockwork ones for your convenience :P
- Added copycat wing. Copycat wing has variable width (which can be increased by Shift + RMB it). Wings of different widths have different masses and aerodynamic parameters.
Please note that unlike clockwork wings, propulsion ones do not have any angle of attack. So behavior-wise they are an alternative to clockwork flaps.
QOL
- Reworked Assembly Gauge selection behavior to allow selection of both target block and face-relative block. Added interpolation.
- Lodestone Tracker now keeps compass at the same orientation it was inserted in.
- Unfinished lens (the one you get by not finishing optical lens creation process) now halves the range of optical sensor it is inserted into. Added this because I really needed inline optical sensor based bombs to explode at right distance.
- Updated numerous language files.
Fixes
- Fixed Thruster initialization logic. I have no idea why loading world with running thrusters worked before this fix.
- Fixed Thruster model having incorrect AO.
- Fixed Lodestone Tracker crashing the game when inserted compass returns null positions.
- Even more redstone magnet model fixes.
- Fixed propulsion not loading up with some version of CBC.
- And a lot more smaller fixes!
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:fmudhH0S:ztkTeBAZ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:fmudhH0S:ztkTeBAZ"
}





