[2.0.47] Signals of the same item but different quality get grouped together in blueprint parametrisation

[RainbowFire]

When parametrising a blueprint, signals (values) of the same item but different quality get grouped together. The quality of this signal (value) cannot be changed.

What did I do?

When setting up blueprint parametrisation for a module design, I tried to change the quality of the modules using blueprint parametrisation.

module_blueprint_string.txt

(1.61 KiB) Downloaded 13 times

What happened?

I changed the quality of prod mod 1s, prod mod 2s, but was unable to change the quality of prod mod 3s, as it existed as a recipe (normal quality) and as a signal in my inserters (legendary quality). The signals of different qualities get grouped together in the "parametrise/reconfigure the blueprint"

05-01-2025, 12-40-47.png (231.2 KiB) Viewed 269 times

Possible to change quality

05-01-2025, 12-41-01.png (19.51 KiB) Viewed 269 times

Prod mod3 as recipe (normal quality in EM plant) and circuit condition (legendary quality in inserters)

05-01-2025, 12-41-07.png (150.68 KiB) Viewed 269 times

The signals of different qualities are grouped together. No option to change quality ^^

05-01-2025, 12-41-55.png (180.82 KiB) Viewed 269 times

05-01-2025, 12-42-08.png (70.62 KiB) Viewed 269 times

What did I expect to happen?

I would be able to set the recipe in the EM plants, and the inserters would be untouched.

Reproducibility

Every time.


Smaller example with two inserters. The signals (value) of two different qualities get grouped together, and as a result cannot change quality of the signal (value)

inserters_blueprint.txt

(357 Bytes) Downloaded 12 times

05-01-2025, 12-43-50.png (113.63 KiB) Viewed 269 times

05-01-2025, 12-43-55.png (182.42 KiB) Viewed 269 times

05-01-2025, 12-47-47.png (155.15 KiB) Viewed 269 times

^^ Expecting two signals, prod mod3 of rare quality, and prod mod3 of epic quality.

[boskid]

That is working exactly as intended.

Changes

• Changed the blueprint parametrisation logic related to quality. Before, whenever anything other than normal quality was used with parameters, the quality was always taken from the blueprint, and only the core id was parametrised. Now, this only happens when more than 1 quality with the same id is present instead.

[RainbowFire]

That is working exactly as intended.

Changes

• Changed the blueprint parametrisation logic related to quality. Before, whenever anything other than normal quality was used with parameters, the quality was always taken from the blueprint, and only the core id was parametrised. Now, this only happens when more than 1 quality with the same id is present instead.

So I can't set a recipe using the parametrise/configure blueprint if I also am using that recipe as a signal of different quality.
If this isn't a bug, then I'd like to suggest it as a feature.
What would you suggest I do instead?

[RainbowFire]

For those looking for a workaround, what I ended up doing was reading the contents of the logistics network, outputting to an arithmetic combinator, multiplying the value I wanted (Legendary prod mod3s) by 1, and outputting a unique signal (example, P) I could use (and change in blueprint parametrisation).