You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
i'm not completely sure if that might be intended behaviour.
assume i have 2 engines 'A' and 'B' available, and i have currently 2 trains '1' and '2' with engine 'A' in the depot.
'1' is stopped in the depot.
'2' is set to go, but is currently unable to do so (exit blocked)
i set up a replacement rule from 'A' to 'B'
and now i hit the "upgrade" button in the depot
now it replaces the engine of the train '1' as expected
but it also replaces the engine of train '2', while one would expect, that autoreplace for train '2' fails, because it is not stopped (selling, moving wagons etc. don't work either).
I coded it like this on purpose. It will (like completely automated autoreplace) stop and start the vehicles without the user being able to notice this.
Eddi opened the ticket and wrote:
Reported version: trunk
Operating system: All
This issue was imported from FlySpray: https://bugs.openttd.org/task/684
The text was updated successfully, but these errors were encountered: