[2.0.75] (Minor) Inconsistency between "Read train count" and "Read stopped train"
Posted: Tue Feb 24, 2026 7:27 pm
Both the descriptions of a train stop's "read train count" and "read stopped train" claim that they include the train stopped at the station, which is the case during normal operation. But if the train cannot path to the next train stop (either due to no station being full or there being no path to the target station) such that the train "sits" at the previous stop, then only one of the two signals disappears, implying that the train is both stopped and not stopped at the station simultaneously.
Steps to reproduce:
The train should automatically travel to the "Reachable" station, where it will wait for 10 seconds. During this period both signal T and signal C should be present, as expected.
Once 10 seconds have passed, the train will attempt to path to the "Unreachable" station (which it cannot) and then the train ID will disappear while the train count signal remains present:
If the train is still considered at this stop, then I would expect both signals to be present here. If the train is not considered at this stop, then I would expect both signals to be absent. Perhaps there is a good reason for this behavior behind the scenes, but if this is the case the current tool-tips should probably be amended to mention this behavior.
Steps to reproduce:
- Create a new sandbox save
- Enter editor mode
- Import this blueprint and paste it into the world:
The train should automatically travel to the "Reachable" station, where it will wait for 10 seconds. During this period both signal T and signal C should be present, as expected.
Once 10 seconds have passed, the train will attempt to path to the "Unreachable" station (which it cannot) and then the train ID will disappear while the train count signal remains present:
If the train is still considered at this stop, then I would expect both signals to be present here. If the train is not considered at this stop, then I would expect both signals to be absent. Perhaps there is a good reason for this behavior behind the scenes, but if this is the case the current tool-tips should probably be amended to mention this behavior.