Tags
Creators
Details
Licensed LGPL-2.1-only
Published 4 years ago
Updated 3 months ago
All versions
8.1.1
Release
"PneumaticCraft: Repressurized" 8.1.1 MC-1.21.12 years ago 473
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
Added
- There is now a JEI category showing which blocks can be used as grid blocks for the Electrostatic Compressor
- Iron Bars and Lightning Rods by default, but modpacks may add more blocks via the
pneumaticcraft:electrostatic_gridblock tag - The category shows up when you view the uses of any grid block or the Electrostatic Compressor in JEI (right click / 'U' key)
- Iron Bars and Lightning Rods by default, but modpacks may add more blocks via the
- Added a
pneumaticcraft:minigun_ammoitem tag containing the six ammo items
Fixes
- Fixed server-side memory leak with drones not correctly unregistering an event handler on removal
- Fixed Refinery sometimes caching invalid recipes (in particular if oil is added before there are enough outputs)
- The Drone Interface is now craftable again (re-enabled the recipe datagen)
- Fixed changes to Aphorism Tiles not sync'ing to nearby players (were only getting sync'd on player login)
- Fixed crash in importing legacy Drone Programs
- This only occurs when using vanilla launcher (which is also used by CurseForge launcher) since it installs an older version of the Gson library
- Worked around the issue for now
- Machines with empty tags and/or upgrades should now stack better with fresh blocks of the same type when broken and/or sneak-wrenched
- Fixed Minigun Ammo not being enchantable in an Enchanting Table
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:83vjBvJt"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ncAcdgk7:83vjBvJt"
}

