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
I've tested the issue against at least the latest MILESTONE version
I've asked on the MegaMek Discord about the error
I've reviewed the BattleTech rules and MekHQ documentation, and I've confirmed that something isn't working as intended.
I've searched the Github tracker and haven't found the issue listed
Severity *
Medium (Gameplay Limitation): Non-core functionality is impaired, providing a suboptimal but playable experience.
Brief Description *
Got maybe a thousand(?) of these when running auto repair, which seemed like it froze MekHQ but it eventually recovered.
Seems like it is getting hung up on some ammunition in some conditions.
Included are prior day auto save and campaign save for the day of running the suspect autorepair logs.zip
Steps to Reproduce
Load save, review logs.
Load auto save from prior game day
advance day and run auto repair
Operating System *
Windows 10
Java Version *
17
MekHQ Suite Version *
None
Custom MekHQ Version
12/26 Nightly / 0.50.02 SNAPSHOT
Attach Files
No response
Final Checklist
I've checked to make sure that this issue has not already been filed
I'm reporting only one issue in this ticket for clarity and focus
The text was updated successfully, but these errors were encountered:
It seems like somehow (perhaps due to mothballing and unmothballing), the AC/5 ammo in an arm that isn't attached to the 'mech is able to be reloaded.
Right Torso and Right Arm are missing, ammo is in right arm, and it shows reload-able. It also shows two AC/5 ammo bins, one for standard ammo and one for Flak, but the unit only mounts one AC/5 ammo bin. Scrapping/GM removal/salvage/repair/etc doesn't seem to resolve. Unit appears to be in stuck state.
Discussed with Sleet in Discord, even scrapping the arm doesn't remove the haunted extra ammo bin, it can't ever be successfully loaded, but trying to load it unloads the normal bin. This unit was salvaged from a smart ammo selection enabled game and mothballed, so it seems the only point of origin for this bug might be a weird low probability thing with smart ammo. Will try and find a before-save of the scenario where it was salvaged from.
Found an earlier save where it had already been captured and mothballed, activated and repaired it and this time it worked fine... no extra ammo bin. It was still set to Flak which is funky, but maybe within scope. At this point maybe it's just a weird Repair Bay bug?
Prerequisites and Pre-Issue Checklist
I'm reporting the issue to the correct repository:
MegaMek
MegaMekLab
MekHQ
I've tested the issue against at least the latest MILESTONE version
I've asked on the MegaMek Discord about the error
I've reviewed the BattleTech rules and MekHQ documentation, and I've confirmed that something isn't working as intended.
I've searched the Github tracker and haven't found the issue listed
Severity *
Medium (Gameplay Limitation): Non-core functionality is impaired, providing a suboptimal but playable experience.
Brief Description *
Got maybe a thousand(?) of these when running auto repair, which seemed like it froze MekHQ but it eventually recovered.
Seems like it is getting hung up on some ammunition in some conditions.
Included are prior day auto save and campaign save for the day of running the suspect autorepair
logs.zip
Steps to Reproduce
Operating System *
Windows 10
Java Version *
17
MekHQ Suite Version *
None
Custom MekHQ Version
12/26 Nightly / 0.50.02 SNAPSHOT
Attach Files
No response
Final Checklist
The text was updated successfully, but these errors were encountered: