[0.17.69] Train time passed condition resets if there's no enabled stations to go

[m44v]

So if I setup a train schedule with a time passed condition (like in the image), once the condition is met, if there's no enabled stations to go the timer resets and starts again. I find this kind of odd, I would expect that once the timer runs out, it will stay that way and the train will depart as soon as the other station is enabled.

This is problematic with long times, say I set the time condition to 120s, then the train will depart sometime between 0 and 120s after a destiny is enabled, despite the train having met the condition several times already.

This is in contrast with the inactivity condition, in the same setup, the inactivity timer doesn't reset.

[Loewchen]

If the second stop is disabled and there is no other stop, the train is routing again to the first stop, which it is already stopped at. So the timer resets because the train has stopped at the station again.

[m44v]

I understand what's happening, but it's unexpected to the user that doesn't know the internal logic of the train network.

[Klonan]

I don't see how else it would work,

Moving to not a bug

[m44v]

I don't see how else it would work,

oh let's be creative, how about the timer shouldn't reset if the train doesn't physicaly leave the station?