Issue Description:

I think the priority system of the item routing nodes isn't working as intended.

What happens:

I have a Storage Drawers hub that stores most of my items. I then also have an array of chests that are based off mod. I'm using no filter for inputting into the drawer network, and then mod filters on the chests. No matter what I set the priority to, some items still end up the mod chests instead of the drawer network.

What you expected to happen:

Either low number being the first location, or high number being the first location. No items going elsewhere unless that destination is unable to take more.

Steps to reproduce:

1. Input node on a chest
2. Output node on drawer network. No filter
3. Output node on another chest. Mod filter
4. Place items to be sorted into a drawer slot, have other items from that mod set to the mod filter chest.
5. Seemingly random when items go one way or another regardless of priority settings.
   ...

Affected Versions (Do not use "latest"):

• BloodMagic: 2.1.6-75
• Minecraft: 10.10.2
• Forge: 12.18.3.2254

-Simply Magic 2 pack version 0.1.4

Additional Question

Is there a way to speed the transfer of items? I'm using crushing rituals for cobble gen, obsidian gen, Fortune, and grinding (iron/gold). This alone is pretty much maxing out my transfer capabilities. Can it be upgraded to do more than 8 items per transfer? Or to go faster?

I second the speed transfer question.

and for my routing priority, it goes off which was the first node added to the network-last node added.

Do you have multiple output nodes on the same priority? That could cause some wacky behavior, and have you set the input priority to anything besides default?

I have a similar setup to the OP; Storage Drawers for most stuff, and an overflow chest, one input node from an Multistorage Enderchest. Some items go into the overflow chest when they should not. My impression was that if the link to the drawers is in use (that is, I dumped multiple stacks into the Enderchest), the next item will go to the overflow chest.

I'm having the same issue. Tested with just two output nodes, each set to different priorities and as @laurad2423 mentioned above, it prioritizes in the order the output nodes were added to the network and seems to ignore priority. One of the nodes contained a precise item filter if that matters.

My input priority (single input) was set to default.

Investigate label.