Allow for train interrupts added before current stop
Moderator: ickputzdirwech
Allow for train interrupts added before current stop
I've been trying to create a waiting area for my trains using the new interrupts system (which I love by the way), and I've been having trouble with it. I have an interrupt set to when the destination is full it goes to the waiting area (for example, my smelter station is full as it's leaving the mining station, so it goes to wait until the smelter is available). However, because the interrupt gets added after the target station, this means that the interrupt gets added after my smelter station. Once the train arrives at the waiting area, it paths to the next station (the mining station). This creates a loop of the trains just constantly going back to my mining stations and never waiting at the waiting area. There should be the option for various interrupts to add the interrupt to the schedule before the stop it's currently pathing to, rather than after.
Re: Allow for train interrupts added before current stop
Agree 100%. Just spent 7 hours trying to solve this and got nowhere.
Devs need to look into this.
Devs need to look into this.
Re: Allow for train interrupts added before current stop
When an interrupt is allowed tointerrupt another isn't it selected as the next target in the schedule regardless where it is added?
Re: Allow for train interrupts added before current stop
An interrupt is selected as the target, however it’s added *after* the current target. This means that once the interrupt is completed, instead of resuming its original path, the train skips over the station it was going to before the interrupt and moves on to the next onemrvn wrote: Thu Oct 24, 2024 6:55 am When an interrupt is allowed tointerrupt another isn't it selected as the next target in the schedule regardless where it is added?
Re: Allow for train interrupts added before current stop
I think this is actually a bug. Developers please fix. It should always handle interrupt and return back to the previous task when interrupt was triggered, not the next task in the schedule. The same as it is done in hardware interrupts.