Page 1 of 1

[2.0.76] Train in "no path" state not considered in station

Posted: Fri Jun 12, 2026 5:34 pm
by featheredtoast
Hello, thank you for a wonderful game.

I've noticed that a "no path" interrupt is triggering despite an explicit "not at (Item Input) station" condition when "allow interrupting other interrupts" is set.

Steps to reproduce:
Create a train schedule with the following schedule and interrupts:

Schedule:
pics
Build a connected circuit track with a train + wagon, an Item Input station for iron ore, and a Depot station.
Build a new item drop station for iron ore without connecting to the track circuit.

Expected:
The train at Item Input goes to a "no path" state and remains at Item Input

Observed:
The train at Item Input goes to a "no path" state and departs to Depot

Save file attached using /editor.
The issue appears when "allow interrupting other interrupts" box on the depot interrupt is checked. If the box is unchecked, the train remains at Item Input as expected.
In-game, I am trying to repath any lost trains to a depot, but keep any trains waiting at Item Input stations until a valid Item Drop station is reachable.

Re: [2.0.76] Train schedules with "allow interrupting other interrupts" on "no path" interrupt ignores "not at" conditio

Posted: Fri Jun 12, 2026 6:09 pm
by Loewchen
It is way simpler, a train in No Path state is never considered stopped at any station, the question is if this is intended. Your setup needs to interrupt interrupts because it only gets into the no path state when running the interrupt.

Re: [2.0.76] Train in "no path" state not considered in station

Posted: Fri Jun 12, 2026 6:50 pm
by featheredtoast
Oh yes, thanks for adding the clarification and simplifying it.

It is surprising that a train that is at a station and has not moved may not be considered 'at a station' for interrupts.

Re: [2.0.76] Train in "no path" state not considered in station

Posted: Fri Jun 12, 2026 11:21 pm
by Rseding91
"At station" is when a train is internally registered with a train stop as "stopped at station". A train can physically stay at the same location and un-register from the train stop. At that point - it's not "at station" and instead may be in "no path".

This is working correctly.

Re: [2.0.76] Train in "no path" state not considered in station

Posted: Sat Jun 13, 2026 12:45 am
by featheredtoast
Appreciate the quick response and confirmation, I'll just remove my use of 'no path' conditions entirely in this case.