McJtyMods / XNet

Advanced item/liquid/energy/... networking
MIT License
94 stars 53 forks source link

Tags filter option not working, maybe due to custom tags #479

Open Rodg88 opened 3 years ago

Rodg88 commented 3 years ago

I have set up a small ore processing system, and want to use tags to filter where ingots/dusts are sent, but when I enabled tags matching on a connector I noticed it stopped moving anything. Eg I had an iron ingot in the filter slot, with tags setting enabled, and it would no longer pull iron ingots. If I turned off the tags setting, it pulled the ingot again. It was weird because it wasn't even matching the same item as was in the filter (it wasn't pulling iron ingots, even though I'd used iron ingots as the example item in the filter).

After testing some more, It looks like it just isn't matching any tags at all, I thought it might be a black/whitelist thing, but that was just due to blacklist anything/nothing issue, because the tags option was just not matching anything.

Tested in Enigmatica 6 pack v0.4.8, with xnet-1.16-3.0.11, on forge 36.1.0

Rodg88 commented 3 years ago

The other option is it doesn't like custom tags, as in this modpack there's a lot of tag usage done with kubeJS, so maybe default tags are missing and it's not looking at new ones?

Rodg88 commented 3 years ago

Looks like the filter module, where i can define specific tags, will solve my issue in the meantime

Rodg88 commented 2 years ago

Just an update to say I've tested this with xnet-1.16-3.0.16/mcjtylib-1.16-5.1.3, forge 36.2.22 (enigmatica 6 0.5.23), and it's still happening. This connector is pulling everything from the attached chest: unknown