Tags
Creators
Details
Licensed LGPL-2.1-only
Published 4 years ago
Updated 3 months ago
All versions
8.2.13
Release
"PneumaticCraft: Repressurized" 8.2.13 MC-1.21.1last year 58.3K
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
Added
- Jet Boots max height before cutout is now configurable instead of world build height + 64
- See
jet_boots_height_limitin common config
- See
Changed
- All Pneumaticraft fuel fluids are now just in the
c:<fluid>fluid tag, no longer underc:fuels/<fluid>- This is more in line with other mods
- Json syntax errors in aux config files (files in
config/pneumaticcraft/*.cfg) no longer prevent game startup- Instead, an error is logged and startup continues with default settings for that subsystem
Fixed
- Elevator caller screens now have a better button layout algorithm (in particular when there are many floors)
- The "Limit Interaction" setting for the Drone Entity Attack widget should now work correctly when the drone is using a Minigun or Micromissiles
- Pneumatic Chestplate now honours the Apotheosis Elytra affix (Elytra flying allowed with the affix even without Elytra upgrade installed)
- Fixed Pressure Chamber Valves wrongly reporting a 0x0x0 chamber size under some circumstances
- Fixed some client-side memory leak issues
- Fixed crash with Pneumatic Door renderer under some circumstances
- Fixed Void Liquid widget causing drones to "hang" when no filter is in use and the drone has an empty tank
- Fixed Omnihopper and Liquid Hopper block shapes being incorrect with certain hopper rotations
- Fixed Pneumatic Armor hotkeys not updating correctly if changed via vanilla keybinding screen
- Fixed piston reaction behaviour for PneumaticCraft fluids (was pushing fluids, now overwrites the fluid)
- Fixed a crash caused by unselecting all sides of a sided programming widget
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:5Vpj4ZfC"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ncAcdgk7:5Vpj4ZfC"
}

