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

Maintenance checks should occur a quarter as often in garrison conditions #4709

Closed
Saklad5 opened this issue Aug 25, 2024 · 2 comments · Fixed by #4714
Closed

Maintenance checks should occur a quarter as often in garrison conditions #4709

Saklad5 opened this issue Aug 25, 2024 · 2 comments · Fixed by #4714
Assignees

Comments

@Saklad5
Copy link
Contributor

Saklad5 commented Aug 25, 2024

Page 191 of the fourth printing of Campaign Operations has the following:

Maintenance checks are run every week in the field, or once every four weeks when in garrison conditions (not in the field or in combat). Garrison conditions includes when being transported between systems for ground units and small aerospace units.

MekHQ currently only has a single option for controlling how often maintenance checks are performed, and it simply starts each day by checking if a unit hasn't had a maintenance check recently enough. That behavior means that changing it back and forth can lead to every single unit needing checks at the same time, which is especially problematic as this tends to occur the instant you actually need them in the field.

I propose the following change: each unit should have a floating-point value tracking the number of days elapsed since the last maintenance check. This value should increase by 0.25 daily under garrison conditions and 1.00 daily in the field. If that value exceeds the period specified by the relevant campaign option (or double/triple that depending on the Rugged quirk), a maintenance check is performed. That value should be made visible to the player.

When a maintenance check is performed, the timer resets to zero.

@Saklad5
Copy link
Contributor Author

Saklad5 commented Aug 25, 2024

@IllianiCBT

@IllianiCBT
Copy link
Collaborator

Closing as resolved

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 a pull request may close this issue.

2 participants