Tags
Creators
Details
Licensed LGPL-2.1-only
Published 4 years ago
All versions
8.2.21
Release
"PneumaticCraft: Repressurized" 8.2.21 MC-1.21.13 days ago 933
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
Added
- The Liquid Hopper can now absorb Experience Orbs with a Dispenser Upgrade installed, converting them to Memory Essence fluid
- The Programmer GUI now highlights connection lines between jump & label widgets when they're hovered
- Added a toggle button to the Jackhammer GUI to prevent insta-break of blocks
- Useful if you have a fast drill bit and many speed upgrades, to prevent acccidents in your base...
- The Elytra Upgrade in the Pneumatic Chestplate no longer activates when tapping Space if you are currently in Jet Boots builder mode
- Sculk Sensors now detect player movement when off the ground using Jet Boots
- Sculk Sensors can now be hacked with the Pneumatic Armor, disabling them for 10 seconds
- Added a Condition: Dimension programming widget for Drones
- Allows Drones to detect what dimension they're in and branch in their program accordingly
- Drones which do not have a Condition: Dimension widget in their program may no longer change dimension e.g. via Nether portal
- Significant internal Elevator rework which fixes a number of issues - thanks @FireController#1847
Changed
- Updated
pt_brtranslation - thanks @PrincessStellar - Added
fr_frtranslation - thanks @programgames
Fixed
- Fixed bug causing Thermopneumatic Processing Plant to sometimes not require pressure for recipes that should require it
- Fixed a Thermopneumatic Processing Plant JEI issue when recipe input/output fluid amounts differ by a factor of >64
- Hopefully fixed an occasional crash in drone pathfinding
Optional dependencies
Any compatible version
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:ncAcdgk7:JKqGh7uZ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ncAcdgk7:JKqGh7uZ"
}

