Tags
Creators
Details
1.10.3+26.2
Compatibility
Required content
Changes
Safer dismantling and clearer machine feedback
Mining a stocked pump, pumpjack or refinery in survival now leaves the machine intact and explains what remains inside. Refinery protection also covers stored heat and an unfinished batch. Drain liquids and finish processing before moving equipment to recover the resources.
After a blocked mining attempt, deliberately discard the contents by sneak-right-clicking the same machine with a pickaxe, then mining it while sneaking within ten seconds. The confirmation belongs to that player and machine; adding resources or starting another batch invalidates it. Holding the mining button cannot confirm. Creative removal and existing block-break permissions retain their normal behavior.
Right-click a fuel machine with a pickaxe to inspect its contents, capacities and relocation state. Pumpjacks distinguish missing power, full buffers and depleted or absent fields. Survey results now describe the direction of a field region without presenting a region offset as the player's distance to oil.
Warnings stay readable with chat hidden; enable chat for detailed inspection. Updated messages and illustrated manual pages cover all 18 languages. Production rates, fuel quantities, transfer controls and existing settings are unchanged.
The core works on its own with Fabric API and Java 25. For vehicles, install the matching 1.10.3 integration and Automobility: Unofficial Port 0.5.0-unofficial.36 for the same Minecraft version on the server and every client.
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| pumps-and-pistons-1.10.3+26.2-sources.jar | Sources jar | 41.08 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:gpgRmTNR"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:HXrsHGrT:gpgRmTNR"
}

