[2.0.12] Train interrupt destination path behaves unexpectedly

[tman540]

I was trying to build a train schedule that went something like this:

• 1. Coal Pickup
  • Wait until full cargo OR 5s of inactivity
  2. Dropoff
  • Wait until empty cargo
  3. Iron Pickup
  • Wait until full cargo OR 5s of inactivity
  4. Dropoff
  • Wait until empty cargo

I wanted to make a depot where the trains could go if any of the stations were inaccessible (to prevent clogging).
I couldn't figure out a way to do that so I had the idea to try to build an interrupt like this:

Trigger - Destination full or no path
Target - Depot

• Wait 5s

The behavior I expected was that after the 5 second timeout, the train would attempt to go to the station it was on its way to before (for example, if it finished at "Coal Pickup", it would try to set its destination to "Dropoff"). Instead what happened was the train set its destination to the station it was at when it got interrupted ("Coal pickup" in this example), got to the station and immediately had its wait condition satisfied (full cargo in this case) and then immediately got interrupted again and went back to the depot. The reason I would expect it to try to go to "Dropoff" in this case was because the wait condition of the "Coal Pickup" station was satisfied, THEN it got interrupted. I'm not sure if this is a bug or intended behavior, but it's not very intuitive in my opinion.

[custodia]

+1 on this, I also ran into this problem and there's another post about it here: viewtopic.php?t=117344

This definitely seems like a bug because the behaviour is different to other interrupts. For example if you set the interrupt to be "X station is full" then the intterrupt works as you would expect.

[Loewchen]

viewtopic.php?f=7&t=116850