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

[0.50] Saving a vehicle with BAR8 armour saves as BAR10, putting the design overweight #1633

Closed
7 tasks done
UlyssesSockdrawer opened this issue Oct 7, 2024 · 1 comment
Closed
7 tasks done

Comments

@UlyssesSockdrawer
Copy link
Collaborator

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 *

Critical (Game-breaking/Crash): The game crashes or a core feature (like saving, loading, or network connection) is completely unusable.

Brief Description *

When editing and saving a vehicle with armour below BAR10 e.g. BAR8, when the design is saved the armour is saved as BAR10 rather than the original BAR level.

This happens even if the user makes no changes to the armour type on the design.

image

Steps to Reproduce

(1) - Open the Sherpa Armoured Truck in MML
(2) - Change nothing on the design. Add a variant name of whatever (I used 2).
(3) - Save the design to your customs folder somewhere. Close MML.
(4) - Reopen MML and try to load the design. Design shows as invalid for being 7 tons overweight.

Operating System *

Windows 11

Java Version *

17.0.12

MegaMek Suite Version *

v0.50.0

Custom MegaMekLab Version

No response

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
@UlyssesSockdrawer
Copy link
Collaborator Author

Whoops, this duplicates #1631 - closing as a duplicate. Will add my steps to reproduce in a comment there.

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

No branches or pull requests

1 participant