"Same Names" and Depots - Something to watch for
Posted: Mon Apr 13, 2020 8:09 pm
I'm working on a documentation project and realized an edge-case while considering the 1.13.0 update.
Previously, a station meant to act as a Depot was intentionally named the same as its peers. An improperly configured Depot Station (lacking the depot signal) would show a pink warning lamp as a 'duplicate name" error.
With the current update allowing for duplicate names, it is possible for a train to be routed to a station (sharing the depot name) that cannot fulfill the functions as such. The schedule, filter, locked slots, etc. are preserved and the train will attempt the previous schedule again.
I am in no way suggesting a change, simply that a new "problem" condition arises that folks should watch for.
Previously, a station meant to act as a Depot was intentionally named the same as its peers. An improperly configured Depot Station (lacking the depot signal) would show a pink warning lamp as a 'duplicate name" error.
With the current update allowing for duplicate names, it is possible for a train to be routed to a station (sharing the depot name) that cannot fulfill the functions as such. The schedule, filter, locked slots, etc. are preserved and the train will attempt the previous schedule again.
I am in no way suggesting a change, simply that a new "problem" condition arises that folks should watch for.