Reproduction steps:
1. Create a selector combinator.
2. Set the mode to "Random input".
3. Create a blueprint and click the "Parametrise" button.
Expected behavior:
The value set for "Update interval" should be listed and show the Parameter, Variable, and Formula options.
Actual behavior:
The blueprint shows "Nothing to parametrise".
Signal quality selection (from the "Quality filter"/"Quality transfer" modes) also isn't available as a parameter, but I don't know if that qualifies as a bug because as far as I'm aware there's no UI to parameterize that.
[Kovarex] [2.0.52] Can't parametrise selector combinator update interval
Re: [Kovarex] [2.0.52] Can't parametrise selector combinator update interval
I am hestitating about this similarily to 127695 but given that in the end noone complained about decider combinator constant being possible to parametrise i guess adding this to selector combinator's random in 2.0.67 should not cause any problems.
Re: [Kovarex] [2.0.52] Can't parametrise selector combinator update interval
I was taking time off of Factorio (and gaming in general) when 127695 was fixed otherwise I would have complained mightily. That change combined with the coalescing of like values broke my not-particularly-clever vanilla fungible train network, and I just spent the afternoon debugging a bunch of parameterized station blueprints while reminding myself how my own BPs work.
In my case I have a parametrized requestor station that wants to store up to 1.5x train capacity (formally done via the parameter formula: p0_s * 40 * w * 1.5, where w is the count of cargo wagons this station is configured for, defaulting to 1), with the station opening (using train limits, not enable/disable) if current < wanted storage - train capacity (again, with the default train limit being 1). Train capacity comes from another parameter formula and the math is handled using wire and combinator math because I got annoyed at the parameter editor back in December when I was first creating these. Anyway, all of that is preamble to say that adding decider combinator constant values to the parameterization set broke the ability to set more than a single wagon on my station design because setting wagon count to two would also change the static limit to two. As an aside, I absolutely recognize that I can use station enable/disable (especially now that under the hood it's limit management) but that would make dynamic train limits impossible and while I primarily use a lot of 1-1 trains and zero-or-one limit stations, having the flexibility to adjust train size and queue depth is really nice on the occasion that it's needed.
If selector combinator intervals become parameterized it would be really nice if instead of coalescing like values to the same that only values with the same name were flattened into a single value, in essence storing it as a name,value tuple instead of just the value. I'm happy to open a bug report or feature request in addition to this comment here if that helps.
In my case I have a parametrized requestor station that wants to store up to 1.5x train capacity (formally done via the parameter formula: p0_s * 40 * w * 1.5, where w is the count of cargo wagons this station is configured for, defaulting to 1), with the station opening (using train limits, not enable/disable) if current < wanted storage - train capacity (again, with the default train limit being 1). Train capacity comes from another parameter formula and the math is handled using wire and combinator math because I got annoyed at the parameter editor back in December when I was first creating these. Anyway, all of that is preamble to say that adding decider combinator constant values to the parameterization set broke the ability to set more than a single wagon on my station design because setting wagon count to two would also change the static limit to two. As an aside, I absolutely recognize that I can use station enable/disable (especially now that under the hood it's limit management) but that would make dynamic train limits impossible and while I primarily use a lot of 1-1 trains and zero-or-one limit stations, having the flexibility to adjust train size and queue depth is really nice on the occasion that it's needed.
If selector combinator intervals become parameterized it would be really nice if instead of coalescing like values to the same that only values with the same name were flattened into a single value, in essence storing it as a name,value tuple instead of just the value. I'm happy to open a bug report or feature request in addition to this comment here if that helps.