Describe the Bug

A group of brass tunnels that output to chutes, will not split stacks when filters are involved

Reproduction Steps

1. Belt with three chutes beside it in a row
2. Brass tunnels on the belt, outputting to the chutes
3. Split(and force split) will output 1/2 in first chute, 1/4 in second, 1/8 in third, and 1/8 out the nd of the belt.
4. Add filters to the tunnel outputs - 1st & second chute cobble, 3rd and output something else
5. Throw a stack of cobble on the belt
6. All the cobble will end up in the first chute

Expected Result

I would expect the incoming stack of items to be evenly split among the outputs.

Screenshots and Videos

No response

Crash Report or Log

No response

Operating System

OpenSUSE

Mod Version

0.3.2g

Minecraft Version

1.16.5

Forge Version

36.2.29

Other Mods

Enigmatica 6 Expert pack

Additional Context

No response

This issue has been marked as stale because it has been inactive for 3 weeks. It will be closed if it remains inactive for another 3 weeks.

Really don't like the policy of closing issues just because no one has gotten around to them.

That's not a bug.
From your description you have the tunnels on the same belt.
They do not connect in that configuration and each tunnel works alone.

So both setups in the picture above are the same (distribution/filter logic aspect)

And the behaviour seemingly changes with filters, because a filtered exit is preferred over an unfiltered exit.
The behaviour becomes the same again, if you add a filter to both exits, giving them the same priority again.

I think you missed the point I was trying to make. I haven't tested this in two years, so I don't know if it's been fixed in updates, but the problem I had was that the two sets of tunnels in your picture did not behave the same way, and they should. When a tunnel is in split mode, I expect it to split, and in the first configuration, it did not, and the second one, it did. The problem seems to have been caused by the filters changing priority so that subsequent filters get ignored. If that's not a bug, then it's a design flaw

The behaviour you describe is still the same and both setups do behave the same.
And it is the expected behaviour, if you take the individual tunnel thing into account.