Logistical Sorter Filter - Priority only matters for the first item pull
sumsar2000 opened this issue · 2 comments
Issue description:
Just as the title says. Say I have a material filter set up to gather everything related to stone, so stairs, slabs, etc., but I want the actual normal stone in a chest on it's own.
To do that, I set up tag filter using forge:stone to sort all whole, uncrafted stones to a separate chest, and put that filter to the top of priorities. It works as intended, but only if the logistical sorter is handling ONE stack at a time. If I insert multiple stacks, or switch it to single item pulling, it starts alternating between the two rules. So if I have normal andesite, half of it will go into the stone-only chest, the other half will get sorted under the material filter.
This has to be a bug right? Or am I just stupid and missing a really obvious way to turn this off? I don't have round robin on, if that means anything.
Example with Slate, which is a forge:stone tagged block. Note that I changed the colour of my second filter from red to green after taking the setup screenshots.
Steps to reproduce:
- Make any broad filter in a sorter
- Make a more specific filter that covers an item already covered by the previous filter.
- Place second filter higher in priority (This step currently makes no differrence other than for the very first item pull).
- Move a lot of items at the same time.
Version (make sure you are on the latest version before reporting):
Forge: 31.1.87
Mekanism: 1.15.2-9.10.5.418
Other relevant version: Valhesia 2 2.2.0a (Modpack)