Links
Tags
Creators
Details
Licensed MPL-2.0
Published 4 months ago
Updated 3 weeks ago
All versions
1.1.14
Release
PeterWolf’s Planes 1.1.143 months ago 505
Compatibility
Minecraft: Java Edition
26.2
Platform
Fabric
Supported environments
Client and server
Changes
1.1.14
- Rebuild the water plane as a single high-wing floatplane with short fuselage-mounted wing supports.
- Complete the opaque water-plane entity atlas so the fuselage, floats, and enlarged UV faces no longer render with transparent gaps.
- Keep the parked water plane level on its two full-length floats instead of applying the conventional tail-low two-wheel ground pose.
- Stop treating water contact as locked ground handling, restoring mouse-driven elevator and aileron authority while the floatplane accelerates and lifts off the water.
- Add deterministic ClientGameTest coverage for the parked high-wing silhouette and real mouse-driven pitch/roll response.
- Treat the water surface as float support while retaining live mouse controls, preventing stall pitch from tipping the aircraft onto its nose after landing and braking.
- Cut a full-chord cockpit opening into the high wing so its center section no longer blocks the first-person pilot view.
- Scale floatplane aileron authority with water speed so mouse input cannot roll a stationary aircraft, while control returns progressively during the takeoff run.
- Raise only the solid-ground render baseline by the exact float-bottom offset so the pontoons rest on terrain without changing their water immersion.
- Allow the Water Plane item to be deployed directly onto a targeted water surface while leaving land placement and other aircraft unchanged.
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:McTtzw3T:3UeSOcUh"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:McTtzw3T:3UeSOcUh"
}

