I have a BP I made quite awhile ago, and the param picker allows me to select <=Quality, which corresponds to the filters in the inserters among other things (not all of them preserve the <= condition, which is fine):
The problem I'm having is I was trying to make a similar blueprint, but I no longer get the <= condition filter. I assumed the inserters were the parameter that triggered this, so I split item type up to test, and it doesn't give me the quality selector, or sometimes quality without the condition:
Inventory Filters
I've noticed a similar problem from inventory filters.
If I start with this wagon:
Then create a new BP from it, it doesn't show the quality/condition:
Make it into a parameter:
I can no longer select a quality nor condition. The blueprint was created from a wagon with a >=**quality iron ore filter. Now I can only select the item, and the quality/condition in the filter carries over.
My prior train blueprint gives me the option to set both the condition and quality of the wagon item filters:
Did something change in how parameterized BP's work?
BP Parameter not showing quality condition
-
KeepGridButton
- Inserter

- Posts: 22
- Joined: Sat Nov 14, 2020 2:39 am
- Contact:
-
KeepGridButton
- Inserter

- Posts: 22
- Joined: Sat Nov 14, 2020 2:39 am
- Contact:
Re: BP Parameter not showing quality condition
Did AI search of forum and found 119537
So apparently I need to copy a layout where filters end quality/conditions are only set to ==base quality in order for the resulting parameters to light up the condition/quality. I guess the idea being they unify anything sharing the same item icon, and if any quality/conditions are set, then those are assumed to be explicit and shouldn't be parameterized. So if you want quality/predicate to be parameterized, then they should be set to base quality and =.
So apparently I need to copy a layout where filters end quality/conditions are only set to ==base quality in order for the resulting parameters to light up the condition/quality. I guess the idea being they unify anything sharing the same item icon, and if any quality/conditions are set, then those are assumed to be explicit and shouldn't be parameterized. So if you want quality/predicate to be parameterized, then they should be set to base quality and =.