What did you do?
I blueprinted a locomotive that had a preconfigured route. I've used blueprint parameterization to dynamically apply certain parameters to train station names. The blueprint is created successfully.
What happened?
When I place the blueprint and choose the parameters, not all of them are replaced. Actually, the only parameter that is not replaced dynamically is the name of a train station in an interrupt.
The first screenshot below shows the route of the train I want to blueprint, using the parameters:
In this second screenshot, I'm using the blueprint parameterization so that two parameters can be selected (the number of locomotives and the number of cargo wagons - using the number symbols):
In this third screenshot, we can see that almost all the parameters have been correctly replaced, except for one: the one in the interrupt train station name (I used "Signal-2" for the first parameter, and "Signal-4" for the second parameter while placing the blueprint):
What did you expect to happen instead? It might be obvious to you, but do it anyway!
I expected all parameters to be correctly assigned thanks to the blueprint parameterization, with none left out.
Does it happen always, once, or sometimes?
Always.
---
Log file
Blueprint
Save file
[kovarex] [2.0.15] Train interrupts do not take into account blueprint parameterization
-
- Manual Inserter
- Posts: 1
- Joined: Wed Nov 06, 2024 9:42 pm
- Contact:
Re: [kovarex] [2.0.15] Train interrupts do not take into account blueprint parameterization
The problem with parametrising interrupts is, that interrupts are global, you can create one interrupt and use it in different trains, and edit it for all of them at the same time.
When you parametrise interrupt in a way, that the parametrisation makes completely new interrupt with a new name, it works, but when you try to modify existing interrupt it doesn't, as intended, as you don't want to change other trains interrupt by parametrising blueprint.
When you parametrise interrupt in a way, that the parametrisation makes completely new interrupt with a new name, it works, but when you try to modify existing interrupt it doesn't, as intended, as you don't want to change other trains interrupt by parametrising blueprint.