"No stops with this name exists" blocks other interrupts

[Ranec1]

Tl;dr: When a train is routed to a "no stops with this name exists" it blocks all future interrupts.

This is based on how my train network uses wildcard interrupts normally but then uses a special flag to indicate things need to go my mall/base at times. The setup works except when the wildcard stop does not exist. The tricky part is that the train may sit for awhile in the "no stops with this name exists" because my base doesn't need the resource. When the circuit bit is flipped it no longer interrupts the train.

However, this is not how interrupts behave when the destination is full. In this case, the train will sit idle with Zzz's displayed. When the circuit signal is sent the train will leave after a few seconds (probably the game circuit processing delay).

My current workaround is to create a fake stop with zero train capacity for everything on my rail network. This stops the "No stops with this name exists" but is a bit annoying for the number of items I am managing.

---

Reproduction Steps:

• Setup a loop with three stops: A, B, DeleteMe

• Create a train. It's only listed stop is "A". It has an interrupt to go to "B" when a flag is set and enable allow interrupting other interrupts. It has an interrupt to go to "DeleteMe" when the flag is not set.

Working Test Case #1:

• Set the "DeleteMe" stop to train capacity zero.

• Start the train. It should try to head to "DeleteMe" but fail with Zzz's because it has no capacity.

• Send the flag signal to the train. The train will head to "B" after a small delay.

Unexpected Test Case #2:

• Halt the train back at "A". Disable the flag. Remove the "DeleteMe" train stop completely.

• Start the train. It should try to head to "DeleteMe" but fail with "no stops with this name exists" because it has no capacity.

• Send the flag signal to the train. The train will remain with the same error.

It is unexpected that the "no stops with this name exists" sets the train into an unrecoverable error state. I would hope this would still enable other interrupts to be processed if they become true in the future.

---

Note: There is a semi-related issue that doesn't exist if the above was changed. If at the end of the second test you add the "DeleteMe" stop back with no capacity it will not interrupt the train either. It seems to be in an odd state until you remove the temporary stop that did not exist previously. Even moving from Automated to Manual and back doesn't fix it.

[Rseding91]

Thanks for the report however after disusing his internally, this is working correctly. If you don't want a train to wait for a non-existent stop - don't tell it to go to a non-existent stop.