[Kovarex] [2.0.15] Rocket part can't be used in parameterized blueprint train station names

[Neutrality]

I have a blueprint of a train with a schedule that looks like this:

- "[parameter-0] out" until full cargo
- "[parameter-1] gets [parameter-0]" until empty cargo

with [parameter-0] and [parameter-1] being the special parameter icons

I set up a "[rocket fuel icon] out" station and a "[rocket part icon] gets [rocket fuel icon]" station using the icon picker for the station names. Then, I placed down the blueprint train, and set parameter 0 to be rocket fuel and parameter 1 to be rocket part.

What happens after, is that it says there are no stations with the "[rocket part icon] gets [rocket fuel icon]" name. I can still manually add it to the train's schedule and then it goes to it just fine. I didn't see this issue with the copper plate icon, the advanced oil processing recipe icon, or the green wire icon; in all these cases, it was able to find the station properly.

My guess is that it's caused because the rocket part is a hidden item?

[robot256]

Can you share a savegame with the blueprint in question? I can't reproduce this. The rocket part icon is produced by the tag [recipe=rocket-part], and it hasn't offered me any other icon to click on. Folks have had issues with item/entity/recipe icons looking the same even though they are different, but even if I type [item=rocket-part], it gets counted in the number of stations with [recipe=rocket-part] so maybe they fixed that?

[Neutrality]

I used the /cheat command in this save but I originally saw it in a save without /cheat

[kovarex]

Hello, I fixed this issue for the next release.
The core of the problem was, that rocket part item is hidden, so normally the recipe is selected, but in the parametrisation, it picked the first available object with the compatibile name ignoring the hidden parameter.

So the result was, that blueprint parametrisation made the tag [item=rocket-part], while the original station had [recipe=rocket-part], which looks the same, but is a different name.

I'm not making a migration which would convert the existing stations already present, but newly created stations work properly.