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 MegaMekLab 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 *
High (Major Disruption): A major feature is broken or incorrect, but a workaround exists.
Brief Description *
I suspect this bug is caused by the mech -> mek conversion.
When customising or creating a new dropship, it loses any mech bays assigned to it when it is saved. When the unit is reloaded, all bays except the added mech bay will be present and the tonnage shows as free on the design.
Loading existing designs such as the Union works fine in MML, so this seems to only apply to saving the custom.
This only applies to customising dropships from what I can see. No NPE is thrown.
Steps to Reproduce
Load an existing, or create from scratch, a new dropship.
Add bays of different types, including mech bays.
Save the design.
Reload the design
Mech bays disappear from the design when it is loaded again, either in MML, MHQ, or MM.
Operating System *
Windows 11
Java Version *
17.0.12
MegaMek Suite Version *
Free Text (type manually)
Custom MegaMekLab Version
50.01 CI1635 Nightly
Attach Files
N/A
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:
Can confirm that the underlying issue is that it's writing out "mekbay" to the blk file which results in them disappearing when read back in. If you manually change to "mechbay" then things work fine. So assuming this is a result of the mass renaming
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 MegaMekLab 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 *
High (Major Disruption): A major feature is broken or incorrect, but a workaround exists.
Brief Description *
I suspect this bug is caused by the mech -> mek conversion.
When customising or creating a new dropship, it loses any mech bays assigned to it when it is saved. When the unit is reloaded, all bays except the added mech bay will be present and the tonnage shows as free on the design.
Loading existing designs such as the Union works fine in MML, so this seems to only apply to saving the custom.
This only applies to customising dropships from what I can see. No NPE is thrown.
Steps to Reproduce
Operating System *
Windows 11
Java Version *
17.0.12
MegaMek Suite Version *
Free Text (type manually)
Custom MegaMekLab Version
50.01 CI1635 Nightly
Attach Files
N/A
Final Checklist
The text was updated successfully, but these errors were encountered: