Interrupt condition and waiting condition should match up
Posted: Thu Nov 06, 2025 7:04 pm
There is an interrupt condition "Destination full or no path"
There are also similar sounding wait conditions "Station is (not) full"
Unfortunately the wait conditions don't emulate the interrupt condition
Consider a situation when you have disjoint rail networks, with same name stations
Within first rail network suppose the station is full, and in the second it is not full
If a train in first rail network has the interrupt condition, it would trigger
But waiting on condition "Station is not full" would immediately pass, because the station in the separate rail network fulfills it
Hilariously though waiting on "Station is not full" is not even necessary, functionally this situation works, as the train is stuck in a perpetual interrupt loop
But despite this working, it is annoying because it is constantly alerting "train has no path" , and disabling that alert is not ideal
There are also similar sounding wait conditions "Station is (not) full"
Unfortunately the wait conditions don't emulate the interrupt condition
Consider a situation when you have disjoint rail networks, with same name stations
Within first rail network suppose the station is full, and in the second it is not full
If a train in first rail network has the interrupt condition, it would trigger
But waiting on condition "Station is not full" would immediately pass, because the station in the separate rail network fulfills it
Hilariously though waiting on "Station is not full" is not even necessary, functionally this situation works, as the train is stuck in a perpetual interrupt loop
But despite this working, it is annoying because it is constantly alerting "train has no path" , and disabling that alert is not ideal