I feel like I should write a followup to explain more broadly, since we're off topic here, but it does work with both station types - I do it by first waiting for a signal, and if nothing happens, allow wildcard interrupt to trigger after.

The downside is a train needs to wait a few seconds longer ...

- circuit-based train routing (see eg. this on Reddit ):

indeterministic destination: trains might arrive to wrong destinations, requiring corrections by rerouting
is incompatible with interrupt-based generic trains
only 1x requester station might be open at the same time, requiring ...

With the inclusion of multiple universe channels coming in 2.1, a player may expect surface mode to also have multiple channels.

(Regardless, having multiple universe channels is huge, definitely my favorite feature in 2.1 - thank you!!!)

Appreciate the quick response and confirmation, I'll just remove my use of 'no path' conditions entirely in this case.

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.

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 ...

This would be such a great quality of life to have.

Absolute positioning helps with initial blueprint alignment, relative positioning is for dragging connected blueprints out.

Having both would be such a good quality of life. As it stands, I'm using absolute positioning for macro-level things ...