Jump to content

Quality of Life issue with None as default filter


Cookiematico
  • Branch: Preview Branch Version: Windows Pending

The change of adding None as default to filters is rather useless and detrimental. It basically allows ANYTHING to go through to the exit port instantly on activation regardless if you set the filtered component, while the original blocked gas output on both ports until you selected the filtered output. While the old version allowed you time to set it up by dupes and activate at your own leisure, now you have to check instantly at its creation and/or before connecting with power. Why go backwards?

Suggestion: don't make None as default.


Steps to Reproduce
- Just build filter with everything needed: power, connection etc. The instant it gets completed it lets anything through to output filter. While this is to be expected, its a serious step down on planning/building as old version only activated once you manually set the filter.



User Feedback


There are no comments to display.



Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
  • Create New...