Create Fabric

Create Fabric

10M Downloads

Smart Chute with filter set to a specific amount doesn't correctly extract items out of inventory

Zetabite opened this issue ยท 6 comments

commented

Describe the Bug

When using a smart chute with a filter set to several items, like nuggets, and set to a specific amount (9) to take out of the connected inventory (double chest for example), i draws 9 nuggets of the same type out of the inventory, till it reaches a stack of a valid nugget that the inventory has less than 9 of it. If there are remaining stacks behind that less than 9 nuggets stack, that have enough nuggets to take out, the chute will stop extracting, even though valid stacks for extraction remain.

Reproduction Steps

1.Place double chest over a smart chute
2.Set filter for smart chute for at least two items
3.Set the smart chute to extract 2 or more items of the same time out of the chest
4.Fill chest with the set items, making sure that the sum of items of the item stacks of one type of the first few filled slots are not dividable by the number set previously.
5. Observe that valid item stacks behind those undividiable item stacks cant be extracted

Expected Result

Smart chute should skip to the next valid item stack if there is one and not stop at the undividable stack.

Screenshots and Videos

Will send tomorrow, just needed to get this off of my chest for now.

Crash Report or Log

No response

Operating System

Arch Linux

Mod Version

0.4.1

Minecraft Version

1.18.2

Other Mods

No response

Additional Context

I am sorry if this is intended behavior. I just expected it would work differently.

commented

Will test on new release in short, and will attach screenshots if the issue remains.

commented

2022-08-09_03 34 47
2022-08-09_03 34 57
2022-08-09_03 35 20

commented

Is this a Forge Create bug?

commented

also, use 0.5.0c if possible.

commented

Its Fabric, I have never used the forge version. Currently trying to get 0.5.0 working, but its crashing

commented

Ok, cant seem to reproduce on 0.5.0, so seems to be fixed. I will reopen in case i have that issue again