All versions
1.1.5-1.21.1
Release
Ender IO: Conduit Optimizer 1.1.5-1.21.12 weeks ago 366
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Changes
📄 Ender IO: Conduit Optimizer 更新日志
English
Fixes
- High-Rate Item Conduits Fell Far Short of Their Rated Throughput: Item conduits whose rated transfer speed exceeds one full stack — such as the Stellar Alloy and Melodic item conduits from Ender IO Evolution — could only move one stack per transfer (64 items, or fewer for items that stack lower). Anything beyond that had to be moved by repeating the same process over and over. As a result, their actual throughput fell far below the values shown in the item tooltip, and moving large amounts of items caused unnecessary extra load on the server.
- This was an oversight on my part during the extensive transfer rework in the previous version — a mistake outside my intention, and I apologize for the inconvenience. Item conduits rated at one stack (64 items) or less per transfer were not affected and behaved exactly as before, and fluid and chemical conduits were never involved.
- This version fixes the issue: high-rate item conduits once again transfer at their full rated speed, while conduits rated at one stack or less remain unchanged.
中文
修复
- 高数值物品导管传输量远低于标称: 标称传输速度超过一组的物品导管(例如末影接口进化中的恒星合金物品导管、旋律物品导管)在上个版本中每次传输最多只能搬运一组(64 个,部分物品一组不足 64 个),多出来的部分只能一遍又一遍地重复搬运。这导致实际传输量远低于物品提示中显示的数值,搬运大量物品时还会给服务器带来不必要的额外负担。
- 这个问题是我在上个版本对传输流程进行较大改动时的疏忽,属于意料之外的失误,给大家带来不便深表歉意。单次传输量等于或低于一组(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:wtxdmB8H"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:SgW9mQeM:wtxdmB8H"
}

