[boskid][2.0.66] Blueprint parameter replaced with nothing on splitter if empty

[VextexFux]

Hello,

I noticed an annoying behavior when creating a blueprint with parameters.
If some parameters are not filled, they are replaced by “nothing”. This especially affects splitters.

Example:
I have a machine that produces item X
X can have up to 6 ingredients
X is placed on "parameter 0"
First ingredient on "parameter 1"
Second ingredient on "parameter 2"
Third ingredient on "parameter 3"
Fourth ingredient on "parameter 4"
Fifth ingredient on "parameter 5"
Sixth ingredient on "parameter 6"

My blueprint contains 6 splitters (each one with a filter set to an ingredient parameter).

If the recipe for X requires fewer ingredients, all the unused parameters are automatically set to “nothing” by the recipe.
As a result, my splitters that were filtered by ingredient (p1, p2, p3 ... p6) lose their filters and become empty.

It would be useful if, when a parameter is not automatically set by the recipe, the filter could keep parameterized icon itself (instead of disappearing).

Example with images:
Base blueprint with parameters:


Placed blueprint with a recipe using only 4 ingredients (out of 6 possible) some items get overflowed to wrong belt:


the blueprint mentioned is attached :

[boskid]

Given that parameters can be empty due to various types of recipe bindings and presence or absence of a filter changes the splitter behavior, i made a change that will only apply to splitters that if a filter would be cleared, splitter will instead keep the original filter whatever it was (in this case it will remain as a parameter filter). This should be now fixed for 2.0.67.

[OvermindDL1]

Will this apply to the filter on the lane splitter type and the filter on the loader type and filtered slots on, say, train wagon types and other such things as well? I've had similar issues with those where they just get cleared and end up 'leaking' things through that they shouldn't on all kinds of filters on various things...

[boskid]

This change only affects Splitters.

LaneSplitters do not support parametrisation right now, Inserters and Loaders should not be affected if a filter is cleared since presence of a filter does not affect anything (they have a "use filter" checkbox that decides if filters should be used at all, compared to splitters where presence of a filter changed mode of operation). If you have problems with other entities please create a new bug report and describe how exactly is the parameter clearing causing your entity to misbehave.