You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My request is that if you use a tech to mothball a unit that is already doing maintenance, have them only use the time they have available for the mothballing task, similar to how Refits are currently handled. If you have a tech start a refit that doesn't have the full 480 minutes available, the tech only uses their unused time for the refit but continues to maintain their assigned unit(s).
Use Cases or Rationale
Currently, if you mothball a unit using a tech assigned to maintenance, the tech stops doing their maintenance until the mothballing is complete. This results in the next maintenance cycle having a "partially maintained" penalty.
Attach Files
No response
MekHQ Suite Version *
0.50.03-SNAPSHOT
Final Verification
I confirm this request hasn't already been submitted (checked the tracker)
I've discussed or asked about this enhancement on MegaMek Discord
I’m opening this on the correct repo (MegaMek, MegaMekLab, or MekHQ)
The text was updated successfully, but these errors were encountered:
Enhancement Type *
New Feature
Brief Description of Enhancement *
My request is that if you use a tech to mothball a unit that is already doing maintenance, have them only use the time they have available for the mothballing task, similar to how Refits are currently handled. If you have a tech start a refit that doesn't have the full 480 minutes available, the tech only uses their unused time for the refit but continues to maintain their assigned unit(s).
Use Cases or Rationale
Currently, if you mothball a unit using a tech assigned to maintenance, the tech stops doing their maintenance until the mothballing is complete. This results in the next maintenance cycle having a "partially maintained" penalty.
Attach Files
No response
MekHQ Suite Version *
0.50.03-SNAPSHOT
Final Verification
The text was updated successfully, but these errors were encountered: