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

[v.0.50.02 Nightly 12-20-24] Previously rejected person from prestigious academy able to reapply after graduating from another academy #5498

Closed
7 tasks done
LadyAdia opened this issue Dec 22, 2024 · 1 comment · Fixed by #5552
Labels
Personnel Personnel-related Issues

Comments

@LadyAdia
Copy link
Contributor

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 *

See https://discord.com/channels/458705327911731231/458706545379639296/1320216433510187059

Testing process: Take personnel who has previously been rejected by a prestigious academy. Send them to another academy (local or prestigious) of the same education level that will advance the highest education level. Upon return, the academy that had previously given rejection was available to apply. In both cases I have seen this, the applicant was accepted.

This bug seems inconsistent and does not happen every time.

Steps to Reproduce

See description

Operating System *

Mac

Java Version *

17.0.12

MekHQ Suite Version *

Free Text (type manually)

Custom MekHQ Version

0.50.02 Nightly

Attach Files

MHQ Academy maybe bug maybe feature 24-12-21.zip

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

Closing as resolved

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Personnel Personnel-related Issues
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants