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

[Issue]50.03 Preserve Victory Condition Does Not List Units Correctly #5979

Closed
5 tasks done
cheesemandan123 opened this issue Feb 4, 2025 · 0 comments · Fixed by #6003
Closed
5 tasks done

[Issue]50.03 Preserve Victory Condition Does Not List Units Correctly #5979

cheesemandan123 opened this issue Feb 4, 2025 · 0 comments · Fixed by #6003
Assignees

Comments

@cheesemandan123
Copy link

Brief Description *

The endgame victory point scoring does not list friendly units that have been preserved.

Image

In this case, it is the dropship defense mission, with delta lance deployed and using beta as the seed to generate the scenario. It is under liaison command rights. The screenshot is immediately after the battle, but the result is the same if you use either PACAR, ACAR, or manually fight it.

I do not know for sure if it is this scenario type exactly and will update later.

3. Steps to Reproduce

  1. Load up the campaign file, the dropship mission is setup to go.
  2. Resolve the mission in any manner.
  3. At the end in the VP screen, it lists no units under the preserve objective.

Attach Files

Howling Gryffons30490224.cpnx.gz

logs.zip

Severity *

High (Major Disruption): A major feature is broken or incorrect, but a workaround exists.

MekHQ Suite Version *

50.03

Operating System *

Windows 11

Java Version *

Eclipse Adoptium 17.0.13

Final Verification

  • I confirm this is a single, unique issue that hasn't been reported before
  • I have filled and provided all necessary information above
  • I have included any and all logs, custom units, and CPNX (save) files
  • I have asked on MegaMek Discord about this issue
  • I have confirmed this issue is being opened on the correct repository: MegaMek, MegaMekLab, or MekHQ
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