-
-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow aspect filter to be ignored when passive Interaction is true #310
Comments
Thanks for reporting! |
Passive interaction will respect the settings of the aspect, which is Can't you just set the boolean to I'm trying to understand if there's really a need to have passive interaction optionally work without respecting the aspect's filter settings. If so, we should create a separate feature request issue, or convert this issue into a feature request. |
I was told that it should work even when the aspect evaluated to false, which is why I opened the issue. There are times when external things have a better understanding when either something is needed (to extract from the network) or should be returned (to import to the network). So to avoid a "buffer chest", I was hoping the passive interaction would assist those types of scenarios. |
Ok, that's fair. I'll make this a feature request then. |
Issue type:
Short description:
I have an item importer setup with Passive Interaction enabled and "Import all items" set to a
false
card. In that configuration it should accept items being pushed into it externally and it does not.Steps to reproduce the problem:
Setup a network with an Item Importer (was also told an export would exhibit the same issue) with Passive Interaction enabled and try to push items into it. It will fail
Expected behaviour:
Items should be able to enter the network from an part with Passive Interaction enabled.
Versions:
Log file:
The text was updated successfully, but these errors were encountered: