Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Vehicles sometimes inherit previous orders of old vehicle number #5914

Closed
DorpsGek opened this issue Feb 15, 2014 · 5 comments
Closed

Vehicles sometimes inherit previous orders of old vehicle number #5914

DorpsGek opened this issue Feb 15, 2014 · 5 comments
Labels
flyspray This issue is imported from FlySpray (https://bugs.openttd.org/)

Comments

@DorpsGek
Copy link
Member

Simons_Mith opened the ticket and wrote:

Buy vehicle x, give it some orders. Sell it. Buy some other vehicle Y which supports the same cargo, but which may be radically different in terms of speed, capacity etc, and if it happens to inherits the old vehicle number it will inherit the old orders too.

Is this intentional? It's sometimes useful, sometimes a pain, but I am a little bit worried by the fact that the old data is still floating about internally even while no vehicle exists for those orders to be associated with.

Reported version: 1.4.0-beta4
Operating system: Mac OS X


This issue was imported from FlySpray: https://bugs.openttd.org/task/5914
@DorpsGek
Copy link
Member Author

Simons_Mith wrote:

I tried this with a 5 passanger Black Cab and then replaced it with a variety of other vehicles. Only when I bought two new vehicles at once did the old orders get cleared.


This comment was imported from FlySpray: https://bugs.openttd.org/task/5914#comment13064

@DorpsGek
Copy link
Member Author

fonsinchen wrote:

The standard use case for that is manual vehicle replacement; in the old days before we got automatic replacement that was the only way to do it. I believe it's been like that already in the original TTD. Arguably, in this day and age, it doesn't make much sense anymore.


This comment was imported from FlySpray: https://bugs.openttd.org/task/5914#comment13067

@DorpsGek
Copy link
Member Author

3298 wrote:

It still makes sense in cases where autoreplace doesn't work, which is mainly the transition between incompatible railtypes (rail->monorail, monorail->maglev). There is the Universal Railtype NewGRF, but not everyone is playing with it.


This comment was imported from FlySpray: https://bugs.openttd.org/task/5914#comment13069

@DorpsGek
Copy link
Member Author

frosch wrote:

The data is cleared when you close the depot window.

Anyway, intentional feature.


This comment was imported from FlySpray: https://bugs.openttd.org/task/5914#comment13070

@DorpsGek
Copy link
Member Author

frosch closed the ticket.

Reason for closing: Not a bug

but a feature


This comment was imported from FlySpray: https://bugs.openttd.org/task/5914

@DorpsGek DorpsGek added Core flyspray This issue is imported from FlySpray (https://bugs.openttd.org/) labels Apr 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
flyspray This issue is imported from FlySpray (https://bugs.openttd.org/)
Projects
None yet
Development

No branches or pull requests

1 participant