[0.11.22] Train still but not "stopped"
Posted: Mon Jul 13, 2015 12:15 pm
Description:
Inserters cannot interact with a train standing in a station, when said train has a non-existing stop as its next destination.
How to reproduce:
1. Build a circular rail with two stops (say "stop1" and "stop2").
2. In stop1, place a crate with some fuel and an inserter which should refuel the locomotive when stopped.
3. Set a path where the train goes to both stations and spends 0 time in each, and let it run.
4. After the train leaves stop2, pick up ("mine") stop2.
5. The train then reaches stop1 and becomes "still but not stopped", and the inserter cannot place fuel in it.
6. If the missing station is removed from the drive-plan, the inserter can now place the fuel in the locomotive.
Here's a savefile which reproduces this:
http://s000.tinyupload.com/?file_id=306 ... 8850226509
(mods: WaiTex 0.5.0 + test-mode 0.11.7)
In my opinion, a good fix is such where inserters could simply interact with moving trains.
(I think that the current behavior/bug is caused exactly because this was something the devs didn't want).
Inserters cannot interact with a train standing in a station, when said train has a non-existing stop as its next destination.
How to reproduce:
1. Build a circular rail with two stops (say "stop1" and "stop2").
2. In stop1, place a crate with some fuel and an inserter which should refuel the locomotive when stopped.
3. Set a path where the train goes to both stations and spends 0 time in each, and let it run.
4. After the train leaves stop2, pick up ("mine") stop2.
5. The train then reaches stop1 and becomes "still but not stopped", and the inserter cannot place fuel in it.
6. If the missing station is removed from the drive-plan, the inserter can now place the fuel in the locomotive.
Here's a savefile which reproduces this:
http://s000.tinyupload.com/?file_id=306 ... 8850226509
(mods: WaiTex 0.5.0 + test-mode 0.11.7)
In my opinion, a good fix is such where inserters could simply interact with moving trains.
(I think that the current behavior/bug is caused exactly because this was something the devs didn't want).