Change: Service at depot resets breakdown chance #8317
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.