Well, the contract is something you should fulfill - it does not make certain platform mandatory. You can chose some platform and then change it to another. Contrary, you can not change the contracted station.

My question is: what is your scenario where the additional information would be helpful for you?

Thanks so much for responding!

I feel like the contracts page is the best place to see a top-level overview of your rail operations - while I know that the contract doesn't technically require a specific platform (as long as you've unlocked the tech to change it), I feel that it'd still be useful to be able to see which platforms are currently set for each of the contracts to avoid confusion. Otherwise, if you have several contracts which start and stop at the same station, you could easily distinguish them. I just feel like it'd be really useful information to have, since otherwise it feels hidden in the edit menu.

Hope this makes sense.

I'd rather prefer to enable routing by stations including their platform numbers. Similar to the arrival sensor, but way far before the station and with many signals in between.

Alternativly routing by not only the next station, but routing by any station on the train plan may work out as well.

The example scenario is a track layout with 3 or more stations, where the last station in the chain can only be reached via the 2nd station, but all routing must be done after the 1st station and before the 2nd station due to missing space on the map and the platforms on the 3rd station will lead to different directions. In that case you cannot route trains on their plan by the next station, because the 2nd station will be the same for all tracks and after the second station there is no way to route the trains.

And by the way this could increase the performance as well when there are a lot of tracks and platforms affected. (Assume 15 tracks and 15 platforms on each station. This will be 15^15^15 possible connections. How much RAM will be needed to hash them and how much CPU cycles well be needed to calculate them?)

(Just a mind!)

We are considering to tackle this with "waypoints" approach - the waypoints would be buildable station-like objects that could be part of the train schedule.

Originally posted by Mišo:

We are considering to tackle this with "waypoints" approach - the waypoints would be buildable station-like objects that could be part of the train schedule.

That sounds interesting! I'm curious to hear more about that - Still, I think it'd be handy to have station info in a unified place, so you can see which stations all the contracts are utilizing to prevent any conflicts - if not the contracts page, then perhaps a separate menu? As a new player, I have trouble avoiding "double booking" of station platforms, and such an overview would be extremely helpful.

Usually, to prevent double booking I look at the station timelines when scheduling the contract. It clearly shows if my contract fits the station schedule & indicates when it does not.

Originally posted by Mišo:

Usually, to prevent double booking I look at the station timelines when scheduling the contract. It clearly shows if my contract fits the station schedule & indicates when it does not.

Yes, that is helpful but it's tricky to see all your station's on one screen - that's where I think having the platform number on the contracts page would be handy, since you could see at a glance what platforms are used.

Originally posted by Mišo:

We are considering to tackle this with "waypoints" approach - the waypoints would be buildable station-like objects that could be part of the train schedule.

Can't wait for it