[Bug] Exponential Item Duplication via Pipez Ultimate Pipe Upgrade and Create Belt
Plstt opened this issue ยท 5 comments
Version Info
- Minecraft: 1.20.1
- Entangled: 1.3.20
- Pipez: 1.2.5
- Create: 6.0.4
The duplication happens when a container holding at least two identical, stack-limited items (e.g., Diamond Pickaxes) is connected to an Item Pipe upgraded with the Ultimate Pipe Upgrade. The pipe extracts items onto a Create conveyor belt, which then feeds into Andesite Funnel or similar block that sends items to a container linked via an Entangled Block.
It is speculated that since Create Belts are internally treated as containers, Pipez attempts to insert items into them as it would with any inventory. If all available inventories (including the belt) are full, Pipez tries to return the item in the direction it came from. With the Ultimate Pipe Upgrade, this feedback cycle happens extremely rapidly, potentially causing a race condition or overflow where the item isn't properly removed but is still duplicated into the system. This appears to result in exponential duplication, especially when the setup is run in parallel.
The more concurrent item routes or belts involved, the faster the duplication escalates.
Steps to Reproduce:
1.Prepare a container (e.g., a chest or barrel) with at least two identical stack-limited items, such as Diamond Pickaxes.
2.Use an Item Pipe with the Ultimate Pipe Upgrade to extract items from the container.
3.Connect the pipe to a Create mod conveyor belt which transports the items.
4.Use a Funnel or equivalent to transfer items from the belt to a container bound via an Entangled Block.
5.Observe the item count in the destination container.
Entangled does nothing but pass on the item capability from the block it is bound to, hence it is unlikely the duplication is related to Entangled.
Does the same happen if, in step 4, you skip the entangled block and have the items go into the container directly?
It won't occur without Entangled. Direactly using a circuit to transport will not trigger the bug.
I can not replicate the issue. I am missing something needed to replicate it?
