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

Multiheaded trainz #1389

Closed
DorpsGek opened this issue Nov 2, 2007 · 1 comment
Closed

Multiheaded trainz #1389

DorpsGek opened this issue Nov 2, 2007 · 1 comment
Labels
flyspray This issue is imported from FlySpray (https://bugs.openttd.org/)

Comments

@DorpsGek
Copy link
Member

DorpsGek commented Nov 2, 2007

Fragster opened the ticket and wrote:

I think, that if we use multiheaded trains, and one of locomotives broke down, others must pull train with their forces. And broken locomotives must be fixed on station, or when it waits on signal...
Optionnally it might be settings, when to fix locomotive - on stops, or immediately after the breakage. In configure patches, or for every train.

PS. sorry for bad english...
PPS. Also i want to know, is there difference between reliability of multiheaded and one-headed trainz? I thought that multiheaded trainz break more often

Reported version: trunk
Operating system: All


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

DorpsGek commented Aug 5, 2017

andythenorth closed the ticket.

Reason for closing: Won't implement

Breakdowns is breakdowns. 10 years later, this is unlikely to change, eh :)


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

@DorpsGek DorpsGek closed this as completed Aug 5, 2017
@DorpsGek DorpsGek added flyspray This issue is imported from FlySpray (https://bugs.openttd.org/) Vehicles labels Apr 6, 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