Given the setup:
- A train has two interrupts A and B, with B set to "Allow interrupting other interrupts"
- The train has triggered A and is waiting at A's station for conditions
- The player manually sends the train to a station in it's schedule (let's say C)
The train will:
- Go to C as manually requested by the player
- Once C's conditions are fulfilled, and assuming B can trigger, B correctly triggers
- B routes a path to B's station and reserves the train stop
- B does not move and seems to think it has already arrived at B's station
Expected behavior:
- Once B triggers, it routes a path and continues there until it's conditions are met
I attached a map to show the bug. To reproduce:
1. Stand near a station to trigger a Train Call interrupt
2. When the train gets there, send it to Station 1 or Station 2 manually
3. Move away from the station so it doesn't call the train back
4. Wait for it to arrive. Its Return to Dispatch interrupt should trigger, and it'll route a path to Dispatch, but it won't actually go there. If the other station triggers its Train Call interrupt the train will interrupt the Return to Dispatch interrupt (even though it's not set to, which I assume is because it thinks it's already at Dispatch)
[2.0.11] Overriding a train interrupt borks the train
[2.0.11] Overriding a train interrupt borks the train
- Attachments
-
- Bug Testing.zip
- (3.67 MiB) Downloaded 12 times
Re: [2.0.11] Overriding a train interrupt borks the train
This seems to be fixed in 2.0.12