If a have two TNFP stations with the same name (like, "Shuttle Main base") and call a TNFP train to one of them, the train may arrive to another one. That's quite fine. The problem is that the train panicks like, "Oh, no, it's not the station I was requested to, I depart back immediately!" That's wrong, the train should understand that it is the correct station.
Thats brilliant and I find it amusing to watch, particularly as its technically sort of working as intended. Its selected the nearest train stop to the player and is tracking it by its id, but the train is pathing to the nearest one to itself based on name alone and clearly they're not always the same train stop ;)
Leave it with me and I'll add some additional logic so it handles this a lot more sensibly.
I've added some additional logic into v0.5.1 to handle this a bit more gracefully. When it detects the trains arrived at an unexpected station with the same name as the one it was dispatched to it will now treat that as a success -- but will provide a different message and also (if enabled) show the path to the station it actually arrived at.
I haven't changed the boarding timeout behaviour though and the default of 15s isn't a long time to react in this kind of situation, which can mean the train departs anyway by hitting that timeout. I was debating adding some additional logic but kinda decided against it because the boarding timeouts already a mod setting, but if you've any particular opinions on that let me know.
