[Kovarex] [2.0.15] Multiple blueprint parameters fields have different selection options

[C__]

There is an inconsistency what you can select for a blueprint parameter value if there are multiple parameters in a blueprint

Steps to reproduce:

• Load attached save file"BlueprintParametersBehaveDifferentOptions.zip". Note this is basically a new game start.

• Place down the blueprint in the player inventory. Since this blueprint contains two parameters, the parameter selection gui appears.

• For the first blueprint parameter value (called "First science") choose any option. For this example choose the iron gear wheel. Notice that only unlocked items are shown.

• For the second blueprint value (called "Second science") choose the logistic science pack (green science). Notice how all options (including unresearched items and items from other planets) are selectable.

Expected behaviour:
For both blueprint parameter fields, I expect the same options to be available.

Observed behaviour:
For the first blueprint parameter field, only unlocked items are shown. For the second blueprint parameter fields, there are many more options (including unresearched items). Comapre the diffence in the attached images "First blueprint parameter selection options.png" and "Second blueprint parameter selection options.png"

When having more than two blueprint parameters (for example a blueprint which contains multiple blueprints of the example blueprint), it seems that the odd numbered blueprint parameters (1, 3, 5, ...) can choose from any item, while the even numbered blueprint parameters (0,2,4,...) can only choose from unlocked items. See attached image "Many blueprint parameters", where the odd numbered blueprint parameters have unresearched items, while the even numbered blueprint parameters only have items unlocked at game start.

[C__]

I also checked in version 2.0.16 and the issue still exists and repreducable with the above steps.

[robot256]

Note that both parameters are used in the same types of entities: Train stop name, combinator output, and combinator input. Neither is assigned to, for example, an assembler recipe where unlocked status might be important.