All versions
1.0.10-1.21.1
Release
Pipez Optimizer 1.0.10-1.21.1last month 414
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Changes
📄 Pipez Optimizer Update Changelog
English
Performance Improvements
- Faster Item Filtering: Pipes with item or fluid filters (especially "exact match" filters that compare an item's full data, such as enchantments or custom names) now decide whether a stack may pass much faster. Repeated checks against the same item are answered instantly.
- Less Re-ordering Work: Pipes no longer re-sort their destination lists over and over when nothing has changed, which noticeably reduces overhead in large pipe networks.
- Lower Overall Overhead: Several heavily used internal routines were rebuilt to avoid creating large amounts of temporary objects every tick.
Fixes
- Random Distribution: Pipes set to "Random" distribution now draw a fresh random order each time, instead of getting stuck on the very first order they rolled.
- Filter Editing: Modifying a filter in the pipe settings window now takes effect immediately. Previously, the old check result could briefly stick around for the same item.
Compatibility
- Invasive Optimizations: Pipez Optimizer can now be installed together with Invasive Optimizations without errors, and all of its features keep working normally.
中文
性能优化
- 物品过滤提速: 配置了物品或流体过滤器(尤其是比较物品完整数据、如附魔或自定义名称的"精确匹配"过滤器)的管道,判断物品能否通过的速度大幅提升。对同一物品的重复检查现在可以立即得出结果。
- 减少重复排序: 管道在目标没有变化时不再反复重新排列目标列表,大型管道网络的运行开销明显降低。
- 整体开销降低: 重写了管道运行中若干使用最频繁的内部流程,减少了每刻大量临时对象的产生。
修复
- 随机分布: 设置为"随机"分布的管道现在每次都会重新抽取随机顺序,不再固定停留在第一次的结果上。
- 过滤器编辑: 在管道设置界面中修改过滤器后立即生效,不再出现同一物品短暂沿用旧判断结果的情况。
兼容性
- Invasive Optimizations 兼容: 现在可以与 Invasive Optimizations(侵入式优化)同时安装而不报错,本模组的全部功能均正常工作
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:HVAFkCTk:SA4jx6m0"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:HVAFkCTk:SA4jx6m0"
}

