All versions
1.0.8-1.21.1
Release
Ender IO: Conduit Optimizer 1.0.8-1.21.13 months ago 472
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
📄 Ender IO Conduit Optimizer Update Changelog
🇺🇸 English
✨ Features & Improvements
- Server Configuration & Custom Frequency Toggle: Added a server configuration file. Server administrators can now disable the "Custom Extraction Frequency" feature for item conduits. Disabling this feature reduces unnecessary server calculations and helps improve overall item conduit performance.
- Native Speed & Smart Sleep Mechanism: When the custom frequency feature is disabled, conduits will strictly operate at their native speeds based on their tier (e.g., normal, enhanced, or ender conduits). The smart sleep / anti-lag algorithm will still remain fully active in the background, pausing conduits for up to 40 ticks when inventories are empty or full to protect server TPS.
- Under-the-hood Performance Optimizations: Optimized the internal routing and distribution logic of item conduits. This helps reduce server resource usage and improves performance stability for complex factory setups and massive conduit networks.
🐛 Bug Fixes
- Extraction Limit Fix: Fixed an issue introduced in recent versions where item conduits were incorrectly limited to extracting a maximum of 64 items per operation in the standard round-robin distribution mode. Conduits can once again bypass this limit and extract large amounts of items at once, depending on their tier and the attached inventory.
🇨🇳 中文
✨ 新增与优化
- 服务器配置文件与频率自定义开关: 新增了服务器配置文件。服主现在可以手动选择关闭“允许玩家自定义物品导管抽取频率”的功能。关闭该功能可以减少不必要的服务器计算,进一步优化物品导管的整体性能。
- 原生速率与智能休眠机制: 在关闭自定义频率功能后,导管将严格按照其自身级别的默认速度运行(如普通、强化、末影导管的原生频率)。同时,防卡顿的智能休眠算法依然会在后台全局生效——当面临空抽或目标满载时,导管仍会自动休眠(最高 40 tick),持续保护服务器的流畅度。
- 底层性能优化: 重新梳理并优化了物品导管在分配和寻路时的底层逻辑。减少了超大型导管网络对服务器资源的占用,有助于改善复杂工厂环境下的 TPS 表现。
🐛 问题修复
- 抽取上限修复: 修复了在近期版本中,物品导管在原版普通分配模式下,单次抽取数量被错误地硬性限制在 64 个的问题。现在导管再次能够根据自身级别的数值,突破该限制并一次性抽取大量物品了。
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:SgW9mQeM:OeSW0z9a"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:SgW9mQeM:OeSW0z9a"
}

