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

12/26 Nightly / 0.50.02 SNAPSHOT - completed contracts show all scenarios 'pending', some have bizarre number of assigned units, no contract currently active. #5543

Closed
7 tasks done
OrbMonky opened this issue Dec 28, 2024 · 4 comments · Fixed by #5549

Comments

@OrbMonky
Copy link

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 *

Low (Minor/Nuisance): Minor glitches or cosmetic issues that don’t affect gameplay and occur rarely.

Brief Description *

I doubt this has any real impact outside of records loss, but I am out of a contract and upgraded to 12/26's nightly. Upon reviewing my Briefing Room, I found this;
image
Dropship Raid on the latter 3026 contract has 477 units assigned somehow

image
All scenarios are set to pending

Again, not on an active contract, but nothing should be showing as pending from what I'm aware of, even if it's meaningless. I guess the question is 'where did the data go?'
logs.zip

Steps to Reproduce

No response

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

Do you have a save from before you noticed this issue?

@OrbMonky
Copy link
Author

OrbMonky commented Dec 28, 2024

That save is from the initial load into the nightly, it technically hasn't been saved in that version

@IllianiCBT
Copy link
Collaborator

We had a bug a few days ago that resulted from contracts failing to load correctly - it was a whole thing. Because the contract failed to load fully it didn't update the status of scenarios (which default to Pending) and, for some reason, dumped the entire TO&E into whatever scenario appears last (possibly first) in the internal array of scenarios for that contract.

This bug was fixed the day it was found, but it looks like you played on the broken version, resulting in the bugged records being enshrined in your save file.

To resolve this error you'd need to roll your campaign back to before the nightly of the 12th. However, this should just be a historical data issue and not cause any negative effects if you chose to continue this campaign - other than looking a bit weird.

Sorry about this one, I know it's a pain.

Closing as resolved.

@IllianiCBT
Copy link
Collaborator

Ignore my earlier message. I've figured out how to fix this retroactively.

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