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

Change: Service at depot resets breakdown chance #8317

Merged
merged 1 commit into from Sep 25, 2020
Merged

Change: Service at depot resets breakdown chance #8317

merged 1 commit into from Sep 25, 2020

Conversation

Galigator
Copy link
Contributor

I have so mush fun with this little change, that I really what to share it.
I have found the idea on Openttd forum.

Each time your vehicle go to service, then the breakdown chance is reset.
It allow to create large trains networks with simple tracks but carefully timed service and length to it.

Services on depot can work a bit like "predictive maintenance". If you do it well, everything goes well, if you start jamming your network sometime everything will go badly wrong after a while. Smoothness is require to operate an interconnection. Also a train waiting in depot for an route, still start raise there breakdown chance, so your buffers must be carefully crafted; but you don't have to do silly/made network with logic to handle breakdown, or disable breakdown.
It just make it playable.

Regards.

Peoples below are right.

@nielsmh
when you're playing with reduced breakdowns, vehicles will never break down right after receiving service (for a while).

@ldpl
This is just the same as the vehicle breaking down, doesn't protect it from further breakdowns completely, only makes it less likely for a while. In some cases it makes it so much less likely that it's effectively 0.

This new PR, correct the #8286 for coding still and is made from the last OpenTTD master.

Copy link
Member

@LordAro LordAro left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

FWIW, the preferred method of updating a PR is to use amending/rebasing/force-pushing, rather than creating a brand new PR. But no matter.

You should also use a branch other than your master branch, to make it easier to do other different things later

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants