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

Planet Selection Bug in Manual Contract Creation #5445

Open
7 tasks done
jschmetzer opened this issue Dec 19, 2024 · 0 comments
Open
7 tasks done

Planet Selection Bug in Manual Contract Creation #5445

jschmetzer opened this issue Dec 19, 2024 · 0 comments
Labels
New Feature Used with the RFE tag to indicate a new feature Severity: High Issues described as high severity as per the new issue form

Comments

@jschmetzer
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 *

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

Brief Description *

When creating a contract, the window doesn't recognize the planet selected. It :does: work if you select a planet from a faction list, but for planetless factions (ie, pirates) no planet can be selected.

You get a "Don't forget to select a planet!" warning dialog.

Steps to Reproduce

  1. Download latest (12/19) nightly.
  2. Unpack and start new campaign.
  3. Select 'full stratcon preset' with no customizations necessary
  4. Attempt to create a contract with Pirate as opfor.

Operating System *

Mac

Java Version *

17.0.12

MekHQ Suite Version *

Free Text (type manually)

Custom MekHQ Version

50.02

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
@HammerGS HammerGS added New Feature Used with the RFE tag to indicate a new feature Severity: High Issues described as high severity as per the new issue form labels Jan 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
New Feature Used with the RFE tag to indicate a new feature Severity: High Issues described as high severity as per the new issue form
Projects
None yet
Development

No branches or pull requests

2 participants