Tags
Creators
Details
Licensed LGPL-2.1-only
Published 4 years ago
Updated 2 weeks ago
All versions
8.2.18
Release
"PneumaticCraft: Repressurized" 8.2.18 MC-1.21.15 months ago 7,048
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
Added
- Added more stonecutter recipes for Reinforced and Compressed Stone to match vanilla stone recipes
- Reinforced/Compressed Stone -> brick slabs, stairs & walls
- More charging modes for both Air Canisters and Pneumatic Armor chestplate charging upgrade
- Added "Held" and "Held + Armor" modes
- Ctrl-V now works to paste clipboard text into the Aphorism Tile GUI
Fixed
- Fixed Pneumatic Armor entity/block trackers not clearing tracked objects on dimension change
- Fixed visual mess with Thermal Compressor GUI temperature gauges
- Fixed equipping a piece of Pneumatic Armor to replace another piece not causing armor re-init
- Fixed several cases of player crouching being wrongly interpreted as "sneak key held"
- e.g. when crouching under a slab without sneak key held, right-clicking minigun opened the gun's GUI
- Fixed Minigun using up ammo when the ammo had Unbreaking enchant or when gun had Item Life upgrades installed
- Fixed issue with opening Pneumatic Armor GUI passing the hotkey into e.g. Entity Tracker GUI as a keypress
- Cleaned up several hardcoded text messages, adding translations for them
- Fixed right-clicking a Reinforced Pressure Valve not opening the Pressure Chamber GUI
- Fixed Reinforced Pressure Valve not accepting upgrades
- Added a mod-present condition to Create: Low Heated Basic Burner heat properties recipe to avoid errors being logged
- Fixed Aerial Interface experience fluid type selection button (was sometimes de-syncing between server & client)
Optional dependencies
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:xiSEBiVi"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ncAcdgk7:xiSEBiVi"
}


