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

Jump to bottom

Old rail types not buildable after loading game. #33

Closed
DorpsGek opened this issue Dec 24, 2005 · 2 comments
Closed

Old rail types not buildable after loading game. #33

DorpsGek opened this issue Dec 24, 2005 · 2 comments
Labels
flyspray This issue is imported from FlySpray (https://bugs.openttd.org/)

Comments

@DorpsGek
Copy link
Member

peter1138 opened the ticket and wrote:

Upon loading a game, each player's available railtypes are reset according to data from railvehicleinfo. However, it is possible that all engines of a certain type have been made obsolete, and thus the railtype is no longer available. This will mean that the track for the obsolete rail type cannot be built, even if obsolete engines are still running.

Reported version: trunk
Operating system: All

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

peter1138 wrote:

This patch semi-fixes the issue by checking if old obsolete vehicles are in the game.

However, there's probably a better way of doing this :)

This comment was imported from FlySpray: https://bugs.openttd.org/task/33#comment63

@DorpsGek
Copy link
Member Author

peter1138 closed the ticket.

Reason for closing: Fixed

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

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

No branches or pull requests
1 participant
@DorpsGek