Issue Description:

The ore sands which have the tag forge:dusts/"material" are not affected by tag item filters with the forge:dusts tag.

What happens:

When using a tag item filter in a routing network the ore sands aren't inputted or outputted when the filter is set to forge:dusts. Similarly, when using the sands in the tag item filter it will only let you choose between the options minecraft:item and forge:dusts/"material". The forge:dusts option does not appear.

What you expected to happen:

For items with the forge:dusts tag to be affected by filter set to that tag or for the ore sands to get their own tag.

Steps to reproduce:

1. Place 2 chests attached to a routing network
   

2. Apply a tag item filter set to "allow: forge:dusts" to both routing nodes
   

3. Put any type of ore sand into the input. It will not be transferred.

4. Putting redstone into the chest will make the redstone transfer to the output. Setting the tag item filter to "allow: forge:dusts/iron" will make it transfer iron dust to the output chest.

Affected Versions (Do not use "latest"):

• BloodMagic: 3.3.3-45
• Minecraft: 1.20.1
• Forge: 47.3.1

bit late to this, but do you think we could support e.g. "forge:dusts/*"?

forge:dusts would do that, it just needs all the "/*" to actually be added to forge:dusts so the tag knows about them
forge:dusts should also be working right now, assuming all the tags surrounding it are set up properly

Similarly, when using the sands in the tag item filter it will only let you choose between the options minecraft:item and forge:dusts/"material". The forge:dusts option does not appear.

This is the problem. The tag filter is working fine, but it cant filter based on a tag that isnt there. forge:dusts/"material" != forge:dusts, thats an extra thing to add that apparently was forgotten. Good news is you can immediately fix it for you with a datapack adding the missing forge:dusts/"material" tags to forge:dusts

At least very very likely