Tags
Creators
Details
1.10.0-rc.15+26.1.2
Compatibility
Required content
Changes
Pumps & Pistons 1.10.0-rc.15
Beta candidate for Fabric on Minecraft 26.1.2 and 26.2. Each Minecraft version has its own build.
- Shorten selected English and German interruption labels to keep them readable beside fuel amounts.
- Configure a pump for petrol or diesel by sneak-using the corresponding can. Sneak-use an empty can to return the pump to automatic mode. Configuration preserves the stored fuel and refuses an incompatible fuel designation.
- Keep the pump's fuel designation fixed while an industrial hose is using it as a source or destination. Disconnect the active transfer before changing the mode.
- Release use before starting another action. Releasing only sneak while still holding use will not turn pump configuration into an accidental fuel transfer.
- Transfer fuel gradually between cans and pumps, and resume an interrupted can refill on the same pump. Holding use after completion waits for a new press.
- See destination contents and capacity alongside the remaining source fuel in a compact HUD. Full and empty messages name the actual container, and an ordinary release shows a neutral stopped state.
The core works independently. For Automobility vehicle fuel support, install the matching Pumps & Pistons: Automobility 1.10.0-rc.15 build for the same Minecraft version. Java 25 and Fabric API are required.
Source code and issue reports: https://git.offchunk.com/Offchunk/pumps-and-pistons
Beta validation includes automated checks and targeted in-game tests on both supported Minecraft versions. Full death/dimension/chunk-unload and client/server protocol-mismatch coverage is still incomplete.
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| pumps-and-pistons-1.10.0-rc.15+26.1.2-sources.jar | Sources jar | 28.51 MiB |
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:HXrsHGrT:8bQweZQT"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:HXrsHGrT:8bQweZQT"
}

