Links
Tags
Creators
Details
1.0.0
Compatibility
Required content
Changes
First release. Minecraft 1.21.1, NeoForge.
Makes ParCool parkour work on Sable physics ships. Wall running along a hull, wall jumping, wall sliding, grabbing a deck edge, climbing up, vaulting, hanging from rigging and diving all work now, including on sloped and curved plating and on a hull that is banking or pitching.
Sable keeps ship blocks in a hidden area far off the map and only draws them at the ship's position, so ParCool was checking empty air where the ship looked like it was. This projects the player into the ship's coordinate space, runs the same checks there, and rotates the result back.
Requires ParCool! and Sable. With either missing the mod disables itself quietly, so it is safe to leave installed.
Worth knowing With no ship nearby it does nothing at all, so ParCool on the ground behaves exactly as it does without this installed. A real world wall always wins over a ship one. Hooks use MixinExtras, which stack with other mods' handlers instead of fighting them. ParCool+ / Compatibility Addon uses no mixins at all, so nothing to clash with there. Create's super glue and honey are untouched. The mod only reads blocks; the one thing it writes is the player's own velocity while clinging. If ParCool renames something in a future version, this goes inert rather than crashing the game. Config lives in config/parcoolxsable-common.toml — reach and slope tolerance for the grip assist are tunable there, and it can be switched back to ParCool's strict flat-wall rules.
Tested against ParCool 1.21.1-3.4.3.3, Sable Companion 1.6.0, NeoForge 21.1.233.
Full details in the README. Русская версия: README.ru.md.
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:cDxoHsmH:GRrFwLgH"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:cDxoHsmH:GRrFwLgH"
}

