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

Feature: Increased aircraft breakdown rate based on travelled tiles. #7312


Copy link

@SamuXarick SamuXarick commented Mar 3, 2019

This patch adds an expert game setting which increases the chances of an aircraft to breakdown every passing day after travelling a user defined number of tiles since last takeoff, ranging from 1 to 65535. If it's set to 0, the feature is disabled. Requires breakdowns being enabled, and it's only kicking in if the aircraft hasn't broken down yet.

Additionally, aircraft have a new property which allows them to keep track of their currently travelled distance by the means of a counter. Each time an aircraft moves from a tile to another, the count is increased by 1. The maximum limit of this counter is 65535, which is equivalent to saying that it has already changed its tile position 65535 times.

  • Savegames before this patch will treat this game setting as disabled.
  • Aircraft from savegames before this patch don't have the feature to keep track of distance travelled. This patch treats them as having travelled 0 tiles.
  • Default value of this setting is 500 tiles. 0 disables it. It is increased or decreased in steps of 15 tiles when pressing the arrows.

unnamed 1950-12-30

@SamuXarick SamuXarick force-pushed the increased-aircraft-breakdown-rate-based-on-travelled-tiles branch from 53969f9 to 08ab8e3 Compare Mar 3, 2019
Copy link

@PeterN PeterN commented Mar 3, 2019

Reliability decreases (and therefore breakdown chance increases) already over time. This does not seem necessary.

Copy link

@TrueBrain TrueBrain commented Mar 3, 2019

I agree; yet another variable, which doesn't seem to have a clear benefit. Going to close this PR for that reason. Nevertheless, tnx for your contribution! (not all features can make it in!)

@TrueBrain TrueBrain closed this Mar 3, 2019
@TrueBrain TrueBrain added the won't implement label Mar 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
won't implement
None yet

Successfully merging this pull request may close these issues.

None yet

3 participants