[2.0.47] Train stop limit and priority are not unique parameters

[connesy]

When creating a blueprint of a train stop, I wanted to include item stack size as a parameter.

Parametrized item pickup train stop

1 - Train stop.png (882.23 KiB) Viewed 250 times

Because this happened to be 50 (p0_s) for the existing item, when blueprinting this train stop, the parametrization created a single parameter where both the "50" for the item stack size, and the "50" for the train stop priority were set.

4 - Combinator with stack size.png (88.35 KiB) Viewed 250 times

3 - Blueprint.png (687.73 KiB) Viewed 250 times

5 - Parametrization, train priority.png (115.02 KiB) Viewed 250 times

The same happens when using circuit logic to set the train stop limit, in which case the train stop limit value is set to 0. If another item in the blueprint also has the value "0" (e.g. a decider/arithmetic combinator), these are also collected into the same parameter.

6 - Parametrization, train limit.png (112.59 KiB) Viewed 250 times

I can de-couple the priority from the item item stack size formula by setting the priority to e.g. 90 before creating the blueprint, but this doesn't work with the train stop limit, as that will always be set to 0 when enabling "Set train limit" circuit logic, so any other "0" in the blueprint will set the train stop limit as well.

7 - Parametrization, with priority set to 90.png (119.05 KiB) Viewed 250 times

I would expect/hope that the train stop limit and priority would always be their own parameters in a blueprint. Then we could set them using variables from earlier parameters.

[Loewchen]

Parameters are distinguished by value only, that is an intended limitation of the feature. It might change in 2.1 though.