[Kovarex] Parametized Splitter filters not setting Quality correctly

[RiverRob]

I need a splitter to filter out all the selected item with the selected quality level, this is what I am trying to produce.
All other items of the same type, but of different quality level, should go the other path.
Then a set of inserters with a filter set for that item and the different levels of quality will pick them up.
One inserter for each quality. If I put down a parameterized blueprint and select Copper plate of Rare quality (My target product), Copper plate of Epic and Legendary will also be produced in lower quantity. I want those Epic and Legendary picked up by their own inserters.
This way I can have the main product handled by a normal setup, and the extra quality ones handled seperately.
When I place this kind of blueprint down, the splitter filter sets to "Normal" quality. Which doesn't work since I'm producing at minimun Rare quality, so everything goes out the other path. Here is a blueprint book with two examples. One works, it doesn't have the filter hardcoded for quality. The other doesn't work, it has the parameter on the inserter set for Legendary quality.
Just place them each and select an item with a higher level quality.

0eNrVVMtqwzAQ/JWwl17kEiVxsQ299R96KMXI8TqI2JKrR1oT/O9d2TgPEkrbQ0kvRlrNzs7uDt5DUXtsjVQuL7TeQrY/RixkLyfX8CbXWo1hKzdK1CGmRIOQgW1r6Rwa6BlIVeIHZLx/ZYDKSSdxzBouXa58UxAy42zKroR1kVQWTaBg0GpLWVqFAsQUJQt+HzPoIFtyOlGNStYEHWmnege6Vhg60Hs0J7I3L0gb5YLSpiHVDNa6CRinSQU8QhDqLeYHUmc89uxC8IJdtHtFK0/PlJbS4HoEJJPuk8H9WCsD7V3rXU5r0WYE11i5oYsD2zgZ17WhhiyJhz7n1QJeOmwofNwyg1oUSJuFZ222dlZJhRTcEePQQvywSFdpGq+WyyThyXHb8zCv23NL/Hu31LhBVQrT/Zlh4n9tmCeNVt252TsZ51uW4dcIo+FHxEDQCHaYT+76gq//BF11k94=

[RiverRob]

This also messes up any other filters (not just the splitter) that don't have the quality set.
So, anytime you set a parameter variable in a blueprint to a specific quality, any other variables in that blueprint without the quality set, default to normal quality.

[RiverRob]

I separated the parameters (hard coded and not) into two different parameter variables, and it resolves the issue. But it requires entering the same parameter value twice which I doubt is what you guys would consider a good solution.
Screen shots below.

11-02-2024, 18-57-26.png (28.45 KiB) Viewed 1079 times

11-02-2024, 18-58-01.png (13.9 KiB) Viewed 1079 times

11-02-2024, 18-58-44.png (21.68 KiB) Viewed 1079 times

[kovarex]

Hello, I'm not able to comprehend what is the actual bug you are trying to explain.
I tried to guess that you mean that any quality changes to normal in splitter, but I tested that and it isn't the case.
I opened the blueprint book, and I don't understand what do you mean by "works" or doesn't work, both blueprints seemed to work as intended for me.

The only difference is, that one of them didn't have special quality, so the actual parametrisation allowed you to select quality, while the other had quality used for the parameter, so you only select the "core" part of the parameter, and value is taken from what is in the blueprint.

[boskid]

This bug report is weird. First of all, it is missing version where the issue was reproduced. Blueprint string is from version 2.0.14. Looking at the code history there was one change around item filters and it is a fix for 118272 but that was fixed in 2.0.13 so the order of events does not match. When i tested latest stable (2.0.43) i was unable to reproduce any issues with the provided blueprint string - any quality item filter was properly set.