Howdy,
I found a scenario where my placed blueprint will leave the parameter 0 symbol instead of replacing it. I have a filtered inserter feeding into a filtered storage chest with a conditional on the inserter. If I select an item and set the quality to any, it will set the conditional on the inserter (to normal quality) but leave the filter on the inserter and storage create as the parameter.
Here is the blueprint in question, all you need to do to reproduce the issue is place it with an item that is set to any quality.
I know that the any quality item type cannot be set in all these places, but I imagine it should either default to normal on placement or not allow it to be selected as a parameter input?
Thanks,
Diddily
[kovarex] [2.0.10] Blueprint parameter will not resolve when placed with any quality in certain situations.
Re: [kovarex] [2.0.10] Blueprint parameter will not resolve when placed with any quality in certain situations.
I'm getting this on ore stations. I mentioned it here viewtopic.php?f=6&t=117901 as part of a suggestion to allow any quality in circuit conditions.
> paramaterized blueprints of these stations is weird, I set the parameter to copper ore any quality, what actually gets set on the inserters is condition copper ore normal quality and filter param zero any quality.
> paramaterized blueprints of these stations is weird, I set the parameter to copper ore any quality, what actually gets set on the inserters is condition copper ore normal quality and filter param zero any quality.
Re: [kovarex] [2.0.10] Blueprint parameter will not resolve when placed with any quality in certain situations.
Hello, this is not a bug, any quality on storage chest or a circuit signal are simply not supported.
Re: [kovarex] [2.0.10] Blueprint parameter will not resolve when placed with any quality in certain situations.
Hello,
I understand any quality is not supported in the places it has the parameter 0 entry, but its not consistent across the same UI. The enable condition does not support any quality but still reverts down to normal there. Is it possible to have that same behavior (revert to normal when any isn't supported) across the whole system? Or have the parameterized build UI not present any quality as an option if the parameter is used in any place that doesn't support it?
I understand any quality is not supported in the places it has the parameter 0 entry, but its not consistent across the same UI. The enable condition does not support any quality but still reverts down to normal there. Is it possible to have that same behavior (revert to normal when any isn't supported) across the whole system? Or have the parameterized build UI not present any quality as an option if the parameter is used in any place that doesn't support it?