For Project Cybersyn we have considered various workarounds, up to and including just forcing the priorities of all same-named stops to 50. Ultimately we settled on issueing a warning when a controlled train lands at a stop with priority not equal to 50.

We have simply been telling people not to ...

With the addition of the new and very helpful LuaSchedule API, I thought it would be a good time to raise this issue again. Having to use intermediating rail stops causes fundamental issues with the builtin priority and train limits systems.

Being able to schedule a train directly to a specific ...

Changed the title.

I don't think it's a duplicate, though. All of the information and developer responses in that thread are no longer valid due to the introduction of train priority. This is a new issue that was solvable in 1.1 but isn't in 2.0.

Mods that generate train schedules often want to send trains to particular stations, even in the absence of unique station names. However, train schedules send trains by station name and can't target particular stations.

In 1.x, mods like LTN would work around this by adding the coordinates of a ...