TL;DR
Unnamed train stops in Blueprints shouldn't override color of existing stops.What?
Was not sure if this was intended design choice or an oversight, so I came here. If it's wrong then sorry
If a named train stop is placed via blueprint, it will inherit its name and set color. For unnamed train stops it will have a random name, but the color is still inherited. The same happens when the blueprint is placed above existing train stop: the color of the train stop gets overwritten, plus the name if exists.
This behavior makes sense in theory, but I found the system very cumbersome to play with, due to blueprints overriding my hand-colored, beautiful train stops with default red. I was using the blueprint below, with train stops unnamed. The train stops were merely meant to act as a convenient anchor point to an existing block.
- 20260731_020626.png (601.66 KiB) Viewed 74 times
Why?
Considering the manual "Rename stop" interaction auto-sets the color together, I think there are arguments to be made for treating a train stop's color as a part of its name, or more broadly, its identity. For nameless train stops I would expect them to have no associated identity, not just a name.I suggest either:
- make so that unnamed train stops in blueprints does not have a color, or
- make so that unnamed train stops in blueprints do have a color, but will not override existing train stop's.
Also, unrelated rant, I would kill for a better color picker. Like seriously? Raw RGB slider? In the year 2026?